<?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>30</NO>
  <DATE>Wednesday, February 13, 2013</DATE>
  <UNITNAME>Contents</UNITNAME>
  <CNTNTS>
    <AGCY>
      <EAR>Agency Health</EAR>
      <PRTPAGE P="iii"/>
      <HD>Agency for Healthcare Research and Quality</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>10175-10178</PGS>
          <FRDOCBP D="3" T="13FEN1.sgm">2013-03217</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Agricultural Marketing</EAR>
      <HD>Agricultural Marketing Service</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Watermelon Research and Promotion Plan:</SJ>
        <SJDENT>
          <SJDOC>Importer Membership Requirements,</SJDOC>
          <PGS>10104-10107</PGS>
          <FRDOCBP D="3" T="13FEP1.sgm">2013-02975</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>Natural Resources Conservation Service</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Rural Utilities Service</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Architectural</EAR>
      <HD>Architectural and Transportation Barriers Compliance Board</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Shared Use Paths:</SJ>
        <SJDENT>
          <SJDOC>Accessibility Guidelines for Pedestrian Facilities in Public Right-of-Way,</SJDOC>
          <PGS>10110-10117</PGS>
          <FRDOCBP D="7" T="13FEP1.sgm">2013-03298</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Consumer Financial Protection</EAR>
      <HD>Bureau of Consumer Financial Protection</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Appraisals for Higher-Priced Mortgage Loans,</DOC>
          <PGS>10368-10447</PGS>
          <FRDOCBP D="79" T="13FER3.sgm">2013-01809</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Children</EAR>
      <HD>Children and Families Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>10178-10179</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03253</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Coast Guard</EAR>
      <HD>Coast Guard</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Safety Zones:</SJ>
        <SJDENT>
          <SJDOC>Sea World San Diego Fireworks, Mission Bay; San Diego, CA,</SJDOC>
          <PGS>10062-10064</PGS>
          <FRDOCBP D="2" T="13FER1.sgm">2013-03261</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Vigor Industrial Roll-Out, West Duwamish Waterway, Seattle, WA,</SJDOC>
          <PGS>10064-10066</PGS>
          <FRDOCBP D="2" T="13FER1.sgm">2013-03264</FRDOCBP>
        </SJDENT>
      </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>International Trade Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Oceanic and Atmospheric Administration</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Comptroller</EAR>
      <HD>Comptroller of the Currency</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Appraisals for Higher-Priced Mortgage Loans,</DOC>
          <PGS>10368-10447</PGS>
          <FRDOCBP D="79" T="13FER3.sgm">2013-01809</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Delaware</EAR>
      <HD>Delaware River Basin Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Commission Meeting and Public Hearing,</DOC>
          <PGS>10160-10161</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03281</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR/>
      <HD>Department of Transportation</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Pipeline and Hazardous Materials Safety Administration</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Education Department</EAR>
      <HD>Education Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>National Advisory Committee on Institutional Quality and Integrity,</SJDOC>
          <PGS>10161-10163</PGS>
          <FRDOCBP D="2" T="13FEN1.sgm">2013-03314</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Energy Department</EAR>
      <HD>Energy Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Energy Regulatory Commission</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Draft Section 3116 Basis for Determination for Closure of H Tank Farm at the Savannah River Site; Availability,</DOC>
          <PGS>10163-10164</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03305</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Environmental Protection</EAR>
      <HD>Environmental Protection Agency</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>National Primary Drinking Water Regulations:</SJ>
        <SJDENT>
          <SJDOC>Revisions to the Total Coliform Rule,</SJDOC>
          <PGS>10270-10365</PGS>
          <FRDOCBP D="95" T="13FER2.sgm">2012-31205</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Access Interpreting; Transfer of Data,</DOC>
          <PGS>10166-10167</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03330</FRDOCBP>
        </DOCENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Pollinator Summit; Status of Ongoing Collaborative Efforts to Protect Pollinators,</SJDOC>
          <PGS>10167</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03332</FRDOCBP>
        </SJDENT>
        <SJ>Pesticide Products:</SJ>
        <SJDENT>
          <SJDOC>Registration Applications for a New Active Ingredient,</SJDOC>
          <PGS>10167-10168</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03333</FRDOCBP>
        </SJDENT>
      </CAT>
    </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>10168-10169</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03213</FRDOCBP>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03265</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Aviation</EAR>
      <HD>Federal Aviation Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Special Conditions:</SJ>
        <SJDENT>
          <SJDOC>Tamarack Aerospace Group, Cirrus Model SR22; Active Technology Load Alleviation System,</SJDOC>
          <PGS>10055-10058</PGS>
          <FRDOCBP D="3" T="13FER1.sgm">2013-03296</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures,</DOC>
          <PGS>10058-10062</PGS>
          <FRDOCBP D="2" T="13FER1.sgm">2013-03146</FRDOCBP>
          <FRDOCBP D="2" T="13FER1.sgm">2013-03147</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Waivers of Aeronautical Land-Use Assurance:</SJ>
        <SJDENT>
          <SJDOC>Chicago Executive Airport, Wheeling, IL,</SJDOC>
          <PGS>10247-10248</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03334</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Lewis University Airport, Romeoville, IL,</SJDOC>
          <PGS>10248</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03336</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Communications</EAR>
      <HD>Federal Communications Commission</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Data Specifications for Collecting Study Area Boundaries,</DOC>
          <PGS>10100-10102</PGS>
          <FRDOCBP D="2" T="13FER1.sgm">2013-03328</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Establishment of a Public Safety Answering Point Do-Not-Call Registry; Correcting Amendments,</DOC>
          <PGS>10099-10100</PGS>
          <FRDOCBP D="1" T="13FER1.sgm">2013-03230</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Communications Security, Reliability, and Interoperability Council,</SJDOC>
          <PGS>10169-10170</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03327</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Election</EAR>
      <HD>Federal Election Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Filing Dates:</SJ>
        <SJDENT>
          <SJDOC>Massachusetts Senate Special Elections,</SJDOC>
          <PGS>10170-10171</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03225</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>South Carolina Special Elections in the 1st Congressional District,</SJDOC>
          <PGS>10171-10172</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03226</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Emergency</EAR>
      <HD>Federal Emergency Management Agency</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Final Flood Elevation Determinations,</DOC>
          <PGS>10066-10085</PGS>
          <FRDOCBP D="13" T="13FER1.sgm">2013-03258</FRDOCBP>
          <FRDOCBP D="6" T="13FER1.sgm">2013-03259</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Changes in Flood Hazard Determinations,</DOC>
          <PGS>10189-10198</PGS>
          <FRDOCBP D="4" T="13FEN1.sgm">2013-03255</FRDOCBP>
          <FRDOCBP D="4" T="13FEN1.sgm">2013-03256</FRDOCBP>
          <FRDOCBP D="3" T="13FEN1.sgm">2013-03257</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Energy</EAR>
      <PRTPAGE P="iv"/>
      <HD>Federal Energy Regulatory Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Combined Filings,</DOC>
          <PGS>10164-10166</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03300</FRDOCBP>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03301</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Highway</EAR>
      <HD>Federal Highway Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
        <SJDENT>
          <SJDOC>Will and Kankakee Counties, IL and Lake County, IN,</SJDOC>
          <PGS>10249</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03289</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Establishment of National Freight Network,</DOC>
          <PGS>10249</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">C1--2013--02580</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Final Federal Agency Actions on Proposed Highway in California; Limitation on Claims,</DOC>
          <PGS>10249-10250</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03307</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Housing Finance Agency</EAR>
      <HD>Federal Housing Finance Agency</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Appraisals for Higher-Priced Mortgage Loans,</DOC>
          <PGS>10368-10447</PGS>
          <FRDOCBP D="79" T="13FER3.sgm">2013-01809</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Maritime</EAR>
      <HD>Federal Maritime Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agreements Filed,</DOC>
          <PGS>10172</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03325</FRDOCBP>
        </DOCENT>
        <SJ>Complaints:</SJ>
        <SJDENT>
          <SJDOC>Lisa Anne Cornell and G. Ware Cornell, Jr. v. Princess Cruise Lines, Ltd (Corp), Carnival plc, and Carnival Corp,</SJDOC>
          <PGS>10172-10173</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03322</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Ocean Transportation Intermediary License Applicants,</DOC>
          <PGS>10173</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03320</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Motor</EAR>
      <HD>Federal Motor Carrier Safety Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Qualification of Drivers; Exemption Applications; Vision,</DOC>
          <PGS>10250-10253</PGS>
          <FRDOCBP D="2" T="13FEN1.sgm">2013-03337</FRDOCBP>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03338</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Reserve</EAR>
      <HD>Federal Reserve System</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Appraisals for Higher-Priced Mortgage Loans,</DOC>
          <PGS>10368-10447</PGS>
          <FRDOCBP D="79" T="13FER3.sgm">2013-01809</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Change in Bank Control Notices; Acquisitions of Shares of a Bank or Bank Holding Company,</DOC>
          <PGS>10173-10174</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03284</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Transit</EAR>
      <HD>Federal Transit Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Certifications and Assurances for Grants and Cooperative Agreements; FY 2013,</DOC>
          <PGS>10253-10260</PGS>
          <FRDOCBP D="7" T="13FEN1.sgm">2013-03335</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Fish</EAR>
      <HD>Fish and Wildlife Service</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Endangered and Threatened Wildlife and Plants:</SJ>
        <SJDENT>
          <SJDOC>Designation of Critical Habitat for Astragalus lentiginosus var. coachellae (Coachella Valley milk-vetch),</SJDOC>
          <PGS>10450-10497</PGS>
          <FRDOCBP D="47" T="13FER4.sgm">2013-03109</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Captive Wildlife Safety Act,</SJDOC>
          <PGS>10200-10201</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03283</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Declaration for Importation or Exportation of Fish or Wildlife,</SJDOC>
          <PGS>10198-10200</PGS>
          <FRDOCBP D="2" T="13FEN1.sgm">2013-03280</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Electronic Duck Stamp Program,</SJDOC>
          <PGS>10201-10202</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03286</FRDOCBP>
        </SJDENT>
        <SJ>Endangered and Threatened Wildlife and Plants:</SJ>
        <SJDENT>
          <SJDOC>Incidental Take Permit; Proposed Low-Effect Habitat Conservation Plan; Martin County, FL,</SJDOC>
          <PGS>10202-10203</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03287</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Food and Drug</EAR>
      <HD>Food and Drug Administration</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Standards for the Growing, Harvesting, Packing, and Holding of Produce for Human Consumption and for Current Good Manufacturing Practice and Hazard Analysis and Risk-Based Preventive Controls for Human Food; Public Meeting,</DOC>
          <PGS>10107-10110</PGS>
          <FRDOCBP D="3" T="13FEP1.sgm">2013-03316</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>10179-10180</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03315</FRDOCBP>
        </DOCENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Annual Computational Science Symposium,</SJDOC>
          <PGS>10180-10181</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03324</FRDOCBP>
        </SJDENT>
        <SJ>Public Workshops:</SJ>
        <SJDENT>
          <SJDOC>Global Quality Systems--An Integrated Approach to Improving Medical Product Safety,</SJDOC>
          <PGS>10181</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03323</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Submission of an Electronic Common Technical Document,</DOC>
          <PGS>10181-10182</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03319</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Foreign Trade</EAR>
      <HD>Foreign-Trade Zones Board</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Expansions and Reorganizations of Foreign-Trade Zones under Alternative Site Framework:</SJ>
        <SJDENT>
          <SJDOC>Foreign-Trade Zone 90; Onondaga County, NY,</SJDOC>
          <PGS>10129</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03362</FRDOCBP>
        </SJDENT>
        <SJ>Expansions and Reorganizations of Foreign-Trade Zones:</SJ>
        <SJDENT>
          <SJDOC>Subzone 70T; Marathon Petroleum Co. LP; Detroit, MI,</SJDOC>
          <PGS>10128</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03352</FRDOCBP>
        </SJDENT>
        <SJ>Expansions of Manufacturing Authority:</SJ>
        <SJDENT>
          <SJDOC>Mitsubishi Power Systems Americas, Inc., Foreign-Trade Zone 104, Pooler, GA,</SJDOC>
          <PGS>10129</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03308</FRDOCBP>
        </SJDENT>
        <SJ>Reorganization of Foreign-Trade Zones under Alternative Site Framework:</SJ>
        <SJDENT>
          <SJDOC>Foreign-Trade Zone 70; Detroit, MI,</SJDOC>
          <PGS>10129-10130</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03363</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>General Services</EAR>
      <HD>General Services Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Public Availability of General Services:</SJ>
        <SJDENT>
          <SJDOC>Administration FY 2012 Service Contract Inventory,</SJDOC>
          <PGS>10174</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03279</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Health and Human</EAR>
      <HD>Health and Human Services Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Agency for Healthcare Research and Quality</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>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>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>10174-10175</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03270</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Health Resources</EAR>
      <HD>Health Resources and Services Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Ryan White HIV/AIDS Program Early Intervention Services Grants,</DOC>
          <PGS>10182-10184</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03291</FRDOCBP>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03292</FRDOCBP>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03293</FRDOCBP>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03295</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR/>
      <HD>Healthcare Research and Quality Agency</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Agency for Healthcare Research and Quality</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Homeland</EAR>
      <HD>Homeland Security Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Coast Guard</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Emergency Management Agency</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Housing</EAR>
      <HD>Housing and Urban Development Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>10198</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03306</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Indian Affairs</EAR>
      <HD>Indian Affairs Bureau</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Indian Gaming:</SJ>
        <SJDENT>
          <SJDOC>Approved Tribal-State Class III Gaming Compact,</SJDOC>
          <PGS>10203</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03326</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Interior</EAR>
      <HD>Interior Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Fish and Wildlife Service</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Indian Affairs Bureau</P>
      </SEE>
      <SEE>
        <PRTPAGE P="v"/>
        <HD SOURCE="HED">See</HD>
        <P>Land Management Bureau</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Internal Revenue</EAR>
      <HD>Internal Revenue Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>10263-10265</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03086</FRDOCBP>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03244</FRDOCBP>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03245</FRDOCBP>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03246</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>International Trade Adm</EAR>
      <HD>International Trade Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Antidumping Duty Administrative Reviews; Results, Extensions, Amendments, etc.:</SJ>
        <SJDENT>
          <SJDOC>Narrow Woven Ribbons With Woven Selvedge from the People's Republic of China,</SJDOC>
          <PGS>10130-10134</PGS>
          <FRDOCBP D="4" T="13FEN1.sgm">2013-03236</FRDOCBP>
        </SJDENT>
        <SJ>Antidumping Duty Orders; Expedited Second Sunset Review:</SJ>
        <SJDENT>
          <SJDOC>Welded Large Diameter Line Pipe from Japan,</SJDOC>
          <PGS>10134-10135</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03364</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>International Trade Com</EAR>
      <HD>International Trade Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Determinations:</SJ>
        <SJDENT>
          <SJDOC>Utility Scale Wind Towers from China and Vietnam,</SJDOC>
          <PGS>10210-10211</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03317</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Justice Department</EAR>
      <HD>Justice Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Proposed Consent Decrees under CERCLA,</DOC>
          <PGS>10211</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03313</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Labor Department</EAR>
      <HD>Labor Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Occupational Safety and Health Administration</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Securities Lending by Employee Benefit Plans,</SJDOC>
          <PGS>10211-10212</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03318</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Land</EAR>
      <HD>Land Management Bureau</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Final Supplementary Rules for Public Lands:</SJ>
        <SJDENT>
          <SJDOC>Arkansas River Travel Management Area in Chaffee, Custer, and Fremont Counties, CO,</SJDOC>
          <PGS>10203-10206</PGS>
          <FRDOCBP D="3" T="13FEN1.sgm">2013-03299</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Mendocino, Glenn, Colusa, Napa, Marin, Yolo, and Solano Counties, CA,</SJDOC>
          <PGS>10206-10209</PGS>
          <FRDOCBP D="3" T="13FEN1.sgm">2013-03282</FRDOCBP>
        </SJDENT>
        <SJ>Plats of Survey:</SJ>
        <SJDENT>
          <SJDOC>Nevada,</SJDOC>
          <PGS>10209-10210</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03288</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Legal</EAR>
      <HD>Legal Services Corporation</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Recompetition; Enforcement; Suspension Procedures; Private Attorney Involvement:</SJ>
        <SJDENT>
          <SJDOC>Limited Reductions of Funding, Termination, and Debarment Procedures,</SJDOC>
          <PGS>10085-10099</PGS>
          <FRDOCBP D="14" T="13FER1.sgm">2013-03241</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Maritime</EAR>
      <HD>Maritime Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>10260</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03297</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>NASA</EAR>
      <HD>National Aeronautics and Space Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>NASA Advisory Council Commercial Space Committee,</SJDOC>
          <PGS>10213-10214</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03209</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Archives</EAR>
      <HD>National Archives and Records Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Records Schedules,</DOC>
          <PGS>10214-10215</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03294</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Credit</EAR>
      <HD>National Credit Union Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Appraisals for Higher-Priced Mortgage Loans,</DOC>
          <PGS>10368-10447</PGS>
          <FRDOCBP D="79" T="13FER3.sgm">2013-01809</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>10186</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03243</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Eunice Kennedy Shriver National Institute of Child Health and Human Development,</SJDOC>
          <PGS>10184-10187</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03233</FRDOCBP>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03234</FRDOCBP>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03235</FRDOCBP>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03237</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Center for Complementary and Alternative Medicine,</SJDOC>
          <PGS>10184</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03242</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Heart, Lung, and Blood Institute,</SJDOC>
          <PGS>10185-10186</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03240</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Institute of Biomedical Imaging and Bioengineering,</SJDOC>
          <PGS>10185</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03238</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Institute on Alcohol Abuse and Alcoholism,</SJDOC>
          <PGS>10185</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03239</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Oceanic</EAR>
      <HD>National Oceanic and Atmospheric Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Fisheries of the Caribbean, Gulf of Mexico, and South Atlantic:</SJ>
        <SJDENT>
          <SJDOC>Snapper-Grouper Resources of the South Atlantic; Trip Limit Reduction,</SJDOC>
          <PGS>10102</PGS>
          <FRDOCBP D="0" T="13FER1.sgm">2013-03311</FRDOCBP>
        </SJDENT>
        <SJ>Fisheries of the Exclusive Economic Zone Off Alaska:</SJ>
        <SJDENT>
          <SJDOC>Pacific Cod by Vessels Using Pot Gear in the Central Regulatory Area of the Gulf of Alaska,</SJDOC>
          <PGS>10102-10103</PGS>
          <FRDOCBP D="1" T="13FER1.sgm">2013-03310</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Fisheries of the Caribbean, Gulf of Mexico, and South Atlantic:</SJ>
        <SJDENT>
          <SJDOC>Reef Fish Fishery of Gulf of Mexico; Amendment 37,</SJDOC>
          <PGS>10122-10126</PGS>
          <FRDOCBP D="4" T="13FEP1.sgm">2013-03372</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Fishing Capacity Reduction Program:</SJ>
        <SJDENT>
          <SJDOC>Longline Catcher Processor Subsector of the Bering Sea and Aleutian Islands Non Pollock Groundfish Fishery,</SJDOC>
          <PGS>10135-10136</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03350</FRDOCBP>
        </SJDENT>
        <SJ>Magnuson-Stevens Act Provisions:</SJ>
        <SJDENT>
          <SJDOC>Fisheries of the Northeastern United States; Northeast Multispecies Fishery, Approved Monitoring Service Providers,</SJDOC>
          <PGS>10136-10137</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03371</FRDOCBP>
        </SJDENT>
        <SJ>Takes of Marine Mammals Incidental to Specified Activities:</SJ>
        <SJDENT>
          <SJDOC>Marine Geophysical Survey on the Mid-Atlantic Ridge in the Atlantic Ocean, April 2013 through June 2013,</SJDOC>
          <PGS>10137-10160</PGS>
          <FRDOCBP D="23" T="13FEN1.sgm">2013-03321</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Science</EAR>
      <HD>National Science Foundation</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Service Contract Inventory, FY 2012; Availability,</DOC>
          <PGS>10215</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03302</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Resources</EAR>
      <HD>Natural Resources Conservation Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Requests for Nominations:</SJ>
        <SJDENT>
          <SJDOC>Agricultural Air Quality Task Force,</SJDOC>
          <PGS>10127-10128</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03247</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Nuclear Regulatory</EAR>
      <HD>Nuclear Regulatory Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>10215-10216</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03263</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Occupational Safety Health Adm</EAR>
      <HD>Occupational Safety and Health Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Walking and Working Surfaces Standard for General Industry,</SJDOC>
          <PGS>10212-10213</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03229</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Pipeline</EAR>
      <PRTPAGE P="vi"/>
      <HD>Pipeline and Hazardous Materials Safety Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Gas Distribution Annual Report,</SJDOC>
          <PGS>10261-10262</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03331</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Rural Utilities</EAR>
      <HD>Rural Utilities Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>10128</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03346</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Securities</EAR>
      <HD>Securities and Exchange Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Rule 15b1-1/Form BD,</SJDOC>
          <PGS>10218</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03272</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Rule 17f-4,</SJDOC>
          <PGS>10216-10217</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03273</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Rule 606 of Regulation NMS,</SJDOC>
          <PGS>10217-10218</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03271</FRDOCBP>
        </SJDENT>
        <SJ>Extensions of Temporary Exemptions:</SJ>
        <SJDENT>
          <SJDOC>Revision of the Definition of Security to Encompass Security-Based Swaps,</SJDOC>
          <PGS>10218-10220</PGS>
          <FRDOCBP D="2" T="13FEN1.sgm">2013-03214</FRDOCBP>
        </SJDENT>
        <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
        <SJDENT>
          <SJDOC>BATS Exchange, Inc.,</SJDOC>
          <PGS>10229-10233</PGS>
          <FRDOCBP D="4" T="13FEN1.sgm">2013-03304</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Chicago Board Options Exchange, Inc.,</SJDOC>
          <PGS>10228-10229</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03274</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>ICE Clear Europe Ltd.,</SJDOC>
          <PGS>10220-10222</PGS>
          <FRDOCBP D="2" T="13FEN1.sgm">2013-03277</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>New York Stock Exchange LLC,</SJDOC>
          <PGS>10226-10228</PGS>
          <FRDOCBP D="2" T="13FEN1.sgm">2013-03275</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>NYSE Arca, Inc.,</SJDOC>
          <PGS>10222-10226, 10233-10246</PGS>
          <FRDOCBP D="4" T="13FEN1.sgm">2013-03276</FRDOCBP>
          <FRDOCBP D="13" T="13FEN1.sgm">2013-03278</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Small Business</EAR>
      <HD>Small Business Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>10246-10247</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03222</FRDOCBP>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03223</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Surface Transportation</EAR>
      <HD>Surface Transportation Board</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Railroad Cost Recovery Procedures, Productivity Adjustment,</DOC>
          <PGS>10262</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03309</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Release of Waybill Data,</DOC>
          <PGS>10262</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03444</FRDOCBP>
        </DOCENT>
        <SJ>Temporary Trackage Rights Exemptions:</SJ>
        <SJDENT>
          <SJDOC>Norfolk Southern Railway Co. from Grand Trunk Western Railroad Co. and Wisconsin Central Ltd.,</SJDOC>
          <PGS>10262-10263</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03345</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 Highway Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Motor Carrier Safety Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Transit Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Maritime Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Pipeline and Hazardous Materials Safety Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Surface Transportation Board</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Treasury</EAR>
      <HD>Treasury Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Comptroller of the Currency</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Internal Revenue Service</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>United States Mint</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>U.S. Mint</EAR>
      <HD>United States Mint</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Pricing for the 2013 Commemorative Coin Programs; Silver and Clad Coin Options,</DOC>
          <PGS>10265</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03231</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Veteran Affairs</EAR>
      <HD>Veterans Affairs Department</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Use of Medicare Procedures to Enter Into Provider Agreements for Extended Care Services,</DOC>
          <PGS>10117-10122</PGS>
          <FRDOCBP D="5" T="13FEP1.sgm">2013-02993</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Declaration of Status of Dependents,</SJDOC>
          <PGS>10266</PGS>
          <FRDOCBP D="0" T="13FEN1.sgm">2013-03262</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Veterans Application for Assistance in Acquiring Special Housing Adaptations,</SJDOC>
          <PGS>10266-10267</PGS>
          <FRDOCBP D="1" T="13FEN1.sgm">2013-03260</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <PTS>
      <HD SOURCE="HED">Separate Parts In This Issue</HD>
      <HD>Part II</HD>
      <DOCENT>
        <DOC>Environmental Protection Agency,</DOC>
        <PGS>10270-10365</PGS>
        <FRDOCBP D="95" T="13FER2.sgm">2012-31205</FRDOCBP>
      </DOCENT>
      <HD>Part III</HD>
      <DOCENT>
        <DOC>Bureau of Consumer Financial Protection,</DOC>
        <PGS>10368-10447</PGS>
        <FRDOCBP D="79" T="13FER3.sgm">2013-01809</FRDOCBP>
      </DOCENT>
      <DOCENT>
        <DOC>Federal Housing Finance Agency,</DOC>
        <PGS>10368-10447</PGS>
        <FRDOCBP D="79" T="13FER3.sgm">2013-01809</FRDOCBP>
      </DOCENT>
      <DOCENT>
        <DOC>Federal Reserve System,</DOC>
        <PGS>10368-10447</PGS>
        <FRDOCBP D="79" T="13FER3.sgm">2013-01809</FRDOCBP>
      </DOCENT>
      <DOCENT>
        <DOC>National Credit Union Administration,</DOC>
        <PGS>10368-10447</PGS>
        <FRDOCBP D="79" T="13FER3.sgm">2013-01809</FRDOCBP>
      </DOCENT>
      <DOCENT>
        <DOC>Treasury Department, Comptroller of the Currency,</DOC>
        <PGS>10368-10447</PGS>
        <FRDOCBP D="79" T="13FER3.sgm">2013-01809</FRDOCBP>
      </DOCENT>
      <HD>Part IV</HD>
      <DOCENT>
        <DOC>Interior Department, Fish and Wildlife Service,</DOC>
        <PGS>10450-10497</PGS>
        <FRDOCBP D="47" T="13FER4.sgm">2013-03109</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>30</NO>
  <DATE>Wednesday, February 13, 2013</DATE>
  <UNITNAME>Rules and Regulations</UNITNAME>
  <RULES>
    <RULE>
      <PREAMB>
        <PRTPAGE P="10055"/>
        <AGENCY TYPE="F">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Federal Aviation Administration</SUBAGY>
        <CFR>14 CFR Part 23</CFR>
        <DEPDOC>[Docket No. FAA-2012-0485; Special Conditions No. 23-258A-SC]</DEPDOC>
        <SUBJECT>Special Conditions: Tamarack Aerospace Group, Cirrus Model SR22; Active Technology Load Alleviation System (ATLAS)</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Aviation Administration (FAA), DOT.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Amended final special conditions; request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This action amends special conditions No. 23-258-SC, issued on July 13, 2012, for the Tamarack Aerospace Group's modification to the Cirrus Model SR22 airplane. This amendment clarifies the intent of two requirements: The requirement for reporting of load alleviation system failures (see paragraph (c) under Loads, Probability of Failure of Load Alleviation System) and the requirement for consideration of limit loads with an unannunciated load alleviation system failure (see paragraph (b) under Factor of Safety, Load Alleviation Systems). This airplane as modified by Tamarack will have a novel or unusual design feature(s) associated with Tamarack Aerospace Group's modification. The design change will install winglets and an Active Technology Load Alleviation System (ATLAS). The addition of the ATLAS mitigates the negative effects of the winglets by effectively aerodynamically turning off the winglet under limit gust and maneuver loads. This is accomplished by measuring the aircraft loading and moving a small aileron-like device called a Tamarack Active Control Surface (TACS). The TACS movement reduces lift at the tip of the wing, resulting in the wing center of pressure moving inboard, thus reducing bending stresses along the wing span. The applicable airworthiness regulations do not contain adequate or appropriate safety standards for this design feature. These final special conditions contain the additional safety standards that the Administrator considers necessary to establish a level of safety equivalent to that established by the existing airworthiness standards. Additionally, this amendment corrects the issue date of special condition No. 23-258-SC to July 13, 2012.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This final rule is effective February 13, 2013, and is applicable beginning February 6, 2013. Comments must be received by March 15, 2013.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Send comments identified by docket number FAA-2012-0485 using any of the following methods:</P>
          <P>•<E T="03">Federal eRegulations Portal:</E>Go to<E T="03">http://www.regulations.gov</E>and follow the online instructions for sending your comments electronically.</P>
          <P>•<E T="03">Mail:</E>Send comments to Docket Operations, M-30, U.S. Department of Transportation (DOT), 1200 New Jersey Avenue SE., Room W12-140, West Building Ground Floor, Washington, DC 20590-0001.</P>
          <P>•<E T="03">Hand Delivery of Courier:</E>Take comments to Docket Operations in Room W12-140 of the West Building Ground Floor at 1200 New Jersey Avenue SE., Washington, DC, between 8 a.m., and 5 p.m., Monday through Friday, except Federal holidays.</P>
          <P>•<E T="03">Fax:</E>Fax comments to Docket Operations at 202-493-2251.</P>
          <P>
            <E T="03">Privacy:</E>The FAA will post all comments it receives, without change, to<E T="03">http://regulations.gov,</E>including any personal information the commenter provides. Using the search function of the docket web site, anyone can find and read the electronic form of all comments received into any FAA docket, including the name of the individual sending the comment (or signing the comment for an association, business, labor union, etc.). DOT's complete Privacy Act Statement can be found in the<E T="04">Federal Register</E>published on April 11, 2000 (65 FR 19477-19478), as well as at<E T="03">http://DocketsInfo.dot.gov.</E>
          </P>
          <P>
            <E T="03">Docket:</E>Background documents or comments received may be read at<E T="03">http://www.regulations.gov</E>at any time. Follow the online instructions for accessing the docket or go to the Docket Operations in Room W12-140 of the West Building Ground Floor at 1200 New Jersey Avenue SE., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>For sections 23.301 through 23.629 (structural requirements), contact Mr. Mike Reyer; telephone (816)-329-4131. For sections 23.672 through 23.701 (control system requirements), contact Mr. Ross Schaller; telephone (816)-329-4162. The address and facsimile for both Mr. Reyer and Mr. Schaller is: Federal Aviation Administration, Small Airplane Directorate, Aircraft Certification Service, 901 Locust, Kansas City, Missouri 64106; facsimile (816) 329-4090.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Comments Invited</HD>
        <P>We invite interested people to take part in this rulemaking by sending written comments, data, or views. The most helpful comments reference a specific portion of the special conditions, explain the reason for any recommended change, and include supporting data.</P>
        <P>We will consider all comments we receive on or before the closing date for comments. We will consider comments filed late if it is possible to do so without incurring expense or delay. We may change these special conditions based on the comments we receive.</P>
        <HD SOURCE="HD1">Background</HD>
        <P>On February 15, 2011, Tamarack Aerospace Group applied for a supplemental type certificate for installation of winglets and an Active Technology Load Alleviation System (ATLAS) on the Cirrus Model SR 22 (serial numbers 0002—2333, 2335—2419, and 2421—2437). The Cirrus model SR22 is a certified, single reciprocating engine, four-passenger, composite airplane.</P>

        <P>The installation of winglets, as proposed by Tamarack, increases aerodynamic efficiency. However, the winglets by themselves also increase wing static loads and the wing fatigue stress ratio, which under limit gust and maneuver loads factors may exceed the certificated wing design limits. The addition of ATLAS mitigates the negative effects of the winglets by effectively aerodynamically turning off the winglet at elevated gust and maneuver loads factors.<PRTPAGE P="10056"/>
        </P>
        <P>The ATLAS functions as a load-relief system. This is accomplished by measuring aircraft loading via an accelerometer, and by moving a small aileron-like device called a Tamarack Active Control Surface (TACS) that reduces lift at the tip of the wing. Because the ATLAS compensates for the increased wing root bending at elevated load factors, the overall effect of this modification is that the winglet can be added to the Cirrus wing without the traditionally required reinforcement of the existing structure. This is the first application of an active loads alleviation system on a part 23 aircraft and the applicable airworthiness regulations do not contain adequate or appropriate safety standards for this design feature.</P>
        <HD SOURCE="HD1">Type Certification Basis</HD>
        <P>Under the provisions of § 21.101, Tamarack Aerospace Group must show that the Cirrus Model SR22, as changed, continues to meet the applicable provisions of the regulations incorporated by reference in Type Certificate Data Sheet A00009CH or the applicable regulations in effect on the date of application for the change. The regulations incorporated by reference in the type certificate are commonly referred to as the “original type certification basis.” The regulations incorporated by reference in Type Certificate Data Sheet A00009CH (Serial Numbers (S/Ns) 0002 through 2333, 2335 through 2419, and 2421 through 2437) are as follows:</P>
        <P>14 CFR part 23 of the Federal Aviation Regulations, effective February 1, 1965, as amended by 23-1 through 23-53, except as follows:</P>
        
        <FP SOURCE="FP-1">14 CFR 23.301 through Amendment 42</FP>
        <FP SOURCE="FP-1">14 CFR 23.855, 23.1326, 23.1359 not applicable</FP>
        <FP SOURCE="FP-1">14 CFR part 36, dated December 1, 1969, as amended by 36-1 through 36-22</FP>
        <P>Except for:</P>
        
        <FP SOURCE="FP-1">Increase in amendment level from the Cirrus Model SR22 certification basis for regulation 14 CFR 23.301 through Amendment 23-42 to: 14 CFR 23.301 through Amendment 23-48.</FP>
        <P>Addition of regulation 14 CFR 23.1306 through Amendment 23-61.</P>
        <P>Addition of regulation 14 CFR 23.1308 through Amendment 23-57.</P>
        <P>Change in Cirrus model SR22 certification basis for regulation 14 CFR 23.1359 through Amendment 23-49 from: Not Applicable to: Applicable</P>
        <HD SOURCE="HD2">Equivalent Level of Safety (ELOS) Findings</HD>
        <P>ACE-96-5 for 14 CFR Section 23.221 (Spinning); Refer to FAA Memorandum, dated June 10, 1998, for models SR20, SR22.</P>
        <P>ACE-00-09 for 14 CFR 23.1143(g) (Engine Controls) and 23.1147(b) (Mixture Controls); Refer to FAA Memorandum, dated September 11, 2000, for model SR22.</P>
        <P>ACE-01-01 for 14 CFR 23.1143(g) (Engine Controls) and 23.1147(b) (Mixture Controls); Refer to FAA Memorandum, dated February 14, 2001, for model SR20.</P>
        <HD SOURCE="HD2">Special Conditions</HD>
        <P>23-ACE-88 for ballistic parachute, for models SR20, SR22.</P>
        <P>23-134-SC for protection of systems for High Intensity Radiated Fields continued: (HIRF), for models SR20, SR22.</P>
        <P>23-163-SC for inflatable restraint system. Addition to the certification basis model SR20 effective S/N 1541 and subsequent; model SR22 S/N 1500, 1520 and subsequent.</P>

        <P>If the Administrator finds that the applicable airworthiness regulations (<E T="03">i.e.,</E>14 CFR part 23) do not contain adequate or appropriate safety standards for the SR22 because of a novel or unusual design feature, special conditions are prescribed under the provisions of § 21.16.</P>
        <P>In addition to the applicable airworthiness regulations and special conditions, the SR22 must comply with the fuel vent and exhaust emission requirements of 14 CFR part 34 and the noise certification requirements of 14 CFR part 36.</P>
        <P>The FAA issues special conditions, as defined in 14 CFR 11.19, in accordance with § 11.38, and they become part of the type-certification basis under § 21.101.</P>
        <P>Special conditions are initially applicable to the model for which they are issued. Should the applicant apply for a supplemental type certificate to modify any other model included on the same type certificate to incorporate the same or similar novel or unusual design feature, the special conditions would also apply to the other model under § 21.101.</P>
        <HD SOURCE="HD1">Novel or Unusual Design Features</HD>
        <P>The SR22 will incorporate the following novel or unusual design features:</P>
        <P>Winglets with an Active Technology Load Alleviation System (ATLAS) that incorporates a small aileron-like device called a Tamarack Active Control Surface (TACS).</P>
        <HD SOURCE="HD1">Discussion</HD>
        <P>Tamarack has applied for a Supplemental Type Certificate to install a winglet and ATLAS. The ATLAS is not a primary flight control system, a trim device, or a wing flap. However, there is definite applicability to ATLAS for several regulations under part 23, Subpart D—Control Systems, which might otherwise be considered “Not Applicable” under a strict interpretation of the regulations. Other conditions may be developed, as needed, based on further FAA review and discussions with the manufacturer.</P>
        <P>Special conditions are also necessary for the effect of ATLAS on structural performance. These special conditions are intended to provide an equivalent level of safety for ATLAS as intended by part 23, Subpart C—Structure, and portions of part 23, Subpart D—Design and Construction.</P>
        <HD SOURCE="HD1">Applicability</HD>
        <P>As discussed above, these special conditions are applicable to the SR22 (S/Ns 0002 thru 2333, 2335 thru 2419, and 2421 thru 2437). Should Tamarack Aerospace Group apply at a later date for a supplemental type certificate to modify any other model included on Type Certificate Data Sheet A00009CH to incorporate the same novel or unusual design feature, the special conditions would apply to that model as well.</P>
        <HD SOURCE="HD1">Conclusion</HD>
        <P>This action affects only certain novel or unusual design features on one model of airplane. It is not a rule of general applicability and it affects only the applicant who applied to the FAA for approval of these features on the airplane.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 14 CFR Part 23</HD>
          <P>Aircraft, Aviation safety, Signs and symbols.</P>
        </LSTSUB>
        <HD SOURCE="HD1">Citation</HD>
        <P>The authority citation for these special conditions is as follows:</P>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>49 U.S.C. 106(g), 40113, 44701-44702, 44704.</P>
        </AUTH>
        <HD SOURCE="HD1">These Special Conditions</HD>
        <P>Accordingly, the Federal Aviation Administration (FAA) are issued the following special conditions as part of the type certification basis for Cirrus Model SR22 airplanes (S/Ns 0002 through 2333, 2335 through 2419, and 2421 through 2437) modified by Tamarack Aerospace Group.</P>
        <HD SOURCE="HD1">1. Active Load Alleviation Systems—Structural Requirements</HD>

        <P>(A) The following special conditions apply to airplanes equipped with load alleviation systems that either directly, or as a result of failure or malfunction, affect structural performance. These<PRTPAGE P="10057"/>special conditions address the direct structural consequences of the system responses and performances and cannot be considered in isolation but should be included in the overall safety evaluation of the airplane. Any statistical or probability terms used in the following special conditions apply to the structural requirements only and do not replace, remove, or supersede other requirements, including those in part 23, subpart E. These criteria are only applicable to structure whose failure could prevent continued safe flight and landing.</P>
        <P>(B) In addition to the requirements in 14 CFR 23.301 Loads, comply with the following:</P>
        <HD SOURCE="HD1">SC 23.301Loads, Probability of Failure of Load Alleviation System</HD>

        <P>(a) Failures of the load alleviation system, including the annunciation system, must be immediately annunciated to the pilot or annunciated prior to the next flight. Failure of the load alleviation system, including the annunciation system, must be no greater than 1 x 10<E T="51">−5</E>per flight hour.</P>

        <P>(b) If failure of the load alleviation system, including the annunciation system, is greater than 1 x 10<E T="51">−8</E>per flight hour, an independent system functional test must be accomplished at a periodic interval to limit time exposure to an undetected failed system. The time interval for the system functional test must be selected so that the product of the time interval in hours and the failure of the load alleviation system, including the annunciation system, is no greater than 1 x 10<E T="51">−5</E>per hour.</P>
        <P>(c) Tamarack must report failed annunciation systems to the FAA in a manner acceptable to the Administrator.</P>
        <P>(C) In place of the requirements in 14 CFR 23.303 Factor of Safety, comply with the following:</P>
        <HD SOURCE="HD1">SC 23.303Factor of Safety, Load Alleviation Systems</HD>
        <P>The airplane must be able to withstand the limit and ultimate loads resulting from the following scenarios:</P>
        <P>(a) The loads resulting from 14 CFR 23.321 through 23.537, as applicable, corresponding to a fully operative load alleviation system. A factor of safety of 1.5 must be applied to determine ultimate loads.</P>
        <P>(b) If an independent system functional test is required by SC 23.301(b), the loads resulting from 14 CFR 23.321 through 23.537, as applicable, corresponding to the system in the inoperative state without additional flight limitations or reconfiguration of the airplane. A factor of safety of 1.0 must be applied to determine ultimate loads.</P>

        <P>(c) The loads corresponding to the time of occurrence of load alleviation system failure and immediately after the failure. These loads must be determined at any speed up to V<E T="52">NE</E>, starting from 1g level flight conditions, and considering realistic scenarios, including pilot corrective actions. A factor of safety of 1.5 must be applied to determine ultimate loads.</P>
        <P>(d) For airplanes equipped with “before the next flight” failure annunciation systems, the loads resulting from 14 CFR 23.321 through 23.537, as applicable, corresponding to the system in the failed state without additional flight limitations or reconfiguration of the airplane. A factor of safety of 1.25 must be applied to determine ultimate loads.</P>
        <P>(e) For airplanes equipped with “immediate” failure annunciation systems, the loads resulting from 14 CFR 23.321 through 23.537, as applicable, corresponding to the system in the failed state with additional flight limitations or reconfiguration of the airplane. A factor of safety of 1.0 must be applied to determine ultimate loads.</P>
        <P>(D) In addition to the requirements in 14 CFR 23.571 through 23.574, comply with the following:</P>
        <HD SOURCE="HD1">SC 23.571 Through SC 23.574Fatigue and Damage Tolerance</HD>
        <P>If any system failure would have a significant effect on the fatigue or damage evaluations required in §§ 23.571 through 23.574, then these effects must be taken into account. If an independent system functional test is required by SC 23.301(b), the effect on fatigue and damage evaluations resulting from the selected inspection interval must be taken into account.</P>
        <P>(E) In addition to the requirements in 14 CFR 23.629 Flutter, comply with the following:</P>
        <HD SOURCE="HD1">SC 23.629Flutter</HD>
        <P>(a) With the load alleviation system fully operative, compliance to 14 CFR 23.629 must be shown. Compliance with § 23.629(f) must include the ATLAS control system and control surface.</P>

        <P>(b) At the time of occurrence of load alleviation system failure and immediately after the failure, compliance with 14 CFR 23.629(a) and (e) must be shown up to V<E T="52">D</E>/M<E T="52">D</E>without consideration of additional operating limitations or reconfiguration of the airplane.</P>

        <P>(c) For airplanes equipped with “before the next flight” failure annunciation systems and the load alleviation system in the failed state, compliance to 14 CFR 23.629 Flutter, paragraphs (a) and (e), must be shown up to V<E T="52">D</E>/M<E T="52">D</E>without consideration of additional operating limitations or reconfiguration of the airplane.</P>

        <P>(d) For airplanes equipped with “immediate” failure annunciation systems and the load alleviation system in the failed state, compliance to 14 CFR 23.629 Flutter, paragraphs (a) and (e), must be shown with consideration of additional operating limitations or reconfiguration of the airplane at speeds up to V<E T="52">D</E>= 1.4 x maximum speed limitation selected by the applicant.</P>
        <HD SOURCE="HD1">2. Active Load Alleviation Systems—Control System Requirements</HD>
        <P>(A) In place of 14 CFR 23.672 Stability augmentation and automatic and power-operated systems requirement, comply with the following:</P>
        <HD SOURCE="HD1">SC 23.672Load Alleviation Systems</HD>
        <P>The load alleviation system must comply with the following:</P>
        <P>(a) A warning, which is clearly distinguishable to the pilot under expected flight conditions without requiring the pilot's attention, must be provided for any failure in the load alleviation system or in any other automatic system that could result in an unsafe condition if the pilot was not aware of the failure. Warning systems must not activate the control system.</P>
        <P>(b) The design of the load alleviation system or of any other automatic system must permit initial counteraction of failures without requiring exceptional pilot skill or strength, by either the deactivation of the system or a failed portion thereof, or by overriding the failure by movement of the flight controls in the normal sense.</P>
        <P>(c) It must be shown that, while the system is active or after any single failure of the load alleviation system—</P>
        <P>(1) The airplane is safely controllable when the failure or malfunction occurs at any speed or altitude within the approved operating limitations that is critical for the type of failure being considered;</P>
        <P>(2) The controllability and maneuverability requirements of this part are met within a practical operational flight envelope (for example, speed, altitude, normal acceleration, and airplane configuration) that is described in the Airplane Flight Manual (AFM); and</P>

        <P>(3) The trim, stability, and stall characteristics are not impaired below a level needed to permit continued safe flight and landing.<PRTPAGE P="10058"/>
        </P>
        <P>(B) In place of 14 CFR 23.677 Trim systems requirement, comply with the following:</P>
        <HD SOURCE="HD1">SC 23.677Load Alleviation Active Control Surface</HD>
        <P>(a) Proper precautions must be taken to prevent inadvertent, improper, or abrupt Tamarack Active Control Surface (TACS) operation.</P>
        <P>(b) The load alleviation system must be designed so that, when any one connecting or transmitting element in the primary flight control system fails, adequate longitudinal control for safe flight and landing is available.</P>
        <P>(c) The load alleviation system must be irreversible unless the TACS is properly balanced and has no unsafe flutter characteristics. The system must have adequate rigidity and reliability in the portion of the system from the tab to the attachment of the irreversible unit to the airplane structure.</P>
        <P>(d) It must be demonstrated that the airplane is safely controllable and that the pilot can perform all maneuvers and operations necessary to effect a safe landing following any probable powered system runaway that reasonably might be expected in service, allowing for appropriate time delay after pilot recognition of the system runaway. The demonstration must be conducted at critical airplane weights and center of gravity positions.</P>
        <P>(C) In place of 14 CFR 23.683 Operation tests requirement, comply with the following:</P>
        <HD SOURCE="HD1">SC 23.683Operation Tests</HD>
        <P>(a) It must be shown by operation tests that, when the load alleviation system is active and operational and loaded as prescribed in paragraph (b) of this section, the system is free from—</P>
        <P>(1) Jamming;</P>
        <P>(2) Excessive friction; and</P>
        <P>(3) Excessive deflection.</P>
        <P>(b) The prescribed test loads are, for the entire system, loads corresponding to the limit airloads on the appropriate surface.</P>
        <P>(D) In place of 14 CFR 23.685 Control system details requirement, comply with the following:</P>
        <HD SOURCE="HD1">SC 23.685Control system details</HD>
        <P>(a) Each detail of the Tamarack Active Control Surface (TACS) must be designed and installed to prevent jamming, chafing, and interference from cargo, passengers, loose objects, or the freezing of moisture.</P>
        <P>(b) There must be means in the cockpit to prevent the entry of foreign objects into places where they would jam any one connecting or transmitting element of the system.</P>
        <P>(c) Each element of the load alleviation system must have design features, or must be distinctively and permanently marked, to minimize the possibility of incorrect assembly that could result in malfunctioning of the control system.</P>
        <P>(E) In place of 14 CFR 23.697 Wing flap controls requirement, comply with the following:</P>
        <HD SOURCE="HD1">SC 23.697Load Alleviation System Controls</HD>
        <P>(a) The Tamarack Active Control Surface (TACS) must be designed so that, when the surface has been placed in any position, it will not move from that position unless the control is adjusted or is moved by the automatic operation of a load alleviation system.</P>
        <P>(b) The rate of movement of the TACS in response to the automatic device must give satisfactory flight and performance characteristics under steady or changing conditions of airspeed, engine power, and attitude.</P>
        <P>(F) In place of 14 CFR 23.701 Flap interconnection requirement, comply with the following:</P>
        <HD SOURCE="HD1">SC 23.701Load Alleviation System Interconnection</HD>
        <P>(a) The load alleviation system and related movable surfaces as a system must—</P>
        <P>(1) Be synchronized by a mechanical interconnection between the movable surfaces; or by an approved equivalent means; or</P>
        <P>(2) Be designed so that the occurrence of any failure of the system that would result in an unsafe flight characteristic of the airplane is extremely improbable; or</P>
        <P>(b) The airplane must be shown to have safe flight characteristics with any combination of extreme positions of individual movable surfaces.</P>
        <SIG>
          <DATED>Issued in Kansas City, Missouri, on February 6, 2013.</DATED>
          <NAME>John Colomy,</NAME>
          <TITLE>Acting Manager, Small Airplane Directorate, Aircraft Certification Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03296 Filed 2-12-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 97</CFR>
        <DEPDOC>[Docket No. 30884; Amdt. No. 3519]</DEPDOC>
        <SUBJECT>Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures; Miscellaneous Amendments</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Aviation Administration (FAA), DOT.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This rule establishes, amends, suspends, or revokes Standard Instrument Approach Procedures (SIAPs) and associated Takeoff Minimums and Obstacle Departure Procedures for operations at certain airports. These regulatory actions are needed because of the adoption of new or revised criteria, or because of changes occurring in the National Airspace System, such as the commissioning of new navigational facilities, adding new obstacles, or changing air traffic requirements. These changes are designed to provide safe and efficient use of the navigable airspace and to promote safe flight operations under instrument flight rules at the affected airports.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective February 13, 2013. The compliance date for each SIAP, associated Takeoff Minimums, and ODP is specified in the amendatory provisions.</P>
          <P>The incorporation by reference of certain publications listed in the regulations is approved by the Director of the Federal Register as of February 13, 2013.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Availability of matters incorporated by reference in the amendment is as follows:</P>
          <P>
            <E T="03">For Examination—</E>
          </P>
          <P>1. FAA Rules Docket, FAA Headquarters Building, 800 Independence Avenue SW., Washington, DC 20591;</P>
          <P>2. The FAA Regional Office of the region in which the affected airport is located;</P>
          <P>3. The National Flight Procedures Office, 6500 South MacArthur Blvd., Oklahoma City, OK 73169, or</P>

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

        <P>The large number of SIAPs, Takeoff Minimums and ODPs, in addition to their complex nature and the need for a special format make publication in the<E T="04">Federal Register</E>expensive and impractical. Furthermore, airmen do not use the regulatory text of the SIAPs, Takeoff Minimums or ODPs, but instead refer to their depiction on charts printed by publishers of aeronautical materials. The advantages of incorporation by reference are realized and publication of the complete description of each SIAP, Takeoff Minimums and ODP listed on FAA forms is unnecessary. This amendment provides the affected CFR sections and specifies the types of SIAPs and the effective dates of the, associated Takeoff Minimums and ODPs. This amendment also identifies the airport and its location, the procedure, and the amendment number.</P>
        <HD SOURCE="HD1">The Rule</HD>
        <P>This amendment to 14 CFR part 97 is effective upon publication of each separate SIAP, Takeoff Minimums and ODP as contained in the transmittal. Some SIAP and Takeoff Minimums and textual ODP amendments may have been issued previously by the FAA in a Flight Data Center (FDC) Notice to Airmen (NOTAM) as an emergency action of immediate flight safety relating directly to published aeronautical charts. The circumstances which created the need for some SIAP and Takeoff Minimums and ODP amendments may require making them effective in less than 30 days. For the remaining SIAPS and Takeoff Minimums and ODPS, an effective date at least 30 days after publication is provided.</P>
        <P>Further, the SIAPs and Takeoff Minimums and ODPS contained in this amendment are based on the criteria contained in the U.S. Standard for Terminal Instrument Procedures (TERPS). In developing these SIAPS and Takeoff Minimums and ODPs, the TERPS criteria were applied to the conditions existing or anticipated at the affected airports. Because of the close and immediate relationship between these SIAPs, Takeoff Minimums and ODPs, and safety in air commerce, I find that notice and public procedures before adopting these SIAPS, Takeoff Minimums and ODPs are impracticable and contrary to the public interest and, where applicable, that good cause exists for making some SIAPs effective in less than 30 days.</P>
        <HD SOURCE="HD1">Conclusion</HD>
        <P>The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore—(1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034; February 26,1979) ; and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. For the same reason, the FAA certifies that this amendment will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 14 CFR part 97</HD>
          <P>Air Traffic Control, Airports, Incorporation by reference, and Navigation (Air).</P>
        </LSTSUB>
        <SIG>
          <DATED>Issued in Washington, DC on February 1, 2013.</DATED>
          <NAME>John M. Allen,</NAME>
          <TITLE>Director, Flight Standards Service.</TITLE>
        </SIG>
        <HD SOURCE="HD1">Adoption of the Amendment</HD>
        <P>Accordingly, pursuant to the authority delegated to me, Title 14, Code of Federal Regulations, Part 97 (14 CFR part 97) is amended by establishing, amending, suspending, or revoking Standard Instrument Approach Procedures and/or Takeoff Minimums and/or Obstacle Departure Procedures effective at 0902 UTC on the dates specified, as follows:</P>
        <REGTEXT PART="97" TITLE="14">
          <PART>
            <HD SOURCE="HED">PART 97—STANDARD INSTRUMENT APPROACH PROCEDURES</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 97 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 106(g), 40103, 40106, 40113, 40114, 40120, 44502, 44514, 44701, 44719, 44721-44722.</P>
          </AUTH>
          <AMDPAR>2. Part 97 is amended to read as follows:</AMDPAR>
          
          <EXTRACT>
            <HD SOURCE="HD2">Effective 7 MARCH 2013</HD>
            <FP SOURCE="FP-1">Tatitlek, AK, Tatitlek, RNAV (GPS) RWY 31, Orig-A</FP>
            <FP SOURCE="FP-1">Jonesboro, AR, Jonesboro Muni, RNAV (GPS) RWY 5, Amdt 1</FP>
            <FP SOURCE="FP-1">Jonesboro, AR, Jonesboro Muni, RNAV (GPS) RWY 23, Amdt 1</FP>
            <FP SOURCE="FP-1">Jonesboro, AR, Jonesboro Muni, RNAV (GPS) RWY 31, Amdt 1</FP>
            <FP SOURCE="FP-1">Jonesboro, AR, Jonesboro Muni, Takeoff Minimums and Obstacle DP, Amdt 3</FP>
            <FP SOURCE="FP-1">Washington, DC, Manassas Rgnl/Harry P. Davis Field, ILS OR LOC RWY 16L, Amdt 5</FP>
            <FP SOURCE="FP-1">Washington, DC, Ronald Reagan Washington National, RNAV (RNP) RWY 19, Amdt 1</FP>
            <FP SOURCE="FP-1">Jacksonville, FL, Jacksonville Executive at Craig Airport, ILS OR LOC RWY 32, Amdt 5</FP>
            <FP SOURCE="FP-1">Jacksonville, FL, Jacksonville Executive at Craig Airport, RNAV (GPS) RWY 14, Amdt 1</FP>
            <FP SOURCE="FP-1">Jacksonville, FL, Jacksonville Executive at Craig Airport, RNAV (GPS) RWY 32, Amdt 1</FP>
            <FP SOURCE="FP-1">Jacksonville, FL, Jacksonville Executive at Craig Airport, Takeoff Minimums and Obstacle DP, Amdt 4</FP>
            <FP SOURCE="FP-1">Jacksonville, FL, Jacksonville Executive at Craig Airport, VOR RWY 14, Amdt 5</FP>
            <FP SOURCE="FP-1">Jacksonville, FL, Jacksonville Executive at Craig Airport, VOR/DME RWY 32, Amdt 3</FP>
            <FP SOURCE="FP-1">Tallahassee, FL, Tallahassee Rgnl, ILS OR LOC/DME RWY 36, Amdt 25</FP>
            <FP SOURCE="FP-1">Tallahassee, FL, Tallahassee Rgnl, NDB RWY 36, Amdt 20B, CANCELED</FP>
            <FP SOURCE="FP-1">Tallahassee, FL, Tallahassee Rgnl, VOR RWY 18, Amdt 12</FP>
            <FP SOURCE="FP-1">Tallahassee, FL, Tallahassee Rgnl, VOR/DME OR TACAN RWY 36, Amdt 1</FP>
            <FP SOURCE="FP-1">Atlanta, GA, Fulton County Airport-Brown Field, RNAV (GPS) RWY 26, Amdt 1A</FP>
            <FP SOURCE="FP-1">Lawrenceville, GA, Gwinnett County—Briscoe Field, ILS OR LOC RWY 25, Amdt 2A</FP>
            <FP SOURCE="FP-1">Lawrenceville, GA, Gwinnett County—Briscoe Field, NDB RWY 25, Amdt 1A</FP>
            <FP SOURCE="FP-1">Lawrenceville, GA, Gwinnett County—Briscoe Field, RNAV (GPS) RWY 7, Orig-A</FP>
            <FP SOURCE="FP-1">Lawrenceville, GA, Gwinnett County—Briscoe Field, RNAV (GPS) RWY 25, Orig-A</FP>

            <FP SOURCE="FP-1">Lawrenceville, GA, Gwinnett County—Briscoe Field, RNAV (GPS)-A, Orig-A<PRTPAGE P="10060"/>
            </FP>
            <FP SOURCE="FP-1">Lawrenceville, GA, Gwinnett County—Briscoe Field, VOR/DME RWY 7, Amdt 2A</FP>
            <FP SOURCE="FP-1">Iowa Falls, IA, Iowa Falls Muni, NDB RWY 31, Amdt 5, CANCELED</FP>
            <FP SOURCE="FP-1">Iowa Falls, IA, Iowa Falls Muni, RNAV (GPS) RWY 13, Orig</FP>
            <FP SOURCE="FP-1">Iowa Falls, IA, Iowa Falls Muni, RNAV (GPS) RWY 31, Amdt 1</FP>
            <FP SOURCE="FP-1">Pinckneyville, IL, Pinckneyville-Du Quoin, RNAV (GPS) RWY 18, Amdt 1</FP>
            <FP SOURCE="FP-1">Boston, MA, General Edward Lawrence Logan Intl, ILS OR LOC RWY 33L, ILS RWY 33L (SA CAT I), ILS RWY 33L (CAT II), ILS RWY 33L (CAT III), Amdt 5</FP>
            <FP SOURCE="FP-1">Boston, MA, General Edward Lawrence Logan Intl, RNAV (GPS) RWY 33L, Amdt 2</FP>
            <FP SOURCE="FP-1">Montague, MA, Turners Falls, RNAV (GPS)-B, Orig</FP>
            <FP SOURCE="FP-1">Montague, MA, Turners Falls, VOR-A, Amdt 4</FP>
            <FP SOURCE="FP-1">Marquette, MI, Sawyer Intl, RNAV (GPS) RWY 1, Orig</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, ILS OR LOC RWY 1L, Amdt 15</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, ILS OR LOC RWY 1R, ILS RWY 1R (SA CAT I), ILS RWY 1R (CAT II), ILS RWY 1R (CAT III), Amdt 4</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, ILS OR LOC RWY 9, Amdt 14</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, ILS OR LOC RWY 19L, Amdt 2</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, ILS OR LOC RWY 19R, ILS RWY 19R (SA CAT I), ILS RWY 19R (CAT II), ILS RWY 19R (CAT III), Amdt 11</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, ILS OR LOC RWY 27, Amdt 3</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, RNAV (GPS) Y RWY 1L, Amdt 2</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, RNAV (GPS) Y RWY 1R, Amdt 2</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, RNAV (GPS) Y RWY 9, Amdt 2</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, RNAV (GPS) Y RWY 19L, Amdt 2</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, RNAV (GPS) Y RWY 19R, Amdt 2</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, RNAV (GPS) Y RWY 27, Amdt 2</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, RNAV (RNP) Z RWY 1L, Amdt 1</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, RNAV (RNP) Z RWY 1R, Amdt 1</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, RNAV (RNP) Z RWY 9, Amdt 1</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, RNAV (RNP) Z RWY 19L, Amdt 1</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, RNAV (RNP) Z RWY 19R, Amdt 1</FP>
            <FP SOURCE="FP-1">Kansas City, MO, Kansas City Intl, RNAV (RNP) Z RWY 27, Amdt 1</FP>
            <FP SOURCE="FP-1">Raymond, MS, John Bell Williams, ILS OR LOC RWY 12, Orig-A</FP>
            <FP SOURCE="FP-1">Gallipolis, OH, Gallia-Meigs Rgnl, GPS RWY 23, Orig, CANCELED</FP>
            <FP SOURCE="FP-1">Gallipolis, OH, Gallia-Meigs Rgnl, RNAV (GPS) RWY 23, Orig</FP>
            <FP SOURCE="FP-1">Erie, PA, Erie Intl/Tom Ridge Field, NDB RWY 6, Amdt 2</FP>
            <FP SOURCE="FP-1">Erie, PA, Erie Intl/Tom Ridge Field, NDB RWY 24, Amdt 19</FP>
            <FP SOURCE="FP-1">Erie, PA, Erie Intl/Tom Ridge Field, VOR RWY 6, Amdt 16, CANCELED</FP>
            <FP SOURCE="FP-1">Erie, PA, Erie Intl/Tom Ridge Field, VOR/DME RWY 24, Amdt 12, CANCELED</FP>
            <FP SOURCE="FP-1">Washington, PA, Washington County, RNAV (GPS) RWY 9, Amdt 1A</FP>
            <FP SOURCE="FP-1">Ponce, PR, Mercedita, Takeoff Minimums and Obstacle DP, Amdt 3</FP>
            <FP SOURCE="FP-1">San Juan, PR, Luis Munoz Marin Intl, ILS OR LOC RWY 10, Amdt 6</FP>
            <FP SOURCE="FP-1">San Juan, PR, Luis Munoz Marin Intl, RNAV (GPS) RWY 10, Amdt 2</FP>
            <FP SOURCE="FP-1">San Juan, PR, Luis Munoz Marin Intl, VOR OR TACAN RWY 10, Amdt 2</FP>
            <FP SOURCE="FP-1">Union City, TN, Everett-Stewart Rgnl, ILS OR LOC RWY 1, Amdt 2</FP>
            <FP SOURCE="FP-1">Union City, TN, Everett-Stewart Rgnl, RNAV (GPS) RWY 1, Amdt 3</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, ILS OR LOC RWY 16C, ILS RWY 16C (SA CAT I), ILS RWY 16C (CAT II), ILS RWY 16C (CAT III), Amdt 14</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, ILS OR LOC RWY 16L, ILS RWY 16L (SA CAT I), ILS RWY 16L (CAT II), ILS RWY 16L (CAT III), Amdt 5</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, ILS OR LOC RWY 16R, ILS RWY 16R (SA CAT I), ILS RWY 16R (CAT II), ILS RWY 16R (CAT III), Amdt 2</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, ILS OR LOC RWY 34C, ILS RWY 34C (SA CAT I), ILS RWY 34C (SA CAT II), Amdt 3</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, ILS OR LOC RWY 34L, ILS RWY 34L (SA CAT I), ILS RWY 34L (SA CAT II), Amdt 1</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, ILS OR LOC RWY 34R, ILS RWY 34R (SA CAT I), ILS RWY 34R (SA CAT II), Amdt 2</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, RNAV (GPS) Y RWY 16C, Amdt 2</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, RNAV (GPS) Y RWY 16L, Amdt 3</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, RNAV (GPS) Y RWY 16R, Amdt 1</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, RNAV (GPS) Y RWY 34C, Amdt 2</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, RNAV (GPS) Y RWY 34L, Amdt 1</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, RNAV (GPS) Y RWY 34R, Amdt 2</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, RNAV (RNP) Z RWY 16C, Orig</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, RNAV (RNP) Z RWY 16L, Orig</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, RNAV (RNP) Z RWY 16R, Orig</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, RNAV (RNP) Z RWY 34C, Orig</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, RNAV (RNP) Z RWY 34L, Orig</FP>
            <FP SOURCE="FP-1">Seattle, WA, Seattle-Tacoma Intl, RNAV (RNP) Z RWY 34R, Orig</FP>
            <HD SOURCE="HD2">Effective 4 APRIL 2013</HD>
            <FP SOURCE="FP-1">Connersville, IN, Mettel Field, RNAV (GPS) RWY 18, Amdt 1A</FP>
            <FP SOURCE="FP-1">Georgetown, TX, Georgetown Muni, NDB RWY 18, Amdt 5, CANCELED</FP>
            <NOTE>
              <HD SOURCE="HED">Rescinded:</HD>
              <P>On January 25, 2013 (78 FR 5256), the FAA published an Amendment in Docket No. 30880, Amdt No. 3515 to Part 97 of the Federal Aviation Regulations under section 97.33. The following 4 entries for Lakeview, CA, effective 7 March, 2013, are hereby rescinded in their entirety:</P>
            </NOTE>
            <FP SOURCE="FP-1">Lakeview, OR, Lake County, GPS RWY 34, Orig-A, CANCELED</FP>
            <FP SOURCE="FP-1">Lakeview, OR, Lake County, RNAV (GPS) RWY 17, Orig</FP>
            <FP SOURCE="FP-1">Lakeview, OR, Lake County, RNAV (GPS) RWY 35, Orig</FP>
            <FP SOURCE="FP-1">Lakeview, OR, Lake County, Takeoff Minimums and Obstacle DP, Amdt 3</FP>
          </EXTRACT>
        </REGTEXT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03147 Filed 2-12-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 97</CFR>
        <DEPDOC>[Docket No. 30885; Amdt. No. 3520]</DEPDOC>
        <SUBJECT>Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures; Miscellaneous Amendments</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Aviation Administration (FAA), DOT.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This rule establishes, amends, suspends, or revokes Standard Instrument Approach Procedures (SIAPs) and associated Takeoff Minimums and Obstacle Departure Procedures for operations at certain airports. These regulatory actions are needed because of the adoption of new or revised criteria, or because of changes occurring in the National Airspace System, such as the commissioning of new navigational facilities, adding new obstacles, or changing air traffic requirements. These changes are designed to provide safe and efficient use of the navigable airspace and to promote safe flight operations under instrument flight rules at the affected airports.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective February 13, 2013. The compliance date for each SIAP, associated Takeoff Minimums, and ODP is specified in the amendatory provisions.</P>
          <P>The incorporation by reference of certain publications listed in the regulations is approved by the Director of the Federal Register as of February 13, 2013.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Availability of matter incorporated by reference in the amendment is as follows:</P>
          <P>
            <E T="03">For Examination</E>—</P>
          <P>1. FAA Rules Docket, FAA Headquarters Building, 800 Independence Avenue SW., Washington, DC 20591;</P>
          <P>2. The FAA Regional Office of the region in which the affected airport is located;</P>
          <P>3. The National Flight Procedures Office, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 or,</P>

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

        <P>The large number of SIAPs, their complex nature, and the need for a special format make their verbatim publication in the<E T="04">Federal Register</E>expensive and impractical. Further, airmen do not use the regulatory text of the SIAPs, but refer to their graphic depiction on charts printed by publishers of aeronautical materials. Thus, the advantages of incorporation by reference are realized and publication of the complete description of each SIAP contained in FAA form documents is unnecessary. This amendment provides the affected CFR sections and specifies the types of SIAP and the corresponding effective dates. This amendment also identifies the airport and its location, the procedure and the amendment number.</P>
        <HD SOURCE="HD1">The Rule</HD>
        <P>This amendment to 14 CFR part 97 is effective upon publication of each separate SIAP as amended in the transmittal. For safety and timeliness of change considerations, this amendment incorporates only specific changes contained for each SIAP as modified by FDC/P-NOTAMs.</P>
        <P>The SIAPs, as modified by FDC P-NOTAM, and contained in this amendment are based on the criteria contained in the U.S. Standard for Terminal Instrument Procedures (TERPS). In developing these changes to SIAPs, the TERPS criteria were applied only to specific conditions existing at the affected airports. All SIAP amendments in this rule have been previously issued by the FAA in a FDC NOTAM as an emergency action of immediate flight safety relating directly to published aeronautical charts. The circumstances which created the need for all these SIAP amendments requires making them effective in less than 30 days.</P>
        <P>Because of the close and immediate relationship between these SIAPs and safety in air commerce, I find that notice and public procedure before adopting these SIAPs are impracticable and contrary to the public interest and, where applicable, that good cause exists for making these SIAPs effective in less than 30 days.</P>
        <HD SOURCE="HD1">Conclusion</HD>
        <P>The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore—(1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. For the same reason, the FAA certifies that this amendment will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 14 CFR Part 97</HD>
          <P>Air Traffic Control, Airports, Incorporation by reference, and Navigation (Air).</P>
        </LSTSUB>
        <SIG>
          <DATED>Issued in Washington, DC on February 1, 2013.</DATED>
          <NAME>John M. Allen,</NAME>
          <TITLE>Director, Flight Standards Service.</TITLE>
        </SIG>
        <HD SOURCE="HD1">Adoption of the Amendment</HD>
        <P>Accordingly, pursuant to the authority delegated to me, Title 14, Code of Federal regulations, Part 97, 14 CFR part 97, is amended by amending Standard Instrument Approach Procedures, effective at 0901 UTC on the dates specified, as follows:</P>
        <REGTEXT PART="97" TITLE="14">
          <PART>
            <HD SOURCE="HED">PART 97—STANDARD INSTRUMENT APPROACH PROCEDURES</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 97 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 106(g), 40103, 40106, 40113, 40114, 40120, 44502, 44514, 44701, 44719, 44721-44722.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="97" TITLE="14">
          <AMDPAR>2. Part 97 is amended to read as follows:</AMDPAR>
          <P>§§ 97.23, 97.25, 97.27, 97.29, 97.31, 97.33 and 97.35 [Amended]</P>
          <P>By amending: § 97.23 VOR, VOR/DME, VOR or TACAN, and VOR/DME or TACAN; § 97.25 LOC, LOC/DME, LDA, LDA/DME, SDF, SDF/DME; § 97.27 NDB, NDB/DME; § 97.29 ILS, ILS/DME, MLS, MLS/DME, MLS/RNAV; § 97.31 RADAR SIAPs; § 97.33 RNAV SIAPs; and § 97.35 COPTER SIAPs, Identified as follows:</P>
          
          <EXTRACT>
            <HD SOURCE="HD2">* * * Effective Upon Publication</HD>
          </EXTRACT>
          
          <GPOTABLE CDEF="xs48,xs32,r50,r75,10,10,xls120" COLS="7" OPTS="L2,tp0,i1">
            <TTITLE/>
            <BOXHD>
              <CHED H="1">AIRAC Date</CHED>
              <CHED H="1">State</CHED>
              <CHED H="1">City</CHED>
              <CHED H="1">Airport</CHED>
              <CHED H="1">FDC No.</CHED>
              <CHED H="1">FDC Date</CHED>
              <CHED H="1">Subject</CHED>
            </BOXHD>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>TX</ENT>
              <ENT>Palacios</ENT>
              <ENT>Palacios Muni</ENT>
              <ENT>3/1794</ENT>
              <ENT>01/11/13</ENT>
              <ENT>This NOTAM, published in TL 13-05, is hereby rescinded in its entirety.</ENT>
            </ROW>
            <ROW>
              <ENT I="01"/>
              <ENT/>
              <ENT/>
              <ENT/>
              <ENT/>
              <ENT/>
              <ENT/>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>ID</ENT>
              <ENT>Pocatello</ENT>
              <ENT>Pocatello Rgnl</ENT>
              <ENT>2/2570</ENT>
              <ENT>01/16/13</ENT>
              <ENT>VOR Rwy 3, Amdt 17</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>ID</ENT>
              <ENT>Pocatello</ENT>
              <ENT>Pocatello Rgnl</ENT>
              <ENT>2/2572</ENT>
              <ENT>01/16/13</ENT>
              <ENT>RNAV (GPS) Rwy 3, Amdt 1A</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>CA</ENT>
              <ENT>Apple Valley</ENT>
              <ENT>Apple Valley</ENT>
              <ENT>2/4862</ENT>
              <ENT>01/23/13</ENT>
              <ENT>RNAV (GPS) Z Rwy 18, Orig</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>CA</ENT>
              <ENT>Apple Valley</ENT>
              <ENT>Apple Valley</ENT>
              <ENT>2/4868</ENT>
              <ENT>01/23/13</ENT>
              <ENT>RNAV (GPS) Y Rwy 18, Amdt 1</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>CA</ENT>
              <ENT>Mountain View</ENT>
              <ENT>Moffett Federal Afld</ENT>
              <ENT>2/6390</ENT>
              <ENT>01/16/13</ENT>
              <ENT>TACAN Rwy 32L, Orig</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>CA</ENT>
              <ENT>Mountain View</ENT>
              <ENT>Moffett Federal Afld</ENT>
              <ENT>2/6396</ENT>
              <ENT>01/16/13</ENT>
              <ENT>ILS or LOC/DME Rwy 32R, Orig</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>CA</ENT>
              <ENT>Mountain View</ENT>
              <ENT>Moffett Federal Afld</ENT>
              <ENT>2/6397</ENT>
              <ENT>01/16/13</ENT>
              <ENT>LOC/DME Rwy 14L, Orig</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>CA</ENT>
              <ENT>Mountain View</ENT>
              <ENT>Moffett Federal Afld</ENT>
              <ENT>2/6398</ENT>
              <ENT>01/16/13</ENT>
              <ENT>TACAN Rwy 32R, Orig</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>CA</ENT>
              <ENT>Willits</ENT>
              <ENT>Ells Field-Willits Muni</ENT>
              <ENT>3/1482</ENT>
              <ENT>01/18/13</ENT>
              <ENT>RNAV (GPS) Rwy 34, Amdt 1</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10062"/>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>CA</ENT>
              <ENT>Willits</ENT>
              <ENT>Ells Field-Willits Muni</ENT>
              <ENT>3/1491</ENT>
              <ENT>01/18/13</ENT>
              <ENT>RNAV (GPS) Rwy 16, Amdt 1</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>CA</ENT>
              <ENT>Van Nuys</ENT>
              <ENT>Van Nuys</ENT>
              <ENT>3/1631</ENT>
              <ENT>01/18/13</ENT>
              <ENT>VOR A, Amdt 4</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>CA</ENT>
              <ENT>Van Nuys</ENT>
              <ENT>Van Nuys</ENT>
              <ENT>3/1632</ENT>
              <ENT>01/18/13</ENT>
              <ENT>VOR/DME or GPS B, Amdt 2A</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>CA</ENT>
              <ENT>Van Nuys</ENT>
              <ENT>Van Nuys</ENT>
              <ENT>3/1633</ENT>
              <ENT>01/18/13</ENT>
              <ENT>LDA C, Amdt 2B</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>CA</ENT>
              <ENT>Van Nuys</ENT>
              <ENT>Van Nuys</ENT>
              <ENT>3/1634</ENT>
              <ENT>01/18/13</ENT>
              <ENT>ILS Rwy 16R, Amdt 5F</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>PA</ENT>
              <ENT>Chambersburg</ENT>
              <ENT>Franklin County Rgnl</ENT>
              <ENT>3/2081</ENT>
              <ENT>01/24/13</ENT>
              <ENT>RNAV (GPS) Rwy 6, Orig</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>PA</ENT>
              <ENT>Chambersburg</ENT>
              <ENT>Franklin County Rgnl</ENT>
              <ENT>3/2082</ENT>
              <ENT>01/24/13</ENT>
              <ENT>RNAV (GPS) Rwy 24, Orig</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>PA</ENT>
              <ENT>Chambersburg</ENT>
              <ENT>Franklin County Rgnl</ENT>
              <ENT>3/2083</ENT>
              <ENT>01/24/13</ENT>
              <ENT>VOR/DME B, Amdt 2</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>LA</ENT>
              <ENT>Jonesboro</ENT>
              <ENT>Jonesboro</ENT>
              <ENT>3/2484</ENT>
              <ENT>01/18/13</ENT>
              <ENT>RNAV (GPS) Rwy 18, Orig</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>LA</ENT>
              <ENT>Jonesboro</ENT>
              <ENT>Jonesboro</ENT>
              <ENT>3/2485</ENT>
              <ENT>01/18/13</ENT>
              <ENT>RNAV (GPS) Rwy 36, Orig</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>ME</ENT>
              <ENT>Bar Harbor</ENT>
              <ENT>Hancock County-Bar Harbor</ENT>
              <ENT>3/2504</ENT>
              <ENT>01/16/13</ENT>
              <ENT>Takeoff Minimums and (Obstacle) DP, Amdt 4</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>NM</ENT>
              <ENT>Zuni Pueblo</ENT>
              <ENT>Black Rock</ENT>
              <ENT>3/2558</ENT>
              <ENT>01/16/13</ENT>
              <ENT>VOR/DME Rwy 6, Amdt 2A</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>MN</ENT>
              <ENT>Long Prairie</ENT>
              <ENT>Todd Field</ENT>
              <ENT>3/2560</ENT>
              <ENT>01/16/13</ENT>
              <ENT>RNAV (GPS) Rwy 34, Amdt 1</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>ID</ENT>
              <ENT>Lewiston</ENT>
              <ENT>Lewiston-Nez Perce County</ENT>
              <ENT>3/2608</ENT>
              <ENT>01/18/13</ENT>
              <ENT>ILS Rwy 26, Amdt 13</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>PA</ENT>
              <ENT>Bedford</ENT>
              <ENT>Bedford County</ENT>
              <ENT>3/2756</ENT>
              <ENT>01/16/13</ENT>
              <ENT>VOR A, Amdt 1</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7-Mar-13</ENT>
              <ENT>PA</ENT>
              <ENT>Bedford</ENT>
              <ENT>Bedford County</ENT>
              <ENT>3/2757</ENT>
              <ENT>01/16/13</ENT>
              <ENT>RNAV (GPS) Rwy 14, Amdt 1</ENT>
            </ROW>
          </GPOTABLE>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03146 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-13-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-2013-0022]</DEPDOC>
        <RIN>RIN 1625-AA00</RIN>
        <SUBJECT>Safety Zone; Sea World San Diego Fireworks, Mission Bay; San Diego, CA</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Coast Guard, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Temporary final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Coast Guard is establishing a safety zone on the navigable waters of Mission Bay in support of the Sea World San Diego Fireworks. This safety zone is necessary to provide for the safety of the participants, crew, spectators, participating vessels, and other vessels and users of the waterway. Persons and vessels are prohibited from entering into, transiting through, or anchoring within this safety zone unless authorized by the Captain of the Port, or his designated representative.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective from 8:50 p.m. to 10 p.m. on February 16, 2013.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Documents mentioned in this preamble are part of docket [USCG-2013-0022]. To view documents mentioned in this preamble as being available in the docket, go to<E T="03">http://www.regulations.gov,</E>type the docket number in the “SEARCH” box and click “SEARCH.” Click on Open Docket Folder on the line associated with this rulemaking. You may also visit the Docket Management Facility in Room W12-140 on the ground floor of the Department of Transportation West Building, 1200 New Jersey Avenue SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>If you have questions on this rule, call or email Petty Officer Deborah Metzger, Waterways Management, U.S. Coast Guard Sector San Diego, Coast Guard; telephone 619-278-7656, email<E T="03">d11-pf-marineeventssandiego@uscg.mil</E>. If you have questions on viewing or submitting material to the docket, call Renee V. Wright, Program Manager, Docket Operations, telephone (202) 366-9826.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Table of Acronyms</HD>
        <EXTRACT>
          <FP SOURCE="FP-1">DHSDepartment of Homeland Security</FP>
          <FP SOURCE="FP-1">FR<E T="04">Federal Register</E>
          </FP>
          <FP SOURCE="FP-1">NPRMNotice of Proposed Rulemaking</FP>
        </EXTRACT>
        <HD SOURCE="HD1">A. Regulatory History and Information</HD>
        <P>The Coast Guard is issuing this final rule without prior notice and opportunity to comment pursuant to authority under section 4(a) of the Administrative Procedure Act (APA) (5 U.S.C. 553(b)). This provision authorizes an agency to issue a rule without prior notice and opportunity to comment when the agency for good cause finds that those procedures are “impracticable, unnecessary, or contrary to the public interest.” Under 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule because delay would be impracticable. Immediate action is necessary to ensure the safety of vessels, spectators, participants, and others in the vicinity of the marine event on the dates and times this rule will be in effect.</P>

        <P>Under 5 U.S.C. 553(d)(3), the Coast Guard finds that good cause exists for making this rule effective less than 30 days after publication in the<E T="04">Federal Register</E>. Delaying the effective date would be impracticable, since immediate action is needed to ensure the public's safety.</P>
        <HD SOURCE="HD1">B. Basis and Purpose</HD>
        <P>The legal basis for this temporary rule is the Ports and Waterways Safety Act which authorizes the Coast Guard to establish safety zones (33 U.S.C sections 1221 et seq.).</P>
        <P>Sea World is sponsoring the Sea World Fireworks, which will include a fireworks presentation from a barge in Mission Bay. The fireworks display is scheduled to occur between 8:50 p.m. and 10 p.m. on February 16, 2013. This fireworks display could cause a hazard for crew, spectators, participants, and other vessels and users of the waterway.</P>
        <HD SOURCE="HD1">C. Discussion of the Final Rule</HD>
        <P>The Coast Guard is establishing a safety zone that will be enforced from 8:50 p.m. to 10 p.m. on February 16, 2013. The safety zone will cover a 600 foot radius surrounding the fireworks barge in approximate position 32°46′03″ N, 117°13′11″ W. The safety zone is necessary to provide for the safety of the crew, spectators, participants, and other vessels and users of the waterway. When this safety zone is being enforced, persons and vessels are prohibited from entering into, transiting through, or anchoring within this safety zone unless authorized by the Captain of the Port, or his designated representative.</P>
        <HD SOURCE="HD1">D. Regulatory Analyses</HD>

        <P>We developed this rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on these statutes and executive orders.<PRTPAGE P="10063"/>
        </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. This determination is based on the size and location of the safety zone. Commercial vessels will not be hindered by the safety zone. Recreational vessels will not be allowed to transit through the designated safety zone during the specified times.</P>
        <HD SOURCE="HD2">2. Impact on Small Entities</HD>
        <P>The Regulatory Flexibility Act of 1980 (RFA), 5 U.S.C. 601-612, as amended, requires federal agencies to consider the potential impact of regulations on small entities during rulemaking. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000. The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities.</P>
        <P>(1) This rule will affect the following entities, some of which may be small entities: The owners or operators of vessels intending to transit or anchor in a portion of Mission Bay from 8:50 p.m. to 10 p.m. on February 16, 2013.</P>
        <P>(2) This safety zone will not have a significant economic impact on a substantial number of small entities for the following reasons: The safety zone will only be in effect for one hour and 10 minutes late in the evening when vessel traffic is low.</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 INTFORMATION CONTACT</E>section to coordinate protest activities so that your message can be received without jeopardizing the safety or security of people, places or vessels.</P>
        <HD SOURCE="HD2">7. Unfunded Mandates Reform Act</HD>
        <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or more in any one year. Though this rule will not result in such an expenditure, we do discuss the effects of this rule elsewhere in this preamble.</P>
        <HD SOURCE="HD2">8. Taking of Private Property</HD>
        <P>This rule will not cause a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.</P>
        <HD SOURCE="HD2">9. Civil Justice Reform</HD>
        <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.</P>
        <HD SOURCE="HD2">10. Protection of Children</HD>
        <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or risk to safety that may disproportionately affect children.</P>
        <HD SOURCE="HD2">11. Indian Tribal Governments</HD>
        <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
        <HD SOURCE="HD2">12. Energy Effects</HD>
        <P>This action is not a “significant energy action” under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use.</P>
        <HD SOURCE="HD2">13. Technical Standards</HD>
        <P>This rule does not use technical standards. Therefore, we did not consider the use of voluntary consensus standards.</P>
        <HD SOURCE="HD2">14. Environment</HD>

        <P>We have analyzed this rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA) (42 U.S.C. 4321-4370f), and have determined that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment. This rule involves establishment of a temporary safety zone. 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<PRTPAGE P="10064"/>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. 1226, 1231; 46 U.S.C. Chapter 701, 3306, 3703; 50 U.S.C. 191, 195; 33 CFR 1.05-1, 6.04-1, 6.04-6, and 160.5; Pub. L. 107-295, 116 Stat. 2064; Department of Homeland Security Delegation No. 0170.1.</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="165" TITLE="33">
          <AMDPAR>2. Add § 165.T11-545 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 165.T11-545</SECTNO>
            <SUBJECT>Safety Zone; Sea World San Diego Fireworks, Mission Bay; San Diego, CA.</SUBJECT>
            <P>(a)<E T="03">Location.</E>The safety zone will include the area within 600 feet of the fireworks barge in approximate position 32°46′03″ N, 117°13′11″ W.</P>
            <P>(b)<E T="03">Enforcement Period.</E>This safety zone will be enforced from 8:50 p.m. to 10 p.m. on February 16, 2013.</P>
            <P>(c)<E T="03">Definitions.</E>The following definition applies to this section:<E T="03">designated representative</E>means any commissioned, warrant, or petty officer of the Coast Guard on board Coast Guard, Coast Guard Auxiliary, local, state, or federal law enforcement vessels who have been authorized to act on the behalf of the Captain of the Port.</P>
            <P>(d)<E T="03">Regulations.</E>(1) In accordance with general regulations in 33 CFR Part 165, Subpart C, entry into, transit through or anchoring within this safety zone is prohibited unless authorized by the Captain of the Port of San Diego or his designated representative.</P>
            <P>(2) Mariners requesting permission to transit through the safety zone may request authorization to do so from the Sector San Diego Command Center. The Command Center may be contacted on VHF-FM Channel 16.</P>
            <P>(3) All persons and vessels shall comply with the instructions of the Coast Guard Captain of the Port or his designated representative.</P>
            <P>(4) Upon being hailed by U.S. Coast Guard patrol personnel by siren, radio, flashing light, or other means, the operator of a vessel shall proceed as directed.</P>
            <P>(5) The Coast Guard may be assisted by other federal, state, or local agencies.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: January 29, 2013.</DATED>
          <NAME>J.A. Janszen,</NAME>
          <TITLE>Commander, United States Coast Guard, Acting, Captain of the Port San Diego.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03261 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-04-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Coast Guard</SUBAGY>
        <CFR>33 CFR Part 165</CFR>
        <DEPDOC>[Docket Number USCG-2013-0039]</DEPDOC>
        <RIN>RIN 1625-AA00</RIN>
        <SUBJECT>Safety Zone; Vigor Industrial Roll-Out, West Duwamish Waterway, Seattle, WA</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Coast Guard, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Temporary final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Coast Guard is establishing a temporary safety zone in the West Duwamish Waterway in Seattle, Washington for a vessel roll-out at Vigor Industrial. The safety zone is necessary to ensure the safety of the maritime public and workers involved in the roll-out. The safety zone will prohibit any person or vessel from entering or remaining in the safety zone unless authorized by the Captain of the Port or a Designated Representative.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective on February 28, 2013 from 2:00 a.m. until 10:00 a.m.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Documents mentioned in this preamble are part of docket [USCG-2013-0039]. To view documents mentioned in this preamble as being available in the docket, go to<E T="03">http://www.regulations.gov,</E>type the docket number in the “SEARCH” box and click “SEARCH.” Click on Open Docket Folder on the line associated with this rulemaking. You may also visit the Docket Management Facility in Room W12-140 on the ground floor of the Department of Transportation West Building, 1200 New Jersey Avenue SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>If you have questions on this rule, call or email Ensign Nathaniel P. Clinger, Waterways Management Division, Coast Guard Sector Puget Sound, Coast Guard; telephone 206-217-6045, email<E T="03">SectorPugetSoundWWM@uscg.mil</E>. If you have questions on viewing or submitting material to the docket, call Renee V. Wright, Program Manager, Docket Operations, telephone (202) 366-9826.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Table of Acronyms</HD>
        <EXTRACT>
          <FP SOURCE="FP-1">DHSDepartment of Homeland Security</FP>
          <FP SOURCE="FP-1">FR<E T="04">Federal Register</E>
          </FP>
          <FP SOURCE="FP-1">NPRMNotice of Proposed Rulemaking</FP>
        </EXTRACT>
        <HD SOURCE="HD1">A. Regulatory History and Information</HD>
        <P>The Coast Guard is issuing this temporary final rule without prior notice and opportunity to comment pursuant to authority under section 4(a) of the Administrative Procedure Act (APA) (5 U.S.C. 553(b)). This provision authorizes an agency to issue a rule without prior notice and opportunity to comment when the agency for good cause finds that those procedures are “impracticable, unnecessary, or contrary to the public interest.” Under 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule because it would be impracticable to do so. Delaying promulgation may result in injury or damage to persons and vessels since the roll-out event is scheduled to occur before a comment period would end and a Final Rule could be published.</P>

        <P>Under 5 U.S.C. 553(d)(3), the Coast Guard finds that good cause exists for making this rule effective less than 30 days after publication in the<E T="04">Federal Register</E>. Delaying the effective date until 30 days after publication would be impracticable, as this delay would eliminate the safety zones' effectiveness and usefulness in protecting persons, property, and the safe navigation of maritime traffic during the 30-day period.</P>
        <HD SOURCE="HD1">B. Basis and Purpose</HD>
        <P>Vigor Industrial is conducting a vessel roll-out in the West Duwamish Waterway in Seattle, Washington on February 28, 2013. Due to the dangers involved with a large slow moving dry dock that will be maneuvering close to the shore, the Coast Guard is establishing a temporary safety zone to ensure the safety of the workers involved as well as the maritime public.</P>
        <HD SOURCE="HD1">C. Discussion of the Final Rule</HD>

        <P>The safety zone helps ensure the public's safety during a vessel roll-out that will take place on February 28, 2013 in the waters of the West Duwamish Waterway. The safety zone created by this rule encompasses all waters of the West Duwamish Waterway in Seattle, Washington within the area created by connecting the following points: 47°35′04″ N, 122°21′30″ W thence westerly to 47°35′04″ N, 122°21′50″ W thence northerly to 47°35′19″ N, 122°21′50″ W thence easterly to 47°35′19″ N, 122°21′30″ W<PRTPAGE P="10065"/>thence southerly to 47°35′04″ N, 122°21′30″ W. Geographically, the safety zone is adjacent to the northern tip of Harbor Island in Seattle, WA.</P>
        <P>All persons and vessels will be prohibited from entering or remaining in the safety zone. The safety zone will be effective on February 28, 2013 from 2:00 a.m. to 10:00 a.m. unless cancelled sooner by the Captain of the Port or a Designated Representative. The safety zone will be enforced by the U.S. Coast Guard. The Captain of the Port may also be assisted in the enforcement of this safety zone by other federal, state, or local agencies.</P>
        <HD SOURCE="HD1">D. Regulatory Analyses</HD>
        <P>We developed this rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on these statutes and executive orders.</P>
        <HD SOURCE="HD2">1. Regulatory Planning and Review</HD>
        <P>This rule is not a significant regulatory action under section 3(f) of Executive Order 12866, Regulatory Planning and Review, as supplemented by Executive Order 13563, Improving Regulation and Regulatory Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of Executive Order 12866 or under section 1 of Executive Order 13563. The Office of Management and Budget has not reviewed it under those Orders. The Coast Guard has made this finding based on the fact that the safety zone is limited in duration, and maritime traffic may be able to transit through the safety zone with permission of the Captain of the Port or a Designated Representative.</P>
        <HD SOURCE="HD2">2. Impact on Small Entities</HD>
        <P>The Regulatory Flexibility Act of 1980 (RFA), 5 U.S.C. 601-612, as amended, requires federal agencies to consider the potential impact of regulations on small entities during rulemaking. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000. The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities. This rule will affect the following entities, some of which may be small entities: The owners or operators of vessels intending to transit through the safety zone created by this rule. This rule will not have a significant economic impact on a substantial number of small entities, although the safety zone will apply to the entire width of the waterway, the zone will be enforced for a limited period of time, and vessel traffic will be allowed to pass through the safety zone with the permission of the Captain of the Port or a Designated Representative.</P>
        <HD SOURCE="HD2">3. Assistance for Small Entities</HD>

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

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

        <P>We have analyzed this rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA) (42 U.S.C. 4321-4370f), and have determined that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment. This rule involves the establishment of a temporary safety zone. 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, 160.5; Pub. L. 107-295, 116 Stat. 2064; Department of Homeland Security Delegation No. 0170.1</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="165" TITLE="33">
          <AMDPAR>2. Add § 165.T13-241 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 165.T13-241</SECTNO>
            <SUBJECT>Safety Zone; Vigor Industrial Vessel Roll-Out, West Duwamish Waterway, Seattle, WA.</SUBJECT>
            <P>(a)<E T="03">Location.</E>The following area is a safety zone: All waters of the West Duwamish Waterway in Seattle, WA encompassed within the area created by connecting the following points: 47°35′04″ N, 122°21′30″ W thence westerly to 47°35′04″ N, 122°21′50″ W thence northerly to 47°35′19″ N, 122°21′50″ W thence easterly to 47°35′19″ N, 122°21′30″ W thence southerly to 47°35′04″ N, 122°21′30″ W.</P>
            <P>(b)<E T="03">Regulations.</E>In accordance with the general regulations in 33 CFR Part 165, Subpart C, no person may enter or remain in the safety zone created in this rule unless authorized by the Captain of the Port or a Designated Representative. See 33 CFR Part 165, Subpart C, for additional information and requirements. Vessel operators wishing to enter the zone during the enforcement period must request permission for entry by contacting Vessel Traffic Service Puget Sound on VHF channel 14, or the Sector Puget Sound Joint Harbor Operations Center at (206) 217-6001.</P>
            <P>(c)<E T="03">Enforcement Period.</E>The safety zone created in this rule is enforced from 2:00 a.m. to 10:00 a.m. on February 28, 2013 unless cancelled sooner by the Captain of the Port.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: February 1, 2013.</DATED>
          <NAME>S. J. Ferguson,</NAME>
          <TITLE>Captain, U.S. Coast Guard, Captain of the Port, Puget Sound.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03264 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-04-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Federal Emergency Management Agency</SUBAGY>
        <CFR>44 CFR Part 67</CFR>
        <DEPDOC>[Docket ID FEMA-2013-0002]</DEPDOC>
        <SUBJECT>Final Flood Elevation Determinations</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Emergency Management Agency, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Base (1% annual-chance) Flood Elevations (BFEs) and modified BFEs are made final for the communities listed below. The BFEs and modified BFEs are the basis for the floodplain management measures that each community is required either to adopt or to show evidence of being already in effect in order to qualify or remain qualified for participation in the National Flood Insurance Program (NFIP).</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The date of issuance of the Flood Insurance Rate Map (FIRM) showing BFEs and modified BFEs for each community. This date may be obtained by contacting the office where the maps are available for inspection as indicated in the table below.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The final BFEs for each community are available for inspection at the office of the Chief Executive Officer of each community. The respective addresses are listed in the table below.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal Emergency Management Agency, 500 C Street SW., Washington, DC 20472, (202) 646-4064, or (email)<E T="03">Luis.Rodriguez3@fema.dhs.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The Federal Emergency Management Agency (FEMA) makes the final determinations listed below for the modified BFEs for each community listed. These modified elevations have been published in newspapers of local circulation and ninety (90) days have elapsed since that publication. The Deputy Associate Administrator for Mitigation has resolved any appeals resulting from this notification.</P>
        <P>This final rule is issued in accordance with section 110 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4104, and 44 CFR part 67. FEMA has developed criteria for floodplain management in floodprone areas in accordance with 44 CFR part 60.</P>
        <P>Interested lessees and owners of real property are encouraged to review the proof Flood Insurance Study and FIRM available at the address cited below for each community.The BFEs and modified BFEs are made final in the communities listed below. Elevations at selected locations in each community are shown.</P>
        <P>
          <E T="03">National Environmental Policy Act.</E>This final rule is categorically excluded from the requirements of 44 CFR part 10, Environmental Consideration. An environmental impact assessment has not been prepared.</P>
        <P>
          <E T="03">Regulatory Flexibility Act.</E>As flood elevation determinations are not within the scope of the Regulatory Flexibility Act, 5 U.S.C. 601-612, a regulatory flexibility analysis is not required.</P>
        <P>
          <E T="03">Regulatory Classification.</E>This final rule is not a significant regulatory action under the criteria of section 3(f) of Executive Order 12866 of September 30, 1993, Regulatory Planning and Review, 58 FR 51735.</P>
        <P>
          <E T="03">Executive Order 13132, Federalism.</E>This final rule involves no policies that have federalism implications under Executive Order 13132.</P>
        <P>
          <E T="03">Executive Order 12988, Civil Justice Reform.</E>This final rule meets the applicable standards of Executive Order 12988.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 44 CFR Part 67</HD>
          <P>Administrative practice and procedure, Flood insurance, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        
        <P>Accordingly, 44 CFR part 67 is amended as follows:</P>
        <REGTEXT PART="67" TITLE="44">
          <PART>
            <HD SOURCE="HED">PART 67—[AMENDED]</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 67 continues to read as follows:</AMDPAR>
          <AUTH>
            <PRTPAGE P="10067"/>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 4001<E T="03">et seq.;</E>Reorganization Plan No. 3 of 1978, 3 CFR, 1978 Comp., p. 329; E.O. 12127, 44 FR 19367, 3 CFR, 1979 Comp., p. 376.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="67" TITLE="44">
          <SECTION>
            <SECTNO>§ 67.11</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. The tables published under the authority of § 67.11 are amended as follows:</AMDPAR>
          <GPOTABLE CDEF="s25,r25,r25,r50,15" COLS="5" OPTS="L2,tp0,i1">
            <TTITLE/>
            <BOXHD>
              <CHED H="1">State</CHED>
              <CHED H="1">City/town/county</CHED>
              <CHED H="1">Source of flooding</CHED>
              <CHED H="1">Location</CHED>
              <CHED H="1">* Elevation in feet<LI>(NGVD)</LI>
                <LI>+ Elevation in feet</LI>
                <LI>(NAVD)</LI>
                <LI># Depth in feet above ground</LI>
                <LI>⁁ Elevation in meters (MSL)</LI>
                <LI>modified</LI>
              </CHED>
            </BOXHD>
            <ROW EXPSTB="04">
              <ENT I="21">
                <E T="02">Unincorporated Areas of Halifax County, North Carolina</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="21">
                <E T="02">Docket No.: FEMA-B-1198</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">North Carolina</ENT>
              <ENT>Unincorporated Areas of Halifax County</ENT>
              <ENT>Fishing Creek</ENT>
              <ENT>At the upstream side of the railroad</ENT>
              <ENT>+97</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT O="xl"/>
              <ENT>Approximately 50 feet downstream of White Oak Road</ENT>
              <ENT>+132</ENT>
            </ROW>
            <ROW EXPSTB="04">
              <ENT I="22">* National Geodetic Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">+ North American Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"># Depth in feet above ground.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">⁁ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
            </ROW>
            <ROW>
              <ENT I="21">
                <E T="02">ADDRESSES</E>
              </ENT>
            </ROW>
            
            <ROW>
              <ENT I="21">
                <E T="02">Unincorporated Areas of Halifax County</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the Halifax County Planning Department, 15 West Pittsylvania Street, Halifax, NC 27839.</ENT>
            </ROW>
          </GPOTABLE>
          <GPOTABLE CDEF="s25,r50,15,r25" COLS="4" OPTS="L2,tp0,i1">
            <TTITLE/>
            <BOXHD>
              <CHED H="1">Flooding source(s)</CHED>
              <CHED H="1">Location of referenced elevation</CHED>
              <CHED H="1">* Elevation in feet<LI>(NGVD)</LI>
                <LI>+ Elevation in feet</LI>
                <LI>(NAVD)</LI>
                <LI># Depth in feet above ground</LI>
                <LI>⁁ Elevation in meters</LI>
                <LI>(MSL)</LI>
                <LI>modified</LI>
              </CHED>
              <CHED H="1">Communities affected</CHED>
            </BOXHD>
            <ROW EXPSTB="03">
              <ENT I="21">
                <E T="02">Osceola County, Florida, and Incorporated Areas</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="21">
                <E T="02">Docket No.: FEMA-B-1198</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Bass Slough (Lower Reach)</ENT>
              <ENT>Approximately 1,211 feet downstream of County Route 525</ENT>
              <ENT>+57</ENT>
              <ENT>City of Kissimmee, Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.6 mile upstream of State Route 530</ENT>
              <ENT>+76</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Bass Slough (Upper Reach)</ENT>
              <ENT>Approximately 1,863 feet downstream of the Bass Slough Tributary confluence</ENT>
              <ENT>+79</ENT>
              <ENT>City of Kissimmee, Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 337 feet upstream of Florida Parkway</ENT>
              <ENT>+80</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Bass Slough Tributary</ENT>
              <ENT>At the Bass Slough (Upper Reach) confluence</ENT>
              <ENT>+79</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.4 mile upstream of the Bass Slough (Upper Reach) confluence</ENT>
              <ENT>+79</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Clay Hole Pond</ENT>
              <ENT>Entire shoreline</ENT>
              <ENT>+66</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Courthouse Pond</ENT>
              <ENT>Entire shoreline</ENT>
              <ENT>+68</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Eagle Pond</ENT>
              <ENT>Entire shoreline</ENT>
              <ENT>+65</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">East City Canal Tributary 1</ENT>
              <ENT>At the upstream side of Vine Street</ENT>
              <ENT>+66</ENT>
              <ENT>City of Kissimmee.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 637 feet upstream of Vine Street</ENT>
              <ENT>+66</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Lake Marian</ENT>
              <ENT>Entire shoreline</ENT>
              <ENT>+59</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Multiple Ponding Areas</ENT>
              <ENT>Area bound by San Remo Road to the north and east, Cypress Parkway to the south, and Marigold Avenue to the west</ENT>
              <ENT>+69</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Multiple Ponding Areas</ENT>
              <ENT>Area bound by Florida's Turnpike to the north and east and State Route 523 to the south and west</ENT>
              <ENT>+65</ENT>
              <ENT>City of Kissimmee.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Multiple Ponding Areas</ENT>
              <ENT>Area approximately 0.8 mile northwest of the intersection of Brandon Lane and County Route 523, bound by Williams Road to the north, U.S. Route 441 to the east, and Florida's Turnpike to the south and west</ENT>
              <ENT>+69</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10068"/>
              <ENT I="01">Multiple Ponding Areas</ENT>
              <ENT>Area bound by County Route 523 to the north, U.S. Route 441 to the east, Hayman Ranch Road to the south, and Florida's Turnpike to the west</ENT>
              <ENT>+69</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Multiple Ponding Areas</ENT>
              <ENT>Area approximately 2.4 miles north of the intersection of 3rd Street and 4th Avenue, bound by Williams Road to the north, U.S. Route 441 to the east, and Florida's Turnpike to the south and west</ENT>
              <ENT>+67</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Otter Pond</ENT>
              <ENT>Entire shoreline</ENT>
              <ENT>+69</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ponding Area</ENT>
              <ENT>Area bound by West Orange Street to the north, North Main Street to the east, Sumner Street to the south, and U.S. Routes 17/92 to the west</ENT>
              <ENT>+66</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ponding Area</ENT>
              <ENT>Area bound by Pleasant Hill Road to the north, Florida's Turnpike to the east, and Scrub Jay Trail to the south and west</ENT>
              <ENT>+64</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ponding Area</ENT>
              <ENT>Area approximately 0.9 mile east of the intersection of Martigues Drive and Amiens Road, bound by West Southport Road to the north, Florida's Turnpike to the east, and Scrub Jay Trail to the south and west</ENT>
              <ENT>+63</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ponding Area</ENT>
              <ENT>Area bound by Amiens Road to the north and east, Chestnut Street to the south, and Bordeaux Road to the west</ENT>
              <ENT>+62</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ponding Area</ENT>
              <ENT>Area approximately 0.6 mile east of the intersection of Saint Michel Way and Amiens Road, bound by West Southport Road to the north, Florida's Turnpike to the east, and Scrub Jay Trail to the south and west</ENT>
              <ENT>+62</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ponding Area</ENT>
              <ENT>Area bound by Old Pleasant Hill Road to the north, Scrub Jay Trail to the east, and the Polk County boundary to the south and west</ENT>
              <ENT>+60</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ponding Area</ENT>
              <ENT>Area bound by Chestnut Street to the north, Scrub Jay Trail to the east, and the Polk County boundary to the south and west</ENT>
              <ENT>+63</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ponding Area</ENT>
              <ENT>Area approximately 2.2 miles north of the intersection of Coulter Drive and County Route 523, bound by Williams Road to the north, U.S. Route 441 to the east, and Florida's Turnpike to the south and west</ENT>
              <ENT>+66</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Unnamed Connecting Channel downstream of Clay Hole Pond</ENT>
              <ENT>Just upstream of Eagle Pond</ENT>
              <ENT>+65</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Clay Hole Pond</ENT>
              <ENT>+66</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Unnamed Connecting Channel downstream of Eagle Pond</ENT>
              <ENT>Approximately 0.6 mile downstream of Eagle Pond</ENT>
              <ENT>+65</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Eagle Pond</ENT>
              <ENT>+65</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Unnamed Connecting Channel upstream of Lake Marian</ENT>
              <ENT>Just upstream of Lake Marian</ENT>
              <ENT>+59</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.4 mile upstream of Lake Marian</ENT>
              <ENT>+65</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Unnamed Connecting Channel upstream of Lake Marian</ENT>
              <ENT>Just upstream of Lake Marian</ENT>
              <ENT>+59</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.0 mile upstream of Lake Marian</ENT>
              <ENT>+69</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Unnamed Flooding Area upstream of Lake Marian</ENT>
              <ENT>Just upstream of Lake Marian</ENT>
              <ENT>+59</ENT>
              <ENT>Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.5 mile upstream of Lake Marian</ENT>
              <ENT>+65</ENT>
            </ROW>
            <ROW>
              <ENT I="01">WPA Canal Tributary 1</ENT>
              <ENT>Approximately 1,612 feet upstream of the WPA Canal confluence</ENT>
              <ENT>+71</ENT>
              <ENT>City of St. Cloud, Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.6 miles upstream of Snail Kite Avenue</ENT>
              <ENT>+75</ENT>
            </ROW>
            <ROW>
              <ENT I="01">WPA Canal Tributary 1-1</ENT>
              <ENT>At the WPA Canal Tributary 1 confluence</ENT>
              <ENT>+75</ENT>
              <ENT>City of St. Cloud, Unincorporated Areas of Osceola County.</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22"/>
              <ENT>Approximately 0.7 mile upstream of the WPA Canal Tributary 1 confluence</ENT>
              <ENT>+75</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">* National Geodetic Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">+ North American Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"># Depth in feet above ground.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">⁁ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10069"/>
              <ENT I="21">
                <E T="02">ADDRESSES</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">
                <E T="02">City of Kissimmee</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at City Hall, Engineering Department, Suite 301, 101 North Church Street, Kissimmee, FL 34741.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">City of St. Cloud</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at City Hall, Public Works Department, Building A, 2nd Floor, 1300 9th Street, St. Cloud, FL 34769.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="21">
                <E T="02">Unincorporated Areas of Osceola County</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22">Maps are available for inspection at the Osceola County Stormwater Section, 1 Courthouse Square, Suite 1400, Kissimmee, FL 34741.</ENT>
            </ROW>
            <ROW>
              <ENT I="21">
                <E T="02">Oswego County, New York (All Jurisdictions)</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="21">
                <E T="02">Docket Nos.: FEMA-B-1210 and 1232</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Bell Creek (backwater area)</ENT>
              <ENT>From the Town of Schroeppel corporate limits to approximately 1,380 feet upstream of the Town of Schroeppel corporate limits</ENT>
              <ENT>+379</ENT>
              <ENT>Town of Volney.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Black Creek (backwater area)</ENT>
              <ENT>From the Town of Mexico corporate limits to approximately 200 feet upstream of the Town of Mexico corporate limits</ENT>
              <ENT>+442</ENT>
              <ENT>Town of Palermo.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Lake Ontario</ENT>
              <ENT>Entire shoreline within Selkirk Shores State Park boundary</ENT>
              <ENT>+249</ENT>
              <ENT>Town of Richland.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Lycoming Creek (backwater area)</ENT>
              <ENT>From the Town of Scriba corporate limits to approximately 0.5 mile upstream of the Town of Scriba corporate limits</ENT>
              <ENT>+277</ENT>
              <ENT>Town of New Haven.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Panther Lake</ENT>
              <ENT>Entire shoreline within community</ENT>
              <ENT>+600</ENT>
              <ENT>Town of Amboy.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Salmon River</ENT>
              <ENT>Approximately 0.63 mile upstream of County Route 2A (Lehigh Road)</ENT>
              <ENT>+436</ENT>
              <ENT>Town of Albion.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.96 mile upstream of County Route 2A (Lehigh Road)</ENT>
              <ENT>+440</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Scriba Creek</ENT>
              <ENT>Approximately 0.90 mile upstream of County Route 23 (Potter Road)</ENT>
              <ENT>+546</ENT>
              <ENT>Town of Amboy.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.30 miles upstream of County Route 23 (Potter Road)</ENT>
              <ENT>+547</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="01">South Branch Grindstone Creek (backwater effects from Lake Ontario)</ENT>
              <ENT>Areas within Selkirk Shores State Park boundary</ENT>
              <ENT>+249</ENT>
              <ENT>Town of Richland.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">* National Geodetic Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">+ North American Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"># Depth in feet above ground.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">⁁ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
            </ROW>
            <ROW>
              <ENT I="21">
                <E T="02">ADDRESSES</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">
                <E T="02">Town of Albion</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the Albion Town Municipal Building, 15 Bridge Street, Altmar, NY 13302.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">Town of Amboy</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the Amboy Town Hall, 822 State Route 69, Williamstown, NY 13493.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">Town of New Haven</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the Town Hall, 4279 State Route 104, New Haven, NY 13121.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">Town of Palermo</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the Palermo Town Municipal Offices, 53 County Route 35, Fulton, NY 13069.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">Town of Richland</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the Town of Richland Courthouse Building, 1 Bridge Street, Pulaski, NY 13142.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">Town of Volney</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22">Maps are available for inspection at the Volney Town Offices, 1445 County Road 6, Fulton, NY 13069.</ENT>
            </ROW>
            <ROW>
              <ENT I="21">
                <E T="02">Washoe County, Nevada, and Incorporated Areas</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="21">
                <E T="02">Docket No.: FEMA-B-1227</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">211 Creek</ENT>
              <ENT>Approximately 400 feet downstream of U.S. Route 395</ENT>
              <ENT>+5039</ENT>
              <ENT>City of Reno, Unincorporated Areas of Washoe County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.42 mile upstream of Union Pacific Railroad</ENT>
              <ENT>+5513</ENT>
            </ROW>
            <ROW>
              <ENT I="01">6015 Creek</ENT>
              <ENT>At the upstream side of the West Copperfield Creek confluence</ENT>
              <ENT>+5166</ENT>
              <ENT>City of Reno.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,500 feet upstream of the West Copperfield Creek confluence</ENT>
              <ENT>+5252</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10070"/>
              <ENT I="01">6634 Creek</ENT>
              <ENT>Approximately 1.11 miles downstream of Union Pacific Railroad</ENT>
              <ENT>+5068</ENT>
              <ENT>City of Reno.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.47 mile upstream of Union Pacific Railroad</ENT>
              <ENT>+5473</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Copperfield Creek</ENT>
              <ENT>Approximately 1,600 feet downstream of the West Copperfield Creek confluence</ENT>
              <ENT>+5040</ENT>
              <ENT>City of Reno, Unincorporated Areas of Washoe County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.92 mile upstream of U.S. Route 395 (southbound on-ramp)</ENT>
              <ENT>+5295</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Evans Creek</ENT>
              <ENT>Approximately 1,700 feet upstream of Lakeside Drive</ENT>
              <ENT>+4682</ENT>
              <ENT>City of Reno, Unincorporated Areas of Washoe County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.52 mile upstream of Evans Creek Drive</ENT>
              <ENT>+5070</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Fat Creek</ENT>
              <ENT>Approximately 460 feet downstream of U.S. Route 395</ENT>
              <ENT>+5040</ENT>
              <ENT>City of Reno, Unincorporated Areas of Washoe County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.62 mile upstream of Frontage Road</ENT>
              <ENT>+5086</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Flat Creek</ENT>
              <ENT>Approximately 975 feet downstream of the Flat Creek Split confluence</ENT>
              <ENT>+5043</ENT>
              <ENT>City of Reno, Unincorporated Areas of Washoe County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.58 mile upstream of the Flat Creek Split confluence</ENT>
              <ENT>+5177</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Flat Creek Split</ENT>
              <ENT>Approximately 50 feet upstream of Frontage Road</ENT>
              <ENT>+5043</ENT>
              <ENT>City of Reno, Unincorporated Areas of Washoe County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 130 feet downstream of the Flat Creek confluence</ENT>
              <ENT>+5052</ENT>
            </ROW>
            <ROW>
              <ENT I="01">North Evans Creek</ENT>
              <ENT>Approximately 160 feet downstream of the Evans Creek confluence</ENT>
              <ENT>+4900</ENT>
              <ENT>Unincorporated Areas of Washoe County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.74 mile upstream of the Evans Creek confluence</ENT>
              <ENT>+5094</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Short Creek</ENT>
              <ENT>Approximately 1,500 feet downstream of U.S. Route 395</ENT>
              <ENT>+5039</ENT>
              <ENT>City of Reno, Unincorporated Areas of Washoe County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.61 mile upstream of Frontage Road</ENT>
              <ENT>+5153</ENT>
            </ROW>
            <ROW>
              <ENT I="01">West Copperfield Creek</ENT>
              <ENT>Approximately 1,000 feet downstream of Frontage Road</ENT>
              <ENT>+5060</ENT>
              <ENT>City of Reno, Unincorporated Areas of Washoe County.</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22"/>
              <ENT>Approximately 1.01 miles upstream of Frontage Road</ENT>
              <ENT>+5259</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">* National Geodetic Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">+ North American Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"># Depth in feet above ground.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">⁁ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
            </ROW>
            <ROW>
              <ENT I="21">
                <E T="02">ADDRESSES</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">
                <E T="02">City of Reno</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the City Hall Annex, 450 Sinclair Street, Reno, NV 89501.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="21">
                <E T="02">Unincorporated Areas of Washoe County</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22">Maps are available for inspection at the Washoe County Administration Building, 1001 East 9th Street, Reno, NV 89512.</ENT>
            </ROW>
            <ROW>
              <ENT I="21">
                <E T="02">Edgecombe County, North Carolina, and Incorporated Areas</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="21">
                <E T="02">Docket No.: FEMA-B-1202 and B-1213</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Cokey Swamp</ENT>
              <ENT>Approximately 0.9 mile downstream of North Carolina Highway 43</ENT>
              <ENT>+77</ENT>
              <ENT>Town of Sharpsburg, Unincorporated Areas of Edgecombe County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 70 feet downstream of the railroad</ENT>
              <ENT>+118</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cokey Swamp Tributary</ENT>
              <ENT>At the Cokey Swamp confluence</ENT>
              <ENT>+88</ENT>
              <ENT>Unincorporated Areas of Edgecombe County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 450 feet upstream of Floods Store Road (State Route 1146)</ENT>
              <ENT>+106</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cowlick Creek</ENT>
              <ENT>At the Tar River confluence</ENT>
              <ENT>+78</ENT>
              <ENT>City of Rocky Mount.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the Parkers Canal confluence</ENT>
              <ENT>+79</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Fishing Creek</ENT>
              <ENT>Approximately 0.3 mile downstream of U.S. Highway 301</ENT>
              <ENT>+94</ENT>
              <ENT>Unincorporated Areas of Edgecombe County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,000 feet downstream of the railroad</ENT>
              <ENT>+95</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Indian Branch</ENT>
              <ENT>Approximately 175 feet downstream of Gay Road (State Route 1268)</ENT>
              <ENT>+70</ENT>
              <ENT>Unincorporated Areas of Edgecombe County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Cokey Swamp</ENT>
              <ENT>At the Cokey Swamp confluence</ENT>
              <ENT>+80</ENT>
              <ENT>Unincorporated Areas of Edgecombe County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 250 feet downstream of Greenpasture Road (State Route 1141)</ENT>
              <ENT>+93</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10071"/>
              <ENT I="01">Swift Creek</ENT>
              <ENT>Approximately 0.6 mile downstream of Seven Bridges Road (State Route 1404)</ENT>
              <ENT>+78</ENT>
              <ENT>Unincorporated Areas of Edgecombe County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 400 feet downstream of the railroad</ENT>
              <ENT>+90</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Tar River</ENT>
              <ENT>Approximately 0.5 mile downstream of the Cowlick Creek confluence</ENT>
              <ENT>+78</ENT>
              <ENT>City of Rocky Mount, Unincorporated Areas of Edgecombe County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,100 feet downstream of Atlantic Avenue</ENT>
              <ENT>+81</ENT>
            </ROW>
            <ROW>
              <ENT I="01">White Oak Swamp</ENT>
              <ENT>Approximately 0.6 mile upstream of Speight's Chapel Road</ENT>
              <ENT>+103</ENT>
              <ENT>Town of Whitakers, Unincorporated Areas of Edgecombe County.</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22"/>
              <ENT>Approximately 630 feet upstream of South Cutchin Street (State Route 1410)</ENT>
              <ENT>+124</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">* National Geodetic Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">+ North American Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"># Depth in feet above ground.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">⁁ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
            </ROW>
            <ROW>
              <ENT I="21">
                <E T="02">ADDRESSES</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">
                <E T="02">City of Rocky Mount</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the Planning Department, 331 South Franklin Street, Rocky Mount, NC 27802.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">Town of Sharpsburg</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the Town Hall, 110 Railroad Street, Sharpsburg, NC 27878.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">Town of Whitakers</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the Town Hall, 302 Northwest Railroad Street, Whitakers, NC 27891.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="21">
                <E T="02">Unincorporated Areas of Edgecombe County</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22">Maps are available for inspection at the Edgecombe County Planning Department, 201 Saint Andrews Street, Tarboro, NC 27886.</ENT>
            </ROW>
            <ROW>
              <ENT I="21">
                <E T="02">Nash County, North Carolina, and Incorporated Areas</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="21">
                <E T="02">Docket No.: FEMA-B-1153</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Cokey Swamp</ENT>
              <ENT>Approximately 90 feet downstream of Old Wilson Road (Secondary Road 1002)</ENT>
              <ENT>+107</ENT>
              <ENT>City of Rocky Mount.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.1 mile upstream of Old Wilson Road (Secondary Road 1002)</ENT>
              <ENT>+118</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cowlick Creek</ENT>
              <ENT>Just upstream of U.S. Highway 64</ENT>
              <ENT>+79</ENT>
              <ENT>City of Rocky Mount.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Cortland Avenue</ENT>
              <ENT>+92</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Fishing Creek</ENT>
              <ENT>Just upstream of the railroad</ENT>
              <ENT>+97</ENT>
              <ENT>Unincorporated Areas of Nash County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet downstream of Ward Road (Secondary Road 1502)</ENT>
              <ENT>+132</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Grape Branch</ENT>
              <ENT>Approximately 200 feet upstream of Beechwood Drive</ENT>
              <ENT>+107</ENT>
              <ENT>City of Rocky Mount, Unincorporated Areas of Nash County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,100 feet upstream of Beechwood Drive</ENT>
              <ENT>+107</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Indian Branch</ENT>
              <ENT>Approximately 175 feet downstream of Gay Road (Secondary Road 1268)</ENT>
              <ENT>+70</ENT>
              <ENT>City of Rocky Mount.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 190 feet upstream of Hunting Lodge Drive</ENT>
              <ENT>+91</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Cokey Swamp</ENT>
              <ENT>Approximately 250 feet downstream of Greenpasture Road (Secondary Road 1141)</ENT>
              <ENT>+93</ENT>
              <ENT>City of Rocky Mount.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet downstream of Kingston Avenue</ENT>
              <ENT>+130</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Cokey Swamp Tributary</ENT>
              <ENT>At the confluence with Little Cokey Swamp</ENT>
              <ENT>+105</ENT>
              <ENT>City of Rocky Mount.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 200 feet upstream of South Church Street</ENT>
              <ENT>+126</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Maple Creek</ENT>
              <ENT>Approximately 0.3 mile upstream of Bethlehem Road (Secondary Road 1142)</ENT>
              <ENT>+111</ENT>
              <ENT>City of Rocky Mount, Unincorporated Areas of Nash County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 280 feet upstream of South Old Carriage Road</ENT>
              <ENT>+166</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Parkers Canal</ENT>
              <ENT>At the confluence with Cowlick Creek</ENT>
              <ENT>+79</ENT>
              <ENT>City of Rocky Mount.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 60 feet downstream of Atlantic Avenue</ENT>
              <ENT>+98</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Pig Basket Creek</ENT>
              <ENT>Approximately 900 feet upstream of Red Oak Road (Secondary Road 1003)</ENT>
              <ENT>+127</ENT>
              <ENT>Town of Red Oak, Unincorporated Areas of Nash County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.4 mile upstream of Taylors Store Road (Secondary Road 1004)</ENT>
              <ENT>+155</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10072"/>
              <ENT I="01">Polecat Branch</ENT>
              <ENT>At the confluence with Maple Creek</ENT>
              <ENT>+112</ENT>
              <ENT>Unincorporated Areas of Nash County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.8 mile upstream of the confluence with Polecat Branch Tributary</ENT>
              <ENT>+120</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sapony Creek</ENT>
              <ENT>Approximately 200 feet upstream of Sandy Cross Road (Secondary Road 1717)</ENT>
              <ENT>+132</ENT>
              <ENT>Unincorporated Areas of Nash County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,550 feet upstream of NC Highway 58</ENT>
              <ENT>+145</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Stony Creek</ENT>
              <ENT>Approximately 0.5 mile downstream of Red Oak Road (Secondary Road 1003)</ENT>
              <ENT>+130</ENT>
              <ENT>City of Rocky Mount, Town of Nashville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of U.S. Route 64</ENT>
              <ENT>+152</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Swift Creek</ENT>
              <ENT>Approximately 1.8 miles downstream of the Edgecombe County boundary</ENT>
              <ENT>+88</ENT>
              <ENT>City of Rocky Mount, Unincorporated Areas of Nash County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At Red Oak Road (Secondary Road 1003)</ENT>
              <ENT>+131</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Tar River</ENT>
              <ENT>Approximately 150 feet downstream of South Old Carriage Road</ENT>
              <ENT>+133</ENT>
              <ENT>City of Rocky Mount, Unincorporated Areas of Nash County.</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22"/>
              <ENT>Approximately 0.64 mile downstream of U.S. Highway 64</ENT>
              <ENT>+162</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">* National Geodetic Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">+ North American Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"># Depth in feet above ground.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">⁁ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
            </ROW>
            <ROW>
              <ENT I="21">
                <E T="02">ADDRESSES</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">
                <E T="02">City of Rocky Mount</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the Planning Department, 331 South Franklin Street, Rocky Mount, NC 27802.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">Town of Nashville</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the Town Hall, 499 South Barnes Street, Nashville, NC 27856.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">Town of Red Oak</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the Town Hall, 8406 Main Street, Red Oak, NC 27868.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="21">
                <E T="02">Unincorporated Areas of Nash County</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the Nash County Planning Department, 120 West Washington Street, Suite 2110, Nashville, NC 27856.</ENT>
            </ROW>
          </GPOTABLE>
          <EXTRACT>
            <FP>(Catalog of Federal Domestic Assistance No. 97.022, “Flood Insurance.”)</FP>
          </EXTRACT>
        </REGTEXT>
        <SIG>
          <NAME>James A. Walke,</NAME>
          <TITLE>Acting Deputy Associate Administrator for Mitigation, Department of Homeland Security, Federal Emergency Management Agency.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03259 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-12-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Federal Emergency Management Agency</SUBAGY>
        <CFR>44 CFR Part 67</CFR>
        <DEPDOC>[Docket ID FEMA-2013-0002]</DEPDOC>
        <SUBJECT>Final Flood Elevation Determinations</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Emergency Management Agency, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Base (1% annual-chance) Flood Elevations (BFEs) and modified BFEs are made final for the communities listed below. The BFEs and modified BFEs are the basis for the floodplain management measures that each community is required either to adopt or to show evidence of being already in effect in order to qualify or remain qualified for participation in the National Flood Insurance Program (NFIP).</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Dates:</E>The date of issuance of the Flood Insurance Rate Map (FIRM) showing BFEs and modified BFEs for each community. This date may be obtained by contacting the office where the maps are available for inspection as indicated in the table below.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The final BFEs for each community are available for inspection at the office of the Chief Executive Officer of each community. The respective addresses are listed in the table below.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal Emergency Management Agency, 500 C Street SW., Washington, DC 20472, (202) 646-4064, or (email)<E T="03">luis.rodriguez3@fema.dhs.gov</E>.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The Federal Emergency Management Agency (FEMA) makes the final determinations listed below for the modified BFEs for each community listed. These modified elevations have been published in newspapers of local circulation and ninety (90) days have elapsed since that publication. The Deputy Federal Insurance and Mitigation Administrator has resolved any appeals resulting from this notification.</P>
        <P>This final rule is issued in accordance with section 110 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4104, and 44 CFR part 67. FEMA has developed criteria for floodplain management in floodprone areas in accordance with 44 CFR part 60.</P>

        <P>Interested lessees and owners of real property are encouraged to review the<PRTPAGE P="10073"/>proof Flood Insurance Study and FIRM available at the address cited below for each community.The BFEs and modified BFEs are made final in the communities listed below. Elevations at selected locations in each community are shown.</P>
        <P>
          <E T="03">National Environmental Policy Act.</E>This final rule is categorically excluded from the requirements of 44 CFR part 10, Environmental Consideration. An environmental impact assessment has not been prepared.</P>
        <P>
          <E T="03">Regulatory Flexibility Act.</E>As flood elevation determinations are not within the scope of the Regulatory Flexibility Act, 5 U.S.C. 601-612, a regulatory flexibility analysis is not required.</P>
        <P>
          <E T="03">Regulatory Classification.</E>This final rule is not a significant regulatory action under the criteria of section 3(f) of Executive Order 12866 of September 30, 1993, Regulatory Planning and Review, 58 FR 51735.</P>
        <P>
          <E T="03">Executive Order 13132, Federalism.</E>This final rule involves no policies that have federalism implications under Executive Order 13132.</P>
        <P>
          <E T="03">Executive Order 12988, Civil Justice Reform.</E>This final rule meets the applicable standards of Executive Order 12988.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 44 CFR Part 67</HD>
          <P>Administrative practice and procedure, Flood insurance, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        
        <P>Accordingly, 44 CFR part 67 is amended as follows:</P>
        <REGTEXT PART="67" TITLE="44">
          <PART>
            <HD SOURCE="HED">PART 67—[AMENDED]</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 67 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 4001<E T="03">et seq.;</E>Reorganization Plan No. 3 of 1978, 3 CFR, 1978 Comp., p. 329; E.O. 12127, 44 FR 19367, 3 CFR, 1979 Comp., p. 376.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="67" TITLE="44">
          <SECTION>
            <SECTNO>§ 67.11</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. The tables published under the authority of § 67.11 are amended as follows:</AMDPAR>
          <GPOTABLE CDEF="s30,r45,17,r30" COLS="4" OPTS="L2,i1">
            <TTITLE/>
            <BOXHD>
              <CHED H="1">Flooding source(s)</CHED>
              <CHED H="1">Location of referenced elevation</CHED>
              <CHED H="1">* Elevation in feet (NGVD)<LI>+ Elevation in feet</LI>
                <LI>(NAVD)</LI>
                <LI># Depth in feet above ground</LI>
                <LI>⁁ Elevation in meters (MSL)</LI>
              </CHED>
              <CHED H="1">Communities affected</CHED>
            </BOXHD>
            <ROW EXPSTB="03">
              <ENT I="21">
                <E T="02">Duval County, Florida, and Incorporated Areas</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="21">
                <E T="02">Docket No.: FEMA-B-1126</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Big Davis Creek</ENT>
              <ENT>Just upstream of I-95</ENT>
              <ENT>+6</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.25 mile upstream of Philips Highway</ENT>
              <ENT>+17</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Big Fishweir Creek</ENT>
              <ENT>Just upstream of Roosevelt Boulevard</ENT>
              <ENT>+6</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Lakeshore Boulevard</ENT>
              <ENT>+21</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Big Fishweir Creek Tributary 1</ENT>
              <ENT>Just upstream of the railroad</ENT>
              <ENT>+10</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Cassat Avenue</ENT>
              <ENT>+19</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Bigelow Branch</ENT>
              <ENT>Just upstream of Talleyrand Avenue</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,500 feet upstream of Buckman Street</ENT>
              <ENT>+15</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Blockhouse Creek</ENT>
              <ENT>Approximately 6,700 feet upstream of the confluence with the Trout River</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Armsdale Road</ENT>
              <ENT>+17</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Bonett Branch</ENT>
              <ENT>At the confluence with Pottsburg Creek</ENT>
              <ENT>+10</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of I-95</ENT>
              <ENT>+19</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Box Branch</ENT>
              <ENT>At the confluence with Pablo Creek</ENT>
              <ENT>+7</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the confluence with Box Branch Tributary 1</ENT>
              <ENT>+14</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Box Branch Tributary 1</ENT>
              <ENT>At the confluence with Box Branch</ENT>
              <ENT>+14</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 3,350 feet upstream of the confluence with Box Branch</ENT>
              <ENT>+17</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Butcher Pen Creek</ENT>
              <ENT>Just upstream of Wesconnet Road</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 600 feet upstream of Randia Road</ENT>
              <ENT>+17</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Caldwell Branch</ENT>
              <ENT>Approximately 1,300 feet upstream of the confluence with Yellow Water Creek</ENT>
              <ENT>+68</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 4,100 feet upstream of the confluence with Caldwell Branch Tributary 2</ENT>
              <ENT>+79</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Caldwell Branch Tributary 1</ENT>
              <ENT>At the confluence with Caldwell Branch</ENT>
              <ENT>+74</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 6,700 feet upstream of the confluence with Caldwell Branch</ENT>
              <ENT>+81</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Caldwell Branch Tributary 2</ENT>
              <ENT>At the confluence with Caldwell Branch</ENT>
              <ENT>+77</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 4,000 feet upstream of the confluence with Caldwell Branch</ENT>
              <ENT>+81</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Caney Branch</ENT>
              <ENT>Approximately 4,000 feet upstream of the confluence with Rushing Branch</ENT>
              <ENT>+7</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 2.5 miles upstream of the confluence with Rushing Branch</ENT>
              <ENT>+22</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cedar Creek</ENT>
              <ENT>Just upstream of I-95</ENT>
              <ENT>+6</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of Lem Turner Road</ENT>
              <ENT>+23</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cedar Creek Tributary 2</ENT>
              <ENT>At the confluence with Cedar Creek</ENT>
              <ENT>+13</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of Terrell Road</ENT>
              <ENT>+16</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cedar Creek Tributary 6</ENT>
              <ENT>At the confluence with Cedar Creek</ENT>
              <ENT>+8</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10074"/>
              <ENT I="22"/>
              <ENT>Just downstream of Biscayne Boulevard</ENT>
              <ENT>+15</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cedar Creek Tributary 7</ENT>
              <ENT>At the confluence with Cedar Creek</ENT>
              <ENT>+18</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Lem Turner Road</ENT>
              <ENT>+19</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cedar Creek Tributary 8</ENT>
              <ENT>At the confluence with Cedar Creek</ENT>
              <ENT>+18</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Lem Turner Road</ENT>
              <ENT>+18</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cedar River</ENT>
              <ENT>Approximately 1,500 feet upstream of the confluence with Cedar River Tributary 1</ENT>
              <ENT>+6</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 3,000 feet upstream of the confluence with Cedar River Tributary 16</ENT>
              <ENT>+42</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cedar River Tributary 1</ENT>
              <ENT>At the confluence with the Cedar River</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet upstream of Lakeshore Boulevard</ENT>
              <ENT>+6</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cedar River Tributary 12</ENT>
              <ENT>At the confluence with the Cedar River</ENT>
              <ENT>+8</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 150 feet upstream of Lane Avenue</ENT>
              <ENT>+11</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cedar River Tributary 13</ENT>
              <ENT>At the confluence with the Cedar River</ENT>
              <ENT>+8</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 100 feet upstream of Normandy Boulevard</ENT>
              <ENT>+29</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cedar River Tributary 14</ENT>
              <ENT>At the confluence with the Cedar River</ENT>
              <ENT>+14</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 900 feet upstream of the confluence with Cedar River Tributary 18</ENT>
              <ENT>+17</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cedar River Tributary 15</ENT>
              <ENT>At the confluence with Cedar River Tributary 14</ENT>
              <ENT>+17</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,300 feet upstream of the confluence with Cedar River Tributary 14</ENT>
              <ENT>+18</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cedar River Tributary 16</ENT>
              <ENT>At the confluence with the Cedar River</ENT>
              <ENT>+21</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 2,200 feet upstream of the confluence with the Cedar River</ENT>
              <ENT>+22</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cedar River Tributary 17</ENT>
              <ENT>At the confluence with the Cedar River</ENT>
              <ENT>+20</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 350 feet upstream of Beaver Street</ENT>
              <ENT>+25</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cedar River Tributary 19</ENT>
              <ENT>Approximately 700 feet upstream of the confluence with the Cedar River</ENT>
              <ENT>+12</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 250 feet upstream of Grace Terrace</ENT>
              <ENT>+12</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cedar Swamp Creek</ENT>
              <ENT>At the confluence with Pablo Creek</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 3,400 feet upstream of Huffman Boulevard</ENT>
              <ENT>+37</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cedar Swamp Creek Tributary 1</ENT>
              <ENT>At the confluence with Cedar Swamp Creek</ENT>
              <ENT>+29</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Beach Boulevard</ENT>
              <ENT>+33</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cedar Swamp Creek Tributary 2</ENT>
              <ENT>At the confluence with Cedar Swamp Creek</ENT>
              <ENT>+28</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the confluence with Pablo Creek Tributary 3</ENT>
              <ENT>+34</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Christopher Creek</ENT>
              <ENT>At the confluence with Christopher Creek Tributary 1</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet upstream of Old Saint Augustine Road</ENT>
              <ENT>+20</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Christopher Creek Tributary 1</ENT>
              <ENT>At the confluence with Christopher Creek</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet upstream of Dupont Avenue</ENT>
              <ENT>+11</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cormorant Branch</ENT>
              <ENT>Approximately 1,800 feet upstream of Julington Creek Road</ENT>
              <ENT>+4</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of Ricky Drive</ENT>
              <ENT>+17</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Craig Creek</ENT>
              <ENT>Just upstream of Hendricks Avenue</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of I-95</ENT>
              <ENT>+21</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Deep Bottom Creek</ENT>
              <ENT>Just upstream of Scott Mill Road</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Hampton Road</ENT>
              <ENT>+19</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Deep Bottom Creek Tributary 1</ENT>
              <ENT>At the confluence with Deep Bottom Creek</ENT>
              <ENT>+18</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Hartley Road</ENT>
              <ENT>+19</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Deer Creek</ENT>
              <ENT>Approximately 900 feet upstream of the Saint Johns River</ENT>
              <ENT>+4</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 4,400 feet upstream of the Saint Johns River</ENT>
              <ENT>+9</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Dunn Creek</ENT>
              <ENT>Approximately 3,600 feet upstream of the confluence with Rushing Branch</ENT>
              <ENT>+6</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of Bernard Road</ENT>
              <ENT>+22</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Dunn Creek Tributary 1</ENT>
              <ENT>At the confluence with Dunn Creek</ENT>
              <ENT>+8</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Shamrock Avenue</ENT>
              <ENT>+19</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Dunn Creek Tributary 2</ENT>
              <ENT>At the confluence with Dunn Creek</ENT>
              <ENT>+14</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10075"/>
              <ENT I="22"/>
              <ENT>Approximately 3,500 feet upstream of Webb Road</ENT>
              <ENT>+22</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Durbin Creek</ENT>
              <ENT>At the confluence with Julington Creek</ENT>
              <ENT>+4</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the St. Johns County boundary</ENT>
              <ENT>+9</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Durbin Creek Tributary 1</ENT>
              <ENT>At the confluence with Durbin Creek</ENT>
              <ENT>+7</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Philips Highway</ENT>
              <ENT>+19</ENT>
            </ROW>
            <ROW>
              <ENT I="01">East Branch</ENT>
              <ENT>Just upstream of Bessent Road</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 100 feet upstream of the confluence with East Branch Tributary 1</ENT>
              <ENT>+14</ENT>
            </ROW>
            <ROW>
              <ENT I="01">East Branch Tributary 1</ENT>
              <ENT>At the confluence with East Branch</ENT>
              <ENT>+14</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 60 feet upstream of Lem Turner Road</ENT>
              <ENT>+14</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Fishing Creek</ENT>
              <ENT>Just upstream of Timiquana Road</ENT>
              <ENT>+7</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,500 feet upstream of Jammes Road</ENT>
              <ENT>+21</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Fishing Creek Tributary 1</ENT>
              <ENT>At the confluence with Fishing Creek</ENT>
              <ENT>+8</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 300 feet upstream of 103rd Street</ENT>
              <ENT>+30</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ginhouse Creek</ENT>
              <ENT>Just upstream of Fort Caroline Road</ENT>
              <ENT>+6</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet downstream of Bradley Road</ENT>
              <ENT>+38</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Goodbys Creek</ENT>
              <ENT>Approximately 2,400 feet upstream of Sanchez Road</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 800 feet downstream of Praver Drive</ENT>
              <ENT>+16</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Goodbys Creek Tributary 1</ENT>
              <ENT>Approximately 1,000 feet downstream of Sunbeam Road</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 9,300 feet upstream of the confluence with Goodbys Creek</ENT>
              <ENT>+23</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Goodbys Creek Tributary 2</ENT>
              <ENT>Just downstream of the end of San Rae Road</ENT>
              <ENT>+4</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,750 feet upstream of Runnymeade Road</ENT>
              <ENT>+20</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Goodbys Creek Tributary 3</ENT>
              <ENT>At the confluence with Goodbys Creek</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 100 feet upstream of Philips Highway</ENT>
              <ENT>+22</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Goodbys Creek Tributary 4</ENT>
              <ENT>At the confluence with Goodbys Creek Tributary 2</ENT>
              <ENT>+17</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 3,200 feet upstream of the confluence with Goodbys Creek Tributary 2</ENT>
              <ENT>+21</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Goodbys Creek Tributary 5</ENT>
              <ENT>At the confluence with Goodbys Creek</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 2,000 feet upstream of the confluence with Goodbys Creek</ENT>
              <ENT>+5</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Greenfield Creek</ENT>
              <ENT>Approximately 350 feet downstream of Atlantic Boulevard</ENT>
              <ENT>+8</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,500 feet upstream of Hodges Boulevard</ENT>
              <ENT>+17</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gulley Branch</ENT>
              <ENT>At the confluence with the Trout River</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,650 feet upstream of Dunn Avenue</ENT>
              <ENT>+18</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Half Creek</ENT>
              <ENT>At the confluence with the Trout River</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 400 feet upstream of V.C. Johnson Road</ENT>
              <ENT>+17</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Half Creek Tributary 1</ENT>
              <ENT>At the confluence with Half Creek</ENT>
              <ENT>+13</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,000 feet upstream of V.C. Johnson Road</ENT>
              <ENT>+21</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Half Creek Tributary 2</ENT>
              <ENT>At the confluence with Half Creek</ENT>
              <ENT>+17</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 580 feet upstream of the confluence with Half Creek</ENT>
              <ENT>+18</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hogan Creek</ENT>
              <ENT>Just upstream of Bay Street</ENT>
              <ENT>+6</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,050 feet upstream of 11th Street</ENT>
              <ENT>+21</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hogpen Creek</ENT>
              <ENT>Just upstream of San Pablo Road</ENT>
              <ENT>+6</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,050 feet upstream of San Pablo Road</ENT>
              <ENT>+6</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hogpen Creek Tributary 1</ENT>
              <ENT>At the confluence with Hogpen Creek</ENT>
              <ENT>+6</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,350 feet upstream of Canyon Falls Drive</ENT>
              <ENT>+13</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10076"/>
              <ENT I="01">Hopkins Creek</ENT>
              <ENT>At the confluence with Pablo Creek</ENT>
              <ENT>+5</ENT>
              <ENT>City of Atlantic Beach, City of Neptune Beach.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,100 feet upstream of Cutlass Drive</ENT>
              <ENT>+7</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hopkins Creek Tributary 1</ENT>
              <ENT>At the confluence with Hopkins Creek Tributary 2</ENT>
              <ENT>+4</ENT>
              <ENT>City of Jacksonville Beach, City of Neptune Beach.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,700 feet upstream of the confluence with Hopkins Creek</ENT>
              <ENT>+4</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hopkins Creek Tributary 2</ENT>
              <ENT>At the confluence with Hopkins Creek</ENT>
              <ENT>+4</ENT>
              <ENT>City of Neptune Beach.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Bay Street</ENT>
              <ENT>+8</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hopkins Creek Tributary 3</ENT>
              <ENT>At the confluence with Hopkins Creek Tributary 2</ENT>
              <ENT>+6</ENT>
              <ENT>City of Jacksonville Beach, City of Neptune Beach.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of 15th Avenue</ENT>
              <ENT>+9</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Jones Creek</ENT>
              <ENT>Approximately 800 feet upstream of Monument Road</ENT>
              <ENT>+10</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the upstream confluence with Jones Creek Tributary 1</ENT>
              <ENT>+39</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Jones Creek Tributary 1</ENT>
              <ENT>At the downstream confluence with Jones Creek</ENT>
              <ENT>+23</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the upstream confluence with Jones Creek</ENT>
              <ENT>+39</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Jones Creek Tributary 2</ENT>
              <ENT>At the confluence with Jones Creek</ENT>
              <ENT>+4</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 150 feet upstream of State Route 9A</ENT>
              <ENT>+44</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Julington Creek</ENT>
              <ENT>Approximately 2,800 feet upstream of Julington Tributary 8</ENT>
              <ENT>+4</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of Hood Road</ENT>
              <ENT>+23</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Julington Creek Tributary 1</ENT>
              <ENT>At the confluence with Julington Creek</ENT>
              <ENT>+17</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Deer Creek Club Road</ENT>
              <ENT>+28</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Julington Creek Tributary 4</ENT>
              <ENT>At the confluence with Julington Creek</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet downstream of I-295</ENT>
              <ENT>+22</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Julington Creek Tributary 5</ENT>
              <ENT>At the confluence with Julington Creek</ENT>
              <ENT>+7</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 500 feet upstream of Greenland Oaks Drive</ENT>
              <ENT>+16</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Julington Creek Tributary 8</ENT>
              <ENT>At the confluence with Julington Creek</ENT>
              <ENT>+2</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 850 feet upstream of Julington Creek Road</ENT>
              <ENT>+18</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Cedar Creek</ENT>
              <ENT>Approximately 2,800 feet upstream of I-95</ENT>
              <ENT>+6</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of Owens Road</ENT>
              <ENT>+25</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Cedar Creek Tributary 1</ENT>
              <ENT>At the confluence with Little Cedar Creek</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 6,650 feet upstream of I-95</ENT>
              <ENT>+24</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Cedar Creek Tributary 2</ENT>
              <ENT>At the confluence with Little Cedar Creek</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 150 feet upstream of I-95</ENT>
              <ENT>+6</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Fishweir Creek</ENT>
              <ENT>Just upstream of St. Johns Avenue</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Roosevelt Boulevard</ENT>
              <ENT>+17</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Pottsburg Creek</ENT>
              <ENT>Just upstream of the Hart Expressway</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 600 feet upstream of I-95</ENT>
              <ENT>+19</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Pottsburg Creek Tributary 1</ENT>
              <ENT>At the confluence with Little Pottsburg Creek</ENT>
              <ENT>+10</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 600 feet upstream of Hickman Road</ENT>
              <ENT>+21</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Pottsburg Creek Tributary 2</ENT>
              <ENT>At the confluence with Little Pottsburg Creek</ENT>
              <ENT>+12</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet downstream of Spring Glen Road</ENT>
              <ENT>+20</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Pottsburg Creek Tributary 3</ENT>
              <ENT>At the confluence with Little Pottsburg Creek</ENT>
              <ENT>+12</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,250 feet upstream of the confluence with Little Pottsburg Creek</ENT>
              <ENT>+14</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Sixmile Creek</ENT>
              <ENT>At the confluence with the Ribault River</ENT>
              <ENT>+12</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 2,700 feet upstream of 5th Street</ENT>
              <ENT>+17</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Sixmile Creek Tributary 1</ENT>
              <ENT>At the confluence with Little Sixmile Creek</ENT>
              <ENT>+13</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of Shawland Road</ENT>
              <ENT>+15</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Sixmile Creek Tributary 2</ENT>
              <ENT>At the confluence with Little Sixmile Creek Tributary 1</ENT>
              <ENT>+15</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 750 feet upstream of Dahlia Road</ENT>
              <ENT>+18</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Sixmile Creek Tributary 3</ENT>
              <ENT>At the confluence with Sixmile Creek</ENT>
              <ENT>+13</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Lucoma Drive</ENT>
              <ENT>+13</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Trout River</ENT>
              <ENT>At the confluence with the Trout River</ENT>
              <ENT>+4</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,000 feet upstream of the confluence with Little Trout River Tributary 4</ENT>
              <ENT>+15</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10077"/>
              <ENT I="01">Little Trout River Tributary 4</ENT>
              <ENT>At the confluence with the Little Trout River</ENT>
              <ENT>+15</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,200 feet upstream of the confluence with the Little Trout River</ENT>
              <ENT>+15</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Trout River Tributary 6</ENT>
              <ENT>At the confluence with the Little Trout River</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 600 feet downstream of Plummer Road</ENT>
              <ENT>+13</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Trout River Tributary 10</ENT>
              <ENT>At the confluence with the Little Trout River</ENT>
              <ENT>+4</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 2,600 feet upstream of the confluence with the Little Trout River</ENT>
              <ENT>+9</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Long Branch</ENT>
              <ENT>Just upstream of Buffalo Avenue</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 400 feet upstream of Liberty Street</ENT>
              <ENT>+12</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Long Branch Tributary 1</ENT>
              <ENT>Approximately 400 feet upstream of Liberty Street</ENT>
              <ENT>+12</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,100 feet upstream of Liberty Street</ENT>
              <ENT>+14</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Magnolia Gardens Creek</ENT>
              <ENT>At the confluence with the Ribault River</ENT>
              <ENT>+2</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 300 feet upstream of Cleveland Road</ENT>
              <ENT>+19</ENT>
            </ROW>
            <ROW>
              <ENT I="01">McCoy Creek</ENT>
              <ENT>At the end of Oak Street</ENT>
              <ENT>+7</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of Commonwealth Avenue</ENT>
              <ENT>+20</ENT>
            </ROW>
            <ROW>
              <ENT I="01">McCoy Creek North Branch</ENT>
              <ENT>At the confluence with McCoy Creek</ENT>
              <ENT>+17</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of 3rd Street</ENT>
              <ENT>+20</ENT>
            </ROW>
            <ROW>
              <ENT I="01">McCoy Creek Southwest Branch</ENT>
              <ENT>At the confluence with McCoy Creek</ENT>
              <ENT>+12</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of College Street</ENT>
              <ENT>+17</ENT>
            </ROW>
            <ROW>
              <ENT I="01">McCoy Creek Tributary 5</ENT>
              <ENT>Just upstream of Roselle Road at the confluence with McCoy Creek Southwest Branch</ENT>
              <ENT>+14</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet upstream of Gilmore Street</ENT>
              <ENT>+15</ENT>
            </ROW>
            <ROW>
              <ENT I="01">McGirts Creek</ENT>
              <ENT>At the confluence with the Ortega River</ENT>
              <ENT>+58</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,000 feet upstream of Halsems Road</ENT>
              <ENT>+75</ENT>
            </ROW>
            <ROW>
              <ENT I="01">McGirts Creek Tributary 11</ENT>
              <ENT>At the confluence with McGirts Creek</ENT>
              <ENT>+60</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.3 mile upstream of the confluence with McGirts Creek</ENT>
              <ENT>+74</ENT>
            </ROW>
            <ROW>
              <ENT I="01">McGirts Creek Tributary 12</ENT>
              <ENT>At the confluence with McGirts Creek</ENT>
              <ENT>+63</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,200 feet upstream of William Avenue</ENT>
              <ENT>+80</ENT>
            </ROW>
            <ROW>
              <ENT I="01">McGirts Creek Tributary 14</ENT>
              <ENT>At the confluence with McGirts Creek</ENT>
              <ENT>+59</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,750 feet upstream of Joes Road</ENT>
              <ENT>+79</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Mill Dam Branch</ENT>
              <ENT>At the confluence with Pablo Creek</ENT>
              <ENT>+21</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 3,750 feet upstream of Leaby Road</ENT>
              <ENT>+43</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Mill Dam Branch Canal</ENT>
              <ENT>At the confluence with Mill Dam Branch</ENT>
              <ENT>+27</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 100 feet upstream of Gate Parkway</ENT>
              <ENT>+34</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Mill Dam Branch Tributary 3</ENT>
              <ENT>At the confluence with Mill Dam Branch</ENT>
              <ENT>+38</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 100 feet upstream of Beach Boulevard</ENT>
              <ENT>+38</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Mill Dam Branch Tributary 4</ENT>
              <ENT>At the confluence with Mill Dam Branch</ENT>
              <ENT>+38</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet upstream of Anniston Road</ENT>
              <ENT>+41</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Mill Dam Branch Tributary 5</ENT>
              <ENT>At the confluence with Mill Dam Branch at Lantana Lakes Drive</ENT>
              <ENT>+41</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of Forest Boulevard</ENT>
              <ENT>+45</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Miller Creek</ENT>
              <ENT>At the confluence with the Saint Johns River</ENT>
              <ENT>+6</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 400 feet upstream of Camden Avenue</ENT>
              <ENT>+18</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Miller Creek Tributary 1</ENT>
              <ENT>At the confluence with Miller Creek</ENT>
              <ENT>+16</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Stillman Street</ENT>
              <ENT>+16</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Miramar Tributary</ENT>
              <ENT>At the confluence with the Saint Johns River</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,200 feet upstream of Orlando Circle West</ENT>
              <ENT>+13</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Moncrief Creek</ENT>
              <ENT>At the confluence with the Trout River</ENT>
              <ENT>+2</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 250 feet upstream of 9th Street</ENT>
              <ENT>+21</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Moncrief Creek Tributary 4</ENT>
              <ENT>At the confluence with Moncrief Creek</ENT>
              <ENT>+17</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 250 feet upstream of Spring Grove Avenue</ENT>
              <ENT>+19</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10078"/>
              <ENT I="01">Mount Pleasant Creek</ENT>
              <ENT>Approximately 3,400 feet upstream of Ashley Melisse Boulevard</ENT>
              <ENT>+7</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of General Doolittle Drive</ENT>
              <ENT>+36</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Mount Pleasant Creek Tributary 3</ENT>
              <ENT>At the confluence with Tiger Pond Creek</ENT>
              <ENT>+6</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 2,050 feet upstream of Ashley Melisse Boulevard</ENT>
              <ENT>+26</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Mount Pleasant Creek Tributary 4</ENT>
              <ENT>Approximately 1,150 feet upstream of Blue Eagle Way</ENT>
              <ENT>+23</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the confluence with Mount Pleasant Creek</ENT>
              <ENT>+26</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Mount Pleasant Creek Tributary 6</ENT>
              <ENT>At the confluence with Mount Pleasant Creek</ENT>
              <ENT>+27</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Running River Road</ENT>
              <ENT>+35</ENT>
            </ROW>
            <ROW>
              <ENT I="01">New Rose Creek</ENT>
              <ENT>At the confluence with the Saint Johns River</ENT>
              <ENT>+7</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of Saint Augustine Road</ENT>
              <ENT>+21</ENT>
            </ROW>
            <ROW>
              <ENT I="01">New Rose Creek Tributary 1</ENT>
              <ENT>At the confluence with New Rose Creek</ENT>
              <ENT>+6</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 100 feet upstream of Grant Road</ENT>
              <ENT>+22</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Newcastle Creek</ENT>
              <ENT>At the confluence with the Saint Johns River</ENT>
              <ENT>+7</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 200 feet downstream of Greenfern Lane</ENT>
              <ENT>+27</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Newcastle Creek Tributary 1</ENT>
              <ENT>At the confluence with Newcastle Creek</ENT>
              <ENT>+14</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 700 feet upstream of the confluence with Newcastle Creek</ENT>
              <ENT>+18</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ninemile Creek</ENT>
              <ENT>At the confluence with the Trout River</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,250 feet upstream of Smalley Road</ENT>
              <ENT>+22</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ninemile Creek Tributary 1</ENT>
              <ENT>At the confluence with Ninemile Creek</ENT>
              <ENT>+10</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,600 feet upstream of Old Kings Road</ENT>
              <ENT>+14</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ninemile Creek Tributary 2</ENT>
              <ENT>At the confluence with Ninemile Creek</ENT>
              <ENT>+20</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,500 feet upstream of the railroad</ENT>
              <ENT>+21</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ninemile Creek Tributary 6</ENT>
              <ENT>At the confluence with Ninemile Creek</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 2,100 feet upstream of Old Kings Road</ENT>
              <ENT>+22</ENT>
            </ROW>
            <ROW>
              <ENT I="01">North Fork Sixmile Creek</ENT>
              <ENT>At the confluence with Sixmile Creek</ENT>
              <ENT>+20</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 3,300 feet upstream of Fish Road west</ENT>
              <ENT>+75</ENT>
            </ROW>
            <ROW>
              <ENT I="01">North Fork Sixmile Creek Tributary 1</ENT>
              <ENT>At the confluence with North Fork Sixmile Creek</ENT>
              <ENT>+21</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 3,600 feet upstream of Bulls Bay Highway</ENT>
              <ENT>+23</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Oldfield Creek</ENT>
              <ENT>Approximately 400 feet upstream of the confluence with Oldfield Tributary 4</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the confluence with Oldfield Creek Tributary 7</ENT>
              <ENT>+26</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Oldfield Creek Tributary 1</ENT>
              <ENT>Approximately 1,000 feet downstream of Old Saint Augustine Road</ENT>
              <ENT>+11</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 100 feet downstream of I-295</ENT>
              <ENT>+22</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Oldfield Creek Tributary 2</ENT>
              <ENT>At the confluence with Oldfield Creek</ENT>
              <ENT>+16</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet upstream of Old Saint Augustine Road</ENT>
              <ENT>+19</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Oldfield Creek Tributary 3</ENT>
              <ENT>At the confluence with Oldfield Creek</ENT>
              <ENT>+23</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 2,250 feet upstream of the confluence with Oldfield Creek</ENT>
              <ENT>+25</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Oldfield Creek Tributary 4</ENT>
              <ENT>At the confluence with Oldfield Creek</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 25 feet upstream of Hood Landing Road</ENT>
              <ENT>+25</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Oldfield Creek Tributary 7</ENT>
              <ENT>Approximately 450 feet upstream of Knottingby Drive</ENT>
              <ENT>+26</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the confluence with Oldfield Creek</ENT>
              <ENT>+26</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Open Creek</ENT>
              <ENT>Approximately 2,000 feet upstream of the confluence with Open Creek Tributary 1</ENT>
              <ENT>+8</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,900 feet upstream of Open Creek Tributary 4</ENT>
              <ENT>+23</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Open Creek Tributary 1</ENT>
              <ENT>Approximately 2,200 feet upstream of Crosswater Boulevard</ENT>
              <ENT>+10</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 4,700 feet upstream of Crosswater Boulevard</ENT>
              <ENT>+19</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Open Creek Tributary 2</ENT>
              <ENT>At the confluence with Open Creek</ENT>
              <ENT>+13</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10079"/>
              <ENT I="22"/>
              <ENT>Approximately 200 feet upstream of Wm. Davis Parkway</ENT>
              <ENT>+22</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Open Creek Tributary 3</ENT>
              <ENT>At the confluence with Open Creek</ENT>
              <ENT>+4</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,450 feet upstream of San Pablo Parkway</ENT>
              <ENT>+14</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Open Creek Tributary 4</ENT>
              <ENT>At the confluence with Open Creek</ENT>
              <ENT>+23</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,300 feet upstream of Highland Glen Way</ENT>
              <ENT>+30</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ortega River</ENT>
              <ENT>Approximately 2,000 feet downstream of Collins Road</ENT>
              <ENT>+4</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 5,400 feet upstream of Normandy Boulevard at the confluence with McGirts Creek</ENT>
              <ENT>+58</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ortega River Tributary 1</ENT>
              <ENT>At the confluence with the Ortega River</ENT>
              <ENT>+4</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Jubal Lane</ENT>
              <ENT>+20</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ortega River Tributary 2</ENT>
              <ENT>At the confluence with the Ortega River</ENT>
              <ENT>+39</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 900 feet upstream of Old Middleburg Road</ENT>
              <ENT>+68</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ortega River Tributary 3</ENT>
              <ENT>At the confluence with the Ortega River</ENT>
              <ENT>+34</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 250 feet upstream of Steamboat Springs Drive</ENT>
              <ENT>+85</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ortega River Tributary 4</ENT>
              <ENT>At the confluence with the Ortega River</ENT>
              <ENT>+28</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Connie Jean Road</ENT>
              <ENT>+71</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ortega River Tributary 5</ENT>
              <ENT>At the confluence with the Ortega River</ENT>
              <ENT>+20</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of I-295</ENT>
              <ENT>+25</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ortega River Tributary 6</ENT>
              <ENT>Approximately 1,600 feet upstream of Argyle Forest Boulevard</ENT>
              <ENT>+8</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of I-295</ENT>
              <ENT>+21</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ortega River Tributary 7</ENT>
              <ENT>Approximately 600 feet upstream of Argyle Forest Boulevard</ENT>
              <ENT>+8</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of I-295</ENT>
              <ENT>+18</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ortega River Tributary 10</ENT>
              <ENT>At the confluence with the Ortega River</ENT>
              <ENT>+22</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,000 feet upstream of Brett Forest Drive</ENT>
              <ENT>+67</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ortega River Tributary 11</ENT>
              <ENT>At the confluence with the Ortega River</ENT>
              <ENT>+20</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 20 feet downstream of Collins Road</ENT>
              <ENT>+40</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Pablo Creek</ENT>
              <ENT>Approximately 2,500 feet upstream of the Duval County line</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the confluence with Sawmill Slough/Buckhead Branch</ENT>
              <ENT>+22</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Pablo Creek Tributary 1</ENT>
              <ENT>At the confluence with Pablo Creek</ENT>
              <ENT>+11</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet downstream of J. Turner Butler Boulevard</ENT>
              <ENT>+35</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Pablo Creek Tributary 2</ENT>
              <ENT>At the confluence with Pablo Creek</ENT>
              <ENT>+12</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 6,300 feet upstream of Kernan Boulevard</ENT>
              <ENT>+36</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Pablo Creek Tributary 3</ENT>
              <ENT>At the confluence with Pablo Creek Tributary 2</ENT>
              <ENT>+22</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 6,000 feet upstream of the confluence with Cedar Swamp Creek Tributary 2</ENT>
              <ENT>+34</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Pickett Branch</ENT>
              <ENT>At the confluence with Cedar Creek</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Yankee Clipper Drive</ENT>
              <ENT>+21</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Pickett Branch Tributary 3</ENT>
              <ENT>At the confluence with Pickett Branch</ENT>
              <ENT>+19</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of Pecan Park Road</ENT>
              <ENT>+21</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Pickett Branch Tributary 4</ENT>
              <ENT>At the confluence with Pickett Branch</ENT>
              <ENT>+20</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Pecan Park Road</ENT>
              <ENT>+20</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Pickett Branch Tributary 5</ENT>
              <ENT>At the confluence with Pickett Branch</ENT>
              <ENT>+21</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of Pecan Park Road</ENT>
              <ENT>+21</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Pottsburg Creek</ENT>
              <ENT>Approximately 1 mile downstream of Beach Boulevard</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of Baymeadows Road</ENT>
              <ENT>+17</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Pottsburg Creek Tributary 5</ENT>
              <ENT>At the confluence with Pottsburg Creek</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 300 feet upstream of Spring Park Road</ENT>
              <ENT>+20</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Puckett Creek</ENT>
              <ENT>Approximately 100 feet upstream of State Route A1A</ENT>
              <ENT>+6</ENT>
              <ENT>City of Atlantic Beach, City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10080"/>
              <ENT I="22"/>
              <ENT>Approximately 1,050 feet upstream of Fairway Villas Drive</ENT>
              <ENT>+7</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Red Bay Branch</ENT>
              <ENT>Approximately 700 feet downstream of Arlington Expressway</ENT>
              <ENT>+8</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 4,100 feet upstream of Lone Star Road</ENT>
              <ENT>+22</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Red Bay Branch Tributary 1</ENT>
              <ENT>At the confluence with Red Bay Branch</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Lone Star Road</ENT>
              <ENT>+13</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ribault River</ENT>
              <ENT>Approximately 3,000 feet downstream of Howell Drive</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the confluence with Sixmile Creek</ENT>
              <ENT>+12</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ribault River Tributary 2</ENT>
              <ENT>At the confluence with Ribault Creek</ENT>
              <ENT>+11</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 70 feet downstream of Edgewood Drive</ENT>
              <ENT>+11</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ribault River Tributary 5</ENT>
              <ENT>At the confluence with Ribault Creek</ENT>
              <ENT>+11</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 2,200 feet upstream of the confluence with Ribault Creek</ENT>
              <ENT>+11</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ribault River Tributary 8</ENT>
              <ENT>At the confluence with Ribault Creek</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,600 feet upstream of Clyde Drive</ENT>
              <ENT>+11</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ribault River Tributary 9</ENT>
              <ENT>At the confluence with Ribault Creek</ENT>
              <ENT>+11</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 300 feet upstream of West Virginia Avenue</ENT>
              <ENT>+11</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Rowell Creek</ENT>
              <ENT>At the confluence with Sal Taylor Creek</ENT>
              <ENT>+52</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.51 mile upstream of the intersection of Inspiration Avenue and D Avenue</ENT>
              <ENT>+80</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Rowell Creek Tributary 2</ENT>
              <ENT>At the confluence with Rowell Creek</ENT>
              <ENT>+78</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 3,700 feet upstream of New World Avenue</ENT>
              <ENT>+82</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Rushing Branch</ENT>
              <ENT>Approximately 1,800 feet upstream of Yellow Bluff Road</ENT>
              <ENT>+6</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of Cedar Point Road</ENT>
              <ENT>+19</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Rushing Branch Tributary 1</ENT>
              <ENT>At the confluence with Rushing Branch</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of New Berlin Road</ENT>
              <ENT>+13</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sal Taylor Creek</ENT>
              <ENT>Approximately 3,700 feet upstream of the confluence with Yellow Water Creek</ENT>
              <ENT>+50</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the confluence with Rowell Creek Tributary 1 approximately 2,800 feet east of Aviation Avenue</ENT>
              <ENT>+76</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sal Taylor Creek Tributary 2</ENT>
              <ENT>At the confluence with Sal Taylor Creek</ENT>
              <ENT>+62</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,500 feet upstream of the confluence with Sal Taylor Creek Tributary 3</ENT>
              <ENT>+68</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sal Taylor Creek Tributary 3</ENT>
              <ENT>At the confluence with Sal Taylor Creek Tributary 2</ENT>
              <ENT>+66</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 3,400 feet upstream of the confluence with Sal Taylor Creek Tributary 2</ENT>
              <ENT>+70</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sal Taylor Creek Tributary 4</ENT>
              <ENT>At the confluence with Sal Taylor Creek</ENT>
              <ENT>+69</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 800 feet upstream of 103rd Street</ENT>
              <ENT>+80</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sandalwood Canal</ENT>
              <ENT>Approximately 1,100 feet upstream of San Pablo Road</ENT>
              <ENT>+6</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 2 miles upstream of Kernan Boulevard</ENT>
              <ENT>+35</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sawmill Slough/Buckhead Branch</ENT>
              <ENT>At the confluence with Pablo Creek</ENT>
              <ENT>+23</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 2,300 feet upstream of J. Turner Butler Boulevard</ENT>
              <ENT>+29</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sawmill Slough/Buckhead Branch Tributary 1</ENT>
              <ENT>At the confluence with Sawmill Slough/Buckhead Branch</ENT>
              <ENT>+25</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,200 feet upstream of J. Turner Butler Boulevard</ENT>
              <ENT>+27</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sawmill Slough/Buckhead Branch Tributary 2</ENT>
              <ENT>At the confluence with Sawmill Slough/Buckhead Branch</ENT>
              <ENT>+34</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 550 feet upstream of the confluence with Sawmill Slough/Buckhead Branch</ENT>
              <ENT>+34</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Seaton Creek</ENT>
              <ENT>At the confluence with Thomas Creek</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the confluence with Seaton Creek Tributary 2</ENT>
              <ENT>+13</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Seaton Creek Tributary 1</ENT>
              <ENT>At the confluence with Seaton Creek</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10081"/>
              <ENT I="22"/>
              <ENT>Approximately 2 miles upstream of Arnold Road</ENT>
              <ENT>+17</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Seaton Creek Tributary 2</ENT>
              <ENT>At the confluence with Seaton Creek</ENT>
              <ENT>+13</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of Arnold Road</ENT>
              <ENT>+18</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Second Puncheon Branch</ENT>
              <ENT>At the confluence with Pablo Creek</ENT>
              <ENT>+21</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Beach Boulevard</ENT>
              <ENT>+44</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Second Puncheon Branch Tributary 1</ENT>
              <ENT>At the confluence with Second Puncheon Branch</ENT>
              <ENT>+27</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 100 feet downstream of Point Meadows Drive</ENT>
              <ENT>+34</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Second Puncheon Branch Tributary 3</ENT>
              <ENT>At the confluence with Second Puncheon Branch</ENT>
              <ENT>+31</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Courtyards Lane</ENT>
              <ENT>+40</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Second Puncheon Branch Tributary 4</ENT>
              <ENT>At the confluence with Second Puncheon Branch</ENT>
              <ENT>+32</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 2,000 feet upstream of the confluence with Second Puncheon Branch</ENT>
              <ENT>+39</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Second Puncheon Branch Tributary 5</ENT>
              <ENT>At the confluence with Second Puncheon Branch</ENT>
              <ENT>+42</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of Gate Parkway</ENT>
              <ENT>+45</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Second Puncheon Branch Tributary 6</ENT>
              <ENT>At the confluence with Second Puncheon Branch</ENT>
              <ENT>+43</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,400 feet upstream of the confluence with Second Puncheon Branch</ENT>
              <ENT>+50</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sherman Creek</ENT>
              <ENT>Just downstream of Pioneer Drive</ENT>
              <ENT>+6</ENT>
              <ENT>City of Atlantic Beach, City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 100 feet upstream of Seminole Road</ENT>
              <ENT>+7</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sherman Creek Canal</ENT>
              <ENT>At the confluence with Sherman Creek</ENT>
              <ENT>+6</ENT>
              <ENT>City of Atlantic Beach, City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Fleet Landing Boulevard</ENT>
              <ENT>+7</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Silversmith Creek</ENT>
              <ENT>At the confluence with Pottsburg Creek</ENT>
              <ENT>+4</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 2,250 feet upstream of Silversmith Tributary 1</ENT>
              <ENT>+20</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Silversmith Creek Tributary 1</ENT>
              <ENT>At the confluence with Silversmith Creek</ENT>
              <ENT>+13</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet upstream of Century 21 Drive</ENT>
              <ENT>+24</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sixmile Creek</ENT>
              <ENT>At the confluence with the Ribault River</ENT>
              <ENT>+12</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 3,100 feet upstream of Commonwealth Avenue</ENT>
              <ENT>+68</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sixmile Creek Tributary 6</ENT>
              <ENT>At the confluence with Sixmile Creek</ENT>
              <ENT>+34</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 3,000 feet upstream of railroad</ENT>
              <ENT>+56</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sixmile Creek Tributary 9</ENT>
              <ENT>At the confluence with Sixmile Creek</ENT>
              <ENT>+17</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Pritchard Road</ENT>
              <ENT>+17</ENT>
            </ROW>
            <ROW>
              <ENT I="01">St. Mary's River Tributary</ENT>
              <ENT>Just upstream of Beaver Street</ENT>
              <ENT>+81</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 3,700 feet upstream of I-10</ENT>
              <ENT>+82</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Strawberry Creek</ENT>
              <ENT>Approximately 2,400 feet upstream of the confluence with Pottsburg Creek</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet downstream of Merril Road</ENT>
              <ENT>+35</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek</ENT>
              <ENT>At the confluence with Julington Creek</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 2,300 feet upstream of Vineyard Lake Road North</ENT>
              <ENT>+29</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Tacito Creek</ENT>
              <ENT>Approximately 2,000 feet upstream of Scott Mill Road</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 3,300 feet upstream of Scott Mill Road</ENT>
              <ENT>+8</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Tiger Hole Swamp</ENT>
              <ENT>At the confluence with Pottsburg Creek</ENT>
              <ENT>+14</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,650 feet upstream of J. Turner Butler Boulevard</ENT>
              <ENT>+23</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Tiger Pond Creek</ENT>
              <ENT>At the confluence with Mt. Pleasant Creek</ENT>
              <ENT>+3</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,600 feet upstream of McCormick Road</ENT>
              <ENT>+28</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Tiger Pond Creek Tributary 1</ENT>
              <ENT>At the confluence with Tiger Pond Creek</ENT>
              <ENT>+14</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 300 feet upstream of Kernan Forest Boulevard</ENT>
              <ENT>+20</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Tributary 1 to Miramar Tributary</ENT>
              <ENT>At the confluence with Miramar Tributary</ENT>
              <ENT>+8</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10082"/>
              <ENT I="22"/>
              <ENT>Approximately 1,000 feet upstream of Greenridge Road</ENT>
              <ENT>+11</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Tributary to Little Sixmile Creek Tributary 1</ENT>
              <ENT>At the confluence with Little Sixmile Creek Tributary 1</ENT>
              <ENT>+15</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Edgewood Avenue</ENT>
              <ENT>+19</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Tributary to Ortega River Tributary 1</ENT>
              <ENT>At the confluence with Ortega River Tributary 1</ENT>
              <ENT>+4</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Ovella Road</ENT>
              <ENT>+10</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Trout River</ENT>
              <ENT>Approximately 2,000 feet upstream of New Kings Road</ENT>
              <ENT>+6</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Cisco Gardens Road</ENT>
              <ENT>+61</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Trout River Tributary 2</ENT>
              <ENT>At the confluence with the Trout River</ENT>
              <ENT>+21</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,200 feet upstream of Jones Road</ENT>
              <ENT>+52</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Trout River Tributary 3</ENT>
              <ENT>At the confluence with the Trout River</ENT>
              <ENT>+13</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 100 feet upstream of the Norfolk Southern Railway</ENT>
              <ENT>+19</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Trout River Tributary 7</ENT>
              <ENT>At the confluence with Trout River Tributary 2</ENT>
              <ENT>+32</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Jones Road</ENT>
              <ENT>+49</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Trout River Tributary 8</ENT>
              <ENT>At the confluence with the Trout River and Trout River Tributary 9</ENT>
              <ENT>+39</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,600 feet upstream of Pines Plantation Road</ENT>
              <ENT>+55</ENT>
            </ROW>
            <ROW>
              <ENT I="01">West Branch</ENT>
              <ENT>Just downstream of Bessent Road</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,200 feet upstream of Dunn Avenue</ENT>
              <ENT>+12</ENT>
            </ROW>
            <ROW>
              <ENT I="01">West Branch Tributary 1</ENT>
              <ENT>At the confluence with West Branch</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 500 feet upstream of North Campus Boulevard</ENT>
              <ENT>+18</ENT>
            </ROW>
            <ROW>
              <ENT I="01">West Branch Tributary 2</ENT>
              <ENT>At the confluence with West Branch</ENT>
              <ENT>+11</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet upstream of Dunn Avenue</ENT>
              <ENT>+11</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Williamson Creek</ENT>
              <ENT>At the confluence with the Cedar River</ENT>
              <ENT>+5</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Wilson Boulevard</ENT>
              <ENT>+25</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Williamson Creek Tributary 3</ENT>
              <ENT>At the confluence with Williamson Creek</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Wilson Boulevard</ENT>
              <ENT>+25</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Williamson Creek Tributary 4</ENT>
              <ENT>At the confluence with Williamson Creek</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet downstream of Lucente Road</ENT>
              <ENT>+23</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Wills Branch</ENT>
              <ENT>At the confluence with the Cedar River</ENT>
              <ENT>+7</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 400 feet upstream of Ramona Boulevard</ENT>
              <ENT>+62</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Wills Branch Tributary 1</ENT>
              <ENT>At the confluence with Wills Branch</ENT>
              <ENT>+9</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of Frank H. Peterson Academy Road</ENT>
              <ENT>+64</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Wills Branch Tributary 2</ENT>
              <ENT>At the confluence with Wills Branch Tributary 1</ENT>
              <ENT>+34</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,400 feet upstream of Fouraker Road</ENT>
              <ENT>+47</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Wills Branch Tributary 3</ENT>
              <ENT>At the confluence with Wills Branch</ENT>
              <ENT>+23</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just downstream of I-10</ENT>
              <ENT>+82</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Wills Branch Tributary 4</ENT>
              <ENT>At the confluence with Wills Branch Tributary 3</ENT>
              <ENT>+50</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,600 feet upstream of Herlong Road</ENT>
              <ENT>+77</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Wills Branch Tributary 5</ENT>
              <ENT>At the confluence with Wills Branch Tributary 1</ENT>
              <ENT>+10</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet downstream of Dayton Road</ENT>
              <ENT>+25</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Wills Branch Tributary 6</ENT>
              <ENT>At the confluence with Wills Branch Tributary 1</ENT>
              <ENT>+17</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 50 feet upstream of Spring Branch Drive</ENT>
              <ENT>+50</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Yellow Water Creek Tributary 1</ENT>
              <ENT>Just upstream of Bicentennial Drive</ENT>
              <ENT>+62</ENT>
              <ENT>City of Jacksonville.</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22"/>
              <ENT>Approximately 5,200 feet upstream of Bicentennial Drive</ENT>
              <ENT>+78</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">* National Geodetic Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">+ North American Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"># Depth in feet above ground.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">⁁ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10083"/>
              <ENT I="21">
                <E T="02">ADDRESSES</E>
              </ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">City of Atlantic Beach</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the City Building, 800 Seminole Road, Atlantic Beach, FL 32233.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">City of Jacksonville</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at City Hall, 117 West Duval Street, Jacksonville, FL 32202.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">City of Jacksonville Beach</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at City Hall, 11 North 3rd Street, Jacksonville Beach, FL 32250.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">City of Neptune Beach</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22">Maps are available for inspection at City Hall, 116 1st Street, Neptune Beach, FL 32266.</ENT>
            </ROW>
            <ROW>
              <ENT I="21">
                <E T="02">Pennington County, South Dakota, and Incorporated Areas</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="21">
                <E T="02">Docket No.: FEMA-B-1197</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Arrowhead Creek</ENT>
              <ENT>At the Rapid Creek confluence</ENT>
              <ENT>+3318</ENT>
              <ENT>City of Rapid City.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 408 feet upstream of Summerset Drive</ENT>
              <ENT>+3490</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Box Elder Creek through Box Elder</ENT>
              <ENT>Approximately 0.8 mile downstream of 151st Avenue</ENT>
              <ENT>+2994</ENT>
              <ENT>City of Box Elder, Unincorporated Areas of Pennington County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the downstream side of 146th Avenue (Bennett Road)</ENT>
              <ENT>+3085</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Box Elder Creek through Box Elder Overflow</ENT>
              <ENT>At the Box Elder Creek confluence</ENT>
              <ENT>+3039</ENT>
              <ENT>City of Box Elder, Unincorporated Areas of Pennington County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the Box Elder Creek divergence</ENT>
              <ENT>+3082</ENT>
            </ROW>
            <ROW>
              <ENT I="01">East Tributary to Box Elder Creek</ENT>
              <ENT>At the North Tributary to Box Elder Creek confluence</ENT>
              <ENT>+2998</ENT>
              <ENT>City of Box Elder, Unincorporated Areas of Pennington County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 515 feet upstream of G Avenue</ENT>
              <ENT>+3168</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ellsworth AFB Alert Apron Drainage</ENT>
              <ENT>At the Box Elder Creek through Box Elder Overflow confluence</ENT>
              <ENT>+3056</ENT>
              <ENT>City of Box Elder, Unincorporated Areas of Pennington County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.0 mile upstream of Kenney Road</ENT>
              <ENT>+3186</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ellsworth AFB West Drainage Basin</ENT>
              <ENT>At the Box Elder Creek through Box Elder Overflow confluence</ENT>
              <ENT>+3071</ENT>
              <ENT>City of Box Elder, Unincorporated Areas of Pennington County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the downstream side of 225th Street</ENT>
              <ENT>+3156</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Haines Avenue Drainage Basin</ENT>
              <ENT>At the Rapid Creek confluence</ENT>
              <ENT>+3213</ENT>
              <ENT>City of Rapid City.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 340 feet upstream of Curtis Street</ENT>
              <ENT>+3285</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Meade-Hawthorne Drainage Basin</ENT>
              <ENT>At the Rapid Creek confluence</ENT>
              <ENT>+3141</ENT>
              <ENT>City of Rapid City.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the downstream side of Saint Anne Street</ENT>
              <ENT>+3236</ENT>
            </ROW>
            <ROW>
              <ENT I="01">North Tributary to Box Elder Creek</ENT>
              <ENT>At the Box Elder Creek confluence</ENT>
              <ENT>+2994</ENT>
              <ENT>City of Box Elder, Unincorporated Areas of Pennington County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 540 feet upstream of 225th Street</ENT>
              <ENT>+3117</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Northwest Tributary to Box Elder Creek</ENT>
              <ENT>At the North Tributary to Box Elder Creek confluence</ENT>
              <ENT>+3045</ENT>
              <ENT>City of Box Elder, Unincorporated Areas of Pennington County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 280 feet upstream of 225th Street</ENT>
              <ENT>+3255</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Rapid Creek through Silver City</ENT>
              <ENT>At the Pactola Reservoir confluence</ENT>
              <ENT>+4593</ENT>
              <ENT>Unincorporated Areas of Pennington County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 2.7 miles upstream of the Pactola Reservoir confluence</ENT>
              <ENT>+4667</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Red Rock Canyon</ENT>
              <ENT>At the Rapid Creek confluence</ENT>
              <ENT>+3375</ENT>
              <ENT>City of Rapid City, Unincorporated Areas of Pennington County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.0 mile upstream of Red Rock Canyon Road</ENT>
              <ENT>+3545</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Robinsdale Drain</ENT>
              <ENT>At the Southeast Drainage Basin confluence</ENT>
              <ENT>+3172</ENT>
              <ENT>City of Rapid City.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 220 feet upstream of 5th Street</ENT>
              <ENT>+3340</ENT>
            </ROW>
            <ROW>
              <ENT I="01">South Canyon Creek</ENT>
              <ENT>At the Lime Creek confluence</ENT>
              <ENT>+3334</ENT>
              <ENT>City of Rapid City, Unincorporated Areas of Pennington County.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10084"/>
              <ENT I="22"/>
              <ENT>Approximately 1,030 feet upstream of Nemo Road</ENT>
              <ENT>+3571</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Southeast Drainage Basin</ENT>
              <ENT>At the Rapid Creek confluence</ENT>
              <ENT>+3133</ENT>
              <ENT>City of Rapid City, Unincorporated Areas of Pennington County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,180 feet upstream of Old Folsom Road</ENT>
              <ENT>+3223</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Tributary 1 to East Tributary to Box Elder Creek</ENT>
              <ENT>At the East Tributary to Box Elder Creek confluence</ENT>
              <ENT>+3077</ENT>
              <ENT>City of Box Elder.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.5 mile upstream of the East Tributary to Box Elder Creek confluence</ENT>
              <ENT>+3153</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Truck Bypass</ENT>
              <ENT>At the Southeast Drainage Basin confluence</ENT>
              <ENT>+3213</ENT>
              <ENT>City of Rapid City, Unincorporated Areas of Pennington County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,870 feet upstream of State Highway 16</ENT>
              <ENT>+3310</ENT>
            </ROW>
            <ROW>
              <ENT I="01">West Tributary to Box Elder Creek</ENT>
              <ENT>At the East Tributary to Box Elder Creek confluence</ENT>
              <ENT>+3025</ENT>
              <ENT>City of Box Elder, Unincorporated Areas of Pennington County.</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22"/>
              <ENT>Approximately 700 feet upstream of Kenney Road</ENT>
              <ENT>+3130</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">* National Geodetic Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">+ North American Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"># Depth in feet above ground.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">⁁ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
            </ROW>
            <ROW>
              <ENT I="21">
                <E T="02">ADDRESSES</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">
                <E T="02">City of Box Elder</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at 520 North Ellsworth Road, Suite 9C, Box Elder, SD 57719.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">City of Rapid City</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at 300 6th Street, Rapid City, SD 57701.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">Unincorporated Areas of Pennington County</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22">Maps are available for inspection at 832 Saint Joseph Street, Rapid City, SD 57701.</ENT>
            </ROW>
            <ROW>
              <ENT I="21">
                <E T="02">Ellis County, Texas, and Incorporated Areas</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="21">
                <E T="02">Docket No.: FEMA-B-1140</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Armstrong Creek</ENT>
              <ENT>Approximately 100 feet downstream of Waterworks Road</ENT>
              <ENT>+740</ENT>
              <ENT>Unincorporated Areas of Ellis County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,040 feet upstream of Waterworks Road</ENT>
              <ENT>+746</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Bedford Branch</ENT>
              <ENT>Approximately 0.5 mile downstream of Southern Pacific Railroad</ENT>
              <ENT>+538</ENT>
              <ENT>City of Grand Prairie, Unincorporated Areas of Ellis County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 275 feet upstream of Southern Pacific Railroad</ENT>
              <ENT>+567</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cottonwood Creek</ENT>
              <ENT>Approximately 0.74 mile upstream of Old Fort Worth Road</ENT>
              <ENT>+574</ENT>
              <ENT>City of Grand Prairie, Unincorporated Areas of Ellis County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the confluence with Newton Branch</ENT>
              <ENT>+584</ENT>
            </ROW>
            <ROW>
              <ENT I="01">East Fork to Soap Creek</ENT>
              <ENT>At the confluence with Soap Creek</ENT>
              <ENT>+594</ENT>
              <ENT>City of Midlothian, Unincorporated Areas of Ellis County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Just upstream of Weatherford Road</ENT>
              <ENT>+616</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hollings Branch</ENT>
              <ENT>Approximately 0.66 mile downstream of Magic Valley Lane</ENT>
              <ENT>+641</ENT>
              <ENT>City of Cedar Hill.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 725 feet downstream of Magic Valley Lane</ENT>
              <ENT>+659</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Joe Pool Lake</ENT>
              <ENT>Approximately 0.48 mile downstream of Southern Pacific Railroad</ENT>
              <ENT>+538</ENT>
              <ENT>City of Grand Prairie, Unincorporated Areas of Ellis County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.37 mile upstream of FM 661</ENT>
              <ENT>+540</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Newton Branch</ENT>
              <ENT>At the confluence with Soap Creek</ENT>
              <ENT>+550</ENT>
              <ENT>City of Grand Prairie, City of Midlothian, Unincorporated Areas of Ellis County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,360 feet upstream of Kimble Road</ENT>
              <ENT>+564</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="10085"/>
              <ENT I="01">Soap Creek</ENT>
              <ENT>At the confluence with Joe Pool Lake</ENT>
              <ENT>+540</ENT>
              <ENT>City of Grand Prairie, City of Midlothian, Unincorporated Areas of Ellis County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.26 mile downstream of U.S. Route 67</ENT>
              <ENT>+598</ENT>
            </ROW>
            <ROW>
              <ENT I="01">West Soap Creek</ENT>
              <ENT>At the confluence with Soap Creek</ENT>
              <ENT>+581</ENT>
              <ENT>Unincorporated Areas of Ellis County.</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22"/>
              <ENT>Approximately 0.5 mile upstream of Ray White Road</ENT>
              <ENT>+601</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">* National Geodetic Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">+ North American Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"># Depth in feet above ground.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">⁁ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
            </ROW>
            <ROW>
              <ENT I="21">
                <E T="02">ADDRESSES</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">
                <E T="02">City of Cedar Hill</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at City Hall, 502 Cedar Street, Cedar Hill, TX 75104.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">City of Grand Prairie</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at City Hall, 317 College Street, Grand Prairie, TX 75053.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">City of Midlothian</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at City Hall, 104 West Avenue East, Midlothian, TX 76065.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">Unincorporated Areas of Ellis County</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the Ellis County Courthouse, 101 West Main Street, Waxahachie, TX 75165.</ENT>
            </ROW>
          </GPOTABLE>
          
          <EXTRACT>
            <FP>(Catalog of Federal Domestic Assistance No. 97.022, “Flood Insurance.”)</FP>
          </EXTRACT>
          
        </REGTEXT>
        <SIG>
          <NAME>James A. Walke,</NAME>
          <TITLE>Acting Deputy Associate Administrator for Mitigation, Department of Homeland Security, Federal Emergency Management Agency.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03258 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-12-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">LEGAL SERVICES CORPORATION</AGENCY>
        <CFR>45 CFR Parts 1606, 1614, 1618, and 1623</CFR>
        <SUBJECT>Limited Reductions of Funding, Termination, and Debarment Procedures; Recompetition; Enforcement; Suspension Procedures; Private Attorney Involvement</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Legal Services Corporation.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This final rule amends the Legal Services Corporation's regulations on enforcement procedures through the addition of options for limited reductions of funding, expansion of non-audit based suspensions for up to ninety days, and immediate special grant conditions for compliance issues. The final rule provides updates and enhancements to the rules regarding enforcement generally, terminations, debarments, and suspensions. It also provides a technical conforming update to a cross-reference in the private attorney involvement regulation.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>This rule is effective as of March 15, 2013.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Mark Freedman, Senior Assistant General Counsel, Office of Legal Affairs, Legal Services Corporation, 3333 K Street NW., Washington, DC 20007; 202-295-1623 (phone); 202-337-6519 (fax);<E T="03">mfreedman@lsc.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Procedural Background</HD>

        <P>On January 31, 2012, the Legal Services Corporation (LSC) published in the<E T="04">Federal Register</E>at 77 FR 4749 a Notice of Proposed Rulemaking (NPRM) proposing changes to LSC's enforcement mechanisms. On August 7, 2012, LSC published in the<E T="04">Federal Register</E>at 77 FR 46995 a Further Notice of Proposed Rulemaking (FNPRM) expanding on the NPRM. LSC is now publishing final rules to conclude this rulemaking.</P>
        <P>LSC undertook this rulemaking to add three new enforcement options to the LSC regulations regarding grants for the provision of legal assistance:</P>
        <P>(1) A new “limited reduction of funding” that enables LSC to respond quickly to instances of substantial violation of LSC requirements through funding reductions of less than five percent using more simple procedures than for terminations of five percent or greater;</P>
        <P>(2) suspensions for non-audit based compliance issues that could last for up to ninety days, an increase from thirty days in the previous rule; and</P>
        <P>(3) special grant conditions regarding compliance issues that LSC could add immediately to a current grant.</P>
        
        <P>In the course of the rulemaking, LSC developed new administrative procedures to enhance the opportunities for informal resolution when LSC proposes to undertake a limited reduction of funding, a termination in whole or in part, or a debarment. The rule already provided for informal resolution through an informal conference with opportunities for settlement or compromise. The rule has enhanced the informal conference and added procedures to provide for resolution of the matter through prompt corrective action agreements, when appropriate.</P>

        <P>This rulemaking also clarifies existing regulations and makes conforming changes to the rules in order to accommodate the new process and procedures indicated. All of the comments and related memos submitted to the LSC Board regarding this<PRTPAGE P="10086"/>rulemaking are available in the open rulemaking section of LSC's Web site at<E T="03">www.lsc.gov.</E>
        </P>
        
        <FP SOURCE="FP-1">
          <E T="03">http://www.lsc.gov/about/regulations-rules/open-rulemaking</E>
        </FP>
        
        <P>After the effective date of the rule, those materials will appear in the closed rulemaking section.</P>
        
        <FP SOURCE="FP-1">
          <E T="03">http://www.lsc.gov/about/regulations-rules/closed-rulemaking</E>
        </FP>
        <HD SOURCE="HD1">II. General Authorities, Impetus for Rulemaking, and Existing Regulatory Compliance Mechanisms</HD>
        <P>The LSC Act provides general authority to the Corporation “to insure the compliance of recipients and their employees with the provisions of [the Act] and the rules, regulations, and guidelines promulgated pursuant to [the Act].” 42 U.S.C. 2996e(b)(1)(A). LSC's principal regulation discussing general enforcement authority and procedures is the Enforcement Procedures regulation at 45 CFR part 1618. LSC uses a variety of enforcement tools, formal and informal, to ensure compliance. Among these are informal consultations and compliance training, on-site Case Service Report/Case Management System reviews, the imposition of Required Corrective Actions (RCAs), and the imposition of Special Grant Conditions (SGCs) at the beginning of a grant award period or at grant renewal. Several enforcement tools involving suspending or reducing funding to a recipient to address significant non-compliance are provided in LSC-adopted regulations. LSC has adopted grant termination procedures (45 CFR part 1606) that provide for the termination of funding in whole or part in cases of a recipient's substantial noncompliance with LSC statutory or regulatory requirements and other policies, instructions, or grant terms and conditions. LSC has also adopted suspension procedures (45 CFR part 1623) and disallowed-cost procedures (45 CFR part 1630). Lastly, part 1606 provides authority for LSC to debar recipients from eligibility to receive future grants.</P>
        <P>LSC amended the part 1606 termination procedures in 1998 and created a separate provision for reductions of funding of less than five percent, which are not considered terminations and not subject to the full set of procedures that apply to terminations. The 1998 amendments to the rule required, however, that to reduce funding to a recipient by less than five percent, LSC would have to establish additional procedures by rulemaking. 45 CFR 1606.2(d)(2)(v). LSC commenced this rulemaking to establish those procedures.</P>
        <P>The majority of LSC recipients are in substantial compliance with LSC requirements most of the time. When non-compliance occurs, recipients almost always work diligently and cooperatively with LSC staff to come promptly into compliance, but there have been exceptions and situations in which LSC has felt the need for the kind of enforcement tools covered by this rulemaking.</P>
        <P>This rulemaking also addresses a problem in the previous rules regarding LSC's ability to take timely actions. LSC can impose suspensions after as little as eleven days of process, but the previous rule limited suspensions to thirty days (other than audit-based suspensions). The next enforcement option available to LSC was terminations, which require five months or more of procedures if the recipient uses all available levels of review. Similarly, disallowed costs may be available to recover improperly spent funds, although that process is designed for recovery rather than enforcement and sanction. Also, disallowed costs can take over five months to complete (except for disallowed costs of less than $2,500). This rulemaking provides for suspensions of funding for up to ninety days, for limited reductions of funding that can be implemented in approximately eighty days, and for special grant conditions that can be added immediately to an existing grant.</P>

        <P>This rulemaking also addresses concerns expressed by the Government Accountability Office (GAO) in its report, Legal Services Corporation: Improved internal controls needed in grants management and oversight, GAO-08-37 (December 2007). In that report, the GAO opined that LSC has “limited options for sanctioning or replacing poor-performing recipients.” GAO-08-37 at 17. The existing enforcement mechanisms available to LSC are best suited to situations involving numerous and/or very significant violations that merit severe actions such as terminations, or to situations in which compliance issues are technical or minor and can be resolved through corrective actions, grant conditions, and similar actions. LSC has not had enforcement mechanisms well suited to violations or compliance issues in an intermediate range (<E T="03">e.g.,</E>material but not extreme, or multiple but not profuse) in situations where a recipient does not voluntarily take corrective action in a timely manner. Furthermore, disallowed costs are not a good substitute for an intermediate range enforcement mechanism. The amount of funds in question is not necessarily proportional to the severity of the violation. Minor violations could have large associated costs while major violations could have relatively small associated costs.</P>
        <P>LSC significantly revised LSC's enforcement rules in 1998 in response to Congressional changes to the governing law. Prior to 1996, section 1011 of the LSC Act provided minimum process requirements for suspensions over thirty days, terminations, and denials of refunding that included hearing rights and review by independent hearing examiners. 42 U.S.C. 2996j. LSC implemented these statutory requirements in 1976 and 1978 through the original enforcement regulations: part 1618 (General enforcement thresholds), part 1606 (Terminations and denials of refunding), and part 1623 (Suspensions). In 1996, Congress suspended section 1011 via riders to the annual LSC appropriation, which have been reincorporated every year thereafter, including some modifications in 1998.</P>
        
        <P>For the purposes of the funding provided in this [FY 1996 Appropriations] Act, rights under sections 1007(a)(9) [interim funding for refunding applicants] and 1011 of the Legal Services Corporation Act (42 U.S.C. 2996f(a)(9) and 42 U.S.C. 2996j) shall not apply.</P>
        

        <FP>Pub. L. 104-134, section 503(f), 110 Stat. 1321 (1996) (FY 1996); Pub. L. 104-208, section 501(b), 110 Stat. 3009 (1996) (FY 1997) (reiterating the FY 1996 language). For FY 1998, Congress reiterated the FY 1996 language and further elaborated that LSC “may terminate” a grant or contract if LSC finds “that the recipient has failed to comply with any requirement of the Legal Services Corporation Act (42 U.S.C. 2996<E T="03">et seq.</E>), this [appropriations] Act, or any other applicable law relating to funding for the Corporation * * *.” Pub. L. 105-119, sections 501(b) and (c), 111 Stat. 2440 (1997) (FY 1998). Congress has incorporated that language by reference in every annual LSC appropriation since 1998. Congress also mandated in 1996 and thereafter that LSC have the option to suspend funding to a recipient, in full or in part, if the recipient fails to have an acceptable audit. Audit-based suspensions last until completion of an acceptable audit. Pub. L. 104-134, section 509(c), 110 Stat. 1321 (1996) (FY 1996) (incorporated by reference thereafter).</FP>

        <P>LSC implemented these statutory changes by revising 45 CFR parts 1606 and 1623. 63 FR 64636 (1998) (parts<PRTPAGE P="10087"/>1606 and 1625), 63 FR 64646 (1998) (part 1623). LSC explained that:</P>
        
        
        <EXTRACT>

          <FP>the new law in the appropriations act emphasizes a congressional intent to strengthen the ability of the Corporation to ensure that recipients are in full compliance with the LSC Act and regulations and other applicable law.<E T="03">See</E>H. Rep. No. 207, 105th. Cong., 1st Sess. 140 (1997). Accordingly, under this rule, the hearing procedures in part 1606 have been streamlined. The changes are intended to emphasize the seriousness with which the Corporation takes its obligation to ensure that recipients comply with the terms of their grants and provide quality legal assistance. At the same time, the Corporation intends that recipients be provided notice and a fair opportunity to be heard before any termination or debarment action is taken.</FP>
        </EXTRACT>
        
        <FP>63 FR at 64637 (preamble to revised parts 1606 and 1625). LSC further elaborated in the preamble to the rulemaking that:</FP>
        
        <EXTRACT>
          <FP>[t]he legislative intent underlying Sections 501(b) and (c) of the Corporation's FY 1998 appropriations act was to enable the Corporation to streamline its due process procedures in order to ensure that recipients are in full compliance with LSC grant requirements and restrictions.</FP>
        </EXTRACT>
        
        <FP>
          <E T="03">Id.</E>at 64640. LSC carefully balanced the concerns for ongoing client services and recipient rights with the clear direction from Congress to enhance accountability and oversight of recipients' use of LSC funds. The current rulemaking is designed to build upon, but not fundamentally alter, the rationale for the 1998 rulemaking.</FP>
        <P>The changes in this final rule reflect LSC's obligation to safeguard public funds appropriated by Congress for civil legal aid by ensuring compliance with LSC rules, restrictions, and requirements. These additions to the enforcement mechanisms are consistent with LSC's understanding of Congress's intent to strengthen LSC's enforcement mechanisms, while carefully accounting for the importance of continued delivery of legal services and the rights of LSC recipients.</P>
        <HD SOURCE="HD1">III. Summary of Existing Compliance Tools Not Covered by the Regulations</HD>
        <P>LSC uses a variety of non-regulation based tools to track and ensure compliance. Among these are informal consultations and compliance training, on-site Case Service Report/Case Management System reviews, the imposition of Required Corrective Actions (RCAs), and the imposition of Special Grant Conditions (SGCs) at the beginning of a grant year.</P>

        <P>LSC relies primarily on RCAs to remedy compliance problems. The LSC Office of Compliance and Enforcement (OCE) estimates that in approximately 90 percent of cases in which RCAs are imposed, recipients implement the RCAs on a timely and satisfactory basis. In approximately ten percent of the cases, however, a recipient fails to implement the required corrective actions in a timely or satisfactory manner. In some instances in which recipients have failed to implement RCAs in a timely or satisfactory manner, LSC has imposed SGCs. Although SGCs may be substantively identical to the measures contained in RCAs, SGCs elevate the matter by formally incorporating the conditions into the recipient's grant documents and ensuring that the recipient's Board Chair, who has to sign the SGCs, is aware of an ongoing problem. In recent years, LSC has also used short-term funding to encourage compliance by providing a grant or successive grants for less than a year (<E T="03">e.g.,</E>month-to-month).</P>
        <HD SOURCE="HD1">IV. Summary of Procedures for Compliance Tools</HD>
        <P>Members of the LSC Board raised concerns that the parallel and interrelated procedures for different enforcement mechanisms could be confusing. For clarification, the table below summarizes the enforcement actions provided for in the rules and the respective procedures for each. This table uses the revised nomenclature provided in the final rule. The prior suspension and termination rules contained inconsistencies in the terms used for each stage of the process; those terms have been standardized in the final rule.</P>
        <GPOTABLE CDEF="s75,r75,r75,r75" COLS="4" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Limited reductions</CHED>
            <CHED H="1">Termination</CHED>
            <CHED H="1">Debarment</CHED>
            <CHED H="1">Suspension</CHED>
          </BOXHD>
          <ROW RUL="s">
            <ENT I="01">§ 1606.2, Less than 5 Percent</ENT>
            <ENT>§ 1606.2, 5 percent or more</ENT>
            <ENT>§ 1606.2</ENT>
            <ENT>§ 1623.2</ENT>
          </ROW>
          <ROW EXPSTB="03" RUL="s">
            <ENT I="21">Type of Violation</ENT>
          </ROW>
          <ROW EXPSTB="00">
            <ENT I="01">Substantial violation,<LI>§ 1606.2</LI>
            </ENT>
            <ENT>Substantial violation, § 1606.2</ENT>
            <ENT/>
            <ENT>Substantial violation, § 1623.3(a), § 1606.2.</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Substantial failure, § 1606.3(a)(2)</ENT>
            <ENT/>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT/>
            <ENT>Good cause, § 1606.4(b)</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT/>
            <ENT/>
            <ENT>Prompt action is necessary, § 1623.3(a).</ENT>
          </ROW>
          <ROW RUL="s">
            <ENT I="22"/>
            <ENT/>
            <ENT/>
            <ENT>Failure of an audit, § 1623.3(b).</ENT>
          </ROW>
          <ROW EXPSTB="03" RUL="s">
            <ENT I="21">Procedure</ENT>
          </ROW>
          <ROW EXPSTB="00">
            <ENT I="01">Preliminary Determination, § 1606.6(a)</ENT>
            <ENT>Preliminary Determination, § 1606.6(a)</ENT>
            <ENT>Preliminary Determination, § 1606.6(a)</ENT>
            <ENT>Proposed Determination, § 1623.4(b).</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Compliance Agreement (if available and agreed to), § 1606.7(a)</ENT>
            <ENT>Compliance Agreement (if available and agreed to), § 1606.7(a)</ENT>
            <ENT>Compliance Agreement (if available and agreed to),  § 1606.7(a)</ENT>
            <ENT>Prompt Corrective Action,  § 1623.2.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Submission of Written Materials in Opposition to the Preliminary Determination (if no compliance agreement),  § 1606.7(b)</ENT>
            <ENT>Submission of Written Materials in Opposition to the Preliminary Determination (if no compliance agreement),  § 1606.7(b)</ENT>
            <ENT>Submission of Written Materials in Opposition to the Preliminary Determination (if no compliance agreement),  § 1606.7(b)</ENT>
            <ENT>Submission of Written Materials in Opposition to the Proposed Determination,  § 1623.4(f).</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Informal Conference,  § 1606.7(b)-(e)</ENT>
            <ENT>Informal Conference,  § 1606.7(b)-(e)</ENT>
            <ENT>Informal Conference,  § 1606.7(b)-(e)</ENT>
            <ENT>Informal Meeting,  § 1623.4(b)-(f).</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Draft Final Decision,  § 1606.7(f)</ENT>
            <ENT>Draft Final Decision,  § 1606.7(f)</ENT>
            <ENT>Draft Final Decision,  § 1606.7(f)</ENT>
            <ENT>Final determination,  § 1623.4(f).</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Hearing,  § 1606.8</ENT>
            <ENT>Hearing,  § 1606.8</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Recommended Decision,  § 1606.9</ENT>
            <ENT>Recommended Decision,  § 1606.9</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="10088"/>
            <ENT I="01">Review by the LSC President,  § 1606.10</ENT>
            <ENT>Review by the LSC President,  § 1606.10</ENT>
            <ENT>Review by the LSC President,  § 1606.10</ENT>
            <ENT>Review by the LSC President (for a suspension lasting more than 30 days not based on an audit failure),  § 1623.4(h).</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Final Decision,  § 1606.10(e)</ENT>
            <ENT>Final Decision,  § 1606.10(e)</ENT>
            <ENT>Final Decision,  § 1606.10(e)</ENT>
            <ENT>Suspension Appeal Decision,  § 1623.4(h)(3).</ENT>
          </ROW>
        </GPOTABLE>
        <HD SOURCE="HD1">V. Commentary on Rulemaking Process and Comments Received</HD>

        <P>LSC received nineteen comments on the NPRM and eight comments on the FNPRM. All of the comments and LSC's analysis of them are posted on the rulemaking page of<E T="03">www.lsc.gov.http://www.lsc.gov/about/regulations-rules</E>
        </P>
        <P>The most extensive comments on both proposals were submitted by the LSC Office of Inspector General (OIG), the American Bar Association Standing Committee on Legal Aid and Indigent Defendants (SCLAID), and the National Legal Aid and Defender Association (NLADA). Colorado Legal Services and the Northwest Justice Project (NJP) also submitted detailed comments. The other comments generally endorsed the NLADA comments. Only the OIG fully supported the rulemaking, although the OIG recommended removing any time limit on suspensions and expressed concerns that the requirements for the new special grant conditions were too restrictive. SCLAID did not oppose the rulemaking, but it strongly recommended significant enhancements to standards and procedures similar to those recommended by NLADA. NLADA, and most of the other comments, opposed the rulemaking and recommended significant enhancements to standards and procedures if it proceeded.</P>
        <HD SOURCE="HD2">a. New Compliance Tools</HD>
        <P>The NPRM proposed a new set of procedures for limited reductions of funding based on the existing procedures for suspensions, which provide for one level of review through an informal meeting. In response to comments that this did not provide sufficient process, LSC revised the proposal in the FNPRM in two ways. First, the same process is used at the initial stage for terminations and for limited reductions. Thereafter, limited reductions may be appealed to the LSC President using procedures based on the disallowed cost appeal procedures in 45 CFR part 1630. Some comments also raised similar concerns for suspensions, especially if they could last for up to ninety days. In response, the final rule also adds the same appeal process for suspensions once they extend beyond thirty days (thirty-day suspensions have always been permitted without further appeal). The NPRM proposed allowing LSC to impose SGCs immediately during a grant term rather than waiting for a new grant award or renewal. The OIG's comment expressed concern that the SGC language might appear to constrain some of LSC's authority, and other comments indicated concerns that the SGC language was too vague. In the FNPRM, LSC revised the language to clarify that it applies to the kinds of situations in which LSC has investigated a matter and developed RCAs. LSC may immediately impose SGCs that incorporate those RCAs into the grant documents.</P>
        <HD SOURCE="HD2">b. Standards and Procedures</HD>
        <P>The comments that recommended enhancements in the standards and procedures were not limited to the enforcement actions in the proposed rulemaking. Rather, they recommended revisions that would significantly change the rules as they have existed since 1998. In many cases, they would return to the pre-1998 standards, such as requiring non-LSC, independent hearing examiners, or exceed those standards, such as an increased intent requirement and a safe harbor for reliance on reasonable alternate interpretations of the LSC rules. LSC commenced this rulemaking to enhance enforcement options within the standards and procedures adopted in the 1998 rulemaking to respond to Congress's changes in the enforcement requirements of the LSC Act. The final rule does not adopt the many suggestions in the comments to change that carefully constructed enforcement framework. The OIG also suggested adding a requirement for publication of all final decisions to address due process concerns in the comments through transparency for those final actions. Rather than incorporating that suggestion as a regulatory requirement, LSC will address it in the policies and procedures for enforcement actions.</P>
        <HD SOURCE="HD2">c. Informal Conference and Prompt Corrective Actions</HD>
        <P>The final rule makes a number of revisions to increase the focus on attempts to resolve the violation at or before the informal conference. The final rule adds to the notice of the preliminary determination a requirement for summarizing prior attempts at resolution. The previous rule required that the same LSC employee who issued the notice would hold the informal conference. The final rule permits LSC to designate any senior employee to hold the informal conference, which provides LSC with more flexibility to set a dispute resolution tone. The final rule also adds “implementation of corrective actions” as an example of the types of settlement or compromise envisioned for the informal conference.</P>
        <P>The final rule includes a new alternative strategy for informal resolution prior to the implementation of an enforcement action. LSC has the option of notifying the recipient that it can avoid the enforcement action through corrective action, if appropriate. The recipient may elect to accept that corrective action through timelines and implementation plans acceptable to LSC and documented in a compliance agreement; LSC could hold the enforcement action in abeyance so long as the recipient honors the agreement. If the recipient completes the corrective actions to LSC's satisfaction (in both substance and timeliness), then LSC would withdraw the preliminary determination without implementing the enforcement action. If LSC at any time decides that the recipient has failed to adhere to the agreed-upon corrective action plan, including failing to act in accordance with the established timeline, then LSC could continue with the enforcement process.</P>
        <HD SOURCE="HD2">d. Suspension Appeals</HD>

        <P>In response to the comments received, LSC has included in the final rule an appeals process for suspensions that last over thirty days. The appeals process is based on the appeals process for limited reductions of funding. As with suspension decisions, the timeframe is short to enable LSC to resolve the appeal quickly. Unlike other enforcement actions, suspensions are enforced during the appeal period.<PRTPAGE P="10089"/>
        </P>
        <HD SOURCE="HD2">e. Scope of Enforcement Action</HD>

        <P>The final rule discusses the scope of partial terminations and limited reductions of funding by using the language of the previous rule regarding the level of financial assistance provided by the Corporation to a recipient pursuant to a grant or contract. 45 CFR 1600.1 defines “financial assistance” as the “annualized funding from the Corporation granted under section 1006(a)(1)(A) for the direct delivery of legal assistance to eligible clients.” These grants are for the provision of general-purpose legal assistance in a geographic area or to a specific population. Currently, LSC provides these grants for three types of service areas: basic field, Native American, and migrant. When LSC awards multiple service areas to a recipient (<E T="03">e.g.,</E>both a basic field service area and migrant service area), it typically does so through a single grant or contract. Part 1606 enforcement actions affect the level of financial assistance, which will include all of the 1006(a)(1)(A) service areas.</P>
        <P>Other LSC grants, under sections 1006(a)(1)(B) or (a)(3) of the LSC Act, are not subject to these procedures. Rather, LSC may provide for terminations or other enforcement actions for those grants pursuant to policies and procedures specific to those grant programs. For example, funding for Technology Initiative Grants is project-based and specifically tied to acquisitions, tasks, and timelines.</P>
        <P>The final rule implements the NPRM provision that limited reductions apply only to one grant year. The final rule continues the provisions of the previous rule that a partial termination presumptively applies to only one grant year, but that LSC can specify a longer period up to the entire funding term.</P>
        <HD SOURCE="HD1">VI. Section-by-Section Analysis</HD>
        <HD SOURCE="HD2">Part 1606—Termination, Limited Reduction of Funding, and Debarment Procedures; Recompetition</HD>
        <HD SOURCE="HD3">1606.1Purpose</HD>
        <P>Section 1601.1(b) contains two additions. First, the phrase “proportional to the proposed action” is added to modify “timely and fair due process procedures.” This addition corresponds to the addition of procedures for limited reductions of funding of less than five percent, which do not include a hearing before a hearing officer. The rule provides two sets of overlapping procedures, one for debarments and terminations of funding (five percent and greater) and the other for limited reductions of funding (less than five percent). Second, the phrase “or to impose a limited reduction of funding” is added to the list of remedies available under the rule.</P>
        <P>A new § 1601.1(d) reflects a reorganization of the rule in the interest of clarity. It relocates the previous § 1606.2(c), without change, which described provisions of other LSC regulations that involve funding changes but are not subject to the termination procedures. This relocation emphasizes and clarifies that the indicated situations are not subject to the actions under part 1606. A corresponding change to matching language in 45 CFR part 1614 is included in this final rule.</P>
        <HD SOURCE="HD3">1606.2Definitions</HD>
        <P>This section has substantive and structural changes. All of the definitions now appear alphabetically.</P>
        <P>The term “Corporation” is defined in 45 CFR 1600.1 to mean the Legal Services Corporation. The definition has been expanded here to provide that decisions of the Corporation, such as initiating a part 1606 proceeding, must be made by an individual acting at the level of, or senior to, an LSC office director. A deputy director could make these decisions if he or she is acting with the authority of the director, such as when the director's position is vacant, or the director is unavailable due to an illness and the deputy director has taken over the relevant responsibilities. The FNPRM had proposed that decisions could be made by deputy directors. The final rule narrows the circumstances in which deputy directors can act, in part responding to concerns raised by a commenter.</P>
        <P>“Days” is added as a defined term to mean calendar days as computed under the Federal Rules of Civil Procedure, unless business days are specified, in which case Saturdays, Sundays, and legal holidays recognized under those rules are excluded. The rule had not previously defined days, which could have caused confusion regarding deadlines. In particular, some deadlines were five days, which in some cases could be as little as two business days. All time periods below fifteen days are changed in the rule to business days.</P>
        <P>“Funding term” is added as a defined term to mean the time period for an award of financial assistance for a service area as that term is used in grant-making. The funding term is the longest period between competitions for a service area. Under 45 CFR part 1634, LSC can award a section 1006(a)(1)(A) grant or contract for up to five years, which is the funding term. LSC provides section 1006(a)(1)(A) awards for a maximum funding term, which is normally no greater than three years. Within the funding term, LSC provides funding for grant award periods of no more than one year, which can be renewed for additional grant award periods.</P>
        <P>“Limited reduction of funding” is added as a defined term for reductions of funding of less than five percent, which the previous rule excluded from the definition of terminations. Unlike partial terminations, limited reductions apply only to the current grant year.</P>
        <P>“LSC requirements” is added as a defined term in 45 CFR part 1618 to capture the full list of statutory, regulatory, and other requirements that apply to LSC grants or contracts for financial assistance under the LSC Act. Parts 1606 and 1623 of the previous rules repeatedly referenced the list of sources specified in this definition. For both clarity and consistency, the term is now defined using the language appearing in the previous rules and is cross-referenced in both parts 1606 and 1623.</P>
        <P>“Receipt” of materials is added as a defined term to provide clarity in calculating deadlines under the rule. Formal service of process is not required. Service must be sufficient to ensure that both LSC and the recipient are fully aware of the proceedings and the actions taken by both entities at each stage.</P>
        <P>The definition of “recipient” is functionally unchanged from the previously published version of this rule, which reiterated the definition at 45 CFR 1600.1. The final rule replaces that reiteration with a simple cross-reference.</P>
        <P>The term “substantial noncompliance” is clarified in this rule. The term is defined to mean either a substantial violation of the LSC requirements or a substantial failure to provide high quality, economical, and effective legal assistance.</P>
        <P>A definition of “substantial violation” has been added using the functional definition from § 1606.3(a) without any material modifications that would change its meaning or application from the previous rule.</P>
        <P>The definition of “termination” has been updated to reflect new definitions in the rule and relocation of the cross-references to other regulations; no material modifications that would change its meaning or application from the previous rule have been made.</P>

        <P>A definition of “violation” has been added to make clear that the scope of violations at issue under this rule is limited to the LSC requirements.<PRTPAGE P="10090"/>
        </P>
        <HD SOURCE="HD3">1606.3Grounds for a Termination or a Limited Reduction of Funding</HD>
        <P>The title of this section is updated to add limited reductions of funding.</P>
        <P>Section 1606.3(a) has minor nomenclature changes to conform to the new definitions and terms, including the new definition of “substantial violation,” but without any material modifications that would change its meaning or application from the previous rule. The definition of a “substantial failure” remains in § 1606.3(a)(2) with two adjustments: 1) the LSC appropriations have been added as a measure of performance, and 2) the term “guidance” is changed to “guidelines or instructions” consistent with the use of those terms in lieu of “guidance” throughout the previous and revised rules.</P>
        <P>Section 1606.3(b) is added to specify that LSC may impose a limited reduction of funding for substantial violations, but not substantial failures, when LSC determines that a termination, in whole or in part, is not warranted. As with terminations, LSC can base a limited reduction of funding only on substantial violations occurring within the past five years.</P>
        <P>Section 1606.3(c), the former paragraph (b), is changed to add limited reductions of funding. The requirements for a “substantial violation” are moved, without material modifications that would change their meaning or application from the previous rule, to the new definition of “substantial violation.” As proposed in the NPRM those same criteria apply to the determination of the magnitude of a proposed termination or limited reduction of funding. LSC stated in the NPRM that consideration of these factors was already implicit in considerations of how much funding should be affected by a proposed enforcement mechanism. SCLAID's comments recommended that LSC add an entire new section and criteria for determinations of magnitude, including the impact on client services and other funding for the recipient. The final rule does not do so because the magnitude of an enforcement action should relate directly to the magnitude of the violation and deterrence of future violations. LSC has general discretion to consider the totality of the situation when deciding how to proceed with an enforcement action to foster ongoing compliance while minimizing disruption of client services.</P>
        <HD SOURCE="HD3">1606.4Grounds for Debarment</HD>
        <P>This section does not include any material modifications that would change its meaning or application from the previous rule. All changes are technical adjustments.</P>
        <P>The language of section 1606.4(b)(4) is modified to clarify that it applies to any arrangements that are covered by debarments, not only subgrants or subcontracts, and that reference to a debarred “IPA,” which is undefined in the previous rule, means any debarred independent public accountant or other auditor.</P>
        <P>Last, the reference to the “effective date of this rule” in § 1606.4(b)(5) is changed to December 23, 1998, the effective date of the previous rule.</P>
        <HD SOURCE="HD3">1606.5Procedures</HD>
        <P>The heading and § 1606.5(a) are updated to remove the limited reference to terminations and debarments in order to include limited reductions of funding. These procedures are available for, and apply to, all part 1606 enforcement mechanisms.</P>
        <P>A new § 1606.5(b) is added to correspond to the new level of review in § 1606.10 for limited reductions of funding. The LSC President, or another senior LSC employee, will hear any final appeal of a limited reduction draft final decision. Those procedures are modeled on the 45 CFR part 1630 final appeal procedures for disallowed costs. The person hearing the appeal must have not been involved in the prior proceedings. The final rule requires that LSC designate the person to hear the final appeal before LSC considers whether or not to proceed with a preliminary determination for a limited reduction of funding.</P>
        <HD SOURCE="HD3">1606.6Preliminary Determination and Final Decision</HD>
        <P>The title of this section is updated to include reference to a final decision, which may be issued under this section if the recipient does not request any review of the preliminary determination. The language of this section is updated for clarity and to include limited reductions of funding, without material modifications that would change its meaning or application from the previous rule.</P>
        <P>Section 1606.6(a)(6) is added to explicitly provide an option for LSC to specify corrective action that could resolve the situation without a termination or limited reduction of funding. This language is based on the previous suspension rule at 45 CFR part 1623; it does not appear in the previous part 1606 rule. LSC is not required to provide the recipient with a corrective action option, and the recipient does not have a right to avoid a termination or limited reduction of funding through corrective actions unless explicitly authorized by LSC. This language provides a clear option for resolving these situations through corrective action if LSC determines that doing so would be sufficient pursuant to the new § 1606.7(a).</P>
        <P>Section 1606.6(a)(7) is added to require that the preliminary determination summarize any prior attempts at resolution of the situation. The addition of this paragraph does not require LSC to seek resolution prior to initiating a part 1606 action. Rather, when LSC and the recipient have attempted to resolve the situation, the rule will now require that LSC summarize those attempts and make them part of the administrative record.</P>
        <P>References to a “designated employee” in this section are replaced with references to the Corporation as the actor, consistent with the definition of Corporation.</P>
        <HD SOURCE="HD3">1606.7Corrective Action, Informal Conference, Review of Written Materials in Opposition to the Preliminary Determination, and Final Decision</HD>
        <P>The title and content of this section have been updated to expand and clarify the options available after a recipient receives a preliminary determination. As stated in the previous rule, the informal conference is designed to create the opportunity for narrowing the issues and exploring the possibility of settlement or compromise. The informal conference is retained without material modifications that would change its meaning or application from the previous rule. The rule is changed to permit any senior LSC employee to hold the informal conference rather than the previous requirement that it be held by the same employee who issued the preliminary determination. In some cases, the same employee should handle both matters to bring consistent perspective and experience to the matter. In other situations, it may foster an atmosphere of settlement or compromise to have different LSC employees handle each stage of the process.</P>
        <P>This section now explicitly provides an option for the recipient to submit written materials in opposition to the preliminary determination without a request for an informal conference. This option to present arguments in writing only is based on the similar option in the suspension rule at 45 CFR part 1623; a conference is not required if the recipient requests only a paper review.</P>
        <HD SOURCE="HD3">1606.7(a)Corrective Action</HD>

        <P>Paragraph (a) provides a new option for resolving a preliminary<PRTPAGE P="10091"/>determination through adoption of any corrective action proposed by LSC, in its sole discretion, as a clear path to settlement of the issues. A corrective action proposed by the recipient that significantly differs from the LSC proposal may be considered at an informal conference but not as part of the § 1606.7(a) procedures. The recipient must agree to the terms and timing of implementation of the corrective actions to the satisfaction of LSC, as memorialized in a written compliance agreement. If, at any time, LSC determines that the recipient is not sufficiently implementing the corrective action, LSC can proceed to issue a draft final decision, subject to the further rights of review under later sections of this part. If a recipient chooses this new process, then the recipient cannot later request an informal conference under this section. This option responds to a comment that the proposed rule did not clearly address what would happen if the recipient adopted the suggested corrective action. It also implements suggestions from the LSC Board that the rule should provide better means of alternative resolution when appropriate.</P>
        <HD SOURCE="HD3">1606.7(b)-(g)</HD>
        <P>The provisions regarding the informal conference have been revised to clarify the procedures, permit any senior LSC employee to hold the conference, and to require that a draft decision to proceed with the enforcement option contain a summary of the issues raised in the conference or in submitted written materials.</P>
        <HD SOURCE="HD3">1606.8Hearing for a Termination or Debarment</HD>
        <P>The title of this section is updated to specify that hearings are available only for terminations and debarments, but not for limited reductions of funding. There are no material modifications that would change the meaning or application of this section from the previous rule. The deadlines have been designated as business or calendar days consistent with the new definition of days.</P>
        <HD SOURCE="HD3">1606.9Recommended Decision for Termination or Debarment</HD>
        <P>The title and language of this section are updated to specify that the recommended decision is applicable only to hearings for terminations or debarments. The only substantive change is a new § 1606.9(a)(2) that permits the hearing officer to recommend reducing a termination to below five percent, and thus convert a termination into a limited reduction of funding. The previous rule permitted the hearing officer to recommend terminations only, which would exclude the option of funding reductions of below five percent. Reference to limited reductions of funding is added to § 1606.9(a)(3) for consistency without any material modifications that would change its meaning or application from the previous rule referencing terminations or debarments.</P>
        <HD SOURCE="HD3">1606.10Final Decision for a Termination, Debarment, or Limited Reduction of Funding</HD>
        <P>This section is updated to add direct appeals to the LSC President, or designee, of draft final decisions for limited reductions of funding. This type of appeal is similar to the final appeal of a disallowed cost decision in 45 CFR part 1630. The final review is identical as that provided for in other part 1606 actions, with one exception. For limited reduction of funding appeals to the President, in which there in no right to review by a hearing officer, new paragraph (d) provides that the President must not have had prior involvement with the limited reduction of funding proceedings under this part. That provision is also based on the part 1630 process, which requires that the President not review actions in which he or she had prior involvement. As discussed in the FNPRM, the President is not disqualified merely because he or she is briefed about the situation, contacted by the recipient or other parties, or otherwise is aware but not actively involved in the part 1606 proceedings.</P>

        <P>A number of comments recommended that the hearing officers or the final decision maker for appeals be non-LSC employees. As discussed earlier, in 1996 Congress lifted the LSC Act requirement for enforcement actions to be reviewed by an independent hearing examiner. The final rule does not change the impartiality requirement for hearing officers for terminations and debarment that they have not had prior involvement in the part 1606 enforcement action being reviewed. It also does not change the ability of LSC to suspend funding for up to thirty days without impartial review. For the new limited reductions of funding and suspensions of over thirty days, the final rule provides the same requirement of impartiality for the LSC President or other senior LSC employee providing final review of the matter. These impartiality requirements are sufficient for the process rights of recipients within the statutory framework and LSC's understanding of Congress's expectations for LSC's enforcement procedures. Other changes to this section clarify the process and deadlines without substantive changes. The FNPRM suggested adding the § 1606.6(a) preliminary determination requirements to any final decision modifying or extending the draft final decision. That suggestion is not retained in this final rule because it became apparent during the comment period that those requirements are tailored to the preliminary determination,<E T="03">e.g.,</E>including the notice of rights to appeal and continued funding, and are not appropriate for final decisions.</P>
        <HD SOURCE="HD3">1606.11Qualifications on Hearing Procedures</HD>
        <P>This section is updated for clarity without material modifications that would change its meaning or application from the previous rule. Section 1606.11(c)(3) is updated to require that LSC provide the final decision to the recipient within five days of the expiration of the appeal period. The previous rule stated that the recommended decision would become final if not appealed, but did not state when it must be provided as a final decision.</P>
        <HD SOURCE="HD3">1606.12Time and Waiver</HD>
        <P>This section is updated for clarity without material modifications that would change its meaning or application from the previous rule.</P>
        <HD SOURCE="HD3">1606.13Interim and Other Funding, Reprogramming, Implementation</HD>
        <P>This section is updated to include reference to limited reductions of funding. A new § 1606.13(d) is added to state explicitly that the manner of implementation is at the sole discretion of LSC. For example, depending on the situation, including the timing of the action in the grant year and funding term, LSC may choose to pro-rate a partial termination or limited reduction through the remaining grant payments or to withhold the reduced funds in one lump sum. The previous rule did not address that issue and this new section is consistent with the options available to LSC within its discretion under that rule.</P>

        <P>Section 1606.13(e), the former paragraph (d), is modified to remove the reference to using the terminated or reduced funds for the same service area, as proposed in the NPRM. The previous rule provided that LSC may keep the funds in the same service area or otherwise reallocate them for any basic field purposes. Some of the comments recommended keeping the existing rule. As discussed in the NPRM, this language is eliminated because it could<PRTPAGE P="10092"/>lead to an erroneous expectation that LSC would give preference to keeping the funds from a termination in part or from a limited reduction of funding in the same service area in which the same recipient continued to provide services through the end of the funding term. LSC had the authority under the previous rule and has the authority under this final rule to exercise its discretion to determine the best use of these funds in light of considerations such as the needs of the service area, the behavior of the recipient, and other uses of recovered funds for emergencies or special grants in other service areas. The change in language does not change the substance of the rule.</P>
        <HD SOURCE="HD2">Part 1614—Private Attorney Involvement</HD>
        <HD SOURCE="HD3">1614.7(b)Failure To Comply</HD>
        <P>One technical update to 45 CFR part 1614 relates to this rulemaking. Although not included in the NPRM or FNPRM, this update includes no material modifications that would change the meaning or application of this section from the previous rule and is necessary to harmonize that rule with this rulemaking and other prior changes to the LSC regulations. Part 1614 requires that an LSC recipient expend an amount equivalent to at least 12.5 percent of a basic field award on private attorney involvement (PAI) activities. The failure to do so may result in LSC withholding or recovering some funds from the recipient, depending on the circumstances. Section 1614.7 of the previous rule provided the requirements for those situations and stated that the withholding or recovery of funds for a failure to meet the part 1614 requirements does not constitute either a termination or a denial of refunding. The reference to terminations is changed to a reference to any action under 45 CFR part 1606. The reference to denials of refunding is eliminated, as LSC withdrew the denial of refunding regulation in 1998.</P>
        <HD SOURCE="HD2">Part 1618—Enforcement Procedures</HD>
        <P>This final rule incorporates some substantive changes and some extensive structural, but non-substantive, changes to 45 CFR part 1618 as proposed in the FNPRM. The significant substantive change to the rule involves adding the imposition of special grant conditions during a grant year to § 1618.5(c). The final rule also changes references to violations of the LSC Act throughout the rule to violations of the LSC requirements as the term “LSC requirements” is defined for use in parts 1606 and 1623. The previous rule defined the “Act” as the LSC Act or the LSC rules and regulations, but did not include other applicable laws, such as the LSC appropriations riders, or LSC guidelines and instructions, which have been included in both parts 1606 and 1623 as they have been updated over the past thirty years. Part 1618 is both outdated and confusing in this regard. The new definition of LSC requirements is based on the language used in parts 1606 and 1623, and this definition applies in all three sections for consistency and clarity.</P>
        <P>Some of the comments suggested changing the threshold standard under § 1618.5(b) for proceeding to enforcement actions under parts 1606 and 1623. The rule provides that LSC can proceed to consider enforcement actions:</P>
        
        <EXTRACT>
          <P>[w]henever there is substantial reason to believe that a recipient has persistently or intentionally violated the Act, or, after notice, has failed to take appropriate remedial or disciplinary action to insure compliance by its employees with the Act, and attempts at informal resolution have been unsuccessful. * * *</P>
        </EXTRACT>
        
        <P>45 CFR 1618.5(b). Those comments suggested adding a “knowing and willful” standard to this section. The OIG's comment notes that the 1998 rulemaking considered using “intent” as a factor in the standard for terminations and choose instead to use the defined term “knowing and willful.” The final rule does not change this language and retains the longstanding “intent” prong of the part 1618 analysis consistent with original structure of the rule under the LSC Act and the 1998 changes to parts 1606 and 1623. “Knowing and willful” was adopted in 1998 as a defined term in those regulations as one of many factors for consideration, while “intentionally violated” was retained in part 1618.</P>
        <HD SOURCE="HD3">1618.1Purpose</HD>
        <P>The purpose section is updated to incorporate the broader scope of the LSC requirements.</P>
        <HD SOURCE="HD3">1618.2Definitions</HD>
        <P>The definitions section is updated to incorporate the broader scope of the LSC requirements. A definition of “violation” has been added to make clear that the scope of violations at issue under this rule is limited to the LSC requirements.</P>
        <HD SOURCE="HD3">1618.3Complaints</HD>
        <P>The language of this section is updated for clarity and to reference the new definitions.</P>
        <HD SOURCE="HD3">1618.4Duties of Recipients</HD>
        <P>The language of this section is updated for clarity and to reference the new definitions. A new § 1618.4(c) is added to emphasize that this section does not create rights for recipient employees. Rather, this section is designed to ensure that recipients adopt and follow procedures designed to ensure that employees implement and follow the LSC requirements, and that the recipient applies those requirements consistent with LSC's interpretation of them.</P>
        <HD SOURCE="HD3">1618.5Duties of the Corporation</HD>
        <P>The language of this section is updated for clarity and to reference the new definitions and include reference to limited reductions of funding. Section 1618.5(a) has a new final sentence clarifying that LSC's investigation of a possible violation may be limited to determining if the recipient is taking sufficient actions.</P>
        <P>The existing language in § 1618.5(b) requires “attempts at informal resolution” prior to proceeding to consider enforcement actions under some circumstances. There are no changes to this language, but LSC notes that the informal resolution referenced here includes consideration of remedial actions, preventative actions, and sanctions, as discussed in the FNPRM.</P>
        <P>A new § 1618.5(c) is added regarding immediate special grant conditions. Under previous LSC practice, special grant conditions were imposed only when a new grant was awarded or an existing grant was renewed. Under that practice, a recipient had an opportunity to consider the special grant conditions prior to agreeing to them. The NPRM proposed language to permit LSC to impose immediate grant conditions any time that the § 1618.5(b) thresholds are met. The FNPRM revised that language to permit immediate special grant conditions only after LSC determines that three factors are met: (1) A violation has occurred, (2) corrective actions are required, and (3) special grant conditions are needed prior to the next renewal or competition. The immediate special grant conditions enable LSC to convert required corrective actions contained in reports, such as OCE reports, into specific grant requirements.</P>
        <HD SOURCE="HD2">Part 1623—Suspension Procedures</HD>

        <P>The NPRM proposed to change only the language regarding the thirty-day limit on non-audit based suspensions to increase it to a ninety-day limit. The FNPRM, and this final rule, make a number of non-substantive, technical changes to harmonize the suspension<PRTPAGE P="10093"/>rule with 45 CFR part 1606. In the previous rule, some, but not all, of the relevant definitions are repeated in both rules. The final rule provides a cross reference to the definitions in 45 CFR part 1606 for consistency. An additional change is made in the final rule to permit commencement of other enforcement actions during a suspension. This change is consistent with the overall rulemaking and the revised enforcement mechanisms structure.</P>
        <P>Comments on the NPRM and the FNPRM recommended an appeal process for suspensions, especially those that go beyond certain dollar thresholds. The OIG agreed that some appeal might be appropriate, but expressed concern about adopting appeal procedures that are too cumbersome and emphasized that appeals should occur during the pendency of the suspension, which is meant to protect funds from future misuse. The final rule includes an appeal procedure that mirrors the procedure for limited reductions of funding, which is based on the 45 CFR part 1630 disallowed cost appeal procedure.</P>
        <P>The OIG also recommended eliminating any time limit for suspensions, and permitting suspensions to continue until compliance, as is the case for audit-based suspensions. In the 1998 rulemaking, LSC decided to retain a thirty-day limit on suspensions because LSC determined that a termination process was more appropriate than a prolonged suspension. 63 FR 64636 at 64638 (1998). In this rulemaking LSC has expanded suspensions to ninety days to make them more effective in short timeframes, but LSC continues to believe that terminations or reductions of funding with their corresponding procedures are more appropriate for intractable concerns that cannot be resolved within a limited suspension period.</P>
        <HD SOURCE="HD3">1623.2Definitions</HD>

        <P>The definitions of “knowing and willful” and “recipient” are deleted and replaced with a cross-reference to the definitions in 45 CFR part 1606, which include both of those terms. The definitions are identical in the previous rules and this change makes no substantive change to either. The use of the same definitions for other terms in both rules provides consistency throughout the regulations,<E T="03">e.g.,</E>“LSC requirements” and “substantial violation.”</P>
        <HD SOURCE="HD3">1623.3Grounds for Suspension</HD>
        <P>The previous rule provided a definition of “substantial violation” identical to the use of that term in 45 CFR part 1606. The term is deleted in favor of the new cross-reference to definitions in part 1606. There are no substantive changes to the definition.</P>
        <P>Similarly the term “LSC requirements” replaces the list of LSC requirements that appeared in this rule and in other places in the regulations. It is defined in 45 CFR part 1618 and cross-referenced in 45 CFR part 1606.</P>
        <HD SOURCE="HD3">1623.4Suspension Procedures</HD>
        <P>In response to comments regarding the need for appeals of suspensions, LSC is adding an appeals process for suspensions that last longer than thirty days. The process is specified in § 1623.4(a) and (h). This addition preserves the previous rule's requirements for commencing suspensions based on notice and an informal meeting and continuing those suspensions for up to thirty days without further appeal. If the suspension lasts longer than thirty days, then the recipient may appeal to the LSC President. The appeal procedures are based on the new part 1606 limited reduction of funding appeal procedures, which are in turn based on the part 1630 disallowed cost appeal procedures. The discussion of those procedures in part 1606 applies equally to this section. Unlike part 1606 actions, the suspension will continue pending the appeal. The final rule requires that LSC issue a suspension decision within fifteen calendar days of receipt of the appeal in order to resolve the appeal promptly.</P>
        <P>New § 1623.4(d) and (e) are copied from the revised informal conference procedures in 45 CFR part 1606. That language emphasizes seeking settlement or compromise and provides that the informal meeting can be conducted by the same employee who issued the proposed determination, or another senior LSC employee.</P>
        <P>Section 1623.4(k), regarding audit-based suspensions, is updated to state that the new appeal process does not apply to audit-based suspensions, preserving the previous rule's requirements.</P>
        <HD SOURCE="HD3">1623.6Interim Funding</HD>
        <P>A technical change is made to § 1623.6(b) to state that suspended funds will be “released” at the end of the suspension period rather than “returned.”</P>
        <HD SOURCE="HD1">Promulgation of Regulations</HD>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <CFR>45 CFR Part 1606</CFR>
          <P>Administrative practice and procedure, Grant programs-law, Legal services.</P>
          <CFR>45 CFR Part 1614</CFR>
          <P>Grant programs-law, Legal services, Reporting and recordkeeping requirements.</P>
          <CFR>45 CFR Part 1618</CFR>
          <P>Grant programs-law, Legal services.</P>
          <CFR>45 CFR Part 1623</CFR>
          <P>Administrative practice and procedure, Grant programs-law, Legal services.</P>
        </LSTSUB>
        
        <P>For the reasons set forth above, and under the authority of 42 U.S.C. 2996g(3), LSC proposes to amend 45 CFR chapter XVI as follows:</P>
        <REGTEXT PART="1606" TITLE="45">
          <AMDPAR>1. 1. Revise part 1606 to read as follows:</AMDPAR>
          <PART>
            <HD SOURCE="HED">PART 1606—TERMINATION, LIMITED REDUCTION OF FUNDING, AND DEBARMENT PROCEDURES; RECOMPETITION</HD>
            <CONTENTS>
              <SECHD>Sec.</SECHD>
              <SECTNO>1606.1</SECTNO>
              <SUBJECT>Purpose.</SUBJECT>
              <SECTNO>1606.2</SECTNO>
              <SUBJECT>Definitions.</SUBJECT>
              <SECTNO>1606.3</SECTNO>
              <SUBJECT>Grounds for a termination or a limited reduction of funding.</SUBJECT>
              <SECTNO>1606.4</SECTNO>
              <SUBJECT>Grounds for debarment.</SUBJECT>
              <SECTNO>1606.5</SECTNO>
              <SUBJECT>Procedures.</SUBJECT>
              <SECTNO>1606.6</SECTNO>
              <SUBJECT>Preliminary determination and final decision.</SUBJECT>
              <SECTNO>1606.7</SECTNO>
              <SUBJECT>Corrective action, informal conference, review of written materials, and final decision.</SUBJECT>
              <SECTNO>1606.8</SECTNO>
              <SUBJECT>Hearing for a termination or debarment.</SUBJECT>
              <SECTNO>1606.9</SECTNO>
              <SUBJECT>Recommended decision for a termination or debarment.</SUBJECT>
              <SECTNO>1606.10</SECTNO>
              <SUBJECT>Final decision for a termination, debarment, or limited reduction of funding.</SUBJECT>
              <SECTNO>1606.11</SECTNO>
              <SUBJECT>Qualifications on hearing procedures.</SUBJECT>
              <SECTNO>1606.12</SECTNO>
              <SUBJECT>Time and waiver.</SUBJECT>
              <SECTNO>1606.13</SECTNO>
              <SUBJECT>Interim and termination funding; reprogramming, implementation.</SUBJECT>
              <SECTNO>1606.14</SECTNO>
              <SUBJECT>Recompetition.</SUBJECT>
            </CONTENTS>
            <AUTH>
              <HD SOURCE="HED">Authority:</HD>
              <P>42 U.S.C. 2996e(b)(1), 2996f(a)(3), and 2996f(d); Pub. L. 105-119, Title V, Secs. 501(b) and (c), 502, 503, and 504, 111 Stat. 2440, 2510-12; Pub. L. 104-134, Title V, Sec. 503(f), 110 Stat. 1321, 1321-53.</P>
            </AUTH>
            <SECTION>
              <SECTNO>§ 1606.1</SECTNO>
              <SUBJECT>Purpose.</SUBJECT>
              <P>The purpose of this rule is to:</P>

              <P>(a) Ensure that the Corporation is able to take timely action to deal with incidents of substantial noncompliance by recipients with a provision of the LSC Act, the Corporation's appropriations act or other law<PRTPAGE P="10094"/>applicable to LSC funds, a Corporation rule, regulation, guideline or instruction, or the terms and conditions of the recipient's grant or contract with the Corporation;</P>
              <P>(b) Provide timely and fair due process procedures, proportional to the proposed action, when the Corporation has made a preliminary decision to terminate a recipient's LSC grant or contract, to debar a recipient from receiving future LSC awards of financial assistance, or to impose a limited reduction in funding; and</P>
              <P>(c) Ensure that scarce funds are provided to recipients who can provide the most effective and economical legal assistance to eligible clients.</P>
              <P>(d) None of the following actions are subject to the procedures or requirements of this part:</P>
              <P>(1) A reduction of funding required by law, including but not limited to a reduction in, or rescission of, the Corporation's appropriation that is apportioned among all recipients of the same class in proportion to their current level of funding;</P>
              <P>(2) A reduction or deduction of LSC support for a recipient under the Corporation's fund balance regulation at 45 CFR part 1628;</P>
              <P>(3) A recovery of disallowed costs under the Corporation's regulation on costs standards and procedures at 45 CFR part 1630;</P>
              <P>(4) A withholding of funds pursuant to the Corporation's Private Attorney Involvement rule at 45 CFR part 1614.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1606.2</SECTNO>
              <SUBJECT>Definitions.</SUBJECT>
              <P>For the purposes of this part:</P>
              <P>
                <E T="03">Corporation,</E>when used to refer to decisions by the Legal Services Corporation, means that those decisions are made by an individual acting with a seniority level at, or equivalent to, the level of an office director or higher.</P>
              <P>
                <E T="03">Days</E>shall mean the number of calendar days as determined by the rules for computing time in the Federal Rules of Civil Procedure, Rule 6, except that computation of<E T="03">business days</E>shall exclude Saturdays, Sundays, and legal holidays (as defined in those rules).</P>
              <P>
                <E T="03">Debarment</E>means an action taken by the Corporation to exclude a recipient from receiving an additional award of financial assistance from the Corporation or from receiving additional LSC funds from another recipient of the Corporation pursuant to any other means, including a subgrant, subcontract or similar agreement, for the period of time stated in the final debarment decision.</P>
              <P>
                <E T="03">Funding term</E>means the maximum time period for an award or awards of financial assistance under section 1006(a)(1)(A) of the LSC Act provided by the Corporation to a recipient selected pursuant the competition requirements at 45 CFR part 1634. LSC may award grants or contracts for a period of the entire funding term or for shorter periods that may be renewed or extended up to the funding term.</P>
              <P>
                <E T="03">Knowing and willful</E>means that the recipient had actual knowledge that its action or lack thereof constituted a violation and despite such knowledge, undertook or failed to undertake the action, as the case may be.</P>
              <P>
                <E T="03">Limited reduction of funding</E>means a reduction of funding of less than five percent of a recipient's current level of financial assistance imposed by the Corporation in accordance with the procedures and requirements of this part. A limited reduction of funding will affect only the recipient's current year's funding.</P>
              <P>
                <E T="03">LSC requirements</E>means the same as that term is defined in 45 CFR Part 1618.</P>
              <P>
                <E T="03">Receipt</E>of materials shall mean that the materials were sent to the normal address for physical mail, email, or fax transmission, and there is reliable secondary confirmation of delivery. For physical delivery, confirmation may be provided through tracking information from the delivery service. For other forms of delivery, confirmation may be provided through a document such as a confirmation email or a fax sent from an authorized person at the recipient. Receipt of materials by the LSC recipient or the Corporation is sufficient for the running of applicable time periods. Proof of receipt by the Chair of the governing body is not necessary unless delivery to the recipient itself cannot be reasonably accomplished.</P>
              <P>
                <E T="03">Recipient</E>means the same as the term is defined in 45 CFR Part 1600.</P>
              <P>
                <E T="03">Substantial noncompliance</E>means either a substantial violation, as defined in this part, or a substantial failure, as indicated at § 1606.3(a) of this part.</P>
              <P>
                <E T="03">Substantial violation</E>means a violation that merits action under this part based on consideration of the following criteria by the Corporation:</P>
              <P>(1) The number of restrictions or requirements violated;</P>
              <P>(2) Whether the violation represents an instance of noncompliance with a substantive statutory or regulatory restriction or requirement, rather than an instance of noncompliance with a non-substantive technical or procedural requirement;</P>
              <P>(3) The extent to which the violation is part of a pattern of noncompliance with LSC requirements or restrictions;</P>
              <P>(4) The extent to which the recipient failed to take action to cure the violation when it became aware of the violation; and</P>
              <P>(5) Whether the violation was knowing and willful.</P>
              <P>
                <E T="03">Termination</E>means that a recipient's level of financial assistance under its grant or contract with the Corporation will be reduced in whole or in part in the amount of five percent or greater prior to the expiration of the funding term of a recipient's current grant or contract. A partial termination will affect only the level of funding for the current grant year, unless the Corporation provides otherwise in the final decision.</P>
              <P>
                <E T="03">Violation</E>means a violation by the recipient of the LSC requirements.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1606.3</SECTNO>
              <SUBJECT>Grounds for a termination or a limited reduction of funding.</SUBJECT>
              <P>(a) A grant or contract may be terminated in whole or in part when:</P>
              <P>(1) There has been a substantial violation by the recipient, and the violation occurred less than 5 years prior to the date the recipient receives a preliminary determination pursuant to § 1606.6(a) of this part; or</P>
              <P>(2) There has been a substantial failure by the recipient to provide high quality, economical, and effective legal assistance, as measured by generally accepted professional standards, the provisions of the LSC Act or LSC appropriations, or a rule, regulation, including 45 CFR 1634.9(a)(2), or guidelines or instructions issued by the Corporation.</P>
              <P>(b) The Corporation may impose a limited reduction of funding when the Corporation determines that there has been a substantial violation by the recipient but that termination of the recipient's grant, in whole or in part, is not warranted, and the violation occurred less than 5 years prior to the date the recipient receives a preliminary determination pursuant to § 1606.6(a) of this part.</P>
              <P>(c) A determination of whether there has been a substantial violation for the purposes of this part, and the magnitude of any termination, in whole or in part, or any limited reduction in funding, shall be based on consideration of the criteria set forth in the definition of “substantial violation” in § 1606.2 of this part.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1606.4</SECTNO>
              <SUBJECT>Grounds for debarment.</SUBJECT>
              <P>(a) The Corporation may debar a recipient, on a showing of good cause, from receiving an additional award of financial assistance from the Corporation.</P>

              <P>(b) As used in paragraph (a) of this section, “good cause” means:<PRTPAGE P="10095"/>
              </P>
              <P>(1) A termination of financial assistance to the recipient pursuant to part 1640 of this chapter;</P>
              <P>(2) A termination of financial assistance in whole of the most recent grant or contract of financial assistance;</P>
              <P>(3) The substantial violation by the recipient of the restrictions delineated in § 1610.2(a) and (b) of this chapter, provided that the violation occurred within 5 years prior to the receipt of the debarment notice by the recipient;</P>
              <P>(4) Knowing entry by the recipient into:</P>
              <P>(i) Any agreement or arrangement, including, but not limited to, a subgrant, subcontract, or other similar agreement, with an entity debarred by the Corporation during the period of debarment if so precluded by the terms of the debarment; or</P>
              <P>(ii) An agreement for professional services with an independent public accountant or other auditor debarred by the Corporation during the period of debarment if so precluded by the terms of the debarment; or</P>
              <P>(5) The filing of a lawsuit by a recipient, provided that the lawsuit:</P>
              <P>(i) Was filed on behalf of the recipient as plaintiff, rather than on behalf of a client of the recipient;</P>
              <P>(ii) Named the Corporation, or any agency or employee of a Federal, State, or local government as a defendant;</P>
              <P>(iii) Seeks judicial review of an action by the Corporation or such government agency that affects the recipient's status as a recipient of Federal funding, except for a lawsuit that seeks review of whether the Corporation or agency acted outside of its statutory authority or violated the recipient's constitutional rights; and</P>
              <P>(iv) Was initiated after December 23, 1998.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1606.5</SECTNO>
              <SUBJECT>Procedures.</SUBJECT>
              <P>(a) Before any final action is taken under this part, the recipient will be provided notice and an opportunity to be heard as set out in this part.</P>
              <P>(b) Prior to a preliminary determination involving a limited reduction of funding, the Corporation shall designate either the President or another senior Corporation employee to conduct any final review that is requested pursuant to § 1606.10 of this part. The Corporation shall ensure that the person so designated has had no prior involvement in the proceedings under this part so as to meet the criterion set out in § 1606.10(d) of this part.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1606.6</SECTNO>
              <SUBJECT>Preliminary determination and final decision.</SUBJECT>
              <P>(a) When the Corporation has made a preliminary determination of one or more of the following, the Corporation shall issue a written notice to the recipient and the Chair of the recipient's governing body: that a recipient's grant or contract should be terminated, that a limited reduction of funding shall be imposed, or that a recipient should be debarred. The notice shall:</P>
              <P>(1) State the substantial noncompliance that constitutes the grounds for the proposed action;</P>
              <P>(2) Identify, with reasonable specificity, any facts or documents relied upon as justification for the proposed action;</P>
              <P>(3) Inform the recipient of the proposed amount and proposed effective date for the proposed action;</P>
              <P>(4) Advise the recipient of its procedural rights for review of the proposed action under this part;</P>
              <P>(5) Inform the recipient of its right to receive interim funding pursuant to § 1606.13 of this part;</P>
              <P>(6) Specify what, if any, corrective action the recipient can take to avoid the proposed action; and</P>
              <P>(7) Summarize prior attempts, if any, for resolution of the substantial noncompliance.</P>
              <P>(b) If the recipient does not request review, as provided for in this part, before the relevant time limits have expired, then the Corporation may issue a final decision to the recipient. No further appeal or review will be available under this part.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1606.7</SECTNO>
              <SUBJECT>Corrective action, informal conference, review of written materials, and final decision.</SUBJECT>
              <P>(a) If the Corporation proposes a corrective action in the preliminary determination pursuant to § 1606.6(a)(6) of this part, then the recipient may accept and implement the corrective action, in lieu of an informal conference or submission of written materials under this section, subject to the following requirements:</P>
              <P>(1) Within 10 business days of receipt of the preliminary determination, the recipient may submit a draft compliance agreement to accept the terms of the proposed corrective action, which must include an implementation plan and timeline;</P>
              <P>(2) If the Corporation approves the draft compliance agreement, including any modifications suggested by the recipient or the Corporation, then it shall be memorialized in a final compliance agreement signed by the Corporation and the recipient, which shall stay these proceedings;</P>
              <P>(3) If the recipient completes the terms of the written compliance agreement in a time and manner that is satisfactory to the Corporation, then the Corporation shall withdraw the preliminary determination; and</P>
              <P>(4) If the Corporation determines at any time that the recipient has not presented an acceptable draft compliance agreement, or has not fulfilled any terms of the final compliance agreement, then the Corporation shall notify the recipient in writing. Within 15 calendar days of that notice, the Corporation shall modify or affirm the preliminary determination as a draft final decision. The draft final decision shall summarize these attempts at resolution. The draft final decision need not engage in a detailed analysis of the failure to resolve the substantial noncompliance.</P>
              <P>(b) A recipient may submit written materials in opposition to the preliminary determination, request an informal conference, or both, as follows:</P>
              <P>(1) For terminations or debarments, within 30 calendar days of receipt of the preliminary determination; or</P>
              <P>(2) For limited reductions in funding, within 10 business days of receipt of the preliminary determination.</P>
              <P>(c) Within 5 business days of receipt of a request for a conference, the Corporation shall notify the recipient of the time and place the conference will be held. Some or all of the participants in the conference may attend via telephone, unless the recipient requests an in-person meeting between the Corporation and at least one representative of the recipient. If the recipient requests an in-person meeting, then other participants may attend via telephone. Alternative means of participation other than the telephone are permissible at the sole discretion of the Corporation.</P>
              <P>(d) The informal conference shall be conducted by the Corporation employee who issued the preliminary determination or any other Corporation employee with a seniority level equivalent to the level of an office director or higher.</P>
              <P>(e) At the informal conference, the Corporation and the recipient shall both have an opportunity to state their case, seek to narrow the issues, explore the possibilities of settlement or compromise including implementation of corrective actions, and submit written materials.</P>

              <P>(f) If an informal conference is conducted or written materials are submitted in opposition to the proposed determination by the recipient, or both, the Corporation shall consider any written materials and any oral presentation or written materials submitted by the recipient at an informal conference. Based on any of these materials or the informal<PRTPAGE P="10096"/>conference, or both, the Corporation shall modify, withdraw, or affirm the preliminary determination through a draft final decision in writing, which shall be provided to the recipient within the later of 15 calendar days after the conclusion of the informal conference or after the recipient of written materials in opposition to the proposed determination (when no informal conference is requested). Except for decisions to withdraw the preliminary determination, the draft final decision shall include a summary of the issues raised in the informal conference and presented in any written materials. The draft final decision need not engage in a detailed analysis of all issues raised.</P>
              <P>(g) If the recipient does not request further process, as provided for in this part, then, after the relevant time limits have expired, the Corporation shall notify the recipient that no further appeal or review will be available under this part and may proceed to issue the final decision.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1606.8</SECTNO>
              <SUBJECT>Hearing for a termination or debarment.</SUBJECT>
              <P>(a) For terminations or debarments only, the recipient may make a written request for a hearing within the later of: 30 calendar days of its receipt of the preliminary determination, or 15 calendar days of receipt of the draft final decision issued under § 1606.7 of this part, as the case may be.</P>
              <P>(b) Within 10 business days after receipt of a request for a hearing, the Corporation shall notify the recipient in writing of the date, time, and place of the hearing and the names of the hearing officer and of the attorney who will represent the Corporation. The time, date, and location of the hearing may be changed upon agreement of the Corporation and the recipient.</P>
              <P>(c) A hearing officer shall be appointed by the President or designee and may be an employee of the Corporation. The hearing officer shall not have been involved in the current termination or debarment action, and the President or designee shall determine that the person is qualified to preside over the hearing as an impartial decision maker. An impartial decision maker is a person who has not formed a prejudgment on the case and does not have a pecuniary interest or personal bias in the outcome of the proceeding.</P>
              <P>(d) The hearing shall be scheduled to commence at the earliest appropriate date, ordinarily not later than 30 calendar days after the Corporation receives the notice required by paragraph (b) of this section.</P>
              <P>(e) The hearing officer shall preside over and conduct a full and fair hearing, avoid delay, maintain order, and insure that a record sufficient for full disclosure of the facts and issues is maintained.</P>
              <P>(f) The hearing shall be open to the public unless, for good cause and the interests of justice, the hearing officer determines otherwise.</P>
              <P>(g) The Corporation and the recipient shall be entitled to be represented by counsel or by another person.</P>
              <P>(h) At the hearing, the Corporation and the recipient each may present its case by oral or documentary evidence, conduct examination and cross-examination of witnesses, examine any documents submitted, and submit rebuttal evidence.</P>
              <P>(i) The hearing officer shall not be bound by the technical rules of evidence and may make any procedural or evidentiary ruling that may help to insure full disclosure of the facts, to maintain order, or to avoid delay. Irrelevant, immaterial, repetitious or unduly prejudicial matter may be excluded.</P>
              <P>(j) Official notice may be taken of published policies, rules, regulations, guidelines, and instructions of the Corporation, of any matter of which judicial notice may be taken in a Federal court, or of any other matter whose existence, authenticity, or accuracy is not open to serious question.</P>
              <P>(k) A stenographic or electronic record shall be made in a manner determined by the hearing officer, and a copy shall be made available to the recipient at no cost.</P>
              <P>(l) The Corporation shall have the initial burden to show grounds for a termination or debarment. The burden of persuasion shall then shift to the recipient to show by a preponderance of evidence on the record that its funds should not be terminated or that it should not be debarred.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1606.9</SECTNO>
              <SUBJECT>Recommended decision for a termination or debarment.</SUBJECT>
              <P>(a) For termination or debarment hearings under § 1606.8 of this part, within 20 calendar days after the conclusion of the hearing, the hearing officer shall issue a written recommended decision to the recipient and the Corporation, which may:</P>
              <P>(1) Terminate financial assistance to the recipient commencing as of a specific date;</P>
              <P>(2) Impose a limited reduction of funding commencing as of a specific date;</P>
              <P>(3) Continue the recipient's current level of financial assistance under the grant or contract, subject to any modification or condition that may be deemed necessary on the basis of information adduced at the hearing; or</P>
              <P>(4) Debar the recipient from receiving an additional award of financial assistance from the Corporation.</P>
              <P>(b) The recommended decision shall contain findings of the significant and relevant facts and shall state the reasons for the decision. Findings of fact shall be based solely on the record of, and the evidence adduced at the hearing or on matters of which official notice was taken.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1606.10</SECTNO>
              <SUBJECT>Final decision for a termination, debarment, or limited reduction of funding.</SUBJECT>
              <P>(a) If neither the Corporation nor the recipient requests review by the President of a draft final decision pursuant to § 1606.7 of this part or a recommended decision pursuant to § 1606.9, as provided for in this part, within 10 business days after receipt by the recipient, then the Corporation shall issue to the recipient a final decision containing either the draft final decision or the recommended decision, as the case may be. No further appeal or review will be available under this part.</P>
              <P>(b) The recipient or the Corporation may seek review by the President of a draft final decision or a recommended decision. A request shall be made in writing within 10 business days after receipt of the draft final decision or recommended decision by the party seeking review and shall state in detail the reasons for seeking review.</P>
              <P>(c) The President's review shall be based solely on the administrative record of the proceedings, including the appeal to the President, and any additional submissions, either oral or in writing, that the President may request. A recipient shall be given a copy of, and an opportunity to respond to, any additional submissions made to the President. All submissions and responses made to the President shall become part of the administrative record. Upon request, the Corporation shall provide a copy of the administrative record to the recipient.</P>

              <P>(d) For an appeal of a draft final decision involving a limited reduction of funding pursuant to § 1606.7 of this part (for which there is no right to a hearing under § 1606.8 of this part) the President may not review the appeal if the President has had prior involvement in the proceedings under this part. If the President cannot review the appeal, or the President chooses not to do so, then the appeal shall be reviewed by either the individual designated to do so pursuant to § 1606.5(b) of this part, or by another senior Corporation employee designated by the President who has not<PRTPAGE P="10097"/>had prior involvement in the proceedings under this part.</P>
              <P>(e) As soon as practicable after receipt of the request for review of a draft final decision or a recommended decision, but not later than 30 calendar days thereafter, the President or designee shall adopt, modify, or reverse the draft final decision or the recommended decision, or direct further consideration of the matter. In the event of modification or reversal of a recommended decision pursuant to § 1606.9 of this part, this decision shall conform to the requirements of § 1606.9(b) of this part.</P>
              <P>(f) The decision of the President or designee under this section shall become final upon receipt by the recipient.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1606.11</SECTNO>
              <SUBJECT>Qualifications on hearing procedures.</SUBJECT>
              <P>(a) Except as modified by paragraph (c) of this section, the hearing rights set out in §§ 1606.6 through 1606.10 of this part shall apply to any action to debar a recipient or to terminate a recipient's funding.</P>
              <P>(b) The Corporation may simultaneously take action to debar and terminate a recipient within the same hearing procedure that is set out in §§ 1606.6 through 1606.10 of this part. In such a case, the same hearing officer shall oversee both the termination and debarment actions in the same hearing.</P>
              <P>(c) If the Corporation does not simultaneously take action to debar and terminate a recipient under paragraph (b) of this section and initiates a debarment action based on a prior termination under § 1606.4(b)(1) or (2), the hearing procedures set out in § 1606.6 through 1606.10 of this part shall not apply. Instead:</P>
              <P>(1) The President shall appoint a hearing officer, as described in § 1606.8(c), to review the matter and make a written recommended decision on debarment.</P>
              <P>(2) The hearing officer's recommended decision shall be based solely on the information in the administrative record of the termination proceedings providing grounds for the debarment and any additional submissions, either oral or in writing, that the hearing officer may request. The recipient shall be given a copy of and an opportunity to respond to any additional submissions made to the hearing officer. All submissions and responses made to the hearing officer shall become part of the administrative record.</P>
              <P>(3) If neither party appeals the hearing officer's recommended decision within 10 business days of receipt of the recommended decision, the decision shall become final and the final decision shall be issued by the Corporation to the recipient within 5 business days.</P>
              <P>(4) Either party may appeal the recommended decision to the President who shall review the matter and issue a final written decision pursuant to § 1606.9(b).</P>
              <P>(d) All final debarment decisions shall state the effective date of the debarment and the period of debarment, which shall be commensurate with the seriousness of the cause for debarment but shall not be for longer than 6 years.</P>
              <P>(e) The Corporation may reverse a debarment decision upon request for the following reasons:</P>
              <P>(1) Newly discovered material evidence;</P>
              <P>(2) Reversal of the conviction or civil judgment upon which the debarment was based;</P>
              <P>(3) Bona fide change in ownership or management of a recipient;</P>
              <P>(4) Elimination of other causes for which the debarment was imposed; or</P>
              <P>(5) Other reasons the Corporation deems appropriate.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1606.12</SECTNO>
              <SUBJECT>Time and waiver.</SUBJECT>
              <P>(a) Except for the 6-year time limit for debarments in § 1606.11(d) of this part, any period of time provided in these rules may, upon good cause shown and determined, be extended in writing:</P>
              <P>(1) By the Corporation, unless a hearing officer has been appointed;</P>
              <P>(2) By the hearing officer, until the recommended decision has been issued; or</P>
              <P>(3) By the President at any time.</P>
              <P>(b) Failure by the Corporation to meet a time requirement of this part does not preclude the Corporation from terminating a recipient's grant or contract with the Corporation or imposing a limited reduction of funding.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1606.13</SECTNO>
              <SUBJECT>Interim and other funding, reprogramming, implementation.</SUBJECT>
              <P>(a) Pending the completion of termination or limited reduction of funding proceedings under this part, the Corporation shall provide the recipient with the level of financial assistance provided for under its current grant or contract for financial assistance with the Corporation.</P>
              <P>(b) After a final decision has been made to terminate a recipient's grant or contract or to impose a limited reduction of funding, the recipient loses all rights to the terminated or reduced funds.</P>
              <P>(c) After a final decision has been made to terminate a recipient's grant or contract, the Corporation may authorize closeout or transition funding, or both, if necessary to enable the recipient to close or transfer current matters in a manner consistent with the recipient's professional responsibilities to its present clients.</P>
              <P>(d) The Corporation has sole discretion to determine the manner in which the final decision is implemented. The Corporation's discretion includes, but is not limited to the decision to pro-rate the amount of funds reduced over the remaining disbursements in the funding term or deduct the sum in a single disbursement, or any other method the Corporation deems appropriate.</P>
              <P>(e) Funds recovered by the Corporation pursuant to a termination or limited reduction of funding shall be reallocated by the Corporation for basic field purposes at its sole discretion.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1606.14</SECTNO>
              <SUBJECT>Recompetition.</SUBJECT>
              <P>After a final decision has been issued by the Corporation terminating financial assistance to a recipient in whole for any service area, the Corporation shall implement a new competitive bidding process for the affected service area. Until a new recipient has been awarded a grant pursuant to such process, the Corporation shall take all practical steps to ensure the continued provision of legal assistance in the service area pursuant to § 1634.11 of this part.</P>
            </SECTION>
          </PART>
        </REGTEXT>
        <REGTEXT PART="1614" TITLE="45">
          <PART>
            <HD SOURCE="HED">PART 1614—PRIVATE ATTORNEY INVOLVEMENT</HD>
          </PART>
          <AMDPAR>2. The authority citation for part 1614 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>Sec. 1007(a)(2)(C) and sec. 1007(a)(3); (42 U.S.C. 2996f(a)(2)(C) and 42 U.S.C. 2996f(a)(3)).</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="1614" TITLE="45">
          <AMDPAR>3. Amend § 1614.7 by revising paragraph (b) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 1614.7</SECTNO>
            <SUBJECT>Failure to comply.</SUBJECT>
            <STARS/>
            <P>(b) The withholding of funds under this section shall not be construed as any action under 45 CFR part 1606.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="1618" TITLE="45">
          <AMDPAR>4. Revise part 1618 to read as follows:</AMDPAR>
          <PART>
            <HD SOURCE="HED">PART 1618—ENFORCEMENT PROCEDURES</HD>
            <CONTENTS>
              <SECHD>Sec.</SECHD>
              <SECTNO>1618.1</SECTNO>
              <SUBJECT>Purpose.</SUBJECT>
              <SECTNO>1618.2</SECTNO>
              <SUBJECT>Definition.</SUBJECT>
              <SECTNO>1618.3</SECTNO>
              <SUBJECT>Complaints.</SUBJECT>
              <SECTNO>1618.4</SECTNO>
              <SUBJECT>Duties of recipients.</SUBJECT>
              <SECTNO>1618.5</SECTNO>
              <SUBJECT>Duties of the Corporation.</SUBJECT>
            </CONTENTS>
            <AUTH>
              <HD SOURCE="HED">Authority:</HD>
              <P>42 U.S.C. 2996e(b)(1), 2996e(b)(2), 2996e(b)(5), 2996f(a)(3), 2996f(d), and 2996g(e).</P>
            </AUTH>
            <SECTION>
              <PRTPAGE P="10098"/>
              <SECTNO>§ 1618.1</SECTNO>
              <SUBJECT>Purpose.</SUBJECT>
              <P>In order to ensure uniform and consistent interpretation and application of the provisions of the LSC Act, the Corporation's appropriations act or other law applicable to LSC funds, a Corporation rule, regulation, guideline or instruction, or the terms and conditions of the recipient's grant or contract with the Corporation, and to prevent a question of whether these requirements have been violated from becoming an ancillary issue in any case undertaken by a recipient, this part establishes a systematic procedure for enforcing compliance with them.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1618.2</SECTNO>
              <SUBJECT>Definitions.</SUBJECT>
              <P>
                <E T="03">LSC requirements</E>means the provisions of the LSC Act, the Corporation's appropriations act or other law applicable to LSC funds, a Corporation rule, regulation, guideline or instruction, or the terms or conditions of the recipient's grant or contract with the Corporation.</P>
              <P>
                <E T="03">Violation</E>means a violation by the recipient of the LSC requirements.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1618.3</SECTNO>
              <SUBJECT>Complaints.</SUBJECT>
              <P>A complaint of a violation by a recipient or an employee of a recipient may be made to the recipient, the State Advisory Council, or the Corporation.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1618.4</SECTNO>
              <SUBJECT>Duties of recipients.</SUBJECT>
              <P>(a) A recipient shall:</P>
              <P>(1) Advise its employees of their responsibilities under the LSC requirements;</P>
              <P>(2) Establish procedures, consistent with the notice and hearing requirements of section 1011 of the LSC Act, for determining whether an employee has committed a violation and whether the violation merits a sanction based on consideration of the totality of the circumstances; and</P>
              <P>(3) Establish a policy for determining the appropriate sanction to be imposed for a violation, including:</P>
              <P>(i) Administrative reprimand if a violation is found to be minor and unintentional, or otherwise affected by mitigating circumstances;</P>
              <P>(ii) Suspension and termination of employment; and</P>
              <P>(iii) Other sanctions appropriate for enforcement of the LSC requirements.</P>
              <P>(b) Before suspending or terminating the employment of any person for a violation, a recipient shall consult the Corporation to ensure that its interpretation of these requirements is consistent with Corporation policy.</P>
              <P>(c) This section provides procedural requirements between the Corporation and recipients. It does not create rights for recipient employees.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1618.5</SECTNO>
              <SUBJECT>Duties of the Corporation.</SUBJECT>
              <P>(a) Whenever the Corporation learns that there is reason to believe that a recipient or a recipient's employee may have committed a violation, the Corporation shall investigate the matter promptly and attempt to resolve it through informal consultation with the recipient. Such actions may be limited to determining if the recipient is sufficiently investigating and resolving the matter itself.</P>
              <P>(b) Whenever there is substantial reason to believe that a recipient has persistently or intentionally violated the LSC requirements, or, after notice, has failed to take appropriate remedial or disciplinary action to ensure compliance by its employees with the LSC requirements, and attempts at informal resolution have been unsuccessful, the Corporation may proceed to suspend or terminate financial support of the recipient, or impose a limited reduction in funding, pursuant to the procedures set forth in parts 1623 and 1606, or may take other action to enforce compliance with the LSC requirements.</P>
              <P>(c) Whenever the Corporation determines that a recipient has committed a violation, that corrective actions by the recipient are required to remedy the violation and/or prevent recurrence of the violation, and that imposition of special grant conditions are needed prior to the next grant renewal or competition for the service area, the Corporation may immediately impose Special Grant Conditions on the recipient to require completion of those corrective actions.</P>
            </SECTION>
          </PART>
        </REGTEXT>
        <REGTEXT PART="1623" TITLE="45">
          <AMDPAR>5. Revise part 1623 to read as follows:</AMDPAR>
          <PART>
            <HD SOURCE="HED">PART 1623—SUSPENSION PROCEDURES</HD>
            <CONTENTS>
              <SECHD>Sec.</SECHD>
              <SECTNO>1623.1</SECTNO>
              <SUBJECT>Purpose.</SUBJECT>
              <SECTNO>1623.2</SECTNO>
              <SUBJECT>Definitions.</SUBJECT>
              <SECTNO>1623.3</SECTNO>
              <SUBJECT>Grounds for suspension.</SUBJECT>
              <SECTNO>1623.4</SECTNO>
              <SUBJECT>Suspension procedures.</SUBJECT>
              <SECTNO>1623.5</SECTNO>
              <SUBJECT>Time extensions and waiver.</SUBJECT>
              <SECTNO>1623.6</SECTNO>
              <SUBJECT>Interim funding.</SUBJECT>
            </CONTENTS>
            <AUTH>
              <HD SOURCE="HED">Authority:</HD>
              <P>42 U.S.C. 2996e(b)(1), 2996f(a)(3), and 2996f(d); Pub. L. 105-119, Title V, Secs. 501(b), 502, and 503, 111 Stat. 2440, 2510-11; Pub. L. 104-134, Title V, Secs. 503(f) and 509(c), 110 Stat. 1321, 1321-53, 1321-58, and 1321-59.</P>
            </AUTH>
            <SECTION>
              <SECTNO>§ 1623.1</SECTNO>
              <SUBJECT>Purpose.</SUBJECT>
              <P>The purpose of this rule is to:</P>
              <P>(a) Ensure that the Corporation is able to take prompt action when necessary to safeguard LSC funds or to ensure the compliance of a recipient with applicable provisions of law, or a rule, regulation, guideline or instruction issued by the Corporation, or the terms and conditions of a recipient's grant or contract with the Corporation; and</P>
              <P>(b) Provide procedures for prompt review that will ensure informed deliberation by the Corporation when it has made a proposed determination that financial assistance to a recipient should be suspended.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1623.2</SECTNO>
              <SUBJECT>Definitions.</SUBJECT>
              <P>For the purposes of this part the definitions in 45 CFR part 1606 shall apply and also:</P>
              <P>
                <E T="03">Suspension</E>means an action taken during the term of the recipient's current year's grant or contract with the Corporation that withholds financial assistance to a recipient, in whole or in part, until the end of the suspension period pending prompt corrective action by the recipient or a decision by the Corporation to initiate termination proceedings.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1623.3</SECTNO>
              <SUBJECT>Grounds for suspension.</SUBJECT>
              <P>(a) Financial assistance provided to a recipient may be suspended when the Corporation determines that there has been a substantial violation by the recipient of the LSC requirements, and the Corporation has reason to believe that prompt action is necessary to:</P>
              <P>(1) Safeguard LSC funds; or</P>
              <P>(2) Ensure immediate corrective action necessary to bring a recipient into compliance with an applicable provision of law, or a rule, regulation, guideline or instruction issued by the Corporation, or the terms and conditions of the recipient's grant or contract with the Corporation.</P>
              <P>(b) Financial assistance provided to a recipient may also be suspended by the Corporation pursuant to a recommendation by the Office of Inspector General when the recipient has failed to have an acceptable audit in accordance with the guidance promulgated by the Corporation's Office of Inspector General.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1623.4</SECTNO>
              <SUBJECT>Suspension procedures.</SUBJECT>
              <P>(a) Prior to a preliminary determination involving a suspension of funding, the Corporation shall designate either the President or another senior Corporation employee to conduct any final review that is requested pursuant this part. The Corporation shall ensure that the person so designated has had no prior involvement in the proceedings under this part so as to meet the criterion of impartiality described in this section.</P>

              <P>(b) When the Corporation has made a proposed determination, based on the grounds set out in § 1623.3 of this part, that financial assistance to a recipient should be suspended, the Corporation<PRTPAGE P="10099"/>shall serve a written proposed determination on the recipient. The proposed determination shall:</P>
              <P>(1) State the grounds and effective date for the proposed suspension;</P>
              <P>(2) Identify, with reasonable specificity, any facts or documents relied upon as justification for the suspension;</P>
              <P>(3) Specify what, if any, prompt corrective action the recipient can take to avoid or end the suspension;</P>
              <P>(4) Advise the recipient that it may request, within 5 business days of receipt of the proposed determination, an informal meeting with the Corporation at which it may attempt to show that the proposed suspension should not be imposed; and</P>
              <P>(5) Advise the recipient that, within 10 business days of its receipt of the proposed determination and without regard to whether it requests an informal meeting, it may submit written materials in opposition to the proposed suspension.</P>
              <P>(c) If the recipient requests an informal meeting with the Corporation, the Corporation shall designate the time and place for the meeting. The meeting shall occur within 5 business days after the recipient's request is received.</P>
              <P>(d) The informal meeting shall be conducted by the Corporation employee who issued the preliminary determination or any other Corporation employee with a seniority level at, or equivalent to, the level of an office director or higher.</P>
              <P>(e) At the informal meeting, the Corporation and the recipient shall both have an opportunity to state their case, seek to narrow the issues, explore the possibilities of settlement or compromise including implementation of corrective actions, and submit written materials.</P>
              <P>(f) The Corporation shall consider any written materials submitted by the recipient in opposition to the proposed suspension and any oral presentation or written materials submitted by the recipient at an informal meeting. If, after considering such materials, the Corporation determines that the recipient has failed to show that the suspension should not become effective, the Corporation may issue a written final determination to suspend financial assistance to the recipient in whole or in part and under such terms and conditions the Corporation deems appropriate and necessary. The final determination shall include a summary of the issues raised in the informal conference and presented in any written materials. The final determination need not engage in a detailed analysis of all issues raised.</P>
              <P>(g) The final determination shall be promptly transmitted to the recipient in a manner that verifies receipt of the determination by the recipient, and the suspension shall become effective when the final determination is received by the recipient or on such later date as is specified therein.</P>
              <P>(h) If a suspension lasts for more than 30 days, then the recipient may seek review of the suspension by the President. A request may be made in writing on the thirty-first day or any day thereafter, and shall state, in detail, the reasons for seeking review.</P>
              <P>(1) The President may not review the suspension appeal if the President has had prior involvement in the suspension proceedings. If the President cannot review, or the President chooses not to do so, then the appeal shall be reviewed by either the individual designated to do so pursuant to § 1623.4(a) of this part, or by another senior Corporation employee designated by the President who has not had prior involvement in the suspension proceedings.</P>
              <P>(2) The President's review shall be based on the administrative record of the proceedings, including the appeal to the President, and any additional submissions, either oral or in writing that the President may request. A recipient shall be given a copy of, and an opportunity to respond to, any additional submissions made to the President. All submissions and responses made to the President shall become part of the administrative record. Upon request, the Corporation shall provide a copy of the administrative record to the recipient.</P>
              <P>(3) The President shall affirm, modify, or terminate the suspension through a suspension appeal decision within 15 calendar days of receipt of the appeal by the Corporation, unless the Corporation and the recipient agree to a later date.</P>
              <P>(i) The Corporation may at any time rescind or modify the terms of the final determination to suspend and, on written notice to the recipient, may reinstate the suspension without further proceedings under this part.</P>
              <P>(j) Except as provided in § 1623.4(k) of this part, the total time of a suspension shall not exceed 90 calendar days, unless the Corporation and the recipient agree to a continuation of the suspension without further proceedings under this part.</P>
              <P>(k) When the suspension is based on the grounds in § 1623.3(b) of this part, a recipient's funds may be suspended until an acceptable audit is completed. No appeal to the President will be available for audit-based suspensions pursuant to § 1623.3(b).</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1623.5</SECTNO>
              <SUBJECT>Time extensions and waiver.</SUBJECT>
              <P>(a) Except for the time limits in § 1623.4(i) and (j), any period of time provided in this part may be extended by the Corporation for good cause. Requests for extensions of time shall be considered in light of the overall objective that the procedures prescribed by this part ordinarily shall be concluded within 30 calendar days of the service of the proposed determination.</P>
              <P>(b) Any other provision of this part may be waived or modified by agreement of the recipient and the Corporation for good cause.</P>
              <P>(c) Failure by the Corporation to meet a time requirement of this part shall not preclude the Corporation from suspending a recipient's grant or contract with the Corporation.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1623.6</SECTNO>
              <SUBJECT>Interim funding.</SUBJECT>
              <P>(a) Pending the completion of suspension proceedings under this part, the Corporation shall provide the recipient with the level of financial assistance provided for under its current grant or contract with the Corporation.</P>
              <P>(b) Funds withheld pursuant to a suspension shall be released to the recipient at the end of the suspension period.</P>
            </SECTION>
          </PART>
        </REGTEXT>
        <SIG>
          <DATED>Dated: February 6, 2013.</DATED>
          <NAME>Victor M. Fortuno.</NAME>
          <TITLE>Vice President &amp; General Counsel.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03241 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 7050-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
        <CFR>47 CFR Part 1</CFR>
        <DEPDOC>[CG Docket No. 12-129; FCC 12-129]</DEPDOC>
        <SUBJECT>Implementation of the Middle Class Tax Relief and Job Creation Act of 2012; Establishment of a Public Safety Answering Point Do-Not-Call Registry</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Communications Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Correcting amendments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>This document contains a correction to the final regulations of the Commission's rules, which were published in the<E T="04">Federal Register</E>on November 29, 2012, 77 FR 71131. The final regulations establish a do-not-call registry for public safety answering points (PSAP) and prohibit the use of automatic dialing equipment to contact those registered numbers.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Effective February 13, 2013.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Richard D. Smith, Consumer and<PRTPAGE P="10100"/>Governmental Affairs Bureau at (717) 338-2797 or email<E T="03">Richard.Smith@fcc.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>The Federal Communications Commission published a document amending 47 CFR 1.80 in the<E T="04">Federal Register</E>on November 29, 2012, (77 FR 71131). The amended rules are necessary to implement the enforcement provisions of the Middle Class Tax Relief and Job Creation Act of 2012 as applicable to the PSAP Do-Not-Call registry.</P>
        <HD SOURCE="HD1">Need for Correction</HD>
        <P>As published, the final regulations inadvertently created two § 1.80(b)(7)'s in the Commission's rules and needs to be corrected accordingly.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 47 CFR Part 1</HD>
          <P>Administrative practice and procedure.</P>
        </LSTSUB>
        <SIG>
          <FP>Federal Communications Commission.</FP>
          <NAME>Marlene H. Dortch,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
        <P>Accordingly, 47 CFR part 1 is corrected by making the following correcting amendments:</P>
        <REGTEXT PART="1" TITLE="47">
          <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), and 309, the Middle Class Tax Relief and Job Creation Act of 2012, Pub. L. 112-96, and 47 U.S.C. 1473.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="1" TITLE="47">
          <SUBPART>
            <HD SOURCE="HED">Subpart A—General Rules of Practice and Procedure</HD>
          </SUBPART>
          <AMDPAR>2. Amend § 1.80 by redesignating the second paragraph (b)(7) as paragraph (b)(9) and republishing the heading of newly redesignated paragraph (b)(9) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 1.80</SECTNO>
            <SUBJECT>Forfeiture proceedings.</SUBJECT>
            <P>(b) * * *</P>
            <P>(9)<E T="03">Inflation adjustments to the maximum forfeiture amount.</E>* * *</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03230 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6712-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
        <CFR>47 CFR Part 54</CFR>
        <DEPDOC>[WC Docket Nos. 10-90 and 05-337; DA 12-1777]</DEPDOC>
        <SUBJECT>Data Specifications for Collecting Study Area Boundaries</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Communications Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule; announcement of effective date.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>In this document, the Federal Communications Commission (Commission) announces that the Office of Management and Budget (OMB) has approved, until July 31, 2013, the information collection associated with the Commission's Connect America Fund; High-Cost Universal Service<E T="03"/>Support, Report and Order, (<E T="03">Order</E>), released on November 6, 2012. The Commission submitted a request for approval of a new collection under control number 3060-1181 to the OMB for review and approval, as required by the Paperwork Reduction Act (PRA) of 1995 (44 U.S.C. 3501-3520). This notice is consistent with the<E T="03">Order,</E>which stated that the Commission would publish a document in the<E T="04">Federal Register</E>announcing the effective date of those rules once it receives OMB approval.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Paragraph 16 and Appendix A of document DA 12-1777, published at 78 FR 5750, January 28, 2013, are effective February 27, 2013.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Chelsea Fallon, Assistant Division Chief, Wireline Competition Bureau, at (202) 418-7991.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>This document announces that, on January 23, 2013, OMB approved, for a period of six months, the information collection requirements contained in the Commission's<E T="03">Order,</E>FCC 12-1777, published at 78 FR 5750, January 28, 2013. The OMB Control Number is 3060-1181. The Commission publishes this notice as an announcement of the effective date of paragraph 16 and Appendix A of document DA 12-1777. If you have any comments on the burden estimates listed below, or how the Commission can improve the collections and reduce any burdens caused thereby, please contact Judith Boley-Herman, Federal Communications Commission, Room 1-B441, 445 12th Street SW., Washington, DC 20554. Please include the OMB Control Number, 3060-1181, in your correspondence. The Commission also will accept comments via email. Please send them to<E T="03">PRA@fcc.gov.</E>
        </P>

        <P>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 and Governmental Affairs Bureau at (202) 418-0530 (voice), (202) 418-0432 (TTY).</P>
        <HD SOURCE="HD1">Synopsis</HD>
        <P>As required by the Paperwork Reduction Act of 1995 (44 U.S.C. 3507), the FCC is notifying the public that it received OMB approval on January 23, 2013, for the information collection requirements contained in paragraph 16 and Appendix A of document DA 12-1777.</P>
        <P>Under 5 CFR part 1320, an agency may not conduct or sponsor a collection of information unless it displays a current, valid OMB Control Number.</P>
        <P>No person shall be subject to any penalty for failing to comply with a collection of information subject to the Paperwork Reduction Act that does not display a current, valid OMB Control Number. The OMB Control Number is 3060-1181.</P>
        <P>The foregoing notice is required by the Paperwork Reduction Act of 1995, Public Law 104-13, October 1, 1995, and 44 U.S.C. 3507.</P>
        <P>The total annual reporting burdens and costs for the respondents are as follows:</P>
        <P>
          <E T="03">OMB Control Number:</E>3060-1181.</P>
        <P>
          <E T="03">OMB Approval Date:</E>January 23, 2013.</P>
        <P>
          <E T="03">OMB Expiration Date:</E>July 31, 2013.</P>
        <P>
          <E T="03">Title:</E>Study Area Boundary Data Reporting in Esri Shapefile Format, DA 12-1777.</P>
        <P>
          <E T="03">Form Number:</E>N/A.</P>
        <P>
          <E T="03">Respondents:</E>Incumbent local exchange carriers, and state regulatory entities.</P>
        <P>
          <E T="03">Number of Respondents and Responses:</E>1,443 respondents; 1,443 responses.</P>
        <P>
          <E T="03">Estimated Time per Response:</E>26 hours.</P>
        <P>
          <E T="03">Frequency of Response:</E>Annually if changes to study area boundaries; biannually for recertification or previously submitted data.</P>
        <P>
          <E T="03">Obligation to Respond:</E>Required. Statutory authority for this information collection is contained in 47 U.S.C. 254(b).</P>
        <P>
          <E T="03">Total Annual Burden:</E>7,924 hours for in-house work for large incumbent local exchange carriers</P>
        <P>
          <E T="03">Total Annual Cost:</E>$705,935.00 contracting costs for small incumbent local exchange carriers.</P>
        <P>
          <E T="03">Nature and Extent of Confidentiality:</E>The Commission is not requesting that<PRTPAGE P="10101"/>respondents submit confidential information to the Commission. Also, respondents may request materials or information submitted to the Commission be withheld from public inspection under 47 CFR 0.459 of the Commission's rules.</P>
        <P>
          <E T="03">Needs and Uses:</E>In November 2012, the Wireline Competition Bureau of the Federal Communications Commission adopted a<E T="03">Report and Order</E>(<E T="03">Order</E>), in WC Docket No. 10-90; WC Docket No. 05-337; DA 12-1777, 78 FR 5750, Connect America Fund; High-Cost Universal Service Support.</P>
        <P>The<E T="03">Order</E>adopts data specifications for collecting study area boundaries for purposes of implementing various reforms adopted as part of the<E T="03">USF/ICC Transformation Order,</E>76 FR 73830, November 29, 2011. In the<E T="03">USF/ICC Transformation FNPRM,</E>76 FR 78384, December 16, 2011, the Commission sought comment on a process to reduce support where such an unsubsidized competitor offers voice and broadband service to a substantial majority, but not 100 percent of the study area. Study area boundaries are needed to determine whether unsubsidized competitors offer service within all or a portion of an incumbent's study area</P>
        <P>The<E T="03">Order</E>requires incumbent local exchange carriers (LECs) to submit esri shapefiles of their study area boundaries, with each submitted shapefile representing a single study area in each state that the incumbent LEC serves. The shapefile for each study area must depict each exchange within the study area as a closed, non-overlapping polygon. Each exchange-area polygon must constitute one record in the shapefile and must contain associated data with certain attributes used to identify the exchange, such as the exchange name and CLLI (Common Language Location Identifier) code. The Bureau will collect study area boundary data at the exchange level so that it can distinguish those exchanges that are subject to “frozen” support levels from those that are not, and so that the data can be updated to reflect any exchanges that have been transferred from one incumbent LEC to another.</P>
        <P>The<E T="03">Order</E>finds that collecting study area boundary data in an esri shapefile format best balances the need for accurate and timely data with the goal of minimizing burdens on providers. The<E T="03">Order</E>states that the esri shapefile is the best among possible data formats. Since its introduction in the 1990s, the esri shapefile has become the industry standard for storing, depicting, and analyzing spatial data. As a result, there are multiple geographic information system (GIS) platforms capable of creating and managing esri shapefiles, and multiple software programs can convert spatial data stored in other formats (such as MapInfo) to an esri shapefile format. Incumbent LECs that do not already have esri shapefiles of their study area boundaries may either use software and information technology, and/or rely on the expertise of consultants, to develop a shapefile based on the presumably known locations of their physical plant and their customers. Thus, the benefits gained by requiring incumbent LECs to provide and verify esri shapefiles warrant the potential burdens imposed. Incumbent LECs or other entities are not expected to conduct physical surveys in order to produce the degree of accuracy required by the data specification. Incumbent LECs reasonably can be expected to know where they offer services and thus should be able to create and submit an esri shapefile to the degree of accuracy required based largely on existing information.</P>
        <P>State entities are well situated to assist incumbent LECs with their responsibilities under this R&amp;O. Involvement of state entities that undertake or assist with this data collection effort could reduce the burden on incumbent LECs and on Commission staff, particularly because some states already have digitized service territory boundaries. State entities wishing to submit such data should notify the Commission in writing of their intention to do so and submit that notice to WC Docket No. 10-90 via the Commission's Electronic Comment Filing System (ECFS). The Bureau will release a Public Notice identifying the deadlines for these notices (as well as the deadlines for the shapefile submissions and incumbent LEC certifications). In cases where a state entity uploads data to the Commission-sponsored Web site on behalf of one or more incumbent LECs, each incumbent LEC whose data are submitted by the state must log into the Web site to review the shapefile. If the incumbent LEC has a reasonable basis to conclude the shapefile is correct, the incumbent LEC can certify and submit the data using the same web interface. The reporting obligation set forth in the Order ultimately rests with incumbent LECs; state entities may not certify as to the accuracy of the data on behalf of incumbent LECs. If the incumbent LEC cannot certify that the data submitted by the state entities are correct, the incumbent LEC must so notify the Bureau and upload corrected data, either on its own or in conjunction with the state entity that filed it. The incumbent LEC can then certify that the study area boundary data are accurate.</P>
        <P>After reviewing and, if necessary, correcting the study area boundary data submitted by itself or a state entity, each incumbent LEC must certify the accuracy of the data. An official of the firm, such as a corporate officer, managing partner, or sole proprietor, must provide an electronic signature certifying that he or she has examined the study area boundary shapefile and that, to the best of his or her knowledge, information, and belief, the data contained in the shapefile are accurate and correct. The certifying official may be different from the GIS specialist or other individual who developed the study area boundary shapefile, and the web interface will allow filers to enter contact information for both the certifying official and the individual most knowledgeable about the spatial data.</P>
        <P>Once the shapefiles have been submitted and certified, the Bureau will review the study area boundaries and resolve any voids and overlaps. Overlap areas would be those shown to be served by more than one incumbent LEC, while void areas would be those shown to be served by no incumbent LEC. The Bureau will attempt to distinguish unpopulated void areas from populated void areas that are likely to be served by some incumbent LEC, in which case an error in the submitted data may need to be resolved. The Bureau may also seek help from state commissions to resolve gaps, voids, and overlap issues. During review, if boundary overlaps or void areas are found in the submitted boundary data, the Bureau will contact the filer(s) to resolve such issues. Once these issues are resolved, the Bureau will ask incumbent LECs to recertify the new, corrected boundaries. When a complete set of the reconciled boundaries has been compiled the study area boundary data will be published.</P>

        <P>Incumbent LECs must provide updated data when their study area boundaries change. Incumbent LECs and/or state entities must submit updated data by March 15 of each year, beginning the year following the initial data submissions, showing any changes made by December 31 of the previous year. The incumbent LEC is responsible for making any necessary changes and for filing the revised shapefile. The changes cannot be made using the web interface itself; incumbent LECs will need to modify the shapefile. However, incumbent LECs can upload a revised shapefile to the same Web site used for the original filing. In addition, all incumbent LECs must recertify their<PRTPAGE P="10102"/>study area boundary data every two years. Filers will need to examine, through the web interface described below, the boundary data previously submitted, and then either certify that they are correct or submit revised data.</P>
        <P>In the near future, the Bureau will issue a Public Notice providing detailed instructions and announcing the deadline for the submission of data and providing further filing information. The Commission plans to submit information required to obtain OMB review and approval to extend approval of this collection.</P>
        <SIG>
          <FP>Federal Communications Commission.</FP>
          <NAME>Lisa Gelb,</NAME>
          <TITLE>Deputy Bureau Chief, Wireline Competition Bureau.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03328 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6712-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <CFR>50 CFR Part 622</CFR>
        <DEPDOC>[Docket No. 120403249-2492-02]</DEPDOC>
        <RIN>RIN 0648-XC437</RIN>
        <SUBJECT>Fisheries of the Caribbean, Gulf of Mexico, and South Atlantic; Snapper-Grouper Resources of the South Atlantic; Trip Limit Reduction</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Temporary rule; trip limit reduction.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>NMFS reduces the commercial trip limit for golden tilefish in the South Atlantic to 300 lb (136 kg), gutted weight, per trip in or from the exclusive economic zone (EEZ). This trip limit reduction is necessary to protect the South Atlantic golden tilefish resource.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>

          <P>This rule is effective 12:01 a.m., local time, February 18, 2013, through December 31, 2013, unless changed by subsequent notification in the<E T="04">Federal Register</E>.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Catherine Hayslip, telephone: 727-824-5305, or email:<E T="03">Catherine.Hayslip@noaa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The snapper-grouper fishery includes golden tilefish in the South Atlantic and is managed under the Fishery Management Plan for the Snapper-Grouper Resources of the South Atlantic (FMP). The FMP was prepared by the South Atlantic Fishery Management Council and is implemented under the authority of the Magnuson-Stevens Fishery Conservation and Management Act (Magnuson-Stevens Act) by regulations at 50 CFR part 622.</P>
        <P>Under 50 CFR 622.44(c)(2), NMFS is required to reduce the trip limit in the commercial sector for golden tilefish from 4,000 lb (1,814 kg) to 300 lb (136 kg) per trip when 75 percent of the fishing year quota is met prior to September 1, by filing a notification to that effect with the Office of the Federal Register. As implemented by the final rule for Regulatory Amendment 12 (77 FR 61295, October 9, 2012), the commercial quota for golden tilefish in the South Atlantic is 541,295 lb (245,527 kg), gutted weight, as specified in 50 CFR 622.42(e)(2). Based on current statistics, NMFS has determined that 75 percent of the available commercial quota of 541,295 lb (245,527 kg), gutted weight, for golden tilefish will be reached on or before February 18, 2013. Accordingly, NMFS is reducing the commercial golden tilefish trip limit to 300 lb (136 kg), gutted weight, in the South Atlantic EEZ from 12:01 a.m., local time, on February 18, 2013, until the quota is reached and the commercial sector closes, or through December 31, 2013, whichever occurs first.</P>
        <HD SOURCE="HD1">Classification</HD>
        <P>The Regional Administrator, Southeast Region, NMFS, has determined this temporary rule is necessary for the conservation and management of South Atlantic golden tilefish and is consistent with the Magnuson-Stevens Act and other applicable laws.</P>
        <P>This action is taken under 50 CFR 622.44(c)(2) and is exempt from review under Executive Order 12866.</P>
        <P>These measures are exempt from the procedures of the Regulatory Flexibility Act because the temporary rule is issued without opportunity for prior notice and comment.</P>
        <P>Pursuant to 5 U.S.C. 553(b)(B), the Assistant Administrator for Fisheries, NOAA, (AA), finds good cause to waive the requirements to provide prior notice and the opportunity for public comment on this temporary rule. Such procedures are unnecessary because the rule itself has already been subject to notice and comment, and all that remains is to notify the public of the trip limit reduction.</P>
        <P>Allowing prior notice and opportunity for public comment is contrary to the public interest because of the need to immediately implement this action to protect golden tilefish because the capacity of the fishing fleet allows for rapid harvest of the quota. Prior notice and opportunity for public comment for this trip limit reduction would require time and would potentially result in a harvest well in excess of the established quota.</P>
        <P>For the aforementioned reasons, the AA also finds good cause to waive the 30-day delay in the effectiveness of this action under 5 U.S.C. 553(d)(3).</P>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>16 U.S.C. 1801<E T="03">et seq.</E>
          </P>
        </AUTH>
        <SIG>
          <DATED>Dated: February 8, 2013.</DATED>
          <NAME>Kara Meckley,</NAME>
          <TITLE>Acting Deputy Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03311 Filed 2-8-13; 4:15 pm]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <CFR>50 CFR Part 679</CFR>
        <DEPDOC>[Docket No. 111207737-2141-02]</DEPDOC>
        <RIN>RIN 0648-XC495</RIN>
        <SUBJECT>Fisheries of the Exclusive Economic Zone Off Alaska; Pacific Cod by Vessels Using Pot Gear in the Central Regulatory Area of the Gulf of Alaska</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Temporary rule; closure.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>NMFS is prohibiting directed fishing for Pacific cod by vessels using pot gear in the Central Regulatory Area of the Gulf of Alaska (GOA). This action is necessary to prevent exceeding the A season allowance of the 2013 Pacific cod total allowable catch apportioned to vessels using pot gear in the Central Regulatory Area of the GOA.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Effective 1200 hours, Alaska local time (A.l.t.), February 10, 2013, through 1200 hours, A.l.t., September 1, 2013.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Obren Davis, 907-586-7228.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>NMFS manages the groundfish fishery in the GOA exclusive economic zone according to the Fishery Management Plan for Groundfish of the Gulf of Alaska (FMP) prepared by the North Pacific Fishery Management Council under authority of the Magnuson-Stevens Fishery Conservation and Management Act. Regulations governing fishing by U.S. vessels in accordance with the FMP appear at subpart H of 50<PRTPAGE P="10103"/>CFR part 600 and 50 CFR part 679. Regulations governing sideboard protections for GOA groundfish fisheries appear at subpart B of 50 CFR part 680.</P>
        <P>The A season allowance of the 2013 Pacific cod total allowable catch (TAC) apportioned to vessels using pot gear in the Central Regulatory Area of the GOA is 6,459 metric tons (mt), as established by the final 2012 and 2013 harvest specifications for groundfish of the GOA (77 FR 15194, March 14, 2012) and inseason adjustment to the final 2013 harvest specifications for Pacific cod (78 FR 267, January 3, 2013).</P>
        <P>In accordance with § 679.20(d)(1)(i), the Administrator, Alaska Region, NMFS (Regional Administrator) has determined that the A season allowance of the 2013 Pacific cod TAC apportioned to vessels using pot gear in the Central Regulatory Area of the GOA will soon be reached. Therefore, the Regional Administrator is establishing a directed fishing allowance of 6,449 mt and is setting aside the remaining 10 mt as bycatch to support other anticipated groundfish fisheries. In accordance with § 679.20(d)(1)(iii), the Regional Administrator finds that this directed fishing allowance has been reached. Consequently, NMFS is prohibiting directed fishing for Pacific cod by vessels using pot gear in the Central Regulatory Area of the GOA. After the effective date of this closure the maximum retainable amounts at § 679.20(e) and (f) apply at any time during a trip.</P>
        <HD SOURCE="HD1">Classification</HD>
        <P>This action responds to the best available information recently obtained from the fishery. The Assistant Administrator for Fisheries, NOAA (AA), finds good cause to waive the requirement to provide prior notice and opportunity for public comment pursuant to the authority set forth at 5 U.S.C. 553(b)(B) as such requirement is impracticable and contrary to the public interest. This requirement is impracticable and contrary to the public interest as it would prevent NMFS from responding to the most recent fisheries data in a timely fashion and would delay the directed fishing closure of Pacific cod for vessels using pot gear in the Central Regulatory Area of the GOA. NMFS was unable to publish a notice providing time for public comment because the most recent, relevant data only became available as of February 7, 2013.</P>
        <P>The AA also finds good cause to waive the 30-day delay in the effective date of this action under 5 U.S.C. 553(d)(3). This finding is based upon the reasons provided above for waiver of prior notice and opportunity for public comment.</P>
        <P>This action is required by § 679.20 and is exempt from review under Executive Order 12866.</P>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>16 U.S.C. 1801<E T="03">et seq.</E>
          </P>
        </AUTH>
        <SIG>
          <DATED>Dated: February 8, 2013.</DATED>
          <NAME>Kara Meckley,</NAME>
          <TITLE>Acting Deputy Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03310 Filed 2-8-13; 4:15 pm]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </RULE>
  </RULES>
  <VOL>78</VOL>
  <NO>30</NO>
  <DATE>Wednesday, February 13, 2013</DATE>
  <UNITNAME>Proposed Rules</UNITNAME>
  <PRORULES>
    <PRORULE>
      <PREAMB>
        <PRTPAGE P="10104"/>
        <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Agricultural Marketing Service</SUBAGY>
        <CFR>7 CFR Part 1210</CFR>
        <DEPDOC>[Document Number AMS-FV-11-0031]</DEPDOC>
        <SUBJECT>Watermelon Research and Promotion Plan; Importer Membership Requirements</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Agricultural Marketing Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This rule proposes to amend the Watermelon Research and Promotion Plan (Plan) importer membership requirements to serve on the National Watermelon Promotion Board (Board). The Board recommended to eliminate the requirement that an importer import more than 50 percent of the total volume handled and imported in order to qualify as an importer member. This change would allow for additional parties to qualify as an importer member.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be received by March 15, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Interested persons are invited to submit written comments on the Internet at:<E T="03">http://www.regulations.gov</E>or to the Promotion and Economics Division, Fruit and Vegetable Program, Agricultural Marketing Service (AMS), U.S. Department of Agriculture, (USDA) Room 0632-S, Stop 0244, 1400 Independence Avenue SW., Washington, DC 20250-0244; facsimile: (202) 205-2800. All 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 made available for public inspection in the above office during regular business hours or it can be viewed at<E T="03">http://www.regulations.gov</E>. All comments received will be posted without change, including any personal information provided. Please be advised that the identity of the individuals or entities submitting 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>Jeanette Palmer, Marketing Specialist, Promotion and Economics Division, Fruit and Vegetable Program, AMS, U.S. Department of Agriculture, Stop 0244, 1400 Independence Avenue SW., Room 0632-S, Washington, DC 20250-0244; telephone: (888) 720-9917; facsimile: (202) 205-2800; or electronic mail:<E T="03">Jeanette.Palmer@ams.usda.gov</E>.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>This rule is issued under the Watermelon Research and Promotion Plan [7 CFR part 1210]. The Plan is authorized under the Watermelon Research and Promotion Act (Act) [7 U.S.C. 4901-4916].</P>
        <HD SOURCE="HD1">Executive Order 12866 and Executive Order 13563</HD>
        <P>Executive Orders 12866 and 13563 direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). Executive Order 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. This rule has been designated as “non-significant regulatory action” under section 3(f) of Executive Order 12866. Accordingly, the Office of Management and Budget (OMB) has waived the review process.</P>
        <HD SOURCE="HD1">Executive Order 12988</HD>
        <P>In addition, this rule has been reviewed under Executive Order 12988, Civil Justice Reform. The rule is not intended to have retroactive effect.</P>
        <P>The Act allows producers, producer-packers, handlers, and importers to file a written petition with the Secretary of Agriculture (Secretary) if they believe that the Plan, any provision of the Plan, or any obligation imposed in connection with the Plan, is not established in accordance with the law. In any petition, the person may request a modification of the Plan or an exemption from the Plan. The petitioner will have the opportunity for a hearing on the petition. Afterwards, an Administrative Law Judge (ALJ) will issue a decision. If the petitioner disagrees with the ALJ's ruling, the petitioner has 30 days to appeal to the Judicial Officer, who will issue a ruling on behalf of the Secretary. If the petitioner disagrees with the Secretary's ruling, the petitioner may file, within 20 days, an appeal in the U.S. District Court for the district where the petitioner resides or conducts business.</P>
        <HD SOURCE="HD1">Initial Regulatory Flexibility Act and Paperwork Reduction Act</HD>
        <P>In accordance with the Regulatory Flexibility Act [5 U.S.C. 601-612], AMS has examined the economic impact of this rule on the small producers, handlers, and importers that would be affected by this rule.</P>
        <P>The Small Business Administration defines, in 13 CFR part 121, small agricultural producers as those having annual receipts of no more than $750,000 and small agricultural service firms (handlers and importers) as those having annual receipts of no more than $7 million. Under these definitions, the majority of the producers, handlers, and importers that would be affected by this rule would be considered small entities. Producers of less than 10 acres of watermelons are exempt from this program. Importers of less than 150,000 pounds of watermelons per year are also exempt.</P>
        <P>USDA's National Agricultural Statistics Service (NASS) data for the 2011 crop year was about 312 hundredweight (cwt.) of watermelons were produced per acre. The 2011 grower price published by NASS was $14.00 per hundredweight. Thus, the value of watermelon production per acre in 2011 averaged about $4,368 (312 cwt. × $14.00). At that average price, a producer would have to farm over 172 acres to receive an annual income from watermelons of $750,000 ($750,000 divided by $4,368 per acre equals 172). Accordingly, as previously noted, a majority of the watermelon producers would be classified as small businesses.</P>

        <P>Based on the Board's data, using an average of freight on board (f.o.b.) price of $.164 per pound and the number of pounds handled in 2011, none of the watermelon handlers had receipts over the $7.5 million threshold. Therefore, the watermelon handlers would all be considered small businesses. A handler would have to ship over 45.7 million pounds of watermelons to be considered large (457,317,073 times $.164 f.o.b. equals $7,500,000).<PRTPAGE P="10105"/>
        </P>
        <P>According to the Board, there are approximately 950 producers, 230 handlers, and 137 importers who are required to pay assessments under the program.</P>
        <P>Based on the watermelon import assessments received for the year 2011, the United States imported watermelons worth over $211 million dollars. The largest imports of watermelon came from Mexico which accounted for 89 percent of the total in 2011. Other suppliers of imported watermelon are Guatemala at 8 percent and Costa Rica at 1 percent. The remaining 2 percent of imported watermelon came from Nicaragua, Honduras, Panama, Vietnam, Canada, Dominican Republic, and Israel.</P>

        <P>The Board's audit records show imports for the fiscal years 2009, 2010, and 2011 at $754,760, $746,043, and $855,890 respectively. Based on this data, the three-year average of imports for watermelon totals $785,564 (2,356,693 divided by 3). This represents approximately 30 percent of the total assessments paid to the Board. Currently, the Board membership distribution consists of 14 producers, 14 handlers, 8 importers, and 1 public member. A final rule to increase the number of importers on the Board was published in the July 18, 2011,<E T="04">Federal Register</E>[76 FR 42009].</P>

        <P>The Watermelon Research and Promotion Improvement Act of 1993 amended the Watermelon Research and Promotion Act by adding importer members to the Board among other things. At that time the industry recommended that, in order to qualify as an importer member on the Board, an individual that both handles and imports watermelons may vote for importer members and serve as an importer member if that person imports 50 percent or more of the combined total volume of watermelons handled and imported by that person. A final rule was published in the<E T="04">Federal Register</E>on February 28, 1995 [60 FR 10795] containing this and other amendments to the program.</P>
        <P>At the time of this amendment there was a more clear division of roles among producers, handlers, and importers. In other words, those individuals that imported watermelons did not cross over into handling or producing watermelons as much as they do now. Since then, the industry has become more consolidated and of the 137 importers required to pay assessments 42 also handled watermelons and would be eligible to serve as either handler or importer member.</P>
        <P>At its February 26, 2011, meeting, the Board voted unanimously, to modify the importer eligibility requirements to serve on the Board. The Board is having difficulty finding eligible importers to serve on the Board because of the requirement in the Plan that a person who both imports and handles watermelon will be counted as an importer if that person imports 50 percent or more of the combined total volume of watermelons handled and imported by that person. The Board voted to eliminate the 50 percent requirement or more of the combined total volume of watermelons handled and imported by a person to allow more individuals to become eligible to serve on the Board as an importer. Individuals that both handle and import would be allowed to decide which part of the industry they would prefer to represent regardless of the volume handled or imported. The industry believes that this change would increase the importer representation on the Board by allowing more individuals to be eligible to serve. This action may also increase diversity representation on the Board.</P>
        <P>The Board considered a second alternative by changing the 50 percent or more of the combined total volume of watermelons handled and imported by the person to 25 percent or more of the combined total volume of watermelons handled and imported by the person. However, the Board did not choose this option because they wanted to allow more importers to be eligible for nomination on the Board and therefore, they eliminated the percentage requirement. By eliminating the percentage requirement for the importer member, this will allow for smaller importer businesses to become eligible to serve as an importer member on the Board.</P>
        <P>Section 1655(a) of the Act provides for referenda to be conducted to ascertain approval of changes to the Plan prior to going into effect. In order to implement the amendments to the Plan, the Secretary determines that the Plan has been approved by a majority of the producers, handlers, and importers of watermelon voting in the referendum. Accordingly, before these amendments are made to the Plan, a referendum will be conducted among eligible producers, handlers, and importers of watermelon.</P>
        <P>In accordance with the Office of Management and Budget (OMB) regulation[5 CFR part 1320] which implements the Paperwork Reduction Act of 1995 [44 U.S.C. Chapter 35], have been assigned OMB number 0581-0093, which represents the information collection and recordkeeping requirements that are imposed by the Plan that have been approved previously, except that the background form, has been approved under OMB number 0505-0001.</P>
        <P>USDA has not identified any relevant Federal rules that duplicate, overlap, or conflict with this rule.</P>
        <P>We have performed this Initial Regulatory Flexibility Analysis regarding the impact of this amendment to the Plan on small entities, and we invite comments concerning potential effects of this amendment.</P>
        <HD SOURCE="HD1">Background</HD>
        <P>Under the Plan, the Board administers a nationally coordinated program of research, development, advertising, and promotion designed to strengthen the watermelon's position in the market place and to establish, maintain, and expand markets for watermelons. This program is financed by assessments on producers growing 10 acres or more of watermelons, handlers of watermelons, and importers of 150,000 pounds of watermelons or more per year. The Plan specifies that handlers are responsible for collecting and submitting both the producer and handler assessments to the Board, reporting their handling of watermelons, and maintaining records necessary to verify their reporting(s). Importers are responsible for payment of assessments to the Board on watermelons imported into the United States through the U.S. Customs Service and Border Protection. This action will not have any impact on the assessment rates paid by producers, handlers, and importers.</P>

        <P>Membership on the Board consists of two producers and two handlers for each of the seven districts established by the Plan, at least one importer, and one public member. The Board currently consists of 37 members: 14 producers, 14 handlers, 8 importers, and 1 public member. A final rule to increase the number of importers on the Board was published in the July 18, 2011,<E T="04">Federal Register</E>[76 FR 42009].</P>

        <P>The Watermelon Research and Promotion Improvement Act of 1993 amended the Watermelon Research and Promotion Act by adding importer members to the Board among other things. At that time the industry recommended that, in order to qualify as an importer member on the Board, an individual that both handles and imports watermelons may vote for importer members and serve as an importer member if that person imports 50 percent or more of the combined total volume of watermelons handled and imported by that person. A final rule was published in the<E T="04">Federal Register</E>on February 28, 1995 [60 FR<PRTPAGE P="10106"/>10795] containing this and other amendments to the program. At the time of this amendment there was a more clear division of roles among producers, handlers, and importers. In other words, those individuals that imported watermelons did not cross over into handling or producing watermelons as much as they do now. Since then, the industry has become more consolidated and of the 137 importers required to pay assessments 42 also handled watermelons and would be eligible to serve as either handler or importer member.</P>
        <P>At its February 26, 2011, meeting, the Board voted unanimously, to modify the importer eligibility requirements to serve on the Board. The Board is having difficulty finding eligible importers to serve on the Board because of the requirement in the Plan that a person who both imports and handles watermelon will be counted as an importer if that person imports 50 percent or more of the combined total volume of watermelons handled and imported by that person. The Board voted to eliminate the 50 percent requirement or more of the combined total volume of watermelons handled and imported by a person to allow more individuals to become eligible to serve on the Board as an importer. Individuals that both handle and import would be allowed to decide which part of the industry they would prefer to represent regardless of the volume handled or imported. The industry believes that this change would increase the importer representation on the Board by allowing more individuals to be eligible to serve. This action may also increase diversity representation on the Board.</P>
        <P>Accordingly, the propose rule would amend sections 1210.321(d), 1210.363(b), 1210.404(g), and 1210.602(a) which reference importer eligibility requirements to be nominated to the Board and participation in a referendum. These sections would be revised to read as follows: a person who both imports and handles watermelon may vote for importer members and serve as an importer member if that person identifies that their vote will be considered as an importer.</P>
        <P>For changes to the Plan to become effective, the proposed amendments to the Plan must be approved by a majority of producers, handlers, and importers of watermelon voting in a referendum. Accordingly, a referendum will be conducted among eligible producers, handlers, and importers of watermelon. Specific dates for the referendum will be announced at a later date.</P>
        <P>A 30-day comment period is provided to allow interested persons to respond to this proposal. Thirty days is deemed appropriate so that the proposed amendments, if adopted, may be implemented to allow for the calendar year 2013 nomination meetings to take place before the appointments for new Board members are due. All written comments received in response to this rule by the date specified would be considered prior to finalizing this action.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 7 CFR Part 1210</HD>
          <P>Administrative practice and procedure, Advertising, Consumer information, Marketing agreements, Reporting and recordkeeping requirements, Watermelon promotion.</P>
        </LSTSUB>
        
        <P>For the reasons set forth in the preamble, Part 1210, Chapter XI of Title 7 is proposed to be amended as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 1210—WATERMELON RESEARCH AND PROMOTION PLAN</HD>
        </PART>
        <AMDPAR>1. The authority citation for 7 CFR part 1210 continues to read as follows:</AMDPAR>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>7 U.S.C. 4901-4916 and 7 U.S.C. 7401.</P>
        </AUTH>
        
        <AMDPAR>2. Revise § 1210.321 paragraph (d) to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 1210.321</SECTNO>
          <SUBJECT>Nomination and selection.</SUBJECT>
          <STARS/>

          <P>(d) Nominations for importers positions that become vacant may be made by mail ballot, nomination conventions, or by other means prescribed by the Secretary. The Board shall provide notice of such vacancies and the nomination process to all importers through press releases and any other available means as well as direct mailing to known importers. All importers may participate in the nomination process:<E T="03">Provided,</E>That a person who both imports and handles watermelon may vote for importer members and serve as an importer member if that person identifies that their vote be considered as an importer.</P>
          <STARS/>
        </SECTION>
        <AMDPAR>3. Revise § 1210.363 paragraph (b) to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 1210.363</SECTNO>
          <SUBJECT>Suspension or termination.</SUBJECT>
          <STARS/>

          <P>(b) The Secretary may conduct a referendum at any time and shall hold a referendum on request of the Board or at least 10 percent of the combined total of the watermelon producers, handlers, and importers to determine if watermelon producers, handlers, and importers favor termination or suspension of this Plan. The Secretary shall suspend or terminate this Plan at the end of the marketing year whenever the Secretary determines that the suspension or termination is favored by a majority of the watermelon producers, handlers, and importers voting in such referendum who, during a representative period determined by the Secretary, have been engaged in the production, handling, or importing of watermelons and who produced, handled, or imported more than 50 percent of the combined total of the volume of watermelons produced, handled, or imported by those producers, handlers, and importers voting in the referendum. For purposes of this section, the vote of a person who both produces and handles watermelons will be counted as a handler vote if the producer purchased watermelons from other producers, in a combined total volume that is equal to 25 percent or more of the producer's own production; or the combined total volume of watermelon handled by the producer from the producer's own production and purchases from other producer's production is more than 50 percent of the producer's own production.<E T="03">Provided,</E>That a person who both imports and handles watermelon may vote for importer members and serve as an importer member if that person identifies that their vote be considered as an importer. Any such referendum shall be conducted by mail ballot.</P>
          
        </SECTION>
        <AMDPAR>4. Revise § 1210.404 paragraph (g) to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 1210.404</SECTNO>
          <SUBJECT>Importer member nomination and selection.</SUBJECT>
          <STARS/>
          <P>(g) Any individual who both imports and handles watermelons will be considered an importer if that person identifies themselves as an importer.</P>
          
        </SECTION>
        <AMDPAR>5. Revise § 1210.602 paragraph (a) to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 1210.602</SECTNO>
          <SUBJECT>Voting.</SUBJECT>

          <P>(a) Each person who is an eligible producer, handler, or importer as defined in this subpart, at the time of the referendum and who also was a producer, handler, or importer during the representative period, shall be entitled to one vote in the referendum:<E T="03">Provided,</E>That each producer in a landlord-tenant relationship or a divided ownership arrangement involving totally independent entities cooperating only to produce watermelons in which more than one of the parties is a producer, shall be entitled to one vote in the referendum covering only that producer's share of the ownership:<E T="03">Provided further,</E>That the vote of a person who both produces and handles watermelons will be counted as a handler vote if the producer purchased watermelons from<PRTPAGE P="10107"/>other producers, in a combined total volume that is equal to 25 percent or more of the producer's own production; or the combined total volume of watermelon handled by the producer from the producer's own production and purchased from other producer's production is more than 50 percent of the producer's own production:<E T="03">Provided further,</E>That a person who both imports and handles watermelons may vote and serve as an importer if that person identifies that their vote be considered as an importer.</P>
          <STARS/>
        </SECTION>
        <SIG>
          <DATED>Dated: February 5, 2013.</DATED>
          <NAME>David R. Shipman,</NAME>
          <TITLE>Administrator.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-02975 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-02-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 1, 16, 106, 110, 112, 114, 117, 120, 123, 129, 179, and 211</CFR>
        <DEPDOC>[Docket Nos. FDA-2011-N-0920 and FDA-2011-N-0921]</DEPDOC>
        <SUBJECT>Food and Drug Administration Food Safety Modernization Act: Proposed Rules To Establish Standards for the Growing, Harvesting, Packing, and Holding of Produce for Human Consumption and for Current Good Manufacturing Practice and Hazard Analysis and Risk-Based Preventive Controls for Human Food; Public Meeting</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Food and Drug Administration, HHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notification of public meeting.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The Food and Drug Administration (FDA) is providing public meeting registration information for two FSMA related public meetings announced in the January 31, 2013,<E T="04">Federal Register</E>. These public meetings will be held along with the February 28 to March 1, 2013, Washington, DC public meeting to discuss the proposed rules to establish standards for the growing, harvesting, packing, and holding of produce for human consumption (the produce safety proposed rule) and for current good manufacturing practice and hazard analysis and risk-based preventive controls for human food (the preventive controls proposed rule). These proposed rules are the first of several proposed rules that would establish the foundation of, and central framework for, the modern food safety system envisioned by Congress in the FDA Food Safety Modernization Act (FSMA). The purpose of the public meetings is to solicit oral stakeholder and public comments on the proposed rules and to inform the public about the rulemaking process (including how to submit comments, data, and other information to the rulemaking dockets), and to respond to questions about the proposed rules.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>

          <P>See section II “How to Participate in the Public Meeting” in the<E T="02">SUPPLEMENTARY INFORMATION</E>section of this document for dates and times of the Chicago, IL and Portland, OR public meetings, closing dates for advance registration, and information on deadlines for submitting either electronic or written comments to FDA's Division of Dockets Management.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>See section II “How to Participate in the Public Meeting” in the<E T="02">SUPPLEMENTARY INFORMATION</E>section of this document.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>
            <E T="03">For questions about registering for these meetings, to register by phone, or to submit a notice of participation by mail, fax, or email:</E>Courtney Treece, Planning Professionals, Ltd., 1210 West McDermott Dr., Suite 111, Allen, TX 75013, 704-258-4983, FAX: 469-854-6992, email:<E T="03">ctreece@planningprofessionals.com.</E>
          </P>
          <P>
            <E T="03">For general questions about these meetings, to request an opportunity to make an oral presentation at one of the public meetings, to submit the full text, comprehensive outline, or summary of an oral presentation, or for special accommodations due to a disability, contact:</E>Juanita Yates, Center for Food Safety and Applied Nutrition (HFS-009), Food and Drug Administration, 5100 Paint Branch Pkwy., College Park, MD 20740, 240-402-1731, email:<E T="03">Juanita.yates@fda.hhs.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Background</HD>
        <P>FSMA (Pub. L. 111-353) was signed into law by President Obama on January 4, 2011, to better protect public health by helping to ensure the safety and security of the food supply. FSMA amends the Federal Food, Drug, and Cosmetic Act (the FD&amp;C Act) to establish the foundation of a modernized, prevention-based food safety system. Among other things, FSMA requires FDA to issue regulations requiring preventive controls for human and animal food and set standards for produce safety.</P>
        <P>FSMA was the first major legislative reform of FDA's food safety authorities in more than 70 years, even though FDA has increased the focus of its food safety efforts on prevention over the past several years. For example, applying the concept of Hazard Analysis and Critical Control Point (HACCP) that was pioneered by industry in the late 1960s, FDA established HACCP-based regulations for seafood (21 CFR part 123) in 1995 (60 FR 65096, December 18, 1995) and for juice (21 CFR part 120) in 2001 (66 FR 6138, January 19, 2001). Similarly, in 1996, the U.S. Department of Agriculture's Food Safety and Inspection Service instituted HACCP-based rules for meat and poultry (9 CFR part 417) (61 FR 38806, July 25, 1996).</P>
        <P>In the<E T="04">Federal Register</E>of January 16, 2013 (78 FR 3503 and 78 FR 3646), FDA announced the establishment of two dockets so that the public can review the produce safety proposed rule and the preventive controls proposed rule and submit comments to the Agency. These proposed rulemakings are the first of several key proposals in furtherance of FSMA's food safety mandate. The produce safety proposed rule would establish science-based minimum standards for the safe growing, harvesting, packing, and holding of produce, meaning fruits and vegetables, grown for human consumption. The produce safety proposed rule would set forth procedures, processes, and practices that FDA expects would reduce foodborne illness associated with the consumption of produce. The produce safety proposed rule and related fact sheets are available on FDA's FSMA Web page located at<E T="03">http://www.fda.gov/Food/FoodSafety/FSMA/default.htm.</E>
        </P>

        <P>The preventive controls proposed rule would apply to human food and require domestic and foreign facilities that are required to register under the FD&amp;C Act to have written plans that identify hazards, specify the steps that will be put in place to minimize or prevent those hazards, monitor results, and act to correct problems that arise. The preventive controls proposed rule and related fact sheets are available on FDA's FSMA Web page located at<E T="03">http://www.fda.gov/Food/FoodSafety/FSMA/default.htm.</E>
        </P>
        <P>In the<E T="04">Federal Register</E>of January 31, 2013 (78 FR 6762), FDA announced the first public meeting in a series of three public meetings entitled “The Food Safety Modernization Act Public Meeting on Proposed Rules for Produce Safety and for Preventive Controls for Human Food” so that the food industry, consumers, foreign governments, and other stakeholders can evaluate and comment on the proposals. FDA also noted that the Agency intended to hold<PRTPAGE P="10108"/>additional public meetings in Chicago, IL and Portland, OR and that those specific locations, dates, and registration information for these meetings would appear in a separate<E T="04">Federal Register</E>document to publish shortly. It was also noted that all three public meetings would have the same agenda and are intended to facilitate and support the proposed rules' evaluation and commenting process.</P>
        <P>In this document, FDA is providing the locations, dates, and registration information for the Chicago, IL and Portland, OR public meetings.</P>
        <HD SOURCE="HD1">II. How To Participate in the Public Meeting</HD>
        <P>FDA is holding the public meetings on the produce safety proposed rule and the preventive controls proposed rule to inform the public about the rulemaking process, including how to submit comments, data, and other information to the rulemaking docket; to respond to questions about the proposed rules; and to provide an opportunity for interested persons to make oral presentations. Due to limited space and time, FDA encourages all persons who wish to attend the public meetings to register in advance. There is no fee to register for the public meetings, and registration will be on a first-come, first-served basis. Early registration is recommended because seating is limited. Onsite registration will be accepted, as space permits, after all preregistered attendees are seated.</P>
        <P>Those requesting an opportunity to make an oral presentation during the time allotted for public comment at the meetings are asked to submit a request and to provide the specific topic or issue to be addressed. Due to the anticipated high level of interest in presenting public comment and limited time available, FDA is allocating 3 minutes to each speaker to make an oral presentation. Speakers will be limited to making oral remarks; there will not be an opportunity to display materials such as slide shows, videos, or other media during the meeting. If time permits, individuals or organizations that did not register in advance may be granted the opportunity to make an oral presentation. FDA would like to maximize the number of individuals who make a presentation at the meetings and will do our best to accommodate all persons who wish to make a presentation or express their opinions at the meeting.</P>
        <P>FDA encourages persons and groups who have similar interests to consolidate their information for presentation by a single representative at a single location. After reviewing the presentation requests, FDA will notify each participant before the meeting of the approximate time their presentation is scheduled to begin, and remind them of the presentation format (i.e., 3-minute oral presentation without visual media).</P>

        <P>While oral presentations from specific individuals and organizations will be necessarily limited due to time constraints during the public meeting, stakeholders may submit electronic or written comments discussing any issues of concern to the administrative record (the docket) for the rulemaking. All relevant data and documentation should be submitted with the comments to the relevant docket (i.e., for the produce safety proposed rule,<E T="03">http://www.regulations.gov/#!docketDetail;D=FDA-2011-N-0921;</E>and for the preventive controls proposed rule,<E T="03">http://www.regulations.gov/#!docketDetail;D=FDA-2011-N-0920)</E>.</P>
        <P>Table 1 of this document provides information on participation in the public meetings:</P>
        <GPOTABLE CDEF="s50,r50,r100,r100,r100" COLS="5" OPTS="L2,i1">
          <TTITLE>Table 1—Information on Participation in the Meetings and on Submitting Comments to the Rulemaking Dockets</TTITLE>
          <BOXHD>
            <CHED H="1"/>
            <CHED H="1">Date</CHED>
            <CHED H="1">Electronic address</CHED>
            <CHED H="1">Address</CHED>
            <CHED H="1">Other information</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Washington, DC Public meeting</ENT>
            <ENT>February 28, 2013, from 8:30 a.m. to 5 p.m. and March 1, 2013, from 8:30 a.m. to 12 noon</ENT>
            <ENT O="xl"/>

            <ENT>Jefferson Auditorium, U.S. Department of Agriculture (USDA), Wing 5 Entrance, 14th and Independence Ave. SW., Washington, DC 20024.<E T="03">Photo ID Required</E>
            </ENT>
            <ENT>Onsite registration both days from 8 a.m. to 8:30 a.m.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Washington, DC Advance registration</ENT>
            <ENT>By February 20, 2013</ENT>

            <ENT>Individuals who wish to participate in person are asked to preregister at<E T="03">http://www.fda.gov/Food/NewsEvents/WorkshopsMeetingsConferences/default.htm</E>
            </ENT>
            <ENT O="xl">We encourage you to use electronic registration if possible.<SU>1</SU>
            </ENT>
            <ENT>There is no registration fee for the public meetings. Early registration is recommended because seating is limited.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Washington, DC Request to make an oral presentation</ENT>
            <ENT>By February 8, 2013</ENT>
            <ENT O="xl">
              <E T="03">http://www.fda.gov/Food/NewsEvents/WorkshopsMeetingsConferences/default.htm.</E>
              <SU>2</SU>
            </ENT>
            <ENT O="xl"/>

            <ENT>Requests made on the day of the meeting to make an oral presentation will be granted as time permits. Information on requests to make an oral presentation may be posted without change to<E T="03">http://www.regulations.gov,</E>including any personal information provided.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Washington, DC Request special accommodations due to a disability</ENT>
            <ENT>By February 15, 2013</ENT>
            <ENT>Juanita Yates, email:<E T="03">Juanita.yates@fda.hhs.gov</E>
            </ENT>
            <ENT>See<E T="02">FOR FURTHER INFORMATION CONTACT</E>
            </ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="10109"/>
            <ENT I="01">Chicago, IL Public meeting</ENT>
            <ENT>March 11, 2013, from 8:30 a.m. to 5 p.m. and March 12, 2013, from 8:30 a.m. to 12 noon</ENT>
            <ENT O="xl"/>
            <ENT>The Westin-Michigan Avenue, 909 North Michigan Ave., Chicago, IL 60611</ENT>
            <ENT>Onsite registration both days from 8 a.m. to 8:30 a.m.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Chicago, IL Advance registration</ENT>
            <ENT>By March 1, 2013</ENT>

            <ENT>Individuals who wish to participate in person are asked to preregister at<E T="03">http://www.fda.gov/Food/NewsEvents/WorkshopsMeetingsConferences/default.htm</E>
            </ENT>
            <ENT O="xl">We encourage you to use electronic registration if possible.<SU>1</SU>
            </ENT>
            <ENT>There is no registration fee for the public meetings. Early registration is recommended because seating is limited.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Chicago, IL Request to make an oral presentation</ENT>
            <ENT>By February 21, 2013</ENT>
            <ENT O="xl">
              <E T="03">http://www.fda.gov/Food/NewsEvents/WorkshopsMeetingsConferences/default.htm</E>.<SU>2</SU>
            </ENT>
            <ENT O="xl"/>

            <ENT>Requests made on the day of the meeting to make an oral presentation will be granted as time permits. Information on requests to make an oral presentation may be posted without change to<E T="03">http://www.regulations.gov,</E>including any personal information provided.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Chicago, IL Request special accommodations due to a disability</ENT>
            <ENT>By February 21, 2013</ENT>
            <ENT>Juanita Yates, email:<E T="03">Juanita.yates@fda.hhs.gov</E>
            </ENT>
            <ENT>See<E T="02">FOR FURTHER INFORMATION CONTACT</E>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="01">Portland, OR Public meeting</ENT>
            <ENT>March 27, 2013, from 8:30 a.m. to 5 p.m. and March 28, 2013, from 8:30 a.m. to 12 noon</ENT>
            <ENT O="xl"/>
            <ENT>Crown Plaza Portland Downtown Convention Center, 1441 NE 2nd Ave., Portland, OR 97232</ENT>
            <ENT>Onsite registration both days from 8 a.m. to 8:30 a.m.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Portland, OR Advance registration</ENT>
            <ENT>By March 18, 2013</ENT>

            <ENT>Individuals who wish to participate in person are asked to preregister at<E T="03">http://www.fda.gov/Food/NewsEvents/WorkshopsMeetingsConferences/default.htm</E>
            </ENT>
            <ENT O="xl">We encourage you to use electronic registration if possible.<SU>1</SU>
            </ENT>
            <ENT>There is no registration fee for the public meetings. Early registration is recommended because seating is limited.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Portland, OR Request to make an oral presentation</ENT>
            <ENT>By March 8, 2013</ENT>
            <ENT O="xl">
              <E T="03">http://www.fda.gov/Food/NewsEvents/WorkshopsMeetingsConferences/default.htm</E>.<SU>2</SU>
            </ENT>
            <ENT O="xl"/>

            <ENT>Requests made on the day of the meeting to make an oral presentation will be granted as time permits. Information on requests to make an oral presentation may be posted without change to<E T="03">http://www.regulations.gov,</E>including any personal information provided.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Portland, OR Request special accommodations due to a disability</ENT>
            <ENT>By March 8, 2013</ENT>
            <ENT>Juanita Yates, email:<E T="03">Juanita.yates@fda.hhs.gov</E>
            </ENT>
            <ENT>See<E T="02">FOR FURTHER INFORMATION CONTACT</E>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="01">Submit electronic or written comments</ENT>
            <ENT>By May 16, 2013</ENT>
            <ENT>Docket Nos. FDA-2011-N-0920 and FDA-2011-N-0921</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT>Preventive Controls for Human Food Proposed Rule:<E T="03">http://www.regulations.gov/#!docketDetail;D=FDA-2011-N-0920</E>
            </ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="10110"/>
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT>Produce Safety Proposed Rule:<E T="03">http://www.regulations.gov/#!docketDetail;D=FDA-2011-N-0921</E>
            </ENT>
          </ROW>
          <TNOTE>

            <SU>1</SU>You may also register via email, mail, or fax. Please include your name, title, firm name, address, and phone and FAX numbers in your registration information and send to Courtney Treece (see<E T="02">FOR FURTHER INFORMATION CONTACT</E>). Onsite registration will also be available.</TNOTE>
          <TNOTE>

            <SU>2</SU>You may also request to make an oral presentation at the public meeting via email. Please include your name, title, firm name, address, and phone and fax numbers as well as the full text, comprehensive outline, or summary of your oral presentation, and send to Juanita Yates (see<E T="02">FOR FURTHER INFORMATION CONTACT</E>).</TNOTE>
        </GPOTABLE>
        <HD SOURCE="HD1">III. Comments, Transcripts, and Recorded Video</HD>

        <P>Information and data submitted voluntarily to FDA during the public meetings will become part of the administrative record for the relevant rulemaking and will be accessible to the public at<E T="03">http://www.regulations.gov.</E>The transcript of the proceedings from the public meetings will become part of the administrative record for each of the rulemakings. Please be advised that as soon as a transcript is available, it will be accessible at<E T="03">http://www.regulations.gov</E>and at FDA's FSMA Web site at<E T="03">http://www.fda.gov/Food/FoodSafety/FSMA/.</E>It may also be viewed at the Division of Dockets Management (HFA-305), Food and Drug Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852. A transcript for each public meeting will also be available in either hardcopy or on CD-ROM, after submission of a Freedom of Information request. Written requests are to be sent to the Division of Freedom of Information (ELEM-1029), 12420 Parklawn Dr., Element Bldg., Rockville, MD 20857. Additionally, FDA will be video recording the first public meeting in Washington, DC. Once the recorded video is available, it will be accessible at FDA's FSMA Web site at<E T="03">http://www.fda.gov/Food/FoodSafety/FSMA/.</E>
        </P>
        <SIG>
          <DATED>Dated: February 8, 2013.</DATED>
          <NAME>Leslie Kux,</NAME>
          <TITLE>Assistant Commissioner for Policy.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03316 Filed 2-12-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 1190</CFR>
        <DEPDOC>[Docket No. ATBCB-2013-0002]</DEPDOC>
        <RIN>RIN 3014-AA26</RIN>
        <SUBJECT>Accessibility Guidelines for Pedestrian Facilities in the Public Right-of-Way; Shared Use Paths</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Architectural and Transportation Barriers Compliance Board.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Supplemental notice of proposed rulemaking.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>We, the Architectural and Transportation Barriers Compliance Board (Access Board), issued an advance notice of proposed rulemaking (ANPRM) announcing our intent to develop accessibility guidelines for shared used paths. Shared use paths are multi-use paths designed primarily for use by bicyclists and pedestrians, including pedestrians with disabilities, for transportation and recreation purposes. Shared use paths are physically separated from motor vehicle traffic by an open space or barrier, and are either within the highway right-of-way or within an independent right-of-way. We noted in the ANPRM that we are considering including accessibility guidelines for shared use paths in the accessibility guidelines that we are developing for sidewalks and other pedestrian facilities in the public right-of-way. We subsequently issued a notice of proposed rulemaking (NPRM) requesting comments on proposed accessibility guidelines for pedestrian facilities in the public right-of-way. The NPRM did not include specific provisions for shared use paths. We are issuing this supplemental notice of proposed rulemaking (SNPRM) to include specific provisions for shared use paths in the proposed accessibility guidelines for pedestrian facilities in the public right-of-way. The proposed accessibility guidelines would apply to the design, construction, and alteration of pedestrian facilities in the public right-of-way, including shared use paths, covered by the Americans with Disabilities Act and the Architectural Barriers Act, and would ensure that the facilities are readily accessible to and usable by individuals with disabilities.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Submit comments by May 14, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Submit comments by any of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>Follow the instructions for submitting comments. Regulations.gov ID for this docket is ATBCB-2013-0002.</P>
          <P>•<E T="03">Email: docket@access-board.gov.</E>Include docket number ATBCB 2013-0002 in the subject line of the message.</P>
          <P>•<E T="03">Fax:</E>202-272-0081.</P>
          <P>•<E T="03">Mail or Hand Delivery/Courier:</E>Scott Windley, Access Board, 1331 F Street NW., Suite 1000, Washington, DC 20004-1111.</P>
          <P>All comments will be posted without change to<E T="03">http://www.regulations.gov</E>, including any personal information provided.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Scott Windley, Access Board, 1331 F Street NW., Suite 1000, Washington, DC 20004-1111. Telephone (202) 272-0025 (voice) or (202) 272-0028 (TTY). Email<E T="03">address row@access-board.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Table of Contents</HD>
        
        <EXTRACT>
          <FP SOURCE="FP-2">1. Executive Summary</FP>
          <FP SOURCE="FP-2">2. Background</FP>
          <FP SOURCE="FP-2">3. Proposed Supplements to Proposed Accessibility Guidelines for Pedestrian Facilities in the Public Right-of-Way</FP>
          <FP SOURCE="FP-2">4. Comparison of Proposed Technical Provisions Applicable to Shared Use Paths and AASHTO Guide</FP>
          <FP SOURCE="FP-2">5. Conflicts Between Shared Path Users</FP>
          <FP SOURCE="FP-2">6. Regulatory Analyses</FP>
        </EXTRACT>
        

        <P>In this preamble, “we,” “us,” and “our” refer to the Architectural and Transportation Barriers Compliance Board (Access Board).<PRTPAGE P="10111"/>
        </P>
        <HD SOURCE="HD1">1. Executive Summary</HD>

        <P>This supplemental notice of proposed rulemaking (SNPRM) proposes to include specific provisions for shared use paths in the proposed accessibility guidelines for pedestrian facilities in the public right-of-way published in the<E T="04">Federal Register</E>on July 26, 2011. See 76 FR 44664 (July 26, 2011). A copy of the proposed accessibility guidelines for pedestrian facilities in the public right-of-way with the specific provisions for shared use paths proposed in the SNPRM is available on our Web site at:<E T="03">http://www.access-board.gov/sup.htm.</E>
        </P>
        <P>We are required by section 502 of the Rehabilitation Act to establish and maintain accessibility guidelines for the design, construction, and alteration of facilities covered by the Americans with Disabilities Act (ADA) and the Architectural Barriers Act (ABA) to ensure that the facilities are readily accessible to and usable by individuals with disabilities. See 29 U.S.C. 792(b)(3). The ADA covers state and local government facilities, places of public accommodation, and commercial facilities. See 42 U.S.C. 12101 et seq. The ABA covers facilities financed with federal funds. See 42 U.S.C. 4151 et seq.</P>
        <P>We are issuing the SNPRM in response to public comments on separate rulemakings to develop accessibility guidelines for trails and other outdoor developed areas, and for sidewalks and other pedestrian facilities in the public right-of-way. The comments noted that shared use paths are distinct from trails and sidewalks, and recommended that we develop accessibility guidelines for shared use paths. As defined in the SNPRM, shared use paths are multi-use paths designed primarily for use by bicyclists and pedestrians, including pedestrians with disabilities, for transportation and recreation purposes. Shared use paths are physically separated from motor vehicle traffic by an open space or barrier, and are either within the highway right-of-way or within an independent right-of-way.</P>
        <P>As noted above, the SNPRM would include specific provisions for shared use paths in the proposed accessibility guidelines for pedestrian facilities in the public right-of-way. The proposed accessibility guidelines for pedestrian facilities in the public right-of-way would require pedestrian access routes to be provided within pedestrian circulation paths located in the public right-of-way, and would establish proposed technical provisions for the width, grade, cross slope, and surface of pedestrian access routes. See R204.2 and R302. Where existing pedestrian circulation paths are altered and existing physical constraints make it impracticable for the altered paths to fully comply with the proposed technical provisions, compliance would be required to the extent practicable. See R202.3.1.</P>
        <P>The SNPRM would:</P>
        <P>• Require the full width of a shared use path to comply with the proposed technical provisions for the grade, cross slope, and surface of pedestrian access routes (see R302.3.2);</P>
        <P>• Permit compliance with the proposed technical provisions for the grade of pedestrian access routes to the extent practicable where physical constraints or regulatory constraints prevent full compliance (see R302.5.4 and R302.5.5);</P>
        <P>• Prohibit objects from overhanging or protruding into any portion of a shared use path at or below 8 feet measured from the finished surface (see R210.3); and</P>
        <P>• Require the width of curb ramps and blended transitions in shared use paths to be equal to the width of the shared use path (see R304.5.1.2).</P>
        <P>The SNPRM is consistent with the design criteria for shared used paths in the American Association of State Highway and Transportation Officials (AASHTO) “Guide for the Development of Bicycle Facilities” (2012) (hereinafter referred to as the “AASHTO Guide”). The SNPRM is not expected to increase the cost of constructing shared use paths for state and local government jurisdictions that use the AASHTO Guide.</P>
        <P>As discussed in the preamble to the proposed accessibility guidelines for pedestrian facilities in the public right-of-way, other federal agencies are required to adopt accessibility standards for the design, construction, and alteration of facilities covered by the ADA and ABA that are consistent with our accessibility guidelines. When the other federal agencies adopt accessibility standards for the design, construction, and alteration of pedestrian facilities in the public right-of-way, including shared use paths, covered by the ADA and ABA, compliance with the standards is mandatory.</P>
        <HD SOURCE="HD1">2. Background</HD>
        <P>We are conducting separate rulemakings to develop accessibility guidelines for trails and other outdoor developed areas, and for sidewalks and other pedestrian facilities in the public right-of-way.</P>
        <P>We issued a notice of proposed rulemaking (NPRM) requesting comments on proposed accessibility guidelines for trails and other outdoor developed areas in 2007. See 72 FR 34074 (June 20, 2007). A trail would be defined for purposes of these accessibility guidelines as a pedestrian route developed primarily for outdoor recreational purposes. A pedestrian route developed primarily to connect elements, spaces, or facilities within a site is not a trail.</P>
        <P>We requested comments on draft accessibility guidelines for sidewalks and other pedestrian facilities in the public right-of-way in 2002 and 2005. See 67 FR 41206 (June 17, 2002); and 70 FR 70734 (November 23, 2005). These accessibility guidelines would adopt the definition of sidewalk in the Manual on Uniform Traffic Control Devices (MUTCD). The MUTCD (2009) defines a sidewalk as the portion of a street between the curb line, or the lateral line of a roadway, and the adjacent property line or on easements of private property that is paved or improved and intended for use by pedestrians.</P>
        <P>Public comments on these rulemakings noted that shared use paths are distinct from trails and sidewalks in that they are used by bicyclists and pedestrians, including pedestrians with disabilities, for transportation and recreation purposes. The comments recommended that we develop accessibility guidelines for shared use paths. On March 28, 2011, we issued an advance notice of proposed rulemaking (ANPRM) announcing our intent to develop accessibility guidelines for shared use paths, and requested comments on a definition and draft technical provisions for shared use paths. See 76 FR 17064 (March 28, 2011). We noted in the ANPRM that we are considering including accessibility guidelines for shared use paths in the accessibility guidelines for pedestrian facilities in the public right-of-way since state and local transportation departments are the principal entities that design and construct shared use paths, and many of the draft technical provisions for shared use paths in the ANPRM are the same as those in the draft accessibility guidelines for pedestrian facilities in the public right-of-way (e.g., curb ramps and blended transitions, and detectable warning surfaces).</P>

        <P>On July 26, 2011, we issued a NPRM requesting comments on proposed accessibility guidelines for pedestrian facilities in the public right-of-way. See 76 FR 44664 (July 26, 2011). The NPRM did not include specific provisions for shared use paths. The comment period on the NPRM ended on November 23, 2011. The comment period was reopened on December 5, 2011 to allow<PRTPAGE P="10112"/>additional time for the public to submit comments. See 76 FR 75844 (December 5, 2011). The additional comment period ended on February 2, 2012.</P>
        <HD SOURCE="HD1">3. Proposed Supplements to Proposed Accessibility Guidelines for Pedestrian Facilities in the Public Right-of-Way</HD>

        <P>We are issuing this SNPRM to include specific provisions for shared use paths in the proposed accessibility guidelines for pedestrian facilities in the public right-of-way published in the<E T="04">Federal Register</E>on July 26, 2011. See 76 FR 44664 (July 26, 2011). The proposed accessibility guidelines for pedestrian facilities in the public right-of-way will be codified as an appendix to 36 CFR part 1190. The SNPRM would supplement the following sections of the proposed accessibility guidelines for pedestrian facilities in the public right-of-way: R105.5 Defined Terms; R204 and R302 Pedestrian Access Routes; R210 Protruding Objects; R218 Doors, Doorways, and Gates; and R304 Curb Ramps and Blended Transitions. The proposed supplements to these sections are set forth below.</P>
        <HD SOURCE="HD2">R105.5Defined Terms</HD>
        <HD SOURCE="HD3">Shared Use Path</HD>
        <P>The SNPRM would add a proposed definition of shared use path in R105.5 to read as follows:</P>
        <P>
          <E T="03">Shared Use Path.</E>A multi-use path designed primarily for use by bicyclists and pedestrians, including pedestrians with disabilities, for transportation and recreation purposes. Shared use paths are physically separated from motor vehicle traffic by an open space or barrier, and are either within the highway right-of-way or within an independent right-of-way.</P>
        <P>The proposed definition is based on the AASHTO Guide, which defines a shared use path as a bikeway physically separated from motor vehicle traffic by an open space or barrier, and either within the highway right-of-way or within an independent right of way. The AASHTO Guide notes that pedestrians, including pedestrians with disabilities, also use shared use paths and that they can serve transportation and recreation purposes. See AASHTO Guide, 5.1 Introduction. The U.S. Department of Transportation, Federal Highway Administration (FHWA) defines a shared use path similar to the AASHTO Guide.<SU>1</SU>
          <FTREF/>State transportation departments also define shared use paths similar to the AASHTO Guide.<SU>2</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>1</SU>The FHWA defines a shared use path as a multi-use trail or path physically separated from motorized vehicular traffic by an open space or barrier, either within the highway right-of-way or within an independent right of way, and usable for transportation purposes. The FHWA definition of shared use path is available at:<E T="03">http://www.fhwa.dot.gov/environment/bicycle_pedestrian/guidance/design_guidance/freeways.cfm.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>

            <SU>2</SU>For example, the Washington State Department of Transportation Design Manual (July 2012) defines a shared use path as a facility physically separated from motorized vehicular traffic within the highway right-of-way or on an exclusive right-of-way with minimal cross flow by motor vehicles. The Washington State Department of Transportation Design Manual is available at:<E T="03">http://www.wsdot.wa.gov/Publications/Manuals/M22-01.htm.</E>
          </P>
        </FTNT>
        <P>As noted in the AASHTO Guide, the primary factor that distinguishes shared use paths and sidewalks is the intended user. Shared use paths are designed for use by bicyclists and pedestrians, including pedestrians with disabilities. Sidewalks are designed for use by pedestrians, including pedestrians with disabilities, and are not intended for use by bicyclists. See AASHTO Guide, 5.2.2, Shared Use Paths Adjacent to Roadways (Sidepaths).</P>
        <HD SOURCE="HD3">Public Right-of-Way</HD>
        <P>The SNPRM would revise the proposed definition of public right-of-way in R105.5 to read as follows:</P>
        <P>
          <E T="03">Public Right-of-Way.</E>Public land acquired for or dedicated to transportation purposes, or other land where there is a legally established right for use by the public for transportation purposes.</P>
        <P>The NPRM proposed to define public right-of-way as public land or property, usually in interconnected corridors, that is acquired for or dedicated to transportation purposes. Some shared use paths may cross private land. In these situations, an easement or other legal means is used to establish a right for the public to use the portion of the land that the shared use path crosses for transportation purposes. The SNPRM would revise the proposed definition of public right-of-way to include these situations.</P>
        <HD SOURCE="HD2">R204 and R302Pedestrian Access Routes</HD>
        <P>The SNPRM would revise these sections relating to pedestrian access routes.</P>
        <HD SOURCE="HD2">R204.2Pedestrian Circulation Paths</HD>
        <P>The SNPRM would revise R204.2 to read as follows:</P>
        <P>
          <E T="03">R204.2Pedestrian Circulation Paths.</E>A pedestrian access route shall be provided within pedestrian circulation paths located in the public right-of-way. The pedestrian access route shall connect to accessible elements, spaces, and facilities required by this document and to accessible routes required by section 206.2.1 of appendix B to 36 CFR part 1191 or section F206.2.1 of appendix C to 36 CFR 1191 that connect building and facility entrances to public streets and sidewalks.</P>
        <P>As proposed in the NPRM, R204.2 would require a pedestrian access route to be provided within sidewalks and other pedestrian circulation paths located in the public right-of-way. The NPRM proposed to define a pedestrian circulation path as a prepared exterior or interior surface provided for pedestrian travel in the public right-of-way. See R105.5. Sidewalks and shared use paths are types of pedestrian circulation paths. As revised by the SNPRM, the term “pedestrian circulation paths” in R204.2 includes sidewalks and shared use paths.</P>
        <HD SOURCE="HD2">R302.3Continuous Width</HD>
        <P>The SNPRM would revise R302.3 to read as follows:</P>
        <P>
          <E T="03">R302.3Continuous Width.</E>Except as provided in R302.3.1 and R302.3.2, the continuous clear width of pedestrian access routes shall be 1.2 m (4.0 ft) minimum, exclusive of the width of the curb.</P>
        <P>
          <E T="03">R302.3.1Medians and Pedestrian Refuge Islands.</E>The clear width of pedestrian access routes within medians and pedestrian refuge islands shall be 1.5 m (5.0 ft) minimum.</P>
        <P>
          <E T="03">R302.3.2Shared Use Paths.</E>A pedestrian access route shall be provided for the full width of a shared use path.</P>
        <P>As proposed in the NPRM, R302.3 would require pedestrian access routes to be 4 feet wide minimum, except R302.3.1 would require pedestrian access routes within medians and pedestrian refuge islands to be 5 feet wide minimum to allow for passing space.</P>

        <P>The SNPRM would add a new provision at R302.3.2 that would require a pedestrian access route to be provided for the full width of a shared use path since shared use paths are typically two-directional and path users travel in each direction on the right hand side of the path, except to pass. The AASHTO Guide recommends that two-directional shared use paths should be 10 feet wide minimum. Where shared use paths are anticipated to serve a high percentage of pedestrians and high user volumes, the AASHTO Guide recommends that the paths should be 11 to 14 feet wide to enable a bicyclist to pass another path user travelling in the same direction, at the same time a path user is approaching from the opposite direction. In certain very rare circumstances, the AASHTO Guide permits the width of shared use paths to<PRTPAGE P="10113"/>be reduced to 8 feet. See AASHTO Guide, 5.2.1 Width and Clearance.</P>
        <HD SOURCE="HD2">R302.5Grade</HD>
        <P>The SNPRM would revise R302.5 to read as follows:</P>
        <P>
          <E T="03">R302.5Grade.</E>The grade of pedestrian access routes shall comply with R302.5.</P>
        <P>
          <E T="03">R302.5.1Within Street or Highway Right-of-Way.</E>Except as provided in R302.5.3, where pedestrian access routes are contained within a street or highway right-of-way, the grade of pedestrian access routes shall not exceed the general grade established for the adjacent street or highway.</P>
        <P>
          <E T="03">R302.5.2Not Within Street or Highway Right-of-Way.</E>Where pedestrian access routes are not contained within a street or highway right-of-way, the grade of pedestrian access routes shall be 5 percent maximum.</P>
        <P>
          <E T="03">R302.5.3Within Pedestrian Street Crossings.</E>Where pedestrian access routes are contained within a pedestrian street crossing, the grade of pedestrian access routes shall be 5 percent maximum.</P>
        <P>
          <E T="03">R302.5.4Physical Constraints.</E>Where compliance with R302.5.1 or R302.5.2 is not practicable due to existing terrain or infrastructure, right-of-way availability, a notable natural feature, or similar existing physical constraints, compliance is required to the extent practicable.</P>
        <P>
          <E T="03">R302.5.5Regulatory Constraints.</E>Where compliance with R302.5.1 or R302.5.2 is precluded by federal, state, or local laws the purpose of which is to preserve threatened or endangered species; the environment; or archaeological, cultural, historical, or significant natural features, compliance is required to the extent practicable.</P>
        <P>As proposed in the NPRM, R302.5 would require the grade of pedestrian access routes contained within a street or highway right-of-way, except at pedestrian street crossings, to not exceed the general grade established for the adjacent street or highway; and the grade of pedestrian access routes not contained within a street or highway right-of-way to be 5 percent maximum. R302.5.1 would require the grade of pedestrian access routes contained within a pedestrian street crossing to be 5 percent maximum.</P>
        <P>The SNPRM would renumber R302.5 to include a general provision in R302.5; the specific provision for the grade of pedestrian access routes contained within a street or highway right-of-way in R302.5.1; the specific provision for the grade of pedestrian access routes not contained within a street or highway right-of-way in R302.5.2; and the specific provision for the grade of pedestrian access routes contained within a pedestrian street crossing in R302.5.3.</P>
        <P>The SNPRM would add new provisions at R302.5.4 and R302.5.5 that would require compliance with the grade provisions in R302.5.1 or R302.5.2 to the extent practicable where compliance is not practicable due to physical constraints and where compliance is precluded by regulatory constraints. We propose to add these new provisions in response to public comments on the ANPRM, which included draft technical provisions for grade similar to those proposed in the R302.5. The comments noted that physical or regulatory constraints may prevent full compliance with the grade provisions. Physical constraints would include existing terrain or infrastructure, right-of-way availability, a notable natural feature, or similar existing physical constraints. Regulatory constraints would include federal, state, or local laws the purpose of which is to preserve threatened or endangered species; the environment; or archaeological, cultural, historical, or significant natural features.</P>
        <P>The proposed provisions are consistent with the AASHTO Guide. The AASHTO Guide recommends that the grade of a shared use path should not exceed 5 percent; but, where the path is adjacent to a roadway with a grade that exceeds 5 percent, the grade of the path should be less than or equal to the roadway grade. The AASHTO Guide notes that grades steeper than 5 percent are undesirable because ascents are difficult for many path users, and the descents can cause some path users to exceed the speeds at which they are competent or comfortable. See AASHTO Guide, 5.2.7 Grade.</P>
        <HD SOURCE="HD2">R210Protruding Objects</HD>
        <P>The SNPRM would revise R210 to read as follows:</P>
        <P>
          <E T="03">R210.1General.</E>Protruding objects shall comply with the applicable requirements in R210.</P>
        <P>
          <E T="03">R210.2Pedestrian Circulation Paths Other Than Shared Use Paths.</E>Objects along or overhanging any portion of a pedestrian circulation path other than a shared use path shall comply with R402 and shall not reduce the clear width required for pedestrian access routes.</P>
        <P>
          <E T="03">R210.3Shared Use Paths.</E>Objects shall not overhang or protrude into any portion of a shared use path at or below 2.4 m (8.0 ft) measured from the finish surface.</P>
        <P>As proposed in the NPRM, R210 would require objects along or overhanging any portion of a pedestrian circulation path to comply with the proposed technical provisions for protruding objects in R402 and to not reduce the clear width required for pedestrian access routes.</P>
        <P>The SNPRM would renumber R210 to include a general provision in R210.1 and a specific provision for pedestrian circulation paths other than shared use paths in R210.2 that would require objects along or overhanging any portion of the path to comply with the proposed technical provisions for protruding objects in R402 and to not reduce the clear width required for pedestrian access routes, as proposed in the NPRM.</P>
        <P>The SNPRM would add a new provision for shared use paths at R210.3 that would prohibit objects from overhanging or protruding into any portion of a shared use path at or below 8 feet measured from the finish surface.</P>
        <P>The proposed provision for shared used paths is consistent with the AASHTO Guide. The AASHTO Guide recommends 10 feet vertical clearance along shared use paths, and 8 feet minimum vertical clearance in constrained areas. The AASHTO Guide recommends that fixed objects should not be permitted to protrude within the vertical or horizontal clearance of a shared use path. See AASHTO Guide, 5.2.1 Width and Clearance.</P>
        <HD SOURCE="HD2">R218Doors, Doorways, and Gates</HD>
        <P>The SNPRM would revise R218 to read as follows:</P>
        <P>
          <E T="03">R218Doors, Doorways, and Gates.</E>Except for shared use paths, doors, doorways, and gates provided at pedestrian facilities shall comply with section 404 of Appendix D to 36 CFR to 36 CFR part 1191.</P>

        <P>The SNPRM would not apply the technical provisions for doors, doorways, and gates referenced in R218 to shared use paths to avoid conflicts with the AASHTO Guide. The AASHTO Guide does not recommend the use of gates or other barriers to prevent unauthorized motor vehicle entry to shared use paths because gates and barriers create permanent obstacles to path users. The AASHTO Guide recommends alternative methods to control unauthorized motor vehicle entry to shared use paths, including posting regulatory signs prohibiting motor vehicle entry and targeted surveillance and enforcement. Where there is a documented history of unauthorized entry by motor vehicles despite the use of alternative methods to control such entry, the need for bollards or other vertical barriers may be justified. The AASHTO Guide includes<PRTPAGE P="10114"/>recommended designs for bollards where justified. The AASHTO Guide recommends the use of one bollard in the center of the shared use path. Where more than one bollard is used, the AASHTO Guide recommends an odd number of posts spaced at 6 feet. The AASHTO Guide does not recommend two posts since they direct opposing path users toward the middle, creating conflict and the possibility of a head-on collision. See AASHTO Guide, 5.3.5 Other Intersection Treatments.</P>
        <HD SOURCE="HD2">R304Curb Ramps and Blended Transitions</HD>
        <P>The SNPRM would revise R304.5.1 to read as follows:</P>
        <P>
          <E T="03">R304.5.1Width.</E>The width of curb ramps and blended transitions shall comply with 304.5.1.1 or 304.5.1.2, as applicable. If provided, flared sides of curb ramp runs and blended transitions shall be located outside the width of the curb ramp run or blended transition.</P>
        <P>
          <E T="03">R304.5.1.1Pedestrian Circulation Paths Other Than Shared Use Paths.</E>In pedestrian circulation paths other than shared use paths, the clear width of curb ramp runs, blended transitions, and turning spaces shall be 1.2 m (4.0 ft) minimum.</P>
        <P>
          <E T="03">R304.5.1.2Shared Use Paths.</E>In shared use paths, the width of curb ramps runs and blended transitions shall be equal to the width of the shared use path.</P>
        <P>As proposed in the NPRM, R304.5.1 would require the clear width of curb ramp runs (excluding flared sides), blended transitions, and turning spaces to be 4 feet minimum.</P>
        <P>The SNPRM would renumber R304.5.1 to include a general provision in R304.5.1 that would clarify that if flared sides are provided at curb ramps and blended transitions, the flared sides are to be located outside the width of the curb ramp run or blended transition; and a specific provision for pedestrian circulation paths other than shared use paths in R304.5.1.1 that would require the clear width of curb ramp runs, blended transitions, and turning spaces to be 4 feet minimum, as proposed in the NPRM.</P>
        <P>The SNPRM would add a new provision for shared use paths at R304.5.1.2 that would require the width of curb ramps runs and blended transitions to be equal to the width of the shared use path.</P>
        <P>The proposed provision for shared used paths is consistent with the AASHTO Guide. The AASHTO Guide recommends that where curb ramps are provided on shared use paths, the curb ramps should extend the full width of the path, not including any flared sides. See AASHTO Guide, 5.3.5 Other Intersection Treatments.</P>
        <HD SOURCE="HD1">4. Comparison of Proposed Technical Provisions Applicable to Shared Use Paths and AASHTO Guide</HD>
        <P>The proposed technical provisions applicable to shared used paths in the proposed accessibility guidelines for pedestrian facilities in the public right-of-way, as supplemented by the SNPRM, and the design criteria for shared use paths in the AASHTO Guide are compared in the table below.</P>
        <GPOTABLE CDEF="xl100,xl100" COLS="2" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Proposed accessibility guidelines for pedestrian facilities in the public right-of-way<LI>Proposed technical provisions applicable to shared use paths</LI>
            </CHED>
            <CHED H="1">AASHTO Guide for the development of bicycle facilities (2012)<LI>Chapter 5: design of shared use paths</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">
              <E T="03">R302.3.2Shared Use Paths.</E>A pedestrian access route shall be provided for the full width of a shared use path.</ENT>
            <ENT>
              <E T="03">5.2.1Width and Clearance</E>
              <LI>The minimum paved width for a two-directional shared use path is 10 ft (3.0 m). * * * In very rare circumstances, a reduced width of 8 ft (2.4 m) may be used. * * * Wider pathways, 11 to 14 ft (3.4 to 4.2 m) are recommended in locations that are anticipated to serve a high percentage of pedestrians (30 percent or more of the total pathway volume) and higher user volumes (more than 300 total users in the peak hour).</LI>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="01">
              <E T="03">R302.5Grade.</E>The grade of pedestrian access routes shall comply with R302.5.<LI O="xl">
                <E T="03">R302.5.1Within Street or Highway Right-of-Way.</E>Except as provided in R302.5.3, where pedestrian access routes are contained within a street or highway right-of-way, the grade of pedestrian access routes shall not exceed the general grade established for the adjacent street or highway.</LI>
              <LI O="xl">
                <E T="03">R302.5.2Not Within Street or Highway Right-of-Way.</E>Where pedestrian access routes are not contained within a street or highway right-of-way, the grade of pedestrian access routes shall be 5 percent maximum.</LI>
              <LI O="xl">
                <E T="03">R302.5.3Within Pedestrian Street Crossings.</E>Where pedestrian access routes are contained within a pedestrian street crossing, the grade of pedestrian access routes shall be 5 percent maximum.</LI>
            </ENT>
            <ENT>
              <E T="03">5.2.7Grade</E>
              <LI>The maximum grade of a shared use path adjacent to a roadway should be 5 percent, but the grade should generally match the grade of the adjacent roadway. Where a shared use path runs along a roadway with a grade that exceeds 5 percent, the sidepath grade may exceed 5 percent but must be less than or equal to the roadway grade. Grades on shared use paths in independent rights-of-way should be kept to a minimum. Grades steeper than 5 percent are undesirable because the ascents are difficult for many path users, and the descents can cause some users to exceed the speeds at which they are competent or comfortable. * * * Grades on paths in independent rights-of-way should also be limited to 5 percent maximum.</LI>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="22">
              <E T="03">R302.5.4Physical Constraints.</E>Where compliance with R302.5.1 or R302.5.2 is not practicable due to existing terrain or infrastructure, right-of-way availability, a notable natural feature, or similar existing physical constraints, compliance is required to the extent practicable.</ENT>
          </ROW>
          <ROW>
            <ENT I="22">
              <E T="03">R302.5.5Regulatory Constraints.</E>Where compliance with 302.5.1 or 302.5.2 is precluded by federal, state, or local laws the purpose of which is to preserve threatened or endangered species; the environment; or archaeological, cultural, historical, or significant natural features, compliance is required to the extent practicable.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">
              <E T="03">R302.6Cross Slope.</E>Except as provided in R302.6.1 and R302.6.2, the cross slope of pedestrian access routes shall be 2 percent maximum.<LI O="xl">
                <E T="03">R302.6.1Pedestrian Street Crossings Without Yield or Stop Control.</E>Where pedestrian access routes are contained within pedestrian street crossings without yield or stop control, the cross slope of the pedestrian access route shall be 5 percent maximum.</LI>
            </ENT>
            <ENT>
              <E T="03">5.2.5Cross Slope</E>
              <LI>As described in the previous section, 1 percent cross slopes are recommended on shared use paths, to better accommodate people with disabilities and to provide enough slope to convey surface drainage in most situations.</LI>
            </ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="10115"/>
            <ENT I="22">
              <E T="03">R302.6.2Midblock Pedestrian Street Crossings.</E>Where pedestrian access routes are contained within midblock pedestrian street crossings, the cross slope of the pedestrian access route shall be permitted to equal the street or highway grade.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">
              <E T="03">R302.7Surfaces.</E>The surfaces of pedestrian access routes and elements and spaces required to comply with R302.7 that connect to pedestrian access routes shall be firm, stable, and slip resistant and shall comply with R302.7.<LI O="xl">
                <E T="03">R302.7.1Vertical Alignment.</E>Vertical alignment shall be generally planar within pedestrian access routes (including curb ramp runs, blended transitions, turning spaces, and gutter areas within pedestrian access routes) and surfaces at other elements and spaces required to comply with R302.7 that connect to pedestrian access routes. Grade breaks shall be flush. Where pedestrian access routes cross rails at grade, the pedestrian access route surface shall be level and flush with the top of rail at the outer edges of the rails, and the surface between the rails shall be aligned with the top of rail.</LI>
              <LI O="xl">
                <E T="03">R302.7.2Vertical Surface Discontinuities.</E>Vertical surface discontinuities shall be 13 mm (0.5 in) maximum. Vertical surface discontinuities between 6.4 mm (0.25 in) and 13 mm (0.5 in) shall be beveled with a slope not steeper than 50 percent. The bevel shall be applied across the entire vertical surface discontinuity.</LI>
            </ENT>
            <ENT>
              <E T="03">5.2.9Surface Structure</E>
              <LI>Hard, all-weather pavement surfaces are generally preferred over those of crushed aggregate, sand, clay, or stabilized earth.* * * Unpaved surfaces may be appropriate on rural paths, where the intended use of the path is primarily recreational, or as a temporary measure to open a path before funding is available for paving. Unpaved pathways should be constructed of materials that are firm and stable. * * * It is important to construct and maintain a smooth riding surface on shared use paths.* * * Utility covers (i.e., manholes) and bicycle-compatible drainage grates should be flush with the surface of the pavement on all sides.* * * Railroad crossings should be smooth and should be designed at an angle between 60 and 90 degrees to the direction of travel to minimize the possibility of falls.</LI>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="22">
              <E T="03">R302.7.3Horizontal Openings.</E>Horizontal openings in gratings and joints shall not permit passage of a sphere more than 13 mm (0.5 in) in diameter. Elongated openings in gratings shall be placed so that the long dimension is perpendicular to the dominant direction of travel.</ENT>
          </ROW>
          <ROW>
            <ENT I="22">
              <E T="03">R302.7.4Flangeway Gaps.</E>Flangeway gaps at pedestrian at-grade rail crossings shall be 64 mm (2.5 in) maximum on non-freight rail track and 75 mm (3 in) maximum on freight rail track.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">
              <E T="03">R210.3Shared Use Paths.</E>Objects shall not overhang or protrude into any portion of a shared use path at or below 2.4 m (8.0 ft) measured from the finish surface.</ENT>
            <ENT>
              <E T="03">5.2.1Width and Clearance</E>
              <LI>The desirable vertical clearance to obstructions is 10 ft (3.0 m). Fixed objects should not be permitted to protrude within the vertical or horizontal clearance of a shared use path. The recommended minimum vertical clearance that can be used in constrained areas is 8 ft (2.4 m).</LI>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="01">
              <E T="03">R304.5.1.2Shared Use Paths.</E>In shared use paths, the width of curb ramps runs and blended transitions shall be equal to the width of the shared use path.<LI O="xl">
                <E T="03">R305.1.4Size.</E>Detectable warning surfaces shall extend 610 mm (2.0 ft) minimum in the direction of pedestrian travel. At curb ramps and blended transitions, detectable warning surfaces shall extend the full width of the ramp run (excluding any flared sides).</LI>
            </ENT>
            <ENT>
              <E T="03">5.3.5Other Intersection Treatments</E>
              <LI>The opening of a shared use path at the roadway should be at least the same width as the shared use path itself. If a curb ramp is provided, the ramp should be the full width of the path, not including any flared sides if utilized.* * * Detectable warnings should be placed across the full width of the ramp.</LI>
            </ENT>
          </ROW>
        </GPOTABLE>
        <HD SOURCE="HD1">5. Conflicts Between Shared Path Users</HD>
        <P>Public comments submitted in response to the ANPRM expressed concern about the risk of collisions between pedestrians who are blind or have low vision and bicyclists who pass them too closely at fast speeds, and at intersections where a shared use path crosses another shared use path or a sidewalk. According to the AASHTO Guide, the 85th percentile speed for recreational bicyclists is 18 miles per hour. See AASHTO Guide, 5.2.4 Design Speed. The comments noted that bicycles are relatively quiet and pedestrians who are blind or have low vision may not be aware when bicyclists are approaching and passing them or crossing their path at intersections. Pedestrians with other disabilities may also have limited awareness of approaching bicyclists. For example, individuals who are deaf or hard of hearing may not be aware of a bicycle approaching from behind even when riders indicate their presence audibly. Individuals with limited mobility who may be alert to bicyclists may find it difficult to move aside in time to avoid collision. The comments recommended that traffic on shared use paths be regulated and strictly enforced in order to protect pedestrians. For example, a comment stated that bicyclists should be required to always yield to pedestrians. The comments also recommended design solutions to avoid conflicts between users, including separate pathways for pedestrians and bicyclists; and detectable warning surfaces at intersections where a shared use path crosses another shared use path or a sidewalk. These design solutions are discussed below.</P>
        <HD SOURCE="HD2">Separate Pathways for Pedestrians and Bicyclists</HD>

        <P>An organization representing individuals who are blind and have low-vision stated that “all shared use paths present an unacceptable safety risk to blind or visually impaired pedestrians unless there is a clear separation between pedestrians and other motorized and non-motorized vehicles including bicyclists.” The comments noted that path users cannot be expected to always follow the “rules of the road” and suggested that if paths cannot be physically separated that lanes for pedestrians and other users should be marked tactilely. An organization of educators and rehabilitation professionals who work with individuals who are blind suggested that blind pedestrians may have considerable difficulty maintaining the course, particularly on two-<PRTPAGE P="10116"/>directional shared use paths where all users are expected to travel on the right hand side of the path in each direction and bicyclists pass pedestrians and slower moving path users on their left hand side. In addition to the recommendation to physically separate pedestrians and bicyclists, the comments suggested that it may be necessary to separate the two directions of travel within each pathway, particularly on busy paths. The comments, however, acknowledged that determining what volume of users should require two-directional separation would be a challenge.</P>
        <P>The AASHTO Guide makes a number of recommendations to minimize conflicts between pedestrians and bicyclists. These recommendations include required sight triangles to ensure that bicyclists have the needed yielding distance to avoid conflicts, and additional width around horizontal curves to allow safe distance between users. See AASHTO 5.2.8, Stopping Sight Distance. The AAHSTO Guide also recommends use of a centerline stripe within a path to provide directional separation and to indicate when passing is permitted. For paths with “extremely heavy volume”, the AASHTO Guide recommends two alternatives for segregation of pedestrians and bicyclists. The first option is to provide separate lanes within a single path; pedestrians have a bidirectional lane and bicyclists have two one-directional lanes. Such separation is not recommended unless a minimum path width of 15 feet can be provided (10 feet for bicycles and 5 feet for pedestrians). A second alternative is to physically separate user groups, particularly where the pathway volume is “extremely heavy” and where sites and settings, such as one that constricts the path width, necessitate divergent pathways. Physically separated pathways also are recommended where the origins and destinations of pedestrians and bicyclists differ. The AAHSTO Guide notes that both alternatives (lane separation and physical separation) may not be effective unless the volume of bicycle traffic is sufficient to discourage pedestrians from encroaching into the bicycle lanes and that these solutions will not necessarily be needed for the full length of a shared use path. See AASHTO Guide, 5.2.1 Width and Clearance.</P>
        <P>We agree with the comments that physical separation between pedestrians and other users would likely render shared use paths safer for, and more accessible to, individuals with disabilities and others. However, the AASHTO Guide does not recommend physical separation of user groups unless the traffic volume or other considerations make separate pathways necessary. The AASHTO Guide provides little guidance regarding methods for determining the point at which traffic volume or other considerations would justify separation of the pathways. In the absence of any data on which to base such a requirement, we are not proposing to require physically separated pathways for pedestrians and bicyclists. The impact of such a requirement if applied to the full length of all shared use paths would likely result in many not being constructed due to the increased costs associated with more land and the need to engineer and construct two pathways instead of one.</P>
        <P>The comments suggested that enhanced signage and warnings, including audible signs and tactile pavement markings would improve the ability of blind pedestrians to remain within their lanes. In Great Britain, tactile pavement markings are used to indicate bicycle and pedestrian lanes. A ladder pattern is used to indicate the start and end of the pedestrian lane; a tramline pattern is used to indicate the start and end of the bicycle lane; and a tactile dividing line is used to indicate the separation between the lanes.<SU>3</SU>
          <FTREF/>At least one U.S. manufacturer makes tactile pavement markings for shared use paths. We request comments on whether tactile pavement markings have been used on any shared use paths in the U.S. and the experience with such markings. We also request comments on other design solutions to reduce potential conflicts between pedestrians who are blind or have low vision and bicyclists. Comments should include factors that would make such solutions necessary.</P>
        <FTNT>
          <P>

            <SU>3</SU>Department of Transport, “Tactile Markings for Segregated Shared Use by Cyclists and Pedestrians” [available at:<E T="03">http://www.ukroads.org/webfiles/TAL%204-90%20Tactile%20Markings%20for%20Segregated%20Shared%20Use.pdf]</E>; Department for Transport, “Guidance on the Use of Tactile Paving Surfaces, “Chapter 5—Segregated Shared Cycle Track/Footway Surface and Central Delineator Strip [available at:<E T="03">http://www.dft.gov.uk/publications/guidance-on-the-use-of-tactile-paving-surfaces/]</E>; and Department of Transport,” Shared Use Routes for Pedestrians and Cyclists,” Chapter 6—General Design Considerations, 6.18 and 6.19 [available at:<E T="03">http://assets.dft.gov.uk/publications/ltn-01-12/shared-use-routes-for-pedestrians-and-cyclists.pdf].</E>
          </P>
        </FTNT>
        <P>We are considering including an advisory section in the final accessibility guidelines on separate pathways for pedestrians and bicyclists. Advisory sections are not mandatory requirements but provide guidance for entities who want to exceed the minimum requirements for accessible design. We request comments on information to include in the advisory section.</P>
        <HD SOURCE="HD2">Detectable Warning Surfaces at Shared Use Path Intersections</HD>
        <P>Detectable warning surfaces consist of small truncated domes that are integral to a walking surface and that are detectable underfoot. The proposed accessibility guidelines for pedestrian facilities in the public right-of-way would require the use of detectable warning surfaces to indicate the boundary between a pedestrian route and a vehicular route where there is a curb ramp or blended transition; and the boundary of passenger boarding platforms at transit stops for buses and rail vehicles and at passenger boarding and alighting areas at sidewalk or street level transit stops for rail vehicles. See R208 and R305.</P>
        <P>Because pedestrians who are blind would not be aware of bicyclists approaching from the left or right hand side at intersections, we are considering including a requirement in the final accessibility guidelines to provide detectable warning surfaces where a shared use path intersects another shared use path or a sidewalk to indicate the boundaries where bicyclists may be crossing the intersection. The edge of the detectable warning surface would be installed between 6 inches minimum and 12 inches maximum from the edge of the intersecting segments of the shared use paths and sidewalks. The detectable warning surface would extend 2 feet minimum in the direction of pedestrian travel and the full width of the intersecting segments. We request comments on this issue.</P>
        <HD SOURCE="HD1">6. Regulatory Analyses</HD>

        <P>We prepared a preliminary regulatory assessment discussing the cost and benefits of the proposed accessibility guidelines for pedestrian facilities in the public right-of-way and an initial regulatory flexibility analysis of the impacts on small governmental jurisdictions with a population of less than 50,000 when the NPRM was issued. These regulatory analyses are available on our Web site at:<E T="03">http://www.access-board.gov/prowac/.</E>
        </P>

        <P>There is no database available on the number of shared use paths in the United States. AASHTO surveyed five state transportation departments when preparing comments on the ANPRM. The responding departments reported approximately 1,500 to 3,000 miles of existing shared use paths in their states. The Alliance for Biking and Walking surveyed more than 50 large cities about<PRTPAGE P="10117"/>their bicycle and pedestrian facilities.<SU>4</SU>
          <FTREF/>The average number of miles of existing shared use paths per city was 70 miles, and ranged from 3.1 miles in Milwaukee to 328 miles in New York City. The cities used federal funds to construct many of the shared use paths.</P>
        <FTNT>
          <P>
            <SU>4</SU>Alliance for Biking and Walking, “Bicycling and Walking in the United States 2012 Benchmarking Report.”</P>
          <P>The report is available at:<E T="03">http://www.peoplepoweredmovement.org/site/.</E>
          </P>
        </FTNT>
        <P>As discussed above, the proposed technical provisions applicable to shared use paths are consistent with the AASHTO Guide. State and local government entities that design and construct shared use paths generally use the AASHTO Guide. The SNPRM is not expected to increase the costs of constructing shared use paths for state and local government entities that use the AASHTO Guide.</P>
        <P>We request comments on the following to assess the impacts of the SNPRM:</P>
        <P>• The extent to which the AASHTO Guide, or other design guides and standards are used for shared use paths.</P>
        <P>• Whether any of the proposed provisions applicable to shared use paths would result in additional costs for design work, materials, earthmoving, retaining structures, or other items compared to construction practices or design guides and standards currently used? Commenters are encouraged to identify the specific provisions that would result in additional costs and estimate the additional costs on a per mile basis to the extent possible.</P>
        <P>• Whether any of the proposed provisions applicable to shared use paths would result in any additional costs, such as maintenance and operational costs, compared to current practices? Commenters are encouraged to identify the specific provisions that would result in additional costs and estimate the additional costs on a per mile basis to the extent possible.</P>
        <P>• What are the benefits of the proposed provisions applicable to shared use paths?</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 36 CFR Part 1190</HD>
          <P>Buildings and facilities, Civil rights, Individuals with disabilities, Transportation.</P>
        </LSTSUB>
        <SIG>
          <NAME>Susan Brita,</NAME>
          <TITLE>Chair.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03298 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 8150-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
        <CFR>38 CFR Part 17</CFR>
        <RIN>RIN 2900-AO15</RIN>
        <SUBJECT>Use of Medicare Procedures To Enter Into Provider Agreements for Extended Care Services</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Department of Veterans Affairs.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This rulemaking proposes to amend the medical regulations of the Department of Veterans Affairs (VA) to allow VA to use Medicare or State procedures to enter into provider agreements to obtain extended care services from non-VA providers. In addition, this rulemaking proposes to include home health care, palliative care, and noninstitutional hospice care services as extended care services, when provided as an alternative to nursing home care. Under this proposed rule, VA would be able to obtain extended care services for veterans from providers who are closer to veterans' homes and communities.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be received by VA on or before March 15, 2013.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Written comments may be submitted by email through<E T="03">http://www.regulations.gov</E>; by mail or hand-delivery to Director, Regulations Management (02REG), Department of Veterans Affairs, 810 Vermont Avenue NW., Room 1068, Washington, DC 20420; or by fax to (202) 273-9026. Comments should indicate that they are submitted in response to “RIN 2900-AO15, Use of Medicare Procedures to Enter Into Provider Agreements for Extended Care Services.” Copies of comments received will be available for public inspection in the Office of Regulation Policy and Management, Room 1063B, between the hours of 8:00 a.m. and 4:30 p.m. Monday through Friday (except holidays). Please call (202) 461-4902 for an appointment. In addition, during the comment period, comments may be viewed online through the Federal Docket Management System (FDMS) at<E T="03">http://www.regulations.gov</E>.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Daniel Schoeps, Office of Geriatrics and Extended Care (10P4G), Department of Veterans Affairs, 810 Vermont Avenue NW., Washington, DC 20420; (202) 461-6763. (This is not a toll-free number.)</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Subsection (a) of 38 U.S.C. 1710B authorizes VA to provide extended care services to eligible veterans, including geriatric evaluation, nursing home care, domiciliary services, and adult day health care. Subsection (a) of 38 U.S.C. 1720 authorizes VA to pay for the nursing home care in non-VA facilities of eligible veterans and eligible members of the Armed Forces. Section 1720(f) authorizes VA to furnish (in VA and non-VA facilities) adult day health care to enrolled veterans who would otherwise need nursing home care. Contracts between VA and these non-VA facilities are currently negotiated under Federal contract statutes and regulations (including the Federal Acquisition Regulation, which is set forth at 48 CFR chapter 1; and VA Acquisition Regulations, which are set forth at 48 CFR chapter 8).</P>
        <P>We propose to establish a new 38 CFR 17.75, which would implement VA's authority to use Medicare procedures to enter into provider agreements. Section 105 of the Veterans Health Care, Capital Asset, and Business Improvement Act of 2003 (Pub. L. 108-170) amended section 1720 to authorize VA to use these procedures. This amendment, which is codified at 38 U.S.C. 1720(c)(1), authorizes VA to enter into agreements with providers of nursing home care, adult day health care, and other community-based extended care services under “the procedures available for entering into provider agreements under section 1866(a) of the Social Security Act.” Section 1866(a) (codified at 42 U.S.C. 1395cc(a)) authorizes the Department of Health and Human Services to enter into agreements with participating Medicare providers, and specifies the terms of those agreements.</P>
        <P>The plain language of 38 U.S.C. 1720(c)(1)(B) authorizes VA, in its discretion, to furnish extended care services through non-VA providers using the above-described noncontractual mechanism. Moreover, the legislative history of Public Law 108-170 further shows that its purpose was to improve VA's ability to furnish eligible veterans with extended care services of non-VA providers by using a noncontractual mechanism. A Senate committee report explains that Medicare procedures are simpler and less burdensome than VA contracting procedures. The report includes the following discussion of this provision:</P>
        
        <EXTRACT>

          <P>Under current law, VA is authorized to enter into contractual arrangements with private providers of extended care services to serve the needs of veterans. Federal reporting requirements relating to the demographics of contractor employees and applicants are required to be submitted to the Department of Labor under these contractual arrangements. The Committee has learned that, due to these reporting requirements,<PRTPAGE P="10118"/>many small providers of extended care services are unable, or they are unwilling, to admit VA patients. Many such providers have apparently concluded that reimbursement from VA for caring for one or two veterans is not worth the cost of compiling and reporting the data required by general Federal contract law.</P>
          <P>The Social Security Act allows the Centers for Medicare and Medicaid Services (hereinafter, “CMS”) to enter into provider agreements for the provision of care to both Medicare and Medicaid beneficiaries. Such agreements require that contractors comply with Federal laws concerning hiring practices. But they do not require that providers prepare reports of such compliance. Nor do they subject providers to annual audits like most Federal contracts do. Not surprisingly, CMS is more successful than VA in inducing smaller providers to provide care to its beneficiaries.</P>
          <P>Section 102 of the Committee bill places VA contractors in a similar position as CMS contractors with respect to Federal reporting requirements. By this action, the Committee seeks to encourage VA to bring care closer to veterans' homes and community support structures by contracting with small community-based providers. Even so, however, the Committee fully anticipates and expects that VA will require compliance with all applicable Federal laws concerning employment and hiring practices.</P>
        </EXTRACT>
        
        <FP>S. Rep. No. 108-193, at 6 (2003), as reprinted in 2003 U.S.C.C.A.N. 1783, 1788. To clarify the above quotation, the Social Security Act allows for the Centers for Medicare and Medicaid Services (CMS) to enter into provider agreements with Medicare providers only. States, not CMS, enter into provider agreements with Medicaid providers. Medicare agreements enable a provider to bill and receive reimbursement for Medicare-covered services furnished by the provider. The terms of those agreements often concern the kind and quality of care to be provided. Although those CMS and State agreements do not involve the provision of care, Congress specifically authorized VA to use provider agreements under 38 U.S.C. 1720(c)(1)(B) “for furnishing” care. Accordingly, we propose to establish a VA regulation regarding use of provider agreements. We believe that by using these agreements, VA would be able to obtain services from providers who are closer to veterans' homes and community support structures.</FP>
        <P>Proposed § 17.75(a) would define “[e]xtended care services” as “geriatric evaluation; nursing home care; domiciliary services; adult day health care; noninstitutional palliative care, noninstitutional hospice care, and home health care when they are noninstitutional alternatives to nursing home care; and respite care.” The proposed definition is derived from 38 U.S.C. 1710B(a), which requires VA to “operate and maintain a program to provide extended care services,” and requires that such extended care services include geriatric evaluation, nursing home care, domiciliary services, adult day health care, respite care, and “[s]uch other noninstitutional alternatives to nursing home care as the Secretary may furnish as medical services under [38 U.S.C. 1701(10)].” 38 U.S.C. 1710B(a)(1)-(6).</P>
        <P>We propose to include home health care in the definition of “[e]xtended care services” as a noninstitutional alternative to nursing home care because in many circumstances it would be a noninstitutional alternative to nursing home care. For example, a veteran applying for nursing home care would receive a person-centered assessment by a VA health care team. The team, working with the veteran and caregiver, would explore care needs and how these needs could be met. In this process, they may decide that a combination of skilled nursing, home health aide, and respite services would meet the veteran's needs and allow the veteran to remain at home. In this case, home health services would avert a nursing home placement. We also propose to include noninstitutional palliative and noninstitutional hospice care in the definition because they would always be alternatives to nursing home care.</P>
        <P>We understand that Medicare and States do not necessarily enter into provider agreements for all the services listed under the proposed definition for “extended care services.” We are proposing only to enter into provider agreements with providers that do have a Medicare or State provider agreement for the services listed in this proposed rule as “extended care services.” VA would continue to use contracts and other mechanisms to ensure that veterans receive needed health care services for which they are eligible, but for which there is no available provider agreement. Additionally, many States enter into provider agreements for a broader array of services than those listed in this proposed rule. We do not intend to enter into agreements that would expand beyond the scope of those services specifically listed in the proposed definition of extended care services.</P>
        <P>Including home health care, noninstitutional palliative care, and noninstitutional hospice care in the definition of extended care services would not require VA to consider these services as extended care services for purposes of determining whether a copayment is required. Noninstitutional hospice care is exempt from both outpatient and extended care copayments. 38 U.S.C. 1710(g)(1), 1710B(c)(2)(B). Noninstitutional palliative care is a form of home health care, and the law currently requires VA to charge the outpatient copayment for home health care. 38 U.S.C. 1710(g)(1).</P>
        <P>As noted above, under 38 U.S.C. 1710B(a)(5), VA is required to “operate and maintain a program to provide extended care services” that includes “[s]uch * * * noninstitutional alternatives to nursing home care as the Secretary may furnish as medical services under [38 U.S.C. 1701(10)]”. 38 U.S.C. 1710B(a)(5). However, section 1701 no longer contains a subsection (10).</P>
        <P>Prior to enactment of section 801 of Public Law 110-387, 38 U.S.C. 1701(10) defined medical services to include noninstitutional extended care services provided through December 31, 2008, and defined such services as follows: “[T]he term `noninstitutional extended care services' means such alternatives to institutional extended care which [VA] may furnish (i) directly, (ii) by contract, or (iii) (through provision of case management) by another provider or payer.” See 38 U.S.C. 1710(10) (2008). With the enactment of Public Law 110-387 in 2008, section 1701 was amended to essentially move subsection (10) to subsection (6)(E) of section 1701 which provides that medical services include “[n]oninstitutional extended care services, including alternatives to institutional extended care that [VA] may furnish directly, by contract, or through provision of case management by another provider or payer.” Public Law 110-387, title VIII, § 801 (Oct. 10, 2008). Thus, the language of former subsection (10) and current subsection (6)(E) is virtually identical, except that subsection (6)(E) does not contain the 2008 sunset provision. We therefore believe that the reference to section 1701(10) in 38 U.S.C. 1710B(a)(5) must now be read as a reference to section 1701(6)(E).</P>
        <P>Consistent with section 1720(c)(1), we would define “[p]rovider” in § 17.75(a) to mean any non-VA entity that provides extended care services and is participating in Medicare under title XVIII of the Social Security Act or a State Medicaid plan under title XIX of the Social Security Act (42 U.S.C. 1396 et seq.) pursuant to a valid provider agreement. This could include physicians and other providers who provide extended care services to veterans in non-VA nursing homes.</P>

        <P>In proposed paragraph (b), we would implement VA's authority under section 1720(c)(1) to obtain extended care<PRTPAGE P="10119"/>services from non-VA providers, and would set forth the conditions under which such services may be obtained. Paragraph (b)(1) would prescribe that VA may enter into provider agreements for extended care services with non-VA providers who have a Medicare provider agreement with CMS. Paragraph (b)(2) would prescribe that VA may also enter into provider agreements for extended care services with non-VA providers who do not have a Medicare provider agreement with CMS if the provider is participating in a State Medicaid plan. Section 1720(c)(1) clearly authorizes VA to enter into provider agreements with non-VA providers of extended care services that participate in the Medicare program or a State Medicaid plan. A number of States enter into provider agreements related to services not otherwise covered by Medicare. For example, States often enter into provider agreements with Medicaid adult day health care providers, which are not eligible for similar agreements under Medicare.</P>
        <P>Proposed paragraph (c)(1) would establish the procedure that VA would use to notify a provider of the agreement that VA proposes to use to obtain extended care services from the provider. The Director of the VA medical center of jurisdiction would provide written notification identifying the applicable Medicare or State Medicaid provider agreement to be used and the changes and additional terms that would apply to the agreement with VA, and would request written acceptance of the agreement from the provider. This documentation would serve as a record for both VA and the provider that an agreement is in place and of the parties' acceptance of all the terms of the adopted agreement. Therefore, VA would not attempt to obtain services under a provider agreement from the provider until after the provider's acceptance is received. For providers with both Medicare and State Medicaid agreements, the letter would clarify which of the two provider agreements would be used as the basis for VA's provider agreement.</P>
        <P>Paragraph (c)(2) would establish that the terms and rates of a provider's agreement with VA would be the same as the terms and rates of the provider's separate Medicare provider agreement with CMS or agreement under a State Medicaid plan, or, if a provider has agreements with both Medicare and under a State Medicaid plan, the terms and rates would be the same as the agreement with the highest rates. VA's payment under the agreement with the highest rates would serve as an incentive to encourage providers to enter into agreements with VA for the care of veterans. We interpret VA's authority under section 1720(c)(1)(B) to use Medicare procedures as also authorizing the use of rates established under the appropriate Medicare fee schedule or payment system because there are no procedures for rate negotiation in obtaining Medicare provider agreements.</P>
        <P>Although a provider's agreement with VA would generally contain the same terms as the provider's separate Medicare provider agreement or agreement under a State Medicaid plan, VA would need unique terms for purposes of identifying VA as the Government agency entering into the agreement with the provider and paying for the provider's services for veterans. Since the purpose of this proposed rule is to address the needs of specific veterans or groups of veterans based upon location and the availability of VA resources, VA might also need unique agreement terms to limit the scope of the agreement consistent with VA's authority under section 1720(c)(1)(B). Accordingly, proposed paragraph (c)(3) would clarify that a provider's agreement with VA will not be the same as the provider's agreement with CMS under Medicare or under a State Medicaid plan to the extent that the provider's agreement with VA will identify VA as the Government agency entering into the agreement and specify that the provider's services are for specific veterans or groups of veterans. It would also make clear that the provider's agreement with VA would be administered by VA according to the procedures in this proposed rule and not under the rules applicable to the administration of Medicare provider agreements with CMS or agreements under a State Medicaid plan. In all other respects, VA intends that a provider's agreement with VA will be the same as the provider's Medicare provider agreement with CMS or under a State Medicaid plan.</P>
        <P>Proposed paragraph (d) would delegate to the Director of the VA medical center of jurisdiction (or a designee) the authority to enter into an agreement under the proposed rule. Under paragraph (d)(1), we would also establish that the criteria for whether to enter into an agreement under this section will be based on the needs of local veterans and the ability of VA to provide for those needs. For example, where VA does not provide equivalent care in a particular locality, or where providing VA care would be more expensive than providing care through a non-VA provider, VA would enter into agreements under this section. Similarly, if resources permit, wherever possible VA would enter into an agreement with a provider selected by the veteran. This is consistent with the purpose of section 1720(c)(1)(B), which is to help veterans receive the care that they require from providers in their own communities, as well as to improve the efficiency of care delivery from an economic perspective. However, we do not interpret section 1720(c)(1) as creating any right to care pursuant to a provider agreement or any right to enter into a provider agreement with VA. We interpret the statute as authorizing care pursuant to an agreement when a Director, based upon medical judgment and evaluation of available resources, determines that an agreement is in the best interest of the veteran under the Director's care.</P>
        <P>Under proposed paragraph (d)(2), VA would empower the veteran to select his or her preferred provider, should more than one provider exist within a given region, subject to the provider's determination to accept the veteran, clinical appropriateness and available resources at the VA medical center of jurisdiction. VA understands the significance of placing such an important life decision in the hands of the veteran and would only intervene if a provider was not able to provide the care clinically required by the veteran, or the VA medical center of jurisdiction is simply unable to accommodate the veteran's selection due to limited resources. Foreseeable strains on resources that might prevent VA from accommodating a veteran's request could include whether the veteran has special needs that can be addressed by resources in that region or whether VA has sufficient staff to monitor the veteran in a particular facility due to the facility being remote or because VA is monitoring several veterans at another facility that is distant from the veteran's preferred provider. The decision to approve or deny a particular provider for an agreement with VA would be made by the Director (or designee) according to the criteria prescribed in paragraphs (d)(2)(A), (B), and (C).</P>
        <P>Proposed paragraph (d)(3) would establish that the factual determination of whether a provider is eligible to enter into an agreement with VA to provide extended care services for veterans will be made based on evidence of an existing Medicare provider agreement or agreement under a State Medicaid plan as verified through Web sites maintained by CMS or the appropriate State office.</P>

        <P>Proposed paragraph (e) would govern termination of a VA provider agreement. Under paragraph (e)(1), we would allow<PRTPAGE P="10120"/>a provider to voluntarily terminate an agreement but we would require the provider to notify VA at least 15 days in advance of the planned termination and provide the intended date of termination. The 15-day requirement would provide VA with a reasonable amount of time to secure alternative arrangements for affected veterans. VA would require 15 days to find an arrangement that is suitable for the veteran and provides a potential for long-term care. We determined that a notice of termination period of less than 15 days would likely require an unsatisfactory short-term solution. Such a solution might require multiple relocations of, or multiple caregiver changes for, an affected veteran in order to meet their immediate health care needs. We have determined that the 15-day notice requirement would allow VA to protect veterans from the physical, mental, and emotional health risks caused by multiple changes in their care plan and/or living arrangement.</P>
        <P>Proposed paragraph (e)(2) would set forth when VA may terminate an agreement. VA would also be required to give providers at least 15 days notice before terminating an agreement. If, however, VA finds that the health of the veteran is in immediate jeopardy, VA would be authorized to terminate the agreement with only 2 days notice. The termination of the agreement should not be confused with VA's ability to physically remove the veteran from a dangerous situation, which can be done as soon as necessary in order to protect the health of the veteran. Proposed paragraph (e)(2) thus would assert VA's right to remove a veteran from a dangerous situation prior to terminating the applicable provider agreement.</P>
        <P>Proposed paragraph (f) would establish procedures for appeal of a Director's decision not to enter into a VA provider agreement or to terminate an agreement. A provider may appeal a decision issued by the Director by filing a written request for review with the Chief Consultant, Office of Geriatrics and Extended Care. An appeal must be filed in writing within 90 days after the date of the Director's decision. The Chief Consultant would provide written notice of the determination, which would constitute the final agency decision regarding eligibility for or termination of a VA provider agreement. The notice would explain why the decision is appropriate.</P>
        <P>Proposed paragraph (g) would state that providers need not comply with the Service Contract Act of 1965 (set forth at 41 U.S.C. 351, et seq.). This is the law referred to in the legislative history that requires contractors to report to the Department of Labor. While this Act applies to contracts entered into by the United States for services through the use of service employees, it does not apply to Medicare providers because they do not enter into contracts with the United States—Medicare provider agreements with CMS are used instead of contracts. However, proposed paragraph (g) would require that providers comply with all other applicable Federal laws concerning employment and hiring practices including the Fair Labor Standards Act, National Labor Relations Act, the Civil Rights Acts, the Age Discrimination in Employment Act of 1967, the Vocational Rehabilitation Act of 1973, Worker Adjustment and Retraining Notification Act, Sarbanes-Oxley Act of 2002, Occupational Health and Safety Act of 1970, Immigration Reform and Control Act of 1986, Consolidated Omnibus Reconciliation Act, the Family and Medical Leave Act, the Americans with Disabilities Act, the Uniformed Services Employment and Reemployment Rights Act, the Immigration and Nationality Act, the Consumer Credit Protection Act, the Employee Polygraph Protection Act, and the Employee Retirement Income Security Act. This is consistent with the legislative history set forth above.</P>
        <P>We would rescind all conflicting internal VA guidance that could be interpreted as providing an alternate benefit pertaining to extended care services. Specifically, we would rescind Veterans Health Administration (VHA) Handbooks 1143.2, “VHA Community Nursing Home Oversight Procedures”; 1140.6, “Purchased Home Health Care Services Procedures”; and 1140.5, “Community Hospice Care: Referral and Purchase Procedures”; and VHA Manual M-5 Part III, Chapter 6, pertaining to Community Residential Care. This policy guidance would be reissued in connection with the final rule.</P>
        <HD SOURCE="HD1">Executive Orders 12866 and 13563</HD>
        <P>Executive Orders 12866 and 13563 direct agencies to assess the costs and benefits of available regulatory alternatives and, when regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, and other advantages; distributive impacts; and equity). Executive Order 13563 (Improving Regulation and Regulatory Review) emphasizes the importance of quantifying both costs and benefits, reducing costs, harmonizing rules, and promoting flexibility. Executive Order 12866 (Regulatory Planning and Review) defines a “significant regulatory action,” which requires review by the Office of Management and Budget (OMB), as “any regulatory action that is likely to result in a rule that may: (1) Have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy, a sector of the economy, productivity, competition, jobs, the environment, public health or safety, or State, local, or tribal governments or communities; (2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another agency; (3) Materially alter the budgetary impact of entitlements, grants, user fees, or loan programs or the rights and obligations of recipients thereof; or (4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in this Executive Order.”</P>
        <P>The economic, interagency, budgetary, legal, and policy implications of this regulatory action have been examined and it has been determined to be a significant regulatory action under the Executive Order.</P>
        <HD SOURCE="HD1">Comment Period</HD>

        <P>Although under the rulemaking guidelines in Executive Order 12866, VA ordinarily provides a 60-day comment period, the Secretary has determined that there is good cause to limit the public comment period on this proposed rule to 30 days. VA does not expect to receive a large number of comments on this proposed rule, particularly comments that are negative or that oppose this rule, because it would increase the opportunity for veterans to obtain non-VA extended care services from local providers that furnish vital and often life-sustaining medical services. Accordingly, VA has provided that comments must be received within 30 days of publication in the<E T="04">Federal Register</E>.</P>
        <HD SOURCE="HD1">Paperwork Reduction Act</HD>
        <P>The proposed rule does not contain any collections of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3521).</P>
        <HD SOURCE="HD1">Regulatory Flexibility Act</HD>

        <P>The Secretary hereby certifies that the provisions of this proposed rule would not have a significant economic impact on a substantial number of small entities as they are defined in the Regulatory Flexibility Act, 5 U.S.C. 601-612. The proposed rule would not have a significant economic impact on any small entities because such entities would obtain only an insignificant<PRTPAGE P="10121"/>portion of their business from VA. Therefore, pursuant to 5 U.S.C. 605(b), this rulemaking is exempt from the initial and final regulatory flexibility analysis requirements of sections 603 and 604.</P>
        <HD SOURCE="HD1">Unfunded Mandates</HD>
        <P>The Unfunded Mandates Reform Act requires, at 2 U.S.C. 1532, that agencies prepare an assessment of anticipated costs and benefits before issuing any rule that may result in an expenditure by State, local, and tribal governments, in the aggregate, or by the private sector, of $100 million or more (adjusted annually for inflation) in any one year. This proposed rule would have no such effect on State, local, and tribal governments, or on the private sector.</P>
        <HD SOURCE="HD1">Catalog of Federal Domestic Assistance</HD>
        <P>The Catalog of Federal Domestic Assistance program numbers and titles affected by this rulemaking are 64.007, Blind Rehabilitation Centers; 64.009, Veterans Medical Care Benefits; 64.010, Veterans Nursing Home Care; 64.011, Veterans Dental Care; 64.013, Veterans Prosthetic Appliances; 64.018, Sharing Specialized Medical Resources; 64.019, Veterans Rehabilitation Alcohol and Drug Dependence; and 64.022, Veterans Home Based Primary Care.</P>
        <HD SOURCE="HD1">Signing Authority</HD>
        <P>The Secretary of Veterans Affairs, or designee, approved this document and authorized the undersigned to sign and submit the document to the Office of the Federal Register for publication electronically as an official document of the Department of Veterans Affairs. John R. Gingrich, Chief of Staff, Department of Veterans Affairs, approved this document on February 5, 2013, for publication.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 38 CFR Part 17</HD>
          <P>Administrative practice and procedure, Alcohol abuse, Alcoholism, Claims, Day care, Dental health, Drug abuse, Foreign relations, Government contracts, Grant programs-health, Grant programs-veterans, Health care, Health facilities, Health professions, Health records, Homeless, Medical and dental schools, Medical devices, Medical research, Mental health programs, Nursing homes, Philippines, Reporting and record-keeping requirements, Scholarships and fellowships, Travel and transportation expenses, Veterans.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: February 6, 2013.</DATED>
          <NAME>Robert C. McFetridge,</NAME>
          <TITLE>Director of Regulation Policy and Management, Office of the General Counsel, Department of Veterans Affairs.</TITLE>
        </SIG>
        
        <P>For the reasons set forth in the preamble, VA proposes to amend 38 CFR Part 17 as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 17—MEDICAL</HD>
        </PART>
        <AMDPAR>1. The authority citation for part 17 continues to read as follows:</AMDPAR>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>38 U.S.C. 501, and as noted in specific sections.</P>
        </AUTH>
        
        <AMDPAR>2. Add an undesignated center heading and § 17.75 immediately after § 17.74 to read as follows:</AMDPAR>
        <HD SOURCE="HD1">Agreements for Extended Care Services</HD>
        <SECTION>
          <SECTNO>§ 17.75</SECTNO>
          <SUBJECT>Agreements for extended care services.</SUBJECT>
          <P>(a)<E T="03">Definitions.</E>For purposes of this section:</P>
          <P>
            <E T="03">Extended care services</E>means geriatric evaluation; nursing home care; domiciliary services; adult day health care; noninstitutional palliative care, noninstitutional hospice care, and home health care when they are noninstitutional alternatives to nursing home care; and respite care.</P>
          <P>
            <E T="03">Provider</E>means any non-VA entity that provides extended care services and is participating in Medicare or a State plan under title XIX of the Social Security Act pursuant to a valid provider agreement.</P>
          <P>(b)<E T="03">Eligible providers from whom VA may obtain extended care services.</E>Subject to paragraph (d) of this section, VA may obtain extended care services from providers under this section only if:</P>
          <P>(1) The provider has entered into a Medicare provider agreement under 42 U.S.C. 1395cc(a) with the Centers for Medicare &amp; Medicaid Services (“CMS agreement”); or</P>
          <P>(2) If the provider has not entered into a Medicare provider agreement, but the provider is participating in an agreement under a State plan under title XIX of the Social Security Act (42 U.S.C. 1396 et seq.).</P>
          <P>(c)<E T="03">Terms of agreements.</E>(1) The Director of the VA medical center of jurisdiction, or designee, will send to a provider written notification that identifies the Medicare provider agreement or agreement under a State Medicaid plan that VA proposes to use as the basis for its agreement to obtain extended care services, identifies the changes and any additional terms that would apply to the provider agreement, and requests written acceptance from the provider of that agreement. VA will not obtain extended care services from the provider through a provider agreement until such acceptance is received.</P>
          <P>(2) Provider agreements with VA under this section must reflect the following:</P>
          <P>(i) For a provider with a valid Medicare provider agreement, the terms of the provider's agreement with VA, including the payment rates, will be the same as the terms of the provider's agreement with CMS pursuant to the Medicare Enrollment Application for Institutional Providers (OMB No. 0938-0685).</P>
          <P>(ii) For providers with no Medicare provider agreement but one or more agreements under a State plan, the terms of the provider's agreement with VA, including the payment rates, will be the same as the terms of the provider's agreement with the State that pays the highest rates.</P>
          <P>(iii) For providers with both a Medicare provider agreement and an agreement under a State Medicaid plan, the terms of the provider's agreement with VA, including the payment rates, will be the same as the CMS or State agreement that provides for the higher rates.</P>
          <P>(iv) The provider shall not charge any individual, insurer, or entity (other than VA) for the items or services obtained by VA under this section.</P>
          <P>(3) The terms of the provider's agreement with VA will be different from the provider's separate agreement with CMS or a State only to the extent that the non-VA agreement prescribes terms or procedures inconsistent with this section and that it is necessary to identify VA as the Government agency entering into the agreement with the provider and paying for the provider's services for veterans.</P>
          <P>(d)<E T="03">Decisions regarding agreements.</E>(1) The Director of the VA medical center of jurisdiction, or designee, will decide, based upon medical judgment regarding the health care needs of veterans in the community and the availability and feasibility of VA or local resources to efficiently provide for those needs, whether it is necessary to enter into provider agreements for extended care services.</P>
          <P>(2) If there is more than one provider in a given region, the veteran will select his or her preferred provider, subject to:</P>
          <P>(i) The provider's determination to accept the veteran;</P>
          <P>(ii) The availability and feasibility of resources at the VA medical center of jurisdiction; and</P>

          <P>(iii) The determination of the Director of the VA medical center of jurisdiction, or designee, that the services offered by<PRTPAGE P="10122"/>the provider would be clinically appropriate for the care of the veteran.</P>
          <P>(3) Factual determination of whether a provider has a Medicare provider agreement or an agreement under a State Medicaid plan will be based on verification of an existing agreement. Medicare provider agreements will be verified using CMS Web sites, which list providers with agreements. State agreements will be verified using appropriate State Web sites, which list providers with agreements, or using records maintained by the appropriate State office.</P>
          <P>(e)<E T="03">Termination of agreements.</E>(1) A provider that wishes to terminate its agreement with VA must send written notice of its intent at least 15 days before the effective date of termination of the agreement. The notice shall include the intended date of termination.</P>
          <P>(2) VA may terminate an agreement with any provider if the Director of the VA medical center of jurisdiction, or designee, determines that the provider's service is no longer required or that the provider is not complying with a provision of the provider agreement, and must terminate an agreement with a provider that no longer has a Medicare provider agreement with CMS or no longer participates under a State Medicaid plan. VA will provide written notice of termination at least 15 days before the effective date of termination of the provider agreement. If the Director of the VA medical center of jurisdiction, or designee, determines the health of the veteran to be in immediate jeopardy, VA will provide notice of termination at least 2 days before the effective date of termination of the provider agreement. VA may physically remove a veteran from a dangerous situation at any time in order to protect the health of the veteran prior to terminating the applicable provider agreement.</P>
          <P>(f)<E T="03">Appeals.</E>Appeals of a determination by the Director of the VA medical center of jurisdiction, or designee, not to enter into or to terminate a VA provider agreement must be made in writing to the Chief Consultant, Office of Geriatrics and Extended Care, no later than 90 days after the date of the decision being appealed. The decision of the Chief Consultant will constitute a final agency decision.</P>
          <P>(g)<E T="03">Compliance with Federal laws.</E>Under agreements entered into under this section, providers are not required to comply with reporting and auditing requirements imposed under the Service Contract Act of 1965, as amended (41 U.S.C. 351, et seq.); however, providers must comply with all other applicable Federal laws concerning employment and hiring practices including the Fair Labor Standards Act, National Labor Relations Act, the Civil Rights Acts, the Age Discrimination in Employment Act of 1967, the Vocational Rehabilitation Act of 1973, Worker Adjustment and Retraining Notification Act, Sarbanes-Oxley Act of 2002, Occupational Health and Safety Act of 1970, Immigration Reform and Control Act of 1986, Consolidated Omnibus Reconciliation Act, the Family and Medical Leave Act, the Americans with Disabilities Act, the Uniformed Services Employment and Reemployment Rights Act, the Immigration and Nationality Act, the Consumer Credit Protection Act, the Employee Polygraph Protection Act, and the Employee Retirement Income Security Act.</P>
          <SECAUTH>(Authority: 38 U.S.C. 501, 1720; 42 U.S.C. 1395cc)</SECAUTH>
          
        </SECTION>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-02993 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 8320-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <CFR>50 CFR Part 622</CFR>
        <DEPDOC>[Docket No. 130207066-3066-01]</DEPDOC>
        <RIN>RIN 0648-BC66</RIN>
        <SUBJECT>Fisheries of the Caribbean, Gulf of Mexico, and South Atlantic; Reef Fish Fishery of the Gulf of Mexico; Amendment 37</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed rule; request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>NMFS proposes to implement management measures described in Amendment 37 to the Fishery Management Plan for the Reef Fish Resources of the Gulf of Mexico (FMP) prepared by the Gulf of Mexico Fishery Management Council (Council). If implemented, this rule would revise the commercial and recreational sector's annual catch limits (ACLs) and annual catch targets (ACTs) for gray triggerfish; revise the recreational sector accountability measures (AMs) for gray triggerfish; revise the gray triggerfish recreational bag limit; establish a commercial trip limit for gray triggerfish; and establish a fixed closed season for the gray triggerfish commercial and recreational sectors. Additionally, Amendment 37 would modify the gray triggerfish rebuilding plan. The intent of this rule is to end overfishing of gray triggerfish and help achieve optimum yield (OY) for the gray triggerfish resource in accordance with the requirements of the Magnuson-Stevens Fishery Conservation and Management Act (Magnuson-Stevens Act).</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Written comments must be received on or before March 15, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments on this document, identified by “NOAA-NMFS-2012-0199”, by any of the following methods:</P>
          <P>•<E T="03">Electronic Submission:</E>Submit all electronic public comments via the Federal e-Rulemaking Portal. Go to<E T="03">www.regulations.gov/#!docketDetail;D=NOAA-NMFS-2012-0199,</E>click the “Comment Now!” icon, complete the required fields, and enter or attach your comments.</P>
          <P>•<E T="03">Mail:</E>Submit written comments to Rich Malinowski, Southeast Regional Office, NMFS, 263 13th Avenue South, St. Petersburg, FL 33701.</P>
          <P>
            <E T="03">Instructions:</E>Comments sent by any other method, to any other address or individual, or received after the end of the comment period, may not be considered by NMFS. All comments received are a part of the public record and will generally be posted for public viewing on<E T="03">www.regulations.gov</E>without change. All personal identifying information (<E T="03">e.g.,</E>name, address, etc.), confidential business information, or otherwise sensitive information submitted voluntarily by the sender will be publicly accessible. NMFS will accept anonymous comments (enter “N/A” in the required fields if you wish to remain anonymous). Attachments to electronic comments will be accepted in Microsoft Word, Excel, or Adobe PDF file formats only.</P>

          <P>Electronic copies of Amendment 37, which includes a draft environmental assessment and a regulatory impact review, may be obtained from the Southeast Regional Office Web site at<E T="03">http://sero.nmfs.noaa.gov.</E>
          </P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Rich Malinowski, Southeast Regional Office, telephone 727-824-5305, email<E T="03">rich.malinowski@noaa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>The reef fish fishery of the Gulf is managed under the FMP. The FMP was prepared by the Council and is implemented through regulations at 50 CFR part 622 under the authority of the Magnuson-Stevens Act. All gray triggerfish weights discussed in this proposed rule are in round weight.<PRTPAGE P="10123"/>
        </P>
        <HD SOURCE="HD1">Background</HD>
        <P>The Magnuson-Stevens Act requires NMFS and regional fishery management councils to prevent overfishing and achieve, on a continuing basis, the OY from federally managed fish stocks. These mandates are intended to ensure that fishery resources are managed for the greatest overall benefit to the nation, particularly with respect to providing food production and recreational opportunities, and protecting marine ecosystems. To further this goal, the Magnuson-Stevens Act requires fishery managers to end overfishing of stocks and to minimize bycatch and bycatch mortality to the extent practicable.</P>
        <HD SOURCE="HD2">Status of the Gray Triggerfish Stock</HD>
        <P>The last Southeast Data, Assessment, and Review (SEDAR) benchmark stock assessment for gray triggerfish was completed in 2006 (SEDAR 9). SEDAR 9 indicated that the gray triggerfish stock was both overfished and possibly undergoing overfishing. Subsequently, Amendment 30A to the FMP established a gray triggerfish rebuilding plan beginning in the 2008 fishing year (73 FR 38139, July 3, 2008). In 2011, a SEDAR 9 update stock assessment for gray triggerfish determined that the gray triggerfish stock was still overfished and was additionally undergoing overfishing. The 2011 SEDAR 9 Update indicated the 2008 gray triggerfish rebuilding plan had not made adequate progress toward ending overfishing and rebuilding the stock. NMFS informed the Council of this determination in a letter dated March 13, 2012. NMFS also requested that the Council work to end overfishing of gray triggerfish immediately and to revise the gray triggerfish stock rebuilding plan.</P>
        <P>As a way to more quickly implement measures to end overfishing and rebuild the stock, the Council requested and NMFS implemented a temporary rule to reduce the gray triggerfish commercial and recreational ACLs and ACTs (77 FR 28308, May 14, 2012). The temporary rule also established an in-season AM for the gray triggerfish recreational sector to be more consistent with the commercial sector AMs and provide for an additional level of protection to ensure that the recreational ACL is not exceeded and that the risk of overfishing is reduced. These interim measures were then extended through May 15, 2013, to ensure that the more permanent measures being developed through Amendment 37 could be implemented without a lapse in these more protective management measures (77 FR 67303, November 9, 2012).</P>
        <HD SOURCE="HD3">Management Measures Contained in This Proposed Rule</HD>
        <P>This proposed rule would revise the gray triggerfish commercial and recreational sector ACLs and ACTs (commercial ACT expressed as commercial quota in the regulatory text), revise the gray triggerfish recreational sector AMs, revise the gray triggerfish recreational bag limit, establish a commercial trip limit for gray triggerfish, and establish a fixed closed season for the gray triggerfish commercial and recreational sectors.</P>
        <HD SOURCE="HD2">ACLs and ACTs</HD>
        <P>This rule would revise the ACLs for the gray triggerfish commercial and recreational sectors. This rule would also revise the ACTs (commercial ACT expressed as a quota in the regulatory text) for both sectors.</P>
        <P>The Council's Scientific and Statistical Committee (SSC) reviewed the gray triggerfish 2011 SEDAR 9 Update. The SSC recommended that the gray triggerfish acceptable biological catches (ABC) for the 2012 and 2013 fishing years be set at 305,300 lb (138,346 kg). The current gray triggerfish stock ABC is 595,000 lb (269,887 kg). Based on this recommendation, the commercial and recreational ACLs and ACTs for the gray triggerfish need to be updated.</P>
        <P>The Magnuson-Stevens Act requires that the FMP contain a mechanism for specifying ACLs at a level such that overfishing does not occur. An ACT is a management target established to account for management uncertainty in controlling the actual catch at or below the ACL. An ACT is used in the system of AMs so that the ACL is not exceeded. Therefore, a sector ACT should be set below the sector ACL to allow the sector to be closed when the ACT is projected to be reached.</P>
        <P>In Amendment 30A to the FMP, the Council established a 21 percent commercial and 79 percent recreational allocation of the gray triggerfish ABC (73 FR 38139, July 3, 2008). These allocations are used to set the commercial and recreational sector-specific ACLs. The ABC recommended by the SSC is 305,300 lb (138,482 kg) and the combined sector ACLs are equal to the ABC. Based on the allocations established in Amendment 30A to the FMP, this proposed rule would set a reduced commercial ACL of 64,100 lb (29,075 kg), and a reduced recreational ACL of 241,200 lb (109,406 kg).</P>
        <P>The Generic Annual Catch Limit Amendment developed by the Council and implemented by NMFS (76 FR 82044, December 29, 2011) established a standardized procedure to set sector-specific ACTs based on the ACLs. ACTs are intended to account for management uncertainty and provide a buffer that better ensures a sector does not exceed its designated ACL. The Council chose to use this procedure, which resulted in a 5 percent buffer between the commercial ACL and ACT, and a 10 percent buffer between the recreational ACL and ACT. Therefore, this proposed rule would set the commercial ACT (commercial quota) at 60,900 lb (27,624 kg), and the recreational ACT at 217,100 lb (98,475 kg). The proposed ACLs and ACTs in this rule are the same as those currently in place as implemented through the temporary rule (77 FR 28308, May 14, 2012). The current commercial gray triggerfish quota functions as the commercial ACT.</P>
        <HD SOURCE="HD2">AMs</HD>
        <P>To reduce the risk of overfishing, Amendment 30A to the FMP established gray triggerfish AMs. AMs are management controls that are implemented to prevent ACLs from being exceeded (in-season AMs), and to correct or mitigate overages of the ACL if they occur (post-season AMs). For the commercial sector, there are currently both in-season and post-season AMs. The in-season AM closes the commercial sector after the commercial quota (commercial ACT) is reached or projected to be reached. Additionally, if the commercial ACL is exceeded despite the quota closure, the post-season AM would reduce the following year's commercial quota (commercial ACT) by the amount of the prior-year's commercial ACL overage.</P>
        <P>For the recreational sector, there is currently no in-season AM, but a post-season AM is in effect. For the recreational sector, if the recreational ACL is exceeded, NMFS will reduce the length of the following year's fishing season by the amount necessary to ensure that recreational landings do not exceed the recreational ACT during the following year.</P>

        <P>In 2008, recreational landings exceeded both the recreational ACT and ACL. In 2009, the recreational ACT was exceeded. However, in 2010, recreational landings did not exceed the ACT or ACL. Reduced 2010 recreational landings may be attributable to fishery closures implemented that year as a result of the Deepwater Horizon MC252 oil spill. Based on recent trends in recreational landings and anticipated future recreational effort, the Council and NMFS have determined that implementing an in-season AM would reduce the risk of exceeding the ACL in the future. This proposed rule would<PRTPAGE P="10124"/>replace the current post-season AM with an in-season AM for the recreational sector to prohibit the recreational harvest of gray triggerfish (a recreational sector closure) after the recreational ACT is reached or projected to be reached. This proposed rule would also add an overage adjustment that would apply if the recreational sector ACL is exceeded and gray triggerfish are overfished. This post-season AM would reduce the recreational ACL and ACT for the following year by the amount of the ACL overage in the prior fishing year, unless the best scientific information available determines that a greater, lesser, or no overage adjustment is necessary.</P>
        <HD SOURCE="HD2">Commercial Trip Limit</HD>
        <P>Currently, there is no trip limit for the commercial sector. This rule proposes to establish a commercial trip limit for gray triggerfish of 12 fish. This commercial trip limit would be applicable until the commercial ACT (commercial quota) is reached or projected to be reached during a fishing year and the commercial sector is closed.</P>
        <HD SOURCE="HD2">Seasonal Closure of the Commercial and Recreational Sectors</HD>
        <P>This proposed rule would establish a seasonal closure of the gray triggerfish commercial and recreational sectors in the Gulf from June through July, each year. This fixed seasonal closure would assist rebuilding of the gray triggerfish stock by prohibiting harvest during the gray triggerfish peak spawning season. Additionally, June and July are the months that have the highest percentage of recreational landings.</P>
        <HD SOURCE="HD2">Recreational Bag Limit</HD>
        <P>Gray triggerfish currently have a recreational bag limit that is part of the 20-fish aggregate reef fish bag limit. As part of this 20-fish aggregate, there is currently no specific limit for recreational gray triggerfish landings as long as the total is 20 fish or less. This proposed rule would establish a 2-fish gray triggerfish recreational bag limit within the 20-fish aggregate reef fish bag limit. This recreational bag limit would be applicable until the recreational ACT is reached or projected to be reached during a fishing year and the recreational sector is closed.</P>
        <HD SOURCE="HD1">Other Action Contained in Amendment 37</HD>
        <P>Amendment 37 would revise the rebuilding plan for gray triggerfish. The gray triggerfish stock is currently in the 5th year of a rebuilding plan that began in 2008. Amendment 37 would modify the rebuilding plan in response to the results from the 2011 SEDAR update assessment and subsequent SSC review and recommendations for the gray triggerfish ABC. The modified rebuilding plan would be based on a constant fishing mortality rate that does not exceed the fishing mortality rate at OY.</P>
        <HD SOURCE="HD1">Classification</HD>
        <P>Pursuant to section 304(b)(1)(A) of the Magnuson-Stevens Act, the Assistant Administrator, NMFS, has determined that this proposed rule is consistent with the FMP, Amendment 37, the Magnuson-Stevens Act and other applicable law, subject to further consideration after public comment.</P>
        <P>This proposed rule has been determined to be not significant for purposes of Executive Order 12866.</P>
        <P>The Chief Counsel for Regulation of the Department of Commerce certified to the Chief Counsel for Advocacy of the Small Business Administration that this proposed rule, if implemented, would not have a significant economic impact on a substantial number of small entities. The factual basis for this determination is as follows:</P>
        <P>The purpose of this proposed rule is to end overfishing of gray triggerfish and rebuild the gray triggerfish stock by the end of 2017 to achieve OY. The Magnuson-Stevens Act provides the statutory basis for this proposed rule. No duplicative, overlapping, or conflicting Federal rules have been identified. This proposed rule would not introduce any changes to current reporting, record-keeping, and other compliance requirements.</P>

        <P>This rule, if implemented, is expected to directly affect approximately 400 vessels that have a valid (non-expired) or renewable commercial Gulf reef fish permit. A renewable permit is an expired permit that may not be actively fished, but is renewable for up to 1 year after permit expiration. Although over 900 vessels have a commercial Gulf reef fish permit, which is required to possess and sell quantities of gray triggerfish in excess of the recreational bag limit, only an average of 382 vessels per year harvested gray triggerfish during the period 2005 through 2009. More recent commercial landings data is either not available (2011 to current) or is not expected to be representative of normal fishing performance,<E T="03">i.e.,</E>the 2010 fishing year as a result of the Deepwater Horizon MC252 oil spill and associated fisheries closures. The average annual dockside revenue for commercial vessels that harvested gray triggerfish during this period was approximately $87,000 per vessel (2010 dollars).</P>
        <P>This rule, if implemented, is also be expected to directly affect 1,366 vessels that possess a valid or renewable charter/headboat permit for Gulf reef fish (for-hire). The for-hire fleet is comprised of charterboats, which charge a fee on a vessel basis, and headboats, which charge a fee on an individual angler (head) basis. Although the for-hire permit does not distinguish between charterboats and headboats, an estimated 69 headboats operate in the Gulf. The average charterboat is estimated to earn approximately $77,000 (2010 dollars) in annual revenue, and the average headboat is estimated to earn approximately $234,000 (2010 dollars).</P>
        <P>NMFS has not identified any other small entities that would be expected to be directly affected by this proposed rule.</P>
        <P>The Small Business Administration has established size criteria for all major industry sectors in the U.S. including fish harvesters. A business involved in fish harvesting is classified as a small business if it is independently owned and operated, is not dominant in its field of operation (including its affiliates), and has combined annual receipts not in excess of $4.0 million (NAICS code 114111, finfish fishing) for all its affiliated operations worldwide. The revenue threshold for a business involved in the for-hire fishing industry is $7.0 million (NAICS code 713990, recreational industries). All commercial and for-hire vessels expected to be directly affected by this proposed rule are believed to be small business entities.</P>
        <P>Amendment 37, on which this proposed rule is based, addresses five basic actions: (1) Revision of the gray triggerfish rebuilding plan; (2) specification of the commercial and recreational gray triggerfish ACLs and ACTs; (3) establishment of a gray triggerfish commercial sector closed season and trip limit; (4) establishment of a gray triggerfish recreational closed season and bag limit; and (5) revision of the AMs for the gray triggerfish recreational sector.</P>

        <P>Rebuilding plans are not contained in the regulatory text associated with this proposed rule and are therefore outside the scope of the Regulatory Flexibility Act (RFA). Further, revision of the rebuilding plan would be an administrative action and, as a result, would not be expected to have any direct economic effects on any small entities. Direct effects of a rebuilding plan would only be expected to accrue to any resultant harvest restrictions implemented through a future rulemaking to achieve the goals of the<PRTPAGE P="10125"/>rebuilding plan. The proposed harvest restrictions encompass modification of the sector ACTs, fishing seasons, commercial trip limits, and recreational bag limits. The expected economic effects of these proposed modifications are discussed below.</P>
        <P>AMs are intended to ensure harvest overages do not occur and to correct or mitigate for overages if they do occur. In-season AMs are specifically intended to prevent or minimize harvest overages. The establishment of AMs, or their modification, would be an administrative action that would only be expected to have indirect effects on small entities. These effects would occur if the AMs are triggered. Because the proposed action would only modify and not implement the current AMs, no direct effects would be expected to accrue to any small entities. As a result, this component of the proposed rule is also outside the scope of the RFA.</P>
        <P>However, because the potential implementation of the proposed in-season AM would be expected to restrict fishing operations and potentially result in direct short-term reductions in revenue and profit, further discussion of the potential significance of these effects is provided. The proposed in-season gray triggerfish recreational sector AM would result in closure of the gray triggerfish recreational season if the recreational sector ACT is reached or is projected to be reached. As a result, harvest and possession would be prohibited. Few, if any, fishing trips would be expected to be cancelled in response to a prohibition on the harvest and possession of gray triggerfish because anglers rarely target gray triggerfish: It was identified as a primary target species for less than 1/10th of 1 percent of all fishing trips (2005-2009). Rather, gray triggerfish are often harvested incidental to fishing for other reef fish species. Because other, more desirable reef species would still be available for recreational harvest, any prohibition on the harvest or possession of gray triggerfish would not be expected to have a significant impact on a substantial number of small entities.</P>
        <P>Because gray triggerfish is not a significantly targeted species, the proposed overage adjustment if the recreational ACL is exceeded would also be expected to result in minimal, if any, reduction in revenue to small entities. Because of the combination of in-season closure authority, low total harvest and target effort, and the expected recovery of gray triggerfish, overage adjustments would be expected to be infrequent and, if necessary, require only minimal reductions in the recreational ACT. Therefore, few, if any, recreational trips would be expected to be lost and the revenue to small entities would not be expected to be significantly affected.</P>
        <P>Although Amendment 37 contained three proposed actions associated with the commercial harvest of gray triggerfish—specification of the ACT, establishment of the closed season, and establishment of a commercial trip limit—the expected economic effects of this rule would be determined primarily by the specification of the ACT. Individually, assuming no change in fishing behavior, the proposed commercial sector closed season and trip limit would be expected to result in a reduction in total annual revenue for all vessels that harvest gray triggerfish of approximately $26,000 and $72,000, respectively. All reductions are expressed in 2010 dollars. Combined, these two measures would be expected to result in a reduction in total annual revenue of approximately $88,000. This result is less than the total of the two individual proposed actions, approximately $98,000, because the proposed closed season would negate the expected effects of the trip limit during that period. However, the combined effects of these two proposed actions would not be expected to be sufficient to constrain commercial gray triggerfish harvest to the ACT and avoid an in-season closure. The proposed ACT, 60,900 lb (27,624 kg), would be expected to require a reduction in expected annual commercial harvest of approximately 118,000 lb (53,524 kg). The combined effects of the proposed commercial sector seasonal closure and trip limit would be a reduction in annual commercial harvest of approximately 92,000 lb (41,730 kg). Because commercial harvest would be prohibited when the commercial ACT is reached, the full necessary commercial sector harvest reduction would be expected to occur as a result of the three measures combined (seasonal closure, trip limit, and closure when the ACT is reached). Thus, although the total effect of the proposed seasonal closure and trip limit would be an expected reduction in annual revenue of approximately $88,000, the net effect of the proposed commercial ACT, seasonal closure, and trip limit would be a reduction in annual revenue of approximately $112,000. Distributed across all commercial sector entities expected to be directly affected by these proposed measures (382 vessels), the average expected effect would be a reduction in annual revenue of approximately $300 per entity, or less than one percent of the average annual revenue per vessel of $87,000. Although some vessels may be expected to experience a reduction in revenue by more than the average, overall, any reduction would not be expected to be significant because of the small amount of gray triggerfish traditionally harvested by commercial reef fish fishermen.</P>
        <P>Impacts on the recreational sector are expected to be similar to those affecting the commercial sector. The proposed gray triggerfish recreational ACT, seasonal closure, and recreational bag limit would be expected to individually result in an annual reduction in producer surplus, used as a proxy for profit, of approximately $295,000, $232,000, and $137,000, respectively. All reductions are expressed in 2010 dollars and equal the combined effects of the proposed actions across all affected entities. Combined, the proposed seasonal closure and bag limit would be expected to result in an annual reduction in producer surplus of approximately $310,000, which would be less than the effects of the two individual proposed actions combined because of the interactive effects of the two proposed measures. The combined effects of these two proposed measures exceeds the expected effects of the proposed recreational ACT because the estimated reduction in harvest under the proposed seasonal closure and bag limit exceeds the reduction necessary to limit harvest to the proposed gray triggerfish recreational ACT and avoid an in-season closure. Thus, for the proposed actions affecting the recreational sector, the net expected economic effect would be determined by the combined effects of the proposed seasonal closure and bag limit rather than the proposed ACT.</P>

        <P>Unlike the case for the commercial sector, the number of vessels within the for-hire fleet that take trips targeting gray triggerfish cannot be determined with available data. If the projected reduction in producer surplus is distributed across all Gulf reef fish for-hire vessels (1,366 vessels), the average annual reduction in producer surplus would be approximately $230 (2010 dollars) per vessel, or approximately 1 percent in average annual profit per vessel (approximately $22,800 (2010 dollars)). Because all vessels would not be expected to target gray triggerfish, however, the average reduction in producer surplus per affected vessel would be expected to increase. However, the estimates of expected reduction in producer surplus associated with the proposed actions affecting the recreational sector were generated using a worst-case<PRTPAGE P="10126"/>assumption. Specifically, the projected reductions in producer surplus were based on the assumption that recreational angler effort, and associated for-hire revenue, would be reduced proportionate to the change in allowable harvest. As previously discussed, gray triggerfish is regarded as a bycatch or general harvest species, harvested in connection with general reef fish fishing (no target species) or as a result of fishing for other reef fish species. As a result, instead of cancelling fishing trips, few if any for-hire vessels would be expected to experience a reduction in customer traffic, and associated revenue, as a result of either the proposed seasonal closure or reduced recreational bag limit. Instead, substitution of another target species during the proposed closed season and continued fishing at the proposed lower bag would be expected. As a result, the proposed actions affecting the recreational sector would not be expected to significantly reduce profits for a significant number of small for-hire entities.</P>
        <P>In summary, the proposed rule, if implemented, would not be expected to have a significant impact on a substantial number of small entities and, as a result, an initial regulatory flexibility analysis is not required and none has been prepared.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 50 CFR Part 622</HD>
          <P>Fisheries, Fishing, Puerto Rico, Reporting and recordkeeping requirements, Virgin Islands.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: February 8, 2013.</DATED>
          <NAME>Samuel D. Rauch III,</NAME>
          <TITLE>Deputy Assistant Administrator for Regulatory Programs, performing the functions and duties of the Assistant Administrator for Fisheries, National Marine Fisheries Service.</TITLE>
        </SIG>
        <P>For the reasons set out in the preamble, 50 CFR part 622 is proposed to be amended as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 622—FISHERIES OF THE CARIBBEAN, GULF, AND SOUTH ATLANTIC</HD>
        </PART>
        <AMDPAR>1. The authority citation for part 622 continues to read as follows:</AMDPAR>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>16 U.S.C. 1801<E T="03">et seq.</E>
          </P>
        </AUTH>
        
        <AMDPAR>2. In § 622.34, paragraph (w) is added to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 622.34</SECTNO>
          <SUBJECT>Gulf EEZ seasonal and/or area closures.</SUBJECT>
          <STARS/>
          <P>(w)<E T="03">Seasonal closure of the commercial and recreational sectors for gray triggerfish.</E>The commercial and recreational sectors for gray triggerfish in or from the Gulf EEZ are closed from June 1 through July 31, each year. During the closure, all harvest or possession in or from the Gulf EEZ of gray triggerfish is prohibited and the sale and purchase of gray triggerfish taken from the Gulf EEZ is prohibited.</P>
        </SECTION>
        <AMDPAR>3. In § 622.39, paragraph (b)(1)(v) is revised to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 622.39</SECTNO>
          <SUBJECT>Bag and possession limits.</SUBJECT>
          <STARS/>
          <P>(b) * * *</P>
          <P>(1) * * *</P>
          <P>(v) Gulf reef fish, combined, excluding those specified in paragraphs (b)(1)(i) through (b)(1)(iv) and paragraphs (b)(1)(vi) through (b)(1)(vii) of this section—20. In addition, within the 20-fish aggregate reef fish bag limit, no more than two fish may be gray triggerfish.</P>
          <STARS/>
        </SECTION>
        <AMDPAR>4. In § 622.42, paragraph (a)(1)(vi) is revised to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 622.42</SECTNO>
          <SUBJECT>Quotas.</SUBJECT>
          <STARS/>
          <P>(a) * * *</P>
          <P>(1) * * *</P>
          <P>(vi) Gray triggerfish—60,900 lb (27,624 kg), round weight.</P>
          <STARS/>
        </SECTION>
        <AMDPAR>5. In § 622.44, paragraph (g) is added to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 622.44</SECTNO>
          <SUBJECT>Commercial trip limits.</SUBJECT>
          <STARS/>
          <P>(g)<E T="03">Gulf gray triggerfish.</E>Until the commercial ACT (commercial quota) specified in § 622.42(a)(1)(vi) is reached—12 fish. See § 622.43(a)(1)(i)  for the limitations regarding gray triggerfish after the commercial ACT (commercial quota) is reached.</P>
          <STARS/>
        </SECTION>
        <AMDPAR>6. In § 622.49, paragraph (a)(2) is revised to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 622.49</SECTNO>
          <SUBJECT>Annual catch limits (ACLs), annual catch targets (ACTs), and accountability measures (AMs).</SUBJECT>
          <P>(a) * * *</P>
          <P>(2)<E T="03">Gray triggerfish</E>—(i)<E T="03">Commercial sector.</E>If commercial landings, as estimated by the SRD, reach or are projected to reach the commercial ACT (commercial quota) specified in§ 622.42(a)(1)(vi),  the AA will file a notification with the Office of the Federal Register to close the commercial sector for the remainder of the fishing year. In addition, if despite such closure, commercial landings exceed the commercial ACL, the AA will file a notification with the Office of the Federal Register, at or near the beginning of the following fishing year to reduce the commercial ACL and ACT (commercial quota) for that following year by the amount the prior-year ACL was exceeded. The commercial ACL is 64,100 lb (29,075 kg), round weight.</P>
          <P>(ii)<E T="03">Recreational sector.</E>(A) Without regard to overfished status, if gray triggerfish recreational landings, as estimated by the SRD, reach or are projected to reach the applicable ACT specified in paragraph (a)(2)(ii)(C) of this section, the AA will file a notification with the Office of the Federal Register, to close the recreational sector for the remainder of the fishing year. On and after the effective date of such a notification, the bag and possession limit of gray triggerfish in or from the Gulf EEZ is zero. This bag and possession limit applies in the Gulf on board a vessel for which a valid Federal charter vessel/headboat permit for Gulf reef fish has been issued, without regard to where such species were harvested,<E T="03">i.e.</E>in state or Federal waters.</P>
          <P>(B) In addition to the measures specified in paragraphs (a)(2)(ii)(A) of this section, if gray triggerfish recreational landings, as estimated by the SRD, exceed the applicable ACL specified in paragraph (a)(2)(ii)(C) of this section, and gray triggerfish are overfished, based on the most recent Status of U.S. Fisheries Report to Congress, the AA will file a notification with the Office of the Federal Register, at or near the beginning of the following fishing year to reduce the ACL and the ACT for that following year by the amount of the ACL overage in the prior fishing year, unless the best scientific information available determines that a greater, lesser, or no overage adjustment is necessary.</P>
          <P>(C) The recreational ACL for gray triggerfish is 241,200 lb (109,406 kg), round weight. The recreational ACT for gray triggerfish is 217,100 lb (98,475 kg), round weight. Recreational landings will be evaluated relative to the ACL based on a moving multi-year average of landings, as described in the FMP.</P>
          <STARS/>
        </SECTION>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03372 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </PRORULE>
  </PRORULES>
  <VOL>78</VOL>
  <NO>30</NO>
  <DATE>Wednesday, February 13, 2013</DATE>
  <UNITNAME>Notices</UNITNAME>
  <NOTICES>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="10127"/>
        <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Natural Resources Conservation Service</SUBAGY>
        <SUBJECT>Request for Nominations to the Agricultural Air Quality Task Force</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Natural Resources Conservation Service, United States Department of Agriculture.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of Request for Nominations to the Agricultural Air Quality Task Force.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Secretary of Agriculture invites nominations of qualified candidates to be considered for a 2-year term on the Agricultural Air Quality Task Force (AAQTF) which was established by the Federal Agriculture Improvement and Reform Act of 1996 to provide recommendations to the Secretary of Agriculture on agricultural air quality issues. This notice solicits nominations for membership on the AAQTF.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>This is effective February 13, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Nominations should be postmarked no later than April 1, 2013 to: Greg Johnson, Designated Federal Official, Department of Agriculture, Natural Resources Conservation Service, 1201 Lloyd Boulevard, Suite 1000, Portland, Oregon 97232, or by email at<E T="03">greg.johnson@por.usda.gov</E>.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Greg Johnson, Designated Federal Official, Department of Agriculture, Natural Resources Conservation Service, 1201 Lloyd Boulevard, Suite 1000, Portland, Oregon 97232; telephone: (503) 273-2424; fax: (503) 273-2401; email:<E T="03">greg.johnson@por.usda.gov</E>.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">AAQTF Purpose</HD>
        <P>Section 391 of the Federal Agriculture Improvement and Reform Act of 1996, Public Law 104-127, 7 U.S.C. 5405, requires the Chief of the Natural Resource Conservation Service (NRCS) to establish a task force to address air agricultural quality issues. The task force advises the Secretary of Agriculture on the role of the Secretary for providing oversight and coordination related to agricultural air quality. The requirements of the Federal Advisory Committee Act, 5 U.S.C. App.2., apply to this task force.</P>
        <P>The task force will:</P>
        <P>1. Strengthen vital research efforts related to agricultural air quality;</P>
        <P>2. Determine the extent to which agricultural activities contribute to air pollution;</P>
        <P>3. Determine cost-effective ways in which the agricultural industry can improve air quality;</P>
        <P>4. Coordinate and ensure intergovernmental cooperation on research activities related to agricultural air quality issues to avoid duplication and ensure data quality and sound interpretation of data; and</P>
        <P>5. Advise the Secretary of Agriculture on the role of the Secretary for providing oversight and coordination related to agricultural air quality.</P>
        <HD SOURCE="HD1">AAQTF Membership</HD>
        <P>The task force expects to meet 2-3 times each year, with meetings held at various locations across the United States. A task force member will serve for a term of 2 years, starting with the date of charter establishment for this task force. The Chief of NRCS serves as Chair of the task force. The task force is composed of United States citizens representing a broad spectrum of individuals with interest in agricultural air quality issues. This includes, but is not limited to, representatives from the agricultural production/processing sector, as well as those from academia, agribusiness, regulatory organizations, environmental organizations, and local or state agencies.</P>
        <P>Nominees to the AAQTF will be evaluated on a number of criteria, including expertise in or experience with agricultural air quality research, agricultural production, and air quality environmental or regulatory issues.</P>
        <P>Serving as a task force member will not constitute employment by, or the holding of, an office of the United States for the purpose of any Federal law. Persons selected for membership on the task force will not receive compensation from NRCS for their service as task force members except that while away from home or regular place of business, the member will be eligible for travel expenses paid by NRCS, including per diem in lieu of subsistence, at the same rate as a person employed intermittently in the government service, under section 5703 of Title 5, U.S.C.</P>

        <P>Additional information about the AAQTF may be found on the World Wide Web at<E T="03">http://www.airquality.nrcs.usda.gov/wps/portal/nrcs/detail/national/air/taskforce/</E>.</P>
        <HD SOURCE="HD1">Member Nominations</HD>
        <P>Any interested person or organization may nominate qualified individuals for membership. Interested candidates may nominate themselves. Previous nominees and task force members who wish to be considered for membership on the task force must submit a new nomination with updated information, including a new background disclosure form (Form AD-755).</P>
        <P>Nominations should be typed and include the following:</P>
        <P>1. A brief summary, of no more than two pages, explaining the nominee's qualifications to serve on the AAQTF and addressing the criteria described above;</P>
        <P>2. Resume, which provides the nominee's background, experience, and educational qualifications;</P>

        <P>3. A completed background disclosure form (Form AD-755) signed by the nominee (<E T="03">http://www.fsa.usda.gov/Internet/FSA_File/ad755.pdf</E>);</P>
        <P>4. Any recent publications by the nominee relative to air quality (if appropriate); and</P>
        <P>5. Up to two letters of endorsement (optional).</P>

        <P>Send written nominations to: Greg Johnson, Designated Federal Official, Department of Agriculture, Natural Resources Conservation Service, 1201 Lloyd Boulevard, Suite 1000, Portland, Oregon 97232; email to<E T="03">greg.johnson@por.usda.gov</E>. The Designated Federal Official will acknowledge receipt of nominations.</P>
        <HD SOURCE="HD1">Equal Opportunity Statement</HD>

        <P>To ensure that recommendations of the task force take into account the needs of underserved and diverse communities served by USDA, membership will include, to the extent practicable, individuals representing minorities, women, and persons with disabilities. USDA prohibits<PRTPAGE P="10128"/>discrimination in all of its programs and activities on the basis of race, sex, color, national origin, gender, religion, age, sexual orientation, or disability. Additionally, discrimination on the basis of political beliefs and marital status or family status is also prohibited by statutes enforced by USDA (not all prohibited bases apply to all programs). Persons with disabilities who require alternate means for communication of program information (Braille, large print, audio tape, etc.) should contact USDA's Target Center at (202) 720-2600 (voice and TDD). USDA is an equal opportunity provider and employer.</P>
        <SIG>
          <DATED>Signed this 31 day of January 2013, in Washington, DC.</DATED>
          <NAME>Jason A. Weller,</NAME>
          <TITLE>Acting Chief, Natural Resources Conservation Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03247 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-16-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Rural Utilities Service</SUBAGY>
        <SUBJECT>Information Collection Activity; Comment Request</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Rural Utilities Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice and request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35, as amended), the United States Department of Agriculture (USDA) Rural Development administers rural utilities programs through the Rural Utilities Service (RUS). The USDA Rural Development invites comments on the following information collections for which the Agency intends to request approval from the Office of Management and Budget (OMB).</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments on this notice must be received by April 15, 2013.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Michele Brooks, Director, Program Development and Regulatory Analysis, USDA Rural Development, 1400 Independence Ave. SW., STOP 1522, Room 5162, South Building, Washington, DC 20250-1522. Telephone: (202) 690-1078. FAX: (202) 720-8435. EMAIL:<E T="03">Michele.Brooks@wdc.usda.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The Office of Management and Budget's (OMB) regulation (5 CFR part 1320) implementing provisions of the Paperwork Reduction Act of 1995 (Pub. L. 104-13) requires that interested members of the public and affected agencies have an opportunity to comment on information collection and recordkeeping activities [see 5 CFR 1320.8(d)]. This notice identifies information collections that RUS is submitting to OMB for extension.</P>
        <P>
          <E T="03">Comments are invited on:</E>(a) Whether this collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; (b) the accuracy of the agency's estimate of the burden of the proposed collection of information including the validity of the methodology and assumptions used; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents, including through the use of appropriate automated, electronic, mechanical or other technological collection techniques or other forms of information technology. Comments may be sent to: Michele Brooks, Director, Program Development and Regulatory Analysis, USDA Rural Development, Stop 1522, 1400 Independence Ave. SW., Washington, DC 20250-1522. FAX: (202) 720-8435. EMAIL:<E T="03">Michele.Brooks@wdc.usda.gov.</E>
        </P>
        <P>
          <E T="03">Title:</E>Emergency and Imminent Community Water Assistance Grants.</P>
        <P>
          <E T="03">OMB Control Number:</E>0572-0110.</P>
        <P>
          <E T="03">Type of Request:</E>Extension of an existing information collection package.</P>
        <P>
          <E T="03">Abstract:</E>Rural Utilities Service (RUS), an agency delivering the U.S. Department of Agriculture (USDA) Rural Development Programs, is a funding agency. Grants under this RUS program may be made to public bodies and private nonprofit corporations serving rural areas. Public bodies include counties, cities, townships, incorporated towns and villages, boroughs, authorities, districts, and other political subdivisions of a state. Public bodies also include Indian Tribes on Federal and State reservations and other Federally-recognized Indian tribal groups in rural areas. Applicants will provide information to be collected as part of the application and grant process through certain documentation, certifications, or completed forms. These procedures are codified at 7 CFR part 1778.</P>
        <P>
          <E T="03">Estimate of Burden:</E>Public reporting for this collection of information is estimated to average 4 hours per response.</P>
        <P>
          <E T="03">Respondents:</E>Not-for-profit Institutions.</P>
        <P>
          <E T="03">Estimated Number of Respondents:</E>100.</P>
        <P>
          <E T="03">Estimated Number of Responses per Respondent:</E>1.</P>
        <P>
          <E T="03">Estimated Total Annual Burden on Respondents:</E>4 hours.</P>

        <P>Copies of this information collection can be obtained from Anne Mayberry, Program Development and Regulatory Analysis, at (202) 690-1756, FAX (202) 720-8345 or email:<E T="03">anne.mayberry@wdc.usda.gov.</E>
        </P>
        <SIG>
          <DATED>Dated: February 8, 2013.</DATED>
          <NAME>John Charles Padalino,</NAME>
          <TITLE>Administrator, Rural Utilities Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03346 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>Foreign-Trade Zones Board</SUBAGY>
        <DEPDOC>[Order No. 1881]</DEPDOC>
        <SUBJECT>Expansion/Reorganization of Foreign-Trade Subzone 70T;Marathon Petroleum Company LP;Detroit, MI</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 Greater Detroit Foreign-Trade Zone, Inc., grantee of Foreign-Trade Zone 70, submitted an application to the Board for authority to expand Site 1 of Subzone 70T and remove Site 3 of the subzone at the Marathon Petroleum Company LP refinery in Detroit, Michigan. (B-42-2012, docketed 6/1/2012);</P>
        <P>
          <E T="03">Whereas,</E>notice inviting public comment has been given in the<E T="04">Federal Register</E>(77 FR 33716-33717) 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;</P>
        <P>
          <E T="03">Now, therefore,</E>the Board hereby orders:</P>
        <P>The application to expand and reorganize Subzone 70T is approved, subject to the FTZ Act and the Board's regulations, including Section 400.13.</P>
        <SIG>
          <DATED>Signed at Washington, DC, this 6th day of February 2013.</DATED>
          <NAME>Paul Piquado,</NAME>
          <TITLE>Assistant Secretary of Commerce for 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-03352 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="10129"/>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>Foreign-Trade Zones Board</SUBAGY>
        <DEPDOC>[Order No. 1883]</DEPDOC>
        <SUBJECT>Approval for Expansion of Manufacturing Authority; Foreign-Trade Zone 104; Mitsubishi Power Systems Americas, Inc. (Power Generation Turbines); Pooler, GA</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 Savannah Airport Commission, grantee of FTZ 104, has requested an expansion of the scope of manufacturing authority on behalf of Mitsubishi Power Systems Americas, Inc. (MPSA), operator of Site 12, to include additional finished products and foreign components (FTZ Docket 11-2012, filed 2-23-2012);</P>
        <P>
          <E T="03">Whereas,</E>notice inviting public comment has been given in the<E T="04">Federal Register</E>(77 FR 12799-12800, 3-2-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 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 expand scope of FTZ manufacturing authority to include additional finished products and foreign components, as described in the application and<E T="04">Federal Register</E>notice, is approved, subject to the FTZ Act and the Board's regulations, including Section 400.13.</P>
        <SIG>
          <DATED>Signed at Washington, DC, this 6th day of February 2013.</DATED>
          <NAME>Paul Piquado,</NAME>
          <TITLE>Assistant Secretary of Commerce for Import Administration, Alternate Chairman, Foreign-Trade Zones Board.</TITLE>
          <NAME>Andrew McGilvray,</NAME>
          <TITLE>Executive Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-03308 Filed 2-12-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. 1879]</DEPDOC>
        <SUBJECT>Reorganization/Expansion of Foreign-Trade Zone 90 Under Alternative Site Framework, Onondaga County, NY</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 County of Onondaga, New York, grantee of Foreign-Trade Zone 90, submitted an application to the Board (FTZ Docket B-61-2012, docketed 8/6/2012) for authority to reorganize and expand under the ASF with a service area of Onondaga, Cayuga, Oswego and Madison Counties, New York, in and adjacent to the Syracuse Customs and Border Protection port of entry, FTZ 90's existing Site 1 would be removed, and the grantee proposes two new magnet sites (Sites 2 and 3);</P>
        <P>
          <E T="03">Whereas,</E>notice inviting public comment was given in the<E T="04">Federal Register</E>(77 FR 47815-47816, 8/10/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 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 is in the public interest;</P>
        <P>
          <E T="03">Now, therefore,</E>the Board hereby orders:</P>
        <P>The application to reorganize FTZ 90 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 five-year ASF sunset provision for magnet sites that would terminate authority for Sites 2 and 3 if not activated by January 31, 2018.</P>
        <SIG>
          <DATED>Signed at Washington, DC, this 6th day of February 2013.</DATED>
          <NAME>Paul Piquado,</NAME>
          <TITLE>Assistant Secretary of Commerce for 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-03362 Filed 2-12-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. 1878]</DEPDOC>
        <SUBJECT>Reorganization of Foreign-Trade Zone 70 Under Alternative Site Framework, Detroit, MI</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 400.2(c)) as an option for the establishment or reorganization of zones;</P>
        <P>
          <E T="03">Whereas,</E>the Greater Detroit Foreign-Trade Zone, Inc., grantee of Foreign-Trade Zone 70, submitted an application to the Board (FTZ Docket B-46-2012, docketed 6/20/2012) for authority to reorganize under the ASF with a service area of Macomb, Monroe, Oakland, Washtenaw and Wayne Counties, Michigan, in and adjacent to the Detroit Customs and Border Protection port of entry, FTZ 70's existing 3, 5, 12, 14 and 19 would be categorized as magnet sites, existing Sites 2, 4, 6, 8-11, 13, 15, 17, 18, 20-26, 29-31, 33-42 and 49-51 would be categorized as usage-driven sites, Site 15A would be removed, parcels from Site 5 would be renumbered as Sites 43 and 44, parcels from Site 11 would be renumbered as Sites 45 and 46 and parcels from Site 14 would be renumbered as Sites 47 and 48;</P>
        <P>
          <E T="03">Whereas,</E>notice inviting public comment was given in the<E T="04">Federal Register</E>(77 FR 38037-38038, 6/26/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 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 is in the public interest;<PRTPAGE P="10130"/>
        </P>
        <P>
          <E T="03">Now, therefore,</E>the Board hereby orders:</P>

        <P>The application to reorganize FTZ 70 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 five-year ASF sunset provisions for magnet sites that would terminate authority for Sites 3, 5, 12, 14 and 19 if not activated by January 31, 2018, and to three-year ASF sunset provisions for usage-driven sites that would terminate authority for Sites 2, 4, 6, 8-11, 13, 15, 17, 18, 20-26, and 29-31 and 33-51 if no foreign-status merchandise is admitted for a<E T="03">bona fide</E>customs purpose by January 31, 2016.</P>
        <SIG>
          <DATED>Signed at Washington, DC, this 6th day of February 2013.</DATED>
          <NAME>Paul Piquado,</NAME>
          <TITLE>Assistant Secretary of Commerce for 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-03363 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>International Trade Administration</SUBAGY>
        <DEPDOC>[A-570-952]</DEPDOC>
        <SUBJECT>Narrow Woven Ribbons With Woven Selvedge From the People's Republic of China: Final Results of Antidumping Duty Administrative Review; 2010-2011</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Import Administration, International Trade Administration, Department of Commerce.</P>
        </AGY>
        
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The Department of Commerce (the “Department”) published its<E T="03">Preliminary Results</E>of administrative review of the antidumping duty order on narrow woven ribbons with woven selvedge (“narrow woven ribbons”) on August 8, 2012.<SU>1</SU>

            <FTREF/>The period of review (“POR”) is September 1, 2010, through August 31, 2011. The Department invited interested parties to comment on the<E T="03">Preliminary Results.</E>Based on an analysis of the comments received, the Department made no changes to the margins assigned in the<E T="03">Preliminary Results.</E>The final dumping margins for this review are listed in the “Final Results of Review” section below.</P>
          <FTNT>
            <P>
              <SU>1</SU>
              <E T="03">See Narrow Woven Ribbons With Woven Selvedge From the People's Republic of China: Preliminary Results and Partial Rescission of Antidumping Duty Administrative Review,</E>77 FR 47363 (August 8, 2012) (“<E T="03">Preliminary Results”</E>).</P>
          </FTNT>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>February 13, 2013.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Karine Gziryan or Robert Bolling, AD/CVD Operations, Office 4, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue NW., Washington, DC 20230; telephone: (202) 482-4081 or (202) 482-3434, respectively.</P>
          <HD SOURCE="HD1">Background</HD>
          <P>On August 8, 2012, the Department published its<E T="03">Preliminary Results.</E>On September 7, 2012, Hubscher Ribbon Corp., Ltd. (“Hubschercorp”) submitted a case brief for this administrative review.<SU>2</SU>
            <FTREF/>On September 12, 2012, the Department received a rebuttal brief from Berwick Offray LLC and its wholly-owned subsidiary Lion Ribbon Company, Inc. (collectively, “Petitioner”).<SU>3</SU>
            <FTREF/>No other party submitted comments.</P>
          <FTNT>
            <P>
              <SU>2</SU>
              <E T="03">See</E>Letter from Hubschercorp to the Secretary of Commerce, “Narrow Woven Ribbons With Woven Selvedge from China, Antidumping Duty: Case Brief” (September 7, 2012).</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>3</SU>
              <E T="03">See</E>Letter from Petitioner to the Secretary of Commerce, “Rebuttal Brief on Behalf of Petitioner Berwick Offray LLC and Its Wholly-Owned Subsidiary Lion Ribbon Company, Inc.” (September 12, 2012).</P>
          </FTNT>
          <HD SOURCE="HD1">Extension of Final Results Due to Government Closure During Hurricane Sandy</HD>
          <P>As explained in the memorandum from the Assistant Secretary for Import Administration, the Department has exercised its discretion to toll deadlines for the duration of the closure of the Federal Government from October 29, through October 30, 2012. Thus, all deadlines in this segment of the proceeding have been extended by two days.<SU>4</SU>
            <FTREF/>Therefore, the revised deadline for the final results of this review is now February 6, 2013.</P>
          <FTNT>
            <P>
              <SU>4</SU>
              <E T="03">See</E>Memorandum For the Record from Paul Piquado, Assistant Secretary for Import Administration, “Tolling of Administrative Deadlines as a Result of the Government Closure During Hurricane Sandy” (October 31, 2012).</P>
          </FTNT>
          <HD SOURCE="HD1">Scope of the Order</HD>
          <P>The merchandise covered by this order includes narrow woven ribbons with woven selvedge, in any length, but with a width (measured at the narrowest span of the ribbon) less than or equal to 12 centimeters, composed of, in whole or in part, man-made fibers (whether artificial or synthetic, including but not limited to nylon, polyester, rayon, polypropylene, and polyethylene teraphthalate), metal threads and/or metalized yarns, or any combination thereof.<SU>5</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>5</SU>
              <E T="03">See</E>Issues and Decision Memorandum for the Final Results of Antidumping Duty Administrative Review issued concurrently with this notice for a complete description of the Scope of the Order.</P>
          </FTNT>
          <P>The merchandise subject to the order is classifiable under the Harmonized Tariff Schedule of the United States (“HTSUS”) statistical categories 5806.32.1020; 5806.32.1030; 5806.32.1050 and 5806.32.1060. Subject merchandise also may enter under subheadings 5806.31.00; 5806.32.20; 5806.39.20; 5806.39.30; 5808.90.00; 5810.91.00; 5810.99.90; 5903.90.10; 5903.90.25; 5907.00.60; and 5907.00.80 and under statistical categories 5806.32.1080; 5810.92.9080; 5903.90.3090; and 6307.90.9889. The HTSUS statistical categories and subheadings are provided for convenience and customs purposes; however, the written description of the merchandise covered by the order is dispositive.<SU>6</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>6</SU>
              <E T="03">See Notice of Antidumping Duty Orders: Narrow Woven Ribbons With Woven Selvedge From Taiwan and the People's Republic of China: Antidumping Duty Orders,</E>75 FR 53632 (September 1, 2010), as amended in<E T="03">Narrow Woven Ribbons With Woven Selvedge From Taiwan and the People's Republic of China: Amended Antidumping Duty Orders,</E>75 FR 56982 (September 17, 2010) (“<E T="03">Orders”</E>).</P>
          </FTNT>
          <HD SOURCE="HD1">Analysis of Comments Received</HD>

          <P>All issues raised in the case and rebuttal briefs submitted by parties in this review are addressed in the Memorandum from Christian Marsh, Deputy Assistant Secretary for Antidumping and Countervailing Duty Operations, to Paul Piquado, Assistant Secretary for Import Administration, “Issues and Decision Memorandum for the Final Results of the Administrative Review of Narrow Woven Ribbons with Woven Selvedge from the People's Republic of China” (dated concurrently with this notice) (“Issues and Decision Memorandum”) and the Memorandum to the File from Karine Gziryan, Senior Financial Analyst, Office 4, NME Unit, “Antidumping Administrative Review of Narrow Woven Ribbons with Woven Selvedge from the People's Republic of China: Proprietary Memorandum regarding Corroboration of Adverse Facts Available Rate” (dated concurrently with this notice) (“Final Corroboration Memo”), which is hereby adopted by this notice. The issue that parties raised and to which the Department responded in the Issues and Decision Memorandum is attached to this notice as an appendix. The Issues and Decision Memorandum is a public document and is on file electronically via Import Administration's Antidumping and Countervailing Duty<PRTPAGE P="10131"/>Centralized Electronic Service System (“IA ACCESS”). Access to IA ACCESS is available to registered users at<E T="03">http://iaaccess.trade.gov</E>, and is available to all parties in the Central Records Unit, which is in room 7046 of the main Department of Commerce building. In addition, a complete version of the Issues and Decision Memorandum can be accessed directly on the internet at<E T="03">www.trade.gov/ia/</E>. The signed Issues and Decision Memorandum and the electronic versions of the Issues and Decision Memorandum are identical in content.</P>
          <HD SOURCE="HD1">Changes Since the Preliminary Results</HD>

          <P>Based on an analysis of the comment received, the Department made no changes to the margins assigned in the<E T="03">Preliminary Results.</E>
          </P>
          <HD SOURCE="HD1">Non-Market Economy Country</HD>
          <P>The PRC has been treated as a non-market economy (“NME”) in every proceeding conducted by the Department. In accordance with section 771(18)(C)(i) of the Tariff Act of 1930, as amended (the “Act”), any determination that a foreign country is an NME shall remain in effect until revoked by the administering authority. The Department has not revoked the PRC's status as an NME. Therefore, the Department continues to treat the PRC as an NME for purposes of these final results and, accordingly, applied the NME methodology.</P>
          <HD SOURCE="HD1">Separate Rates</HD>
          <P>In proceedings involving NMEs, the Department maintains a rebuttable presumption that all companies within the NME are subject to government control and, therefore, should be assessed a single weighted-average dumping margin.<SU>7</SU>
            <FTREF/>The Department's policy is to assign all exporters of merchandise under consideration that are in an NME this single rate unless an exporter can demonstrate that it is sufficiently independent so as to be entitled to a separate rate.<SU>8</SU>

            <FTREF/>The Department analyzes whether each entity exporting the merchandise under consideration is sufficiently independent under a test established in<E T="03">Sparklers</E>
            <SU>9</SU>
            <FTREF/>and further developed in<E T="03">Silicon Carbide.</E>
            <SU>10</SU>

            <FTREF/>According to this separate rate test, the Department will assign a separate rate in NME proceedings if a respondent can demonstrate the absence of both<E T="03">de jure</E>and<E T="03">de facto</E>government control over its export activities. If, however, the Department determines that a company is wholly foreign owned, then a separate rate analysis is not necessary to determine whether that company is independent from government control and eligible for a separate rate.</P>
          <FTNT>
            <P>
              <SU>7</SU>
              <E T="03">See, e.g.,</E>
              <E T="03">Polyethylene Terephthalate Film, Sheet, and Strip from the People's Republic of China: Final Determination of Sales at Less Than Fair Value,</E>73 FR 55039, 55040 (September 24, 2008).</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>8</SU>
              <E T="03">See Final Determination of Sales at Less Than Fair Value: Sparklers From the People's Republic of China,</E>56 FR 20588, 20589 (May 6, 1991) (“<E T="03">Sparklers”</E>).</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>9</SU>
              <E T="03">Id.</E>
            </P>
          </FTNT>
          <FTNT>
            <P>
              <SU>10</SU>
              <E T="03">See Notice of Final Determination of Sales at Less Than Fair Value: Silicon Carbide From the People's Republic of China,</E>59 FR 22585 (May 2, 1994) (“<E T="03">Silicon Carbide”</E>).</P>
          </FTNT>
          <P>In the<E T="03">Preliminary Results,</E>the Department found that Weifang Dongfang Ribbon Weaving Co., Ltd. (“Weifang Dongfang”) demonstrated its eligibility for separate-rate status.<SU>11</SU>

            <FTREF/>No party commented on this preliminary determination. For the final results, the Department continues to find that the evidence placed on the record of this administrative review by Weifang Dongfang demonstrate both a<E T="03">de jure</E>and<E T="03">de facto</E>absence of government control and, therefore, is eligible for separate-rate status.</P>
          <FTNT>
            <P>
              <SU>11</SU>
              <E T="03">See Preliminary Results,</E>77 FR at 47366.</P>
          </FTNT>
          <HD SOURCE="HD1">Calculation of Separate Rate</HD>
          <P>In accordance with section 777A(c)(2)(B) of the Act, the Department employed a limited examination methodology, as it did not have the resources to examine all companies for which a review request was made. The Department selected two respondents for review, Precious Planet Ribbons &amp; Bows Co., Ltd. (“Precious Planet”) and Hubschercorp. On January 24, 2012, Precious Planet timely withdrew its request for an administrative review of its sales.<SU>12</SU>
            <FTREF/>On May 29, 2012, Hubschercorp indicated that it would no longer participate in the administrative review and failed to further answer the Department's questionnaires.<SU>13</SU>
            <FTREF/>For those companies not selected for review, only Weifang Dongfang submitted timely information as requested by the Department and remains subject to the review as a cooperative separate rate respondent.</P>
          <FTNT>
            <P>
              <SU>12</SU>
              <E T="03">See</E>Letter from Precious Planet to the Secretary of Commerce, “Narrow Woven Ribbons With Woven Selvedge from China, Antidumping Duty: Revised Withdrawal of Request for Administrative Review” (January 24, 2012).</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>13</SU>
              <E T="03">See</E>Letter from Hubschercorp's to the Secretary of Commerce, “Narrow Woven Ribbons With Woven Selvedge from China, Antidumping Duty: Withdrawal from Administrative Review” (May 29, 2012).</P>
          </FTNT>

          <P>We note that the Act and the Department's regulations do not directly address the establishment of a rate to be applied to individual companies not selected for examination where the Department limited its examination in an administrative review pursuant to section 777A(c)(2) of the Act. The Department's practice in cases involving limited selection based on exporters accounting for the largest volumes of trade has been to look to section 735(c)(5) of the Act, which provides instructions for calculating the all-others rate in an investigation, for guidance. Section 735(c)(5)(A) of the Act instructs that in most investigations we are not to calculate an all-others rate using any zero or<E T="03">de minimis</E>margins or any margins based entirely on facts available. Section 735(c)(5)(B) of the Act also provides that, where all margins are zero rates,<E T="03">de minimis</E>rates, or rates based entirely on facts available, we may use “any reasonable method” for assigning the rate to non-selected respondents. Furthermore, Congress, in the Statement of Administrative Action (“SAA”), stated that when “the dumping margins for all of the exporters and producers that are individually investigated are determined entirely on the basis of the facts available or are zero or<E T="03">de minimis</E>* * * (t)he expected method in such cases will be to weight-average the zero and<E T="03">de minimis</E>margins and margins determined pursuant to the facts available.”<SU>14</SU>
            <FTREF/>However, Congress also stated that “if this method is not feasible, or if it results in an average that would not be reasonably reflective of potential dumping margins for non-investigated exporters or producers, (the Department) may use other reasonable methods.”<SU>15</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>14</SU>
              <E T="03">See</E>SAA accompanying the Uruguay Round Agreements Act, H.R. Doc. No. 103-316 at 873 (1994), reprinted in 1994 U.S.C.C.A.N. 4040, 4200.</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>15</SU>
              <E T="03">Id.</E>
            </P>
          </FTNT>
          <P>In this instance, because one of the two selected respondents, Precious Planet, timely withdrew its request for an administrative review of its sales, the only rate determined in this review for a selected respondent, Hubschercorp, is based entirely on facts available.</P>

          <P>We note that the Department has used other reasonable means to assign separate-rate margins to non-reviewed companies in instances in which the use of an “average” of calculated zero rates,<E T="03">de minimis</E>rates, or rates based entirely on facts available was not possible.<SU>16</SU>
            <FTREF/>In<E T="03">Vietnam Shrimp AR3 Final,</E>the Department assigned to those separate<PRTPAGE P="10132"/>rate companies with no history of an individually calculated rate the margin determined for cooperative separate rate respondents from the underlying investigation.<SU>17</SU>
            <FTREF/>However, for those separate rate respondents that had received a calculated rate in a prior segment, concurrent with or more recent than the calculated rate in the underlying investigation, the Department assigned that calculated rate as the company's separate rate in the review at hand.<SU>18</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>16</SU>
              <E T="03">See Certain Frozen Warmwater Shrimp From the Socialist Republic of Vietnam: Final Results and Final Partial</E>
              <E T="03">Rescission of Antidumping Duty Administrative Review,</E>74 FR 47191, 47194 (September 15, 2009) (“<E T="03">Vietnam Shrimp AR3 Final”</E>).</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>17</SU>
              <E T="03">See Administrative Review of Certain Frozen Warmwater Shrimp From the People's Republic of China: Final Results and Partial Rescission of Antidumping Duty Administrative Review,</E>75 FR 49460, 49463 (August 13, 2010).</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>18</SU>
              <E T="03">Id.</E>
            </P>
          </FTNT>
          <P>In this review, we preliminarily found that a reasonable method was to assign to the separate rate company Weifang Dongfang, with no history of an individually calculated rate, the margin calculated for cooperative separate rate respondents in the underlying investigation, 123.83 percent.<SU>19</SU>
            <FTREF/>No parties commented on this separate rate and we continue to assign this separate rate for the final results.</P>
          <FTNT>
            <P>
              <SU>19</SU>
              <E T="03">See Narrow Woven Ribbons With Woven Selvedge From the People's Republic of China: Final Determination of Sales at Less Than Fair Value,</E>75 FR 41808, 41812 (July 19, 2010) (“Final LTFV Determination”).</P>
          </FTNT>
          <HD SOURCE="HD1">The PRC-Wide Entity</HD>
          <P>In addition to the separate-rate certification discussed above, there were two companies, Stribbons (Guangzhou) Ltd. (“Stribbons Guangzhou”), Stribbons (Nanyang) MNC, Ltd. (“Stribbons MNC”), (collectively “MNC Stribbons”<SU>20</SU>
            <FTREF/>) for which we initiated a review in this proceeding and which previously had a separate rate. However, in accordance with the Department's established NME methodology, a party's separate rate status must be established in each segment of the proceeding in which the party is involved.<SU>21</SU>
            <FTREF/>Because these companies did not file a timely (<E T="03">i.e.,</E>within 60 calendar days after publication of Initiation Notice<SU>22</SU>
            <FTREF/>) separate rate certification to demonstrate eligibility for a separate rate in this administrative review, or certify that they had no shipments,<SU>23</SU>
            <FTREF/>we preliminarily determined that these companies were part of the PRC-wide entity. In addition, because Precious Planet withdrew timely the only request for review and did not have a prior separate rate status, it is also part of the PRC-wide entity. No parties commented on these determinations and we continue to find these companies part of the PRC-wide entity for these final results.</P>
          <FTNT>
            <P>
              <SU>20</SU>MNC Stribbons filed their Separate Rate Certification on behalf of two companies under collective name MNC Stribbons, however, the Department initiated our administrative review on two companies Stribbons Guangzhou and Stribbons MNC, and we will continue to treat these two companies as two separate entities.</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>21</SU>
              <E T="03">See Sigma Corp.</E>v.<E T="03">United States,</E>117 F.3d 1401, 1405-06 (Fed. Cir. 1997) (affirming the Department's presumption of State control over exporters in NME cases).</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>22</SU>
              <E T="03">See Initiation of Antidumping and Countervailing Duty Administrative Reviews and Requests for Revocation in Part,</E>76 FR 67133, 67134 (October 31, 2011).</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>23</SU>
              <E T="03">See id.</E>
            </P>
          </FTNT>

          <P>We note that MNC Stribbons filed a request to be selected as a voluntary respondent after one of the selected respondents withdrew from the proceeding. However, MNC Stribbons made this request after it had missed the 60-day deadline to demonstrate its eligibility for a separate rate (<E T="03">i.e.,</E>failed to provide a timely separate rate certification) and the Department returned its submissions in accordance with 19 CFR 351.302(d).<SU>24</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>24</SU>
              <E T="03">See</E>Letter from Robert Bolling, Program Manager, AD/CVD Operations, Office 4 to Mr. James Cannon, Williams Mullen, representing Stribbons (Guangzhou) Ltd. and Stribbons (Nanyang) MNC Ltd., dated January 13, 2012 (“Rejection Letter”).</P>
          </FTNT>
          <HD SOURCE="HD1">Use of Facts Otherwise Available and AFA</HD>
          <P>Section 776(a) of the Act provides that the Department shall apply “facts otherwise available” if: (1) necessary information is not on the record; or (2) an interested party or any other person (A) withholds information that has been requested, (B) fails to provide information within the deadlines established, or in the form and manner requested by the Department, subject to subsections (c)(1) and (e) of section 782 of the Act, (C) significantly impedes a proceeding, or (D) provides information that cannot be verified as provided by section 782(i) of the Act.</P>
          <P>Hubschercorp did not respond to the Department's Section D questionnaire or Sections A and C supplemental questionnaires in this administrative review, and informed the Department that it would no longer participate in this review.<SU>25</SU>
            <FTREF/>As a result, Hubschercorp failed to provide requested information that is necessary for the Department to calculate an antidumping duty rate for Hubschercorp in this administrative review. This information includes complete product characteristics related to control numbers of products sold in the United States, FOPs, consumption rates of FOPs, and production processes data. Without this information, it is not possible for the Department to determine or calculate an antidumping margin.</P>
          <FTNT>
            <P>
              <SU>25</SU>
              <E T="03">See</E>Hubschercorp's May 29, 2012, submission.</P>
          </FTNT>
          <P>Hubschercorp withheld requested information, significantly impeded this proceeding and did not provide the Department with the information necessary to calculate an antidumping duty margin. Therefore, pursuant to section 776(a)(1) and (2)(A) and (C) of the Act, the Department finds that the use of total facts available is appropriate.</P>
          <P>Section 776(b) of the Act further provides that the Department may use an adverse inference in applying the facts otherwise available when a party has failed to cooperate by not acting to the best of its ability to comply with a request for information.<SU>26</SU>
            <FTREF/>Adverse inferences are appropriate “to ensure that the party does not obtain a more favorable result by failing to cooperate than if it had cooperated fully.”<SU>27</SU>
            <FTREF/>Furthermore, “affirmative evidence of bad faith on the part of a respondent is not required before the Department may make an adverse inference.”<SU>28</SU>
            <FTREF/>We find that Hubschercorp did not act to the best of its ability in this administrative review, within the meaning of section 776(b) of the Act, because it failed to respond to the Department's requests for information and failed to provide timely information. Therefore, we preliminarily determined that an adverse inference was warranted in selecting from the facts otherwise available with respect to this company.<SU>29</SU>
            <FTREF/>No parties disagreed with this determination and we continue to apply facts available with an adverse inference to Hubschercorp for these final results.</P>
          <FTNT>
            <P>
              <SU>26</SU>
              <E T="03">See Notice of Final Results of Antidumping Duty Administrative Review: Stainless Steel Bar from India,</E>70 FR 54023, 54025-26 (September 13, 2005);<E T="03">Notice of Final Determination of Sales at Less Than Fair Value and Final Negative Critical Circumstances: Carbon and Certain Alloy Steel Wire Rod from Brazil,</E>67 FR 55792, 55794-96 (August 30, 2002).</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>27</SU>
              <E T="03">See</E>SAA, at 870.</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>28</SU>
              <E T="03">See Antidumping Duties; Countervailing Duties; Final rule,</E>62 FR 27296, 27340 (May 19, 1997);<E T="03">see also</E>
              <E T="03">Nippon Steel Corp.</E>v.<E T="03">United States,</E>337 F.3d 1373, 1382-83 (Fed. Cir. 2003) (“<E T="03">Nippon”</E>).</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>29</SU>
              <E T="03">See Nippon,</E>337 F.3d at 1382-83.</P>
          </FTNT>
          <HD SOURCE="HD1">Selection of the Adverse Facts Available (“AFA”) Rate</HD>
          <P>Section 776(b) of the Act provides that the Department may use as AFA information derived from: (1) The petition; (2) the final determination in the investigation; (3) any previous review; or (4) any other information placed on the record.</P>

          <P>In the SAA, Congress expressly stated that the choice of AFA must “ensure<PRTPAGE P="10133"/>that the party does not obtain a favorable result by failing to corroborate than if it had cooperated fully. In employing adverse inferences, “one factor” the Department “will consider is the extent to which a party may benefit from its own lack of cooperation.”<SU>30</SU>
            <FTREF/>The Department's practice, when selecting an AFA rate from among the possible sources of information, has been to select the highest rate on the record of the proceeding and to ensure that the margin is sufficiently adverse “as to effectuate the statutory purposes of the adverse facts available rule to induce respondents to provide the Department with complete and accurate information in a timely manner.”<SU>31</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>30</SU>
              <E T="03">See</E>SAA, at 870.</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>31</SU>
              <E T="03">See, e.g.,</E>
              <E T="03">Certain Steel Concrete Reinforcing Bars from Turkey; Final Results and Rescission of Antidumping Duty Administrative Review in Part,</E>71 FR 65082, 65084 (November 7, 2006).</P>
          </FTNT>
          <P>As a result, we have assigned to Hubschercorp a rate of 247.65 percent, which is the highest rate alleged in the petition, as noted in the initiation of the less-than-fair-value (“LTFV”) investigation, adjusted with the surrogate value for labor rate used in the final determination.<SU>32</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>32</SU>
              <E T="03">See Narrow Woven Ribbons with Woven Selvedge from the People's Republic of China and Taiwan: Initiation of Antidumping Duty Investigations,</E>74 FR 39291 (August 6, 2009) (“<E T="03">LTFV Initiation”</E>) and<E T="03">Final LTFV Determination,</E>75 FR at 41812, and accompanying Issues and Decision Memorandum at Comment 1.</P>
          </FTNT>
          <HD SOURCE="HD1">Corroboration of Secondary Information</HD>
          <P>Information from prior segments of the proceeding constitutes secondary information and section 776(c) of the Act provides that the Department shall, to the extent practicable, corroborate that secondary information from independent sources reasonably at its disposal. The Department's regulations provide that “corroborate” means that the Department will satisfy itself that the secondary information to be used has probative value.<SU>33</SU>
            <FTREF/>To be considered corroborated, the Department must find the secondary information is both reliable and relevant.<SU>34</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>33</SU>
              <E T="03">See</E>19 CFR 351.308(d);<E T="03">see also</E>SAA, at 870.</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>34</SU>
              <E T="03">See, e.g.,</E>
              <E T="03">Tapered Roller Bearings and Parts Thereof, Finished and Unfinished, From Japan, and Tapered Roller Bearings, Four Inches or Less in Outside Diameter, and Components Thereof, From Japan; Preliminary Results of Antidumping Duty Administrative Reviews and Partial Termination of Administrative Reviews,</E>61 FR 57391, 57392 (November 6, 1996), unchanged in<E T="03">Tapered Roller Bearings and Parts Thereof, Finished and Unfinished, From Japan, and Tapered Roller Bearings, Four Inches or Less in Outside Diameter, and Components Thereof, From Japan; Final Results of Antidumping Duty Administrative Reviews and Termination in Part,</E>62 FR 11825 (March 13, 1997).</P>
          </FTNT>
          <P>To determine whether the information is reliable, we placed information from the LTFV investigation on the record of this segment of the proceeding, and reviewed the adequacy and accuracy of the information in the petition during our pre-initiation analysis for purposes of these final results, including source documents as well as publicly available information.<SU>35</SU>
            <FTREF/>Based on our examination of the information, we have determined that the margins in the petition are reliable for the purposes of this administrative review.<SU>36</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>35</SU>
              <E T="03">See LTFV Initiation,</E>74 FR at 39294-39296.</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>36</SU>
              <E T="03">See</E>Issues and Decision Memorandum, at Comment 1.</P>
          </FTNT>

          <P>To determine the relevance of the petition margin, we placed the model-specific rates calculated for the mandatory respondent, Yama Ribbons and Bows Co., Ltd. (“Yama”), in the LTFV investigation on the record of this segment of the proceeding and compared the 247.65 percent rate with those model-specific rates. We find that this margin is relevant because the petition rate fell within the range of model-specific margins calculated for the mandatory respondent in the LTFV investigation, this is the first review under this order (<E T="03">i.e.,</E>only one segment removed from the LTFV investigation), and Hubschercorp exported merchandise during the POR that was specifically produced by Yama.<SU>37</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>37</SU>
              <E T="03">See id.;</E>Final Corroboration Memo; and the Memorandum to the File from Karine Gziryan, Analyst, entitled, “Placement of Proprietary Model-Specific Margins from the Less-Than-Fair-Value Investigation on the Record and Corroboration of Adverse Facts Available Rate for the Preliminary Results in the 2010-2011 Antidumping Duty Administrative Review of Narrow Woven Ribbons with Woven Selvedge from the PRC,” dated July 31, 2012 (“Preliminary Corroboration Memo”).</P>
          </FTNT>
          <P>Further, the Department will consider information reasonably at its disposal as to whether there are circumstances that would render a margin inappropriate. Where circumstances indicate that the selected margin is not appropriate as AFA, the Department may disregard the margin and determine an appropriate margin.<SU>38</SU>
            <FTREF/>Therefore, we examined whether any information on the record would discredit the selected rate as reasonable facts available. No information on the administrative record discredits the selected AFA rate.</P>
          <FTNT>
            <P>
              <SU>38</SU>
              <E T="03">See, e.g.,</E>
              <E T="03">Fresh Cut Flowers from Mexico; Final Results of Antidumping Duty Administrative Review,</E>61 FR 6812, 6814 (February 22, 1996) (where the Department disregarded the highest calculated margin as AFA because the margin was based on a company's uncharacteristic business expense resulting in an unusually high margin).</P>
          </FTNT>

          <P>Based on the above, for these final results, the Department finds the highest rate derived from the petition (<E T="03">i.e.,</E>247.65 percent) is, therefore, corroborated to the extent practicable, pursuant to section 776(c) of the Act. Thus, we have assigned Hubschercorp this rate, as AFA, in this administrative review. For further discussion of the corroboration of this rate,<E T="03">see</E>Issues and Decision Memorandum at Comment 1, Final Corroboration Memo, and the Preliminary Corroboration Memo.</P>
          <HD SOURCE="HD1">Final Results of Review</HD>
          <P>The Department<FTREF/>determined that the dumping margins for the POR are as follows:</P>
          <FTNT>
            <P>
              <SU>39</SU>We note that Hubscher Ribbons Corp., Ltd. (d/b/a Hubschercorp) is a third-country reseller from Canada.</P>
            <P>
              <SU>40</SU>For the reasons stated above, the Department has concluded that the PRC-wide Entity includes Stribbons (Guangzhou) Ltd.; Stribbons (Nanyang) MNC Ltd. and Precious Planet.</P>
          </FTNT>
          <GPOTABLE CDEF="s25,12" COLS="2" OPTS="L2,tp0,i1">
            <TTITLE/>
            <BOXHD>
              <CHED H="1">Exporter</CHED>
              <CHED H="1">Weighted-average margin<LI>(percentage)</LI>
              </CHED>
            </BOXHD>
            <ROW>
              <ENT I="01">Hubscher Ribbon Corp., Ltd. (d/b/a Hubschercorp)<SU>39</SU>
              </ENT>
              <ENT>247.65</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Weifang Dongfang Ribbon Weaving Co., Ltd.</ENT>
              <ENT>123.83</ENT>
            </ROW>
            <ROW>
              <ENT I="01">PRC-wide Entity<SU>40</SU>
              </ENT>
              <ENT>247.65</ENT>
            </ROW>
          </GPOTABLE>
          <HD SOURCE="HD1">Assessment</HD>
          <P>Pursuant to section 751(a)(2)(A) of the Act and 19 CFR 351.212(b), the Department will determine, and U.S. Customs and Border Protection (“CBP”) shall assess, antidumping duties on all appropriate entries of subject merchandise in accordance with the final results of this review. In this case, the Department determined that the assessment rate for the separate rate respondent Weifang Dongfang will be the separate rate of 123.83 percent from the previous period less the 0.39 percent export subsidy rate<SU>41</SU>
            <FTREF/>which will be equal to 123.44 percent. The Department also determined that the assessment rate for Hubschercorp will be the highest petition rate of 247.65 percent less the 0.39 percent export subsidy rate<SU>42</SU>
            <FTREF/>which will be equal to 247.26 percent. Additionally, the Department will instruct CBP to liquidate entries of subject merchandise exported by the PRC-wide entity at the PRC-wide rate of 247.65 percent less the 0.39 percent export subsidy rate<SU>43</SU>

            <FTREF/>which will equal 247.26 percent. Accordingly, the Department is adjusting the assessment rates of Weifang Dongfang, Hubschercorp and the PRC-wide entity for export subsidies<PRTPAGE P="10134"/>in the same manner that the Department adjusted each company's cash deposit rate.<E T="03">See</E>Cash Deposit Requirements section below. The Department intends to issue appropriate assessment instructions directly to CBP 15 days after publication of the final results of this review.</P>
          <FTNT>
            <P>
              <SU>41</SU>
              <E T="03">See See</E>
              <E T="03">Narrow Woven Ribbons with Woven Selvedge from the People's Republic of China: Final Affirmative Countervailing Duty Determination,</E>75 FR 41801 (July 19, 2010) (“<E T="03">Final CVD Determination”</E>).</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>42</SU>
              <E T="03">See Final CVD Determination.</E>
            </P>
          </FTNT>
          <FTNT>
            <P>
              <SU>43</SU>
              <E T="03">See Final CVD Determination.</E>
            </P>
          </FTNT>
          <HD SOURCE="HD1">Cash Deposit Requirements</HD>
          <P>While the Department did not conduct a companion countervailing duty (“CVD”) administrative review, in the final determination of the CVD investigation on narrow woven ribbons from the PRC, the Department determined that the product under investigation benefitted from an export subsidy.<SU>44</SU>

            <FTREF/>Accordingly, the Department will instruct CBP to require an antidumping cash deposit equal to the weighted-average amount by which the normal value exceeds the export price, as indicated above, reduced by an amount, as appropriate, determined to constitute an export subsidy in the<E T="03">Final CVD Determination.</E>Therefore, for Hubschercorp, the separate rate respondent, Weifang Dongfang and the PRC-wide entity the Department will instruct CBP to require an antidumping duty cash deposit for each entry equal to the weighted-average margins indicated above adjusted for the export subsidy rate determined in the<E T="03">Final CVD Determination.</E>The adjusted cash deposit rates are 123.44 percent for Weifang Dongfang and 247.26 percent for Hubschercorp and the PRC-wide entity.<SU>45</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>44</SU>
              <E T="03">See Narrow Woven Ribbons with Woven Selvedge from the People's Republic of China: Final Affirmative Countervailing Duty Determination,</E>75 FR 41801 (July 19, 2010) (“<E T="03">Final CVD Determination”</E>).</P>
          </FTNT>
          <FTNT>
            <P>
              <SU>45</SU>
              <E T="03">See</E>Memorandum from Karine Gziryan to Robert Bolling regarding the adjusted cash deposit rate (dated concurrently with this notice) for further detail on the calculation of these adjustments.</P>
          </FTNT>
          <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 from the PRC entered, or withdrawn from warehouse, for consumption on or after the publication date, as provided for by section 751(a)(2)(C) of the Act: (1) For Hubschercorp, a third-country reseller from Canada, the cash deposit rate will be that established in the final results of this review; (2) for Weifang Dongfang, a PRC exporter which has a separate rate, the cash deposit rate will be that established in the final results of this review; (3) for previously investigated PRC exporters not listed above that received a separate rate in a prior segment of this proceeding, the cash deposit rate will continue to be the exporter-specific rate; (4) for all PRC exporters of subject merchandise that have not been found to be entitled to a separate rate, the cash deposit rate will be the PRC-wide rate of 247.26 percent;<SU>46</SU>
            <FTREF/>and (5) for all non-PRC exporters of subject merchandise which have not received their own rate, the cash deposit rate will be the rate applicable to the PRC exporter that supplied that non-PRC exporter. These deposit requirements, when imposed, shall remain in effect until further notice.</P>
          <FTNT>
            <P>
              <SU>46</SU>
              <E T="03">See Final LTFV Determination,</E>75 FR at 41812.</P>
          </FTNT>
          <HD SOURCE="HD1">Notification to Interested Parties</HD>
          <P>This notice serves as a final reminder to importers of their responsibility under 19 CFR 351.402(f)(2) to file a certificate regarding the reimbursement of antidumping duties prior to liquidation of the relevant entries during the review period. Pursuant to 19 CFR 351.402(f)(3), failure to comply with this requirement could result in the Department presuming that the exporter or producer paid or reimbursed the antidumping duties.</P>
          <P>This notice also serves as a reminder to parties subject to administrative protective order (“APO”) of their responsibility concerning the disposition of proprietary information disclosed under APO. 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 the terms of an APO is a sanctionable violation.</P>
          <P>This notice of the final results of this review is issued and published in accordance with sections 751(a)(1) and 777(i) of the Act.</P>
          <SIG>
            <DATED>Dated: February, 5, 2013.</DATED>
            <NAME>Paul Piquado,</NAME>
            <TITLE>Assistant Secretary for Import Administration.</TITLE>
          </SIG>
          <APPENDIX>
            <HD SOURCE="HED">APPENDIX</HD>
            <HD SOURCE="HD1">Comment in the Issues and Decision Memorandum</HD>
            <FP SOURCE="FP-1">Comment 1: Use of the Highest Petition Rate as Adverse Facts Available</FP>
            
          </APPENDIX>
        </FURINF>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-03236 Filed 2-12-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-588-857]</DEPDOC>
        <SUBJECT>Welded Large Diameter Line Pipe From Japan: Final Results of the Expedited Second Sunset Review of the Antidumping Duty Order</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 October 1, 2012, the Department of Commerce (the Department) initiated the second sunset review of the antidumping duty order on welded large diameter line pipe (line pipe) from Japan pursuant to section 751(c) of the Tariff Act of 1930, as amended (the Act).<SU>1</SU>
            <FTREF/>On the basis of a notice of intent to participate and an adequate substantive response filed on behalf of domestic interested parties, and no response from a respondent interested party, the Department conducted an expedited (120-day) sunset review. As a result of this sunset review, the Department finds that revocation of the antidumping duty order would likely lead to the continuation or recurrence of dumping. The magnitude of the margin of dumping likely to prevail if the order were revoked is identified in the “Final Results of Review” section of this notice.</P>
          <FTNT>
            <P>
              <SU>1</SU>
              <E T="03">See Initiation of Five-Year (“Sunset”) Review,</E>77 FR 59897 (October 1, 2012) (<E T="03">Sunset Initiation</E>).</P>
          </FTNT>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>February 13, 2013.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>John Drury or Angelica Mendoza, AD/CVD Operations, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue NW., Washington, DC 20230; telephone: (202) 482-0195 or (202) 482-3019, respectively.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Background</HD>

        <P>On October 1, 2012, the Department initiated the sunset review of the antidumping duty order on line pipe from Japan pursuant to section 751(c) of the Act.<E T="03">See Sunset Initiation.</E>The Department received a notice of intent to participate from United States Steel Corporation on October 10, 2012, and a notice of intent to participate from American Cast Iron Pipe Company (ACIPCO); Berg Steel Pipe Company; Dura-Bond Pipe LLC; Stupp Corporation; and Welspun Tubular LLC USA on October 11, 2012 (collectively,<PRTPAGE P="10135"/>domestic interested parties). All domestic interested parties provided information within the deadline specified in 19 CFR 351.218(d)(1)(i), and provided information required under 19 CFR 351.218(d)(1)(ii). The domestic interested parties claimed interested party status under section 771(9)(C) of the Act as U.S. producers of a domestic like product. We received a complete substantive response from the domestic interested parties within the 30-day deadline specified in 19 CFR 351.218(d)(3)(i) on October 31, 2012. No respondent interested parties submitted responses. As a result of the timely filed, substantive response from the domestic interested parties, the Department conducted an expedited sunset review of the order, pursuant to section 751(c)(3)(B) of the Act and 19 CFR 351.218(e)(1)(ii)(C)(2).</P>
        <HD SOURCE="HD1">Scope of the Order</HD>

        <P>The product currently is classified under U.S. Harmonized Tariff Schedule (HTSUS) item numbers 7305.11.10.30, 7305.11.10.60, 7305.11.50.00, 7305.12.10.30, 7305.12.10.60, 7305.12.50.00, 7305.19.10.30. 7305.19.10.60, and 7305.19.50.00. Although the HTSUS item numbers are provided for convenience and customs purposes, the written description of the scope in the accompanying decision memorandum remains dispositive.<E T="03">See</E>“Issues and Decision Memorandum” from Christian Marsh, Deputy Assistant Secretary for Antidumping and Countervailing Duty Operations, to Paul Piquado, Assistant Secretary for Import Administration, dated concurrently with this notice (Decision Memorandum).</P>
        <HD SOURCE="HD1">Analysis of Comments Received</HD>

        <P>All issues raised in this sunset review are addressed in the Decision Memorandum, which is hereby adopted by this notice. The issues discussed in the Decision Memorandum include the likelihood of the continuation or recurrence of dumping and the magnitude of the margin of dumping that is likely to prevail if the order were revoked. Parties can find a complete discussion of all issues raised in this sunset review and the corresponding recommendations in this public memorandum, which is on file electronically via Import Administration's Antidumping and Countervailing Duty Centralized Electronic Service System (IA ACCESS). IA ACCESS is available to registered users at<E T="03">http://iaaccess.trade.gov</E>and is available to all parties in the Central Records Unit, Room 7046, of the main Department of Commerce building. In addition, a complete version of the Decision Memorandum can be accessed directly on the Internet at<E T="03">http://ia.ita.doc.gov/frn.</E>The paper copy and electronic versions of the Decision Memorandum are identical in content.</P>
        <HD SOURCE="HD1">Final Results of Review</HD>
        <P>The Department determines that revocation of the antidumping duty order on line pipe from Japan would likely lead to continuation or recurrence of dumping. Further, the Department finds that the magnitude of the margin of dumping that is likely to prevail if the order was revoked is 30.80 percent for Nippon Steel Corporation, Kawasaki Steel Corporation, and for all other Japanese producers and exporters of subject merchandise.</P>
        <HD SOURCE="HD1">Notification</HD>
        <P>This notice also serves as the only reminder to parties subject to administrative protective order (APO) of their responsibility concerning the return or destruction of proprietary information disclosed under APO in accordance with 19 CFR 351.305. Timely notification of the return or destruction of APO materials or conversion to judicial protective order is hereby requested. Failure to comply with the regulations and terms of an APO is a violation which is subject to sanction.</P>
        <P>The Department is issuing and publishing the results and notice in accordance with sections 751(c), 752(c), and 777(i)(1) of the Act.</P>
        <SIG>
          <DATED>Dated: January 31, 2013.</DATED>
          <NAME>Paul Piquado,</NAME>
          <TITLE>Assistant Secretary for Import Administration.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03364 Filed 2-12-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-XC485</RIN>
        <SUBJECT>Fishing Capacity Reduction Program for the Longline Catcher Processor Subsector of the Bering Sea and Aleutian Islands Non-Pollock Groundfish Fishery</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration, Commerce.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of fee rate adjustment.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>NMFS issues this notice to decrease the fee rate for the non-pollock groundfish fishery to repay the $35,000,000 reduction loan to finance the non-pollock groundfish fishing capacity reduction program.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The non-pollock groundfish program fee rate decrease is effective January 1, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Send questions about this notice to Paul Marx, Chief, Financial Services Division, National Marine Fisheries Service, 1315 East-West Highway, Silver Spring, MD 20910-3282.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Paul Marx, (301) 427-8799.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Background</HD>
        <P>Sections 312(b)-(e) of the Magnuson-Stevens Fishery Conservation and Management Act (16 U.S.C. 1861a(b) through (e)) generally authorize fishing capacity reduction programs. In particular, section 312(d) authorizes industry fee systems for repaying reduction loans which finance reduction program costs.</P>
        <P>Subpart L of 50 CFR part 600 is the framework rule generally implementing section 312(b)-(e).</P>
        <P>Sections 1111 and 1112 of the Merchant Marine Act, 1936 (46 App. U.S.C. 1279f and 1279g) generally authorize reduction loans.</P>
        <P>Enacted on December 8, 2004, section 219, Title II, of FY 2005 Appropriations Act, Public Law 104-447 (Act) authorizes a fishing capacity reduction program implementing capacity reduction plans submitted to NMFS by catcher processor subsectors of the Bering Sea and Aleutian Islands (“BSAI”) non-pollock groundfish fishery (“reduction fishery”) as set forth in the Act.</P>
        <P>The longline catcher processor subsector (the “Longline Subsector”) is among the catcher processor subsectors eligible to submit to NMFS a capacity reduction plan under the terms of the Act.</P>
        <P>The longline subsector non-pollock groundfish reduction program's objective was to reduce the number of vessels and permits endorsed for longline subsector of the non-pollock groundfish fishery.</P>
        <P>All post-reduction fish landings from the reduction fishery are subject to the longline subsector non-pollock groundfish program's fee.</P>
        <P>NMFS proposed the implementing notice on August 11, 2006 (71 FR 46364), and published the final notice on September 29, 2006 (71 FR 57696).</P>

        <P>NMFS allocated the $35,000,000 reduction loan (A loan) to the reduction fishery and this loan is repayable by fees from the fishery.<PRTPAGE P="10136"/>
        </P>
        <P>On September 24, 2007, NMFS published in the<E T="04">Federal Register</E>(72 FR 54219), the final rule to implement the industry fee system for repaying the non-pollock groundfish program's reduction loan and established October 24, 2007, as the effective date when fee collection and loan repayment began. The regulations implementing the program are located at § 600.1012 of 50 CFR part 600's subpart M.</P>
        <P>NMFS published, in the<E T="04">Federal Register</E>on November 2, 2009 (74 FR 56592), a notice to decrease the A Loan fee rate to $0.016 per pound effective January 1, 2010. On November 12, 2010, NMFS published a notice (75 FR 69401) to decrease the fee rate to $0.015 per pound, effective January 1, 2011. NMFS published a notice on November 30, 2011 (76 FR 74048) to further decrease the fee rate once more to $0.0145 per pound effective January 1, 2012.</P>

        <P>NMFS published a final rule to implement a second $2,700,000 reduction loan (B loan) for this fishery in the<E T="04">Federal Register</E>on September 24, 2012 (77 FR 58775). The loan was disbursed December 18, 2012 with fee collection of $0.001 per pound to begin January 1, 2013. This fee is in addition to the A Loan fee.</P>
        <HD SOURCE="HD1">II. Purpose</HD>
        <P>The purpose of this notice is to adjust the fee rate for the reduction fishery in accordance with the framework rule's § 600.1013(b). Section 600.1013(b) directs NMFS to recalculate the fee to a rate that will be reasonably necessary to ensure reduction loan repayment within the specified 30 year term.</P>
        <P>NMFS has determined for the reduction fishery that the current fee rate of $0.0145 per pound is more than is needed to service the A loan. Therefore, NMFS is decreasing the fee rate to $0.0111 per pound which NMFS has determined is sufficient to ensure timely loan repayment. The fee rate for the B loan will remain $0.001 per pound.</P>
        <P>Subsector members may continue to use<E T="03">Pay.gov</E>to disburse collected fee deposits at:<E T="03">http://www.pay.gov/ paygov/.</E>
        </P>

        <P>Please visit the NMFS Web site for additional information at:<E T="03">http://www.nmfs.noaa.gov/mb/financial_services/buyback.htm.</E>
        </P>
        <HD SOURCE="HD1">III. Notice</HD>
        <P>The new fee rate for the non-pollock Groundfish fishery is effective January 1, 2013.</P>
        <P>From and after this date, all subsector members paying fees on the non-pollock groundfish fishery shall begin paying non-pollock groundfish fishery program fees at the revised rate. Any over-payments of landings made using the previous higher fee rate will be credited to future landings.</P>

        <P>Fee collection and submission shall follow previously established methods in § 600.1013 of the framework rule and in the final fee rule published in the<E T="04">Federal Register</E>on September 24, 2007 (72 FR 54219).</P>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>

          <P>The authority for this action is Public Law 108-447, 16 U.S.C. 1861a (b-e), and 50 CFR 600.1000<E T="03">et seq.</E>
          </P>
        </AUTH>
        <SIG>
          <DATED>Dated: February 7, 2013.</DATED>
          <NAME>Gary Reisner,</NAME>
          <TITLE>Director, Office of Management and Budget, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03350 Filed 2-12-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-XC398</RIN>
        <SUBJECT>Magnuson-Stevens Act Provisions; Fisheries of the Northeastern United States; Northeast Multispecies Fishery; Approved Monitoring Service Providers</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, approved monitoring service providers.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>NMFS has approved four companies to provide dockside and/or at-sea monitoring services to Northeast (NE) multispecies vessels in fishing year (FY) 2013. Regulations implementing Amendment 16 to the NE Multispecies Fishery Management Plan (Amendment 16) require third-party monitoring service providers to apply to, and be approved by, NMFS in a manner consistent with the Administrative Procedure Act in order to be eligible to provide dockside and/or at-sea monitoring services to sectors.</P>
        </SUM>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Copies of the list of NMFS-approved sector monitoring service providers are available at<E T="03">http://www.nero.noaa.gov/sfd/sfdmultisector.html</E>or by sending a written request to:</P>
          <P>• Fax: (978) 281-9135, Attn: Mark Grant.</P>
          <P>• Mail: 55 Great Republic Drive, Gloucester, MA 01930, Attn: Mark Grant.</P>
          <P>For service provider contact information, see the<E T="02">SUPPLEMENTARY INFORMATION</E>section of this notice.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Mark Grant, Sector Policy Analyst, (978) 281-9145, fax (978) 281-9135, email<E T="03">Mark.Grant@NOAA.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Amendment 16 expanded the sector management program, including adding a requirement to ensure accurate monitoring of both sector at-sea catch and dockside landings, and common pool dockside landings (75 FR 18262; April 9, 2010). Framework Adjustment 45 to the FMP (Framework 45, 76 FR 23042, April 25, 2011) revised several dockside monitoring requirements.</P>
        <HD SOURCE="HD1">Standards for Approving Sectors</HD>
        <P>Regulations at 50 CFR 648.87(b)(4) describe the criteria for NMFS approval of interested at-sea and dockside service providers. Once approved, providers must document having met performance requirements in order to maintain eligibility (§ 648.87(b)(4)(ii)). NMFS can disapprove any previously approved service provider during the FY if the service provider in question ceases to meet the performance standards. NMFS must notify service providers of disapproval in writing.</P>
        <P>NMFS first approved service providers for FY 2010, based upon the completeness of their application addressing the regulatory requirements (§ 648.87(b)(4)(i)), and a determination of the applicant's ability to perform the duties and responsibilities of a monitoring service provider. In FY 2011, NMFS approved service providers based on completeness of applications, determination of ability, and performance during FY 2010. NMFS did not approve any providers for FY 2012 because there was no dockside monitoring requirement and at-sea monitoring was provided solely by NMFS.</P>
        <P>NMFS is approving service providers for FY 2013 (beginning May 1, 2013) based on: (1) Completeness of applications; (2) determination of the applicant's ability to perform the duties and responsibilities of a sector monitoring service provider; and (3) performance as NMFS-funded providers in FY 2012.</P>

        <P>NE multispecies sectors are required to design and implement independent, third-party at-sea monitoring in FY 2013, and are responsible for the costs of these monitoring requirements, unless otherwise instructed by NMFS. The regulations currently require the NE multispecies fishery to hire and pay for dockside monitoring in FY 2013. In December 2012, the New England Fishery Management Council approved measures to modify the at-sea<PRTPAGE P="10137"/>monitoring program and eliminate the requirement for dockside monitoring for both sector and common pool vessels. As this measure has not yet been approved, and a sector may elect to retain dockside monitoring through its operations plan, NMFS is also approving dockside monitoring service providers.</P>
        <HD SOURCE="HD1">Approved Monitoring Service Providers</HD>
        <P>NMFS received complete applications from three service providers intending to provide dockside and/or at-sea monitoring services, and one service provider intending to provide only at-sea monitoring services. All four applicants were previously approved and provided dockside and/or at-sea monitoring services to sectors. The Regional Administrator has approved the following service providers as eligible to provide dockside monitoring and/or at-sea monitoring services in FY 2013:</P>
        <GPOTABLE CDEF="s50,10C,10C,r100,xs60,xs60,xls100" COLS="7" OPTS="L2,i1">
          <TTITLE>Table 1—Approved FY 2013 Providers</TTITLE>
          <BOXHD>
            <CHED H="1">Provider name</CHED>
            <CHED H="1">At-Sea monitoring</CHED>
            <CHED H="1">Dockside monitoring</CHED>
            <CHED H="1">Address</CHED>
            <CHED H="1">Phone</CHED>
            <CHED H="1">Fax</CHED>
            <CHED H="1">Web site</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">A.I.S., Inc</ENT>
            <ENT>X</ENT>
            <ENT>X</ENT>
            <ENT>89 North Water Street, New Bedford, MA 02747</ENT>
            <ENT>(508) 990-9054</ENT>
            <ENT>(508) 990-9055</ENT>
            <ENT>
              <E T="03">www.aisobservers.com</E>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="01">MRAG Americas</ENT>
            <ENT>X</ENT>
            <ENT>X</ENT>
            <ENT>65 Eastern Ave., Unit B2C, Essex, MA 01929</ENT>
            <ENT>(978) 768-3880</ENT>
            <ENT>(978) 768-3878</ENT>
            <ENT>
              <E T="03">www.mragamericas.com</E>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="01">Atlantic Catch Data Ltd.</ENT>
            <ENT>X</ENT>
            <ENT>X</ENT>
            <ENT>99 Wyse Road, Suite 815, Dartmouth, Nova Scotia, CANADA B3A 4S5</ENT>
            <ENT>(902) 422-4745</ENT>
            <ENT>(902) 422-9780</ENT>
            <ENT>
              <E T="03">www.atlanticcatchdata.ca</E>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="01">East West Technical Services, LLC</ENT>
            <ENT/>
            <ENT>X</ENT>
            <ENT>34 Batterson Drive, New Britain, CT 06053</ENT>
            <ENT>(860) 223-5165</ENT>
            <ENT>(860) 223-6005</ENT>
            <ENT>
              <E T="03">www.ewts.com</E>
            </ENT>
          </ROW>
        </GPOTABLE>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>16 U.S.C. 1801<E T="03">et seq.</E>
          </P>
        </AUTH>
        <SIG>
          <DATED>Dated: February 8, 2013.</DATED>
          <NAME>Kara Meckley,</NAME>
          <TITLE>Acting Deputy Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03371 Filed 2-12-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-XC238</RIN>
        <SUBJECT>Takes of Marine Mammals Incidental to Specified Activities; Marine Geophysical Survey on the Mid-Atlantic Ridge in the Atlantic Ocean, April 2013, Through June 2013</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>National Marine Fisheries Service, National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice; proposed incidental harassment authorization; request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>We have received an application from the Lamont-Doherty Earth Observatory (Observatory), in collaboration with the National Science Foundation (Foundation), for an Incidental Harassment Authorization to take marine mammals, by harassment, incidental to conducting a marine geophysical (seismic) survey on the Mid-Atlantic Ridge in the north Atlantic Ocean in international waters, from April 2013 through May 2013. Per the Marine Mammal Protection Act, we are requesting comments on our proposal to issue an Incidental Harassment Authorization to the Observatory and the Foundation to incidentally harass by Level B harassment only, 28 species of marine mammals during the 20-day seismic survey.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments and information must be received no later than March 15, 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.Cody@noaa.gov.</E>Please include 0648-XC238 in the subject line. We are not responsible for email comments sent to other addresses other than the one provided here. Comments sent via email to<E T="03">ITP.Cody@noaa.gov,</E>including all attachments, must not exceed a 10-megabyte file size.</P>

          <P>All submitted comments are a part of the public record and we will post to<E T="03">http://www.nmfs.noaa.gov/pr/permits/incidental.htm#applications</E>without change. All Personal Identifying Information (for example, name, address, etc.) voluntarily submitted by the commenter may be publicly accessible. Do not submit confidential business information or otherwise sensitive or protected information.</P>

          <P>To obtain an electronic copy of the application, write to the previously mentioned address, telephone the contact listed here (see<E T="02">FOR FURTHER INFORMATION CONTACT</E>), or visit the internet at:<E T="03">http://www.nmfs.noaa.gov/pr/permits/incidental.htm#applications.</E>
          </P>
          <P>The following associated documents are also available at the same internet address:</P>

          <P>The Foundation's draft environmental analysis titled, “Marine geophysical survey by the R/V MARCUS G.<E T="03"/>LANGSETH on the mid-Atlantic Ridge, April-May 2013,” for their federal action of funding the Observatory's seismic survey. LGL Ltd., Environmental Research Associates (LGL), prepared this analysis on behalf of the Foundation pursuant to Executive Order 12114: Environmental Effects Abroad of Major Federal Actions. The Foundation's environmental analysis evaluates the effects of the proposed seismic survey on the human environment including impacts to marine mammals. We will prepare a separate National Environmental Policy Act (NEPA: 42 U.S.C. 4321<E T="03">et seq.</E>) analysis to evaluate the environmental effects related to the scope of our federal action which is the proposed issuance of an incidental take authorization to the Observatory and the Foundation. We plan to incorporate the Foundation's environmental analysis, in whole or part, by reference, into our NEPA document as that analysis provides a detailed description of the planned survey and its anticipated effects on marine mammals. This notice and the referenced document present detailed information on the scope of our federal action under NEPA (i.e., potential impacts to marine mammals from<PRTPAGE P="10138"/>issuing the proposed IHA including measures for mitigation, and monitoring) and we will consider comments submitted in response to this notice as we prepare our NEPA analysis.</P>
          <P>The public can view documents cited in this notice by appointment, during regular business hours, at the aforementioned address.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Jeannine Cody, National Marine Fisheries Service, Office of Protected Resources, (301) 427-8401.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Background</HD>

        <P>Section 101(a)(5)(D) of the Marine Mammal Protection Act of 1972, as amended (MMPA; 16 U.S.C. 1361<E T="03">et seq.</E>) directs the Secretary of Commerce to authorize, upon request, the incidental, but not intentional, taking of small numbers of marine mammals of a species or population stock, by United States citizens who engage in a specified activity (other than commercial fishing) within a specified geographical region if, after notice of a proposed authorization to the public for review and public comment: (1) We make certain findings; and (2) the taking is limited to harassment.</P>
        <P>We shall grant authorization for the incidental taking of small numbers of marine mammals if we find that the taking will have a negligible impact on the species or stock(s), and will not have an unmitigable adverse impact on the availability of the species or stock(s) for subsistence uses (where relevant). The authorization must set forth the permissible methods of taking; other means of effecting the least practicable adverse impact on the species or stock and its habitat; and requirements pertaining to the mitigation, monitoring and reporting of such taking. We have defined “negligible impact” in 50 CFR 216.103 as “* * * an impact resulting from the specified activity that cannot be reasonably expected to, and is not reasonably likely to, adversely affect the species or stock through effects on annual rates of recruitment or survival.”</P>

        <P>Section 101(a)(5)(D) of the MMPA established an expedited process by which citizens of the United States can apply for an authorization to incidentally take small numbers of marine mammals by harassment. Section 101(a)(5)(D) of the MMPA establishes a 45-day time limit for our review of an application followed by a 30-day public notice and comment period on any proposed authorizations for the incidental harassment of small numbers of marine mammals. Within 45 days of the close of the public comment period, we must either issue or deny the authorization and must publish a notice in the<E T="04">Federal Register</E>within 30 days of our determination to issue or deny the authorization.</P>
        <P>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>We received an application from the Observatory on December 7, 2012, requesting that we issue an Incidental Harassment Authorization (Authorization) for the take, by Level B harassment only, of small numbers of marine mammals incidental to conducting a marine seismic survey in the north Atlantic Ocean in international waters from April 8, 2013, through May 13, 2013. We received a revised application from the Observatory on December 23, 2012 and January 17, 2013, which reflected updates to the mitigation safety zones, incidental take requests for marine mammals, and information on marine protected areas. Upon receipt of additional information, we determined the application complete and adequate on January 18, 2013.</P>
        <P>
          <E T="03">Project Purpose</E>—The Observatory plans to conduct a two-dimensional (2-D) seismic survey on the Mid-Atlantic Ridge in the north Atlantic Ocean. Specifically, the proposed survey would image the Rainbow massif to determine the characteristics of the magma body that supplies heat to the Rainbow hydrothermal field; determine the distribution of the different rock types that form the Rainbow massif; document large- and small-scale faults in the vicinity and investigate their role in controlling hydrothermal fluid discharge.</P>
        <P>
          <E T="03">Vessel</E>—The Observatory plans to use one source vessel, the R/V<E T="03">Marcus G.</E>LANGSETH (LANGSETH), a seismic airgun array, a single hydrophone streamer, and ocean bottom seismometers (seismometers) to conduct the seismic survey. In addition to the operations of the seismic airgun array and hydrophone streamer, and the seismometers, the Observatory intends to operate a multibeam echosounder and a sub-bottom profiler continuously throughout the proposed survey.</P>
        <P>
          <E T="03">Marine Mammal Take</E>—Acoustic stimuli (i.e., increased underwater sound) generated during the operation of the seismic airgun arrays, may have the potential to cause behavioral disturbance for marine mammals in the survey area. This is the principal means of marine mammal take associated with these activities and the Observatory requested an authorization to take 28 species of marine mammals by Level B harassment.</P>

        <P>In the Observatory's application, they did not request authorization to take marine mammals by Level A Harassment because their environmental analyses estimate that marine mammals would not be exposed to levels of sound likely to result in Level A harassment (we refer the reader to Appendix B of the Foundation's NEPA document titled, “2011 Final Programmatic Environmental Impact Statement/Overseas Environmental Impact Statement (2011 PEIS) for Marine Seismic Research funded by the National Science Foundation or Conducted by the U.S. Geological Survey,” (NSF/USGS, 2011) at<E T="03">http://www.nsf.gov/geo/oce/envcomp/usgs-nsf-marine-seismic-research/nsf-usgs-final-eis-oeis-with-appendices.pdf</E>for details). Consequently, the Observatory's request for take by Level A harassment is zero animals for any species.</P>
        <P>We do not expect that the use of the multibeam echosounder, the sub-bottom profiler, or the ocean bottom seismometer would result in the take of marine mammals and will discuss our reasoning later in this notice. Also, we do not expect take to result from a collision with the LANGSETH during seismic acquisition activities because the vessel moves at a relatively slow speed (approximately 8.3 kilometers per hour (km/h); 5.2 miles per hour (mph); 4.5 knots (kts)), for a relatively short period of time (approximately 20 operational days). It is likely that any marine mammal would be able to avoid the vessel during seismic acquisition activities. The Observatory has no recorded cases of a vessel strike with a marine mammal during the conduct of over eight years of seismic surveys covering over 160,934 km (86,897.4 nmi) of transect lines.</P>
        <HD SOURCE="HD1">Description of the Proposed Specified Activities</HD>
        <HD SOURCE="HD2">Survey Details</HD>

        <P>The Observatory's proposed seismic survey on the Mid-Atlantic Ridge in the north Atlantic Ocean would commence<PRTPAGE P="10139"/>on April 8, 2013, and end on May 13, 2013. The LANGSETH would depart from St. George's, Bermuda, on April 8, 2013, and transit to the proposed survey area in international waters approximately 300 km (186.4 miles (mi)) offshore of Pico and Faial Islands in the Azores. At the conclusion of the proposed survey activities, the LANGSETH would arrive in Ponta Delgada, Azores on May 13, 2012. The proposed study area would encompass an area on the Mid-Atlantic Ridge bounded by the following coordinates: Approximately 35.5 to 36.5° North by 33.5 to 34.5° West.</P>
        <P>Some minor deviation from these dates is possible, depending on logistics, weather conditions, and the need to repeat some lines if data quality is substandard. Therefore, we propose to issue an authorization that is effective from April 8, 2013, to June 24, 2013.</P>
        <P>Typically, 2-D surveys acquire data along single track lines with wide intervals; cover large areas; provide a coarse sampled subsurface image; and project less acoustic energy into the environment than other types of seismic surveys. During the survey, the LANGSETH would deploy an 36-airgun array as an energy source, an 8-kilometer (km)-long (3.7 mi-long) hydrophone streamer, and 46 seismometers. The seismometers are portable, self-contained passive receiver systems designed to sit on the seafloor and record seismic signals generated primarily by airguns and earthquakes.</P>
        <P>The LANGSETH would transect approximately 2,582 km (1.6 mi) of transect lines which are spaced 1 to 2 meters (m) (3.2 to 6.6 feet (ft)) apart from one another (see Figure 1 in the Observatory's application). As the LANGSETH tows the airgun array along the transect lines, the hydrophone streamer would receive the returning acoustic signals and transfer the data to the vessel's onboard processing system. The seismometers also record and store the returning signals for later analysis. The LANGSETH would retrieve the seismometers at the conclusion of the survey.</P>
        <P>The proposed study (e.g., equipment testing, startup, line changes, repeat coverage of any areas, and equipment recovery) would require approximately 20 days. At the proposed survey area, the LANGSETH would conduct seismic acquisition activities in a grid pattern using the seismometers as a receiver over a total of approximately 1,680 km (1,044 mi) of survey lines and would also conduct seismic acquisition activities in multichannel seismic (MCS) mode using the 8-km (3.7 mi) streamer as the receiver over a total of approximately 900 km (559 mi). The seismic lines are over water depths of approximately 900 to 3,000 m (2,952 ft to 1.9 mi). Approximately 2,565 km (1,594 mi) of the survey effort would occur in depths greater than 1,000 m (3,280 ft). The remaining effort (17 km; 10.5 mi) would occur in water depths of 100 to 1,000 m (328 to 3,280 ft).</P>
        <P>The proposed data acquisition would include approximately 480 hours of airgun operations (i.e., 20 days over 24 hours), with airgun discharges occurring on either a 3.25 minute interval with the seismometers or a 16-second interval for the MCS seismic portion. The Observatory would conduct all planned seismic activities with on-board assistance by the scientists who have proposed the study, Drs. J.P. Canales and R. Sohn of Woods Hole Oceanographic Institution and Dr. R. Dunn of the University of Hawaii. The vessel is self-contained and the crew would live aboard the vessel for the entire cruise.</P>
        <HD SOURCE="HD1">Vessel Specifications</HD>
        <HD SOURCE="HD2">R/V LANGSETH</HD>
        <P>The LANGSETH, owned by the Foundation and operated by the Observatory, is a seismic research vessel with a quiet propulsion system that avoids interference with the seismic signals emanating from the airgun array. The vessel is 71.5 m (235 ft) long; has a beam of 17.0 m (56 ft); a maximum draft of 5.9 m (19 ft); and a gross tonnage of 3,834 pounds. Its two 3,550 horsepower (hp) Bergen BRG-6 diesel engines drive two propellers. Each propeller has four blades and the shaft typically rotates at 750 revolutions per minute. The vessel also has an 800-hp bowthruster, which is not used during seismic acquisition. The cruising speed of the vessel outside of seismic operations is 18.5 km/h (11.5 mph; 10 kts).</P>
        <P>The LANGSETH would tow the 36-airgun array, as well as the hydrophone streamer during the first and last surveys, along predetermined lines. When the LANGSETH is towing the airgun array and the hydrophone streamer, the turning rate of the vessel is limited to five degrees per minute. Thus, the maneuverability of the vessel is limited during operations with the streamer.</P>
        <P>The vessel also has an observation tower from which protected species visual observers (observer) would watch for marine mammals before and during the proposed seismic acquisition operations. When stationed on the observation platform, the observer's eye level would be approximately 21.5 m (71 ft) above sea level providing the observer an unobstructed view around the entire vessel.</P>
        <HD SOURCE="HD1">Acoustic Source Specifications</HD>
        <HD SOURCE="HD2">Seismic Airguns</HD>
        <P>The LANGSETH would deploy an 36-airgun array, with a total volume of approximately 6,600 cubic inches (in<SU>3</SU>). The airguns are a mixture of Bolt 1500LL and Bolt 1900LLX airguns ranging in size from 40 to 360 in<SU>3</SU>, with a firing pressure of 1,900 pounds per square inch. The dominant frequency components range from zero to 188 Hertz (Hz). The array configuration consists of four identical linear strings, with 10 airguns on each string; the first and last airguns would be spaced 16 m (52 ft) apart. Of the 10 airguns, nine would fire simultaneously while the tenth airgun would serve as a spare in case of failure of one of the other airguns. The LANGSETH would distribute the array across an area of approximately 24 x 16 m (78.7 x 52.5 ft) and would tow the array approximately 30 m (98.4 ft) behind the vessel at a tow depth of 12 m (39.4 ft) (see Figure 2-11, page 2-25 in the Foundation's 2011 PEIS) (NSF/USGS, 2011). During firing, the airguns would emit a brief (approximately 0.1 s) pulse of sound; during the intervening periods of operations, the airguns are silent.</P>
        <HD SOURCE="HD2">Metrics Used in This Document</HD>
        <P>This section includes a brief explanation of the sound measurements frequently used in the discussions of acoustic effects in this document. Sound pressure is the sound force per unit area, and is usually measured in micropascals (µPa), where 1 pascal (Pa) is the pressure resulting from a force of one newton exerted over an area of one square meter. We express sound pressure level as the ratio of a measured sound pressure and a reference level. The commonly used reference pressure level in underwater acoustics is 1 µPa, and the units for sound pressure levels are dB re: 1 μPa. Sound pressure level (in decibels (dB)) = 20 log (pressure/reference pressure).</P>

        <P>Sound pressure level is an instantaneous measurement and can be expressed as the peak, the peak-peak (p-p), or the root mean square. Root mean square, which is the square root of the arithmetic average of the squared instantaneous pressure values, is typically used in discussions of the effects of sounds on vertebrates and all references to sound pressure level in this document refer to the root mean square unless otherwise noted. Sound<PRTPAGE P="10140"/>pressure level does not take the duration of a sound into account.</P>
        <HD SOURCE="HD2">Characteristics of the Airgun Pulses</HD>
        <P>Airguns function by venting high-pressure air into the water which creates an air bubble. The pressure signature of an individual airgun consists of a sharp rise and then fall in pressure, followed by several positive and negative pressure excursions caused by the oscillation of the resulting air bubble. The oscillation of the air bubble transmits sounds downward through the seafloor and the amount of sound transmitted in the near horizontal directions is reduced. However, the airgun array also emits sounds that travel horizontally toward non-target areas.</P>

        <P>The nominal source levels of the airgun array on the LANGSETH is 236 to 265 dB re: 1 µPa<E T="52">(p-p)</E>and the root mean square value for a given airgun pulse is typically 16 dB re: 1 μPa lower than the peak-to-peak value (Greene, 1997; McCauley<E T="03">et al.,</E>1998, 2000a). However, the difference between root mean square and peak or peak-to-peak values for a given pulse depends on the frequency content and duration of the pulse, among other factors.</P>
        <P>Accordingly, the Observatory predicted the received sound levels in relation to distance and direction from the 36-airgun array and the single Bolt 1900LL 40-in<SU>3</SU>airgun.</P>
        <P>Appendix H of the Foundation's PEIS (NSF/USGS, 2011) provides a detailed description of the modeling for marine seismic source arrays for species mitigation. These are the source levels applicable to downward propagation. The effective source levels for horizontal propagation are lower than those for downward propagation because of the directional nature of the sound from the airgun array. We refer the reader to the Observatory's authorization application and the Foundation's PEIS for additional information.</P>
        <HD SOURCE="HD2">Predicted Sound Levels for the Airguns</HD>
        <P>The Observatory has developed a model (Diebold<E T="03">et al.,</E>2010) that predicts received sound levels as a function of distance from the airguns for the 36-airgun array and the single 40-in<SU>3</SU>airgun. Their modeling approach uses ray tracing (i.e., a graphical representation of the effects of refracting sound waves) for the direct wave traveling from the array to the receiver and its associated source ghost (reflection at the air-water interface in the vicinity of the array), in a constant-velocity half-space (infinite homogeneous ocean layer, unbounded by a seafloor).</P>
        <P>Additionally, Tolstoy<E T="03">et al.,</E>(2009) reported results for propagation measurements of pulses from the LANGSETH<E T="03">'s</E>36-airgun array in shallow-water (approximately 50 m (164 ft)) and deep-water depths (approximately 1,600 m (5,249 ft)) in the Gulf of Mexico in 2007 and 2008. Results of the Gulf of Mexico calibration study (Tolstoy<E T="03">et al.,</E>2009) showed that radii around the airguns for various received levels varied with water depth and that sound propagation varied with array tow depth.</P>

        <P>The Observatory used the results from their algorithm for acoustic modeling (Diebold<E T="03">et al.,</E>2010) to calculate the exclusion zones for the 36-airgun array and the single airgun. These values designate mitigation zones used during power downs or shutdowns for marine mammals. The Observatory uses the mitigation zones to estimate take (described in greater detail in Chapter 7 of the application) for marine mammals.</P>
        <P>Comparison of the Tolstoy<E T="03">et al.</E>(2009) calibration study with the Observatory's model (Diebold<E T="03">et al.,</E>2010) for the LANGSETH<E T="03">'s</E>36-airgun array indicated that the Observatory's model represents the actual received levels, within the first few kilometers and the locations of the predicted exclusions zones. Thus, the comparison of results from the Tolstoy<E T="03">et al.</E>(2009) calibration study with the Observatory's model (Diebold<E T="03">et al.,</E>2010) at short ranges for the same array tow depth are in good agreement (see Figures 12 and 14 in Diebold<E T="03">et al.,</E>2010). As a consequence, isopleths falling within this domain can be predicted reliably by the Observatory's model.</P>

        <P>In contrast, for actual received levels at longer distances, the Observatory found that their model (Diebold<E T="03">et al.,</E>2010) was a more robust tool for estimating mitigation radii in deep water as it did not overestimate the received sound levels at a given distance. To estimate mitigation radii in intermediate water depths, the Observatory applied a correction factor (multiplication) of 1.5 to the deep water mitigation radii. We refer the reader to Appendix H of the Foundation's PEIS (NSF/USGS, 2011) for a detailed description of the modeling for marine seismic source arrays for species mitigation.</P>
        <P>Table 1 summarizes the predicted distances at which one would expect to receive three sound levels (160-, 180-, and 190-dB) from the 36-airgun array and a single airgun. To avoid the potential for injury or permanent physiological damage (Level A harassment), serious injury, or mortality we have concluded that cetaceans and pinnipeds should not be exposed to pulsed underwater noise at received levels exceeding 180 dB re: 1 μPa and 190 dB re: 1 μPa, respectively (NMFS, 1995, 2000). The 180-dB and 190-dB level shutdown criteria are applicable to cetaceans and pinnipeds, respectively, specified by us (NMFS, 1995, 2000). Thus the Observatory used these received sound levels to establish the mitigation zones. We also assume that marine mammals exposed to levels exceeding 160 dB re: 1 µPa may experience Level B harassment.</P>
        <GPOTABLE CDEF="s100,9,12,8,8" COLS="5" OPTS="L2,i1">

          <TTITLE>Table 1—Modeled Distances to Which Sound Levels Greater Than or Equal to 160 and 180<E T="01">d</E>B re: 1 µP<E T="01">a</E>Could Be Received During the Proposed Survey Over the Mid-Atlantic Ridge in the North Atlantic Ocean, During April Through June, 2013</TTITLE>
          <BOXHD>
            <CHED H="1">Source and volume<LI>(in<SU>3</SU>)</LI>
            </CHED>
            <CHED H="1">Tow depth (m)</CHED>
            <CHED H="1">Water depth (m)</CHED>
            <CHED H="1">Predicted RMS<LI>distances<SU>1</SU>(m)</LI>
            </CHED>
            <CHED H="2">160 dB</CHED>
            <CHED H="2">180 dB</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Single Bolt airgun (40 in<SU>3</SU>)</ENT>
            <ENT>12</ENT>
            <ENT>&gt; 1,000<LI>100 to 1,000</LI>
            </ENT>
            <ENT>388<LI>582</LI>
            </ENT>
            <ENT>100<LI>100</LI>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="01">36-Airgun Array (6,600 in<SU>3</SU>)</ENT>
            <ENT>12</ENT>
            <ENT>&gt; 1,000<LI>100 to 1,000</LI>
            </ENT>
            <ENT>6,908<LI>10,362</LI>
            </ENT>
            <ENT>1,116<LI>1,674</LI>
            </ENT>
          </ROW>
          <TNOTE>
            <SU>1</SU>Diebold, J.B., M. Tolstoy, L. Doermann, S.L. Nooner, S.C. Webb, and T.J. Crone. 2010. R/V Marcus G. Langseth seismic source: Modeling and calibration. Geochem. Geophys. Geosyst.</TNOTE>
        </GPOTABLE>
        <PRTPAGE P="10141"/>
        <HD SOURCE="HD2">Ocean Bottom Seismometers</HD>
        <P>The Observatory proposes to place 46 seismometers on the sea floor prior to the initiation of the seismic survey. Each seismometer is approximately 0.9 m (2.9 ft) high with a maximum diameter of 97 centimeters (cm) (3.1 ft). An anchor, made of a rolled steel bar grate which measures approximately 7 by 91 by 91.5 cm (3 by 36 by 36 inches) and weighs 45 kilograms (99 pounds) would anchor the seismometer to the seafloor.</P>

        <P>After the Observatory completes the proposed seismic survey, an acoustic signal would trigger the release of each of the 46 seismometers from the ocean floor. The LANGSETH<E T="03">'s</E>acoustic release transponder, located on the vessel, communicates with the seismometer at a frequency of 9 to13 kilohertz (kHz). The maximum source level of the release signal is 242 dB re: 1 μPa with an 8-millisecond pulse length. The received signal activates the seismometer's double burn-wire release assembly which then releases the seismometer from the anchor. The seismometer then floats to the ocean surface for retrieval by the LANGSETH. The steel grate anchors from each of the seismometers would remain on the seafloor.</P>
        <P>The LANGSETH crew would deploy the seismometers one-by-one from the stern of the vessel while onboard protected species observers will alert them to the presence of marine mammals and recommend ceasing deploying or recovering the seismometers to avoid potential entanglement with marine mammal. Thus, entanglement of marine mammals is highly unlikely.</P>
        <P>Although placement of the seismometers is dispersed over approximately1,500 square km (km<SU>2</SU>) (579 square mi (mi<SU>2</SU>) of seafloor habitat and may disturb benthic invertebrates, we and the Observatory expect these impacts to be localized and short-term because of natural sedimentation processes and the natural sinking of the anchors from their own weight resulting in no long-term habitat impacts. Also, the deep water habitat potentially affected by the placement of the seismometers is not designated as a marine protected area.</P>
        <HD SOURCE="HD2">Multibeam Echosounder</HD>
        <P>The LANGSETH would operate a Kongsberg EM 122 multibeam echosounder concurrently during airgun operations to map characteristics of the ocean floor. The hull-mounted echosounder emits brief pulses of sound (also called a ping) (10.5 to 13.0 kHz) in a fan-shaped beam that extends downward and to the sides of the ship. The transmitting beamwidth is 1 or 2° fore-aft and 150° athwartship and the maximum source level is 242 dB re: 1 μPa.</P>
        <P>For deep-water operations, each ping consists of eight (in water greater than 1,000 m; 3,280 ft) or four (less than 1,000 m; 3,280 ft) successive, fan-shaped transmissions, from two to 15 milliseconds (ms) in duration and each ensonifying a sector that extends 1° fore-aft. Continuous wave pulses increase from 2 to 15 ms long in water depths up to 2,600 m (8,530 ft). The echosounder uses frequency-modulated chirp pulses up to 100-ms long in water greater than 2,600 m (8,530 ft). The successive transmissions span an overall cross-track angular extent of about 150°, with 2-ms gaps between the pulses for successive sectors.</P>
        <HD SOURCE="HD2">Sub-Bottom Profiler</HD>
        <P>The LANGSETH would also operate a Knudsen Chirp 3260 sub-bottom profiler concurrently during airgun and echosounder operations to provide information about the sedimentary features and bottom topography. The profiler is capable of reaching depths of 10,000 m (6.2 mi). The dominant frequency component is 3.5 kHz and a hull-mounted transducer on the vessel directs the beam downward in a 27º cone. The power output is 10 kilowatts (kW), but the actual maximum radiated power is three kilowatts or 222 dB re: 1 µPa. The ping duration is up to 64 ms with a pulse interval of one second, but a common mode of operation is to broadcast five pulses at 1-s intervals followed by a 5-s pause.</P>
        <P>We expect that acoustic stimuli resulting from the proposed operation of the single airgun or the 36-airgun array has the potential to harass marine mammals, incidental to the conduct of the proposed seismic survey. We assume that during simultaneous operations of the airgun array and the other sources, any marine mammals close enough to be affected by the echosounder and sub-bottom profiler would already be affected by the airguns. We also expect these disturbances to result in a temporary modification in behavior and/or low-level physiological effects (Level B harassment) of small numbers of certain species of marine mammals.</P>
        <P>We do not expect that the movement of the LANGSETH, during the conduct of the seismic survey, has the potential to harass marine mammals because of the relatively slow operation speed of the vessel (4.6 kts; 8.5 km/hr; 5.3 mph) during seismic acquisition.</P>
        <HD SOURCE="HD1">Description of the Marine Mammals in the Area of the Proposed Specified Activity</HD>

        <P>Twenty-eight marine mammal species under our jurisdiction may occur in the proposed survey area, including seven mysticetes (baleen whales), and 21 odontocetes (toothed cetaceans) during April through May, 2013. Six of these species are listed as endangered under the Endangered Species Act of 1973 (ESA; 16 U.S.C. 1531<E T="03">et seq.</E>), including: the blue (<E T="03">Balaenoptera musculus</E>), fin (<E T="03">Balaenoptera physalus</E>), humpback (<E T="03">Megaptera novaeangliae</E>), north Atlantic right (<E T="03">Eubalaena glacialis</E>), sei (<E T="03">Balaenoptera borealis</E>), and sperm (<E T="03">Physeter macrocephalus</E>) whales.</P>

        <P>Based on the best available data, the Observatory does not expect to encounter the following species because of these species rare and/or extralimital occurrence in the survey area. They include the: Atlantic white-sided dolphin (<E T="03">Lagenorhynchus acutus</E>), white-beaked dolphin (<E T="03">Lagenorhynchus albirostris</E>), harbor porpoise (<E T="03">Phocoena phocoena</E>), Clymene dolphin (<E T="03">Stenella clymene</E>), Fraser's dolphin (<E T="03">Lagenodelphis hosei</E>), spinner dolphin (<E T="03">Stenella longirostris</E>), melon-headed whale (<E T="03">Peponocephala electra</E>), Atlantic humpback dolphin (<E T="03">Souza teuszii</E>), long-beaked common dolphin (<E T="03">Delphinus capensis</E>), and any pinniped species. Accordingly, we did not consider these species in greater detail and the proposed authorization would only address requested take authorizations for the 28 species.</P>

        <P>Of these 28 species, the most common marine mammals in the survey area would be the: short-beaked common dolphin (<E T="03">Delphinus delphis</E>), striped dolphin (<E T="03">Stenella coeruleoalba</E>), and short-finned pilot whale (<E T="03">Globicephala macrorhynchus</E>).</P>

        <P>Table 2 presents information on the abundance, distribution, and conservation status of the marine mammals that may occur in the proposed survey area during April through June, 2013.<PRTPAGE P="10142"/>
        </P>
        <GPOTABLE CDEF="s75,r50,xls20,12.2" COLS="4" OPTS="L2,i1">
          <TTITLE>Table 2—Abundance Estimates, Mean Density, and ESA Status of Marine Mammals That May Occur in the Proposed Seismic Survey Area Over the Mid-Atlantic Ridge in the North Atlantic Ocean, During April Through June, 2013.</TTITLE>
          <TDESC>[See text and Table 2 in the Observatory's application for further details]</TDESC>
          <BOXHD>
            <CHED H="1">Species</CHED>
            <CHED H="1">Abundance in the<LI>N. Atlantic Ocean</LI>
            </CHED>
            <CHED H="1">ESA<SU>a</SU>
            </CHED>
            <CHED H="1">Estimated<LI>Density</LI>
              <LI>(#/100 km<SU>2</SU>)<SU>b</SU>
              </LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="22">Mysticetes:</ENT>
          </ROW>
          <ROW>
            <ENT I="03">North Atlantic right whale</ENT>
            <ENT>396<SU>1</SU>
            </ENT>
            <ENT>EN</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Humpback whale</ENT>
            <ENT>11,570<SU>2</SU>
            </ENT>
            <ENT>EN</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Minke whale</ENT>
            <ENT>121,000<SU>3</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Bryde's whale</ENT>
            <ENT>Not available</ENT>
            <ENT>NL</ENT>
            <ENT>0.19</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Sei whale</ENT>
            <ENT>12-13,000<SU>4</SU>
            </ENT>
            <ENT>EN</ENT>
            <ENT>0.19</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Fin whale</ENT>
            <ENT>24,887<SU>5</SU>
            </ENT>
            <ENT>EN</ENT>
            <ENT>4.46</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Blue whale</ENT>
            <ENT>937<SU>6</SU>
            </ENT>
            <ENT>EN</ENT>
            <ENT>1.49</ENT>
          </ROW>
          <ROW>
            <ENT I="22">Odontocetes:</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Sperm whale</ENT>
            <ENT>13,190<SU>7</SU>
            </ENT>
            <ENT>EN</ENT>
            <ENT>3.71</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Pygmy sperm whale</ENT>
            <ENT>395<SU>1</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Dwarf sperm whale</ENT>
            <ENT>395<SU>1</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Cuvier's beaked whale</ENT>
            <ENT>3,513<SU>1,8</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">
              <E T="03">Mesoplodon spp.</E>
            </ENT>
            <ENT>3,513<SU>1,8</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>7.04</ENT>
          </ROW>
          <ROW>
            <ENT I="03">True's beaked whale</ENT>
            <ENT>3,513<SU>1,8</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>7.04</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Gervais beaked whale</ENT>
            <ENT>3,513<SU>1,8</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>7.04</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Sowerby's beaked whale</ENT>
            <ENT>3,513<SU>1,8</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>7.04</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Blainville's beaked whale</ENT>
            <ENT>3,513<SU>1,8</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>7.04</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Northern bottlenose whale</ENT>
            <ENT>40,000<SU>9</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Rough-toothed dolphin</ENT>
            <ENT>Not available</ENT>
            <ENT>NL</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Common bottlenose dolphin</ENT>
            <ENT>81,588<SU>10</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>8.35</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Pantropical spotted dolphin</ENT>
            <ENT>4,439<SU>1</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Atlantic spotted dolphin</ENT>
            <ENT>50,978<SU>1</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>20.03</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Striped dolphin</ENT>
            <ENT>94,462<SU>1</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>185.50</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Short-beaked common dolphin</ENT>
            <ENT>120,741<SU>4</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>379.52</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Risso's dolphin</ENT>
            <ENT>20,479<SU>4</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>3.83</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Pygmy killer whale</ENT>
            <ENT>Not available</ENT>
            <ENT>NL</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">False killer whale</ENT>
            <ENT>Not available</ENT>
            <ENT>NL</ENT>
            <ENT>1.17</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Killer whale</ENT>
            <ENT>Not available</ENT>
            <ENT>NL</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Long-finned pilot whale</ENT>
            <ENT>12,619,<SU>1</SU>780,000<SU>11</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Short-finned pilot whale</ENT>
            <ENT>24,674,<SU>1</SU>780,000<SU>11</SU>
            </ENT>
            <ENT>NL</ENT>
            <ENT>120.96</ENT>
          </ROW>
          <TNOTE>
            <SU>a</SU>ESA status codes: NL—not listed under the ESA; EN—Endangered; T—Threatened</TNOTE>
          <TNOTE>
            <SU>b</SU>The Observatory used Waring<E T="03">et al.</E>, 2008 to calculate density from sightings, effort, mean group sizes, and values for f(0) for the southern part of the survey area.</TNOTE>
          <TNOTE>

            <SU>1</SU>Western North Atlantic, in U.S. and southern Canadian waters (Waring<E T="03">et al.</E>, 2012)</TNOTE>
          <TNOTE>
            <SU>2</SU>Likely negatively biased (Stevick<E T="03">et al.</E>, 2003)</TNOTE>
          <TNOTE>
            <SU>3</SU>Central and Northeast Atlantic (IWC, 2012)</TNOTE>
          <TNOTE>
            <SU>4</SU>North Atlantic (Cattanach<E T="03">et al.</E>, 1993)</TNOTE>
          <TNOTE>
            <SU>5</SU>Central and Northeast Atlantic (Víkingsson<E T="03">et al.</E>, 2009)</TNOTE>
          <TNOTE>
            <SU>6</SU>Central and Northeast Atlantic (Pike<E T="03">et al.</E>, 2009).</TNOTE>
          <TNOTE>
            <SU>7</SU>For the northeast Atlantic, Faroes-Iceland, and the U.S. east coast (Whitehead, 2002).</TNOTE>
          <TNOTE>
            <SU>8</SU>
            <E T="03">Ziphius</E>and<E T="03">Mesoplodon spp.</E>combined</TNOTE>
          <TNOTE>
            <SU>9</SU>Eastern North Atlantic (NAMMCO, 1995)</TNOTE>
          <TNOTE>
            <SU>10</SU>Offshore, Western North Atlantic (Waring<E T="03">et al.</E>, 2012)</TNOTE>
          <TNOTE>
            <SU>11</SU>
            <E T="03">Globicephala sp.</E>combined, Central and Eastern North Atlantic (IWC, 2012)</TNOTE>
        </GPOTABLE>
        <P>Refer to Section 4 of the Observatory's application and Sections 3.6.3.4 and 3.7.3.4 of the 2011 PEIS (NSF/USGS, 2011) for detailed information regarding the abundance and distribution, population status, and life history and behavior of these species and their occurrence in the proposed project area. We have reviewed these data and determined them to be the best available scientific information for the purposes of the proposed incidental harassment authorization.</P>
        <HD SOURCE="HD1">Potential Effects on Marine Mammals</HD>

        <P>Acoustic stimuli generated by the operation of the airguns, which introduce sound into the marine environment, may have the potential to cause Level B harassment of marine mammals in the proposed survey area. The effects of sounds from airgun operations might include one or more of the following: tolerance, masking of natural sounds, behavioral disturbance, temporary or permanent impairment, or non-auditory physical or physiological effects (Richardson<E T="03">et al.</E>, 1995; Gordon<E T="03">et al.</E>, 2004; Nowacek<E T="03">et al.</E>, 2007; Southall<E T="03">et al.</E>, 2007).</P>

        <P>Permanent hearing impairment, in the unlikely event that it occurred, would constitute injury, but temporary threshold shift is not an injury (Southall<E T="03">et al.,</E>2007). Although we cannot exclude the possibility entirely, it is unlikely that the proposed project would result in any cases of temporary or permanent hearing impairment, or any significant non-auditory physical or physiological effects. Based on the available data and studies described here, we expect some behavioral disturbance, but we expect the disturbance to be localized. We refer the reader to a more comprehensive review of these issues in the 2011 PEIS (NSF/USGS, 2011).</P>
        <HD SOURCE="HD2">Tolerance</HD>

        <P>Studies on marine mammals' tolerance to sound in the natural environment are relatively rare. Richardson<E T="03">et al.</E>(1995) defined<PRTPAGE P="10143"/>tolerance as the occurrence of marine mammals in areas where they are exposed to human activities or manmade noise. In many cases, tolerance develops by the animal habituating to the stimulus (i.e., the gradual waning of responses to a repeated or ongoing stimulus) (Richardson,<E T="03">et al.,</E>1995; Thorpe, 1963), but because of ecological or physiological requirements, many marine animals may need to remain in areas where they are exposed to chronic stimuli (Richardson,<E T="03">et al.,</E>1995).</P>

        <P>Numerous studies have shown that pulsed sounds from airguns are often readily detectable in the water at distances of many kilometers. Several studies have shown that marine mammals at distances more than a few kilometers from operating seismic vessels often show no apparent response. That is often true even in cases when the pulsed sounds must be readily audible to the animals based on measured received levels and the hearing sensitivity of the marine mammal group. Although various baleen whales and toothed whales, and (less frequently) pinnipeds have been shown to react behaviorally to airgun pulses under some conditions, at other times marine mammals of all three types have shown no overt reactions (Stone, 2003; Stone and Tasker, 2006; Moulton<E T="03">et al.</E>2005, 2006a; Weir 2008a for sperm whales), (MacLean and Koski, 2005; Bain and Williams, 2006 for Dall's porpoises). The relative responsiveness of baleen and toothed whales are quite variable.</P>
        <HD SOURCE="HD2">Masking</HD>

        <P>The term masking refers to the inability of a subject to recognize the occurrence of an acoustic stimulus as a result of the interference of another acoustic stimulus (Clark<E T="03">et al.,</E>2009). Introduced underwater sound may, through masking, reduce the effective communication distance of a marine mammal species if the frequency of the source is close to that used as a signal by the marine mammal, and if the anthropogenic sound is present for a significant fraction of the time (Richardson<E T="03">et al.,</E>1995).</P>

        <P>We expect that the masking effects of pulsed sounds (even from large arrays of airguns) on marine mammal calls and other natural sounds will be limited, although there are very few specific data on this. Because of the intermittent nature and low duty cycle of seismic airgun pulses, animals can emit and receive sounds in the relatively quiet intervals between pulses. However, in some situations, reverberation occurs for much or the entire interval between pulses (e.g., Simard<E T="03">et al.,</E>2005; Clark and Gagnon, 2006) which could mask calls. We understand that some baleen and toothed whales continue calling in the presence of seismic pulses, and that some researchers have heard these calls between the seismic pulses (e.g., Richardson<E T="03">et al.,</E>1986; McDonald<E T="03">et al.,</E>1995; Greene<E T="03">et al.,</E>1999; Nieukirk<E T="03">et al.,</E>2004; Smultea<E T="03">et al.,</E>2004; Holst<E T="03">et al.,</E>2005a,b, 2006; and Dunn and Hernandez, 2009). However, Clark and Gagnon (2006) reported that fin whales in the northeast Pacific Ocean went silent for an extended period starting soon after the onset of a seismic survey in the area. Similarly, there has been one report that sperm whales ceased calling when exposed to pulses from a very distant seismic ship (Bowles<E T="03">et al.,</E>1994). However, more recent studies have found that they continued calling in the presence of seismic pulses (Madsen<E T="03">et al.,</E>2002; Tyack<E T="03">et al.,</E>2003; Smultea<E T="03">et al.,</E>2004; Holst<E T="03">et al.,</E>2006; and Jochens<E T="03">et al.,</E>2008). Several studies have reported hearing dolphins and porpoises calling while airguns were operating (e.g., Gordon<E T="03">et al.,</E>2004; Smultea<E T="03">et al.,</E>2004; Holst<E T="03">et al.,</E>2005a, b; and Potter<E T="03">et al.,</E>2007). The sounds important to small odontocetes are predominantly at much higher frequencies than are the dominant components of airgun sounds, thus limiting the potential for masking.</P>

        <P>Marine mammals are thought to be able to compensate for masking by adjusting their acoustic behavior through shifting call frequencies, increasing call volume, and increasing vocalization rates. For example, blue whales are found to increase call rates when exposed to noise from seismic surveys in the St. Lawrence Estuary (Dilorio and Clark, 2009). The North Atlantic right whales exposed to high shipping noise increased call frequency (Parks<E T="03">et al.,</E>2007), while some humpback whales respond to low-frequency active sonar playbacks by increasing song length (Miller<E T="03">et al.,</E>2000).</P>
        <P>In general, we expect that the masking effects of seismic pulses would be minor, given the normally intermittent nature of seismic pulses.</P>
        <HD SOURCE="HD2">Behavioral Disturbance</HD>

        <P>Marine mammals may behaviorally react to sound when exposed to anthropogenic noise. Disturbance includes a variety of effects, including subtle to conspicuous changes in behavior, movement, and displacement. Reactions to sound, if any, depend on species, state of maturity, experience, current activity, reproductive state, time of day, and many other factors (Richardson<E T="03">et al.,</E>1995; Wartzok<E T="03">et al.,</E>2004; Southall<E T="03">et al.,</E>2007; Weilgart, 2007). These behavioral reactions are often shown as: Changing durations of surfacing and dives, number of blows per surfacing, or moving direction and/or speed; reduced/increased vocal activities; changing/cessation of certain behavioral activities (such as socializing or feeding); visible startle response or aggressive behavior (such as tail/fluke slapping or jaw clapping); avoidance of areas where noise sources are located; and/or flight responses (e.g., pinnipeds flushing into the water from haul-outs or rookeries). If a marine mammal does react briefly to an underwater sound by changing its behavior or moving a small distance, the impacts of the change are unlikely to be significant to the individual, let alone the stock or population. However, if a sound source displaces marine mammals from an important feeding or breeding area for a prolonged period, impacts on individuals and populations could be significant (e.g., Lusseau and Bejder, 2007; Weilgart, 2007).</P>
        <P>The biological significance of many of these behavioral disturbances is difficult to predict, especially if the detected disturbances appear minor. However, the consequences of behavioral modification could be expected to be biologically significant if the change affects growth, survival, and/or reproduction. Some of these significant behavioral modifications include:</P>
        <P>• Change in diving/surfacing patterns (such as those thought to be causing beaked whale stranding due to exposure to military mid-frequency tactical sonar);</P>
        <P>• Habitat abandonment due to loss of desirable acoustic environment; and</P>
        <P>• Cessation of feeding or social interaction.</P>

        <P>The onset of behavioral disturbance from anthropogenic noise depends on both external factors (characteristics of noise sources and their paths) and the receiving animals (hearing, motivation, experience, demography) and is also difficult to predict (Richardson<E T="03">et al.,</E>1995; Southall<E T="03">et al.,</E>2007). Given the many uncertainties in predicting the quantity and types of impacts of noise on marine mammals, it is common practice to estimate how many mammals would be present within a particular distance of industrial activities and/or exposed to a particular level of industrial sound. In most cases, this approach likely overestimates the numbers of marine mammals that would be affected in some biologically-important manner.</P>

        <P>The sound criteria used to estimate how many marine mammals might be<PRTPAGE P="10144"/>disturbed to some biologically-important degree by a seismic program are based primarily on behavioral observations of a few species. Scientists have conducted detailed studies on humpback, gray, bowhead (<E T="03">Balaena mysticetus</E>), and sperm whales. There are less detailed data available for some other species of baleen whales and small toothed whales, but for many species there are no data on responses to marine seismic surveys.</P>
        <P>
          <E T="03">Baleen Whales</E>—Baleen whales generally tend to avoid operating airguns, but avoidance radii are quite variable (reviewed in Richardson<E T="03">et al.,</E>1995). Whales are often reported to show no overt reactions to pulses from large arrays of airguns at distances beyond a few kilometers, even though the airgun pulses remain well above ambient noise levels out to much longer distances. However, baleen whales exposed to strong noise pulses from airguns often react by deviating from their normal migration route and/or interrupting their feeding and moving away from the area. In the cases of migrating gray and bowhead whales, the observed changes in behavior appeared to be of little or no biological consequence to the animals (Richardson<E T="03">et al.,</E>1995). They avoided the sound source by displacing their migration route to varying degrees, but within the natural boundaries of the migration corridors.</P>

        <P>Studies of gray, bowhead, and humpback whales have shown that seismic pulses with received levels of 160 to 170 dB re: 1 µPa seem to cause obvious avoidance behavior in a substantial fraction of the animals exposed (Malme<E T="03">et al.,</E>1986, 1988; Richardson<E T="03">et al.,</E>1995). In many areas, seismic pulses from large arrays of airguns diminish to those levels at distances ranging from four to 15 km (2.5 to 9.3 mi) from the source. A substantial proportion of the baleen whales within those distances may show avoidance or other strong behavioral reactions to the airgun array. Subtle behavioral changes sometimes become evident at somewhat lower received levels, and studies summarized in Appendix B(5) of the Foundation's Assessment have shown that some species of baleen whales, notably bowhead and humpback whales, at times show strong avoidance at received levels lower than 160-170 dB re: 1 µPa.</P>

        <P>Researchers have studied the responses of humpback whales to seismic surveys during migration, feeding during the summer months, breeding while offshore from Angola, and wintering offshore from Brazil. McCauley<E T="03">et al.</E>(1998, 2000a) studied the responses of humpback whales off western Australia to a full-scale seismic survey with a 16-airgun array (2,678-in<SU>3</SU>) and to a single, 20-in<SU>3</SU>airgun with source level of 227 dB re: 1 µPa (p-p). In the 1998 study, the researchers documented that avoidance reactions began at five to eight km (3.1 to 4.9 mi) from the array, and that those reactions kept most pods approximately three to four km (1.9 to 2.5 mi) from the operating seismic boat. In the 2000 study, McCauley<E T="03">et al.</E>noted localized displacement during migration of four to five km (2.5 to 3.1 mi) by traveling pods and seven to 12 km (4.3 to 7.5 mi) by more sensitive resting pods of cow-calf pairs. Avoidance distances with respect to the single airgun were smaller but consistent with the results from the full array in terms of the received sound levels. The mean received level for initial avoidance of an approaching airgun was 140 dB re: 1 µPa for humpback pods containing females, and at the mean closest point of approach distance, the received level was 143 dB re: 1 µPa. The initial avoidance response generally occurred at distances of five to eight km (3.1 to 4.9 mi) from the airgun array and two km (1.2 mi) from the single airgun. However, some individual humpback whales, especially males, approached within distances of 100 to 400 m (328 to 1,312 ft), where the maximum received level was 179 dB re: 1 µPa.</P>
        <P>Data collected by observers during several seismic surveys in the northwest Atlantic Ocean showed that sighting rates of humpback whales were significantly greater during non-seismic periods compared with periods when a full array was operating (Moulton and Holst, 2010). In addition, humpback whales were more likely to swim away and less likely to swim towards a vessel during seismic versus non-seismic periods (Moulton and Holst, 2010).</P>

        <P>Humpback whales on their summer feeding grounds in southeast Alaska did not exhibit persistent avoidance when exposed to seismic pulses from a 1.64-L (100-in<SU>3</SU>) airgun (Malme<E T="03">et al.,</E>1985). Some humpbacks seemed “startled” at received levels of 150 to 169 dB re: 1 μPa. Malme<E T="03">et al.</E>(1985) concluded that there was no clear evidence of avoidance, despite the possibility of subtle effects, at received levels up to 172 re: 1 μPa. However, Moulton and Holst (2010) reported that humpback whales monitored during seismic surveys in the northwest Atlantic had lower sighting rates and were most often seen swimming away from the vessel during seismic periods compared with periods when airguns were silent.</P>

        <P>Other studies have suggested that south Atlantic humpback whales wintering off Brazil may be displaced or even strand upon exposure to seismic surveys (Engel<E T="03">et al.,</E>2004). Although, the evidence for this was circumstantial and subject to alternative explanations (IAGC, 2004). Also, the evidence was not consistent with subsequent results from the same area of Brazil (Parente<E T="03">et al.,</E>2006), or with direct studies of humpbacks exposed to seismic surveys in other areas and seasons. After allowance for data from subsequent years, there was “no observable direct correlation” between strandings and seismic surveys (IWC, 2007: 236).</P>

        <P>A few studies have documented reactions of migrating and feeding (but not wintering) gray whales to seismic surveys. Malme<E T="03">et al.</E>(1986, 1988) studied the responses of feeding eastern Pacific gray whales to pulses from a single 100-in<SU>3</SU>airgun off St. Lawrence Island in the northern Bering Sea. They estimated, based on small sample sizes, that 50 percent of feeding gray whales stopped feeding at an average received pressure level of 173 dB re: 1 μPa on an (approximate) root mean square basis, and that 10 percent of feeding whales interrupted feeding at received levels of 163 dB re: 1 µPa. Those findings were generally consistent with the results of experiments conducted on larger numbers of gray whales that were migrating along the California coast (Malme<E T="03">et al.,</E>1984; Malme and Miles, 1985), and western Pacific gray whales feeding off Sakhalin Island, Russia (Wursig<E T="03">et al.,</E>1999; Gailey<E T="03">et al.,</E>2007; Johnson<E T="03">et al.,</E>2007; Yazvenko<E T="03">et al.,</E>2007a,b), along with data on gray whales off British Columbia (Bain and Williams, 2006).</P>
        <P>Observers have seen various species of<E T="03">Balaenoptera</E>(blue, sei, fin, and minke whales) in areas ensonified by airgun pulses (Stone, 2003; MacLean and Haley, 2004; Stone and Tasker, 2006), and have localized calls from blue and fin whales in areas with airgun operations (e.g., McDonald<E T="03">et al.,</E>1995; Dunn and Hernandez, 2009; Castellote<E T="03">et al.,</E>2010). Sightings by observers on seismic vessels off the United Kingdom from 1997 to 2000 suggest that, during times of good sightability, sighting rates for mysticetes (mainly fin and sei whales) were similar when large arrays of airguns were shooting vs. silent (Stone, 2003; Stone and Tasker, 2006). However, these whales tended to exhibit localized avoidance, remaining significantly further (on average) from the airgun array during seismic operations compared with non-seismic periods (Stone and Tasker, 2006). Castellote<E T="03">et al.</E>(2010) observed<PRTPAGE P="10145"/>localized avoidance by fin whales during seismic airgun events in the western Mediterranean Sea and adjacent Atlantic waters from 2006-2009 and reported that singing fin whales moved away from an operating airgun array for a time period that extended beyond the duration of the airgun activity.</P>
        <P>Ship-based monitoring studies of baleen whales (including blue, fin, sei, minke, and whales) in the northwest Atlantic found that overall, this group had lower sighting rates during seismic versus non-seismic periods (Moulton and Holst, 2010). Baleen whales as a group were also seen significantly farther from the vessel during seismic compared with non-seismic periods, and they were more often seen to be swimming away from the operating seismic vessel (Moulton and Holst, 2010). Blue and minke whales were initially sighted significantly farther from the vessel during seismic operations compared to non-seismic periods; the same trend was observed for fin whales (Moulton and Holst, 2010). Minke whales were most often observed to be swimming away from the vessel when seismic operations were underway (Moulton and Holst, 2010).</P>

        <P>Data on short-term reactions by cetaceans to impulsive noises are not necessarily indicative of long-term or biologically significant effects. It is not known whether impulsive sounds affect reproductive rate or distribution and habitat use in subsequent days or years. However, gray whales have continued to migrate annually along the west coast of North America with substantial increases in the population over recent years, despite intermittent seismic exploration (and much ship traffic) in that area for decades (Appendix A in Malme<E T="03">et al.,</E>1984; Richardson<E T="03">et al.,</E>1995; Allen and Angliss, 2011). The western Pacific gray whale population did not appear affected by a seismic survey in its feeding ground during a previous year (Johnson<E T="03">et al.,</E>2007). Similarly, bowhead whales have continued to travel to the eastern Beaufort Sea each summer, and their numbers have increased notably, despite seismic exploration in their summer and autumn range for many years (Richardson<E T="03">et al.,</E>1987; Allen and Angliss, 2011). The history of coexistence between seismic surveys and baleen whales suggests that brief exposures to sound pulses from any single seismic survey are unlikely to result in prolonged effects.</P>
        <P>
          <E T="03">Toothed Whales</E>—There is little systematic information available about reactions of toothed whales to noise pulses. There are few studies on toothed whales similar to the more extensive baleen whale/seismic pulse work summarized earlier in this notice. However, there are recent systematic studies on sperm whales (e.g., Gordon<E T="03">et al.,</E>2006; Madsen<E T="03">et al.,</E>2006; Winsor and Mate, 2006; Jochens<E T="03">et al.,</E>2008; Miller<E T="03">et al.,</E>2009). There is an increasing amount of information about responses of various odontocetes to seismic surveys based on monitoring studies (<E T="03">e.g.,</E>Stone, 2003; Smultea<E T="03">et al.,</E>2004; Moulton and Miller, 2005; Bain and Williams, 2006; Holst<E T="03">et al.,</E>2006; Stone and Tasker, 2006; Potter<E T="03">et al.,</E>2007; Hauser<E T="03">et al.,</E>2008; Holst and Smultea, 2008; Weir, 2008; Barkaszi<E T="03">et al.,</E>2009; Richardson<E T="03">et al.,</E>2009; Moulton and Holst, 2010).</P>

        <P>Seismic operators and protected species observers (observers) on seismic vessels regularly see dolphins and other small toothed whales near operating airgun arrays, but in general there is a tendency for most delphinids to show some avoidance of operating seismic vessels (e.g., Goold, 1996a,b,c; Calambokidis and Osmek, 1998; Stone, 2003; Moulton and Miller, 2005; Holst<E T="03">et al.,</E>2006; Stone and Tasker, 2006; Weir, 2008; Richardson<E T="03">et al.,</E>2009; Barkaszi<E T="03">et al.,</E>2009; Moulton and Holst, 2010). Some dolphins seem to be attracted to the seismic vessel and floats, and some ride the bow wave of the seismic vessel even when large arrays of airguns are firing (e.g., Moulton and Miller, 2005). Nonetheless, small toothed whales more often tend to head away, or to maintain a somewhat greater distance from the vessel, when a large array of airguns is operating than when it is silent (e.g., Stone and Tasker, 2006; Weir, 2008, Barry<E T="03">et al.,</E>2010; Moulton and Holst, 2010). In most cases, the avoidance radii for delphinids appear to be small, on the order of one km or less, and some individuals show no apparent avoidance.</P>
        <P>Captive bottlenose dolphins (<E T="03">Tursiops truncatus</E>) and beluga whales (<E T="03">Delphinapterus leucas)</E>exhibited changes in behavior when exposed to strong pulsed sounds similar in duration to those typically used in seismic surveys (Finneran<E T="03">et al.,</E>2000, 2002, 2005). However, the animals tolerated high received levels of sound before exhibiting aversive behaviors.</P>

        <P>Results for porpoises depend on species. The limited available data suggest that harbor porpoises (<E T="03">Phocoena phocoena</E>) show stronger avoidance of seismic operations than do Dall's porpoises (Stone, 2003; MacLean and Koski, 2005; Bain and Williams, 2006; Stone and Tasker, 2006). Dall's porpoises seem relatively tolerant of airgun operations (MacLean and Koski, 2005; Bain and Williams, 2006), although they too have been observed to avoid large arrays of operating airguns (Calambokidis and Osmek, 1998; Bain and Williams, 2006). This apparent difference in responsiveness of these two porpoise species is consistent with their relative responsiveness to boat traffic and some other acoustic sources (Richardson<E T="03">et al.,</E>1995; Southall<E T="03">et al.,</E>2007).</P>

        <P>Most studies of sperm whales exposed to airgun sounds indicate that the whale shows considerable tolerance of airgun pulses (e.g., Stone, 2003; Moulton<E T="03">et al.,</E>2005, 2006a; Stone and Tasker, 2006; Weir, 2008). In most cases the whales do not show strong avoidance, and they continue to call. However, controlled exposure experiments in the Gulf of Mexico indicate that foraging behavior was altered upon exposure to airgun sound (Jochens<E T="03">et al.,</E>2008; Miller<E T="03">et al.,</E>2009; Tyack, 2009).</P>

        <P>There are almost no specific data on the behavioral reactions of beaked whales to seismic surveys. However, some northern bottlenose whales (<E T="03">Hyperoodon ampullatus</E>) remained in the general area and continued to produce high-frequency clicks when exposed to sound pulses from distant seismic surveys (Gosselin and Lawson, 2004; Laurinolli and Cochrane, 2005; Simard<E T="03">et al.,</E>2005). Most beaked whales tend to avoid approaching vessels of other types (e.g., Wursig<E T="03">et al.,</E>1998). They may also dive for an extended period when approached by a vessel (e.g., Kasuya, 1986), although it is uncertain how much longer such dives may be as compared to dives by undisturbed beaked whales, which also are often quite long (Baird<E T="03">et al.,</E>2006; Tyack<E T="03">et al.,</E>2006). Based on a single observation, Aguilar-Soto<E T="03">et al.</E>(2006) suggested that foraging efficiency of Cuvier's beaked whales (<E T="03">Ziphius cavirostris</E>) may be reduced by close approach of vessels. In any event, it is likely that most beaked whales would also show strong avoidance of an approaching seismic vessel, although this has not been documented explicitly. In fact, Moulton and Holst (2010) reported 15 sightings of beaked whales during seismic studies in the northwest Atlantic; seven of those sightings were made at times when at least one airgun was operating. There was little evidence to indicate that beaked whale behavior was affected by airgun operations; sighting rates and distances were similar during seismic and non-seismic periods (Moulton and Holst, 2010).</P>

        <P>There are increasing indications that some beaked whales tend to strand when naval exercises involving mid-frequency sonar operation are underway<PRTPAGE P="10146"/>within the vicinity of the animals (e.g., Simmonds and Lopez-Jurado, 1991; Frantzis, 1998; NOAA and USN, 2001; Jepson<E T="03">et al.,</E>2003; Hildebrand, 2005; Barlow and Gisiner, 2006; see also the Stranding and Mortality section in this notice). These types of strandings are apparently a disturbance response, although auditory or other injuries or other physiological effects may also be involved. Whether beaked whales would ever react similarly to seismic surveys is unknown. Seismic survey sounds are quite different from those of the sonar in operation during the above-cited incidents.</P>

        <P>Odontocete reactions to large arrays of airguns are variable and, at least for delphinids and Dall's porpoises, seem to be confined to a smaller radius than has been observed for the more responsive of the mysticetes. However, other data suggest that some odontocete species, including harbor porpoises, may be more responsive than might be expected given their poor low-frequency hearing. Reactions at longer distances may be particularly likely when sound propagation conditions are conducive to transmission of the higher frequency components of airgun sound to the animals' location (DeRuiter<E T="03">et al.,</E>2006; Goold and Coates, 2006; Tyack<E T="03">et al.,</E>2006; Potter<E T="03">et al.,</E>2007).</P>
        <HD SOURCE="HD2">Hearing Impairment and Other Physical Effects</HD>

        <P>Exposure to high intensity sound for a sufficient duration may result in auditory effects such as a noise-induced threshold shift—an increase in the auditory threshold after exposure to noise (Finneran<E T="03">et al.,</E>2005). Factors that influence the amount of threshold shift include the amplitude, duration, frequency content, temporal pattern, and energy distribution of noise exposure. The magnitude of hearing threshold shift normally decreases over time following cessation of the noise exposure. The amount of threshold shift just after exposure is called the initial threshold shift. If the threshold shift eventually returns to zero (i.e., the threshold returns to the pre-exposure value), it is called temporary threshold shift (Southall<E T="03">et al.,</E>2007).</P>

        <P>Researchers have studied temporary threshold shift in certain captive odontocetes and pinnipeds exposed to strong sounds (reviewed in Southall<E T="03">et al.,</E>2007). However, there has been no specific documentation of temporary threshold shift let alone permanent hearing damage, (i.e., permanent threshold shift, in free-ranging marine mammals exposed to sequences of airgun pulses during realistic field conditions).</P>
        <P>
          <E T="03">Temporary Threshold Shift</E>—This is the mildest form of hearing impairment that can occur during exposure to a strong sound (Kryter, 1985). While experiencing temporary threshold shift, the hearing threshold rises and a sound must be stronger in order to be heard. At least in terrestrial mammals, temporary threshold shift can last from minutes or hours to (in cases of strong shifts) days. For sound exposures at or somewhat above the temporary threshold shift threshold, hearing sensitivity in both terrestrial and marine mammals recovers rapidly after exposure to the noise ends. There are few data on sound levels and durations necessary to elicit mild temporary threshold shift for marine mammals, and none of the published data focus on temporary threshold shift elicited by exposure to multiple pulses of sound. Southall<E T="03">et al.</E>(2007) summarizes available data on temporary threshold shift in marine mammals. Table 1 (introduced earlier in this document) presents the estimated distances from the LANGSETH<E T="03">'s</E>airguns at which the received energy level (per pulse, flat-weighted) would be greater than or equal to 180 or 190 dB re: 1 µPa.</P>
        <P>To avoid the potential for Level A harassment, serious injury or mortality we (NMFS 1995, 2000) concluded that cetaceans should not be exposed to pulsed underwater noise at received levels exceeding 180 dB re: 1 μPa. We do not consider the established 180 criterion to be the level above which temporary threshold shift might occur. Rather, it is a received level above which, in the view of a panel of bioacoustics specialists convened by us before temporary threshold shift measurements for marine mammals started to become available, one could not be certain that there would be no injurious effects, auditory or otherwise, to marine mammals. We also assume that cetaceans exposed to levels exceeding 160 dB re: 1 μPa may experience Level B harassment.</P>

        <P>For toothed whales, researchers have derived temporary threshold shift information for odontocetes from studies on the bottlenose dolphin and beluga. The experiments show that exposure to a single impulse at a received level of 207 kilopascals (or 30 psi, p-p), which is equivalent to 228 dB re: 1 Pa (p-p), resulted in a 7 and 6 dB temporary threshold shift in the beluga whale at 0.4 and 30 kHz, respectively. Thresholds returned to within 2 dB of the pre-exposure level within four minutes of the exposure (Finneran<E T="03">et al.,</E>2002). For the one harbor porpoise tested, the received level of airgun sound that elicited onset of temporary threshold shift was lower (Lucke<E T="03">et al.,</E>2009). If these results from a single animal are representative, it is inappropriate to assume that onset of temporary threshold shift occurs at similar received levels in all odontocetes (cf. Southall<E T="03">et al.,</E>2007). Some cetaceans apparently can incur temporary threshold shift at considerably lower sound exposures than are necessary to elicit temporary threshold shift in the beluga or bottlenose dolphin.</P>

        <P>For baleen whales, there are no data, direct or indirect, on levels or properties of sound that are required to induce temporary threshold shift. The frequencies to which baleen whales are most sensitive are assumed to be lower than those to which odontocetes are most sensitive, and natural background noise levels at those low frequencies tend to be higher. As a result, auditory thresholds of baleen whales within their frequency band of best hearing are believed to be higher (less sensitive) than are those of odontocetes at their best frequencies (Clark and Ellison, 2004). From this, one could suspect that received levels causing temporary threshold shift onset may also be higher in baleen whales (Southall<E T="03">et al.,</E>2007).</P>

        <P>In pinnipeds, researchers have not measured temporary threshold shift thresholds associated with exposure to brief pulses (single or multiple) of underwater sound. Initial evidence from more prolonged (non-pulse) exposures suggested that some pinnipeds (harbor seals in particular) incur temporary threshold shift at somewhat lower received levels than do small odontocetes exposed for similar durations (Kastak<E T="03">et al.,</E>1999, 2005; Ketten<E T="03">et al.,</E>2001). The indirectly estimated temporary threshold shift threshold for pulsed sounds (in sound pressure level) would be approximately 181 to 186 dB re: 1 μPa (Southall<E T="03">et al.,</E>2007), or a series of pulses for which the highest sound exposure level values are a few decibels lower.</P>
        <P>
          <E T="03">Permanent Threshold Shift</E>—When permanent threshold shift occurs, there is physical damage to the sound receptors in the ear. In severe cases, there can be total or partial deafness, whereas in other cases, the animal has an impaired ability to hear sounds in specific frequency ranges (Kryter, 1985). There is no specific evidence that exposure to pulses of airgun sound can cause permanent threshold shift in any marine mammal, even with large arrays of airguns. However, given the possibility that mammals close to an airgun array might incur at least mild temporary threshold shift, there has been further speculation about the<PRTPAGE P="10147"/>possibility that some individuals occurring very close to airguns might incur permanent threshold shift (e.g., Richardson<E T="03">et al.,</E>1995, p. 372<E T="03">ff;</E>Gedamke<E T="03">et al.,</E>2008). Single or occasional occurrences of mild temporary threshold shift are not indicative of permanent auditory damage, but repeated or (in some cases) single exposures to a level well above that causing temporary threshold shift onset might elicit permanent threshold shift.</P>

        <P>Relationships between temporary and permanent threshold shift thresholds have not been studied in marine mammals, but are assumed to be similar to those in humans and other terrestrial mammals. Permanent threshold shift might occur at a received sound level at least several decibels above that inducing mild temporary threshold shift if the animal were exposed to strong sound pulses with rapid rise times. Based on data from terrestrial mammals, a precautionary assumption is that the permanent threshold shift threshold for impulse sounds (such as airgun pulses as received close to the source) is at least six decibels higher than the temporary threshold shift threshold on a peak-pressure basis, and probably greater than 6 dB (Southall<E T="03">et al.,</E>2007).</P>
        <P>Given the higher level of sound necessary to cause permanent threshold shift as compared with temporary threshold shift, it is considerably less likely that permanent threshold shift would occur. Baleen whales generally avoid the immediate area around operating seismic vessels, as do some other marine mammals.</P>
        <HD SOURCE="HD2">Stranding and Mortality</HD>

        <P>When a living or dead marine mammal swims or floats onto shore and becomes “beached” or incapable of returning to sea, the event is termed a “stranding” (Geraci<E T="03">et al.,</E>1999; Perrin and Geraci, 2002; Geraci and Lounsbury, 2005; NMFS, 2007). The legal definition for a stranding under the MMPA is that “(A) a marine mammal is dead and is (i) on a beach or shore of the United States; or (ii) in waters under the jurisdiction of the United States (including any navigable waters); or (B) a marine mammal is alive and is (i) on a beach or shore of the United States and is unable to return to the water; (ii) on a beach or shore of the United States and, although able to return to the water, is in need of apparent medical attention; or (iii) in the waters under the jurisdiction of the United States (including any navigable waters), but is unable to return to its natural habitat under its own power or without assistance”.</P>

        <P>Marine mammals are known to strand for a variety of reasons, such as infectious agents, biotoxicosis, starvation, fishery interaction, ship strike, unusual oceanographic or weather events, sound exposure, or combinations of these stressors sustained concurrently or in series. However, the cause or causes of most strandings are unknown (Geraci<E T="03">et al.,</E>1976; Eaton, 1979; Odell<E T="03">et al.,</E>1980; Best, 1982). Numerous studies suggest that the physiology, behavior, habitat relationships, age, or condition of cetaceans may cause them to strand or might pre-dispose them to strand when exposed to another phenomenon. These suggestions are consistent with the conclusions of numerous other studies that have demonstrated that combinations of dissimilar stressors commonly combine to kill an animal or dramatically reduce its fitness, even though one exposure without the other does not produce the same result (Chroussos, 2000; Creel, 2005; DeVries<E T="03">et al.,</E>2003; Fair and Becker, 2000; Foley<E T="03">et al.,</E>2001; Moberg, 2000; Relyea, 2005a; 2005b, Romero, 2004; Sih<E T="03">et al.,</E>2004).</P>
        <P>
          <E T="03">Strandings Associated with Military Active Sonar</E>—Several sources have published lists of mass stranding events of cetaceans in an attempt to identify relationships between those stranding events and military active sonar (Hildebrand, 2004; IWC, 2005; Taylor<E T="03">et al.,</E>2004). For example, based on a review of stranding records between 1960 and 1995, the International Whaling Commission (2005) identified ten mass stranding events and concluded that, out of eight stranding events reported from the mid-1980s to the summer of 2003, seven had been coincident with the use of mid-frequency active sonar and most involved beaked whales.</P>

        <P>Over the past 12 years, there have been five stranding events coincident with military mid-frequency active sonar use in which exposure to sonar is believed to have been a contributing factor to strandings: Greece (1996); the Bahamas (2000); Madeira (2000); Canary Islands (2002); and Spain (2006). Refer to Cox<E T="03">et al.</E>(2006) for a summary of common features shared by the strandings events in Greece (1996), Bahamas (2000), Madeira (2000), and Canary Islands (2002); and Fernandez<E T="03">et al.,</E>(2005) for an additional summary of the Canary Islands 2002 stranding event.</P>
        <P>
          <E T="03">Potential for Stranding from Seismic Surveys</E>—Marine mammals close to underwater detonations of high explosives can be killed or severely injured, and the auditory organs are especially susceptible to injury (Ketten<E T="03">et al.,</E>1993; Ketten, 1995). However, explosives are no longer used in marine waters for commercial seismic surveys or (with rare exceptions) for seismic research. These methods have been replaced entirely by airguns or related non-explosive pulse generators. Airgun pulses are less energetic and have slower rise times, and there is no specific evidence that they can cause serious injury, death, or stranding even in the case of large airgun arrays.</P>

        <P>However, the association of strandings of beaked whales with naval exercises involving mid-frequency active sonar and, in one case, the co-occurrence of a Lamont-Doherty's seismic survey (Malakoff, 2002; Cox<E T="03">et al.,</E>2006), has raised the possibility that beaked whales exposed to strong “pulsed” sounds may be especially susceptible to injury and/or behavioral reactions that can lead to stranding (e.g., Hildebrand, 2005; Southall<E T="03">et al.,</E>2007).</P>
        <P>Specific sound-related processes that lead to strandings and mortality are not well documented, but may include:</P>
        <P>(1) Swimming in avoidance of a sound into shallow water;</P>
        <P>(2) A change in behavior (such as a change in diving behavior) that might contribute to tissue damage, gas bubble formation, hypoxia, cardiac arrhythmia, hypertensive hemorrhage or other forms of trauma;</P>
        <P>(3) A physiological change such as a vestibular response leading to a behavioral change or stress-induced hemorrhagic diathesis, leading in turn to tissue damage; and</P>

        <P>(4) Tissue damage directly from sound exposure, such as through acoustically-mediated bubble formation and growth or acoustic resonance of tissues. Some of these mechanisms are unlikely to apply in the case of impulse sounds. However, there are increasing indications that gas-bubble disease (analogous to the bends), induced in supersaturated tissue by a behavioral response to acoustic exposure, could be a pathologic mechanism for the strandings and mortality of some deep-diving cetaceans exposed to sonar. However, the evidence for this remains circumstantial and associated with exposure to naval mid-frequency sonar, not seismic surveys (Cox<E T="03">et al.,</E>2006; Southall<E T="03">et al.,</E>2007).</P>

        <P>Seismic pulses and mid-frequency sonar signals are quite different from one another, and some mechanisms by which sonar sounds have been hypothesized to affect beaked whales are unlikely to apply to airgun pulses. Sounds produced by airgun arrays are broadband impulses with most of the energy below one kHz. Typical military mid-frequency sonar emits non-impulse<PRTPAGE P="10148"/>sounds at frequencies of two to 10 kHz, generally with a relatively narrow bandwidth at any one time. A further difference between seismic surveys and naval exercises is that naval exercises can involve sound sources on more than one vessel. Thus, it is not appropriate to assume that there is a direct correlation between the potential effects of military sonar on marine mammals and those caused by seismic surveys using airguns. However, evidence that sonar signals can, in special circumstances, lead (at least indirectly) to physical damage and mortality (e.g., Balcomb and Claridge, 2001; NOAA and USN, 2001; Jepson<E T="03">et al.,</E>2003; Fernández<E T="03">et al.,</E>2004, 2005; Hildebrand 2005; Cox<E T="03">et al.,</E>2006) suggests that caution is warranted when dealing with exposure of marine mammals to any high-intensity sound.</P>

        <P>There is no conclusive evidence of cetacean strandings or deaths at sea as a result of exposure to seismic surveys, but a few cases of strandings in the general area where a seismic survey was ongoing have led to speculation concerning a possible link between seismic surveys and strandings. Suggestions that there was a link between seismic surveys and strandings of humpback whales in Brazil (Engel<E T="03">et al.,</E>2004) were not well founded (IAGC, 2004; IWC, 2007). In September 2002, two Cuvier's beaked whales stranded in the Gulf of California, Mexico while Lamont-Doherty's R/V<E T="03">Maurice Ewing</E>had been operating a 20-airgun (8,490 in<SU>3</SU>) array in the general area. The link between the stranding and the seismic surveys was inconclusive and not based on any physical evidence (Hogarth, 2002; Yoder, 2002). Nonetheless, the Gulf of California incident plus the beaked whale strandings near naval exercises involving use of mid-frequency sonar suggests a need for caution in conducting seismic surveys in areas occupied by beaked whales until more is known about effects of seismic surveys on those species (Hildebrand, 2005).</P>
        <P>We anticipate no injuries of beaked whales during the proposed study because of:</P>
        <P>(1) The likelihood that any beaked whales nearby would avoid the approaching vessel before being exposed to high sound levels; and</P>
        <P>(2) Differences between the sound sources operated by the LANGSETH and those involved in the naval exercises associated with strandings.</P>
        <HD SOURCE="HD2">Non-Auditory Physiological Effects</HD>

        <P>Non-auditory physiological effects or injuries that theoretically might occur in marine mammals exposed to strong underwater sound include stress, neurological effects, bubble formation, resonance, and other types of organ or tissue damage (Cox<E T="03">et al.,</E>2006; Southall<E T="03">et al.,</E>2007). Studies examining such effects are limited. However, resonance effects (Gentry, 2002) and direct noise-induced bubble formations (Crum<E T="03">et al.,</E>2005) are implausible in the case of exposure to an impulsive broadband source like an airgun array. If seismic surveys disrupt diving patterns of deep-diving species, this might perhaps result in bubble formation and a form of the bends, as speculated to occur in beaked whales exposed to sonar. However, there is no specific evidence of this upon exposure to airgun pulses.</P>

        <P>In general, very little is known about the potential for seismic survey sounds (or other types of strong underwater sounds) to cause non-auditory physical effects in marine mammals. Such effects, if they occur at all, would presumably be limited to short distances and to activities that extend over a prolonged period. The available data do not allow identification of a specific exposure level above which non-auditory effects can be expected (Southall<E T="03">et al.,</E>2007), or any meaningful quantitative predictions of the numbers (if any) of marine mammals that might be affected in those ways. Marine mammals that show behavioral avoidance of seismic vessels, including most baleen whales and some odontocetes, are especially unlikely to incur non-auditory physical effects.</P>
        <HD SOURCE="HD2">Potential Effects of Other Acoustic Devices</HD>
        <HD SOURCE="HD3">Multibeam Echosounder</HD>

        <P>The Observatory would operate the Kongsberg EM 122 multibeam echosounder from the source vessel during the planned study. Sounds from the multibeam echosounder are very short pulses, occurring for two to 15 ms once every five to 20 s, depending on water depth. Most of the energy in the sound pulses emitted by this echosounder is at frequencies near 12 kHz, and the maximum source level is 242 dB re: 1 μPa. The beam is narrow (1 to 2°) in fore-aft extent and wide (150°) in the cross-track extent. Each ping consists of eight (in water greater than 1,000 m deep) or four (less than 1,000 m deep) successive fan-shaped transmissions (segments) at different cross-track angles. Any given mammal at depth near the trackline would be in the main beam for only one or two of the segments. Also, marine mammals that encounter the Kongsberg EM 122 are unlikely to be subjected to repeated pulses because of the narrow fore aft width of the beam and will receive only limited amounts of pulse energy because of the short pulses. Animals close to the vessel (where the beam is narrowest) are especially unlikely to be ensonified for more than one 2- to 15-ms pulse (or two pulses if in the overlap area). Similarly, Kremser<E T="03">et al.</E>(2005) noted that the probability of a cetacean swimming through the area of exposure when an echosounder emits a pulse is small. The animal would have to pass the transducer at close range and be swimming at speeds similar to the vessel in order to receive the multiple pulses that might result in sufficient exposure to cause temporary threshold shift.</P>
        <P>Navy sonars linked to avoidance reactions and stranding of cetaceans: (1) Generally have longer pulse duration than the Kongsberg EM 122; and (2) are often directed close to horizontally versus more downward for the echosounder. The area of possible influence of the echosounder is much smaller—a narrow band below the source vessel. Also, the duration of exposure for a given marine mammal can be much longer for naval sonar. During the Observatory's operations, the individual pulses will be very short, and a given mammal would not receive many of the downward-directed pulses as the vessel passes by the animal. The following section outlines possible effects of an echosounder on marine mammals.</P>
        <P>
          <E T="03">Masking</E>—Marine mammal communications would not be masked appreciably by the echosounder's signals given the low duty cycle of the echosounder and the brief period when an individual mammal is likely to be within its beam. Furthermore, in the case of baleen whales, the echosounder's signals (12 kHz) do not overlap with the predominant frequencies in the calls, which would avoid any significant masking.</P>
        <P>
          <E T="03">Behavioral Responses</E>—Behavioral reactions of free-ranging marine mammals to sonars, echosounders, and other sound sources appear to vary by species and circumstance. Observed reactions have included silencing and dispersal by sperm whales (Watkins<E T="03">et al.,</E>1985), increased vocalizations and no dispersal by pilot whales (<E T="03">Globicephala melas</E>) (Rendell and Gordon, 1999), and the previously-mentioned beachings by beaked whales. During exposure to a 21 to 25 kHz “whale-finding” sonar with a source level of 215 dB re: 1 μPa, gray whales reacted by orienting slightly away from the source and being deflected from their course by approximately 200 m (Frankel, 2005). When a 38-kHz<PRTPAGE P="10149"/>echosounder and a 150-kHz acoustic Doppler current profiler were transmitting during studies in the eastern tropical Pacific Ocean, baleen whales showed no significant responses, while spotted and spinner dolphins were detected slightly more often and beaked whales less often during visual surveys (Gerrodette and Pettis, 2005).</P>

        <P>Captive bottlenose dolphins and a beluga whale exhibited changes in behavior when exposed to 1-s tonal signals at frequencies similar to those that would be emitted by the Observatory's echosounder, and to shorter broadband pulsed signals. Behavioral changes typically involved what appeared to be deliberate attempts to avoid the sound exposure (Schlundt<E T="03">et al.,</E>2000; Finneran<E T="03">et al.,</E>2002; Finneran and Schlundt, 2004). The relevance of those data to free-ranging odontocetes is uncertain, and in any case, the test sounds were quite different in duration as compared with those from an echosounder.</P>
        <P>
          <E T="03">Hearing Impairment and Other Physical Effects</E>—Given recent stranding events that have been associated with the operation of naval sonar, there is concern that mid-frequency sonar sounds can cause serious impacts to marine mammals (see above). However, the echosounder proposed for use by the LANGSETH is quite different than sonar used for navy operations. The echosounder's pulse duration is very short relative to the naval sonar. Also, at any given location, an individual marine mammal would be in the echosounder's beam for much less time given the generally downward orientation of the beam and its narrow fore-aft beamwidth; navy sonar often uses near-horizontally-directed sound. Those factors would all reduce the sound energy received from the echosounder relative to that from naval sonar.</P>
        <P>Based upon the best available science, we believe that the brief exposure of marine mammals to one pulse, or small numbers of signals, from the echosounder is not likely to result in the harassment of marine mammals.</P>
        <HD SOURCE="HD2">Sub-Bottom Profiler</HD>

        <P>The Observatory would also operate a sub-bottom profiler from the source vessel during the proposed survey. The profiler's sounds are very short pulses, occurring for one to four ms once every second. Most of the energy in the sound pulses emitted by the profiler is at 3.5 kHz, and the beam is directed downward. The sub-bottom profiler on the LANGSETH has a maximum source level of 222 dB re: 1 µPa. Kremser<E T="03">et al.</E>(2005) noted that the probability of a cetacean swimming through the area of exposure when a bottom profiler emits a pulse is small—even for a profiler more powerful than that on the LANGSETH—if the animal was in the area, it would have to pass the transducer at close range and in order to be subjected to sound levels that could cause temporary threshold shift.</P>
        <P>
          <E T="03">Masking</E>—Marine mammal communications would not be masked appreciably by the profiler's signals given the directionality of the signal and the brief period when an individual mammal is likely to be within its beam. Furthermore, in the case of most baleen whales, the profiler's signals do not overlap with the predominant frequencies in the calls, which would avoid significant masking.</P>
        <P>
          <E T="03">Behavioral Responses</E>—Marine mammal behavioral reactions to other pulsed sound sources are discussed above, and responses to the profiler are likely to be similar to those for other pulsed sources if received at the same levels. However, the pulsed signals from the profiler are considerably weaker than those from the echosounder. Therefore, behavioral responses are not expected unless marine mammals are very close to the source.</P>
        <P>
          <E T="03">Hearing Impairment and Other Physical Effects</E>—It is unlikely that the profiler produces pulse levels strong enough to cause hearing impairment or other physical injuries even in an animal that is (briefly) in a position near the source. The profiler operates simultaneously with other higher-power acoustic sources. Many marine mammals would move away in response to the approaching higher-power sources or the vessel itself before the mammals would be close enough for there to be any possibility of effects from the less intense sounds from the profiler</P>
        <HD SOURCE="HD1">Potential Effects of Vessel Movement and Collisions</HD>
        <P>Vessel movement in the vicinity of marine mammals has the potential to result in either a behavioral response or a direct physical interaction. Both scenarios are discussed below this section.</P>
        <HD SOURCE="HD2">Behavioral Responses to Vessel Movement</HD>

        <P>There are limited data concerning marine mammal behavioral responses to vessel traffic and vessel noise, and a lack of consensus among scientists with respect to what these responses mean or whether they result in short-term or long-term adverse effects. In those cases where there is a busy shipping lane or where there is a large amount of vessel traffic, marine mammals may experience acoustic masking (Hildebrand, 2005) if they are present in the area (e.g., killer whales in Puget Sound; Foote<E T="03">et al.,</E>2004; Holt<E T="03">et al.,</E>2008). In cases where vessels actively approach marine mammals (e.g., whale watching or dolphin watching boats), scientists have documented that animals exhibit altered behavior such as increased swimming speed, erratic movement, and active avoidance behavior (Bursk, 1983; Acevedo, 1991; Baker and MacGibbon, 1991; Trites and Bain, 2000; Williams<E T="03">et al.,</E>2002; Constantine<E T="03">et al.,</E>2003), reduced blow interval (Ritcher<E T="03">et al.,</E>2003), disruption of normal social behaviors (Lusseau, 2003; 2006), and the shift of behavioral activities which may increase energetic costs (Constantine<E T="03">et al.,</E>2003; 2004)). A detailed review of marine mammal reactions to ships and boats is available in Richardson<E T="03">et al.</E>(1995). For each of the marine mammal taxonomy groups, Richardson<E T="03">et al.</E>(1995) provides the following assessment regarding reactions to vessel traffic:</P>
        <P>
          <E T="03">Toothed whales:</E>“In summary, toothed whales sometimes show no avoidance reaction to vessels, or even approach them. However, avoidance can occur, especially in response to vessels of types used to chase or hunt the animals. This may cause temporary displacement, but we know of no clear evidence that toothed whales have abandoned significant parts of their range because of vessel traffic.”</P>
        <P>
          <E T="03">Baleen whales:</E>“When baleen whales receive low-level sounds from distant or stationary vessels, the sounds often seem to be ignored. Some whales approach the sources of these sounds. When vessels approach whales slowly and non-aggressively, whales often exhibit slow and inconspicuous avoidance maneuvers. In response to strong or rapidly changing vessel noise, baleen whales often interrupt their normal behavior and swim rapidly away. Avoidance is especially strong when a boat heads directly toward the whale.”</P>

        <P>Behavioral responses to stimuli are complex and influenced to varying degrees by a number of factors, such as species, behavioral contexts, geographical regions, source characteristics (moving or stationary, speed, direction, etc.), prior experience of the animal and physical status of the animal. For example, studies have shown that beluga whales' reactions varied when exposed to vessel noise and traffic. In some cases, naive beluga whales exhibited rapid swimming from ice-breaking vessels up to 80 km (49.7 mi) away, and showed changes in<PRTPAGE P="10150"/>surfacing, breathing, diving, and group composition in the Canadian high Arctic where vessel traffic is rare (Finley<E T="03">et al.,</E>1990). In other cases, beluga whales were more tolerant of vessels, but responded differentially to certain vessels and operating characteristics by reducing their calling rates (especially older animals) in the St. Lawrence River where vessel traffic is common (Blane and Jaakson, 1994). In Bristol Bay, Alaska, beluga whales continued to feed when surrounded by fishing vessels and resisted dispersal even when purposefully harassed (Fish and Vania, 1971).</P>
        <P>In reviewing more than 25 years of whale observation data, Watkins (1986) concluded that whale reactions to vessel traffic were “modified by their previous experience and current activity: Habituation often occurred rapidly, attention to other stimuli or preoccupation with other activities sometimes overcame their interest or wariness of stimuli.” Watkins noticed that over the years of exposure to ships in the Cape Cod area, minke whales changed from frequent positive interest (e.g., approaching vessels) to generally uninterested reactions; fin whales changed from mostly negative (e.g., avoidance) to uninterested reactions; right whales apparently continued the same variety of responses (negative, uninterested, and positive responses) with little change; and humpbacks dramatically changed from mixed responses that were often negative to reactions that were often strongly positive. Watkins (1986) summarized that “whales near shore, even in regions with low vessel traffic, generally have become less wary of boats and their noises, and they have appeared to be less easily disturbed than previously. In particular locations with intense shipping and repeated approaches by boats (such as the whale-watching areas of Stellwagen Bank), more and more whales had positive reactions to familiar vessels, and they also occasionally approached other boats and yachts in the same ways.”</P>

        <P>Although the radiated sound from the LANGSETH would be audible to marine mammals over a large distance, it is unlikely that animals would respond behaviorally (in a manner that we would consider MMPA harassment) to low-level distant shipping noise as the animals in the area are likely to be habituated to such noises (Nowacek<E T="03">et al.,</E>2004). In light of these facts, we do not expect the LANGSETH<E T="03">'s</E>movements to result in Level B harassment.</P>
        <HD SOURCE="HD2">Vessel Strike</HD>

        <P>Ship strikes of cetaceans can cause major wounds, which may lead to the death of the animal. An animal at the surface could be struck directly by a vessel, a surfacing animal could hit the bottom of a vessel, or an animal just below the surface could be cut by a vessel's propeller. The severity of injuries typically depends on the size and speed of the vessel (Knowlton and Kraus, 2001; Laist<E T="03">et al.,</E>2001; Vanderlaan and Taggart, 2007).</P>

        <P>The most vulnerable marine mammals are those that spend extended periods of time at the surface in order to restore oxygen levels within their tissues after deep dives (e.g., the sperm whale). In addition, some baleen whales, such as the North Atlantic right whale, seem generally unresponsive to vessel sound, making them more susceptible to vessel collisions (Nowacek<E T="03">et al.,</E>2004). These species are primarily large, slow moving whales. Smaller marine mammals (e.g., bottlenose dolphin) move quickly through the water column and are often seen riding the bow wave of large ships. Marine mammal responses to vessels may include avoidance and changes in dive pattern (NRC, 2003).</P>

        <P>An examination of all known ship strikes from all shipping sources (civilian and military) indicates vessel speed is a principal factor in whether a vessel strike results in death (Knowlton and Kraus, 2001; Laist<E T="03">et al.,</E>2001; Jensen and Silber, 2003; Vanderlaan and Taggart, 2007). In assessing records in which vessel speed was known, Laist<E T="03">et al.</E>(2001) found a direct relationship between the occurrence of a whale strike and the speed of the vessel involved in the collision. The authors concluded that most deaths occurred when a vessel was traveling in excess of 24.1 km/h (14.9 mph;13 kts).</P>

        <P>The Observatory's proposed operation of one vessel for the proposed survey is relatively small in scale compared to the number of commercial ships transiting at higher speeds in the same areas on an annual basis. The probability of vessel and marine mammal interactions occurring during the proposed survey is unlikely due to the LANGSETH<E T="03">'s</E>slow operational speed, which is typically 4.6 kts (8.5 km/h; 5.3 mph). Outside of seismic operations, the LANGSETH<E T="03">'s</E>cruising speed would be approximately 11.5 mph (18.5 km/h; 10 kts) which is generally below the speed at which studies have noted reported increases of marine mammal injury or death (Laist<E T="03">et al.,</E>2001).</P>

        <P>As a final point, the LANGSETH has a number of other advantages for avoiding ship strikes as compared to most commercial merchant vessels, including the following: The LANGSETH<E T="03">'s</E>bridge offers good visibility to visually monitor for marine mammal presence; observers posted during operations scan the ocean for marine mammals and must report visual alerts of marine mammal presence to crew; and the observers receive extensive training that covers the fundamentals of visual observing for marine mammals and information about marine mammals and their identification at sea.</P>
        <HD SOURCE="HD2">Entanglement</HD>
        <P>Entanglement can occur if wildlife becomes immobilized in survey lines, cables, nets, or other equipment that is moving through the water column. The proposed seismic survey would require towing approximately 8.0 km (4.9 mi) of equipment and cables. This large of an array carries the risk of entanglement for marine mammals. Wildlife, especially slow moving individuals, such as large whales, have a low probability of becoming entangled due to slow speed of the survey vessel and onboard monitoring efforts. The Observatory has no recorded cases of entanglement of marine mammals during the conduct of over 8 years of seismic surveys covering over 160,934 km (86,897.4 nmi) of transect lines.</P>

        <P>In May, 2011, there was one recorded entanglement of an olive ridley sea turtle (<E T="03">Lepidochelys olivacea</E>) in the LANGSETH<E T="03">'s</E>barovanes after the conclusion of a seismic survey off Costa Rica. There have cases of baleen whales, mostly gray whales (Heyning, 1990), becoming entangled in fishing lines. The probability for entanglement of marine mammals is considered not significant because of the vessel speed and the monitoring efforts onboard the survey vessel.</P>
        <P>The potential effects to marine mammals described in this section of the document do not take into consideration the proposed monitoring and mitigation measures described later in this document (see the “Proposed Mitigation” and “Proposed Monitoring and Reporting” sections) which, as noted are designed to effect the least practicable adverse impact on affected marine mammal species and stocks.</P>
        <HD SOURCE="HD1">Anticipated Effects on Marine Mammal Habitat</HD>

        <P>The proposed seismic survey is not anticipated to have any permanent impact on habitats used by the marine mammals in the proposed survey area, including the food sources they use (i.e., fish and invertebrates). Additionally, no physical damage to any habitat is<PRTPAGE P="10151"/>anticipated as a result of conducting the proposed seismic survey. While it is anticipated that the specified activity may result in marine mammals avoiding certain areas due to temporary ensonification, this impact to habitat is temporary and reversible and was considered in further detail earlier in this document, as behavioral modification. The main impact associated with the proposed activity would be temporarily elevated noise levels and the associated direct effects on marine mammals, previously discussed in this notice. The next section discusses the potential impacts of anthropogenic sound sources on common marine mammal prey in the proposed survey area (i.e., fish and invertebrates).</P>
        <HD SOURCE="HD1">Anticipated Effects on Fish</HD>
        <P>One reason for the adoption of airguns as the standard energy source for marine seismic surveys is that, unlike explosives, they have not been associated with large-scale fish kills. However, existing information on the impacts of seismic surveys on marine fish populations is limited. There are three types of potential effects of exposure to seismic surveys: (1) Pathological, (2) physiological, and (3) behavioral. Pathological effects involve lethal and temporary or permanent sub-lethal injury. Physiological effects involve temporary and permanent primary and secondary stress responses, such as changes in levels of enzymes and proteins. Behavioral effects refer to temporary and (if they occur) permanent changes in exhibited behavior (e.g., startle and avoidance behavior). The three categories are interrelated in complex ways. For example, it is possible that certain physiological and behavioral changes could potentially lead to an ultimate pathological effect on individuals (i.e., mortality).</P>
        <P>The specific received sound levels at which permanent adverse effects to fish potentially could occur are little studied and largely unknown. Furthermore, the available information on the impacts of seismic surveys on marine fish is from studies of individuals or portions of a population; there have been no studies at the population scale. The studies of individual fish have often been on caged fish that were exposed to airgun pulses in situations not representative of an actual seismic survey. Thus, available information provides limited insight on possible real-world effects at the ocean or population scale.</P>
        <P>Hastings and Popper (2005), Popper (2009), and Popper and Hastings (2009a,b) provided recent critical reviews of the known effects of sound on fish. The following sections provide a general synopsis of the available information on the effects of exposure to seismic and other anthropogenic sound as relevant to fish. The information comprises results from scientific studies of varying degrees of rigor plus some anecdotal information. Some of the data sources may have serious shortcomings in methods, analysis, interpretation, and reproducibility that must be considered when interpreting their results (see Hastings and Popper, 2005). Potential adverse effects of the program's sound sources on marine fish are noted.</P>
        <P>
          <E T="03">Pathological Effects</E>-The potential for pathological damage to hearing structures in fish depends on the energy level of the received sound and the physiology and hearing capability of the species in question. For a given sound to result in hearing loss, the sound must exceed, by some substantial amount, the hearing threshold of the fish for that sound (Popper, 2005). The consequences of temporary or permanent hearing loss in individual fish on a fish population are unknown; however, they likely depend on the number of individuals affected and whether critical behaviors involving sound (e.g., predator avoidance, prey capture, orientation and navigation, reproduction, etc.) are adversely affected.</P>

        <P>Little is known about the mechanisms and characteristics of damage to fish that may be inflicted by exposure to seismic survey sounds. Few data have been presented in the peer-reviewed scientific literature. As far as the Observatory, and we know, there are only two papers with proper experimental methods, controls, and careful pathological investigation implicating sounds produced by actual seismic survey airguns in causing adverse anatomical effects. One such study indicated anatomical damage, and the second indicated temporary threshold shift in fish hearing. The anatomical case is McCauley<E T="03">et al.</E>(2003), who found that exposure to airgun sound caused observable anatomical damage to the auditory maculae of pink snapper (<E T="03">Pagrus auratus</E>). This damage in the ears had not been repaired in fish sacrificed and examined almost two months after exposure. On the other hand, Popper<E T="03">et al.</E>(2005) documented only temporary threshold shift (as determined by auditory brainstem response) in two of three fish species from the Mackenzie River Delta. This study found that broad whitefish (<E T="03">Coregonus nasus</E>) exposed to five airgun shots were not significantly different from those of controls. During both studies, the repetitive exposure to sound was greater than would have occurred during a typical seismic survey. However, the substantial low-frequency energy produced by the airguns (less than 400 Hz in the study by McCauley<E T="03">et al.</E>(2003) and less than approximately 200 Hz in Popper<E T="03">et al.</E>(2005)) likely did not propagate to the fish because the water in the study areas was very shallow (approximately 9 m in the former case and less than 2 m in the latter). Water depth sets a lower limit on the lowest sound frequency that will propagate (i.e., the cutoff frequency) at about one-quarter wavelength (Urick, 1983; Rogers and Cox, 1988).</P>
        <P>Wardle<E T="03">et al.</E>(2001) suggested that in water, acute injury and death of organisms exposed to seismic energy depends primarily on two features of the sound source: (1) The received peak pressure and (2) the time required for the pressure to rise and decay. Generally, as received pressure increases, the period for the pressure to rise and decay decreases, and the chance of acute pathological effects increases. According to Buchanan<E T="03">et al.</E>(2004), for the types of seismic airguns and arrays involved with the proposed program, the pathological (mortality) zone for fish would be expected to be within a few meters of the seismic source. Numerous other studies provide examples of no fish mortality upon exposure to seismic sources (Falk and Lawrence, 1973; Holliday<E T="03">et al.,</E>1987; La Bella<E T="03">et al.,</E>1996; Santulli<E T="03">et al.,</E>1999; McCauley<E T="03">et al.,</E>2000a,b, 2003; Bjarti, 2002; Thomsen, 2002; Hassel<E T="03">et al.,</E>2003; Popper<E T="03">et al.,</E>2005; Boeger<E T="03">et al.,</E>2006).</P>

        <P>An experiment of the effects of a single 700 in<SU>3</SU>airgun was conducted in Lake Meade, Nevada (USGS, 1999). The data were used in an Environmental Assessment of the effects of a marine reflection survey of the Lake Meade fault system by the National Park Service (Paulson<E T="03">et al.,</E>1993, in USGS, 1999). They suspended the airgun 3.5 m (11.5 ft) above a school of threadfin shad in Lake Meade and fired three successive times at a 30 second interval. Neither surface inspection nor diver observations of the water column and bottom found any dead fish.</P>

        <P>For a proposed seismic survey in Southern California, USGS (1999) conducted a review of the literature on the effects of airguns on fish and fisheries. They reported a 1991 study of the Bay Area Fault system from the continental shelf to the Sacramento River, using a 10 airgun (5,828 in<SU>3</SU>) array. Brezzina and Associates were hired by USGS to monitor the effects of the surveys, and concluded that airgun operations were not responsible for the<PRTPAGE P="10152"/>death of any of the fish carcasses observed, and the airgun profiling did not appear to alter the feeding behavior of sea lions, seals, or pelicans observed feeding during the seismic surveys.</P>

        <P>Some studies have reported, some equivocally, that mortality of fish, fish eggs, or larvae can occur close to seismic sources (Kostyuchenko, 1973; Dalen and Knutsen, 1986; Booman<E T="03">et al.,</E>1996; Dalen<E T="03">et al.,</E>1996). Some of the reports claimed seismic effects from treatments quite different from actual seismic survey sounds or even reasonable surrogates. However, Payne<E T="03">et al.</E>(2009) reported no statistical differences in mortality/morbidity between control and exposed groups of capelin eggs or monkfish larvae. Saetre and Ona (1996) applied a worst-case scenario, mathematical model to investigate the effects of seismic energy on fish eggs and larvae. They concluded that mortality rates caused by exposure to seismic surveys are so low, as compared to natural mortality rates, that the impact of seismic surveying on recruitment to a fish stock must be regarded as insignificant.</P>
        <P>
          <E T="03">Physiological Effects</E>—Physiological effects refer to cellular and/or biochemical responses of fish to acoustic stress. Such stress potentially could affect fish populations by increasing mortality or reducing reproductive success. Primary and secondary stress responses of fish after exposure to seismic survey sound appear to be temporary in all studies done to date (Sverdrup<E T="03">et al.,</E>1994; Santulli<E T="03">et al.,</E>1999; McCauley<E T="03">et al.,</E>2000a,b). The periods necessary for the biochemical changes to return to normal are variable and depend on numerous aspects of the biology of the species and of the sound stimulus.</P>
        <P>
          <E T="03">Behavioral Effects</E>—Behavioral effects include changes in the distribution, migration, mating, and catchability of fish populations. Studies investigating the possible effects of sound (including seismic survey sound) on fish behavior have been conducted on both uncaged and caged individuals (e.g., Chapman and Hawkins, 1969; Pearson<E T="03">et al.,</E>1992; Santulli<E T="03">et al.,</E>1999; Wardle<E T="03">et al.,</E>2001; Hassel<E T="03">et al.,</E>2003). Typically, in these studies fish exhibited a sharp startle response at the onset of a sound followed by habituation and a return to normal behavior after the sound ceased.</P>
        <P>The Minerals Management Service (MMS, 2005) assessed the effects of a proposed seismic survey in Cook Inlet, Alaska. The seismic survey proposed using three vessels, each towing two, four-airgun arrays ranging from 1,500 to 2,500 in<SU>3</SU>. The Minerals Management Service noted that the impact to fish populations in the survey area and adjacent waters would likely be very low and temporary and also concluded that seismic surveys may displace the pelagic fishes from the area temporarily when airguns are in use. However, fishes displaced and avoiding the airgun noise are likely to backfill the survey area in minutes to hours after cessation of seismic testing. Fishes not dispersing from the airgun noise (e.g., demersal species) may startle and move short distances to avoid airgun emissions.</P>
        <P>In general, any adverse effects on fish behavior or fisheries attributable to seismic testing may depend on the species in question and the nature of the fishery (season, duration, fishing method). They may also depend on the age of the fish, its motivational state, its size, and numerous other factors that are difficult, if not impossible, to quantify at this point, given such limited data on effects of airguns on fish, particularly under realistic at-sea conditions.</P>
        <HD SOURCE="HD2">Anticipated Effects on Invertebrates</HD>

        <P>The existing body of information on the impacts of seismic survey sound on marine invertebrates is very limited. However, there is some unpublished and very limited evidence of the potential for adverse effects on invertebrates, thereby justifying further discussion and analysis of this issue. The three types of potential effects of exposure to seismic surveys on marine invertebrates are pathological, physiological, and behavioral. Based on the physical structure of their sensory organs, marine invertebrates appear to be specialized to respond to particle displacement components of an impinging sound field and not to the pressure component (Popper<E T="03">et al.,</E>2001).</P>
        <P>The only information available on the impacts of seismic surveys on marine invertebrates involves studies of individuals; there have been no studies at the population scale. Thus, available information provides limited insight on possible real-world effects at the regional or ocean scale. The most important aspect of potential impacts concerns how exposure to seismic survey sound ultimately affects invertebrate populations and their viability, including availability to fisheries.</P>

        <P>Literature reviews of the effects of seismic and other underwater sound on invertebrates were provided by Moriyasu<E T="03">et al.</E>(2004) and Payne<E T="03">et al.</E>(2008). The following sections provide a synopsis of available information on the effects of exposure to seismic survey sound on species of decapod crustaceans and cephalopods, the two taxonomic groups of invertebrates on which most such studies have been conducted. The available information is from studies with variable degrees of scientific soundness and from anecdotal information. A more detailed review of the literature on the effects of seismic survey sound on invertebrates is in Appendix E of the 2011 PEIS (NSF/USGS, 2011).</P>
        <P>
          <E T="03">Pathological Effects</E>—In water, lethal and sub-lethal injury to organisms exposed to seismic survey sound appears to depend on at least two features of the sound source: (1) The received peak pressure; and (2) the time required for the pressure to rise and decay. Generally, as received pressure increases, the period for the pressure to rise and decay decreases, and the chance of acute pathological effects increases. For the type of airgun array planned for the proposed program, the pathological (mortality) zone for crustaceans and cephalopods is expected to be within a few meters of the seismic source, at most; however, very few specific data are available on levels of seismic signals that might damage these animals. This premise is based on the peak pressure and rise/decay time characteristics of seismic airgun arrays currently in use around the world.</P>

        <P>Some studies have suggested that seismic survey sound has a limited pathological impact on early developmental stages of crustaceans (Pearson<E T="03">et al.,</E>1994; Christian<E T="03">et al.,</E>2003; DFO, 2004). However, the impacts appear to be either temporary or insignificant compared to what occurs under natural conditions. Controlled field experiments on adult crustaceans (Christian<E T="03">et al.,</E>2003, 2004; DFO, 2004) and adult cephalopods (McCauley<E T="03">et al.,</E>2000a,b) exposed to seismic survey sound have not resulted in any significant pathological impacts on the animals. It has been suggested that exposure to commercial seismic survey activities has injured giant squid (Guerra<E T="03">et al.,</E>2004), but the article provides little evidence to support this claim.</P>

        <P>Tenera Environmental (2011b) reported that Norris and Mohl (1983, summarized in Mariyasu<E T="03">et al.,</E>2004) observed lethal effects in squid (<E T="03">Loligo vulgaris</E>) at levels of 246 to 252 dB after 3 to 11 minutes.</P>
        <P>Andre<E T="03">et al.</E>(2011) exposed four cephalopod species (<E T="03">Loligo vulgaris,</E>
          <E T="03">Sepia officinalis,</E>
          <E T="03">Octopus vulgaris,</E>and<E T="03">Ilex coindetii</E>) to two hours of continuous sound from 50 to 400 Hz at 157 ± 5 dB re: 1 μPa. They reported lesions to the sensory hair cells of the statocysts of the exposed animals that<PRTPAGE P="10153"/>increased in severity with time, suggesting that cephalopods are particularly sensitive to low-frequency sound. The received sound pressure level was 157 ± 5 dB re: 1 µPa, with peak levels at 175 dB re 1 µPa. As in the McCauley<E T="03">et al.</E>(2003) paper on sensory hair cell damage in pink snapper as a result of exposure to seismic sound, the cephalopods were subjected to higher sound levels than they would be under natural conditions, and they were unable to swim away from the sound source.</P>
        <P>
          <E T="03">Physiological Effects</E>—Physiological effects refer mainly to biochemical responses by marine invertebrates to acoustic stress. Such stress potentially could affect invertebrate populations by increasing mortality or reducing reproductive success. Primary and secondary stress responses (i.e., changes in haemolymph levels of enzymes, proteins, etc.) of crustaceans have been noted several days or months after exposure to seismic survey sounds (Payne<E T="03">et al.,</E>2007). It was noted however, than no behavioral impacts were exhibited by crustaceans (Christian<E T="03">et al.,</E>2003, 2004; DFO, 2004). The periods necessary for these biochemical changes to return to normal are variable and depend on numerous aspects of the biology of the species and of the sound stimulus.</P>
        <P>
          <E T="03">Behavioral Effects</E>—There is increasing interest in assessing the possible direct and indirect effects of seismic and other sounds on invertebrate behavior, particularly in relation to the consequences for fisheries. Changes in behavior could potentially affect such aspects as reproductive success, distribution, susceptibility to predation, and catchability by fisheries. Studies investigating the possible behavioral effects of exposure to seismic survey sound on crustaceans and cephalopods have been conducted on both uncaged and caged animals. In some cases, invertebrates exhibited startle responses (e.g., squid in McCauley<E T="03">et al.,</E>2000a,b). In other cases, no behavioral impacts were noted (e.g., crustaceans in Christian<E T="03">et al.,</E>2003, 2004; DFO, 2004). There have been anecdotal reports of reduced catch rates of shrimp shortly after exposure to seismic surveys; however, other studies have not observed any significant changes in shrimp catch rate (Andriguetto-Filho<E T="03">et al.,</E>2005). Similarly, Parry and Gason (2006) did not find any evidence that lobster catch rates were affected by seismic surveys. Any adverse effects on crustacean and cephalopod behavior or fisheries attributable to seismic survey sound depend on the species in question and the nature of the fishery (season, duration, fishing method).</P>
        <HD SOURCE="HD1">Proposed Mitigation</HD>
        <P>In order to issue an incidental take authorization under section 101(a)(5)(D) of the MMPA, we must set forth the permissible methods of taking pursuant to such activity, and other means of effecting the least practicable adverse impact on such species or stock and its habitat, paying particular attention to rookeries, mating grounds, and areas of similar significance, and the availability of such species or stock for taking for certain subsistence uses.</P>
        <P>The Observatory has reviewed the following source documents and have incorporated a suite of proposed mitigation measures into their project description.</P>
        <P>(1) Protocols used during previous Foundation and Observatory-funded seismic research cruises as approved by us and detailed in the Foundation's 2011 PEIS;</P>
        <P>(2) Previous incidental harassment authorizations applications and authorizations that we have approved and authorized; and</P>
        <P>(3) Recommended best practices in Richardson<E T="03">et al.</E>(1995), Pierson<E T="03">et al.</E>(1998), and Weir and Dolman (2007).</P>
        <P>To reduce the potential for disturbance from acoustic stimuli associated with the activities, the Observatory, and/or its designees have proposed to implement the following mitigation measures for marine mammals:</P>
        <P>(1) Vessel-based visual mitigation monitoring;</P>
        <P>(2) Proposed exclusion zones;</P>
        <P>(3) Power down procedures;</P>
        <P>(4) Shutdown procedures;</P>
        <P>(5) Ramp-up procedures; and</P>
        <P>(6) Speed and course alterations.</P>
        <HD SOURCE="HD2">Vessel-Based Visual Mitigation Monitoring</HD>
        <P>The Observatory would position observers aboard the seismic source vessel to watch for marine mammals near the vessel during daytime airgun operations and during any start-ups at night. Observers would also watch for marine mammals near the seismic vessel for at least 30 minutes prior to the start of airgun operations after an extended shutdown (i.e., greater than approximately eight minutes for this proposed cruise). When feasible, the observers would conduct observations during daytime periods when the seismic system is not operating for comparison of sighting rates and behavior with and without airgun operations and between acquisition periods. Based on the observations, the LANGSETH would power down or shutdown the airguns when marine mammals are observed within or about to enter a designated 180-dB exclusion zone.</P>
        <P>During seismic operations, at least four protected species observers would be aboard the LANGSETH. The Observatory would appoint the observers with our concurrence and they would conduct observations during ongoing daytime operations and nighttime ramp-ups of the airgun array. During the majority of seismic operations, two observers would be on duty from the observation tower to monitor marine mammals near the seismic vessel. Using two observers would increase the effectiveness of detecting animals near the source vessel. However, during mealtimes and bathroom breaks, it is sometimes difficult to have two observers on effort, but at least one observer would be on watch during bathroom breaks and mealtimes. Observers would be on duty in shifts of no longer than four hours in duration.</P>
        <P>Two observers on the LANGSETH would also be on visual watch during all nighttime ramp-ups of the seismic airguns. A third observer would monitor the passive acoustic monitoring equipment 24 hours a day to detect vocalizing marine mammals present in the action area. In summary, a typical daytime cruise would have scheduled two observers (visual) on duty from the observation tower, and an observer (acoustic) on the passive acoustic monitoring system. Before the start of the seismic survey, the Observatory would instruct the vessel's crew to assist in detecting marine mammals and implementing mitigation requirements.</P>

        <P>The LANGSETH is a suitable platform for marine mammal observations. When stationed on the observation platform, the eye level would be approximately 21.5 m (70.5 ft) above sea level, and the observer would have a good view around the entire vessel. During daytime, the observers would scan the area around the vessel systematically with reticle binoculars (e.g., 7 x 50 Fujinon), Big-eye binoculars (25 x 150), and with the naked eye. During darkness, night vision devices would be available (ITT F500 Series Generation 3 binocular-image intensifier or equivalent), when required. Laser range-finding binoculars (Leica LRF 1200 laser rangefinder or equivalent) would be available to assist with distance estimation. Those are useful in training observers to estimate distances visually, but are generally not useful in measuring distances to animals directly;<PRTPAGE P="10154"/>that is done primarily with the reticles in the binoculars.</P>
        <P>When the observers see marine mammals within or about to enter the designated exclusion zone, the LANGSETH would immediately power down or shutdown the airguns. The observer(s) would continue to maintain watch to determine when the animal(s) are outside the exclusion zone by visual confirmation. Airgun operations would not resume until the observer has confirmed that the animal has left the zone, or if not observed after 15 minutes for species with shorter dive durations (small odontocetes and pinnipeds) or 30 minutes for species with longer dive durations (mysticetes and large odontocetes, including sperm, pygmy sperm, dwarf sperm, killer, and beaked whales).</P>
        <P>
          <E T="03">Proposed Exclusion Zones</E>—The Observatory would use safety radii to designate exclusion zones and to estimate take for marine mammals. Table 1 (presented earlier in this document) shows the distances at which one would expect to receive three sound levels (160- and 180-dB) from the 36-airgun array and a single airgun. The 180-dB level shutdown criteria are applicable to cetaceans as specified by us (2000). The Observatory used these levels to establish the exclusion zones.</P>
        <P>If the protected species visual observer detects marine mammal(s) within or about to enter the appropriate exclusion zone, the LANGSETH crew would immediately power down the airgun array, or perform a shutdown if necessary (see Shut-down Procedures).</P>
        <P>
          <E T="03">Power Down Procedures</E>-A power down involves decreasing the number of airguns in use such that the radius of the 180-dB zone is smaller to the extent that marine mammals are no longer within or about to enter the exclusion zone. A power down of the airgun array can also occur when the vessel is moving from one seismic line to another. During a power down for mitigation, the LANGSETH would operate one airgun (40 in<SU>3</SU>). The continued operation of one airgun is intended to alert marine mammals to the presence of the seismic vessel in the area. A shutdown occurs when the LANGSETH suspends all airgun activity.</P>
        <P>If the observer detects a marine mammal outside the exclusion zone and the animal is likely to enter the zone, the crew would power down the airguns to reduce the size of the 180-dB exclusion zone before the animal enters that zone. Likewise, if a mammal is already within the zone when first detected, the crew would power-down the airguns immediately. During a power down of the airgun array, the crew would operate a single 40-in<SU>3</SU>airgun which has a smaller exclusion zone. If the observer detects a marine mammal within or near the smaller exclusion zone around the airgun (Table 1), the crew would shut down the single airgun (see next section).</P>
        <P>Resuming Airgun Operations After a Power Down—Following a power-down, the LANGSETH crew would not resume full airgun activity until the marine mammal has cleared the 180-dB exclusion zone (see Table 1). The observers would consider the animal to have cleared the exclusion zone if:</P>
        <P>• The observer has visually observed the animal leave the exclusion zone; or</P>
        <P>• An observer has not sighted the animal within the exclusion zone for 15 minutes for species with shorter dive durations (i.e., small odontocetes or pinnipeds), or 30 minutes for species with longer dive durations (i.e., mysticetes and large odontocetes, including sperm, pygmy sperm, dwarf sperm, and beaked whales); or</P>
        <P>The LANGSETH crew would resume operating the airguns at full power after 15 minutes of sighting any species with short dive durations (i.e., small odontocetes or pinnipeds). Likewise, the crew would resume airgun operations at full power after 30 minutes of sighting any species with longer dive durations (i.e., mysticetes and large odontocetes, including sperm, pygmy sperm, dwarf sperm, and beaked whales).</P>

        <P>We estimate that the LANGSETH would transit outside the original 180-dB exclusion zone after an 8-minute wait period. This period is based on the 180-dB exclusion zone for the 36-airgun array towed at a depth of 12 m (39.4 ft) in relation to the average speed of the LANGSETH while operating the airguns (8.5 km/h; 5.3 mph). Because the vessel has transited away from the vicinity of the original sighting during the 8-minute period, implementing ramp-up procedures for the full array after an extended power down (i.e., transiting for an additional 35 minutes from the location of initial sighting) would not meaningfully increase the effectiveness of observing marine mammals approaching or entering the exclusion zone for the full source level and would not further minimize the potential for take. The LANGSETH<E T="03">'s</E>observers are continually monitoring the exclusion zone for the full source level while the mitigation airgun is firing. On average, observers can observe to the horizon (10 km; 6.2 mi) from the height of the LANGSETH<E T="03">'s</E>observation deck and should be able to say with a reasonable degree of confidence whether a marine mammal would be encountered within this distance before resuming airgun operations at full power.</P>
        <P>
          <E T="03">Shutdown Procedures</E>—The LANGSETH crew would shutdown the operating airgun(s) if a marine mammal is seen within or approaching the exclusion zone for the single airgun. The crew would implement a shutdown:</P>
        <P>(1) If an animal enters the exclusion zone of the single airgun after the crew has initiated a power down; or</P>
        <P>(2) If an animal is initially seen within the exclusion zone of the single airgun when more than one airgun (typically the full airgun array) is operating.</P>
        <P>Considering the conservation status for north Pacific right whales, the LANGSETH crew would shutdown the airgun(s) immediately in the unlikely event that this species is observed, regardless of the distance from the vessel. The LANGSETH would only begin ramp-up would only if the north Pacific right whale has not been seen for 30 minutes.</P>
        <P>Resuming Airgun Operations After a Shutdown—Following a shutdown in excess of eight minutes, the LANGSETH crew would initiate a ramp-up with the smallest airgun in the array (40-in<SU>3</SU>). The crew would turn on additional airguns in a sequence such that the source level of the array would increase in steps not exceeding 6 dB per five-minute period over a total duration of approximately 30 minutes. During ramp-up, the observers would monitor the exclusion zone, and if he/she sights a marine mammal, the LANGSETH crew would implement a power down or shutdown as though the full airgun array were operational.</P>
        <P>During periods of active seismic operations, there are occasions when the LANGSETH crew would need to temporarily shut down the airguns due to equipment failure or for maintenance. In this case, if the airguns are inactive longer than eight minutes, the crew would follow ramp-up procedures for a shutdown described earlier and the observers would monitor the full exclusion zone and would implement a power down or shutdown if necessary.</P>

        <P>If the full exclusion zone is not visible to the observer for at least 30 minutes prior to the start of operations in either daylight or nighttime, the LANGSETH crew would not commence ramp-up unless at least one airgun (40-in<SU>3</SU>or similar) has been operating during the interruption of seismic survey operations. Given these provisions, it is likely that the vessel's crew would not ramp up the airgun array from a complete shutdown at night or in thick fog, because the outer part of the zone<PRTPAGE P="10155"/>for that array would not be visible during those conditions.</P>
        <P>If one airgun has operated during a power down period, ramp-up to full power would be permissible at night or in poor visibility, on the assumption that marine mammals would be alerted to the approaching seismic vessel by the sounds from the single airgun and could move away. The vessel's crew would not initiate a ramp-up of the airguns if a marine mammal is sighted within or near the applicable exclusion zones during the day or close to the vessel at night.</P>
        <P>
          <E T="03">Ramp-Up Procedures</E>—Ramp-up of an airgun array provides a gradual increase in sound levels, and involves a step-wise increase in the number and total volume of airguns firing until the full volume of the airgun array is achieved. The purpose of a ramp-up is to “warn” marine mammals in the vicinity of the airguns, and to provide the time for them to leave the area and thus avoid any potential injury or impairment of their hearing abilities. The Observatory would follow a ramp-up procedure when the airgun array begins operating after an 8 minute period without airgun operations or when shut down has exceeded that period. The Observatory has used similar waiting periods (approximately eight to 10 minutes) during previous seismic surveys.</P>
        <P>Ramp-up would begin with the smallest airgun in the array (40 in<SU>3</SU>). The crew would add airguns in a sequence such that the source level of the array would increase in steps not exceeding six dB per five minute period over a total duration of approximately 30 to 35 minutes. During ramp-up, the observers would monitor the exclusion zone, and if marine mammals are sighted, the Observatory would implement a power-down or shut-down as though the full airgun array were operational.</P>
        <P>If the complete exclusion zone has not been visible for at least 30 minutes prior to the start of operations in either daylight or nighttime, the Observatory would not commence the ramp-up unless at least one airgun (40 in<SU>3</SU>or similar) has been operating during the interruption of seismic survey operations. Given these provisions, it is likely that the crew would not ramp up the airgun array from a complete shut-down at night or in thick fog, because the outer part of the exclusion zone for that array would not be visible during those conditions. If one airgun has operated during a power-down period, ramp-up to full power would be permissible at night or in poor visibility, on the assumption that marine mammals would be alerted to the approaching seismic vessel by the sounds from the single airgun and could move away. The Observatory would not initiate a ramp-up of the airguns if a marine mammal is sighted within or near the applicable exclusion zones.</P>
        <HD SOURCE="HD2">Speed and Course Alterations</HD>
        <P>If during seismic data collection, the Observatory detects marine mammals outside the exclusion zone and, based on the animal's position and direction of travel, is likely to enter the exclusion zone, the LANGSETH would change speed and/or direction if this does not compromise operational safety. Due to the limited maneuverability of the primary survey vessel, altering speed and/or course can result in an extended period of time to realign onto the transect. However, if the animal(s) appear likely to enter the exclusion zone, the LANGSETH would undertake further mitigation actions, including a power down or shut down of the airguns.</P>
        <P>We have carefully evaluated the applicant's proposed mitigation measures and have considered a range of other measures in the context of ensuring that we have prescribed the means of effecting the least practicable adverse impact on the affected marine mammal species and stocks and their habitat. Our evaluation of potential measures included consideration of the following factors in relation to one another:</P>
        <P>(1) The manner in which, and the degree to which, we expect that the successful implementation of the measure would minimize adverse impacts to marine mammals;</P>
        <P>(2) The proven or likely efficacy of the specific measure to minimize adverse impacts as planned; and</P>
        <P>(3) The practicability of the measure for applicant implementation.</P>
        <HD SOURCE="HD1">Proposed Monitoring and Reporting</HD>
        <P>In order to issue an incidental take authorization for an activity, section 101(a)(5)(D) of the MMPA states that we must set forth “requirements pertaining to the monitoring and reporting of such taking.” The Act's implementing regulations at 50 CFR 216.104 (a)(13) indicate that requests for an authorization must include the suggested means of accomplishing the necessary monitoring and reporting that would result in increased knowledge of the species and our expectations of the level of taking or impacts on populations of marine mammals present in the action area.</P>
        <HD SOURCE="HD2">Proposed Monitoring</HD>
        <P>The Observatory proposes to sponsor marine mammal monitoring during the present project to supplement the mitigation measures that require real-time monitoring, and to satisfy the monitoring requirements of the Incidental Harassment Authorization. The Observatory understands that this monitoring plan would be subject to review by us, and that we may require refinements to the plan. The Observatory planned the monitoring work as a self-contained project independent of any other related monitoring projects that may occur in the same regions at the same time. Further, the Observatory is prepared to discuss coordination of its monitoring program with any other related work that might be conducted by other groups working insofar as it is practical and desirable.</P>
        <HD SOURCE="HD2">Vessel-Based Passive Acoustic Monitoring</HD>
        <P>Passive acoustic monitoring would complement the visual mitigation monitoring program, when practicable. Visual monitoring typically is not effective during periods of poor visibility or at night, and even with good visibility, is unable to detect marine mammals when they are below the surface or beyond visual range. Passive acoustical monitoring can be used in conjunction with visual observations to improve detection, identification, and localization of cetaceans. The passive acoustic monitoring would serve to alert visual observers (if on duty) when vocalizing cetaceans are detected. It is only useful when marine mammals call, but it can be effective either by day or by night, and does not depend on good visibility. The acoustic observer would monitor the system in real time so that he/she can advise the visual observers if they acoustic detect cetaceans.</P>

        <P>The passive acoustic monitoring system consists of hardware (i.e., hydrophones) and software. The “wet end” of the system consists of a towed hydrophone array that is connected to the vessel by a tow cable. The tow cable is 250 m (820.2 ft) long, and the hydrophones are fitted in the last 10 m (32.8 ft) of cable. A depth gauge is attached to the free end of the cable, and the cable is typically towed at depths less than 20 m (65.6 ft). The LANGSETH crew would deploy the array from a winch located on the back deck. A deck cable would connect the tow cable to the electronics unit in the main computer lab where the acoustic station, signal conditioning, and processing system would be located. The acoustic signals received by the hydrophones are amplified, digitized, and then processed by the Pamguard software. The system<PRTPAGE P="10156"/>can detect marine mammal vocalizations at frequencies up to 250 kHz.</P>
        <P>One acoustic observer, an expert bioacoustician with primary responsibility for the passive acoustic monitoring system would be aboard the LANGSETH in addition to the four visual observers. The acoustic observer would monitor the towed hydrophones 24 hours per day during airgun operations and during most periods when the LANGSETH is underway while the airguns are not operating. However, passive acoustic monitoring may not be possible if damage occurs to both the primary and back-up hydrophone arrays during operations. The primary passive acoustic monitoring streamer on the LANGSETH is a digital hydrophone streamer. Should the digital streamer fail, back-up systems should include an analog spare streamer and a hull-mounted hydrophone.</P>
        <P>One acoustic observer would monitor the acoustic detection system by listening to the signals from two channels via headphones and/or speakers and watching the real-time spectrographic display for frequency ranges produced by cetaceans. The observer monitoring the acoustical data would be on shift for one to six hours at a time. The other observers would rotate as an acoustic observer, although the expert acoustician would be on passive acoustic monitoring duty more frequently.</P>
        <P>When the acoustic observer detects a vocalization while visual observations are in progress, the acoustic observer on duty would contact the visual observer immediately, to alert him/her to the presence of cetaceans (if they have not already been seen), so that the vessel's crew can initiate a power down or shutdown, if required. The observer would enter the information regarding the call into a database. Data entry would include an acoustic encounter identification number, whether it was linked with a visual sighting, date, time when first and last heard and whenever any additional information was recorded, position and water depth when first detected, bearing if determinable, species or species group (e.g., unidentified dolphin, sperm whale), types and nature of sounds heard (e.g., clicks, continuous, sporadic, whistles, creaks, burst pulses, strength of signal, etc.), and any other notable information. The acoustic detection can also be recorded for further analysis.</P>
        <HD SOURCE="HD2">Observer Data and Documentation</HD>
        <P>Observers would record data to estimate the numbers of marine mammals exposed to various received sound levels and to document apparent disturbance reactions or lack thereof. They would use the data to estimate numbers of animals potentially `taken' by harassment (as defined in the MMPA). They will also provide information needed to order a power down or shut down of the airguns when a marine mammal is within or near the exclusion zone.</P>
        <P>When an observer makes a sighting, they will record the following information:</P>
        <P>1. Species, group size, age/size/sex categories (if determinable), behavior when first sighted and after initial sighting, heading (if consistent), bearing and distance from seismic vessel, sighting cue, apparent reaction to the airguns or vessel (e.g., none, avoidance, approach, paralleling, etc.), and behavioral pace.</P>
        <P>2. Time, location, heading, speed, activity of the vessel, sea state, visibility, and sun glare.</P>
        <P>The observer will record the data listed under (2) at the start and end of each observation watch, and during a watch whenever there is a change in one or more of the variables.</P>
        <P>Observers will record all observations and power downs or shutdowns in a standardized format and will enter data into an electronic database. The observers will verify the accuracy of the data entry by computerized data validity checks as the data are entered and by subsequent manual checking of the database. These procedures will allow the preparation of initial summaries of data during and shortly after the field program, and will facilitate transfer of the data to statistical, graphical, and other programs for further processing and archiving.</P>
        <P>Results from the vessel-based observations will provide:</P>
        <P>1. The basis for real-time mitigation (airgun power down or shutdown).</P>
        <P>2. Information needed to estimate the number of marine mammals potentially taken by harassment, which the Observatory must report to the Office of Protected Resources.</P>
        <P>3. Data on the occurrence, distribution, and activities of marine mammals and turtles in the area where the Observatory would conduct the seismic study.</P>
        <P>4. Information to compare the distance and distribution of marine mammals and turtles relative to the source vessel at times with and without seismic activity.</P>
        <P>5. Data on the behavior and movement patterns of marine mammals detected during non-active and active seismic operations.</P>
        <HD SOURCE="HD2">Proposed Reporting</HD>
        <P>The Observatory would submit a report to us and to the Foundation within 90 days after the end of the cruise. The report would describe the operations that were conducted and sightings of marine mammals and turtles near the operations. The report would provide full documentation of methods, results, and interpretation pertaining to all monitoring. The 90-day report would summarize the dates and locations of seismic operations, and all marine mammal sightings (dates, times, locations, activities, associated seismic survey activities). The report would also include estimates of the number and nature of exposures that could result in “takes” of marine mammals by harassment or in other ways.</P>

        <P>In the unanticipated event that the specified activity clearly causes the take of a marine mammal in a manner not permitted by the authorization (if issued), such as an injury, serious injury, or mortality (e.g., ship-strike, gear interaction, and/or entanglement), the Observatory shall immediately cease the specified activities and immediately report the incident to the Incidental Take Program Supervisor, Permits and Conservation Division, Office of Protected Resources, NMFS, at 301-427-8401 and/or by email to<E T="03">Jolie.Harrison@noaa.gov</E>and<E T="03">ITP.Cody@noaa.gov.</E>The report must include the following information:</P>
        <P>• Time, date, and location (latitude/longitude) of the incident;</P>
        <P>• Name and type of vessel involved;</P>
        <P>• Vessel's speed during and leading up to the incident;</P>
        <P>• Description of the incident;</P>
        <P>• Status of all sound source use in the 24 hours preceding the incident;</P>
        <P>• Water depth;</P>
        <P>• Environmental conditions (e.g., wind speed and direction, Beaufort sea state, cloud cover, and visibility);</P>
        <P>• Description of all marine mammal observations in the 24 hours preceding the incident;</P>
        <P>• Species identification or description of the animal(s) involved;</P>
        <P>• Fate of the animal(s); and</P>
        <P>• Photographs or video footage of the animal(s) (if equipment is available).</P>
        <P>The Observatory shall not resume its activities until we are able to review the circumstances of the prohibited take. We shall work with the Observatory to determine what is necessary to minimize the likelihood of further prohibited take and ensure MMPA compliance. The Observatory may not resume their activities until notified by us via letter, email, or telephone.</P>

        <P>In the event that the Observatory discovers an injured or dead marine<PRTPAGE P="10157"/>mammal, and the lead visual observer determines that the cause of the injury or death is unknown and the death is relatively recent (i.e., in less than a moderate state of decomposition as we describe in the next paragraph), the Observatory will immediately report the incident to the Incidental Take Program Supervisor, Permits and Conservation Division, Office of Protected Resources, at 301-427-8401 and/or by email to<E T="03">Jolie.Harrison@noaa.gov</E>and<E T="03">ITP.Cody@noaa.gov.</E>The report must include the same information identified in the paragraph above this section. Activities may continue while we review the circumstances of the incident. We would work with the Observatory to determine whether modifications in the activities are appropriate.</P>

        <P>In the event that the Observatory discovers an injured or dead marine mammal, and the lead visual observer determines that the injury or death is not associated with or related to the authorized activities (e.g., previously wounded animal, carcass with moderate to advanced decomposition, or scavenger damage), the Observatory would report the incident to the Incidental Take Program Supervisor, Permits and Conservation Division, Office of Protected Resources, at 301-427-8401 and/or by email to<E T="03">Jolie.Harrison@noaa.gov</E>and<E T="03">ITP.Cody@noaa.gov,</E>within 24 hours of the discovery. The Observatory would provide photographs or video footage (if available) or other documentation of the stranded animal sighting to us.</P>
        <HD SOURCE="HD1">Estimated Take by Incidental Harassment</HD>
        <P>Except with respect to certain activities not pertinent here, the MMPA defines “harassment” as: 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>
        <P>We propose to authorize take by Level B harassment for the proposed seismic survey. Acoustic stimuli (i.e., increased underwater sound) generated during the operation of the seismic airgun array may have the potential to result in the behavioral disturbance of some marine mammals. There is no evidence that planned activities could result in serious injury or mortality within the specified geographic area for the requested authorization. The required mitigation and monitoring measures would minimize any potential risk for serious injury or mortality.</P>
        <P>The following sections describe the Observatory's methods to estimate take by incidental harassment and present their estimates of the numbers of marine mammals that could be affected during the proposed seismic program. The estimates are based on a consideration of the number of marine mammals that could be harassed by seismic operations with the 36-airgun array during approximately 5,572 km<SU>2</SU>(2,151 mi<SU>2</SU>) of transect lines on the Mid-Atlantic Ridge in the north Atlantic Ocean, as depicted in Figure 1 of the application.</P>
        <P>We assume that during simultaneous operations of the airgun array and the other sources, any marine mammals close enough to be affected by the echosounder and sub-bottom profiler would already be affected by the airguns. However, whether or not the airguns are operating simultaneously with the other sources, we expect that the marine mammals would exhibit no more than short-term and inconsequential responses to the echosounder and profiler given their characteristics (e.g., narrow downward-directed beam) and other considerations described previously. Based on the best available information, we do not consider that these reactions constitute a “take” (NMFS, 2001). Therefore, the Observatory did not provide any additional allowance for animals that could be affected by sound sources other than the airguns.</P>
        <P>
          <E T="03">Ensonified Area Calculations</E>—Because the Observatory assumes that the LANGSETH may need repeat some tracklines, accommodate the turning of the vessel, address equipment malfunctions, or conduct equipment testing to complete the survey; they have increased the proposed number of line-kilometers for the seismic operations by 25 percent (i.e., contingency lines).</P>
        <P>
          <E T="03">Density Information</E>—The Observatory based the density estimates on information calculated from sightings, effort, mean group sizes, and values for f(0) for the southern part of the survey area in Waring et al. (2008), which extends from the Azores at approximately 38° N to 53° N. The allocated densities calculated for undifferentiated “common/striped dolphins” to common and striped dolphins in proportion to the calculated densities of the two species. The density calculated for “unidentified dolphin” was allocated to bottlenose, Atlantic spotted, and Risso's dolphins, species that could occur in the proposed survey area based on their presence in the Azores, in proportion to the number of sightings in the OBIS database for those species around the Azores. The density calculated for “unidentified small whale” was allocated to the false killer whale, the one small whale species that could occur in the proposed survey area based on its presence in the Azores. The four “long-finned/short-finned pilot whales” sighted in the southern part of the survey area by Waring et al. (2008) were assumed to be short-finned pilot whales based on OBIS sightings around the Azores. The density calculated for the one “sei/Bryde's whale” sighting in the southern part of the survey area was allocated to sei and Bryde's whales in equal proportions. The authors' calculated value of f(0) for the sei whale was used for calculating densities of Bryde's, fin, and blue whales, and that for “small Delphinidae” was used for calculating densities of<E T="03">Mesoplodon spp.,</E>dolphins, the false killer whale, and the short-finned pilot whale. Because the survey effort in the southern stratum of Waring<E T="03">et al.</E>(2008) is limited (1,047 km; 650 mi), the survey area is north of the proposed seismic area (38-52° N versus 36-36.5° N), and the survey was conducted during a somewhat different season (June versus April-May), there is some uncertainty about the representativeness of the data and the assumptions used in the calculations.</P>
        <P>
          <E T="03">Exposure Estimation</E>—The Observatory estimated the number of different individuals that could be exposed to airgun sounds with received levels greater than or equal to 160 dB re: 1 µPa on one or more occasions by considering the total marine area that would be within the 160-dB radius around the operating airgun array on at least one occasion and the expected density of marine mammals. The number of possible exposures (including repeat exposures of the same individuals) can be estimated by considering the total marine area that would be within the 160-dB radius around the operating airguns, excluding areas of overlap. Some individuals may be exposed multiple times since the survey tracklines are spaced close together, however, it is unlikely that a particular animal would stay in the area during the entire survey.</P>
        <P>The number of different individuals potentially exposed to received levels greater than or equal to 160 re: 1 µPa (rms) was calculated by multiplying:</P>
        <P>(1) The expected species density (in number/km<SU>2</SU>), times</P>

        <P>(2) The anticipated area to be ensonified to that level during airgun operations (5,571 km<SU>2</SU>; (2,151 mi<SU>2</SU>).<PRTPAGE P="10158"/>
        </P>
        <P>The Observatory's estimates of exposures to various sound levels assume that the proposed surveys would be carried out in full (i.e., approximately 20 days of seismic airgun operations), however, the ensonified areas calculated using the planned number of line-kilometers have been increased by 25 percent to accommodate lines that may need to be repeated, equipment testing, account for repeat exposure, etc. As is typical during offshore ship surveys, inclement weather and equipment malfunctions are likely to cause delays and may limit the number of useful line-kilometers of seismic operations that can be undertaken.</P>
        <GPOTABLE CDEF="s100,17,14,12,12" COLS="5" OPTS="L2,i1">

          <TTITLE>Table 3—Estimates of the Possible Numbers of Marine Mammals Exposed to Sound Levels Greater Than or Equal to 160<E T="01">d</E>B re: 1 μP<E T="01">a</E>During the Proposed Seismic Survey Over the Mid-Atlantic Ridge in the North Atlantic Ocean, During April Through June, 2013</TTITLE>
          <BOXHD>
            <CHED H="1">Species</CHED>
            <CHED H="1">Estimated number of individuals exposed<LI>to sound levels</LI>
              <LI>≥160 dB re: 1 µPa<SU>1</SU>
              </LI>
            </CHED>
            <CHED H="1">Requested<LI>or adjusted take</LI>
              <LI>authorization<SU>2</SU>
              </LI>
            </CHED>
            <CHED H="1">Regional<LI>population<SU>3</SU>
              </LI>
            </CHED>
            <CHED H="1">Approx.<LI>percent of</LI>
              <LI>regional</LI>
              <LI>population<SU>3</SU>
              </LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="22">Mysticetes:</ENT>
          </ROW>
          <ROW>
            <ENT I="03">North Atlantic right whale</ENT>
            <ENT>0</ENT>
            <ENT>0</ENT>
            <ENT>0</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Humpback whale</ENT>
            <ENT>0</ENT>
            <ENT>
              <SU>4</SU>2</ENT>
            <ENT>0</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Minke whale</ENT>
            <ENT>0</ENT>
            <ENT>
              <SU>4</SU>3</ENT>
            <ENT>0</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Bryde's whale</ENT>
            <ENT>1</ENT>
            <ENT>1</ENT>
            <ENT>N/A</ENT>
            <ENT>N/A</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Sei whale</ENT>
            <ENT>1</ENT>
            <ENT>1</ENT>
            <ENT>13,000</ENT>
            <ENT>0.01</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Fin whale</ENT>
            <ENT>25</ENT>
            <ENT>25</ENT>
            <ENT>24,887</ENT>
            <ENT>0.10</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Blue whale</ENT>
            <ENT>8</ENT>
            <ENT>8</ENT>
            <ENT>937</ENT>
            <ENT>0.89</ENT>
          </ROW>
          <ROW>
            <ENT I="22">Odontocetes</ENT>
            <ENT/>
            <ENT>21</ENT>
            <ENT/>
            <ENT>0.16</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Sperm whale</ENT>
            <ENT>21</ENT>
            <ENT/>
            <ENT>13,190</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="03">Pygmy sperm whale</ENT>
            <ENT>0</ENT>
            <ENT>0</ENT>
            <ENT>395</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Dwarf sperm whale</ENT>
            <ENT>0</ENT>
            <ENT>0</ENT>
            <ENT>395</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Cuvier's beaked whale</ENT>
            <ENT>0</ENT>
            <ENT>
              <SU>4</SU>7</ENT>
            <ENT>3,513</ENT>
            <ENT>0.2</ENT>
          </ROW>
          <ROW>
            <ENT I="03">
              <E T="03">Mesoplodon spp.</E>
            </ENT>
            <ENT/>
            <ENT/>
            <ENT/>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="03">True's beaked whale</ENT>
            <ENT/>
            <ENT/>
            <ENT/>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="03">Gervais beaked whale</ENT>
            <ENT>39</ENT>
            <ENT>39</ENT>
            <ENT/>
            <ENT>1.12</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Sowerby's beaked whale</ENT>
            <ENT/>
            <ENT/>
            <ENT/>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="03">Blainville's beaked whale</ENT>
            <ENT/>
            <ENT/>
            <ENT>3,502</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="03">Northern bottlenose whale</ENT>
            <ENT>0</ENT>
            <ENT>
              <SU>4</SU>4</ENT>
            <ENT>∼40,000</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Rough-toothed dolphin</ENT>
            <ENT>0</ENT>
            <ENT>0</ENT>
            <ENT>N/A</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Common bottlenose dolphin</ENT>
            <ENT>47</ENT>
            <ENT>47</ENT>
            <ENT>81,588</ENT>
            <ENT>0.06</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Pantropical spotted dolphin</ENT>
            <ENT>0</ENT>
            <ENT>0</ENT>
            <ENT>4,439</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Atlantic spotted dolphin</ENT>
            <ENT>112</ENT>
            <ENT>112</ENT>
            <ENT>50,978</ENT>
            <ENT>0.22</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Striped dolphin</ENT>
            <ENT>1,034</ENT>
            <ENT>1,034</ENT>
            <ENT>94,462</ENT>
            <ENT>1.09</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Short-beaked common dolphin</ENT>
            <ENT>2,115</ENT>
            <ENT>2,115</ENT>
            <ENT>120,741</ENT>
            <ENT>1.75</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Risso's dolphin</ENT>
            <ENT>21</ENT>
            <ENT>21</ENT>
            <ENT>20,479</ENT>
            <ENT>0.10</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Pygmy killer whale</ENT>
            <ENT>0</ENT>
            <ENT>0</ENT>
            <ENT>N/A</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">False killer whale</ENT>
            <ENT>7</ENT>
            <ENT>7</ENT>
            <ENT>N/A</ENT>
            <ENT>N/A</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Killer whale</ENT>
            <ENT>0</ENT>
            <ENT>
              <SU>4</SU>5</ENT>
            <ENT>N/A</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Long-finned pilot whale</ENT>
            <ENT>0</ENT>
            <ENT>0</ENT>
            <ENT>780,000</ENT>
            <ENT>0</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Short-finned pilot whale</ENT>
            <ENT>674</ENT>
            <ENT>674</ENT>
            <ENT>780,000</ENT>
            <ENT>0.09</ENT>
          </ROW>
          <TNOTE>N/A = Not Available.</TNOTE>
          <TNOTE>
            <SU>1</SU>Estimates are based on densities in Table 2 and an ensonified area of (5,571 km<SU>2</SU>; (2,151 mi<SU>2</SU>)</TNOTE>
          <TNOTE>
            <SU>2</SU>Requested or adjusted take includes a 25 percent contingency for repeated exposures due to the overlap of parallel survey tracks.</TNOTE>
          <TNOTE>
            <SU>3</SU>Regional population size estimates are from Table 2.</TNOTE>
          <TNOTE>
            <SU>4</SU>Requested take authorization increased to group size for species for which densities were not calculated but for which there were OBIS sightings around the Azores.</TNOTE>
        </GPOTABLE>
        <HD SOURCE="HD1">Encouraging and Coordinating Research</HD>
        <P>The Observatory would coordinate the planned marine mammal monitoring program associated with the seismic survey on the Mid-Atlantic Ridge in the north Atlantic Ocean with other parties that may have interest in the area and/or may be conducting marine mammal studies in the same region during the seismic surveys.</P>
        <HD SOURCE="HD1">Negligible Impact and Small Numbers Analysis and Determination</HD>
        <P>We have defined “negligible impact” in 50 CFR 216.103 as “* * * an impact resulting from the specified activity that cannot be reasonably expected to, and is not reasonably likely to, adversely affect the species or stock through effects on annual rates of recruitment or survival.” In making a negligible impact determination, we consider:</P>
        <P>(1) The number of anticipated injuries, serious injuries, or mortalities;</P>
        <P>(2) The number, nature, and intensity, and duration of Level B harassment (all relatively limited); and</P>
        <P>(3) The context in which the takes occur (i.e., impacts to areas of significance, impacts to local populations, and cumulative impacts when taking into account successive/contemporaneous actions when added to baseline data);</P>
        <P>(4) The status of stock or species of marine mammals (i.e., depleted, not depleted, decreasing, increasing, stable, impact relative to the size of the population);</P>
        <P>(5) Impacts on habitat affecting rates of recruitment/survival; and</P>
        <P>(6) The effectiveness of monitoring and mitigation measures.</P>

        <P>For reasons stated previously in this document and based on the following factors, the specified activities associated with the marine seismic surveys are not likely to cause permanent threshold shift, or other non-auditory injury, serious injury, or death. They include:<PRTPAGE P="10159"/>
        </P>
        <P>(1) The likelihood that, given sufficient notice through relatively slow ship speed, we expect marine mammals to move away from a noise source that is annoying prior to its becoming potentially injurious;</P>
        <P>(2) The potential for temporary or permanent hearing impairment is relatively low and that we would likely avoid this impact through the incorporation of the required monitoring and mitigation measures (including power-downs and shutdowns); and</P>
        <P>(3) The likelihood that marine mammal detection ability by trained visual observers is high at close proximity to the vessel.</P>
        <P>We do not anticipate that any injuries, serious injuries, or mortalities would occur as a result of the Observatory's planned marine seismic surveys, and we do not propose to authorize injury, serious injury or mortality for this survey. We anticipate only behavioral disturbance to occur during the conduct of the survey activities.</P>
        <P>Table 4 in this document outlines the number of requested Level B harassment takes that we anticipate as a result of these activities. Due to the nature, degree, and context of Level B (behavioral) harassment anticipated and described (see “Potential Effects on Marine Mammals” section in this notice), we do not expect the activity to impact rates of recruitment or survival for any affected species or stock.</P>
        <P>Further, the seismic surveys would not take place in areas of significance for marine mammal feeding, resting, breeding, or calving and would not adversely impact marine mammal habitat.</P>

        <P>Many animals perform vital functions, such as feeding, resting, traveling, and socializing, on a diel cycle (i.e., 24 hour cycle). Behavioral reactions to noise exposure (such as disruption of critical life functions, displacement, or avoidance of important habitat) are more likely to be significant if they last more than one diel cycle or recur on subsequent days (Southall<E T="03">et al.,</E>2007). While we anticipate that the seismic operations would occur on consecutive days, the estimated duration of the survey would last no more than 20 days. Additionally, the seismic survey would be increasing sound levels in the marine environment in a relatively small area surrounding the vessel (compared to the range of the animals), which is constantly travelling over distances, and some animals may only be exposed to and harassed by sound for shorter less than day.</P>
        <P>Of the 28 marine mammal species under our jurisdiction that are known to occur or likely to occur in the study area, six of these species are listed as endangered under the ESA, including: The blue, fin, humpback, north Atlantic right, sei, and sperm whales. These species are also categorized as depleted under the MMPA. With the exception of the north Atlantic right whale, the Observatory has requested authorized take for these listed species.</P>
        <P>As mentioned previously, we estimate that 28 species of marine mammals under our jurisdiction could be potentially affected by Level B harassment over the course of the proposed authorization. For each species, these take numbers are small (most estimates are less than or equal to two percent) relative to the regional or overall population size and we have provided the regional population estimates for the marine mammal species that may be taken by Level B harassment in Table 4 in this document.</P>

        <P>Our practice has been to apply the 160 dB re: 1 µPa received level threshold for underwater impulse sound levels to determine whether take by Level B harassment occurs. Southall<E T="03">et al.</E>(2007) provides a severity scale for ranking observed behavioral responses of both free-ranging marine mammals and laboratory subjects to various types of anthropogenic sound (see Table 4 in Southall<E T="03">et al.</E>[2007]).</P>
        <P>We have preliminarily determined, provided that the aforementioned mitigation and monitoring measures are implemented, that the impact of conducting a proposed survey on the Mid-Atlantic Ridge in the north Atlantic Ocean in international waters, from April 2013 through June 2013, may result, at worst, in a modification in behavior and/or low-level physiological effects (Level B harassment) of certain species of marine mammals.</P>
        <P>While these species may make behavioral modifications, including temporarily vacating the area during the operation of the airgun(s) to avoid the resultant acoustic disturbance, the availability of alternate areas within these areas and the short and sporadic duration of the research activities, have led us to preliminary determine that this action would have a negligible impact on the species in the specified geographic region.</P>
        <P>Based on the analysis contained herein of the likely effects of the specified activity on marine mammals and their habitat, and taking into consideration the implementation of the mitigation and monitoring measures, we preliminarily find that the Observatory's planned research activities would result in the incidental take of small numbers of marine mammals, by Level B harassment only, and that the required measures mitigate impacts to affected species or stocks of marine mammals to the lowest level practicable.</P>
        <HD SOURCE="HD1">Impact on Availability of Affected Species or Stock for Taking for Subsistence Uses</HD>
        <P>Section 101(a)(5)(D) of the Marine Mammal Protection Act also requires us to determine that the authorization would not have an unmitigable adverse effect on the availability of marine mammal species or stocks for subsistence use. There are no relevant subsistence uses of marine mammals in the study area (on the Mid-Atlantic Ridge in the north Atlantic Ocean in international waters) that implicate section 101(a)(5)(D) of the Marine Mammal Protection Act.</P>
        <HD SOURCE="HD1">Endangered Species Act</HD>
        <P>Of the species of marine mammals that may occur in the proposed survey area, several are listed as endangered under the Endangered Species Act, including the blue, fin, humpback, north Atlantic right, sei, and sperm whales. The Observatory did not request take of endangered north Atlantic right whales because of the low likelihood of encountering these species during the cruise.</P>

        <P>Under section 7 of the Act, the Foundation has initiated formal consultation with the Service's, Office of Protected Resources, Endangered Species Act Interagency Cooperation Division, on this proposed seismic survey. We (i.e., National Marine Fisheries Service, Office of Protected Resources, Permits and Conservation Division), have also initiated formal consultation under section 7 of the Act with the Endangered Species Act Interagency Cooperation Division to obtain a Biological Opinion (Opinion) evaluating the effects of issuing an incidental harassment authorization for threatened and endangered marine mammals and, if appropriate, authorizing incidental take. Both agencies would conclude the formal section 7 consultation (with a single Biological Opinion for the Foundation's Division of Ocean Sciences and NMFS' Office of Protected Resources, Permits and Conservation Division federal actions) prior to making a determination on whether or not to issue the authorization. If we issue the take authorization, the Foundation and the Observatory must comply with the mandatory Terms and Conditions of the Opinion's Incidental Take Statement which would incorporate the mitigation and monitoring requirements included<PRTPAGE P="10160"/>in the Incidental Harassment Authorization.</P>
        <HD SOURCE="HD1">National Environmental Policy Act (NEPA)</HD>

        <P>To meet our NEPA requirements for the issuance of an IHA to the Observatory, we intend to prepare an Environmental Assessment (EA) titled “Issuance of an Incidental Harassment Authorization to the Lamont-Doherty Earth Observatory to Take Marine Mammals by Harassment Incidental to a Marine Geophysical on the Mid-Atlantic Ridge in the north Atlantic Ocean, from April 2013 through June 2013.” This EA would incorporate as appropriate the Foundation's Environmental Analysis Pursuant To Executive Order 12114 (NSF, 2010) titled, “Marine geophysical survey by the R/V MARCUS G.<E T="03">Langseth</E>on the mid-Atlantic Ridge, April-May 2013,” by reference pursuant to 40 CFR 1502.21 and NOAA Administrative Order (NAO) 216-6 § 5.09(d). Prior to making a final decision on the IHA application, we would decide whether or not to issue a Finding of No Significant Impact (FONSI).</P>
        <P>The Foundation's environmental analysis is available for review at the addresses set forth earlier in this notice. This notice and the documents it references provide all relevant environmental information related to our proposal to issue the IHA. We invite the public's comment and will consider any comments related to environmental effects related to the proposed issuance of the IHA submitted in response to this as we conduct and finalize our NEPA analysis.</P>
        <HD SOURCE="HD1">Proposed Authorization</HD>
        <P>As a result of these preliminary determinations, we propose to authorize the take of marine mammals incidental to the Observatory's proposed marine seismic surveys on the Mid-Atlantic Ridge in the north Atlantic Ocean from April 2013, through June 2013, provided the previously mentioned mitigation, monitoring, and reporting requirements are incorporated. The duration of the incidental harassment authorization would not exceed one year from the date of its issuance.</P>
        <HD SOURCE="HD1">Information Solicited</HD>

        <P>We request interested persons to submit comments and information concerning this proposed project and our preliminary determination of issuing a take authorization (see<E T="02">ADDRESSES</E>). Concurrent with the publication of this notice in the<E T="04">Federal Register</E>, we will forward copies of this application to the Marine Mammal Commission and its Committee of Scientific Advisors.</P>
        <SIG>
          <DATED>Dated: February 6, 2013.</DATED>
          <NAME>Matthew J. Brookhart,</NAME>
          <TITLE>Acting Director, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03321 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DELAWARE RIVER BASIN COMMISSION</AGENCY>
        <SUBJECT>Notice of Commission Meeting and Public Hearing</SUBJECT>
        
        <P>Notice is hereby given that the Delaware River Basin Commission will hold a public hearing on Tuesday, March 5, 2013. A business meeting will be held the following day on Wednesday, March 6, 2013. Both the hearing and business meeting are open to the public and will be held at the Commission's office building located at 25 State Police Drive, West Trenton, New Jersey.</P>
        <P>
          <E T="03">Public Hearing.</E>The public hearing on March 5, 2013 will run from 1:00 p.m. until approximately 4:00 p.m. The list of projects scheduled for hearing, with descriptions, is currently available in a long form of this notice posted on the Commission's Web site,<E T="03">www.drbc.net</E>. Draft dockets and resolutions for hearing items will be posted on the Web site approximately ten days prior to the hearing date. Because hearings on particular projects may be postponed to allow additional time for the commission's review, interested parties are advised to check the Web site periodically prior to the hearing date. Postponements, if any, will be duly noted there.</P>
        <P>
          <E T="03">Public Meeting.</E>The business meeting on March 6, 2013 will begin at 12:15 p.m. and will include the following items: adoption of the Minutes of the Commission's December 5, 2012 business meeting, announcements of upcoming meetings and events, a report on hydrologic conditions, reports by the Executive Director and the Commission's General Counsel, consideration of items for which a hearing has been completed, and a public dialogue session. The Commissioners also may consider action on matters not subject to a public hearing.</P>
        <P>There will be no opportunity for additional public comments at the March 6 business meeting on items for which a hearing was completed on March 5 or a previous date. Commission consideration on March 6 of items for which the public hearing is closed may result in either approval of the docket or resolution as proposed, approval with changes, denial, or deferral. When the commissioners defer an action, they may announce an additional period for written comment on the item, with or without an additional hearing date, or they may take additional time to consider the input they have already received without requesting further public input. Any deferred items will be considered for action at a public meeting of the commission on a future date.</P>
        <P>
          <E T="03">Advance sign-up for oral comment.</E>Individuals who wish to comment for the record at the public hearing on March 5th or to address the Commissioners informally during the public dialogue portion of the meeting on March 6 are asked to sign up in advance by contacting Ms. Paula Schmitt of the Commission staff, at<E T="03">paula.schmitt@drbc.state.nj.us</E>or by phoning Ms. Schmitt at 609-883-9500 ext. 224.</P>
        <P>
          <E T="03">Addresses for written comment.</E>Written comment on items scheduled for hearing may be delivered by hand at the public hearing or submitted in advance of the hearing date to: Commission Secretary, P.O. Box 7360, 25 State Police Drive, West Trenton, NJ 08628; by fax to Commission Secretary, DRBC at 609-883-9522 or by email to<E T="03">paula.schmitt@drbc.state.nj.us</E>. Written comment on dockets should also be furnished directly to the Project Review Section at the above address or fax number or by email to<E T="03">william.muszynski@drbc.state.nj.us</E>.</P>
        <P>
          <E T="03">Accommodations for Special Needs.</E>Individuals in need of an accommodation as provided for in the Americans with Disabilities Act who wish to attend the informational meeting, conference session or hearings should contact the Commission Secretary directly at 609-883-9500 ext. 203 or through the Telecommunications Relay Services (TRS) at 711, to discuss how we can accommodate your needs.</P>
        <P>
          <E T="03">Updates.</E>Items scheduled for hearing are occasionally postponed to allow more time for the Commission to consider them. Other meeting items also are subject to change. Please check the Commission's Web site,<E T="03">www.drbc.net,</E>closer to the meeting date for changes that may be made after the deadline for filing this notice.</P>
        <P>
          <E T="03">Additional Information, Contacts.</E>The list of projects scheduled for hearing, with descriptions, is currently available in a long form of this notice posted on the Commission's Web site,<E T="03">www.drbc.net.</E>Draft dockets and resolutions for hearing items will be posted as hyperlinks from the notice at<PRTPAGE P="10161"/>the same location approximately ten days prior to the hearing date. Additional public records relating to hearing items may be examined at the Commission's offices by appointment by contacting Carol Adamovic, 609-883-9500, ext. 249. For other questions concerning hearing items, please contact Project Review Section Assistant Victoria Lawson at 609-883-9500, ext. 216.</P>
        <SIG>
          <DATED>Dated: February 7, 2013.</DATED>
          <NAME>Pamela M. Bush,</NAME>
          <TITLE>Commission Secretary and Assistant General Counsel.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-03281 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6360-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF EDUCATION</AGENCY>
        <SUBJECT>National Advisory Committee on Institutional Quality and Integrity (NACIQI)</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>National Advisory Committee on Institutional Quality and Integrity, Office of Postsecondary Education, U.S. Department of Education.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Announcement of an open meeting of the National Advisory Committee on Institutional Quality and Integrity (NACIQI) and information pertaining to members of the public submitting third-party written and oral comments.</P>
        </ACT>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>U.S. Department of Education, Office of Postsecondary Education, 1990 K Street NW., Room 8072, Washington, DC 20006.</P>
          <P>
            <E T="03">NACIQI'S Statutory Authority and Function:</E>The NACIQI is established under Section 114 of the HEA of 1965, as amended, 20 U.S.C. 1011c. The NACIQI advises the Secretary of Education about:</P>
          <P>• The establishment and enforcement of the criteria for recognition of accrediting agencies or associations under Subpart 2, Part H, Title IV, of the HEA, as amended.</P>
          <P>• The recognition of specific accrediting agencies or associations or a specific State approval agency.</P>
          <P>• The preparation and publication of the list of nationally recognized accrediting agencies and associations.</P>
          <P>• The eligibility and certification process for institutions of higher education under Title IV, of the HEA, together with recommendations for improvement in such process.</P>
          <P>• The relationship between (1) accreditation of institutions of higher education and the certification and eligibility of such institutions, and (2) State licensing responsibilities with respect to such institutions.</P>
          <P>• Any other advisory function relating to accreditation and institutional eligibility that the Secretary may prescribe.</P>
        </ADD>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This notice sets forth the agenda for the June 6-7, 2013 meeting of the National Advisory Committee on Institutional Quality and Integrity (NACIQI); and provides information to members of the public on submitting written comments and on requesting to make oral comments at the meeting. The notice of this meeting is required under Section 10(a)(2) of the Federal Advisory Committee Act (FACA) and Section 114(d)(1)(B) of the Higher Education Act (HEA) of 1965, as amended.</P>
          <P>
            <E T="03">Meeting Date and Place:</E>The NACIQI meeting will be held on June 6-7, 2013, from approximately 8:00 a.m. to approximately 5:30 p.m., at a location to be determined in the Washington DC area. The exact location will be published in the<E T="04">Federal Register</E>and on the Department's Web site at<E T="03">http://www2.ed.gov/about/bdscomm/list/naciqi.html#meetings</E>by May 6, 2013.</P>
          <P>
            <E T="03">Meeting Agenda:</E>Below is a list of agencies, including their current and requested scopes of recognition, scheduled for review during the June 6-7, 2013 meeting:</P>
          <HD SOURCE="HD1">Petitions for Continued Recognition</HD>
          <HD SOURCE="HD2">Accrediting Agencies</HD>
          <P>1. Accrediting Council for Continuing Education and Training (ACCET) (Current Scope: The accreditation of institutions of higher education throughout the United States that offer non-collegiate continuing education programs and those that offer occupational associate degree programs and those that offer such programs via distance education.)</P>
          <P>2. Accreditation Council on Optometric Education (ACOE) (Current Scope: The accreditation in the United States of professional optometric degree programs, optometric technician (associate degree) programs, and optometric residency programs, and for the preaccreditation categories of Preliminary Approval for professional optometric degree programs and Candidacy Pending for optometric residency programs in Department of Veterans Affairs facilities.)</P>
          <P>3. Association of Advanced Rabbinical and Talmudic Schools (AARTS) (Current Scope: The accreditation and pre-accreditation (“Correspondent” and “Candidate”) within the United States of advanced rabbinical and Talmudic schools.) (Requested Scope: The accreditation and pre-accreditation (“Correspondent” and “Candidate”) within the United States of advanced rabbinical and Talmudic schools which grant postsecondary degrees such as Baccalaureate, Masters, Doctorate, First Rabbinic and First Talmudic degrees.)</P>
          <P>4. Commission on Accreditation of Healthcare Management Education (CAHME) (Current Scope: The accreditation throughout the United States of graduate programs in healthcare management.)</P>
          <P>5. National Association of Schools of Dance, Commission on Accreditation (NASD) (Current Scope: The accreditation throughout the United States of freestanding institutions, and units offering dance and dance-related programs (both degree- and non-degree-granting), including those offered via distance education.) (Requested Scope: The accreditation throughout the United States of freestanding institutions, and units offering dance and dance-related programs (both degree- and non-degree-granting), including those offered via distance and correspondence education.)</P>
          <P>6. National Association of Schools of Art and Design, Commission on Accreditation (NASAD)(Current Scope: The accreditation throughout the United States of freestanding institutions, and units offering art/design and art/design-related programs (both degree- and non-degree-granting), including those offered via distance education.) (Requested Scope: The accreditation throughout the United States of freestanding institutions, and units offering art/design and art/design-related programs (both degree- and non-degree-granting), including those offered via distance and correspondence education.)</P>
          <P>7. National Association of Schools of Music, Commission on Accreditation (NASM) (Current Scope: The accreditation throughout the United States of freestanding institutions, and units offering music and music-related programs (both degree- and non-degree-granting), including those offered via distance education.) (Requested Scope: The accreditation throughout the United States of freestanding institutions, and units offering music and music-related programs (both degree- and non-degree-granting), including those offered via distance and correspondence education.)</P>

          <P>8. National Association of Schools of Theatre, Commission on Accreditation (NAST) (Current Scope: The accreditation throughout the United States of freestanding institutions, and units offering theatre and theatre-related programs (both degree-and non-degree-granting), including those offered via distance education.) (Requested Scope:<PRTPAGE P="10162"/>The accreditation throughout the United States of freestanding institutions, and units offering theatre and theatre-related programs (both degree- and non-degree-granting), including those offered via distance and correspondence education.)</P>
          <P>9. New England Association Of Schools and Colleges, Commission on Institutions of Higher Education (NEA-CIHE) (Current Scope: The accreditation and preaccreditation (“Candidacy status”) of institutions of higher education in Connecticut, Maine, Massachusetts, New Hampshire, Rhode Island, and Vermont that award bachelor's, master's, and/or doctoral degrees, and associate degree-granting institutions in those states that include degrees in liberal arts or general studies among their offerings, including the accreditation of programs offered via distance education within these institutions. This recognition extends to the Board of Trustees of the Association jointly with the Commission for decisions involving preaccreditation, initial accreditation, and adverse actions.) (Requested Scope: The accreditation and pre-accreditation (“Candidacy status”) of institutions of higher education in Connecticut, Maine, Massachusetts, New Hampshire, Rhode Island, and Vermont that award bachelor's, master's, and/or doctoral degrees, and associate degree-granting institutions in those states that include degrees in liberal arts or general studies among their offerings, including the accreditation of programs offered via distance education within these institutions. This recognition extends jointly, to the Commission for accreditation and pre-accreditation decisions and to the Board of Trustees of the Association and the Commission for the appeal of adverse actions.)</P>
          <P>10. North Central Association of Colleges and Schools, The Higher Learning Commission (NCA-HLC) (Current Scope: The accreditation and preaccreditation (“Candidate for Accreditation”) of degree-granting institutions of higher education in Arizona, Arkansas, Colorado, Illinois, Indiana, Iowa, Kansas, Michigan, Minnesota, Missouri, Nebraska, New Mexico, North Dakota, Ohio, Oklahoma, South Dakota, West Virginia, Wisconsin, and Wyoming, including the tribal institutions and the accreditation of programs offered via distance education within these institutions. This recognition extends to the Institutional Actions Council jointly with the Board of Trustees of the Commission for decisions on cases for continued accreditation or reaffirmation, and continued candidacy. This recognition also extends to the Review Committee of the Accreditation Review Council jointly with the Board of Trustees of the Commission for decisions on cases for continued accreditation or candidacy and for initial candidacy or initial accreditation when there is a consensus decision by the Review Committee.) (Requested Scope: The accreditation and preaccreditation (“Candidate for Accreditation”) of degree-granting institutions of higher education in Arizona, Arkansas, Colorado, Illinois, Indiana, Iowa, Kansas, Michigan, Minnesota, Missouri, Nebraska, New Mexico, North Dakota, Ohio, Oklahoma, South Dakota, West Virginia, Wisconsin, and Wyoming, including the tribal institutions and the accreditation of programs offered via distance education within these institutions. This recognition extends to the Institutional Actions Council jointly with the Board of Trustees of the Commission for decisions on cases for continued accreditation or reaffirmation, and continued candidacy and to the Appeal Body jointly with the Board of Trustees of the Commission for decisions related to initial candidacy or accreditation or reaffirmation of accreditation.)</P>
          <HD SOURCE="HD1">Petitions for Recognition Based on a Compliance Report</HD>
          <HD SOURCE="HD2">Accrediting Agencies</HD>
          <P>1. Accreditation Commission for Acupuncture and Oriental Medicine (ACAOM) (Current Scope: The accreditation and preaccreditation (“Candidacy” status) throughout the United States of first-professional master's degree and professional master's level certificate and diploma programs in acupuncture and Oriental medicine and professional post-graduate doctoral programs in acupuncture and in Oriental Medicine (DAOM), as well as freestanding institutions and colleges of acupuncture or Oriental medicine that offer such programs.)</P>
          <P>2. Accrediting Council for Independent Colleges and Schools (ACICS) (Current Scope: The accreditation of private postsecondary institutions throughout the United States offering certificates or diplomas, and postsecondary institutions offering associate, bachelor's, or master's degrees in programs designed to educate students for professional, technical, or occupational careers, including those that offer those programs via distance education.)</P>
          <P>3. American Bar Association (ABA) (Current Scope: The accreditation throughout the United States of programs in legal education that lead to the first professional degree in law, as well as freestanding law schools offering such programs. This recognition also extends to the Accreditation Committee of the Section of Legal Education (Accreditation Committee) for decisions involving continued accreditation (referred to by the agency as “approval”) of law schools.)</P>
          <P>4. American Psychological Association (APA) (Current Scope: The accreditation in the United States of doctoral programs in clinical, counseling, school and combined professional-scientific psychology; predoctoral internship programs in professional psychology; and postdoctoral residency programs in professional psychology.)</P>
          <P>5. Commission on Accrediting of the Association of Theological Schools (ATSUSC) (Current Scope: The accreditation and pre-accreditation (“Candidate for Accredited Membership”) of theological schools and seminaries, as well as schools or programs that are parts of colleges or universities, in the United States, offering post baccalaureate degrees in professional and academic theological education, including delivery via distance education.)</P>
          <P>6. American Dental Association, Commission on Dental Accreditation (CODA) (Current Scope: The accreditation of predoctoral dental education programs (leading to the D.D.S. or D.M.D. degree), advanced dental education programs, and allied dental education programs that are fully operational or have attained “Initial Accreditation” status, including programs offered via distance education.)</P>
          <P>7. Council On Occupational Education (COE) (Current Scope: The accreditation and preaccreditation (“Candidacy Status”) throughout the United States of postsecondary occupational education institutions offering non-degree and applied associate degree programs in specific career and technical education fields, including institutions that offer programs via distance education.)</P>

          <P>8. Transnational Association Of Christian Colleges and Schools (TRACS) (Current Scope: The accreditation and pre-accreditation (“Candidate” status) of Christian postsecondary institutions in the United States that offer certificates, diplomas, and associate, baccalaureate, and graduate degrees, including institutions that offer distance education.)<PRTPAGE P="10163"/>
          </P>
          <HD SOURCE="HD1">State Approval Agency for Nurse Education</HD>
          <P>1. Maryland Board of Nursing (MBN) (Current Scope: Stateagency for the approval of nurse education.</P>
          <P>
            <E T="03">Submission of Written Comments:</E>Written comments must be received by March 4, 2013, in the<E T="03">accreditationcommittees@ed.gov</E>mailbox and include the subject line “Written Comments: re (agency name).” The email must include the name, title, affiliation, mailing address, email address, telephone and facsimile numbers and Web site (if any) of the person/group making the comment. Comments should be submitted as a Microsoft Word document or in a medium compatible with Microsoft Word (not a PDF file) that is attached to an electronic mail message (email) or provided in the body of an email message. Comments about an agency's compliance report must relate to the issues raised and the criteria for recognition cited in the Secretary's letter that requested the report. Comments about the renewal of an agency's recognition must relate to its compliance with the Criteria for the Recognition of Accrediting Agencies or the Criteria and Procedures for Recognition of State Agencies for Approval of Nurse Education, as appropriate, which are available at<E T="03">http://www.ed.gov/admins/finaid/accred/index.html</E>. Third parties having concerns about agencies regarding matters outside the scope of the petition should report those concerns to the Department. Only material submitted by the deadline to the email address listed in this notice, and in accordance with these instructions, become part of the official record concerning agencies scheduled for review and are considered by the Department and the NACIQI in their deliberations. Please do not send material directly to the NACIQI members.</P>
          <P>
            <E T="03">Submission of Requests To Make an Oral Comment:</E>There are two methods the public may use to make a third-party oral comment of three to five minutes. All comments must concern one of the agencies scheduled for review at the June 6-7, 2013 meeting, and must relate to the Criteria for Recognition of accrediting agencies or the Criteria and Procedures for Recognition of State Agencies for Approval of Nurse Education, as appropriate. These criteria are available at:<E T="03">http://www.ed.gov/admins/finaid/accred/index.html</E>
          </P>
          <P>
            <E T="03">Method One:</E>Submit a request by email to the<E T="03">accreditationcommittees@ed.gov</E>mailbox. Please do not send material directly to NACIQI members. Requests must be received by March 4, 2013, and include the subject line “Oral Comment Request: re (agency name).” The email must include the name, title, affiliation, mailing address, email address, telephone and facsimile numbers and Web site (if any) of the person/group requesting to speak. All individuals or groups submitting an advance request in accordance with this notice will be afforded an opportunity to speak for a maximum of five minutes each. Each request must concern the recognition of a single agency or institution tentatively scheduled in this notice for review, be no more than one page (maximum), and must include:</P>
          <P>1. The name, title, affiliation, mailing address, email address, telephone and facsimile numbers, and Web site (if any) of the person/group requesting to speak; and,</P>
          <P>2. A brief summary of the principal points to be made during the oral presentation.</P>
          <P>
            <E T="03">Method Two:</E>Register at the meeting location on June 6 or June 7, 2013, to make an oral comment during the NACIQI's deliberations concerning a particular agency or institution scheduled for review that day. The requestor must provide his or her name, title, affiliation, mailing address, email address, telephone and facsimile numbers, and Web site (if any). A total of up to fifteen minutes during each agency review will be allotted for commenters who register on June 6 or June 7, 2013. Individuals or groups will be selected on a first-come, first-served basis. If selected, each commenter may speak from three to five minutes, depending on the number of individuals or groups who signed up the day of the meeting.</P>
          <P>If a person or group requests, in advance, to make comments they cannot also register for an oral presentation opportunity on June 6 or June 7, 2013. The oral comments made will become part of the official record and will be considered by the Department and NACIQI in their deliberations. No individual or group in attendance or making oral presentations may distribute written materials at the meeting.</P>
          <P>
            <E T="03">Access to Records of the Meeting:</E>The Department will post the official report of the meeting on the NACIQI Web site shortly after the meeting. Pursuant to the FACA, the public may also inspect the materials at 1990 K Street NW., Washington, DC, by emailing<E T="03">aslrecordsmanager@ed.gov</E>or by calling (202) 219-7067 to schedule an appointment.</P>
          <P>
            <E T="03">Reasonable Accommodations:</E>The meeting site is accessible to individuals with disabilities. If you will need an auxiliary aid or service to participate in the meeting (e.g., interpreting service, assistive listening device, or materials in an alternate format), notify the contact person listed in this notice at least two weeks before the scheduled meeting date. Although we will attempt to meet a request received after that date, we may not be able to make available the requested auxiliary aid or service because of insufficient time to arrange it.</P>
        </SUM>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Carol Griffiths, Executive Director, NACIQI, U.S. Department of Education, 1990 K Street NW., Room 8073, Washington, DC 20006-8129, telephone: (202) 219-7035, fax: (202) 219-7005, or email:<E T="03">Carol.Griffiths@ed.gov</E>.</P>
          <P>
            <E T="03">Electronic Access to this Document:</E>The official version of this document is the document published in the<E T="04">Federal Register</E>. Free Internet access to the official edition of the<E T="04">Federal Register</E>and the Code of Federal Regulations is available via the Federal Digital System at:<E T="03">www.gpo.gov/fdsys</E>. At this site you can view this document, as well as all other documents of this Department published in the<E T="04">Federal Register</E>, in text or Adobe Portable Document Format (PDF). To use PDF, you must have Adobe Acrobat Reader, which is available free at the site.</P>

          <P>You may also access documents of the Department published in the<E T="04">Federal Register</E>by using the article search feature at:<E T="03">www.federalregister.gov</E>. Specifically, through the advanced search feature at this site, you can limit your search to documents published by the Department.</P>
          <SIG>
            <NAME>David A. Bergeron,</NAME>
            <TITLE>Acting Assistant Secretaryfor Postsecondary Education.</TITLE>
          </SIG>
        </FURINF>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-03314 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
        <SUBJECT>Notice of Availability of Draft Section 3116 Basis for Determination for Closure of H Tank Farm at the Savannah River Site</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>U.S. Department of Energy.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of availability.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The Department of Energy (DOE) announces the availability of the<E T="03">Draft Section 3116 Basis for Determination for Closure of the H Tank Farm at the Savannah River Site</E>(Draft HTF 3116 Basis Document) for public<PRTPAGE P="10164"/>comment. DOE prepared the Draft HTF 3116 Basis Document pursuant to section 3116(a) of the Ronald W. Reagan National Defense Authorization Act for Fiscal Year 2005 (NDAA), which provides that the Secretary of Energy may, in consultation with the U.S. Nuclear Regulatory Commission (NRC), determine that certain waste from reprocessing of spent nuclear fuel is not high-level radioactive waste if the provisions set forth in section 3116(a) are satisfied. To make this determination, the Secretary of Energy must determine that the waste in the HTF: (1) Does not require permanent isolation in a deep geologic repository for spent fuel or high-level radioactive waste; (2) has had highly radioactive radionuclides removed to the maximum extent practical; and (3)(A) does not exceed concentration limits for Class C low-level waste and will be disposed of in compliance with the performance objectives in 10 CFR Part 61, Subpart C and pursuant to a State approved closure plan or State-issued permit; or (3)(B) exceeds concentration limits for Class C low-level waste but will be disposed of in compliance with the performance objectives of 10 CFR Part 61, Subpart C; pursuant to a State approved closure plan or State-issued permit; and pursuant to plans developed by DOE in consultation with the NRC. Although not required by the NDAA, DOE is making the Draft HTF 3116 Basis Document available for public comment. The Draft HTF 3116 Basis Document demonstrates that the cleaned and stabilized HTF tanks, ancillary structures and their stabilized residuals at HTF closure meet the public dose limits and other criteria in section 3116. DOE is consulting with the NRC and will consider public comments before preparing a final HTF 3116 Basis Document and issuing a Secretarial determination undersection 3116.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The comment period will end on May 1, 2013. Comments received after this date will be considered to the extent practicable.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>The Draft HTF Section 3116 Basis document is available on the Internet at h<E T="03">ttp://sro.srs.gov/f_htankfarmsdocuments.htm.</E>
          </P>
          <P>Written comments on the draft HTF Section 3116 Basis document may be submitted by U.S. mail to the following address:Ms. Sherri Ross, DOE-SR,Building 704-S, Room 43,U.S. Department of Energy,Savannah River Operations Office,Aiken, SC 29802(ATTN: H-Tank Farm Draft Basis).</P>

          <P>Alternatively, comments may also be filed electronically by email to<E T="03">sherri.ross@srs.gov</E>, or by Fax at (803) 208-7414.</P>
        </ADD>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The HTF is a 45-acre site, located at the Savannah River Site (SRS) near Aiken, South Carolina. The HTF consists of 29 underground radioactive waste storage tanks and supporting ancillary structures. The major HTF ancillary structures are three evaporator systems, transfer lines, eight diversion boxes, one catch tank, a concentrate transfer system, ten pump pits, nine pump tanks, and eleven valve boxes. There are four waste tank types (Type I, II, III/IIIA, and IV) in HTF with operating capacities ranging from 750,000 gallons to 1,300,000 gallons. The waste tanks have varying degrees of secondary containment and in-tank structural features such as cooling coils and columns. All HTF waste tanks are constructed of carbon steel. The HTF tanks and ancillary structures contain, in part, waste from the prior reprocessing of spent nuclear fuel, and from various SRS production, processing and laboratory facilities.</P>

        <P>DOE is in the process of closing the HTF and is engaged in an expansive campaign to clean, stabilize, and close the tanks and ancillary structures in the HTF, using a process that includes removing bulk waste from tanks and applicable ancillary structures, followed by deployment of tested technologies to remove the majority of the remaining waste. After completing cleaning operations, a small amount of residual radioactive waste will remain in the tanks and ancillary structures. DOE plans to stabilize the residuals in the tanks and certain ancillary structures in place with grout, followed by a closure cap system for the HTF. Tank waste storage and removal operations in the HTF are governed by a South Carolina Department of Health and Environmental Control (SCDHEC) industrial wastewater operating permit. Removal of tanks from service and stabilization of the HTF waste tanks and ancillary structures will be carried out pursuant to a State-approved closure plan, the<E T="03">Industrial Wastewater General Closure Plan for H-Area Waste Tank Systems</E>. Specific Closure Modules for each tank or ancillary structure or groupings of tanks and ancillary structures will be developed and submitted to SCDHEC for approval. After SCDHEC approval of the specific and final closure configuration documentation and grouting, the applicable tank or ancillary structure will be removed from the State's industrial wastewater permit. Where appropriate, the Draft HTF 3116 Basis Document draws upon DOE's experience in cleaning and closing tanks at the similar F-Area Tank Farm at SRS, for which the Secretary of Energy issued a Section 3116 Determination in March 2012.</P>
        <P>As demonstrated and documented in the Draft HTF 3116 Basis Document, the stabilized HTF tanks, ancillary structures and residuals at closure meet the public dose performance objective and other criteria set forth in section 3116(a) of the NDAA. DOE is consulting with the NRC pursuant to section 3116, and will consider this consultation as well as public comments before preparing a final HTF 3116 Basis Document. DOE anticipates that the final HTF 3116 Basis Document will serve as a predicate for the Secretary to determine whether or not the stabilized HTF tanks, ancillary structures and residuals at closure meet the criteria in section 3116(a), are not high-level radioactive waste, and may be disposed of in place as low-level waste.</P>
        <SIG>
          <DATED>Issued in Washington, DC, on February 6, 2013.</DATED>
          <NAME>Mark A. Gilbertson,</NAME>
          <TITLE>Deputy Assistant Secretary for Site Restoration.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03305 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <SUBJECT>Combined Notice of Filings #1</SUBJECT>
        <P>Take notice that the Commission received the following electric rate filings:</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER12-1643-001.</P>
        <P>
          <E T="03">Applicants:</E>ISO New England Inc.</P>
        <P>Description: ISO New England Inc. submits Order No. 755 Regulation Mkt. Compliance Changes to be effective 12/31/9998.</P>
        <P>
          <E T="03">Filed Date:</E>2/6/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130206-5047.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/27/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER12-2277-003.</P>
        <P>
          <E T="03">Applicants:</E>Midwest Independent Transmission System Operator, Inc.</P>
        <P>
          <E T="03">Description:</E>Midwest Independent Transmission System Operator, Inc. submits 2013-02-05 SA 2457 G631-2-3 Term to be effective 4/6/2013.</P>
        <P>
          <E T="03">Filed Date:</E>2/5/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130205-5158.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/26/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-886-000.</P>
        <P>
          <E T="03">Applicants:</E>Midwest Independent Transmission System Operator, Inc.</P>
        <P>
          <E T="03">Description:</E>Midwest Independent Transmission System Operator, Inc.<PRTPAGE P="10165"/>submits tariff filing per 35.13(a)(2)(iii: 02-05-2013 SA 2456 Termination Emmet Cty Energy-ITC to be effective 4/6/2013.</P>
        <P>
          <E T="03">Filed Date:</E>2/5/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130205-5156.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/26/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-887-000.</P>
        <P>
          <E T="03">Applicants:</E>PJM Interconnection, L.L.C.</P>
        <P>
          <E T="03">Description:</E>Request for Limited Waiver of PJM Interconnection, L.L.C.</P>
        <P>
          <E T="03">Filed Date:</E>2/6/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130206-5015.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/27/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-888-000.</P>
        <P>
          <E T="03">Applicants:</E>Niagara Mohawk Power Corporation, New York Independent System Operator, Inc.</P>
        <P>
          <E T="03">Description:</E>Niagara Mohawk Power Corporation submits tariff filing per 35.13(a)(2)(iii: NYISO filing of Agreement No. 1953 between National Grid and Erie Blvd. Hydropowr to be effective 11/9/2012.</P>
        <P>
          <E T="03">Filed Date:</E>2/6/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130206-5040.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/27/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-889-000.</P>
        <P>
          <E T="03">Applicants:</E>Midwest Independent Transmission System Operator, Inc.</P>
        <P>
          <E T="03">Description:</E>Midwest Independent Transmission System Operator, Inc. submits tariff filing per 35.13(a)(2)(iii: 02-05-2013 SA 2509 ITC-Tuscola Wind E&amp;P to be effective 2/7/2013.</P>
        <P>
          <E T="03">Filed Date:</E>2/6/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130206-5044.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/27/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-890-000.</P>
        <P>
          <E T="03">Applicants:</E>PJM Interconnection, L.L.C.</P>
        <P>
          <E T="03">Description:</E>PJM Interconnection, L.L.C. submits Notice of Cancellation of Original Service Agreement No. 3259 to be effective 1/4/2013.</P>
        <P>
          <E T="03">Filed Date:</E>2/6/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130206-5049.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/27/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-891-000.</P>
        <P>
          <E T="03">Applicants:</E>PJM Interconnection, L.L.C.</P>
        <P>
          <E T="03">Description:</E>PJM Interconnection, L.L.C. submits tariff filing per 35.13(a)(2)(iii: Non-Queue 69 Safe Harbor ISA—Original Service Agreement No. 3504 to be effective 1/7/2013.</P>
        <P>
          <E T="03">Filed Date:</E>2/6/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130206-5050.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/27/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-892-000.</P>
        <P>
          <E T="03">Applicants:</E>PJM Interconnection, L.L.C.</P>
        <P>
          <E T="03">Description:</E>PJM Interconnection, L.L.C. submits Notice of Cancellation of Original SA No. 2711 in Dkt No. ER11-2707-000 to be effective 1/10/2013.</P>
        <P>
          <E T="03">Filed Date:</E>2/6/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130206-5055.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/27/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-893-000.</P>
        <P>
          <E T="03">Applicants:</E>PJM Interconnection, L.L.C.</P>
        <P>
          <E T="03">Description:</E>PJM Interconnection, L.L.C. submits Notice of Cancellation of Original SA No. 3149 -Docket No. ER12-518-000 to be effective 1/10/2013.</P>
        <P>
          <E T="03">Filed Date:</E>2/6/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130206-5056.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t 2/27/13.</P>
        
        <P>Take notice that the Commission received the following electric securities filings:</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ES13-17-000.</P>
        <P>
          <E T="03">Applicants:</E>Northern Maine Independent System Administrator, Inc.</P>
        <P>
          <E T="03">Description:</E>Application of Northern Maine Independent System Administrator, Inc. for Authorization to Issue Securities Pursuant to Section 204 of the Federal Power Act.</P>
        <P>
          <E T="03">Filed Date:</E>2/5/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130205-5178.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/26/13.</P>
        
        <P>The filings are accessible in the Commission's eLibrary system by clicking on the links or querying the docket number.</P>
        <P>Any person desiring to intervene or protest in any of the above proceedings must file in accordance with Rules 211 and 214 of the Commission's Regulations (18 CFR 385.211 and 385.214) on or before 5:00 p.m. Eastern time on the specified comment date. Protests may be considered, but intervention is necessary to become a party to the proceeding.</P>

        <P>eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, service, and qualifying facilities filings can be found at:<E T="03">http://www.ferc.gov/docs-filing/efiling/filing-req.pdf.</E>For other information, call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.</P>
        <SIG>
          <DATED>Dated: February 6, 2013.</DATED>
          <NAME>Nathaniel J. Davis, Sr.,</NAME>
          <TITLE>Deputy Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-03301 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <SUBJECT>Combined Notice of Filings</SUBJECT>
        <P>Take notice that the Commission has received the following Natural Gas Pipeline Rate and Refund Report filings:</P>
        <HD SOURCE="HD1">Filings Instituting Proceedings</HD>
        <P>
          <E T="03">Docket Numbers:</E>RP13-540-000.</P>
        <P>
          <E T="03">Applicants:</E>Trailblazer Pipeline Company LLC.</P>
        <P>
          <E T="03">Description:</E>Revisions to FM, Waiver and Indemnification Sections to be effective 3/6/2013.</P>
        <P>
          <E T="03">Filed Date:</E>2/4/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130204-5130.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/19/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP13-541-000.</P>
        <P>
          <E T="03">Applicants:</E>Iroquois Gas Transmission System, L.P.</P>
        <P>
          <E T="03">Description:</E>02/04/13 Negotiated Rates—JP Morgan Ventures Corp (HUB)—6025-89 to be effective 2/2/2013.</P>
        <P>
          <E T="03">Filed Date:</E>2/4/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130204-5134.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/19/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP13-542-000.</P>
        <P>
          <E T="03">Applicants:</E>Equitrans, L.P.</P>
        <P>
          <E T="03">Description:</E>Equitrans, L.P. submits Petition for partial waiver of tariff to defer Pipeline Safety Cost Tracker update filing.</P>
        <P>
          <E T="03">Filed Date:</E>2/5/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130205-5067.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/8/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP13-543-000.</P>
        <P>
          <E T="03">Applicants:</E>White River Hub, LLC.</P>
        <P>
          <E T="03">Description:</E>Sec. 6.18 Request to Acquire Released Capacity to be effective 3/11/2013.</P>
        <P>
          <E T="03">Filed Date:</E>2/5/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130205-5091.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/19/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP13-544-000.</P>
        <P>
          <E T="03">Applicants:</E>Iroquois Gas Transmission System, L.P.</P>
        <P>
          <E T="03">Description:</E>02/05/13 Negotiated Rates—Sequent Energy Management (HUB)—3075-89 to be effective 2/4/2013.</P>
        <P>
          <E T="03">Filed Date:</E>2/5/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130205-5094.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/19/13.</P>
        
        <P>Any person desiring to intervene or protest in any of the above proceedings must file in accordance with Rules 211 and 214 of the Commission's Regulations (18 CFR 385.211 and 385.214) on or before 5:00 p.m. Eastern time on the specified comment date. Protests may be considered, but intervention is necessary to become a party to the proceeding.</P>
        <HD SOURCE="HD1">Filings in Existing Proceedings</HD>
        <P>
          <E T="03">Docket Numbers:</E>RP13-124-003.</P>
        <P>
          <E T="03">Applicants:</E>Hardy Storage Company, LLC.</P>
        <P>
          <E T="03">Description:</E>NAESB 2.0 Compliance to be effective 12/1/2012.</P>
        <P>
          <E T="03">Filed Date:</E>2/4/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130204-5137.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/19/13.</P>
        
        <PRTPAGE P="10166"/>
        <P>
          <E T="03">Docket Numbers:</E>RP13-40-002.</P>
        <P>
          <E T="03">Applicants:</E>National Grid LNG, LP.</P>
        <P>
          <E T="03">Description:</E>NAESB v.3.0.0 to be effective 12/1/2012.</P>
        <P>
          <E T="03">Filed Date:</E>2/4/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130204-5058.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/19/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP13-43-002.</P>
        <P>
          <E T="03">Applicants:</E>Bluewater Gas Storage, LLC.</P>
        <P>
          <E T="03">Description:</E>Bluewater Feb 5 NAESB compliance to be effective 12/1/2012.</P>
        <P>
          <E T="03">Filed Date:</E>2/5/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130205-5087.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/19/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP13-44-002.</P>
        <P>
          <E T="03">Applicants:</E>SG Resources Mississippi, L.L.C.</P>
        <P>
          <E T="03">Description:</E>SG Resources Feb 5 NAESB Compliance to be effective 12/1/2012.</P>
        <P>
          <E T="03">Filed Date:</E>2/5/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130205-5089.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/19/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP13-45-002.</P>
        <P>
          <E T="03">Applicants:</E>Pine Prairie Energy Center, LLC.</P>
        <P>
          <E T="03">Description:</E>Pine Prairie Revise NAESB filing to be effective 12/1/2012.</P>
        <P>
          <E T="03">Filed Date:</E>2/5/13.</P>
        <P>
          <E T="03">Accession Number:</E>20130205-5090.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. e.t. 2/19/13.</P>
        
        <P>Any person desiring to protest in any the above proceedings must file in accordance with Rule 211 of the Commission's Regulations (18 CFR 385.211) on or before 5:00 p.m. Eastern time on the specified comment date.</P>
        <P>The filings are accessible in the Commission's eLibrary system by clicking on the links or querying the docket number.</P>

        <P>eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, and service can be found at:<E T="03">http://www.ferc.gov/docs-filing/efiling/filing-req.pdf.</E>For other information, call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.</P>
        <SIG>
          <DATED>Dated: February 6, 2013.</DATED>
          <NAME>Nathaniel J. Davis, Sr.,</NAME>
          <TITLE>Deputy Secretary</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-03300 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <DEPDOC>[EPA-HQ-OPP-2013-0036; FRL-9376-6]</DEPDOC>
        <SUBJECT>Access Interpreting; Transfer of Data</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This notice announces that pesticide related information submitted to EPA's Office of Pesticide Programs (OPP) pursuant to the Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA) and the Federal Food, Drug, and Cosmetic Act (FFDCA), including information that may have been claimed as Confidential Business Information (CBI) by the submitter, will be transferred to Access Interpreting in accordance with the CBI regulations. Access Interpreting has been awarded a contract to perform work for OPP, and access to this information will enable Access Interpreting to fulfill the obligations of the contract.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Access Interpreting will be given access to this information on or before February 19, 2013.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>MaryC Simmons, Information Technology and Resources Management Division (7502P), Office of Pesticide Programs, Environmental Protection Agency, 1200 Pennsylvania Ave. NW., Washington, DC 20460-0001; telephone number: (703) 305-6452: email address:<E T="03">simmons.maryc@epa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. General Information</HD>
        <HD SOURCE="HD2">A. Does this action apply to me?</HD>

        <P>This action applies to the public in general. As such, the Agency has not attempted to describe all the specific entities that may be affected by this action. If you have any questions regarding the applicability of this action to a particular entity, consult the person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>.</P>
        <HD SOURCE="HD2">B. How can I get copies of this document and other related information?</HD>

        <P>EPA has established a docket for this action under docket identification (ID) number EPA-HQ-OPP-2013-0036. Publicly available docket materials are available either in the electronic docket<E T="03">http://www.regulations.gov</E>or at the Office of Pesticide Programs Regulatory Public Docket (OPP Docket) in the Environmental Protection Agency Docket Center (EPA/DC), EPA West Bldg., Rm. 3334, 1301 Constitution Ave. NW., Washington, DC 20460-0001. The Public Reading Room is open from 8:30 a.m. to 4:30 p.m., Monday through Friday, excluding legal holidays. The telephone number for the Public Reading Room is (202) 566-1744, and the telephone number for the OPP Docket is (703) 305-5805. Please review the visitor instructions and additional information about the docket available at<E T="03">http://www.epa.gov/dockets.</E>
        </P>
        <HD SOURCE="HD1">II. Contractor Requirements</HD>
        <P>Under Contract No. EP10H000109, this contract is to provide the Environmental Protection Agency, Office of Human Resources (OHR) with Sign Language interpreting services. The contractor shall provide professional interpreters who shall make every effort to arrive at scheduled assignments 15 minutes prior to the start of the assignment, concurrent with general interpreting standards. Contract interpreters whom the Contractor sends must have a cell phone or text pager that will allow them to get instant messages for quick communication of last minute changes.</P>
        <P>The work will be performed in a space to be designated by EPA, primarily at EPA Headquarters and other Washington, DC area EPA facilities. Occasional travel will be involved. The sign language personnel will report to the location specified by the EPA Headquarters Interpreting Coordinator, also identified as the Project Officer under this contract. There will be some requests for interpreters in different areas of the United States. The contractor must have the ability to procure services in different locations throughout the country. The Contractor must primarily serve Deaf and hard of hearing persons as a major function of their business and be stationed in the Washington, DC metropolitan area.</P>
        <P>This contract involves no subcontractors.</P>
        <P>OPP has determined that the contract described in this document involves work that is being conducted in connection with FIFRA, in that pesticide chemicals will be the subject of certain evaluations to be made under this contract. These evaluations may be used in subsequent regulatory decisions under FIFRA.</P>
        <P>Some of this information may be entitled to confidential treatment. The information has been submitted to EPA under FIFRA sections 3, 4, 6, and 7 and under FFDCA sections 408 and 409.</P>

        <P>In accordance with the requirements of 40 CFR 2.307(h)(3), the contract with Access Interpreting prohibits use of the information for any purpose not specified in this contract; prohibits disclosure of the information to a third party without prior written approval from the Agency; and requires that each official and employee of the contractor sign an agreement to protect the information from unauthorized release and to handle it in accordance with the<E T="03">FIFRA Information Security Manual.</E>In addition, Access Interpreting is required to submit for EPA approval a security<PRTPAGE P="10167"/>plan under which any CBI will be secured and protected against unauthorized release or compromise. No information will be provided to Access Interpreting until the requirements in this document have been fully satisfied. Records of information provided to Access Interpreting will be maintained by EPA Project Officers for this contract. All information supplied to Access Interpreting by EPA for use in connection with this contract will be returned to EPA when Access Interpreting has completed its work.</P>
        <HD SOURCE="HD1">List of Subjects</HD>
        <P>Environmental protection, Business and industry, Government contract, Government property, Security measures.</P>
        <SIG>
          <DATED>Dated: January 30, 2013.</DATED>
          <NAME>Oscar Morales,</NAME>
          <TITLE>Director, Information Technology and Resources Management Division, Office of Pesticide Programs.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03330 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <DEPDOC>[EPA-HQ-OPP-2012; FRL-9378-3]</DEPDOC>
        <SUBJECT>Pollinator Summit: Status of Ongoing Collaborative Efforts To Protect Pollinators; Notice of Public Meeting</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Office of Chemical Safety and Pollution Prevention, in conjunction with the United States Department of Agriculture, will facilitate a public meeting with parties engaged in activities to reduce potential acute exposure of honey bees and pollinators to pesticides. Invited presenters will provide briefings on current activities in three key areas related to improving seed treatment techniques; reducing the generation of dust that occurs during planting operations; and raising awareness of current best management practices that are available to mitigate potential acute pesticide exposure to pollinators. Pollinators are an important component of agricultural production, critical to food and ecosystems, and must be protected so that they can continue to play this important role. The intended outcome of this meeting is to share information and look for areas of collaboration to lessen the unintended impacts of pesticides on pollinators during coming and future growing seasons. This meeting complements EPA's ongoing work through the Pesticide Program Dialogue Committee (PPDC) to support and take action to improve pollinator health.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The meeting will be held on March 5, 2013 from 8:00 a.m. to 5:00 p.m. e.s.t.</P>

          <P>To request accommodation of a disability, please contact the person listed under<E T="02">FOR FURTHER INFORMATON CONTACT</E>, preferably at least 10 days prior to the meeting, to give EPA as much time as possible to process your request.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The meeting will be held at the Office of Pesticide Programs (OPP), First Floor Conference Center, One Potomac Yard (South Bldg.), 2777 S. Crystal Dr., Arlington, VA 22202.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Mary Clock-Rust, Environmental Fate and Effects Division, (7507P), Office of Pesticide Programs, Environmental Protection Agency, 1200 Pennsylvania Ave. NW., Washington, DC 20460-0001; telephone number: (703) 308-2718; fax number: (703) 305-6309 email address:<E T="03">clock-rust.mary@epa.gov</E>.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. General Information</HD>
        <HD SOURCE="HD2">A. Does this action apply to me?</HD>

        <P>You may be potentially affected by this action if you are engaged in activities to reduce potential exposure of honey bees and pollinators to pesticides. This action is directed to the public in general, and may be of particular interest to, but is not limited to the following entities: Agricultural workers and farmers; beekeepers; pesticide industry and trade associations; environmental, consumer, and farm worker groups; animal welfare organizations; pesticide users and growers; pest consultants, state, local and tribal governments and academia. If you have questions regarding the applicability of this action to a particular entity, consult the person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>.</P>
        <HD SOURCE="HD2">B. How can I request to participate in this meeting?</HD>

        <P>This meeting is open to the public and seating is limited. Please use the following email address to make a reservation for seating:<E T="03">Pollinator_summit@epa.gov.</E>Persons interested in attending the meeting remotely should contact the person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>to obtain details to access the webinar of this meeting. Comments may be made during the public comment session of the meeting; invited presenters will provide briefings and information on their current activities.</P>
        <HD SOURCE="HD1">II. Background</HD>
        <P>EPA is convening a public meeting to facilitate the exchange of information among parties engaged in various activities related to improving the safety of pollinators around agricultural crops. While there are several factors affecting honey bee health, pesticides are among these variables; and, new research is rapidly becoming available on practices and technology aimed at reducing exposure of pollinators to pesticides. Specifically, this summit will focus on the pesticide treated seed, including the technology of seed treatment and the management of dust that can be associated with planting treated seed and which may lead to pesticide exposure to bees. The public meeting will also include best management techniques associated with commercial agriculture and bees. This summit complements EPA's on-going work with the PPDC Workgroup on Pollinator Protection, which is addressing pesticide labeling, best management practices, enforcement, communication and education. This public summit is being held to increase the awareness among the participants and the public of the rapidly changing understanding of, and response to protecting pollinators at agricultural crops.</P>
        <HD SOURCE="HD1">List of Subjects</HD>
        <P>Environmental protection, Pesticides and pests.</P>
        <SIG>
          <DATED>Dated: February 7, 2013.</DATED>
          <NAME>Steven Bradbury,</NAME>
          <TITLE>Director, Office of Pesticide Programs.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03332 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <DEPDOC>[EPA-HQ-OPP-2013-0026; FRL-9378-5]</DEPDOC>
        <SUBJECT>Pesticide Products; Registration Applications for a New Active Ingredient</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>EPA has received applications to register pesticide products containing an active ingredient not included in any currently registered pesticide products. Pursuant to the Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA), EPA is hereby providing notice of receipt and opportunity to comment on these applications.</P>
        </SUM>
        <DATES>
          <PRTPAGE P="10168"/>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be received on or before March 15, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Submit your comments, identified by docket identification (ID) number and the EPA File Symbol<E T="03"/>of interest as shown in the body of this document, by one of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>Follow the online instructions for submitting comments. Do not submit electronically any information you consider to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute.</P>
          <P>•<E T="03">Mail:</E>OPP Docket, Environmental Protection Agency Docket Center (EPA/DC), (28221T), 1200 Pennsylvania Ave. NW., Washington, DC 20460-0001.</P>
          <P>•<E T="03">Hand Delivery:</E>To make special arrangements for hand delivery or delivery of boxed information, please follow the instructions at<E T="03">http://www.epa.gov/dockets/contacts.htm.</E>
          </P>
          

          <FP>Additional instructions on commenting or visiting the docket, along with more information about dockets generally, is available at<E T="03">http://www.epa.gov/dockets.</E>
          </FP>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>A contact person is listed at the end of each registration application summary and may be contacted by telephone, email, or mail. Mail correspondence to the Registration Division (RD) (7505P), Office of Pesticide Programs, Environmental Protection Agency, 1200 Pennsylvania Ave. NW., Washington, DC 20460-0001. As part of the mailing address, include the contact person's name, division, and mail code.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. General Information</HD>
        <HD SOURCE="HD2">A. Does this action apply to me?</HD>
        <P>You may be potentially affected by this action if you are an agricultural producer, food manufacturer, or pesticide manufacturer. The following list of North American Industrial Classification System (NAICS) codes is not intended to be exhaustive, but rather provides a guide to help readers determine whether this document applies to them. Potentially affected entities may include:</P>
        <P>• Crop production (NAICS code 111).</P>
        <P>• Animal production (NAICS code 112).</P>
        <P>• Food manufacturing (NAICS code 311).</P>
        <P>• Pesticide manufacturing (NAICS code 32532).</P>
        <HD SOURCE="HD2">B. What should I consider as I prepare my comments for EPA?</HD>
        <P>1.<E T="03">Submitting CBI.</E>Do not submit this information to EPA through regulations.gov or email. Clearly mark the part or all of the information that you claim to be CBI. For CBI information in a disk or CD-ROM that you mail to EPA, mark the outside of the disk or CD-ROM as CBI and then identify electronically within the disk or CD-ROM the specific information that is claimed as CBI. In addition to one complete version of the comment that includes information claimed as CBI, a copy of the comment that does not contain the information claimed as CBI must be submitted for inclusion in the public docket. Information so marked will not be disclosed except in accordance with procedures set forth in 40 CFR part 2.</P>
        <P>2.<E T="03">Tips for preparing your comments.</E>When submitting comments, remember to:</P>

        <P>i. Identify the document by docket ID number and other identifying information (subject heading,<E T="04">Federal Register</E>date and page number).</P>
        <P>ii. Follow directions. The Agency may ask you to respond to specific questions or organize comments by referencing a Code of Federal Regulations (CFR) part or section number.</P>
        <P>iii. Explain why you agree or disagree; suggest alternatives and substitute language for your requested changes.</P>
        <P>iv. Describe any assumptions and provide any technical information and/or data that you used.</P>
        <P>v. If you estimate potential costs or burdens, explain how you arrived at your estimate in sufficient detail to allow for it to be reproduced.</P>
        <P>vi. Provide specific examples to illustrate your concerns and suggest alternatives.</P>
        <P>vii. Explain your views as clearly as possible, avoiding the use of profanity or personal threats.</P>
        <P>viii. Make sure to submit your comments by the comment period deadline identified.</P>
        <HD SOURCE="HD1">II. Registration Applications</HD>

        <P>EPA has received applications to register pesticide products containing an active ingredient not included in any currently registered pesticide products. Pursuant to the provisions of FIFRA section 3(c)(4), EPA is hereby providing notice of receipt and opportunity to comment on these applications. Notice of receipt of these applications does not imply a decision by the Agency on these applications. For actions being evaluated under the Agency's public participation process for registration actions, there will be an additional opportunity for a 30-day public comment period on the proposed decision. Please see the Agency's public participation Web site for additional information on this process (<E T="03">http://www.epa.gov/pesticides/regulating/registration-public-involvement.html</E>).<E T="03">EPA received the following applications to register</E>pesticide products containing an active ingredient not included in any currently registered products:</P>
        <P>
          <E T="03">EPA File Symbol:</E>62719-AAU, 62719-AAN, 62719-AAR, 62719-AAE, and 62719-AAG.<E T="03">Docket ID Number:</E>EPA-HQ-OPP-2012-0919.<E T="03">Applicant:</E>Dow AgroSciences, LLC, 9330 Zionsville Road, Indianapolis, IN 46268.<E T="03">Active ingredient:</E>Halauxifen-methyl.<E T="03">Product Type:</E>Herbicide.<E T="03">Proposed Uses:</E>Cereal grain crops, including winter wheat, spring wheat, barley and triticale.<E T="03">Contact:</E>Maggie Rudick, (703) 347-0257, email address:<E T="03">rudick.maggie@epa.gov.</E>
        </P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <P>Environmental protection, Pesticides and pest.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: February 7, 2013.</DATED>
          <NAME>Lois Rossi,</NAME>
          <TITLE>Director, Registration Division, Office of Pesticide Programs.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03333 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">EXPORT-IMPORT BANK</AGENCY>
        <DEPDOC>[Public Notice 2013-0112]</DEPDOC>
        <SUBJECT>Agency Information Collection Activities: Comment Request</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Export-Import Bank of the United States.</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>EIB 12-02-Credit Guarantee Facility Disbursement Approval Request.</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 developed an electronic disbursement approval processing system for guaranteed lenders with Credit Guarantee Facilities. After a Credit Guarantee Facility (CGF) has been authorized by Ex-Im Bank and legal documentation has been completed, the Lender will obtain and<PRTPAGE P="10169"/>review the required disbursement documents (e.g. invoices, bills of lading, Exporter's Certificates, etc.) and will disburse the proceeds of the loan for eligible goods and services. The Lender will access and complete an electronic questionnaire through ExIm Online inputting key data and requesting approval of the disbursement. Ex-Im Bank's action (approved or declined) will be posted on the Lender's history page.</P>
          <P>This form will enable Ex-Im Bank to identify the specific details of the export transaction. These details are necessary for determining the eligibility of disbursements for approval.</P>
          <P>The application can be reviewed at:<E T="03">www.exim.gov/pub/pending/EIB 12-02 CGF Disbursement Request.pdf</E>.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments should be received on or before April 15, 2013 to be assured of consideration.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADRESSESES:</HD>
          <P>Comments maybe submitted electronically on<E T="03">www.regulations.gov</E>or by mail to Kit Arendt, 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/>
        <P>
          <E T="03">Titles and Form Number:</E>EIB 12-01 Medium-Term Master Guarantee Agreement. Disbursement Approval Request.</P>
        <P>
          <E T="03">OMB Number:</E>3048-XXXX.</P>
        <P>
          <E T="03">Type of Review:</E>New.</P>
        <P>
          <E T="03">Need and Use:</E>The information requested enables the applicant to provide Ex-Im Bank with the information necessary to obtain legislatively required assurance of repayment and fulfills other statutory requirements.</P>
        <P>
          <E T="03">The number of respondents:</E>50.</P>
        <P>
          <E T="03">Time to Complete:</E>60 minutes.</P>
        <P>
          <E T="03">The frequency of response:</E>Annual.</P>
        <P>
          <E T="03">Total number of responses received</E>50.</P>
        <P>
          <E T="03">Reviewing time per hour:</E>60 minutes.</P>
        <P>
          <E T="03">Responses per year:</E>50.</P>
        <P>
          <E T="03">Reviewing time per year:</E>25 hours.</P>
        <P>
          <E T="03">Average Wages per hour:</E>$30.25.</P>
        <P>
          <E T="03">Average cost per year (time * wages):</E>$756.</P>
        <P>
          <E T="03">Benefits and overhead:</E>20%.</P>
        <P>
          <E T="03">Total Government Cost:</E>$908.</P>
        <SIG>
          <NAME>Sharon A. Whitt,</NAME>
          <TITLE>Agency Clearance Officer.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03265 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6690-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">EXPORT-IMPORT BANK</AGENCY>
        <DEPDOC>[Public Notice 2013-0101]</DEPDOC>
        <SUBJECT>Agency Information Collection Activities: Comment Request</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Export-Import Bank of the United States.</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>EIB 12-01 Medium-Term Master Guarantee Agreement Disbursement Approval Request.</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 developed an electronic disbursement approval processing system for guaranteed lenders with transactions documented under Medium-term Master Guarantee Agreements. After an export transaction has been authorized by Ex-Im Bank and legal documentation has been completed, the lender will obtain and review the required disbursement documents (e.g. invoices, bills of lading, Exporter's Certificates, etc.) and will disburse the proceeds of the loan for eligible goods and services. In order to obtain approval of the disbursement, the lender will access and complete an electronic questionnaire through Ex-Im Bank's automatic application system (ExIm Online). Ex-Im Bank's action (approved or declined) will be posted on the lender's history page.</P>
          <P>The information collected will assist in determining that each disbursement under a Medium-Term Guarantee meets all of the terms and conditions for approval.</P>
          <P>The application can be reviewed at:<E T="03">www.exim.gov/pub/pending/eib12-01</E>MT MGA Disbursement Approval Request.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments should be received on or before April 15, 2013 to be assured of consideration.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Comments maybe submitted electronically on<E T="03">WWW.REGULATIONS.GOV</E>or by mail to Kit Arendt, 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/>
        <P>
          <E T="03">Titles and Form Number:</E>EIB 12-01 Medium-Term Master Guarantee Agreement Disbursement Approval Request.</P>
        <P>
          <E T="03">OMB Number:</E>3048-XXXX.</P>
        <P>
          <E T="03">Type of Review:</E>New.</P>
        <P>
          <E T="03">Need and Use:</E>The information requested enables the applicant to provide Ex-Im Bank with the information necessary to obtain legislatively required assurance of repayment and fulfills other statutory requirements.</P>
        <P>
          <E T="03">The number of respondents:</E>150.</P>
        <P>
          <E T="03">Time to complete:</E>30 minutes.</P>
        <P>
          <E T="03">The frequency of response:</E>Annual.</P>
        <P>
          <E T="03">Total number of responses received</E>: 150.</P>
        <P>
          <E T="03">Annual hour burden; and</E>75 Hours.</P>
        <P>
          <E T="03">Reviewing time per hour:</E>15 minutes.</P>
        <P>
          <E T="03">Responses per year:</E>150.</P>
        <P>
          <E T="03">Reviewing time per year:</E>37.5 hours.</P>
        <P>
          <E T="03">Average wages per hour:</E>$30.25.</P>
        <P>
          <E T="03">Average cost per year:</E>(time * wages)  $1,134.</P>
        <P>
          <E T="03">Benefits and overhead:</E>20%.</P>
        <P>
          <E T="03">Total government cost:</E>$1,361.</P>
        <SIG>
          <NAME>Sharon A. Whitt,</NAME>
          <TITLE>Agency Clearance Officer.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03213 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6690-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
        <SUBJECT>Federal Advisory Committee Act; Communications Security, Reliability, and Interoperability Council</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Communications Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of public meeting.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In accordance with the Federal Advisory Committee Act, this notice advises interested persons that the Federal Communications Commission's (FCC) Communications Security, Reliability, and Interoperability Council (CSRIC) will hold its final meeting. Working groups Next Generation Alerting, E9-1-1 Location Accuracy, Network Security Best Practices, DNSSEC Implementation Practices for ISPs, Secure BGP Deployment, Botnet Remediation, Alerting Issues Associated with CAP Migration, 9-1-1 Prioritization, and Consensus Cybersecurity Controls will be presenting reports for a vote by the Council.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>March 6, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Federal Communications Commission, Room TW-C305 (Commission Meeting Room), 445 12th Street SW., Washington, DC 20554.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Jeffery Goldthorp, Designated Federal Officer, (202) 418-1096 (voice) or<E T="03">jeffery.goldthorp@fcc.gov</E>(email); or Lauren Kravetz, Deputy Designated Federal Officer, (202) 418-7944 (voice) or<E T="03">lauren.kravetz@fcc.gov</E>(email).</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <PRTPAGE P="10170"/>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>The meeting will be held on March 6, 2013, from 9:00 a.m. to 1:00 p.m. in the Commission Meeting Room of the Federal Communications Commission, Room TW-C305, 445 12th Street SW., Washington, DC 20554. The CSRIC is a federal advisory committee that will provide recommendations to the FCC regarding best practices and actions the FCC can take to ensure the security, reliability, and interoperability of communications systems. On March 19, 2011, the FCC, pursuant to the Federal Advisory Committee Act, renewed the charter for the CSRIC for a period of two years through March 18, 2013. Working Groups are described in more detail at<E T="03">http://www.fcc.gov/encyclopedia/communications-security-reliability-and-interoperability-council-iii</E>.</P>

        <P>The FCC will attempt to accommodate as many attendees as possible; however, admittance will be limited to seating availability. The Commission will provide audio and/or video coverage of the meeting over the Internet from the FCC's Web page at<E T="03">http://www.fcc.gov/live</E>. The public may submit written comments before the meeting to Jeffery Goldthorp, CSRIC Designated Federal Officer, by email to<E T="03">jeffery.goldthorp@fcc.gov</E>or U.S. Postal Service Mail to Jeffery Goldthorp, Associate Bureau Chief, Public Safety and Homeland Security Bureau, Federal Communications Commission, 445 12th Street SW., Room 7-A325, Washington, DC 20554.</P>

        <P>Open captioning will be provided for this event. Other reasonable accommodations for people with disabilities are available upon request. Requests for such accommodations should be submitted via 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). Such requests should include a detailed description of the accommodation needed. In addition, please include a way the FCC can contact you if it needs more information. Please allow at least five days' advance notice; last-minute requests will be accepted, but may be impossible to fill.</P>
        <SIG>
          <FP>Federal Communications Commission.</FP>
          <NAME>Marlene H. Dortch,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03327 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6712-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL ELECTION COMMISSION</AGENCY>
        <DEPDOC>[Notice 2013-06]</DEPDOC>
        <SUBJECT>Filing Dates for the Massachusetts Senate Special Elections</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Election Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of filing dates for special election.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Massachusetts has scheduled special elections on April 30, 2013, and June 25, 2013, to fill the U.S. Senate seat vacated by Secretary John F. Kerry.</P>
          <P>Committees required to file reports in connection with the Special Primary Election on April 30, 2013, shall file a 12-day Pre-Primary Report. Committees required to file reports in connection with both the Special Primary and Special General Election on June 25, 2013, shall file a 12-day Pre-Primary Report, 12-day Pre-General, and a 30-day Post-General Report.</P>
        </SUM>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ms. Elizabeth S. Kurland, Information Division, 999 E Street NW., Washington, DC 20463; Telephone: (202) 694-1100; Toll Free (800) 424-9530.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Principal Campaign Committees</HD>
        <P>All principal campaign committees of candidates who participate in the Massachusetts Special Primary and Special General Elections shall file a 12-day Pre-Primary Report on April 18, 2013; a 12-day Pre-General on June 13, 2013; and a 30-day Post-General Report on July 25, 2013. (See charts below for the closing date for each report.)</P>

        <P>All principal campaign committees of candidates participating<E T="03">only</E>in the Special Primary Election shall file a 12-day Pre-Primary Report on April 18, 2013. (See charts below for the closing date for each report.)</P>
        <HD SOURCE="HD1">Unauthorized Committees (PACs and Party Committees)</HD>
        <P>Political committees filing on a semi-annual basis in 2013 are subject to special election reporting if they make previously undisclosed contributions or expenditures in connection with the Massachusetts Special Primary or Special General Elections by the close of books for the applicable report(s). (See charts below for the closing date for each report.)</P>
        <P>Committees filing monthly that make contributions or expenditures in connection with the Massachusetts Special Primary or General Elections will continue to file according to the monthly reporting schedule.</P>

        <P>Additional disclosure information in connection with the Massachusetts Special Elections may be found on the FEC Web site at<E T="03">http://www.fec.gov/info/report_dates.shtml.</E>
        </P>
        <HD SOURCE="HD1">Disclosure of Lobbyist Bundling Activity</HD>
        <P>Principal campaign committees, party committees and Leadership PACs that are otherwise required to file reports in connection with the special elections must simultaneously file FEC Form 3L if they receive two or more bundled contributions from lobbyists/registrants or lobbyist/registrant PACs that aggregate in excess of $17,100 during the special election reporting periods (see charts below for closing date of each period). 11 CFR 104.22(a)(5)(v) and (b).</P>
        <GPOTABLE CDEF="s50,12,12,12" COLS="4" OPTS="L2,i1">
          <TTITLE>Calendar of Reporting Dates for Massachusetts Special Election</TTITLE>
          <BOXHD>
            <CHED H="1">Report</CHED>
            <CHED H="1">Close of books<SU>1</SU>
            </CHED>
            <CHED H="1">Reg./Cert. &amp;<LI>overnight</LI>
              <LI>mailing</LI>
              <LI>deadline</LI>
            </CHED>
            <CHED H="1">Filing deadline</CHED>
          </BOXHD>
          <ROW EXPSTB="03" RUL="s">
            <ENT I="21">
              <E T="02">Quarterly Filing Committees Involved in Only the Special Primary (04/30/13) Must File:</E>
            </ENT>
          </ROW>
          <ROW EXPSTB="00" RUL="n,s">
            <ENT I="01">April Quarterly</ENT>
            <ENT A="02">WAIVED</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Pre-Primary</ENT>
            <ENT>04/10/13</ENT>
            <ENT>04/15/13</ENT>
            <ENT>04/18/13</ENT>
          </ROW>
          <ROW RUL="s">
            <ENT I="01">July Quarterly</ENT>
            <ENT>06/30/13</ENT>
            <ENT>07/15/13</ENT>
            <ENT>07/15/13</ENT>
          </ROW>
          <ROW EXPSTB="03" RUL="s">
            <ENT I="21">
              <E T="02">Semi-Annual Filing Committees Involved in Only the Special Primary (04/30/13) Must File:</E>
            </ENT>
          </ROW>
          <ROW EXPSTB="00">
            <ENT I="01">Pre-Primary</ENT>
            <ENT>04/10/13</ENT>
            <ENT>04/15/13</ENT>
            <ENT>04/18/13</ENT>
          </ROW>
          <ROW RUL="s">
            <ENT I="01">Mid-Year</ENT>
            <ENT>06/30/13</ENT>
            <ENT>07/31/13</ENT>
            <ENT>07/31/13</ENT>
          </ROW>
          <ROW EXPSTB="03" RUL="s">
            <PRTPAGE P="10171"/>
            <ENT I="21">
              <E T="02">Quarterly Filing Committees Involved in Both the Special Primary (04/30/13) and Special General (06/25/13) Must File:</E>
            </ENT>
          </ROW>
          <ROW EXPSTB="00" RUL="n,s">
            <ENT I="01">April Quarterly</ENT>
            <ENT A="02">WAIVED</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Pre-Primary</ENT>
            <ENT>04/10/13</ENT>
            <ENT>04/15/13</ENT>
            <ENT>04/18/13</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">Pre-General</ENT>
            <ENT>06/05/13</ENT>
            <ENT>06/10/13</ENT>
            <ENT>06/13/13</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">July Quarterly</ENT>
            <ENT A="02">WAIVED</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Post-General</ENT>
            <ENT>07/15/13</ENT>
            <ENT>07/25/13</ENT>
            <ENT>07/25/13</ENT>
          </ROW>
          <ROW RUL="s">
            <ENT I="01">October Quarterly</ENT>
            <ENT>09/30/13</ENT>
            <ENT>10/15/13</ENT>
            <ENT>10/15/13</ENT>
          </ROW>
          <ROW EXPSTB="03" RUL="s">
            <ENT I="21">
              <E T="02">Semi-Annual Filing Committees Involved in Both the Special Primary (04/30/13) and Special General (06/25/13) Must File:</E>
            </ENT>
          </ROW>
          <ROW EXPSTB="00">
            <ENT I="01">Pre-Primary</ENT>
            <ENT>04/10/13</ENT>
            <ENT>04/15/13</ENT>
            <ENT>04/18/13</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Pre-General</ENT>
            <ENT>06/05/13</ENT>
            <ENT>06/10/13</ENT>
            <ENT>06/13/13</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">Post-General</ENT>
            <ENT>07/15/13</ENT>
            <ENT>07/25/13</ENT>
            <ENT>07/25/13</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">Mid-Year</ENT>
            <ENT A="02">WAIVED</ENT>
          </ROW>
          <ROW RUL="s">
            <ENT I="01">Year-End</ENT>
            <ENT>12/31/13</ENT>
            <ENT>01/31/14</ENT>
            <ENT>01/31/14</ENT>
          </ROW>
          <ROW EXPSTB="03" RUL="s">
            <ENT I="21">
              <E T="02">Quarterly Filing Committees Involved In Only the Special General (06/25/13) Must File</E>:</ENT>
          </ROW>
          <ROW EXPSTB="00" RUL="n,s">
            <ENT I="01">Pre-General</ENT>
            <ENT>06/05/13</ENT>
            <ENT>06/10/13</ENT>
            <ENT>06/13/13</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">July Quarterly</ENT>
            <ENT A="02">WAIVED</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Post-General</ENT>
            <ENT>07/15/13</ENT>
            <ENT>07/25/13</ENT>
            <ENT>07/25/13</ENT>
          </ROW>
          <ROW RUL="s">
            <ENT I="01">October Quarterly</ENT>
            <ENT>09/30/13</ENT>
            <ENT>10/15/13</ENT>
            <ENT>10/15/13</ENT>
          </ROW>
          <ROW EXPSTB="03" RUL="s">
            <ENT I="21">
              <E T="02">Semi-Annual Filing Committees Involved in Only the Special General (06/25/13) Must File:</E>
            </ENT>
          </ROW>
          <ROW EXPSTB="00">
            <ENT I="01">Pre-General</ENT>
            <ENT>06/05/13</ENT>
            <ENT>06/10/13</ENT>
            <ENT>06/13/13</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">Post-General</ENT>
            <ENT>07/15/13</ENT>
            <ENT>07/25/13</ENT>
            <ENT>07/25/13</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">Mid-Year</ENT>
            <ENT A="02">WAIVED</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Year-End</ENT>
            <ENT>12/31/13</ENT>
            <ENT>01/31/14</ENT>
            <ENT>01/31/14</ENT>
          </ROW>
          <TNOTE>
            <SU>1</SU>The reporting period always begins the day after the closing date of the last report filed. If the committee is new and has not previously filed a report, the first report must cover all activity that occurred before the committee registered as a political committee up through the close of books for the first report due.</TNOTE>
        </GPOTABLE>
        <SIG>
          <DATED>Dated: February 6, 2013.</DATED>
          
          <P>On behalf of the Commission,</P>
          <NAME>Ellen L. Weintraub,</NAME>
          <TITLE>Chair, Federal Election Commission.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03225 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6715-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">FEDERAL ELECTION COMMISSION</AGENCY>
        <DEPDOC>[Docket No. 2013-05]</DEPDOC>
        <SUBJECT>Filing Dates for the South Carolina Special Elections in the 1st Congressional District</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Election Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of filing dates for special party nominating convention.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The South Carolina Green Party will select their party's nominee at a Special Party Convention on March 9, 2013. Committees required to file reports in connection with the Special Green Party Convention shall file a 12-day Pre-Convention Report.</P>
        </SUM>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ms. Elizabeth S. Kurland, Information Division, 999 E Street NW., Washington, DC 20463; Telephone: (202) 694-1100; Toll Free (800) 424-9530.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>On January 8, 2013, the Commission approved the filing dates for the Special Primary, Runoff and General Elections that will be held in the First Congressional District to fill the U.S. House seat vacated by Senator Tim Scott. The Special General Election date is May 7, 2013. The Democratic and Republican parties will nominate candidates for that election in Special Primary Elections on March 19, 2013, with Special Runoff Elections held on April 2, 2013, if necessary. At the time the Commission approved the filing requirements for the Special Primary, Runoff and General Elections, no special nominating conventions had been scheduled by any of the other certified political parties in South Carolina.</P>

        <P>The Commission has received additional information that the South Carolina Green Party has scheduled a convention on March 9, 2013, to select their nominee for the Special General Election. Committees required to file reports in connection with the Special Green Party Convention on March 9, 2013, shall file a 12-day Pre-Convention Report. The date for the Special General is unchanged and, as such, this<E T="04">Federal Register</E>Notice only includes information on the filing requirements in connection with the special nominating convention. The reporting requirements in connection with the South Carolina Special General Election<PRTPAGE P="10172"/>were published in the<E T="04">Federal Register</E>on February 4, 2013 (78 FR 7781).</P>
        <HD SOURCE="HD1">Principal Campaign Committees</HD>
        <P>All principal campaign committees of candidates who participate in the South Carolina Special Green Party Convention shall file a 12-day Pre-Convention Report on February 25, 2013. (See charts below for the closing date for the report.)</P>
        <HD SOURCE="HD1">Unauthorized Committees (PACs and Party Committees)</HD>
        <P>Political committees filing on a semi-annual basis in 2013 are subject to special election reporting if they make previously undisclosed contributions or expenditures in connection with the South Carolina Special Green Party Convention or Special General Election by the close of books for the applicable report(s). (See charts below for the closing date for each report.)</P>
        <P>Committees filing monthly that make contributions or expenditures in connection with the South Carolina Special Green Party Convention or Special General Election will continue to file according to the monthly reporting schedule.</P>

        <P>Additional disclosure information in connection with the South Carolina Special Elections may be found on the FEC Web site at<E T="03">http://www.fec.gov/info/report_dates.shtml.</E>
        </P>
        <HD SOURCE="HD1">Disclosure of Lobbyist Bundling Activity</HD>
        <P>Principal campaign committees, party committees and Leadership PACs that are otherwise required to file reports in connection with the special elections must simultaneously file FEC Form 3L if they receive two or more bundled contributions from lobbyists/registrants or lobbyist/registrant PACs that aggregate in excess of $17,100 during the special election reporting periods (see charts below for closing date of each period). 11 CFR 104.22(a)(5)(v) and (b).</P>
        <GPOTABLE CDEF="s50,12,12,12" COLS="4" OPTS="L2,i1">
          <TTITLE>Calendar of Reporting Dates for South Carolina Special Elections</TTITLE>
          <BOXHD>
            <CHED H="1">Report</CHED>
            <CHED H="1">Close of books<SU>1</SU>
            </CHED>
            <CHED H="1">Reg./cert. &amp; overnight mailing deadline</CHED>
            <CHED H="1">Filing deadline</CHED>
          </BOXHD>
          <ROW EXPSTB="03" RUL="s">
            <ENT I="21">
              <E T="02">Quarterly Filing Committees Involved in Only the Special Green Party Convention (03/09/13) Must File:</E>
            </ENT>
          </ROW>
          <ROW EXPSTB="00" RUL="n,s">
            <ENT I="01">Pre-Convention</ENT>
            <ENT>02/17/13</ENT>
            <ENT>02/22/13</ENT>
            <ENT>02/25/13</ENT>
          </ROW>
          <ROW RUL="s">
            <ENT I="01">April Quarterly</ENT>
            <ENT>03/31/13</ENT>
            <ENT>04/15/13</ENT>
            <ENT>04/15/13</ENT>
          </ROW>
          <ROW EXPSTB="03" RUL="s">
            <ENT I="21">
              <E T="02">Semi-annual Filing Committees Involved in Only The Special Green Party Convention (03/09/13) Must File:</E>
            </ENT>
          </ROW>
          <ROW EXPSTB="00" RUL="n,s">
            <ENT I="01">Pre-Convention</ENT>
            <ENT>02/17/13</ENT>
            <ENT>02/22/13</ENT>
            <ENT>02/25/13</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Mid-Year</ENT>
            <ENT>06/30/13</ENT>
            <ENT>07/31/13</ENT>
            <ENT>07/31/13</ENT>
          </ROW>
          <TNOTE>
            <SU>1</SU>These dates indicate the end of the reporting period. A reporting period always begins the day after the closing date of the last report filed. If the committee is new and has not previously filed a report, the first report must cover all activity that occurred before the committee registered as a political committee with the Commission up through the close of books for the first report due.</TNOTE>
        </GPOTABLE>
        <SIG>
          <DATED>Dated: February 6, 2013.</DATED>
          
          <P>On behalf of the Commission,</P>
          <NAME>Ellen L. Weintraub,</NAME>
          <TITLE>Chair, Federal Election Commission.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03226 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6715-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL MARITIME COMMISSION</AGENCY>
        <SUBJECT>Notice of Agreements Filed</SUBJECT>

        <P>The Commission hereby gives notice of the filing of the following agreements under the Shipping Act of 1984. Interested parties may submit comments on the agreements to the Secretary, Federal Maritime Commission, Washington, DC 20573, within ten days of the date this notice appears in the<E T="04">Federal Register</E>. Copies of the agreements are available through the Commission's Web site (<E T="03">www.fmc.gov</E>) or by contacting the Office of Agreements at (202)-523-5793 or<E T="03">tradeanalysis@fmc.gov.</E>
        </P>
        
        <P>
          <E T="03">Agreement No.:</E>012194.</P>
        <P>
          <E T="03">Title:</E>The G6 Alliance Agreement.</P>
        <P>
          <E T="03">Parties:</E>American President Lines, Ltd. and APL Co. Pte, Ltd. (Operating as one Party); Hapag-Lloyd AG; Hyundai Merchant Marine Co., Ltd.; Mitsui O.S.K. Lines, Ltd.; Nippon Yusen Kaisha; and Orient Overseas Container Line, Limited.</P>
        <P>
          <E T="03">Filing Party:</E>David F. Smith, Esq.; Cozen O'Connor; 1627 I Street NW., Suite 1100, Washington, DC 20006.</P>
        <P>
          <E T="03">Synopsis:</E>The agreement authorizes the parties to charter and exchange space on one another's vessels and to coordinate and cooperate with respect to the parties' transportation services and operations in the trade between ports in North Asia, South Asia, Middle East (including the Persian Gulf region), Spain, Italy, Egypt, Panama, Jamaica, and Canada, on the one hand, and U.S. East Coast ports via the Panama and Suez canals, on the other hand, as well as ports and points served via such U.S. and foreign ports.</P>
        
        <P>
          <E T="03">Agreement No.:</E>201220.</P>
        <P>
          <E T="03">Title:</E>Exclusive Agreement for Terminal Services and Stevedoring Services.</P>
        <P>
          <E T="03">Parties:</E>Lake Charles Harbor &amp; Terminal District and Federal Marine Terminals, Inc. (FMT).</P>
        <P>
          <E T="03">Filing Party:</E>C. Jonathan Benner; Thompson Coburn LLC; 1909 K Street NW. Suite 600, Washington, DC 20006.</P>
        <P>
          <E T="03">Synopsis:</E>The agreement permits FMT to provide, on an exclusive basis, all terminal services and stevedoring services only for the cargo handled within the public areas of the Lake Charles city docks.</P>
        <SIG>
          <DATED>Dated: February 8, 2013.</DATED>
          
          <P>By Order of the Federal Maritime Commission.</P>
          <NAME>Karen V. Gregory,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-03325 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6730-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">FEDERAL MARITIME COMMISSION</AGENCY>
        <DEPDOC>[Docket No. 13-02]</DEPDOC>
        <SUBJECT>Lisa Anne Cornell and G. Ware Cornell, Jr. v. Princess Cruise Lines, Ltd. (Corp), Carnival PLC, and Carnival Corporation; Notice of Filing of Complaint and Assignment</SUBJECT>

        <P>Notice is given that a complaint has been filed with the Federal Maritime Commission (Commission) by Lisa<PRTPAGE P="10173"/>Anne Cornell and G. Ware Cornell, Jr., hereinafter “Complainants,” against Princess Cruise Lines, Ltd (Corp), Carnival plc, and Carnival Corporation hereinafter “Respondents.” Complainant alleges that: Respondent Princess Cruise Lines, Ltd (Corp) “is a California corporation which operates pursuant to the Shipping Act of 1984 as a common carrier for hire of passengers from ports in the United States;” Respondent Carnival plc “is a corporation established under the laws of the United Kingdom which does business under the names of Cunard Line, P&amp;O Cruises, and P&amp;O Cruises Australia as a common carrier for hire of passengers from ports in the United States;” and Respondent Carnival Corporation “is the parent corporation of Princes and Carnival plc as well as other cruise lines which operate as common carriers for hire from ports in the United States.”</P>
        <P>Complainant alleges that Respondents, by banning Complainants from traveling on ships operated by Princess and Carnival plc and failing to refund a deposit, violated 46 U.S.C. 41104(10) which provides that “[a] common carrier, either alone or in conjunction with any other person, directly or indirectly, may not  * * *  (10) unreasonably refuse to deal or negotiate  * * *”</P>
        <P>Complainant requests that “the Commission issue appropriate relief, including, but not limited to, entry of a final order enjoining the refusal to deal policy as to Lisa Cornell and Ware Cornell, entry of final order restoring all economic losses as set forth herein in the amount of $33,1000.00 and a award of fees and costs of action.”</P>

        <P>The full text of the complaint can be found in the Commission's Electronic Reading Room at<E T="03">www.fmc.gov.</E>
        </P>
        <P>This proceeding has been assigned to the Office of Administrative Law Judges. The initial decision of the presiding officer in this proceeding shall be issued by February 10, 2014 and the final decision of the Commission shall be issued by June 9, 2014.</P>
        <SIG>
          <NAME>Karen V. Gregory,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-03322 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6730-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">FEDERAL MARITIME COMMISSION</AGENCY>
        <SUBJECT>Ocean Transportation Intermediary License Applicants</SUBJECT>
        <P>The Commission gives notice that the following applicants have filed an application for an Ocean Transportation Intermediary (OTI) license as a Non-Vessel-Operating Common Carrier (NVO) and/or Ocean Freight Forwarder (OFF) pursuant to section 19 of the Shipping Act of 1984 (46 U.S.C. 40101). Notice is also given of the filing of applications to amend an existing OTI license or the Qualifying Individual (QI) for a licensee.</P>

        <P>Interested persons may contact the Office of Ocean Transportation Intermediaries, Federal Maritime Commission, Washington, DC 20573, by telephone at (202) 523-5843 or by email at<E T="03">OTI@fmc.gov</E>.</P>
        
        <FP SOURCE="FP-1">Agility Project Logistics, Inc. (OFF),15600 Morales Road,Houston, TX 77032,Officers:Grant Wattman, President (QI),Larry Weischwill, Senior Vice President,Application Type: QI Change.</FP>
        <FP SOURCE="FP-1">Ally Logistics LLC (NVO &amp; OFF),387 Hatherly Road,Scituate, MA 02066,Officers:Stephen J. Zambo, Member (QI),Stephen A. Zambo, Member,Application Type: New NVO &amp; OFF License.</FP>
        <FP SOURCE="FP-1">Axiom Worldwide Logistix Inc. (OFF),4251 W. John Carpenter Freeway, #100,Irving, TX 75063,Officers:Jeffrey S. Bell, President (QI),Nicki Combs, Secretary,Application Type: New OFF License.</FP>
        <FP SOURCE="FP-1">Brisk Logistics Inc. (NVO &amp; OFF),1677 Elmhurst Road,Elk Grove Village, IL 60007,Officers:Joshua H. Chau, President (QI),Bessie S. Chau, Secretary,Application Type: New NVO &amp; OFF License.</FP>
        <FP SOURCE="FP-1">Delmar International (N.Y.) Inc. dba Delmar International dba Delmar International (USA),(NVO &amp; OFF),One Cross Island Plaza, Suite 115,Rosedale, NY 11422,Officers:Robert Tayler, Vice President (QI),Robert Cutler, President.</FP>
        <FP SOURCE="FP-1">Direct Line Transportation, LLC (NVO),9034 E. Easter Place, Suite #203,Centennial, CO 80112,Officers:Eric S. Bachman, Manager (QI),William F. Vogel, Managing Member,Application Type: New NVO License,Application Type: QI Change.</FP>
        <FP SOURCE="FP-1">Early Bird Pick Up and Delivery, LLC (OFF),128 Magnolia Street,Bridgeport, CT 06610,Officer:Junior Hart, Member (QI),Application Type: New OFF License.</FP>
        <FP SOURCE="FP-1">Fastgrow Logistics (Americas) Inc (NVO),17588 Rowland Street, Suite 266,City of Industry, CA 91748,Officers:Peter Shih, Secretary (QI),Guang Dong, President,Application Type: New NVO License.</FP>
        <FP SOURCE="FP-1">Jerome Okolo and David Newton dba Emunah Global (NVO &amp; OFF),1904 Farnam Street, Suite 610,Omaha, NE 68102,Officers:David D. Newton, Partner (QI),Jerome Okolo, Partner,Application Type: New NVO &amp; OFF License.</FP>
        <FP SOURCE="FP-1">Jolly Forwarding USA, Inc. dba Jollibox Cargo Express dba Pinoy Express Cargo dba Chips R'US (NVO),470 Cloverleaf Drive, Suite A&amp;B,Baldwin Park, CA 91706,Officers:Maria Lourdes A. Timbol, President (QI),Urdelia C. Linayao, Secretary,Application Type: New NVO License.</FP>
        <FP SOURCE="FP-1">Magnum-Ramstr Cargo LLC (NVO &amp; OFF),2 Ethel Road, Suite 202C,Edison, NJ 08817,Officers:Debora A. Sacco-Alterisio, Secretary (QI),Dilip Ram, President,Application Type: New NVO &amp; OFF License.</FP>
        <FP SOURCE="FP-1">Trans World Freight System NYC Corp. (NVO &amp; OFF),14530 156 Street, Suite 206,Jamaica, NY 11434,Officers:Xiumin Wu, President (QI),Philip Chee, Vice President,Application Type: New NVO &amp; OFF License.</FP>
        <FP SOURCE="FP-1">Unity Cargo Management Services USA Inc. (NVO),9690 Telstar Avenue, Suite 222A,El Monte, CA 91731,Officers:Maggie Lok, Secretary (QI),Yuhong aka Morny Lin, CEO,Application Type: New NVO License.</FP>
        <FP SOURCE="FP-1">Victoria Line LLC (NVO &amp; OFF),2000 N.W. 84th Avenue,Miami, FL 33122,Officers: Alberto J. Marino, Managing Member (QI),Jose R. DeVivero, Member,Application Type: New NVO &amp; OFF License.</FP>
        <FP SOURCE="FP-1">Western Direct Express, LLC (NVO &amp; OFF),47602 Kato Road,Fremont, CA 94538,Officers: Efren G. Yap, Vice President (QI),Anthony D. Zimmer, President,Application Type: New NVO &amp; OFF License.</FP>
        <SIG>
          <P>By the Commission.</P>
          
          <DATED>Dated: February 8, 2013.</DATED>
          <NAME>Karen V. Gregory,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-03320 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6730-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL RESERVE SYSTEM</AGENCY>
        <SUBJECT>Change in Bank Control Notices; Acquisitions of Shares of a Bank or Bank Holding Company</SUBJECT>
        
        <P>The notificants listed below have applied under the Change in Bank Control Act (12 U.S.C. 1817(j)) and § 225.41 of the Board's Regulation Y (12 CFR 225.41) to acquire shares of a bank or bank holding company. The factors that are considered in acting on the notices are set forth in paragraph 7 of the Act (12 U.S.C. 1817(j)(7)).</P>

        <P>The notices are available for immediate inspection at the Federal Reserve Bank indicated. The notices also will be available for inspection at the offices of the Board of Governors.<PRTPAGE P="10174"/>Interested persons may express their views in writing to the Reserve Bank indicated for that notice or to the offices of the Board of Governors. Comments must be received not later than February 28, 2013.</P>
        <P>A. Federal Reserve Bank of Kansas City (Dennis Denney, Assistant Vice President) 1 Memorial Drive, Kansas City, Missouri 64198-0001:</P>
        <P>1.<E T="03">Darryn W. Biggerstaff,</E>Canon City, Colorado; to retain voting shares of Canon Bank Corporation, and thereby indirectly retain voting shares of Canon National Bank, both in Canon City, Colorado.</P>
        <SIG>
          <DATED>Board of Governors of the Federal Reserve System, February 8, 2013.</DATED>
          <NAME>Margaret McCloskey Shanks,</NAME>
          <TITLE>Deputy Secretary of the Board.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-03284 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6210-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">GENERAL SERVICES ADMINISTRATION</AGENCY>
        <DEPDOC>[Notice-MV-2013-02; Docket No. 2013-0002; Sequence 3]</DEPDOC>
        <SUBJECT>Public Availability of General Services Administration FY 2012 Service Contract Inventory</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>General Services Administration (GSA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of Public Availability of FY 2012 Service Contract Inventories.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In accordance with Section 743 of Division C of Fiscal Year (FY) 2010 Consolidated Appropriations Act Public Law 111-117, GSA is publishing this notice to advise the public of the availability of the FY 2012 Service Contract Inventories.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>February 13, 2013.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Questions regarding the service contract inventory should be directed to Mr. Paul F. Boyle in the Office of Acquisition Policy at 202-501-0324 or<E T="03">Paul.Boyle@gsa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>In accordance with Section 743 of Division C of Fiscal Year (FY) 2010 Consolidated Appropriations Act Public Law 111-117, GSA is publishing this notice to advise the public of the availability of the FY 2012 Service Contract Inventories. These inventories provide information on service contract actions over $25,000 that were made in FY 2012. The information is organized by function to show how contracted resources are distributed throughout the agency. The inventory has been developed in accordance with guidance issued on December 19, 2011 by the Office of Management and Budget's Office of Federal Procurement Policy (OFPP). OFPP's guidance is available at:<E T="03">http://www.whitehouse.gov/sites/default/files/omb/procurement/memo/service-contract-inventory-guidance.</E>
        </P>

        <P>The GSA has posted its inventory and a summary of the inventory on the GSA.Gov homepage at the following link:<E T="03">http://www.gsa.gov/gsasci.</E>
        </P>
        <SIG>
          <DATED>Dated: February 7, 2013.</DATED>
          <NAME>Laura G. Auletta,</NAME>
          <TITLE>Acting Senior Procurement Executive &amp; Deputy Chief Acquisition Officer, Office of Acquisition Policy, General Services Administration.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03279 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6820-61-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <DEPDOC>[Document Identifier: HHS-OS-18774-60D]</DEPDOC>
        <SUBJECT>Agency Information Collection Activities; Proposed Collection; Public Comment Request</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of the Secretary, HHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In compliance with section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995, the Office of the Secretary (OS), Department of Health and Human Services, announces plans to submit a new Information Collection Request (ICR), described below, to the Office of Management and Budget (OMB). Prior to submitting that ICR to OMB, OS seeks comments from the public regarding the burden estimate, below, or any other aspect of the ICR.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments on the ICR must be received on or before April 15, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Submit your comments to<E T="03">Information.CollectionClearance@hhs.gov</E>or by calling (202) 690-6162.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Information Collection Clearance staff,<E T="03">Information.CollectionClearance@hhs.gov</E>or (202) 690-6162.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>When submitting comments or requesting information, please include the document identifier HHS-OS-18774-60D for reference. Information Collection Request Title: Survey of Physician Time Use Patterns under the Medicare Fee Schedule.</P>
        <P>
          <E T="03">Abstract:</E>This information collection is a survey of physician providers in five specialties (internal medicine, radiology, cardiology, ophthalmology, and orthopedics) to gather information on the clinical time spent in providing selected services as well as related information on the physician's practice.</P>
        <P>
          <E T="03">Need and Proposed Use of the Information:</E>The Office of the Assistant Secretary for Planning and Evaluation is currently conducting a number of studies aimed at producing evidence that will help to improve the accuracy of the Medicare Physician Fee Schedule. Under the Medicare Physician Fee Schedule, payments are based in part on the relative amount of physician work associated with each service. For a number of reasons, payment differentials for Evaluation and Management services relative to procedures, rather than narrowing, have continued to widen over time. While the fee schedule's relative values are updated to reflect changes in medical practice, technology and physician productivity, some have questioned whether the current process adequately reflects these changes. The intended data collection effort would be used to gather information on the time data that is used as an input in the fee schedule. Analyses show that even though work is defined as both time and intensity, final work values are highly correlated with the time measure, with time explaining between 80 and 90 percent of the inter-service variance in work. However, several studies suggest potential flaws in estimates of time associated with pre-, post- and intra-service work, demonstrating that the time estimates used for many services exceed actual times when objectively measured through, for example, operating room logs. The survey data will be used to inform several gaps in knowledge critical to improving the accuracy of the fee schedule, including (i) the strength of the correlation between physician-reported clinical time and fee-schedule time values for surveyed services; (ii) how consistent the relationships are across services and across specialties; (iii) whether the relationships vary across physicians in different types of practice settings, and (iv) whether this approach to gathering time data is feasible and could be scaled up for a larger effort. Likely Respondents: Practicing physicians in 5 specialties.</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<PRTPAGE P="10175"/>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 ICR are summarized in the table below.</P>
        <GPOTABLE CDEF="s50,12,12,12,9.2" COLS="5" OPTS="L2,i1">
          <TTITLE>Total Estimated Annualized Burden—Hours</TTITLE>
          <BOXHD>
            <CHED H="1"/>
            <CHED H="1">Number of<LI>respondents</LI>
            </CHED>
            <CHED H="1">Number of<LI>responses per</LI>
              <LI>respondent</LI>
            </CHED>
            <CHED H="1">Average<LI>burden per</LI>
              <LI>response</LI>
              <LI>(in hours)</LI>
            </CHED>
            <CHED H="1">Total burden hours</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Ineligible</ENT>
            <ENT>45</ENT>
            <ENT>1</ENT>
            <ENT>.05</ENT>
            <ENT>2.25</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">Eligible</ENT>
            <ENT>600</ENT>
            <ENT>1</ENT>
            <ENT>.25</ENT>
            <ENT>150</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Total</ENT>
            <ENT>645</ENT>
            <ENT>1</ENT>
            <ENT>.24</ENT>
            <ENT>152.25</ENT>
          </ROW>
        </GPOTABLE>
        <P>OS specifically 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>
        <SIG>
          <NAME>Darius Taylor,</NAME>
          <TITLE>Deputy, Information Collection Clearance Officer.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03270 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4150-45-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Agency for Healthcare Research and Quality</SUBAGY>
        <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Agency for Healthcare Research and Quality, HHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This notice announces the intention of the Agency for Healthcare Research and Quality (AHRQ) to request that the Office of Management and Budget (OMB) approve the proposed information collection project: “Patient-Reported Health Information Technology and Workflow.” In accordance with the Paperwork Reduction Act, 44 U.S.C. 3501-3521, AHRQ invites the public to comment on this proposed information collection.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments on this notice must be received by April 15, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Written comments should be submitted to: Doris Lefkowitz, Reports Clearance Officer, AHRQ, by email at<E T="03">doris.lefkowitz@AHRQ.hhs.gov.</E>
          </P>
          <P>Copies of the proposed collection plans, data collection instruments, and specific details on the estimated burden can be obtained from the AHRQ Reports Clearance Officer.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Doris Lefkowitz, AHRQ Reports Clearance Officer, (301) 427-1477, or by email at<E T="03">doris.lefkowitz@AHRQ.hhs.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Proposed Project</HD>
        <HD SOURCE="HD2">Patient-Reported Health Information Technology and Workflow</HD>

        <P>Health IT can improve quality of care by arraying relevant information, displaying clinical guidelines, highlighting test values of concern, calculating medication doses, and supporting clinical decisionmaking in many ways (Chaudhry<E T="03">et al.,</E>2006). Successful health IT implementation requires careful attention to the workflow of clinicians and others involved in care delivery. However, few studies have examined how health IT can change workflow in ambulatory physician practices. Further, in most studies that address health IT in ambulatory settings, workflow is not the main focus of the research (Unertl, Weinger, Johnson et al., 2009, Carayon, Karsh, Cartmill<E T="03">et al.,</E>2010a). The health IT literature has not focused on sociotechnical factors, such as patient or provider characteristics, physical environment and layout; technical training and support; functionality and usability of health IT; worker roles, staff workload, stress, and job satisfaction; and communication flows. Important work that does address such factors comes mainly from inpatient settings, or from other countries where the health care system is quite different than in the U.S. (Tjora and Scambler, 2009; Ammenwerth, Iller, and Mahler, 2006; Niazkhani, Pirnejad, de Bont<E T="03">et al.,</E>2008; Niazkhani, Pirnejad, Berg<E T="03">et al.,</E>2009). Although many of these studies have concluded that changes in workflow occur when implementing different health IT applications, few studies have actually examined how workflow changes.</P>
        <P>In recent years there has been an increase in the use of health IT to capture patient reporting of medical histories, symptoms, results of self-testing (e.g., blood glucose levels, blood pressure), weight questions and concerns, over-the-counter medication use, and other information that patients need to share with their care providers. Health IT can elicit such information from patients, and help incorporate it into the flow of information within a physician's practice so that the information is detailed, actionable, timely, and can be used to meet patients' treatment goals. Gathering and integrating information from patients using health IT can include patient surveys and other pre-formatted information collection mechanisms (e-forms), secure messaging (email) between patients and their providers (Byrne, Elliott, and Firek, 2009; Bergmo, Kummervold, Gammon et al., 2005); and patient portals (sometimes referred to as [electronic] personal health records or PHRs, patient portals allow patients to view portions of their medical records [e.g., view laboratory test results] and support other health-related tasks such as making appointments or requesting medication refills). The use of patient-reported information is not yet widely integrated into health IT.</P>
        <P>This project will fill the gaps in the current literature by exploring the influence of sociotechnical factors—for clinicians and their office staff, and for patients—in capturing and using patient-reported information in ambulatory health IT systems and associated workflows. The goal of the project is to answer the following research questions:</P>
        <P>• How does the use of health IT to capture and use patient-reported information support or hinder the workflow from the viewpoints of clinicians, office staff, and patients?</P>

        <P>• How does the sociotechnical context influence workflow related to<PRTPAGE P="10176"/>the capture and use of patient-reported information?</P>
        <P>• How do practices redesign their workflow to incorporate the capture and use of patient-reported information?</P>
        <P>The study will consist of rigorous mixed-methods case studies of six ambulatory care physician practices including three small practices (1-3 physicians and the other clinicians and office staff in their practices) and three medium-sized practices (4-10 physicians, and the other clinicians and office staff in their practices). These case studies will be conducted during multiday (3 to 4 days) site visits to collect information for this exploratory research. The multiple case study research approach of Eisenhardt and colleagues (Brown &amp; Eisenhardt, 1997; Eisenhardt, 1989) will guide data collection and data analysis, to elucidate health IT workflows and important sociotechnical factors (for patients, clinicians, and office staff) in the capture and use of patient-reported information.</P>
        <P>A focus of the case studies will be to identify current workflows related to patient-reported information, and determine the work system factors that influence workflows (barriers and facilitators). In particular, data collected from the six practices will help identify bottlenecks and sources of delay, unnecessary steps or duplication, rework to correct errors or inconsistencies, role ambiguity, missing information, and lack of data quality controls or reconciliation of inconsistencies. The focus is not on the content of information reported by patients, or how it alters clinicians' diagnostic or treatment decisions. Rather, the focus is on the workflows required to capture, process, and make use of information that patients report to their care providers.</P>
        <P>This study is being conducted by AHRQ through its contractor, Abt Associates Inc., and subcontractors University of Wisconsin-Madison and University of Alabama-Birmingham, pursuant to AHRQ's statutory authority to conduct and support research on health care and on systems for the delivery of such care, including activities with respect to health care technologies and the quality, effectiveness, efficiency, appropriateness and value of health care services including quality measurement and improvement. 42 U.S.C. 299a(a)(1), (2) and (5).</P>
        <HD SOURCE="HD1">Method of Collection</HD>
        <P>To achieve the goal of this project the following activities will be conducted at each of six participating ambulatory physician practices (referred to herein as `study sites'):</P>
        <P>(1) Preliminary Conference Call: The Practice Manager (the individual in each practice who manages day-to-day operations) and the Physician Leader (the physician in each practice who is most knowledgeable about health IT and health IT implementation) will be asked to participate in a preliminary conference call to learn about the study site and what will be expected of their practice as a study site. This call will last approximately one hour and will be completed by up to 2 participants per site for a total of up to 12 participants across sites.</P>
        <P>(2) Pre-Visit Questionnaire: The Practice Manager will be asked to complete a brief questionnaire prior to the site visit, describing the practice size, health IT installed, patient population served, and other general contextual information about the practice and use of health IT. The Pre-Visit Questionnaire will take approximately one hour to complete and will be completed by up to one respondent per study site.</P>
        <P>(3) Practice Tour: Each of the six site visits will begin with a one-hour tour of the practice and discussion with the Practice Manager to observe the physical layout and computer work stations, clarify the purpose of the study and the site visit, and clarify information from the Pre-Visit Questionnaire.</P>
        <P>(4) Interviews with Practice Manager and Physician Leader: Following the tour at each study site, the Practice Manager and Physician Leader will be asked to participate in a one hour interview. The interview with the Practice Manager will focus on the sociotechnical context of the practice, with an emphasis on the social context of the practice. The interview with the Physician Leader will also focus on the sociotechnical context of the practice, and, in particular, the technical aspects of clinicians using the health IT system. The focus will be on the workflow across the practice, not the workflow of these two individuals. This information will be used to create the basic outline or structure of a Workflow Process Map(s), a diagram that shows the temporal sequencing of tasks in relation to other work system elements (person, organization, environment, and tools and technologies). It will also be used to begin to identify potential variation or flexibility in individuals' workflows, and provide context regarding multiple IT systems that may be in use in the practice. The information obtained from these interviews will be augmented by observation of workflows in the practice and interviews with others in the practice, as described in #5 and #6.</P>
        <P>(5) Observations of Clinicians and Office Staff: Researchers will observe between 7 to 20 clinicians (including physicians, nurse practitioners, physician assistants, nurses, medical assistants, and ancillary staff) and between 3 to 7 office staff (including the front desk receptionist, IT staff, clerks, and other non-clinical staff) per study site, depending on site size for a total of up to 81 clinicians and up to 30 office staff observations across the study sites. Observations will take place as clinicians and office staff work to elicit, integrate and work with patient-reported information. Each clinician will be observed for up to two hours and each office staff person will be observed for up to 30 minutes. These observations periods are different because clinicians' work is more complex and varies more from one patient to the next, while office staff work varies less. Observations will focus on processes, bottlenecks, facilitators, workarounds, and points in the workflow when paper information supplements electronic information. Observations of both clinicians and office staff will be recorded on the Observation Form. The observations will be used to create a detailed Workflow Process Map(s). This data collection will not burden the clinic staff and is not included in the burden estimates in Exhibit 1.</P>
        <P>(6) Interviews with Clinicians and Office Staff: Following observations of the workflow, each clinician and office staff person who was observed will be interviewed for up to one hour, for a total of up to 81 clinicians and up to 30 office staff interviews. If there are more clinicians or office staff than can be interviewed during the site visit, those with the most extensive experience with patient-reported information will be selected for interviews. These interviews will include discussion about the sociotechnical context, the workflow observed (see above), facilitators and barriers to capturing and using patient-reported information, and whether there are uncommon workflow patterns that arise occasionally but were not observed. Unlike the interviews with the Physician Leader and Practice Manager, these interviews will focus on the workflow of each individual, not the workflow across the entire practice. The same interview guide will be used for both clinician and office staff interviews.</P>

        <P>(7) Survey of Clinicians and Office Staff: All clinicians and office staff in the six study sites will be invited to respond to a survey. Although there may not be sufficient time on site to<PRTPAGE P="10177"/>observe and interview every clinician and office staff person in the medium-sized practices, all of them will be asked to complete the survey questionnaire. Therefore, the number of survey respondents is greater than the number of observed and interviewed individuals. Up to 10 surveys will be completed at each small-sized study site and up to 35 surveys will be completed at each medium-sized study site, for a total of up to 135 respondents across the six sites. The surveys will be used to collect data regarding attitudes about and perceptions of the health IT workflows staff engage in related to patient-reported information and the impact of health IT on workload, stress, and job satisfaction, because workflow can impact workload and job satisfaction which have been shown to impact quality of care. The survey will also be used to collect data on barriers and facilitators associated with capturing and using patient-reported information.</P>
        <P>(8) Patient Interviews: Patients will be interviewed to understand the workflow of entering or reporting information from the patient's perspective; the extent and adequacy of training or instruction patients received in using the health IT; attitudes about the time it takes to report information; and whether there are challenges, barriers, facilitators, or workarounds commonly used by patients as they report information requested by their care providers. Five patients will be interviewed at each small practice and up to seven at each medium-sized practice, for a total of up to 36 across the six study sites. More patients will be interviewed in the medium-sized practices because there are more clinicians in these practices, and each may have different patterns of interacting with their patients. Interviewing more patients will enhance the ability to capture information about variation in the clinician-patient information sharing and interaction. These interviews will help researchers understand the range of patient experiences.</P>
        <P>(9) Post-Visit Follow-up to Review the Workflow Process Map(s): Following each site visit, researchers will complete the Workflow Process Map(s) for the study site and send it to the Practice Manager and Physician Leader, requesting confirmation that the understanding of their workflows is correct.</P>
        <P>The lessons learned from this research may be used in a variety of ways:</P>
        <P>(1) To identify additional workflow components that ambulatory practices should consider when implementing health IT to capture and use patient-reported information;</P>
        <P>(2) To identify issues relevant to best practice guidelines for health IT implementation;</P>
        <P>(3) To identify issues for consideration in the design and evaluation of other patient-centered health IT tools.</P>
        <P>The study findings will be widely disseminated to health IT researchers and implementers via AHRQ's National Resource Center for Health IT Web site. The study will enhance the existing knowledge about sociotechnical factors that impact health IT workflow, and how small and medium-sized ambulatory practices employ health IT to capture and use patient-reported information as they redesign their workflow to deliver patient-centered care.</P>
        <HD SOURCE="HD1">Estimated Annual Respondent Burden</HD>
        <P>Exhibit 1 shows the estimated annual burden hours for the respondents' time to participate in this research. The Preliminary Conference Call with each site will involve two people, the Practice Manager and the Physician Leader, and will require up to one hour per site. A total of 12 people across the six study sites will be involved. The Pre-Visit Questionnaire and the Practice Tour will be completed by the Practice Manager at each site and will require up to one hour each. The Practice Manager and the Physician Leader at each site (12 individuals in total across the 6 sites) will be separately interviewed to gather in depth information about the sociotechnical context of the practice. The interviews will each take up to one hour to complete. Interviews with Clinicians and Office Staff will be completed with a maximum of 111 clinicians and office staff across the six study sites, and each interview will last up to one hour. A maximum of 135 clinicians and office staff combined (up to 10 for each of three small-sized sites and 35 for each of 3 medium-sized sites) will be asked to complete the clinician and office staff survey, which will take approximately 15 minutes for each respondent to complete. Up to 36 patients will be interviewed (5 in each of the small sites and up to 7 in each of the medium-sized sites). Each interview will take no more than 30 minutes to complete. A total of 12 persons (the Practice Manager and the Physician Leader at each site) will be involved in the Post-Visit Follow-up to Review the Workflow Process Map(s), which will take one hour. The total annual burden hours, is estimated to be 211 hours.</P>
        <P>Exhibit 2 shows the estimated annual cost burden associated with the study sites' time to participate in the research. The total annual cost burden is estimated to be $11,031.</P>
        <GPOTABLE CDEF="s150,12,12,12,12" COLS="5" OPTS="L2,i1">
          <TTITLE>Exhibit 1—Estimated Annualized Burden Hours</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">Hours per<LI>response</LI>
            </CHED>
            <CHED H="1">Total burden<LI>hours</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Preliminary Conference Call</ENT>
            <ENT>12</ENT>
            <ENT>1</ENT>
            <ENT>1</ENT>
            <ENT>12</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Pre-Visit Questionnaire</ENT>
            <ENT>6</ENT>
            <ENT>1</ENT>
            <ENT>1</ENT>
            <ENT>6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Practice Tour</ENT>
            <ENT>6</ENT>
            <ENT>1</ENT>
            <ENT>1</ENT>
            <ENT>6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Interviews with Practice Manager and Physician Leader</ENT>
            <ENT>12</ENT>
            <ENT>1</ENT>
            <ENT>1</ENT>
            <ENT>12</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Interviews with Clinicians and Office Staff</ENT>
            <ENT>111</ENT>
            <ENT>1</ENT>
            <ENT>1</ENT>
            <ENT>111</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Survey of Clinicians and Office Staff</ENT>
            <ENT>135</ENT>
            <ENT>1</ENT>
            <ENT>15/60</ENT>
            <ENT>34</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Patient Interviews</ENT>
            <ENT>36</ENT>
            <ENT>1</ENT>
            <ENT>30/60</ENT>
            <ENT>18</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">Post Visit Follow-up to Review the Workflow Process Map(s)</ENT>
            <ENT>12</ENT>
            <ENT>1</ENT>
            <ENT>1</ENT>
            <ENT>12</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Total</ENT>
            <ENT>330</ENT>
            <ENT>N/A</ENT>
            <ENT>N/A</ENT>
            <ENT>211</ENT>
          </ROW>
        </GPOTABLE>
        <PRTPAGE P="10178"/>
        <GPOTABLE CDEF="s150,12,12,12,12" COLS="5" OPTS="L2,i1">
          <TTITLE>Exhibit 2—Estimated annualized burden hours</TTITLE>
          <BOXHD>
            <CHED H="1">Form name</CHED>
            <CHED H="1">Number of<LI>respondents</LI>
            </CHED>
            <CHED H="1">Total burden<LI>hours</LI>
            </CHED>
            <CHED H="1">Average<LI>hourly wage</LI>
              <LI>rate*</LI>
            </CHED>
            <CHED H="1">Total cost<LI>burden</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Preliminary Conference Call</ENT>
            <ENT>12</ENT>
            <ENT>12</ENT>
            <ENT>
              <SU>a</SU>$67.15</ENT>
            <ENT>$806</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Pre-Visit Questionnaire</ENT>
            <ENT>6</ENT>
            <ENT>6</ENT>
            <ENT>
              <SU>b</SU>46.17</ENT>
            <ENT>277</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Practice Tour</ENT>
            <ENT>6</ENT>
            <ENT>6</ENT>
            <ENT>
              <SU>b</SU>46.17</ENT>
            <ENT>277</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Interviews with Practice Manager and Physician Leader</ENT>
            <ENT>12</ENT>
            <ENT>12</ENT>
            <ENT>
              <SU>a</SU>67.15</ENT>
            <ENT>806</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Interviews with Clinicians and Office Staff</ENT>
            <ENT>111</ENT>
            <ENT>111</ENT>
            <ENT>
              <SU>c</SU>55.00</ENT>
            <ENT>6,105</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Survey of Clinicians and Office Staff</ENT>
            <ENT>135</ENT>
            <ENT>34</ENT>
            <ENT>
              <SU>d</SU>45.98</ENT>
            <ENT>1,563</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Patient Interviews</ENT>
            <ENT>36</ENT>
            <ENT>18</ENT>
            <ENT>
              <SU>e</SU>21.74</ENT>
            <ENT>391</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">Review of the Workflow Process Map(s)</ENT>
            <ENT>12</ENT>
            <ENT>12</ENT>
            <ENT>
              <SU>a</SU>67.15</ENT>
            <ENT>806</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Total</ENT>
            <ENT>330</ENT>
            <ENT>196</ENT>
            <ENT>N/A</ENT>
            <ENT>11,031</ENT>
          </ROW>
          <TNOTE>
            <SU>*</SU>Based upon the mean of the average hourly wages, National Compensation Survey: Occupational wages in the United States May 2011, “U.S. Department of Labor, Bureau of Labor Statistics.”</TNOTE>
          <TNOTE>
            <SU>a</SU>The average wage for Practice Managers ($46.17 per hour) and Physician Leaders ($88.12 per hour) [$88.12 reflects the average for Family and General Practitioners ($85.26 per hour) and Internists, General ($90.97 per hour)].</TNOTE>
          <TNOTE>
            <SU>b</SU>The average U.S. wage for Practice Managers is $46.17 per hour.</TNOTE>
          <TNOTE>
            <SU>c</SU>The weighted average wage for physicians ($88.12 per hour) [$88.12 reflects the average for Family and General Practitioners ($85.26 per hour) and Internists, General ($90.97 per hour)], nurse practitioners and physician assistants ($41.63 per hour) [$41.63 reflects the average for Physician Assistants ($43.01 per hour) and Health Diagnosing and Treating Practitioners, All ($40.24 per hour)], nurses ($33.23 per hour), and Office Staff ($17.94) [reflects the average for Receptionists and Information Clerks ($12.85 per hour), Office and Administration Support Workers, All Other ($16.07 per hour), and Computer Support Specialists ($24.91 per hour)].</TNOTE>
          <TNOTE>
            <SU>d</SU>The weighted average wage for physicians ($88.12), nurse practitioners and physician assistants ($41.63), nurses ($33.23) and office staff ($17.94).</TNOTE>
          <TNOTE>
            <SU>e</SU>The average U.S. hourly wage ($21.74).</TNOTE>
        </GPOTABLE>
        <HD SOURCE="HD1">Request for Comments</HD>
        <P>In accordance with the Paperwork Reduction Act, comments on AHRQ's information collection are requested with regard to any of the following: (a) Whether the proposed collection of information is necessary for the proper performance of AHRQ health care research and health care information dissemination functions, including whether the information will have practical utility; (b) the accuracy of AHRQ's estimate of burden (including hours and costs) of the proposed collection(s) of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information upon the respondents, including the use of automated collection techniques or other forms of information technology.</P>
        <P>Comments submitted in response to this notice will be summarized and included in the Agency's subsequent request for OMB approval of the proposed information collection. All comments will become a matter of public record.</P>
        <SIG>
          <DATED>Dated: February 6, 2012.</DATED>
          <NAME>Carolyn M. Clancy,</NAME>
          <TITLE>Director.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-03217 Filed 2-12-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4160-90-M</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Administration for Children and Families</SUBAGY>
        <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
        <P>
          <E T="03">Title:</E>Tribal TANF Financial Report (ACF-196T).</P>
        <P>
          <E T="03">OMB No.:</E>0970-0345.</P>
        <P>
          <E T="03">Description:</E>Tribes use Form ACF-196T to report expenditures for the Tribal TANF grant. Authority to collect and report this information is found in the Personal Responsibility and Work Opportunity Reconciliation Act of 1996 (PRWORA), Public Law 104-193. Tribal entities with approved Tribal plans for implementation of the TANF program are required by Section 412(h) of the Social Security Act to report financial data. Form ACF-196T provides for the collection of data regarding Federal expenditures. Failure to collect this data would seriously compromise the Administration for Children and Families' (ACF) ability to monitor expenditures. This information is also used to estimate outlays and may be used to prepare ACF budget submissions to Congress. Financial management of the program would be seriously compromised if the expenditure data were not collected. 45 CFR part 286 subpart E requires the strictest controls on funding requirements, which necessities review of documentation in support of Tribal expenditures for reimbursement. Comments received from previous efforts to implement a similar Tribal TANF report Form ACF-196T were used to guide ACF in the development of the product presented with this submittal.</P>
        <P>The American Recovery and Reinvestment Act (ARRA) of 2009, Public Law 111-5 has authorized emergency TANF funds to be awarded to States, Tribes, and Territories who meet certain eligibility requirements written in the legislation. TANF Policy Announcement TANF-ACF-PA-2009-01 provides additional guidance on eligibility requirements. Recipients of ARRA funds are to report spending and performance data to Federal agencies quarterly for posting on the public Web site, “Recovery.gov”. Federal agencies are required to collect ARRA expenditures data and the data must be clearly distinguishable from the regular TANF (non-ARRA) funds. Therefore, in order to meet this data collection requirement, the ACF-196T has been modified with the addition two line items and a column to report ARRA expenditures. The collection and posting of this data is to allow the public to see where their tax dollars are spent.</P>
        <P>
          <E T="03">Respondents:</E>All Tribal TANF Agencies.<PRTPAGE P="10179"/>
        </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">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">ACF-196T</ENT>
            <ENT>72</ENT>
            <ENT>4</ENT>
            <ENT>1.5</ENT>
            <ENT>432</ENT>
          </ROW>
        </GPOTABLE>
        <P>
          <E T="03">Estimated Total Annual Burden Hours:</E>432.</P>
  