<?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>87</VOL>
    <NO>198</NO>
    <DATE>Friday, October 14, 2022</DATE>
    <UNITNAME>Contents</UNITNAME>
    <CNTNTS>
        <AGCY>
            <EAR>
                Agriculture
                <PRTPAGE P="iii"/>
            </EAR>
            <HD>Agriculture Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Request for Information:</SJ>
                <SJDENT>
                    <SJDOC>Financial Assistance for Producers and Landowners Determined to Have Experienced Discrimination, </SJDOC>
                    <PGS>62359-62360</PGS>
                    <FRDOCBP>2022-22435</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Census Bureau</EAR>
            <HD>Census Bureau</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Foreign Trade Regulations:</SJ>
                <SJDENT>
                    <SJDOC>Cancellation of the Advanced Export Information Pilot Program, </SJDOC>
                    <PGS>62303</PGS>
                    <FRDOCBP>2022-21748</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Generic Clearance for Questionnaire Pretesting Research, </SJDOC>
                    <PGS>62363</PGS>
                    <FRDOCBP>2022-22362</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Centers Disease</EAR>
            <HD>Centers for Disease Control and Prevention</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Environmental Impact Statements; Availability, etc., </DOC>
                    <PGS>62413-62414</PGS>
                    <FRDOCBP>2022-22370</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Civil Rights</EAR>
            <HD>Civil Rights Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Indiana Advisory Committee, </SJDOC>
                    <PGS>62362-62363</PGS>
                    <FRDOCBP>2022-22384</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Nevada Advisory Committee, </SJDOC>
                    <PGS>62360-62361, 62363</PGS>
                    <FRDOCBP>2022-22374</FRDOCBP>
                      
                    <FRDOCBP>2022-22375</FRDOCBP>
                      
                    <FRDOCBP>2022-22379</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Pennsylvania Advisory Committee, </SJDOC>
                    <PGS>62362</PGS>
                    <FRDOCBP>2022-22383</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Virginia Advisory Committee, </SJDOC>
                    <PGS>62361-62362</PGS>
                    <FRDOCBP>2022-22380</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Coast Guard</EAR>
            <HD>Coast Guard</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Safety Zone:</SJ>
                <SJDENT>
                    <SJDOC>Mystic River, Mystic, CT, </SJDOC>
                    <PGS>62311-62312</PGS>
                    <FRDOCBP>2022-22395</FRDOCBP>
                </SJDENT>
                <SJ>Safety Zones:</SJ>
                <SJDENT>
                    <SJDOC>Reentry Sites; Tampa and Tallahassee, FL, </SJDOC>
                    <PGS>62310-62311</PGS>
                    <FRDOCBP>2022-22391</FRDOCBP>
                </SJDENT>
                <SJ>Special Local Regulation:</SJ>
                <SJDENT>
                    <SJDOC>Eureka Concert Spectator Area, Eureka Channel, Eureka, CA, </SJDOC>
                    <PGS>62308-62310</PGS>
                    <FRDOCBP>2022-22431</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Pacific Coast Port Access Route Study; Availability, </DOC>
                    <PGS>62434</PGS>
                    <FRDOCBP>2022-22339</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Commerce</EAR>
            <HD>Commerce Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Census Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Oceanic and Atmospheric Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Commission Fine</EAR>
            <HD>Commission of Fine Arts</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings, </DOC>
                    <PGS>62398</PGS>
                    <FRDOCBP>2022-22403</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Defense Department</EAR>
            <HD>Defense Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Navy Department</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Defense Innovation Board, </SJDOC>
                    <PGS>62398-62399</PGS>
                    <FRDOCBP>2022-22377</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Education Department</EAR>
            <HD>Education Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Applications for New Awards:</SJ>
                <SJDENT>
                    <SJDOC>Promise Neighborhoods Program, </SJDOC>
                    <PGS>62401</PGS>
                    <FRDOCBP>2022-22424</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Employment and Training</EAR>
            <HD>Employment and Training Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Native American Employment and Training Council, </SJDOC>
                    <PGS>62457-62458</PGS>
                    <FRDOCBP>2022-22402</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Energy Department</EAR>
            <HD>Energy Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Energy Regulatory Commission</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Environmental Protection</EAR>
            <HD>Environmental Protection Agency</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Air Quality State Implementation Plans; Approvals and Promulgations:</SJ>
                <SJDENT>
                    <SJDOC>California; Innovative Clean Transit Regulation, </SJDOC>
                    <PGS>62337-62341</PGS>
                    <FRDOCBP>2022-21910</FRDOCBP>
                </SJDENT>
                <SJ>Prevention of Significant Deterioration and Nonattainment New Source Review:</SJ>
                <SJDENT>
                    <SJDOC>Reconsideration of Fugitive Emissions Rule, </SJDOC>
                    <PGS>62322-62337</PGS>
                    <FRDOCBP>2022-22259</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Cross-Media Electronic Reporting:</SJ>
                <SJDENT>
                    <SJDOC>Authorized Program Revision Approval, Maine Department of Environmental Protection, </SJDOC>
                    <PGS>62407</PGS>
                    <FRDOCBP>2022-22286</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Environmental Impact Statements; Availability, etc., </DOC>
                    <PGS>62407</PGS>
                    <FRDOCBP>2022-22360</FRDOCBP>
                </DOCENT>
            </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>62407-62410</PGS>
                    <FRDOCBP>2022-22323</FRDOCBP>
                      
                    <FRDOCBP>2022-22324</FRDOCBP>
                      
                    <FRDOCBP>2022-22325</FRDOCBP>
                      
                    <FRDOCBP>2022-22326</FRDOCBP>
                      
                    <FRDOCBP>2022-22327</FRDOCBP>
                      
                    <FRDOCBP>2022-22328</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Communications</EAR>
            <HD>Federal Communications Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>62410-62413</PGS>
                    <FRDOCBP>2022-22373</FRDOCBP>
                      
                    <FRDOCBP>2022-22382</FRDOCBP>
                      
                    <FRDOCBP>2022-22385</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Deposit</EAR>
            <HD>Federal Deposit Insurance Corporation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>62413</PGS>
                    <FRDOCBP>2022-22434</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Emergency</EAR>
            <HD>Federal Emergency Management Agency</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Changes in Flood Hazard Determinations, </DOC>
                    <PGS>62436-62438</PGS>
                    <FRDOCBP>2022-22317</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Proposed Flood Hazard Determinations, </DOC>
                    <PGS>62434-62435</PGS>
                    <FRDOCBP>2022-22316</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Energy</EAR>
            <HD>Federal Energy Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>62404-62405</PGS>
                    <FRDOCBP>2022-22364</FRDOCBP>
                </DOCENT>
                <SJ>Application:</SJ>
                <SJDENT>
                    <SJDOC>Alabama Power Co., </SJDOC>
                    <PGS>62405-62406</PGS>
                    <FRDOCBP>2022-22367</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Combined Filings, </DOC>
                    <PGS>62401-62403</PGS>
                    <FRDOCBP>2022-22350</FRDOCBP>
                </DOCENT>
                <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Spire STL Pipeline, LLC, Spire STL Pipeline Project, </SJDOC>
                    <PGS>62406-62407</PGS>
                    <FRDOCBP>2022-22366</FRDOCBP>
                </SJDENT>
                <SJ>Environmental Review Schedule:</SJ>
                <SJDENT>
                    <SJDOC>Gas Transmission Northwest, LLC, GTN XPress Project, </SJDOC>
                    <PGS>62403-62404</PGS>
                    <FRDOCBP>2022-22365</FRDOCBP>
                </SJDENT>
                <SJ>Filing:</SJ>
                <SJDENT>
                    <SJDOC>EnerSmart Imperial Beach BESS, LLC, </SJDOC>
                    <PGS>62403</PGS>
                    <FRDOCBP>2022-22351</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>EnerSmart Mesa Heights BESS, LLC, </SJDOC>
                    <PGS>62404</PGS>
                    <FRDOCBP>2022-22349</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>
                Federal Maritime
                <PRTPAGE P="iv"/>
            </EAR>
            <HD>Federal Maritime Commission</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Demurrage and Detention Billing Requirements, </DOC>
                    <PGS>62341-62358</PGS>
                    <FRDOCBP>2022-22290</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Motor</EAR>
            <HD>Federal Motor Carrier Safety Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Exemption Application:</SJ>
                <SJDENT>
                    <SJDOC>Qualification of Drivers; Hearing, </SJDOC>
                    <PGS>62487-62489</PGS>
                    <FRDOCBP>2022-22341</FRDOCBP>
                      
                    <FRDOCBP>2022-22342</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Fish</EAR>
            <HD>Fish and Wildlife Service</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Endangered and Threatened Species:</SJ>
                <SJDENT>
                    <SJDOC>Designation of Critical Habitat for Chamaecrista lineata var. keyensis (Big Pine Partridge Pea), Chamaesyce deltoidea ssp. serpyllum (Wedge Spurge), etc., </SJDOC>
                    <PGS>62502-62562</PGS>
                    <FRDOCBP>2022-21587</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Designation of Critical Habitat for Sideroxylon reclinatum ssp. austrofloridense (Everglades Bully), Digitaria pauciflora (Florida Pineland Crabgrass), etc., </SJDOC>
                    <PGS>62564-62611</PGS>
                    <FRDOCBP>2022-21604</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Status for Rim Rock Crowned Snake and Key Ring-Necked Snake and Designation of Critical Habitat, </SJDOC>
                    <PGS>62614-62674</PGS>
                    <FRDOCBP>2022-21543</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Food and Drug</EAR>
            <HD>Food and Drug Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Current Good Manufacturing Practice in Manufacturing, Packaging, Labeling, or Holding Operations for Dietary Supplements, </SJDOC>
                    <PGS>62429-62432</PGS>
                    <FRDOCBP>2022-22303</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Text Analysis of Proprietary Drug Name Interpretations, </SJDOC>
                    <PGS>62426-62429</PGS>
                    <FRDOCBP>2022-22301</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Tobacco Products Subject to the Federal Food, Drug, and Cosmetic Act, </SJDOC>
                    <PGS>62414-62416</PGS>
                    <FRDOCBP>2022-22299</FRDOCBP>
                </SJDENT>
                <SJ>Guidance:</SJ>
                <SJDENT>
                    <SJDOC>Comparability Protocols for Postapproval Changes to the Chemistry, Manufacturing, and Controls Information in a New Drug Application, Abbreviated New Drug Application, or Biologics License Application, </SJDOC>
                    <PGS>62417-62419</PGS>
                    <FRDOCBP>2022-22334</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Prescription Drug User Fee Act VII; Independent Assessment of Communication Through Product Quality Information Requests During Application Review; Statement of Work; Request for Comments, </DOC>
                    <PGS>62419-62421</PGS>
                    <FRDOCBP>2022-22335</FRDOCBP>
                </DOCENT>
                <SJ>Request for Information:</SJ>
                <SJDENT>
                    <SJDOC>Discussion Paper:  Distributed Manufacturing and Point of Care Manufacturing of Drugs, </SJDOC>
                    <PGS>62416-62417</PGS>
                    <FRDOCBP>2022-22386</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Request for Nominations for Individuals and Consumer Organizations for Advisory Committees, </DOC>
                    <PGS>62421-62426</PGS>
                    <FRDOCBP>2022-22305</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>General Services</EAR>
            <HD>General Services Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Federal Travel Regulation:</SJ>
                <SJDENT>
                    <SJDOC>Relocation Allowances; Waiver of Certain Provisions of the FTR Chapter 302 for Official Relocation Travel to Locations in Florida, South Carolina, North Carolina, and the Commonwealth of Puerto Rico impacted by Hurricanes Ian and Fiona, </SJDOC>
                    <PGS>62312-62313</PGS>
                    <FRDOCBP>2022-22168</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Health and Human</EAR>
            <HD>Health and Human Services Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Centers for Disease Control and Prevention</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Food and Drug Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Institutes of Health</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>62432-62433</PGS>
                    <FRDOCBP>2022-22319</FRDOCBP>
                </DOCENT>
                <SJ>Charter Amendments, Establishments, Renewals and Terminations:</SJ>
                <SJDENT>
                    <SJDOC>Establishment of the Medicare Drug Rebate and Negotiations Group within the Center for Medicare, </SJDOC>
                    <PGS>62433</PGS>
                    <FRDOCBP>2022-22296</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Homeland</EAR>
            <HD>Homeland Security Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Coast Guard</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Emergency Management Agency</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>U.S. Citizenship and Immigration Services</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Interior</EAR>
            <HD>Interior Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Fish and Wildlife Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Land Management Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Park Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Ocean Energy Management Bureau</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>International Trade Com</EAR>
            <HD>International Trade Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Complaint, </DOC>
                    <PGS>62453-62454</PGS>
                    <FRDOCBP>2022-22353</FRDOCBP>
                </DOCENT>
                <SJ>Investigations; Determinations, Modifications, and Rulings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Certain Artificial Eyelash Extension Systems, Products, and Components Thereof, </SJDOC>
                    <PGS>62455-62456</PGS>
                    <FRDOCBP>2022-22287</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Certain Graphics Systems, Components Thereof, and Digital Televisions Containing the Same, </SJDOC>
                    <PGS>62452-62453</PGS>
                    <FRDOCBP>2022-22356</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Certain Robotic Floor Cleaning Devices and Components Thereof, </SJDOC>
                    <PGS>62451-62452</PGS>
                    <FRDOCBP>2022-22381</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Certain Semiconductors and Devices and Products Containing the Same, Including Printed Circuit Boards, Automotive Parts, and Automobiles, </SJDOC>
                    <PGS>62454-62455</PGS>
                    <FRDOCBP>2022-22288</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>62457</PGS>
                    <FRDOCBP>2022-22436</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Justice Department</EAR>
            <HD>Justice Department</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Data Protection Review Court, </DOC>
                    <PGS>62303-62308</PGS>
                    <FRDOCBP>2022-22234</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Proposed Consent Decree:</SJ>
                <SJDENT>
                    <SJDOC>Clean Air Act, </SJDOC>
                    <PGS>62457</PGS>
                    <FRDOCBP>2022-22289</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Labor Department</EAR>
            <HD>Labor Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Employment and Training Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Labor Statistics Bureau</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Labor Statistics</EAR>
            <HD>Labor Statistics Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Data Users Advisory Committee, </SJDOC>
                    <PGS>62458</PGS>
                    <FRDOCBP>2022-22322</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Land</EAR>
            <HD>Land Management Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Coal Management, </SJDOC>
                    <PGS>62440-62441</PGS>
                    <FRDOCBP>2022-22404</FRDOCBP>
                </SJDENT>
                <SJ>Application:</SJ>
                <SJDENT>
                    <SJDOC>Crystal Park Recreation Area; Beaverhead County, MT; Withdrawal Extension and Public Meeting, </SJDOC>
                    <PGS>62440</PGS>
                    <FRDOCBP>2022-22398</FRDOCBP>
                </SJDENT>
                <SJ>Filing of Plats of Survey:</SJ>
                <SJDENT>
                    <SJDOC>Alaska, </SJDOC>
                    <PGS>62441-62442</PGS>
                    <FRDOCBP>2022-22318</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Legal</EAR>
            <HD>Legal Services Corporation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>62458-62460</PGS>
                    <FRDOCBP>2022-22452</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>
                National Archives
                <PRTPAGE P="v"/>
            </EAR>
            <HD>National Archives and Records Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>National Industrial Security Program Policy Advisory Committee, </SJDOC>
                    <PGS>62460-62461</PGS>
                    <FRDOCBP>2022-22392</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Highway</EAR>
            <HD>National Highway Traffic Safety Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Compliance Labeling Warning Devices, </SJDOC>
                    <PGS>62496-62498</PGS>
                    <FRDOCBP>2022-22297</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Consolidated Vehicles' Owner's Manual Requirements for Motor Vehicles and Motor Vehicle Equipment, </SJDOC>
                    <PGS>62489-62494</PGS>
                    <FRDOCBP>2022-22298</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Denial of Motor Vehicle Defect Petition, </DOC>
                    <PGS>62494-62496</PGS>
                    <FRDOCBP>2022-22394</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Institute</EAR>
            <HD>National Institutes of Health</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>National Institute on Drug Abuse, </SJDOC>
                    <PGS>62433-62434</PGS>
                    <FRDOCBP>2022-22361</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Oceanic</EAR>
            <HD>National Oceanic and Atmospheric Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Fisheries off West Coast States:</SJ>
                <SJDENT>
                    <SJDOC>Pacific Coast Groundfish Fishery; Pacific Coast Groundfish Fishery Management Plan; Amendment 30; 2023-24 Biennial Specifications and Management Measures, </SJDOC>
                    <PGS>62676-62720</PGS>
                    <FRDOCBP>2022-20430</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Flower Garden Banks National Marine Sanctuary Regulations, </DOC>
                    <PGS>62314-62316</PGS>
                    <FRDOCBP>2022-22368</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Fisheries of the South Atlantic, Gulf of Mexico, and Caribbean; Southeast Data, Assessment, and Review, </SJDOC>
                    <PGS>62395-62396</PGS>
                    <FRDOCBP>2022-22389</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Pacific Fishery Management Council, </SJDOC>
                    <PGS>62396-62398</PGS>
                    <FRDOCBP>2022-22390</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>South Atlantic Fishery Management Council, </SJDOC>
                    <PGS>62396</PGS>
                    <FRDOCBP>2022-22388</FRDOCBP>
                </SJDENT>
                <SJ>Taking or Importing of Marine Mammals:</SJ>
                <SJDENT>
                    <SJDOC>Tugs Towing Drill Rig in Cook Inlet, AK, </SJDOC>
                    <PGS>62364-62395</PGS>
                    <FRDOCBP>2022-22343</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Park</EAR>
            <HD>National Park Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Application for Designation as National Recreation Trail or National Water Trail, </SJDOC>
                    <PGS>62443-62444</PGS>
                    <FRDOCBP>2022-22363</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Visitor Perceptions of Climate Change Study, </SJDOC>
                    <PGS>62442-62443</PGS>
                    <FRDOCBP>2022-22369</FRDOCBP>
                </SJDENT>
                <SJ>Inventory Completion:</SJ>
                <SJDENT>
                    <SJDOC>University of California, Berkeley, Berkeley, CA, </SJDOC>
                    <PGS>62444-62445</PGS>
                    <FRDOCBP>2022-22337</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>University of Michigan, Ann Arbor, MI, </SJDOC>
                    <PGS>62445-62446</PGS>
                    <FRDOCBP>2022-22336</FRDOCBP>
                </SJDENT>
                <SJ>Requests for Nominations:</SJ>
                <SJDENT>
                    <SJDOC>Chesapeake and Ohio Canal National Historical Park Commission, </SJDOC>
                    <PGS>62445</PGS>
                    <FRDOCBP>2022-22293</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Navy</EAR>
            <HD>Navy Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Proposed Land Acquisition at the Washington Navy Yard, Washington, DC; Meetings, </SJDOC>
                    <PGS>62399-62400</PGS>
                    <FRDOCBP>2022-22261</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Nuclear Regulatory</EAR>
            <HD>Nuclear Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Application:</SJ>
                <SJDENT>
                    <SJDOC>Abilene Christian University, </SJDOC>
                    <PGS>62463</PGS>
                    <FRDOCBP>2022-22294</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Guide for Assessing, Monitoring, and Mitigating Aging Effects on Electrical Equipment Used in Production and Utilization Facilities, </DOC>
                    <PGS>62462-62463</PGS>
                    <FRDOCBP>2022-22300</FRDOCBP>
                </DOCENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Advisory Committee on Reactor Safeguards, </SJDOC>
                    <PGS>62461-62462</PGS>
                    <FRDOCBP>2022-22352</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Ocean Energy Management</EAR>
            <HD>Ocean Energy Management Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Leasing of Sulfur or Oil and Gas in the Outer Continental Shelf, </SJDOC>
                    <PGS>62446-62451</PGS>
                    <FRDOCBP>2022-22344</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Peace</EAR>
            <HD>Peace Corps</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>62463-62464</PGS>
                    <FRDOCBP>2022-22372</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Pension Benefit</EAR>
            <HD>Pension Benefit Guaranty Corporation</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Actuarial Assumptions for Determining an Employer's Withdrawal Liability, </DOC>
                    <PGS>62316-62322</PGS>
                    <FRDOCBP>2022-22304</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Postal Service</EAR>
            <HD>Postal Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>International Product Change:</SJ>
                <SJDENT>
                    <SJDOC>Priority Mail Express International, Priority Mail International &amp; First-Class Package International Service Agreement, </SJDOC>
                    <PGS>62464</PGS>
                    <FRDOCBP>2022-22387</FRDOCBP>
                </SJDENT>
                <SJ>Product Change:</SJ>
                <SJDENT>
                    <SJDOC>Parcel Select Negotiated Service Agreement, </SJDOC>
                    <PGS>62464</PGS>
                    <FRDOCBP>2022-22306</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Priority Mail Express, Priority Mail, First-Class Package Service, and Parcel Select Service Negotiated Service Agreement, </SJDOC>
                    <PGS>62464-62466</PGS>
                    <FRDOCBP>2022-22311</FRDOCBP>
                      
                    <FRDOCBP>2022-22312</FRDOCBP>
                      
                    <FRDOCBP>2022-22313</FRDOCBP>
                      
                    <FRDOCBP>2022-22314</FRDOCBP>
                      
                    <FRDOCBP>2022-22307</FRDOCBP>
                      
                    <FRDOCBP>2022-22308</FRDOCBP>
                      
                    <FRDOCBP>2022-22309</FRDOCBP>
                      
                    <FRDOCBP>2022-22310</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Presidential Documents</EAR>
            <HD>Presidential Documents</HD>
            <CAT>
                <HD>PROCLAMATIONS</HD>
                <SJ>Special Observances:</SJ>
                <SJDENT>
                    <SJDOC>General Pulaski Memorial Day (Proc. 10474), </SJDOC>
                    <PGS>62299-62300</PGS>
                    <FRDOCBP>2022-22533</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>International Day of the Girl (Proc. 10475), </SJDOC>
                    <PGS>62301-62302</PGS>
                    <FRDOCBP>2022-22534</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>EXECUTIVE ORDERS</HD>
                <DOCENT>
                    <DOC>U.S. Signals Intelligence Activities; Efforts To Enhance Safeguards (EO 14086), </DOC>
                    <PGS>62283-62297</PGS>
                    <FRDOCBP>2022-22531</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Securities</EAR>
            <HD>Securities and Exchange Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
                <SJDENT>
                    <SJDOC>Cboe BZX Exchange, Inc., </SJDOC>
                    <PGS>62466-62483</PGS>
                    <FRDOCBP>2022-22345</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Social</EAR>
            <HD>Social Security Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>62483-62484</PGS>
                    <FRDOCBP>2022-22302</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>State Department</EAR>
            <HD>State Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Imposition of Nonproliferation Measures against Foreign Persons, Including a Ban on U.S. Government Procurement, </DOC>
                    <PGS>62484-62485</PGS>
                    <FRDOCBP>2022-22347</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Surface Transportation</EAR>
            <HD>Surface Transportation Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Release of Waybill Data, </DOC>
                    <PGS>62485</PGS>
                    <FRDOCBP>2022-22315</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Trade Representative</EAR>
            <HD>Trade Representative, Office of United States</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>China's Acts, Policies, and Practices Related to Technology Transfer, Intellectual Property, and Innovation:</SJ>
                <SJDENT>
                    <SJDOC>Conforming Amendments, </SJDOC>
                    <PGS>62485-62486</PGS>
                    <FRDOCBP>2022-22354</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Technical Amendments to Two Exclusions, </SJDOC>
                    <PGS>62486</PGS>
                    <FRDOCBP>2022-22355</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>
                Transportation Department
                <PRTPAGE P="vi"/>
            </EAR>
            <HD>Transportation Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Motor Carrier Safety Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Highway Traffic Safety Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Treasury</EAR>
            <HD>Treasury Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Debt Management Advisory Committee, </SJDOC>
                    <PGS>62498</PGS>
                    <FRDOCBP>2022-22321</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>U.S. Citizenship</EAR>
            <HD>U.S. Citizenship and Immigration Services</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Consideration of Deferred Action for Childhood Arrivals, </SJDOC>
                    <PGS>62439-62440</PGS>
                    <FRDOCBP>2022-22359</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Veteran Affairs</EAR>
            <HD>Veterans Affairs Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Advisory Committee on Prosthetics and Special-Disabilities Programs; Amended, </SJDOC>
                    <PGS>62498-62499</PGS>
                    <FRDOCBP>2022-22378</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Veterans' Advisory Committee on Education, </SJDOC>
                    <PGS>62499</PGS>
                    <FRDOCBP>2022-22358</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <PTS>
            <HD SOURCE="HED">Separate Parts In This Issue</HD>
            <HD>Part II</HD>
            <DOCENT>
                <DOC>Interior Department, Fish and Wildlife Service, </DOC>
                <PGS>62502-62562</PGS>
                <FRDOCBP>2022-21587</FRDOCBP>
            </DOCENT>
            <HD>Part III</HD>
            <DOCENT>
                <DOC>Interior Department, Fish and Wildlife Service, </DOC>
                <PGS>62564-62611</PGS>
                <FRDOCBP>2022-21604</FRDOCBP>
            </DOCENT>
            <HD>Part IV</HD>
            <DOCENT>
                <DOC>Interior Department, Fish and Wildlife Service, </DOC>
                <PGS>62614-62674</PGS>
                <FRDOCBP>2022-21543</FRDOCBP>
            </DOCENT>
            <HD>Part V</HD>
            <DOCENT>
                <DOC>Commerce Department, National Oceanic and Atmospheric Administration, </DOC>
                <PGS>62676-62720</PGS>
                <FRDOCBP>2022-20430</FRDOCBP>
            </DOCENT>
        </PTS>
        <AIDS>
            <HD SOURCE="HED">Reader Aids</HD>
            <P>Consult the Reader Aids section at the end of this issue for phone numbers, online resources, finding aids, and notice of recently enacted public laws.</P>
            <P>To subscribe to the Federal Register Table of Contents electronic mailing list, go to https://public.govdelivery.com/accounts/USGPOOFR/subscriber/new, enter your e-mail address, then follow the instructions to join, leave, or manage your subscription.</P>
        </AIDS>
    </CNTNTS>
    <VOL>87</VOL>
    <NO>198</NO>
    <DATE>Friday, October 14, 2022</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <RULES>
        <RULE>
            <PREAMB>
                <PRTPAGE P="62303"/>
                <AGENCY TYPE="F">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Census Bureau</SUBAGY>
                <CFR>15 CFR Part 30</CFR>
                <DEPDOC>[Docket Number: 220928-0202]</DEPDOC>
                <RIN>RIN 0607-XC066</RIN>
                <SUBJECT>Foreign Trade Regulations (FTR): Cancellation of the Advanced Export Information (AEI) Pilot Program</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Census Bureau, Department of Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Announcement for the cancellation of the Advanced Export Information (AEI) pilot program.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In a Solicitation of Pilot Program Participants in the 
                        <E T="04">Federal Register</E>
                         on January 31, 2014, the Census Bureau announced the implementation of the Advanced Export Information (AEI) pilot program to evaluate a new filing option in the Automated Export System and solicited AEI pilot program participants. The AEI pilot program filing option allowed participating exporters to submit a limited set of Electronic Export Information (EEI) in accordance with existing filing deadlines, followed by the full set of data elements submitted within five calendar days of the date of export. This notification announces that the Census Bureau, in cooperation with the U.S. Customs and Border Protection (CBP), has decided to cancel the AEI pilot program. This decision to eliminate the AEI pilot program as an AES filing option was made because the Census Bureau was unable to conduct sufficient analysis and evaluation of the pilot program due to a lack of adequate participation.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The Census Bureau cancels the Advanced Export Information (AEI) pilot program that was announced in a Solicitation of Pilot Program Participants published at 79 FR 5330 on January 31, 2014, effective December 13, 2022. On and after December 13, 2022, the remaining pilot program participants shall no longer report EEI through the AEI pilot program and instead shall report EEI to the Automated Export System in accordance with the Foreign Trade Regulations at 15 CFR 30.4.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kiesha Downs, Chief, Trade Regulations Branch, Foreign Trade Division, U.S. Census Bureau, Washington, DC 20233-6010, by phone (301) 763-7079, or by email 
                        <E T="03">kiesha.downs@census.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Background</HD>
                <P>The Census Bureau is responsible for collecting, compiling, and publishing trade statistics for the United States under the provisions of Title 13, United States Code (U.S.C.), Chapter 9, Section 301. The Automated Export System (AES) is the primary instrument used for collecting export trade data. The Census Bureau collects Electronic Export Information (EEI) through the AES, the electronic equivalent of the Shipper's Export Declaration (SED). The EEI is reported pursuant to the Foreign Trade Regulations, title 15, Code of Federal Regulations (CFR), part 30. The EEI consists of the data elements set forth in 15 CFR 30.6 for an export shipment and includes information such as the exporter's identifying information and detailed information concerning the exported product. Other agencies use the EEI for the purpose of enforcing U.S. export laws and regulations. Prior to the implementation of the Advanced Export Information (AEI) pilot program, the Foreign Trade Regulations allowed two filing options: predeparture filing and postdeparture filing. The AEI pilot program was introduced as a voluntary program in which selected exporters agreed to submit a limited set of EEI in accordance with existing filing deadlines, followed by the full set of data elements submitted within five calendar days of the date of export.</P>
                <P>
                    The notification to announce implementation of the AEI pilot program and to solicit pilot program participants, which was published in the 
                    <E T="04">Federal Register</E>
                     on January 31, 2014 (79 FR 5330), attracted only seven pilot program participants. As of July 1, 2022, the number of pilot participants dropped to two. Due to low participation, the Census Bureau was unable to conduct sufficient analysis and evaluation of the pilot program. Therefore, the Census Bureau, in cooperation with the U.S. Customs and Border Protection (CBP), has decided to cancel the AEI pilot program, thus eliminating it as an AES filing option. Thus, on and after the effective date of the cancellation of the AEI pilot program, the two remaining pilot program participants shall no longer report EEI through the AEI pilot program, and instead shall report EEI to the AES in accordance with the predeparture and postdeparture filing options as described in the Foreign Trade Regulations, 15 CFR 30.4.
                </P>
                <P>
                    Robert L. Santos, Director, Census Bureau, approved the publication of this notification in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <DATED>Dated: September 30, 2022.</DATED>
                    <NAME>Shannon Wink,</NAME>
                    <TITLE>Program Analyst, Policy Coordination Office, U.S. Census Bureau.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-21748 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-07-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Office of the Attorney General</SUBAGY>
                <CFR>28 CFR Part 201</CFR>
                <DEPDOC>[Docket No. NSD 103; Attorney General Order No. 5517-2022]</DEPDOC>
                <RIN>RIN 1105-AB68</RIN>
                <SUBJECT>Data Protection Review Court</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Justice.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        As authorized and directed by the Executive order of October 7, 2022, “Enhancing Safeguards for United States Signals Intelligence Activities,” this rule amends Department of Justice regulations to establish within the Department a Data Protection Review Court (“DPRC”). The DPRC will review determinations made by the Civil Liberties Protection Officer of the Office of the Director of National Intelligence (“ODNI CLPO”) in response to qualifying complaints that allege certain violations of United States law in the conduct of United States signals intelligence activities. Applications for review by the DPRC must be filed by individuals through the appropriate public authority in a designated foreign 
                        <PRTPAGE P="62304"/>
                        country or regional economic integration organization. To facilitate their independent and impartial review, DPRC judges will not be subject to the day-to-day supervision of the Attorney General and will be subject to removal protections. DPRC decisions, including the direction of appropriate remedial measures to be undertaken by United States intelligence agencies, will be final and binding. Individual complainants will not be informed whether they were subject to signals intelligence activities, but instead will receive a standardized notice that states that the DPRC's review has been completed and either did not identify any covered violations or the DPRC issued a determination requiring any appropriate remediation.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective October 14, 2022.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>J. Bradford Wiegmann, Deputy Assistant Attorney General, National Security Division, United States Department of Justice, Washington, DC 20530; telephone: (202) 514-1057.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Background</HD>
                <P>Section 3 of the Executive order of October 7, 2022 authorizes and directs the Attorney General to issue regulations to establish a Data Protection Review Court as the second level of a two-level redress mechanism. The redress mechanism will provide for the review of qualifying complaints by individuals, filed through appropriate public authorities in designated foreign countries or regional economic integration organizations, alleging certain violations of United States law concerning United States signals intelligence activities. The Executive order of October 7, 2022 implements commitments made by the United States as part of the U.S.-EU Data Privacy Framework announced in March 2022 to foster trans-Atlantic data flows. The Framework was developed in response to a 2020 ruling by the Court of Justice of the European Union that invalidated the European Commission's “adequacy decision” for the United States, which was part of the then-existing U.S.-EU Privacy Shield Framework.</P>
                <P>The new redress mechanism established by the Executive order of October 7, 2022 will have two levels. The first level is the investigation, review, and determination by the Civil Liberties Protection Officer of the Office of the Director of National Intelligence (“ODNI CLPO”) of whether a covered violation occurred and, where necessary, the appropriate remediation in response to a qualifying complaint. As a second level, the complainant or an element of the Intelligence Community may seek review by the DPRC of the ODNI CLPO's determinations.</P>
                <P>The DPRC will be established within the Department of Justice (“Department”), consisting of individuals chosen from outside the United States Government, to provide independent and impartial review of applications for review. Exercising the Attorney General's authority under 28 U.S.C. 511 and 512 to provide his advice and opinion on questions of law and the authority delegated to the Attorney General under the Executive order of October 7, 2022, as delegated to the DPRC in this rule by the Attorney General pursuant to 28 U.S.C. 510, the DPRC will review whether the ODNI CLPO's determination regarding the occurrence of a covered violation was legally correct and supported by substantial evidence and whether, in the event of a covered violation, the ODNI CLPO's determination as to the appropriate remediation was consistent with the Executive order of October 7, 2022.</P>
                <HD SOURCE="HD1">II. Discussion of Rule</HD>
                <P>This rule establishes within the Department a DPRC. The DPRC will review, upon an application for review, the ODNI CLPO's determinations made in response to a qualifying complaint, transmitted through the appropriate public authority in a designated foreign country or regional economic integration organization, from an individual who alleged a covered violation of United States law in the conduct of United States signals intelligence activities that adversely affected the complainant's individual privacy and civil liberties interests.</P>
                <P>The DPRC will consist of six or more judges appointed by the Attorney General from outside the United States Government. To facilitate their independent and impartial review of the applications for review, the judges will not be subject to the day-to-day supervision of the Attorney General and may not be removed or subjected to other adverse action arising from their service on the DPRC, except for instances of misconduct, malfeasance, breach of security, neglect of duty, or incapacity. The DPRC panels will have access to the classified national security information they need to conduct their reviews and make decisions. In accordance with section 3(d)(ii) and (iv) of the Executive order of October 7, 2022, those decisions, including the direction of appropriate remedial measures, will be final and binding with respect to the application for review.</P>
                <P>Applications for review may be filed by an individual complainant after receiving notification that the ODNI CLPO has completed its review or by an element of the Intelligence Community. Applications for review by complainants must be filed through the appropriate public authority in a “qualifying state,” which is defined under the rule as a country or regional economic integration organization designated as a qualifying state by the Attorney General under section 3(f) of the Executive order of October 7, 2022.</P>
                <P>Each application will be reviewed by a three-judge panel of the DPRC convened by the Department's Office of Privacy and Civil Liberties (“OPCL”). Once convened, the presiding judge on the DPRC panel will select a Special Advocate who, in accordance with section 3(d)(i)(C) of the Executive order of October 7, 2022, will assist the panel by advocating regarding the complainant's interest in the matter and by ensuring that the panel is well informed regarding the issues and the law. The Special Advocate will not be the agent of or have an attorney-client relationship with the complainant and, in the interest of national security, will be subject to restrictions on communications with the complainant and the complainant's counsel to ensure that classified or otherwise privileged or protected information, including whether or not the complainant was subject to United States signals intelligence activities, is not disclosed.</P>
                <P>Each DPRC panel will review the application before it to determine whether the ODNI CLPO's determination regarding whether a covered violation occurred was legally correct under the applicable law and supported by substantial evidence and whether any appropriate remediation was consistent with the Executive order of October 7, 2022. If the DPRC panel decides that the CLPO's determination does not meet these requirements, the panel will issue its own determination, including any appropriate remediation. In conducting this review, the panel will interpret the Executive order of October 7, 2022 exclusively according to United States law and legal traditions and, more generally, will be guided by decisions of the United States Supreme Court in the same way as a court established under Article III of the United States Constitution, including decisions on the appropriate deference to be provided relevant determinations of national security officials.</P>
                <P>
                    The panel will conduct its review based on the record of the ODNI CLPO's review, supplemented by any information or submissions from the 
                    <PRTPAGE P="62305"/>
                    complainant, the Special Advocate, or an element of the Intelligence Community. The DPRC panel may also request that the ODNI CLPO supplement the record in response to specific questions from the panel. The DPRC panel's decision will be by majority vote, and the panel will issue a written decision setting out its determinations and the specification of any appropriate remediation.
                </P>
                <P>The individual complainant will not be informed whether they were subject to signals intelligence activities. Instead, the individual will receive a standardized notice that states that the DPRC's review has been completed, namely that “the review either did not identify any covered violations or the Data Protection Review Court issued determinations requiring appropriate remediation,” and that the notification constitutes final agency action.</P>
                <P>OPCL will provide administrative support to the DPRC and the Special Advocates.</P>
                <HD SOURCE="HD1">III. Regulatory Certifications</HD>
                <HD SOURCE="HD2">A. Administrative Procedure Act</HD>
                <P>This rule involves the foreign affairs function of the United States, relates to a matter of agency management or personnel, and involves a matter relating to agency organization, procedure, or practice. As such, this rule is exempt from the usual requirements of prior notice and comment and a 30-day delay in the effective date. See 5 U.S.C. 553(a)(1), (a)(2), (b), and (d).</P>
                <HD SOURCE="HD2">B. Regulatory Flexibility Act</HD>
                <P>An analysis under the Regulatory Flexibility Act was not required for this rule because the Department was not required to publish a general notice of proposed rulemaking for this matter. See 5 U.S.C. 601(2), 604(a).</P>
                <HD SOURCE="HD2">C. Unfunded Mandates Reform Act of 1995</HD>
                <P>
                    This rule will not result in the expenditure by State, local, and tribal governments, in the aggregate, or by the private sector, of $100 million or more in any one year (adjusted for inflation), and it will not significantly or uniquely affect small governments. Therefore, no actions are necessary under the provisions of the Unfunded Mandates Reform Act of 1995, 2 U.S.C 1501 
                    <E T="03">et seq.</E>
                </P>
                <HD SOURCE="HD2">D. Congressional Review Act</HD>
                <P>This rule is not a major rule as defined by the Congressional Review Act, 5 U.S.C. 804(2). Further, because it relates to agency management or personnel, it is not a “rule” as that term is used in the Congressional Review Act, 5 U.S.C. 804(3)(b), and, accordingly, the reporting requirements of 5 U.S.C. 801 do not apply.</P>
                <HD SOURCE="HD2">E. Paperwork Reduction Act of 1995</HD>
                <P>
                    This rule does not impose any new reporting or recordkeeping requirements under the Paperwork Reduction Act of 1995, 44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                </P>
                <HD SOURCE="HD2">F. Executive Orders 12866 and 13563—Regulatory Review</HD>
                <P>Because the rule involves the foreign affairs function of the United States, it is not a “regulation or rule” under section 3(d) of Executive Order 12866, “Regulatory Planning and Review,” and the requirements of that order and Executive Order 13563, “Improving Regulation and Regulatory Review,” accordingly, do not apply. Nevertheless, this rule has been drafted and reviewed in accordance with section 1(b) of Executive Order 12866 and section 1(b) of Executive Order 13563.</P>
                <HD SOURCE="HD2">G. Executive Order 13132—Federalism</HD>
                <P>This rule will not have substantial direct effects on the States, on the relationship between the National Government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, in accordance with section 6 of Executive Order 13132, “Federalism,” the Department has determined that this rule does not have sufficient federalism implications to warrant the preparation of a federalism summary impact statement.</P>
                <HD SOURCE="HD2">H. Executive Order 12988—Civil Justice Reform</HD>
                <P>This rule meets the applicable standards set forth in sections 3(a) and 3(b)(2) of Executive Order 12988, “Civil Justice Reform.”</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 28 CFR Part 201</HD>
                    <P>Claims, Foreign relations, Privacy, Signals intelligence.</P>
                </LSTSUB>
                <REGTEXT TITLE="28" PART="201">
                    <AMDPAR>Accordingly, for the reasons set forth in the preamble, the Department of Justice adds part 201 to chapter I of title 28 of the Code of Federal Regulations to read as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 201—DATA PROTECTION REVIEW COURT</HD>
                        <CONTENTS>
                            <SECHD>Sec.</SECHD>
                            <SECTNO>201.1</SECTNO>
                            <SUBJECT>Purpose.</SUBJECT>
                            <SECTNO>201.2</SECTNO>
                            <SUBJECT>Definitions.</SUBJECT>
                            <SECTNO>201.3</SECTNO>
                            <SUBJECT>Appointment of judges and rules of procedure.</SUBJECT>
                            <SECTNO>201.4</SECTNO>
                            <SUBJECT>Appointment of Special Advocates.</SUBJECT>
                            <SECTNO>201.5</SECTNO>
                            <SUBJECT>Administrative support for the DPRC.</SUBJECT>
                            <SECTNO>201.6</SECTNO>
                            <SUBJECT>Applications for review.</SUBJECT>
                            <SECTNO>201.7</SECTNO>
                            <SUBJECT>Convening of panels, conduct of judges, and independence of the DPRC.</SUBJECT>
                            <SECTNO>201.8</SECTNO>
                            <SUBJECT>Special Advocates.</SUBJECT>
                            <SECTNO>201.9</SECTNO>
                            <SUBJECT>Consideration of applications and decisions.</SUBJECT>
                            <SECTNO>201.10</SECTNO>
                            <SUBJECT>Guiding principles of law.</SUBJECT>
                            <SECTNO>201.11</SECTNO>
                            <SUBJECT>Information security and classified national security information.</SUBJECT>
                            <SECTNO>201.12</SECTNO>
                            <SUBJECT>Disclaimer.</SUBJECT>
                        </CONTENTS>
                        <AUTH>
                            <HD SOURCE="HED">Authority: </HD>
                            <P> 5 U.S.C. 301; 28 U.S.C. 509, 510-512; Executive order of October 7, 2022.</P>
                        </AUTH>
                        <SECTION>
                            <SECTNO>§ 201.1</SECTNO>
                            <SUBJECT>Purpose.</SUBJECT>
                            <P>This part establishes an independent and impartial Data Protection Review Court (DPRC) to consider, in classified proceedings, applications for review of determinations made by the Civil Liberties Protection Officer of the Office of the Director of National Intelligence (ODNI CLPO) in response to qualifying complaints submitted through the redress mechanism established pursuant to section 3 of the Executive order of October 7, 2022, “Enhancing Safeguards for United States Signals Intelligence Activities.”</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.2</SECTNO>
                            <SUBJECT>Definitions.</SUBJECT>
                            <P>The terms “appropriate remediation,” “covered violation,” “element of the Intelligence Community,” “Intelligence Community,” “national security,” and “qualifying complaint” shall have the same meanings as they have in the Executive order of October 7, 2022. The term “qualifying state” means a country or regional economic integration organization designated as a qualifying state by the Attorney General pursuant to section 3(f) of the Executive order of October 7, 2022.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.3</SECTNO>
                            <SUBJECT>Appointment of judges and rules of procedure.</SUBJECT>
                            <P>(a) The Attorney General shall, in consultation with the Secretary of Commerce, the Director of National Intelligence, and the Privacy and Civil Liberties Oversight Board (PCLOB), appoint not fewer than six individuals to serve as judges on the DPRC for four-year renewable terms, choosing individuals who at the time of their initial appointment have not been employees of the executive branch in the previous two years.</P>
                            <P>
                                (b) The Attorney General's appointments shall be informed by the criteria used by the executive branch in assessing candidates for the Federal judiciary, giving weight to any prior judicial experience, and shall be of individuals with appropriate experience in the fields of data privacy and national security law. The Attorney General shall endeavor to ensure that at least half of the judges at any given time have prior judicial experience, and all persons appointed as judges shall be active members in good standing of the bar of a State, Commonwealth, Territory, or 
                                <PRTPAGE P="62306"/>
                                Possession, or of the District of Columbia and shall be duly licensed to practice law.
                            </P>
                            <P>(c) During their term of appointment as judges on the DPRC, such judges shall not have any official duties or employment within the United States Government other than their official duties and employment as judges on the DPRC.</P>
                            <P>(d) The DPRC shall review and adopt by majority vote rules of procedure consistent with the Executive order of October 7, 2022 and this part, which thereafter shall be made publicly available and applied by each DPRC panel convened under § 201.7(a). The rules of procedure may thereafter be amended at such times and in such ways as a majority of the judges may deem necessary and appropriate to accomplish the work of the DPRC. A quorum of six judges shall be required for the initial adoption of and any amendments to the rules of procedure.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.4</SECTNO>
                            <SUBJECT>Appointment of Special Advocates.</SUBJECT>
                            <P>(a) The Attorney General shall, in consultation with the Secretary of Commerce, the Director of National Intelligence, and the PCLOB, appoint no fewer than two individuals to serve as Special Advocates for two-year renewable terms, choosing individuals who at the time of their initial appointment have not been employees of the executive branch in the previous two years.</P>
                            <P>(b) All persons appointed as Special Advocates shall have appropriate experience in the fields of data privacy and national security law, shall be experienced attorneys and active members in good standing of the bar of a State, Commonwealth, Territory, or Possession, or of the District of Columbia, and shall be duly licensed to practice law.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.5</SECTNO>
                            <SUBJECT>Administrative support for the DPRC.</SUBJECT>
                            <P>(a) The Office of Privacy and Civil Liberties of the Department of Justice (OPCL) shall be responsible for providing administrative support to the DPRC and the Special Advocates.</P>
                            <P>(b) The administrative support provided by OPCL shall include the following functions:</P>
                            <P>(1) Facilitating the Attorney General's consultations with other officials regarding the appointment of judges and Special Advocates;</P>
                            <P>(2) Drafting in consultation with relevant agencies rules of procedure and, when requested by the DPRC, any amendments thereto for consideration by the DPRC;</P>
                            <P>(3) Receiving applications for review of determinations made by the ODNI CLPO and receiving from the ODNI CLPO its record of review;</P>
                            <P>(4) Receiving and maintaining the confidentiality of any written information that a complainant filing an application for review wishes to provide to the DPRC and of any responses the complainant or their counsel provides to questions from the Special Advocate;</P>
                            <P>(5) Coordinating with the ODNI CLPO as needed on matters arising from an application for review;</P>
                            <P>(6) Securely maintaining records pursuant to applicable law;</P>
                            <P>(7) Making publicly available information about the DPRC, including the names of the judges and Special Advocates, the rules of procedure, and the process for filing an application for review, and such other information as the DPRC in its discretion deems appropriate for its function; and</P>
                            <P>(8) Providing other administrative support to the DPRC, its panels and judges, and the Special Advocates.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.6</SECTNO>
                            <SUBJECT>Applications for review.</SUBJECT>
                            <P>(a) A complainant may apply for review by the DPRC of a determination made by the ODNI CLPO in response to a qualifying complaint submitted by the complainant by filing an application for review with the appropriate public authority in a qualifying state, for forwarding to OPCL, no later than sixty (60) days after the date, as reported to OPCL by the appropriate public authority in a qualifying state, on which the complainant receives notification that the ODNI CLPO has completed its review.</P>
                            <P>(b) The complainant shall submit with the application for review, through the appropriate authority in a qualifying state, any information, including argument on questions of law or the application of law to the facts, that the complainant wishes to provide to the DPRC. The complainant may be represented by counsel in submitting this information. OPCL shall maintain the confidentiality of such information.</P>
                            <P>(c) An element of the Intelligence Community may apply for review by the DPRC of a determination made by the ODNI CLPO by filing an application for review with OPCL no later than sixty (60) days after the date on which the element of the Intelligence Community receives notification from the ODNI CPLO that the ODNI CLPO has completed its review of the qualifying complaint. An application for review filed by an element of the Intelligence Community may include any information that the element of the Intelligence Community wishes to provide to the DPRC, including argument on questions of law or the application of law to the facts. To prevent the disclosure of classified or otherwise privileged or protected information, the DPRC, Special Advocates, and OPCL shall not provide to the complainant any information relating to the existence, review, or outcome of any application for review filed by an element of the Intelligence Community.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.7</SECTNO>
                            <SUBJECT>Convening of panels, conduct of judges, and independence of the DPRC.</SUBJECT>
                            <P>(a) Upon receipt of an application for review, OPCL shall convene a panel of the DPRC by selecting three judges on a rotating basis, while ensuring if possible that at least one of the judges selected has prior judicial experience.</P>
                            <P>(b) The three judges on a DPRC panel shall select a presiding judge by unanimous agreement. If agreement is not reached within five (5) days of the convening of the DPRC panel, the presiding judge shall be the judge who was selected first by OPCL who has prior judicial experience; if no judge on the DPRC panel has such experience, the presiding judge shall be the judge selected first by OPCL.</P>
                            <P>(c) Judges on a DPRC panel shall conduct themselves in accordance with the Code of Conduct for United States Judges, except that a judge may participate in extrajudicial activities, including business activities, financial activities, non-profit fundraising activities, fiduciary activities, and the practice of law, where such extrajudicial activities do not interfere with the impartial performance of the judge's duties or the effectiveness or independence of the DPRC.</P>
                            <P>
                                (d) A DPRC panel and its judges shall not be subject to the day-to-day supervision of the Attorney General. The Attorney General shall not remove a judge from a DPRC panel, remove a judge from the DPRC prior to the end of the judge's term of appointment under § 201.3(a), or take any other adverse action against a judge arising from service on the DPRC, except for instances of misconduct, malfeasance, breach of security, neglect of duty, or incapacity, after taking due account of the standards in the Rules for Judicial-Conduct and Judicial-Disability Proceedings promulgated by the Judicial Conference of the United States pursuant to the Judicial Conduct and Disability Act (28 U.S.C. 351 
                                <E T="03">et seq.</E>
                                ).
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.8</SECTNO>
                            <SUBJECT>Special Advocates.</SUBJECT>
                            <P>
                                (a) After a DPRC panel is convened under § 201.7(a), the presiding judge shall select a Special Advocate to assist the panel in the consideration of the application for review.
                                <PRTPAGE P="62307"/>
                            </P>
                            <P>(b) The Special Advocate shall upon selection receive from OPCL the application for review and any information that the complainant provided under § 201.6(b). The Special Advocate shall not be the agent of the complainant, consistent with the rules of professional responsibility, and there shall be no attorney-client relationship between the Special Advocate and the complainant.</P>
                            <P>(c) The Special Advocate shall also have access to the record of the ODNI CLPO's review and any information or submissions provided to the DPRC panel by an element of the Intelligence Community.</P>
                            <P>(d) To prevent the disclosure of classified or otherwise privileged or protected information, the Special Advocate shall adhere to the following rules on communications with the complainant or the complainant's counsel:</P>
                            <P>(1) If the complainant did not file an application for review, the Special Advocate shall not communicate with the complainant or the complainant's counsel.</P>
                            <P>(2) If the complainant did file an application for review, the Special Advocate may at any stage submit to OPCL written questions for the complainant or the complainant's counsel. OPCL shall, in consultation with relevant elements of the Intelligence Community, review any such questions to ensure they do not disclose any classified or otherwise privileged or protected information and, subject to that limitation, shall convey the questions through the appropriate public authority in a qualifying state to the complainant or the complainant's counsel, with an invitation to provide written responses to the Special Advocate through the appropriate public authority in a qualifying state.</P>
                            <P>(e) The Special Advocate shall assist the DPRC panel in its consideration of the application for review, including by advocating regarding the complainant's interest in the matter and by ensuring that the DPRC panel is well informed of the issues and the law with respect to the matter. Where the complainant has filed an application for review, the submissions of the Special Advocate to the DPRC shall include the complainant's application for review and the information and responses to questions submitted to the Special Advocate by the complainant.</P>
                            <P>(f) Affected elements of the Intelligence Community shall be provided an opportunity to respond to submissions made by the Special Advocate.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.9</SECTNO>
                            <SUBJECT>Consideration of applications and decisions.</SUBJECT>
                            <P>(a) A DPRC panel shall consider an application for review in a manner that is timely, impartial, and consistent with the Executive order of October 7, 2022 and this part in order to determine whether a covered violation occurred and, if so, to determine any appropriate remediation.</P>
                            <P>(b) A DPRC panel shall conduct its review based on the record of the ODNI CLPO's review and any information or submissions provided by the complainant, the Special Advocate, or an element of the Intelligence Community. A DPRC panel may request that the ODNI CLPO supplement the record with specific explanatory or clarifying information and that the ODNI CLPO make additional factual findings where necessary to enable the DPRC panel to conduct its review.</P>
                            <P>(c) If the DPRC panel finds no evidence in the record indicating that signals intelligence activities occurred involving personal information of or about the complainant, the DPRC panel shall render a decision to that effect.</P>
                            <P>(d) In all other cases, the DPRC panel shall determine:</P>
                            <P>(1) Whether, under the applicable law as set forth in the definition of a covered violation in the Executive order of October 7, 2022, the ODNI CLPO's determination whether a covered violation occurred was legally correct and supported by substantial evidence; and</P>
                            <P>(2) Whether, in the event of a covered violation, the ODNI CLPO's determination as to the appropriate remediation was consistent with the Executive order of October 7, 2022.</P>
                            <P>(e) If a DPRC panel decides that a determination by the ODNI CLPO does not meet the standard set out in paragraph (d) of this section, the DPRC panel shall issue its own determination.</P>
                            <P>(f) Prior to determining an appropriate remediation under paragraph (e) of this section, a DPRC panel shall seek through the ODNI CLPO the views of affected elements of the Intelligence Community regarding the appropriate remediation, including an assessment of impacts on the operations of the Intelligence Community and the national security of the United States. The panel shall take due account of these views as well as customary ways of addressing a violation of the type identified.</P>
                            <P>(g) A DPRC panel shall make its decision by majority vote. Each DPRC panel shall issue a written decision setting out its determinations and the specification of any appropriate remediation. The decision of each DPRC panel shall be final and binding with respect to the application for review before it and shall be controlling only as to that application for review.</P>
                            <P>(h) After the issuance of a written decision under paragraph (g) of this section, OPCL shall forward the decision to the ODNI CLPO. If the complainant submitted an application for review in the case, OPCL shall notify the complainant through the appropriate public authority in a qualifying state, without confirming or denying whether the complainant was subject to signals intelligence activities, that:</P>
                            <P>(1) The DPRC completed its review;</P>
                            <P>(2) The review either did not identify any covered violations or the Data Protection Review Court issued a determination requiring appropriate remediation; and</P>
                            <P>(3) The notification to the complainant constitutes the final agency action in the matter.</P>
                            <P>(i) A DPRC panel shall provide a classified report on information indicating a violation of any authority subject to the oversight of the Foreign Intelligence Surveillance Court to the Assistant Attorney General for National Security, who shall report violations to the Foreign Intelligence Surveillance Court in accordance with its rules of procedure.</P>
                            <P>(j) For each application for review, OPCL shall maintain a record of the information reviewed by the DPRC panel and the decision of the DPRC panel, which records shall be made available for consideration as non-binding precedent to future DPRC panels considering applications for review.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.10</SECTNO>
                            <SUBJECT>Guiding principles of law.</SUBJECT>
                            <P>(a) The Executive order of October 7, 2022 and its terms shall be interpreted by the DPRC exclusively in light of United States law and the United States legal tradition, and not any other source of law.</P>
                            <P>(b) In a DPRC panel's review of an application under § 201.9, the DPRC panel shall be guided by relevant decisions of the United States Supreme Court in the same way as are courts established under Article III of the United States Constitution, including those decisions regarding appropriate deference to relevant determinations of national security officials.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.11</SECTNO>
                            <SUBJECT>Information security and classified national security information.</SUBJECT>
                            <P>
                                (a) All proceedings before and other activities of the DPRC and all activities of the Special Advocates shall be governed by Executive Order 13526 of 
                                <PRTPAGE P="62308"/>
                                December 29, 2009, “Classified National Security Information,” or any successor order, and this part.
                            </P>
                            <P>(b) Judges may serve on a DPRC panel convened under § 201.7(a), and Special Advocates may be selected to assist a DPRC panel under § 201.8(a), only if they hold the requisite security clearances to access classified national security information. The DPRC and Special Advocates shall have no authority to declassify or grant any person access to any classified or otherwise privileged or protected information, including the information reviewed in or information about the existence or outcome of any proceedings before the DPRC or any information that would tend to reveal whether a complainant was subject to signals intelligence activities.</P>
                            <P>(c) The Department of Justice Security Officer shall be responsible for establishing security procedures for proceedings before and other activities of the DPRC and the Special Advocate, and for amending those procedures as necessary.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.12</SECTNO>
                            <SUBJECT>Disclaimer.</SUBJECT>
                            <P>This part governs the ability to obtain review of the ODNI CLPO's determinations by the DPRC in accordance with the redress mechanism established in section 3 of the Executive order of October 7, 2022. This part is not intended to, and does not, create any other entitlement, right, or benefit, substantive or procedural, enforceable at law or in equity by any party against the United States, its departments, agencies, or entities, its officers, employees, or agents, or any other person. This part is not intended to, and does not, modify the availability or scope of any judicial review of the decisions rendered through the redress mechanism, which is governed by existing law.</P>
                        </SECTION>
                    </PART>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <NAME>Merrick B. Garland,</NAME>
                    <TITLE>Attorney General.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22234 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-PF-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 100</CFR>
                <DEPDOC>[Docket Number USCG-2022-0795]</DEPDOC>
                <RIN>RIN 1625-AA08</RIN>
                <SUBJECT>Special Local Regulation; Eureka Concert Spectator Area, Eureka Channel, Eureka, CA</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, Department of Homeland Security (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 local regulation for the navigable waters of Eureka Channel, in the vicinity of Woodley Island, in support of an onshore concert with spectator vessels. This special local regulation is necessary to protect the safety of life on these navigable waters and to ensure the safety of mariners transiting the area from the dangers associated with the large gathering of on water concert spectators. This special local regulation will temporarily establish the spectator area and safe access lane to be used for transit and emergency response access. This regulation is necessary to provide safety of life on the navigable waters during the event, which will be held on October 16, 2022.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective on October 16, 2022 from 11 a.m. until 7 p.m.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        To view documents mentioned in this preamble as being available in the docket, go to 
                        <E T="03">https://www.regulations.gov,</E>
                         type USCG 2022-0795 in the search box and click “Search.” Next, in the Document Type column, select “Supporting &amp; Related Material.”
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions on this rule, call or email LT William Harris, Waterways Management, U.S. Coast Guard; telephone (415) 399-7440, email 
                        <E T="03">SFWaterways@uscg.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Table of Abbreviations</HD>
                <EXTRACT>
                    <FP SOURCE="FP-1">CFR Code of Federal Regulations</FP>
                    <FP SOURCE="FP-1">DHS Department of Homeland Security</FP>
                    <FP SOURCE="FP-1">FR Federal Register</FP>
                    <FP SOURCE="FP-1">NPRM Notice of proposed rulemaking</FP>
                    <FP SOURCE="FP-1">§ Section </FP>
                    <FP SOURCE="FP-1">U.S.C. United States Code</FP>
                </EXTRACT>
                <HD SOURCE="HD1">II. Background Information and Regulatory History</HD>
                <P>The Coast Guard is issuing this temporary 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) because it would be impracticable to do so. This rule must be effective on October 16, 2022, so we lack sufficient time to provide a reasonable comment period and then consider those comments before issuing this rule.</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 of this rule would be contrary to public interest because the rule must be effective on October 16, 2022, to ensure the safety of the participants and vessels during the Concert Event.
                </P>
                <HD SOURCE="HD1">III. Legal Authority and Need for Rule</HD>
                <P>The Coast Guard is issuing this rule under authority in 46 U.S.C. 70041 (previously 33 U.S.C. 1233). The Captain of the Port Sector San Francisco (COTP) has determined that potential hazards associated with a large gathering of on water concert spectators on October 16, 2022, will be a safety concern for anyone within the Eureka Channel. This rule is needed to protect personnel, vessels, and the marine environment in the navigable waters within the special local regulation while the event is taking place.</P>
                <HD SOURCE="HD1">IV. Discussion of the Rule</HD>
                <P>
                    This rule establishes a special local regulation from 11 a.m. until 7 p.m. on October 16, 2022. This special local regulation involves a designated event anchorage in the vicinity of Woodley Island Marine. The event anchorage area will be established from a point along the southeastern shore of Woodley Island at 40°48′34.5″ N, 124°9′19.7″ W; thence along the Samoa Bridge to 40°48′30.3″ N, 124°9′15.7″; thence along the shore to 40°48′24.2″ N, 124°9′30.6″ W; thence to 40°48′29.4″ N, 124°9′32.8″ W and thence to the point of beginning. No vessel may moor or anchor within 50 yards of the southernmost shoreline to allow access for emergency vessels. This special local regulation also involves a no loitering zone to reduce congregating in Eureka Channel during this concert event from a point along the southwestern shore or Woodley Island at 40°48′28.0″ N, 124°10′0.0″ W; thence 
                    <PRTPAGE P="62309"/>
                    along the shore to 40°48′29.4″ N, 124°9′32.8″ W; thence to 40°48′24.2″ N, 124°9′30.6″ W; thence along the shore to 40°48′21.9″ N, 124°9′59.9″ W and thence to the point of beginning.
                </P>
                <HD SOURCE="HD1">V. Regulatory Analyses</HD>
                <P>We developed this rule after considering numerous statutes and Executive orders related to rulemaking. Below we summarize our analyses based on a number of these statutes and Executive orders, and we discuss First Amendment rights of protestors.</P>
                <HD SOURCE="HD2">A. Regulatory Planning and Review</HD>
                <P>Executive Orders 12866 and 13563 direct agencies to assess the costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits. This rule has not been designated a “significant regulatory action,” under Executive Order 12866. Accordingly, this rule has not been reviewed by the Office of Management and Budget (OMB).</P>
                <P>This regulatory action determination is based on the size, location, duration, and the time-of-day of the special local regulation. This special local regulation would impact a small designated area of the Eureka Channel for a short duration. Moreover the Coast Guard will issue a Broadcast Notice to Mariners via VHF-FM marine channel 16 about the zone.</P>
                <HD SOURCE="HD2">B. Impact on Small Entities</HD>
                <P>The Regulatory Flexibility Act of 1980, 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>While some owners or operators of vessels intending to transit the safety zone may be small entities, for the reasons stated in section V.A above, this rule will not have a significant economic impact on any vessel owner or operator.</P>
                <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 call or email the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section.
                </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">C. 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">D. Federalism and Indian Tribal Governments</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 have determined that it is consistent with the fundamental federalism principles and preemption requirements described in Executive Order 13132.</P>
                <P>Also, 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">E. 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">F. Environment</HD>
                <P>
                    We have analyzed this rule under Department of Homeland Security Directive 023-01, Rev. 1, associated implementing instructions, and Environmental Planning COMDTINST 5090.1 (series), which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (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 special local regulation involves a designated event anchorage from a point along the southeastern shore of Woodley Island at 40°48′34.5″ N, 124°9′19.7″ W; thence along the Samoa Bridge to 40°48′30.3″ N, 124°9′15.7″; thence along the shore to 40°48′24.2″ N, 124°9′30.6″ W; thence to 40°48′29.4″ N, 124°9′32.8″ W and thence to the point of beginning. This special local regulation also involves a no loitering zone to reduce congregating in Eureka Channel during this concert event from a point along the southwestern shore or Woodley Island at 40°48′28.0″ N, 124°10′0.0″ W; thence along the shore to 40°48′29.4″ N, 124°9′32.8″ W; thence to 40°48′24.2″ N, 124°9′30.6″ W; thence along the shore to 40°48′21.9″ N, 124°9′59.9″ W and thence to the point of beginning. It is categorically excluded from further review under paragraph L61 of Appendix A, Table 1 of DHS Instruction Manual 023-01-001-01, Rev. 1. A Memorandum For Record supporting this determination is available in the docket. For instructions on locating the docket, see the 
                    <E T="02">ADDRESSES</E>
                     section of this preamble.
                </P>
                <HD SOURCE="HD2">G. Protest Activities</HD>
                <P>
                    The Coast Guard respects the First Amendment rights of protesters. Protesters are asked to call or email 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>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 33 CFR Part 100</HD>
                    <P>Marine safety, Navigation (water), Reporting and recordkeeping requirements, Waterways.</P>
                </LSTSUB>
                <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 100 as follows:</P>
                <PART>
                    <PRTPAGE P="62310"/>
                    <HD SOURCE="HED">PART 100—SAFETY OF LIFE ON NAVIGABLE WATERS</HD>
                </PART>
                <REGTEXT TITLE="33" PART="100">
                    <AMDPAR>1. The authority citation for part 100 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>46 U.S.C. 70041; 33 CFR 1.05-1.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="100">
                    <AMDPAR>2. Add § 100.T11-113 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 100.T11-113</SECTNO>
                        <SUBJECT>Special Local Regulation; Eureka Concert Spectator Area, Eureka Channel, Eureka, CA.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Regulated area.</E>
                             This special local regulation involves a designated event anchorage from a point along the southeastern shore of Woodley Island at 40°48′34.5″ N, 124°9′19.7″ W; thence along the Samoa Bridge to 40°48′30.3″ N, 124°9′15.7″; thence along the shore to 40°48′24.2″ N, 124°9′30.6″ W; thence to 40°48′29.4″ N, 124°9′32.8″ W and thence to the point of beginning. No vessel may moor or anchor within 50 yards of the southernmost shoreline to allow access for emergency vessels. This special local regulation also involves a no-loitering zone to reduce congregating in Eureka Channel during this concert event from a point along the southwestern shore or Woodley Island at 40°48′28.0″ N, 124°10′0.0″ W; thence along the shore to 40°48′29.4″ N, 124°9′32.8″ W; thence to 40°48′24.2″ N, 124°9′30.6″ W; thence along the shore to 40°48′21.9″ N, 124°9′59.9″ W and thence to the point of beginning.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Definitions.</E>
                             As used in this section—
                        </P>
                        <P>
                            <E T="03">Designated representative</E>
                             means a Coast Guard Patrol Commander, including a Coast Guard coxswain, petty officer, or other officer operating a Coast Guard vessel and a Federal, State, and local officer designated by or assisting the Captain of the Port San Francisco (COTP) in the enforcement of the regulations in this section.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Regulations.</E>
                             All attendees are allowed to anchor within the designated event anchorage and are restricted from remaining within the regulated no-loitering area described in paragraph (a) of this section unless authorized by the Captain of the Port San Francisco or their designated representative.
                        </P>
                        <P>(2) To seek permission to access or for inquiries, contact the COTP or the COTP's representative by VHF Channel 22A (157.100 mhz). Those in the regulated area must comply with all lawful orders or directions given to them by the COTP or the designated representative.</P>
                        <P>(3) The COTP will provide notice of the regulated area through advanced notice via broadcast notice to mariners and by on-scene designated representatives.</P>
                        <P>
                            (d) 
                            <E T="03">Enforcement period.</E>
                             This section will be enforced from 11 a.m. to 7 p.m. on October 16, 2022.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <NAME>Taylor Q. Lam,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port San Francisco.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22431 Filed 10-13-22; 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 No. USCG-2022-0807]</DEPDOC>
                <SUBJECT>Safety Zones in Reentry Sites; Tampa and Tallahassee, Florida</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notification of enforcement of regulation.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is activating two safety zones for the SpaceX Commercial Crew-4 mission, reentry vehicle splashdown, and recovery operations. These operations will occur in the U.S. Exclusive Economic Zone (EEZ). Our regulation for safety zones in reentry sites within the Seventh Coast Guard District identifies the regulated areas for this event. No U.S. flagged vessel may enter the safety zones unless authorized by the Captain of the Port St. Petersburg or a designated representative. Foreign-flagged vessels are encouraged to remain outside the safety zones.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        The regulations in 33 CFR 165.T07-0289 will be enforced for the safety zones identified in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section below for the dates and times specified.
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions about this notification of enforcement, call or email Marine Science Technician second class Regina Cuevas, Waterways Management Division, U.S. Coast Guard; telephone 813-228-2191 ext 8333, email 
                        <E T="03">Regina.L.Cuevas@uscg.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>With this document, the Coast Guard Captain of the Port (COTP) St. Petersburg is activating two safety zones as listed in 33 CFR 165.T07-0289(a)(4) through (a)(5), on October 13, 2022 through October 20, 2022 for the SpaceX Commercial Crew-4 mission (Crew-4), reentry vehicle splashdown, and the associated recovery operations in the U.S. EEZ. These two safety zones are located within the COTP St. Petersburg Area of Responsibility (AOR) offshore of Tampa and Tallahassee, Florida. The COTP St. Petersburg is activating these safety zones in order to protect vessels and waterway users from the potential hazards created by reentry vehicle splashdowns and recovery operations in our exclusive economic zone and implements a special activities provision of the William M. (Mac) Thornberry National Defense Authorization Act for Fiscal Year 2021. In accordance with the general regulations in 33 CFR part 165, subpart C, no U.S.-flagged vessel may enter the safety zones unless authorized by the COTP St. Petersburg or a designated representative except as provided in § 165.T07-0289(d)(3). All foreign-flagged vessels are encouraged to remain outside the safety zones.</P>
                <P>
                    There are three other safety zones listed in § 165.T07-0289(a)(1) through (a)(3), which are located within the COTP Jacksonville AOR, that are being simultaneously activated through a separate notification of enforcement of the regulation document issued under Docket Number USCG-2022-0805.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         This notification of enforcement of the regulation can be found at: 
                        <E T="03">https://regulations.gov</E>
                         by searching for docket number USCG-2022-0805.
                    </P>
                </FTNT>
                <P>
                    Twenty-four hours prior to the Crew-4 recovery operations scheduled as early as October 13, 2022, the COTP Jacksonville or COTP St. Petersburg, or designated representative will inform the public whether any of the five safety zones described in § 165.T07-0289, paragraph (a), will remain activated (subject to enforcement). If one of the safety zones described in § 165.T07-0289, paragraph (a), remains activated, it will be enforced for four hours prior to the Crew-4 splashdown and remain activated until announced by Broadcast Notice to Mariners on VHF-FM channel 16, and/or Marine Safety Information Bulletin (as appropriate) that the safety zone is no longer subject to enforcement. After the Crew-4 reentry vehicle splashdown, the COTP or a designated representative will grant general permission to come no closer than 3 nautical miles of any reentry vehicle or space support vessel engaged in the recovery operations, within the activated safety zone described in § 165.T07-0289, paragraph (a). Once the reentry vehicle, and any personnel involved in reentry service, are removed from the water and secured onboard a space support vessel, the COTP or designated representative will issue a Broadcast Notice to Mariners on VHF-FM channel 16 announcing the activated safety zone is no longer subject to enforcement. The recovery 
                    <PRTPAGE P="62311"/>
                    operations are expected to last approximately one hour.
                </P>
                <P>The Coast Guard may be assisted by other Federal, State, or local law enforcement agencies in enforcing this regulation.</P>
                <SIG>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <NAME>Michael P. Kahle,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port Sector St. Petersburg.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22391 Filed 10-13-22; 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-2022-0354]</DEPDOC>
                <RIN>RIN 1625-AA00</RIN>
                <SUBJECT>Safety Zone; Mystic River, Mystic, CT</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 on the Mystic River for the Mystic Seaport Bridge 100th Anniversary Fireworks Display. This action is necessary to provide for the safety of life on the navigable waters in the vicinity of the Mystic Bascule Bridge during a fireworks display. This rule would prohibit persons and vessels from being in the safety zone unless authorized by the Captain of the Port Long Island Sound or a designated representative.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective from 7:45 p.m. through 9:30 p.m. on Saturday, October 15, 2022 with a rain date effective from 7:45 p.m. through 9:30 p.m. on Sunday, October 16, 2022.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        To view documents mentioned in this preamble as being available in the docket, go to 
                        <E T="03">https://www.regulations.gov,</E>
                         type USCG-2022-0354 in the search box and click “Search.” Next, in the Document Type column, select “Supporting &amp; Related Material.”
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions on this rule, call or email Marine Science Technician 2nd Class Mark Paget, Waterways Management Division, Sector Long Island Sound; Tele: (203) 468-4583; Email: 
                        <E T="03">Mark.A.Paget@uscg.mil</E>
                         .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Table of Abbreviations</HD>
                <EXTRACT>
                    <FP SOURCE="FP-1">CFR Code of Federal Regulations</FP>
                    <FP SOURCE="FP-1">COTP Captain of the Port Long Island Sound</FP>
                    <FP SOURCE="FP-1">DHS Department of Homeland Security</FP>
                    <FP SOURCE="FP-1">FR Federal Register</FP>
                    <FP SOURCE="FP-1">NPRM Notice of proposed rulemaking</FP>
                    <FP SOURCE="FP-1">§ Section </FP>
                    <FP SOURCE="FP-1">U.S.C. United States Code</FP>
                </EXTRACT>
                <HD SOURCE="HD1">II. Background Information and Regulatory History</HD>
                <P>On March 16, 2022, the Mystic Chamber of Commerce notified the Coast Guard that it will be conducting a fireworks display to commemorate the Mystic Seaport Bridge 100th Anniversary from 7:45 p.m. to 9:30 p.m. on Saturday, October 15, 2022, with a rain date scheduled from 7:45 p.m. to 9:30 p.m. on Sunday, October 16, 2022. The fireworks are to be launched from a barge in the Mystic River approximately 200 yards west of the Mystic River Boathouse Park, Mystic, CT. Hazards from fireworks displays include accidental discharge of fireworks, dangerous projectiles, and falling hot embers or other debris.</P>
                <P>In response, on August 3, 2022, the Coast Guard published a notice of proposed rulemaking (NPRM) titled Safety Zone; Mystic River, Mystic, CT (87 FR 47381). There we stated why we issued the NPRM, and invited comments on our proposed regulatory action related to this fireworks display. During the comment period that ended September 2, 2022; we received 0 comments.</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 of this rule would be impracticable and contrary to the public interest because immediate action is needed to to facilitate the safety of the persons and vessels involved in the fireworks display.
                </P>
                <HD SOURCE="HD1">III. Legal Authority and Need for Rule</HD>
                <P>The Coast Guard is issuing this rule under authority in 46 U.S.C. 70034 (previously 33 U.S.C. 1231). The Captain of the Port Long Island Sound (COTP) has determined that potential hazards associated with the fireworks to be used in this October 15, 2022 display will be a safety concern for anyone within a 200-yard radius of the barge. This rule is needed to ensure safety of vessels and the navigable waters in the safety zone before, during, and after the scheduled event.</P>
                <HD SOURCE="HD1">IV. Discussion of Comments, Changes, and the Rule</HD>
                <P>As noted above, we received no comments on our NPRM published August 3, 2022. There are no changes in the regulatory text of this rule from the proposed rule in the NPRM.</P>
                <P>This rule establishes a safety zone from 7:45 p.m. through 9:30 p.m. on Saturday, October 15, 2022 with a rain date scheduled from 7:45 p.m. through 9:30 p.m. on Sunday October 16, 2022. The safety zone will cover all navigable waters within 200 yards of a barge in the Mystic River located approximately 200 yards west of the Mystic River Boathouse Park, Mystic, CT. The duration of the zone is intended to ensure the safety of vessels and these navigable waters before, during, and after the scheduled 8 p.m. to 9 p.m. fireworks display. All persons or vessels would be prohibited from entering the safety zone without permission from the COTP or a designated representative.</P>
                <HD SOURCE="HD1">V. Regulatory Analyses</HD>
                <P>We developed this rule after considering numerous statutes and Executive orders related to rulemaking. Below we summarize our analyses based on a number of these statutes and Executive orders, and we discuss First Amendment rights of protestors.</P>
                <HD SOURCE="HD2">A. Regulatory Planning and Review</HD>
                <P>Executive Orders 12866 and 13563 direct agencies to assess the costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits. This rule has not been designated a “significant regulatory action,” under Executive Order 12866. Accordingly, this rule has not been reviewed by the Office of Management and Budget (OMB).</P>
                <P>This regulatory action determination is based on the size, location, and duration of the safety zone. Due to the size of the fall-out zone, vessel traffic will be impeded throughout the duration of the fireworks display.</P>
                <HD SOURCE="HD2">B. Impact on Small Entities</HD>
                <P>The Regulatory Flexibility Act of 1980, 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 received 0 comments from the Small Business Administration on this rulemaking. The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities.</P>
                <P>
                    While some owners or operators of vessels intending to transit the safety 
                    <PRTPAGE P="62312"/>
                    zone may be small entities, for the reasons stated in section V.A above, this rule will not have a significant economic impact on any vessel owner or operator.]
                </P>
                <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 call or email the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section.
                </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">C. 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">D. Federalism and Indian Tribal Governments</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 have determined that it is consistent with the fundamental federalism principles and preemption requirements described in Executive Order 13132.</P>
                <P>Also, 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">E. 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">F. Environment</HD>
                <P>
                    We have analyzed this rule under Department of Homeland Security Directive 023-01, Rev. 1, associated implementing instructions, and Environmental Planning COMDTINST 5090.1 (series), which guide the Coast Guard in complying with the National Environmental Policy Act of 1969(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 a safety zone lasting one hour and 45 minutes that would prohibit entry within 200 yards of a fireworks barge. Normally such actions are categorically excluded from further review under paragraph L60(a) of Appendix A, Table 1 of DHS Instruction Manual 023-01-001-01, Rev. 1. A Record of Environmental Consideration supporting this determination is available in the docket. For instructions on locating the docket, see the 
                    <E T="02">ADDRESSES</E>
                     section of this preamble.
                </P>
                <HD SOURCE="HD2">G. Protest Activities</HD>
                <P>
                    The Coast Guard respects the First Amendment rights of protesters. Protesters are asked to call or email 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>
                <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>
                <PART>
                    <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
                </PART>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>1. The authority citation for part 165 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 46 U.S.C. 70034, 70051; 33 CFR 1.05-1, 6.04-1, 6.04-6, and 160.5; Department of Homeland Security Delegation No. 00170.1, Revision No. 01.2.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>2. Add § 165.T151-0354 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T151-0354</SECTNO>
                        <SUBJECT>Safety Zone; Mystic River, Mystic, CT.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Location.</E>
                             The following area is a safety zone: All waters within a 200 yard radius of the fireworks barge located at 41°21′54″ N, 71°57′59″ W.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Regulations.</E>
                             (1) Under the general safety zone regulations in subpart C of this part, you may not enter the safety zone described in paragraph (a) of this section unless authorized by the COTP or the COTP's designated representative.
                        </P>
                        <P>(2) To seek permission to enter, contact the COTP or the COTP's representative by (203) 468-4444. Those in the safety zone must comply with all lawful orders or directions given to them by the COTP or the COTP's designated representative.</P>
                        <P>
                            (c) 
                            <E T="03">Enforcement period.</E>
                             This section will be enforced from 7:45 p.m. through 9:30 p.m. on October 15, 2022 with a rain date scheduledon October 16, 2022.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>E.J. Van Camp,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port Long Island Sound.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22395 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">GENERAL SERVICES ADMINISTRATION</AGENCY>
                <CFR>41 CFR Chapter 302</CFR>
                <DEPDOC>[Notice-MA-2022-11; Docket No. 2022-0002; Sequence No. 24]</DEPDOC>
                <SUBJECT>Federal Travel Regulation (FTR); Relocation Allowances—Waiver of Certain Provisions of the FTR Chapter 302 for Official Relocation Travel to Locations in Florida, South Carolina, North Carolina, and the Commonwealth of Puerto Rico Impacted by Hurricanes Ian and Fiona</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Government-wide Policy (OGP), General Services Administration (GSA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notification of waiver.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>GSA informs Federal agencies that certain provisions of the FTR governing official relocation travel are temporarily waived for Florida, South Carolina, North Carolina, and the Commonwealth of Puerto Rico locations impacted by Hurricanes Ian and Fiona and that GSA Bulletin FTR 23-03, containing additional details of that waiver, is available.</P>
                </SUM>
                <EFFDATE>
                    <PRTPAGE P="62313"/>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>October 14, 2022.</P>
                    <P>
                        <E T="03">Applicability Date:</E>
                         This waiver is retroactively applicable for official relocation travel performed on or after the incident period dates impacted by Hurricanes Ian and Fiona. The FTR Bulletin expires 180 days from the respective effective dates, unless GSA publishes a document in the 
                        <E T="04">Federal Register</E>
                         extending or rescinding it.
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Rick Miller, Senior Policy Analyst, Office of Government-wide Policy, Office of Asset and Transportation Management, at 202-501-3822 or by email at 
                        <E T="03">travelpolicy@gsa.gov.</E>
                         Please cite Notice of GSA Bulletin FTR 23-03.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Background</HD>
                <P>Federal agencies authorize relocation entitlements to those individuals listed at FTR § 302-1.1 and those assigned under the Government Employees Training Act (GETA) (5 U.S.C. chapter 41) which must be used within one year. Some agencies will authorize Temporary Quarters Subsistence Expenses (TQSE) and a Househunting trip (HHT) to assist employees with temporary expenses when relocating to the new duty station. The FTR limits the location of where temporary lodging may occur, how long they may receive assistance, and at what per diem rate expenses are based. Hurricanes Ian and Fiona have affected locations in Florida, South Carolina, North Carolina, and the Commonwealth of Puerto Rico, which has resulted in various travel-related disruptions to relocating employees.</P>
                <P>As a result of the storm damage caused by Hurricanes Ian and Fiona, agencies should consider delaying all non-essential relocations to the affected areas given the statutory 120-day maximum for TQSE. Due to the lasting effects of the storm damage to these affected areas, finding lodging facilities and/or adequate meals may be difficult, and distance involved may be great, resulting in increased cost for relocation per diem expenses.</P>
                <P>Accordingly, GSA allows agencies to determine whether to implement waivers of time limits established by the FTR for completion of all aspects of relocation, temporary quarter's locations at the new duty station and per diem rates for TQSE, and per diem rates for HHTs as of the following dates for the locations specified: (a) September 23, 2022, based on the Presidential Disaster Declaration DR-4673-FL dated September 29, 2022, to the locations in Florida, (b) September 23, 2022, based on the Presidential Disaster Declaration DR-4675 dated September 30, 2022, to the locations in Florida, (c) September 25, 2022, based on the Presidential Disaster Declaration EM-3585-SC dated September 29, 2022, to the locations in South Carolina, (d) September 28, 2022, based on the Presidential Disaster Declaration EM-3586-NC dated October 1, 2022, to the locations in North Carolina, and (e) September 17, 2022, based on the Presidential Disaster Declaration DR-4671-PR dated September 21, 2022, to the locations in the Commonwealth of Puerto Rico.</P>
                <P>
                    GSA Bulletin FTR 23-03 can be viewed at 
                    <E T="03">https://www.gsa.gov/ftrbulletins.</E>
                </P>
                <SIG>
                    <NAME>Saul Japson,</NAME>
                    <TITLE>Principal Deputy Associate Administrator, Office of Government-wide Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22168 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P </BILCOD>
        </RULE>
    </RULES>
    <VOL>87</VOL>
    <NO>198</NO>
    <DATE>Friday, October 14, 2022</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <PRORULES>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="62314"/>
                <AGENCY TYPE="F">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <CFR>15 CFR Part 922</CFR>
                <DEPDOC>[Docket No. 221006-0212]</DEPDOC>
                <RIN>RIN 0648-BL38</RIN>
                <SUBJECT>Flower Garden Banks National Marine Sanctuary Regulations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of National Marine Sanctuaries (ONMS), National Ocean Service (NOS), National Oceanic and Atmospheric Administration (NOAA), Department of Commerce (DOC).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule; request for public comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The National Oceanic and Atmospheric Administration (NOAA) is issuing this proposed rule to remove a provision from one section of the existing Flower Garden Banks National Marine Sanctuary (FGBNMS) regulations, regarding the resolution of conflicting Federal agency regulations by the Director of the Office of National Marine Sanctuaries.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by November 14, 2022.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments on this document, identified by NOAA-NOS-2022-0047, 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">https://www.regulations.gov</E>
                         and enter NOAA-NOS-2022-0047 in the Search box. Click on the “Comment” icon, complete the required fields, and enter or attach your comments.
                    </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 NOAA. 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. NOAA will accept anonymous comments (enter “N/A” in the required fields if you wish to remain anonymous).
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        George P. Schmahl, Superintendent, Flower Garden Banks National Marine Sanctuary, 4700 Avenue U, Building 216, Galveston, Texas 77551, at 409-356-0383, or 
                        <E T="03">george.schmahl@noaa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Introduction</HD>
                <HD SOURCE="HD2">A. Flower Garden Banks National Marine Sanctuary</HD>
                <P>The National Marine Sanctuaries Act (NMSA) authorizes the Secretary of Commerce (Secretary) to designate and protect, as national marine sanctuaries, areas of the marine environment that are of special national significance due to their conservation, recreational, ecological, historical, scientific, cultural, archeological, educational, or aesthetic qualities. Day-to-day management of national marine sanctuaries is delegated by the Secretary to NOAA's ONMS. The primary objective of the NMSA is to protect nationally significant marine resources, including biological features such as coral reefs, and cultural resources, such as historic shipwrecks and archaeological sites. The mission of FGBNMS is to identify, protect, conserve, and enhance the natural and cultural resources, values, and qualities of the sanctuary and its regional environment for this and future generations.</P>
                <P>FGBNMS is located in the northwestern Gulf of Mexico approximately 70 to 115 miles (113 to 185 kilometers) off the coasts of Texas and Louisiana. These offshore areas encompass a wide range of geologic features and habitat conditions that support several distinct biological communities, including the northernmost stony coral reefs in the continental United States. The banks, reefs, and similar formations provide the foundation for essential benthic habitats that support a wide variety of species. They are home to the most significant examples of coral and algal reefs, mesophotic and deepwater coral communities, and other biological assemblages in the Gulf of Mexico. The combination of location and geology makes FGBNMS extremely productive and diverse, and presents a unique set of challenges for managing and protecting its natural wonders.</P>
                <P>When NOAA first designated FGBNMS on December 5, 1991 (56 FR 63634), and Congress subsequently passed a law recognizing the designation on January 17, 1992 (Pub. L. 102-251, Title I, Sec. 101), the sanctuary consisted of only two areas known as East and West Flower Garden Banks (56 FR 63634). Among other things, FGBNMS regulated a narrow range of activities, established permit and certification procedures, and exempted certain U.S. Department of Defense (DOD) activities from the sanctuary's prohibitions (56 FR 63634). The regulations also exempted activities necessary to respond to emergencies threatening life, property, or the environment (56 FR 63634). Those regulations became effective on January 18, 1994 (58 FR 65664). In 1996, Congress added Stetson Bank to the sanctuary (Pub. L. 104-283). The boundaries of Stetson Bank and West Flower Garden Bank were later amended to improve administrative efficiencies and increase the precision of all boundary coordinates based on new positioning technology (65 FR 81175, Dec. 22, 2000). Subsequently, on January 19, 2021, NOAA issued a final rule for the expansion of FGBNMS (86 FR 4953). The final rule went into effect on March 22, 2021 (86 FR 15404), and expanded the boundaries of FGBNMS from approximately 56 square miles to approximately 160 square miles (145 square kilometers to 414 square kilometers), and increased the number of protected reefs and banks (86 FR 4953). FGBNMS now protects East and West Flower Garden Banks, Stetson Bank, Horseshoe Bank, MacNeil Bank, Rankin/28 Fathom Banks, Bright Bank, Geyer Bank, Elvers Bank, McGrail Bank, Bouma Bank, Sonnier Bank, Rezak Bank, Sidner Bank, Parker Bank, and Aldrice Bank.</P>
                <P>
                    The areas designated as FGBNMS are currently managed by several Federal agencies that share jurisdiction over the area and its resources. These agencies include: the U.S. Department of the Interior, Bureau of Ocean Energy Management (BOEM) and Bureau of Safety and Environmental Enforcement (BSEE), who share primary jurisdiction 
                    <PRTPAGE P="62315"/>
                    over offshore energy exploration and development; the U.S. Environmental Protection Agency (EPA), which is responsible for protecting the quality of the nation's waters; NOAA's National Marine Fisheries Service (NMFS) and Gulf of Mexico Fishery Management Council (GMFMC), which jointly manage the U.S fisheries; and, as previously stated above, NOAA's ONMS, which provides comprehensive management and protection to the sanctuary. Additionally, DoD and U.S. Coast Guard activities, as well as commercial shipping and other marine activities, occur in and around the waters of FGBNMS.
                </P>
                <HD SOURCE="HD2">B. Summary of the Proposed Revision</HD>
                <P>This action responds to the issues raised by Federal agency partners during interagency review of the final rule to expand FGBNMS (86 FR 4953), and during interagency review of a separate, unrelated interim final rule to update and reorganize the existing sanctuary regulations and eliminate redundancies (87 FR 29606). Specifically, the Federal agency partners expressed concern that the sanctuary regulation at 15 CFR 922.122(b) does not reflect existing practice and may be an overreach of the ONMS Director's delegated authority under the NMSA. Specifically, section 922.122(b) provides that if a Federal agency regulation and a Sanctuary regulation conflict, then the regulation deemed by the Director of the ONMS as being more protective of Sanctuary resources and qualities shall govern. The NMSA does not contain express language that prescribes how potential conflicts with other Federal regulations are to be resolved. The NMSA instead establishes a framework “to facilitate to the extent compatible with the primary objective of resource protection, all public and private uses of the resources of these marine areas not prohibited pursuant to other authorities” (16 U.S.C. 1431(b)(6)). The NMSA also “provide[s] authority for comprehensive and coordinated conservation and management of . . . marine areas, and activities affecting them, in a manner which complements existing regulatory authorities” (16 U.S.C. 1431(b)(2)). To ensure sanctuary regulations facilitate compatible use and complement existing regulatory authorities, the NMSA directs NOAA to consult with other Federal agencies on the proposed designation of new sites or expansion of existing sites (16 U.S.C. 1433(b)(2), 1434(a)(4)). It is through this consultation process, which occurs before the designation or expansion of sanctuaries, that potential conflicts among Federal agency regulations are typically resolved or avoided. NOAA is presently unaware of any situation in which 15 CFR 922.122(b) has ever been triggered, and section 922.122(b) does not reflect NOAA's preferred approach to resolve potential interagency regulatory conflicts. Therefore, to address the concerns raised by Federal partners, NOAA proposes to remove the existing language from 15 CFR 922.122(b) to reflect existing practice and better track the NMSA. The remaining paragraphs of 15 CFR 922.122 would remain unchanged.</P>
                <P>A provision similar to 15 CFR 922.122(b) also appears in Article V of the terms of designation codified in appendix B of 15 CFR part 922, subpart L. This action does not modify that provision. Pursuant to section 304(a)(4) of the NMSA, the terms of designation may only be modified by the same procedures by which the designation is made. The process includes scoping, proposal, consultation with Federal agency partners and public review, as well as review by Congress. Because additional procedures are required to alter the terms of designation, NOAA is using regulatory action as the first step in the process.</P>
                <HD SOURCE="HD1">II. Classification</HD>
                <HD SOURCE="HD2">A. National Environmental Policy Act</HD>
                <P>NOAA concludes that this action will not have a significant effect, individually or cumulatively, on the human environment. This action is categorically excluded from the requirement to prepare an Environmental Assessment or Environmental Impact Statement in accordance with the NOAA Categorical Exclusion G7 because there are no extraordinary circumstances precluding the application of this categorical exclusion. Specifically, this action is a notice of an administrative and legal nature, and any future effects of subsequent actions are too broad, speculative, or conjectural to lend themselves to meaningful analysis and will be subject to later NEPA analysis. This action would remove language that inaccurately describes how a conflict of regulatory authorities between Federal agencies would be addressed, and therefore, is an administrative issue. It does not commit the outcome of any particular Federal action taken by NOAA or other Federal agencies. Furthermore, individual Federal actions taken by ONMS or other Federal agencies will be subject to additional case-by-case analysis, as required under NEPA, which will be completed as any new Federal actions are submitted for specific projects and activities. In these situations, NOAA or other Federal agencies will ensure that the appropriate NEPA documentation is prepared prior to taking any final action. Any such NEPA analysis would describe the impacts of prospective projects or operations.</P>
                <HD SOURCE="HD2">B. Executive Order 12866: Regulatory Impact</HD>
                <P>This notice of proposed rulemaking has been determined to be not significant within the meaning of Executive Order 12866. NOAA has considered this action under E.O. 12866. Based on that review, this action is not expected to have an annual effect on the economy of $100 million or more, or have an adverse effect in a material way on the economy. Furthermore, this action would not create a serious inconsistency or otherwise interfere with an action taken or planned by another agency; or materially alter the budgetary impact of entitlements, grants, user fees, or loan programs or the rights and obligations of recipients thereof; or raise novel or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in this E.O.</P>
                <HD SOURCE="HD2">C. Regulatory Flexibility Act</HD>
                <P>The Regulatory Flexibility Act (RFA) requires Federal agencies to prepare an analysis of a rule's impact on small entities whenever the agency is required to publish a rule, unless the head of the agency can certify, pursuant to 5 U.S.C. 605(b), that the action will not have a significant economic impact on a substantial number of small entities.</P>
                <P>Pursuant to section 605(b), the Chief Counsel for Regulations for the Department of Commerce has certified to the Office of Advocacy of the Small Business Administration that the proposed modifications of the regulations at 15 CFR part 922 would not have a significant economic impact on a substantial number of small entities.</P>
                <P>
                    Because the provision proposed to be removed from the FGBNMS regulations addresses potential conflicts of law between Federal agencies, NOAA does not anticipate any impact on small businesses. This proposed rule also does not establish any new reporting, recordkeeping, or other compliance requirements. This proposed action is strictly an administrative action with implications anticipated only on Federal agency partners. Further, since 15 CFR 922.122(b) has never been triggered, NOAA is strongly convinced there are no overarching impacts of this proposed administrative regulatory 
                    <PRTPAGE P="62316"/>
                    update on any party, whether Federal or otherwise.
                </P>
                <P>Since the impacts of this proposed administrative rule are only intended as an administrative flexibility for Federal agencies, NOAA does not anticipate an impact on marine sanctuary stakeholders that entail small businesses, including entities in the following North American Industry Classification System (NAICS) categories: consumptive and non-consumptive recreational charter businesses (NAICS codes 483114 and 483112); commercial fishing businesses (NAICS codes 114112 (Shellfish Fishing), 114111 (Finfish and mackerel fishing), and 114119 (other marine fishing)); sightseeing businesses (NAICS code 487210); and diving businesses (NAICS codes 611620 (Sports and Recreation Instruction), 561990 (All Other Support Services), 339920 (Sporting and Athletic Goods Manufacturing), 459110 (Sporting Goods Retailers)).</P>
                <P>Based on the analysis presented above, NOAA concludes that the proposed action would result in no negative impact on a substantial number of small entities. Therefore, an initial regulatory flexibility analysis is not required and none has been prepared.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 15 CFR Part 922</HD>
                    <P>Administrative practice and procedure, Marine resources, Natural resources.</P>
                </LSTSUB>
                <SIG>
                    <NAME>Nicole R. LeBoeuf,</NAME>
                    <TITLE>Assistant Administrator for Ocean Services and Coastal Zone Management, National Ocean Service, National Oceanic and Atmospheric Administration.</TITLE>
                </SIG>
                <P>Accordingly, for the reasons set forth above, NOAA proposes to amend part 922, title 15 of the Code of Federal Regulations as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 922—NATIONAL MARINE SANCTUARY PROGRAM REGULATIONS</HD>
                </PART>
                <AMDPAR>1. The authority citation for part 922 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        16 U.S.C. 1431 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SECTION>
                    <SECTNO>§ 922.122</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <AMDPAR>2. Amend § 922.122 by removing and reserving paragraph (b).</AMDPAR>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22368 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-NK-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">PENSION BENEFIT GUARANTY CORPORATION</AGENCY>
                <CFR>29 CFR Part 4213</CFR>
                <RIN>RIN 1212-AB54</RIN>
                <SUBJECT>Actuarial Assumptions for Determining an Employer's Withdrawal Liability</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Pension Benefit Guaranty Corporation.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Pension Benefit Guaranty Corporation is proposing to provide interest rate assumptions that may be used by a plan actuary in determining a withdrawing employer's liability under a multiemployer plan.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by November 14, 2022 to be assured of consideration.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments may be submitted by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: https://www.regulations.gov.</E>
                         Follow the online instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Email: reg.comments@pbgc.gov</E>
                         with subject line “4213 proposed rule.”
                    </P>
                    <P>
                        • 
                        <E T="03">Mail or Hand Delivery:</E>
                         Regulatory Affairs Division, Office of the General Counsel, Pension Benefit Guaranty Corporation, 445 12th Street SW, Washington, DC 20024-2101.
                    </P>
                    <P>Commenters are strongly encouraged to submit comments electronically. PBGC expects to have limited personnel available to process comments submitted on paper by mail or hand delivery. Until further notice, any comments submitted on paper will be considered to the extent practicable.</P>
                    <P>
                        All submissions received must include the agency's name (Pension Benefit Guaranty Corporation, or PBGC) and refer to the 4213 proposed rule. All comments received will be posted without change to PBGC's website, 
                        <E T="03">www.pbgc.gov,</E>
                         including any personal information provided. Do not submit comments that include any personally identifiable information or confidential business information.
                    </P>
                    <P>Copies of comments may also be obtained by writing to Disclosure Division, Office of the General Counsel, Pension Benefit Guaranty Corporation, 445 12th Street SW, Washington, DC 20024-2101, or calling 202-326-4040 during normal business hours. If you are deaf or hard of hearing, or have a speech disability, please dial 7-1-1 to access telecommunications relay services.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        John Ginsberg (
                        <E T="03">ginsberg.john@pbgc.gov</E>
                        ), Assistant General Counsel, Multiemployer Law Division, Office of the General Counsel, at 202-229-3714, or Gregory Katz (
                        <E T="03">katz.gregory@pbgc.gov</E>
                        ), Attorney, Regulatory Affairs Division, Office of the General Counsel, at 202-227-8918. If you are deaf or hard of hearing, or have a speech disability, please dial 7-1-1 to access telecommunications relay services.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Executive Summary</HD>
                <P>The Pension Benefit Guaranty Corporation (PBGC) is proposing to provide interest rate assumptions that may be used by a plan actuary in determining a withdrawing employer's liability under a multiemployer plan.</P>
                <P>PBGC's legal authority for this rulemaking comes from section 4213 of the Employee Retirement Income Security Act of 1974 (ERISA), which authorizes PBGC to prescribe actuarial assumptions and methods for purposes of determining an employer's withdrawal liability, and from section 4002(b)(3) of ERISA, which authorizes PBGC to issue regulations to carry out the purposes of title IV of ERISA.</P>
                <HD SOURCE="HD1">Background</HD>
                <HD SOURCE="HD2">Withdrawal Liability</HD>
                <P>
                    PBGC administers two independent insurance programs for private-sector defined benefit pension plans under title IV of ERISA—one for single-employer defined benefit pension plans and one for multiemployer defined benefit pension plans (multiemployer plans). In general, a multiemployer plan is a collectively bargained plan involving two or more unrelated employers. The multiemployer program protects benefits of approximately 10.9 million workers and retirees in approximately 1,360 plans.
                    <SU>1</SU>
                    <FTREF/>
                     This proposed rule applies only to multiemployer plans.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         See PBGC FY 2021 Annual Report, page 3 at 
                        <E T="03">https://www.pbgc.gov/sites/default/files/documents/pbgc-annual-report-2021.pdf.</E>
                    </P>
                </FTNT>
                <P>
                    Under ERISA, an employer that withdraws from a multiemployer plan may be liable to the plan for withdrawal liability, which generally represents the employer's share of any unfunded vested benefits (UVBs) that the plan may have at the end of the plan year immediately preceding the plan year in which the employer withdraws. UVBs are the amount by which the present value of nonforfeitable benefits under the plan as of the valuation date exceeds the value of plan assets as of that date. The plan actuary determines the present value of all of the plan's nonforfeitable benefits using actuarial assumptions and methods. The assumptions include 
                    <PRTPAGE P="62317"/>
                    the interest rate—sometimes called the “discount rate”—that is used to discount future benefit payments to their present value and the mortality tables used to determine the probability that each benefit payment will be made. Assuming a higher interest rate results in lower UVBs, whereas a lower rate leads to higher UVBs. Disputes between plans and employers about the value of UVBs are resolved through mandatory arbitration, and then, if necessary, litigation.
                </P>
                <P>
                    For plans terminated by mass withdrawal, PBGC's regulation on Duties of Plan Sponsor Following Mass Withdrawal (29 CFR part 4281) specifies actuarial assumptions for valuing benefits, including interest rates described in Appendix B to PBGC's regulation on Allocation of Assets in Single-Employer Plans (29 CFR part 4044).
                    <SU>2</SU>
                    <FTREF/>
                     These interest rates are based on the average market price of a life annuity, which PBGC determines from a quarterly survey of insurance companies and can be used to approximate the cost of purchasing annuities to cover benefits. Annuity prices are derived in part from yields on high-quality corporate bonds.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         29 CFR 4281.13.
                    </P>
                </FTNT>
                <P>For ongoing plans, section 4213(a) of ERISA provides—</P>
                <EXTRACT>
                    <P>The corporation may prescribe by regulation actuarial assumptions which may be used by a plan actuary in determining the unfunded vested benefits of a plan for purposes of determining an employer's withdrawal liability under this part. Withdrawal liability under this part shall be determined by each plan on the basis of—</P>
                    <P>(1) actuarial assumptions and methods which, in the aggregate, are reasonable (taking into account the experience of the plan and reasonable expectations) and which, in combination, offer the actuary's best estimate of anticipated experience under the plan, or</P>
                    <P>(2) actuarial assumptions and methods set forth in the corporation's regulations for purposes of determining an employer's withdrawal liability.</P>
                </EXTRACT>
                <P>Because PBGC has not issued regulations under section 4213(a)(2), withdrawal liability determinations governed by section 4213(a) have heretofore been made under section 4213(a)(1).</P>
                <HD SOURCE="HD2">Actuarial Variety in Selection of Assumptions</HD>
                <P>Plans have used a variety of approaches to determine withdrawal liability; three common approaches are described in the following paragraphs.</P>
                <P>One approach uses the same interest rate assumption that is used to determine minimum funding requirements, based on the expected average return on plan assets over the long term. This approach applies the interest rate assumption used under section 431(b)(6) of the Internal Revenue Code (Code) and section 304(b)(6) of ERISA (funding interest rate assumption) to satisfy both standards under section 4213(a)(1)—that the actuarial assumptions and methods used to determine withdrawal liability are in the aggregate reasonable (taking into account the experience of the plan and reasonable expectations) and in combination offer the actuary's best estimate of anticipated experience.</P>
                <P>Another approach focuses on the contrast between contributing employers and withdrawing employers. This approach identifies contributing employers as continuing to participate in the plan's investment portfolio and share in future gains and losses, including the risk of increased contributions if plan investments do not earn as much as the assumed funding interest rate. This approach considers that a withdrawing employer ceases to participate in the plan's investment experience because the employer is settling its liabilities once and for all and bears no risk of future losses. This approach therefore considers the use of settlement interest rate assumptions prescribed by PBGC under section 4044 of ERISA (4044 rates) to be appropriate to determine the amount sufficient to release a withdrawing employer from any future financial obligations to the plan. Those interest rate assumptions can be used to approximate the market price of purchasing annuities to cover the withdrawing employer's share of the plan's benefit liabilities, which are generally paid in the form of life annuities. From this perspective, the plan trustees' investment risk appetite, asset allocation choices, or the actuary's best estimate of the plan's future investment returns following the withdrawal are not relevant to the withdrawal liability assessment.</P>
                <P>A third approach uses an interest rate assumption that employs both funding and settlement interest rate assumptions. For example, the actuary might value unfunded benefits using the funding interest rate assumption, and value funded benefits using a settlement interest rate assumption like PBGC's 4044 rates.</P>
                <HD SOURCE="HD2">Recent Disputes</HD>
                <P>
                    There has been increasing litigation over withdrawal liability determinations, centered on the interest rate assumption used to discount liabilities of ongoing plans. In five cases since 2018 (and an unknown number of arbitrations), a withdrawing employer has challenged its withdrawal liability assessment by arguing that the interest assumption that the plan actuary used to value nonforfeitable benefits failed to satisfy section 4213(a)(1) of ERISA because it was lower than the actuary's best estimate of anticipated average returns on plan investments. Court decisions have varied 
                    <SU>3</SU>
                    <FTREF/>
                     and some have noted PBGC's unused authority to issue a regulation prescribing assumptions that may be used under section 4213(a)(2).
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See United Mine Workers of Am. 1974 Pension Plan</E>
                         v. 
                        <E T="03">Energy W. Mining Co.,</E>
                         No. 20-7054, 2022 WL 2568025 (D.C. Cir. July 8, 2022) (re 4044 rates); 
                        <E T="03">Sofco Erectors, Inc.</E>
                         v. 
                        <E T="03">Trs. of Ohio, Operating Eng'rs, Pension Fund,</E>
                         15 F. 4th 407 (6th Cir. 2021) (re blend of 4044 rates and funding interest rate assumption); 
                        <E T="03">GCIU Employer Retirement Fund</E>
                         v. 
                        <E T="03">MNG Enterprises, Inc.,</E>
                         No. 2:21-cv-00061, 2021 WL 3260079 (C.D. Cal., July 8, 2021) (re 4044 rates), 
                        <E T="03">appeals filed,</E>
                         Nos. 21-55864, 21-55923; 
                        <E T="03">Manhattan Ford Lincoln, Inc.</E>
                         v. 
                        <E T="03">UAW Local 259 Pension Fund,</E>
                         331 F. Supp. 3d 365 (D.N.J. 2018) (re blended rates), 
                        <E T="03">appeal voluntarily dismissed; New York Times Co.</E>
                         v. 
                        <E T="03">Newspaper and Mail Deliverers'-Publishers' Pension Fund,</E>
                         303 F. Supp. 3d 236 (S.D.N.Y. 2018) (re blended rates), 
                        <E T="03">appeals voluntarily dismissed.</E>
                         In the cross-appeals of the 
                        <E T="03">New York Times</E>
                         decision, PBGC participated as 
                        <E T="03">amicus curiae.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See United Mine Workers,</E>
                         2022 WL 2568025, at *2; 
                        <E T="03">Sofco Erectors,</E>
                         15 F. 4th at 420; 
                        <E T="03">Manhattan Ford Lincoln,</E>
                         331 F. Supp. 3d at 393.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Special Financial Assistance Interim Final Rule</HD>
                <P>
                    On July 12, 2021 (at 86 FR 36598), PBGC published an interim final rule on special financial assistance (SFA) under new section 4262 of ERISA.
                    <SU>5</SU>
                    <FTREF/>
                     In footnote 18 of that rule's preamble, PBGC indicated that it intends to propose a separate rule of general applicability under section 4213(a) of ERISA to prescribe actuarial assumptions that may be used by a plan actuary in determining an employer's withdrawal liability. This proposed rule carries out PBGC's stated intention.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The final rule on SFA was published July 8, 2022, at 87 FR 40968.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Overview of Regulation</HD>
                <P>
                    Section 4213(a)(2) of ERISA authorizes PBGC to set forth in its regulations actuarial assumptions and methods that may be used by a plan actuary for the purpose of determining an employer's withdrawal liability as an alternative to the assumptions and methods used under section 4213(a)(1). This rule is being proposed under section 4213(a)(2) to make clear that use of 4044 rates, either as a standalone assumption or combined with funding interest assumptions represents a valid approach to selecting an interest rate assumption to determine withdrawal liability in all circumstances. Withdrawing employers will not be 
                    <PRTPAGE P="62318"/>
                    making future plan contributions, and ERISA accounts for this by requiring an employer to settle its share of the plan's unfunded liabilities. In the event of worse than expected investment performance or other actuarial experience following an employer's withdrawal, the plan cannot seek additional funds from that employer. Thus, a withdrawing employer shifts its share of investment risk and other risks to the plan and its remaining employers. If a party promising a pension, as an employer participating in a multiemployer plan indirectly does, were to shift all investment risk, mortality risk, and other asset and liability risks to an annuity provider, that party must pay the premium amount necessary to fund the promised pension liability. Accordingly, it is reasonable to base the amount needed to settle the employer's share of the liability on the market price of settling pension liabilities by purchasing annuities from private insurers.
                </P>
                <P>The use of actuarial assumptions and methods prescribed by PBGC under section 4213(a)(2) would not be subject to the requirements of section 4213(a)(1), and accordingly, the plan's actuary would be permitted to determine withdrawal liability under the proposed rule without regard to section 4213(a)(1).</P>
                <P>
                    The proposed rule would specifically permit the use of an interest rate anywhere in the spectrum from 4044 rates alone to funding rates alone.
                    <SU>6</SU>
                    <FTREF/>
                     In the case of an interest assumption that involves two or more rates to value a plan's liabilities, such as a yield curve or the use of separate interest rates for benefits expected to be covered by current assets and for other benefits, this proposed rule would apply to the single interest rate that would result in the same liability measure as the multiple rates. PBGC requests comments on whether the final rule should restrict the allowable options to a narrower range of interest rates or to only specific methodologies for determining interest rates. In particular, should the top of the range of permitted interest rates under section 4213(a)(2) be lower than the typical funding interest rate assumption (which represents the expected return on a portfolio with a significant allocation to return-seeking assets)? PBGC also requests comments on what should be the relationship, if any, between (a) the estimated date of plan insolvency, expected investment mix, and/or funded ratio, and (b) permitted withdrawal liability assumptions.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The proposed rule would not override other statutory or regulatory provisions requiring the use of specific rates such as PBGC's regulation on Duties of Plan Sponsor Following Mass Withdrawal (29 CFR part 4281) which specifies actuarial assumptions for valuing benefits.
                    </P>
                </FTNT>
                <P>
                    Under § 4213.11(c) of the proposed rule, each assumption and method used, other than the interest assumption, would have to be reasonable (taking into account the experience of the plan and reasonable expectations). Additionally, the assumptions and methods other than the interest assumption would, in combination, have to offer the actuary's best estimate of anticipated experience under the plan. Note that the standards under proposed § 4213.11(c) echo the current standard for selecting actuarial assumptions for multiemployer funding under section 431(c)(3) of the Code and section 304(c)(3) of ERISA, which has been updated since the enactment of ERISA.
                    <SU>7</SU>
                    <FTREF/>
                     As with assumptions adopted under those sections, assumptions used under § 4213.11(c) would reflect the actuary's judgment as an independent professional generally bound by actuarial standards of practice. The standards in proposed § 4213.11(c) would apply to assumptions and methods other than interest assumptions. As discussed earlier in this preamble, consideration of the anticipated experience of the plan in selecting withdrawal liability interest assumptions is not necessarily appropriate in light of a withdrawing employer's lack of continued shared investment experience.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         section 9307(b) of the Omnibus Budget Reconciliation Act of 1987 (OBRA '87) (Pub. L. 100-203).
                    </P>
                </FTNT>
                <P>PBGC requests comments on whether the final rule should specify assumptions or methods other than interest assumptions. Also, if PBGC were to specify assumptions under section 4213(a) of ERISA that included demographic assumptions, such as mortality assumptions, that differed from plans' demographic assumptions, would plans be unlikely to use the PBGC assumptions because of those differences? If so, why? Although PBGC is specifically requesting comments on the issues discussed earlier in this preamble, PBGC also invites comment on any other issue relating to section 4213 withdrawal liability assumptions.</P>
                <HD SOURCE="HD1">Applicability</HD>
                <P>The changes in this proposed rule would apply to the determination of withdrawal liability for employer withdrawals from multiemployer plans that occur on or after the effective date of the final rule. The proposed rule does not preclude the use of an interest rate assumption described in proposed § 4213.11(b) to determine unfunded vested benefits before the effective date of the final rule.</P>
                <HD SOURCE="HD1">Regulatory Impact Analysis</HD>
                <HD SOURCE="HD2">(1) Relevant Executive Orders for Regulatory Impact Analysis</HD>
                <P>Under Executive Order (E.O.) 12866, Office of Management and Budget (OMB) reviews any regulation determined to be a “significant regulatory action.” Section 3(f) of E.O. 12866 defines a “significant regulatory action” as an action that is likely to result in a rule that: (1) has an annual effect on the economy of $100 million or more, or adversely affects in a material way a sector of the economy, productivity, competition, jobs, the environment, public health or safety, or State, local, or tribal governments or communities (also referred to as economically significant); (2) creates serious inconsistency or otherwise interferes with an action taken or planned by another agency; (3) materially alters the budgetary impacts of entitlement grants, user fees, or loan programs, or the rights and obligations of recipients thereof; or (4) raises novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in the E.O.</P>
                <P>OMB has determined that this proposed rule is economically significant under section 3(f)(1) and has therefore reviewed this rule under E.O. 12866.</P>
                <P>E.O. 13563 supplements and reaffirms the principles, structures, and definitions governing contemporary regulatory review that were established in E.O. 12866, emphasizing the importance of quantifying both costs and benefits, reducing costs, harmonizing rules, and promoting flexibility. It directs agencies to assess the costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, and public health and safety effects, distributive impacts, and equity).</P>
                <P>PBGC has provided an assessment of the potential benefits, costs, and distributive impacts associated with this proposed rule.</P>
                <HD SOURCE="HD2">(2) Introduction and Need for Regulation</HD>
                <P>
                    Benefit levels in a multiemployer plan are typically set by trustees representing contributing employers and unions. As discussed earlier in this preamble, withdrawal liability generally represents an employer's share of the plan's unfunded vested benefits (UVBs) that 
                    <PRTPAGE P="62319"/>
                    the plan may have at the end of the plan year immediately preceding the plan year in which the employer withdraws. Withdrawal liability is the portion of the UVBs allocable to the withdrawing employer and represents a plan's only opportunity to require a withdrawing employer to pay its allocated share of the unfunded liabilities. When a plan does not collect an adequate amount of withdrawal liability from a withdrawing employer or collects an amount that is less than a withdrawing employer's allocated share of the plan's UVBs, that burden is shifted to the remaining contributing employers in the plan. There is a higher likelihood that the plan will not be able to pay full accrued benefits, and ultimately, there is an increased likelihood that it would not have resources to pay basic (PBGC-guaranteed) benefits. In that case, a plan may have to cut benefits to the PBGC guarantee level and apply to PBGC for financial assistance, which shifts costs to plan participants and to others in the multiemployer insurance system who fund PBGC via annual premiums.
                </P>
                <P>This proposed rule is needed to clarify that a plan actuary's use of 4044 rates represents a valid approach to selecting an interest rate assumption to determine withdrawal liability in all circumstances. The proposed rule would thereby reduce or eliminate the cost-shifting effects of impediments to actuaries' use of 4044 rates:</P>
                <P>• As noted earlier in the preamble discussion, several recent court decisions (and an unknown number of arbitration decisions) have required plans to re-assess withdrawal liability using interest assumptions based on anticipated investment returns rather than 4044 rates (or a blend using such rates), resulting in lower withdrawal liability assessments.</P>
                <P>• The delay, expense, and risk of adverse judgment involved with arbitration and litigation may provide an incentive for plans to settle withdrawal liability claims for less than the amount of withdrawal liability determined by the plan actuary, even in cases where the withdrawal liability dispute is not arbitrated or litigated.</P>
                <P>• Recent court decisions may deter actuaries from using 4044 rates (or a blend incorporating such rates) instead of interest rate assumptions based solely on anticipated plan investment returns.</P>
                <HD SOURCE="HD2">(3) Regulatory Action</HD>
                <P>Under this proposed rule, actuaries would be able to determine an employer's withdrawal liability on the basis of interest rate assumptions ranging from plan funding rates to 4044 rates, provided that the other assumptions and methods selected meet certain specified requirements.</P>
                <P>Because PBGC expects the proposed rule will reduce the litigation risk for plans associated with selection of the interest assumption, PBGC believes that more plans will use 4044 rates, which would tend to increase withdrawal liability and a plan's collection of withdrawal liability assessments. PBGC also believes that increasing plans' withdrawal liability income would have an overall positive effect on the multiemployer system and PBGC's multiemployer program. It is also consistent with PBGC's mission to enhance the retirement security of workers and retirees.</P>
                <HD SOURCE="HD2">(4) Estimated Impact of Regulatory Action</HD>
                <P>For the reasons discussed earlier, this proposed rule would tend to increase the amount of withdrawal liability that multiemployer plans assess and collect.</P>
                <P>The aggregate economic impact of this proposed rule is best measured by the amount of additional withdrawal liability that multiemployer plans are expected to receive from withdrawing employers. PBGC estimates that, in the 20 years following the final rule's effective date, there will be a nominal increase in cumulative withdrawal liability payments ranging between $804 million and $2.98 billion. A 20-year time horizon was chosen to show the impact on withdrawal liability payments which, depending on the circumstances of the withdrawal, can last as long as 20 years, and to capture the impact on plans receiving SFA (which must calculate withdrawal liability using 4044 rates for at least 10 years). However, because the assumptions underlying this analysis become more speculative as projections reach further into the future, PBGC cannot reasonably estimate the impact after 20 years. While PBGC expects that the proposed rule will deter employer withdrawals, it will do so only at the margin, and this impact is difficult to estimate. Accordingly, this analysis does not model any change to the rate of employer withdrawals or decrease in contributions due to improved plan funding attributable to these changes because doing so would be too speculative.</P>
                <P>
                    Currently, the aggregate amount of withdrawal liability paid into the multiemployer plan system each year (taking into account the result of any dispute resolution process) is approximately $1.3 billion, based on a PBGC analysis of attachments to 2018 and 2019 Form 5500 Schedules MB.
                    <SU>8</SU>
                    <FTREF/>
                     As discussed later in this Regulatory Impact Analysis, because the increase in withdrawal liability paid to a plan (and the mechanics of how such increase would come about) would depend on how it currently calculates withdrawal liability, PBGC makes assumptions in this analysis about how plans currently calculate withdrawal liability. For the purpose of this analysis, in the absence of reliable data, current withdrawal liability calculations are assumed as follows: (a) plans for which the Schedule MB was signed by an actuary from the firm associated with the largest number of plans use a blend of funding interest rates and 4044 rates and (b) for remaining plans, 80 percent use funding interest rates and 20 percent use 4044 rates. Further, to simplify the analysis, 4044 rates are assumed to be 3 percent, an approximation of current 4044 rates.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         The 2019 Form 5500 instructions provide that all employer and employee contributions for the plan year must be shown on line 3 of the Schedule MB. If any of the contributions reported include amounts owed for withdrawal liability, a list of withdrawal liability payments and the dates such amounts were contributed must be attached.
                    </P>
                </FTNT>
                <P>PBGC's measurement of the increase in annual withdrawal liability paid attributable to this proposed rule depends on two primary assumptions: (1) the number and size of plans that change withdrawal liability assumptions because of this rulemaking (switching assumption), and (2) the value of reductions in withdrawal liability either directly resulting from the order of an arbitrator or judge interpreting section 4213(a)(1) of ERISA or agreed to by plans in recognition of the risk of similar arbitration and litigation outcomes that would occur if this proposed rule is not finalized (dispute resolution assumption). Due to a lack of reliable data upon which to base these assumptions and because the effect of the proposed rule could vary widely because it allows for a range of approaches, this analysis shows impacts when these assumptions are set at three different levels.</P>
                <P>
                    Because the impact is expected to be substantially lower in the first 10 years after the effective date of the final rule than in the period thereafter, PBGC is separating the impact into two separate time periods: the first 10 years after the effective date of the final rule and the time period thereafter. The reasons for this are as follows: (1) after the final rule's effective date, the number of withdrawal liability payments that would be affected would start at zero and increase over time (before leveling off when substantially all withdrawal liability payments are for withdrawals 
                    <PRTPAGE P="62320"/>
                    occurring after the final rule's effective date) and (2) plans receiving SFA under section 4262 of ERISA are required to use 4044 rates for withdrawal liability calculations for at least the first 10 years after receiving SFA, and as a result, this rule would have no impact on withdrawal liability received by such plans in connection with approximately 10 years of withdrawals.
                </P>
                <P>Within each time period, three sets of assumptions are shown in three tables under the “Estimated Impact of Increase in Withdrawal Liability Received” heading with respect to the switching assumption and the dispute resolution assumption. Row (a), the switching assumption, represents the assumed percentage of plans for which the plan is assumed to change from using funding interest rate assumptions to 4044 rates as a result of this proposed rule. The percentages represent what PBGC believes to be a reasonable range of the percentage of plans assumed to be using funding interest rates for withdrawal liability purposes that would switch to 4044 rates. Row (b), the dispute resolution assumption, represents, for plans currently using 4044 rates or a blend using such rates, in the absence of this rule, the assumed reduction in withdrawal liability payments received by plans due to litigation outcomes, or similar reductions done voluntarily as a result of the threat of litigation. This reduction is measured as the percent reduction in the difference between the expected value of withdrawal liability payments calculated using 4044 rates and the expected value of withdrawal liability payments calculated using funding rates. In calculating the estimated annual increase in withdrawal liability payments, it is assumed that after the rule is effective, plans using 4044 rates or a blend using such rates will receive the expected value of withdrawal liability payments for a given assessment without a reduction due to settlements. The dispute resolution assumption assumes that no plans currently using 4044 rates would, in the absence of this proposed rule, switch from using 4044 rates to funding rates. Assuming that some plans would switch would increase the annual economic impact to some extent.</P>
                <P>The following tables summarize the estimated annual increases to withdrawal liability payments received by multiemployer pension plans and the present value of those increases at 3 percent and 7 percent discount rates:</P>
                <GPOTABLE COLS="4" OPTS="L2,p1,8/9,i1" CDEF="s100,12,12,12">
                    <TTITLE>Estimated Impact of Increase in Withdrawal Liability Received</TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW EXPSTB="03" RUL="s">
                        <ENT I="21">
                            <E T="02">Estimated Impact Years 1-10 ($ Millions)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">(a) % of Plans Switching to 4044 Rates</ENT>
                        <ENT>5%</ENT>
                        <ENT>10%</ENT>
                        <ENT>20%</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">(b) % of Dispute Resolutions for Plans Using 4044 Rates</ENT>
                        <ENT>2%</ENT>
                        <ENT>5%</ENT>
                        <ENT>10%</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="25">Year</ENT>
                        <ENT>Impact</ENT>
                        <ENT>Impact</ENT>
                        <ENT>Impact</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1</ENT>
                        <ENT>$22</ENT>
                        <ENT>$44</ENT>
                        <ENT>$89</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2</ENT>
                        <ENT>23</ENT>
                        <ENT>46</ENT>
                        <ENT>92</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3</ENT>
                        <ENT>25</ENT>
                        <ENT>48</ENT>
                        <ENT>96</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4</ENT>
                        <ENT>26</ENT>
                        <ENT>50</ENT>
                        <ENT>99</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">5</ENT>
                        <ENT>27</ENT>
                        <ENT>52</ENT>
                        <ENT>103</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">6</ENT>
                        <ENT>28</ENT>
                        <ENT>54</ENT>
                        <ENT>106</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7</ENT>
                        <ENT>29</ENT>
                        <ENT>55</ENT>
                        <ENT>109</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">8</ENT>
                        <ENT>30</ENT>
                        <ENT>57</ENT>
                        <ENT>113</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">9</ENT>
                        <ENT>31</ENT>
                        <ENT>59</ENT>
                        <ENT>117</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10</ENT>
                        <ENT>32</ENT>
                        <ENT>61</ENT>
                        <ENT>120</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PV of Impact in First 10 Years (3% Interest)</ENT>
                        <ENT>233</ENT>
                        <ENT>451</ENT>
                        <ENT>898</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">PV of Impact in First 10 Years (7% Interest)</ENT>
                        <ENT>193</ENT>
                        <ENT>374</ENT>
                        <ENT>746</ENT>
                    </ROW>
                    <ROW EXPSTB="03" RUL="s">
                        <ENT I="21">
                            <E T="02">Estimated Impact Years 11-20 ($ Millions)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">(a) % of Plans Switching to 4044 Rates</ENT>
                        <ENT>5%</ENT>
                        <ENT>10%</ENT>
                        <ENT>20%</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">(b) % of Dispute Resolutions for Plans Using 4044 Rates</ENT>
                        <ENT>2%</ENT>
                        <ENT>5%</ENT>
                        <ENT>10%</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="25">Year</ENT>
                        <ENT>Impact</ENT>
                        <ENT>Impact</ENT>
                        <ENT>Impact</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">11</ENT>
                        <ENT>$47</ENT>
                        <ENT>$89</ENT>
                        <ENT>$174</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12</ENT>
                        <ENT>48</ENT>
                        <ENT>91</ENT>
                        <ENT>178</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">13</ENT>
                        <ENT>49</ENT>
                        <ENT>93</ENT>
                        <ENT>183</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">14</ENT>
                        <ENT>51</ENT>
                        <ENT>96</ENT>
                        <ENT>187</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15</ENT>
                        <ENT>52</ENT>
                        <ENT>99</ENT>
                        <ENT>191</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">16</ENT>
                        <ENT>54</ENT>
                        <ENT>101</ENT>
                        <ENT>195</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">17</ENT>
                        <ENT>56</ENT>
                        <ENT>104</ENT>
                        <ENT>200</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">18</ENT>
                        <ENT>57</ENT>
                        <ENT>107</ENT>
                        <ENT>205</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">19</ENT>
                        <ENT>59</ENT>
                        <ENT>109</ENT>
                        <ENT>209</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20</ENT>
                        <ENT>60</ENT>
                        <ENT>112</ENT>
                        <ENT>214</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PV of Impact in Years 11-20 (3% Interest)</ENT>
                        <ENT>340</ENT>
                        <ENT>640</ENT>
                        <ENT>1,240</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">PV of Impact in Years 11-20 (7% Interest)</ENT>
                        <ENT>193</ENT>
                        <ENT>364</ENT>
                        <ENT>706</ENT>
                    </ROW>
                    <ROW EXPSTB="03" RUL="s">
                        <ENT I="21">
                            <E T="02">Estimated Present Value Impact Years 1-20 ($ Millions)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">(a) % of Plans Switching to 4044 Rates</ENT>
                        <ENT>5%</ENT>
                        <ENT>10%</ENT>
                        <ENT>20%</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">(b) % of Dispute Resolutions for Plans Using 4044 Rates</ENT>
                        <ENT>2%</ENT>
                        <ENT>5%</ENT>
                        <ENT>10%</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Nominal Value of Impact in Years 1-20</ENT>
                        <ENT>$804</ENT>
                        <ENT>$1,526</ENT>
                        <ENT>$2,981</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PV of Impact in Years 1-20 (3% Interest)</ENT>
                        <ENT>$573</ENT>
                        <ENT>$1,091</ENT>
                        <ENT>$2,138</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PV of Impact in Years 1-20 (7% Interest)</ENT>
                        <ENT>$386</ENT>
                        <ENT>$738</ENT>
                        <ENT>$1,452</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="62321"/>
                <P>Separate from the distributive impacts, because this rule would provide increased certainty in withdrawal liability determinations, plans and withdrawing employers would see substantial cost savings in the form of reduced arbitration and litigation costs.</P>
                <P>The major expenses associated with a withdrawal liability dispute are attorney fees, arbitration fees (including fees to initiate arbitration and fees charged by an arbitrator), and fees charged by expert witnesses. Though costs will vary greatly from plan to plan based on the plan's benefit formula, size of the plan, attorney and expert witness rates, and other factors, PBGC estimates that a withdrawal liability arbitration, measuring from a request for plan sponsor review of a withdrawal liability determination through the end of arbitration would range from $82,500 to $222,000. For lengthy litigation, costs can be over $1 million. Assuming some arbitrations and litigation would be avoided entirely, and others would be less complex because they would not include disputes over interest assumptions, PBGC estimates that this proposed rule would result in an annual savings of $500,000 to $1 million, split evenly between plans and employers.</P>
                <HD SOURCE="HD2">(5) Regulatory Alternatives Considered</HD>
                <P>PBGC considered a number of alternatives before deciding to issue this proposed rule. None of the alternatives were as cost-effective as the proposed rule.</P>
                <P>One alternative PBGC considered is to not regulate under section 4213 of ERISA. Without a regulation, PBGC would expect a continuation of the recent trend in withdrawal liability dispute resolution toward requiring that withdrawal liability be based on funding rates (or rates closer to funding rates than to 4044 rates). PBGC believes that the adverse effect of employer withdrawals generally contributes to financial stress for plans (and their remaining employers and participants) that the use of 4044 rates in determining withdrawal liability would help alleviate. Inaction would constitute choice of the status quo, which could contribute to plan underfunding, benefit losses for participants, cost-shifting to remaining employers, and higher claims on PBGC's insurance system.</P>
                <P>PBGC also considered issuing a proposed rule that would only authorize use of 4044 rates, without addressing the popular practice of using 4044 rates for benefits expected to be covered by existing assets and funding rates for other benefits. This limited approach would address the issue of comparatively low withdrawal liability assessments for plans that choose to use 4044 rates but by not providing flexibility for other plans, it would limit the effectiveness of the regulation.</P>
                <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
                <P>
                    The Regulatory Flexibility Act 
                    <SU>9</SU>
                    <FTREF/>
                     imposes certain requirements respecting rules that are subject to the notice-and-comment requirements of section 553(b) of the Administrative Procedure Act, or any other law,
                    <SU>10</SU>
                    <FTREF/>
                     and that are likely to have a significant economic impact on a substantial number of small entities. Unless an agency certifies that a proposed rule will not, if promulgated, have a significant economic impact on a substantial number of small entities, section 603 of the Regulatory Flexibility Act requires that the agency present an initial regulatory flexibility analysis at the time of the publication of the proposed rule describing the impact of the rule on small entities and seek public comment on such impact. Small entities include small businesses, organizations, and governmental jurisdictions.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         5 U.S.C. 601 
                        <E T="03">et seq.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         The applicable definition of “rule” is found in section 601 of the Regulatory Flexibility Act. 
                        <E T="03">See</E>
                         5 U.S.C. 601(2).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         The applicable definitions of “small business,” “small organization,” and “small governmental jurisdiction” are found in section 601 of the Regulatory Flexibility Act. 
                        <E T="03">See</E>
                         5 U.S.C. 601.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Small Entities</HD>
                <P>
                    This proposed rule would directly regulate plans by prescribing interest assumptions for their use in calculating withdrawal liability. For purposes of the Regulatory Flexibility Act requirements with respect to this proposed rule, PBGC considers a small entity to be a plan with fewer than 100 participants.
                    <SU>12</SU>
                    <FTREF/>
                     This is substantially the same criterion PBGC uses in other regulations 
                    <SU>13</SU>
                    <FTREF/>
                     and is consistent with certain requirements in title I of ERISA 
                    <SU>14</SU>
                    <FTREF/>
                     and the Code,
                    <SU>15</SU>
                    <FTREF/>
                     as well as the definition of a small entity that PBGC and DOL have used for purposes of the Regulatory Flexibility Act.
                    <SU>16</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         PBGC consulted with the Small Business Administration's Office of Advocacy before making this determination. Memorandum received from the U.S. Small Business Administration, Office of Advocacy on March 9, 2021.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See, e.g.,</E>
                         special rules for small plans under part 4007 (Payment of Premiums).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See, e.g.,</E>
                         section 104(a)(2) of ERISA, which permits the Secretary of Labor to prescribe simplified annual reports for pension plans that cover fewer than 100 participants.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See, e.g.,</E>
                         section 430(g)(2)(B) of the Code, which permits plans with 100 or fewer participants to use valuation dates other than the first day of the plan year.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See, e.g.,</E>
                         PBGC's proposed rule on Reportable Events and Certain Other Notification Requirements, 78 FR 20039, 20057 (April 3, 2013) and DOL's final rule on Prohibited Transaction Exemption Procedures, 76 FR 66637, 66644 (Oct. 27, 2011).
                    </P>
                </FTNT>
                <P>
                    Thus, PBGC believes that assessing the impact of the proposed rule on small plans is an appropriate substitute for evaluating the effect on small entities. The definition of small entity considered appropriate for this purpose differs, however, from a definition of small business based on size standards promulgated by the Small Business Administration 
                    <SU>17</SU>
                    <FTREF/>
                     under the Small Business Act. PBGC therefore requests comments on the appropriateness of the size standard used in evaluating the impact of its proposed rule on small entities.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See,</E>
                         13 CFR 121.201.
                    </P>
                </FTNT>
                <P>
                    Based on its definition of small entity, PBGC certifies under section 605(b) of the Regulatory Flexibility Act (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ) that the amendments in this proposed rule will not, if promulgated, have a significant economic impact on a substantial number of small entities. Based on data for recent premium filings, PBGC estimates that only 38 of the approximately 1,360 plans covered by PBGC's multiemployer program are small plans. Plans would be able, but not required, to set assumptions to determine withdrawal liability under this proposed rule. As discussed in the Regulatory Impact Analysis, because this proposed rule would authorize a wide range of commonly used interest assumptions, few plans would switch assumptions. In that analysis, PBGC estimated that, for plans currently using funding assumptions (which are assumed to be less than 80 percent of all plans), from 5 to 20 percent would switch to 4044 rates. Consequently, of the 38 small multiemployer plans, PBGC estimates that no more than 6 would switch assumptions.
                </P>
                <P>
                    For a plan that does move to 4044 rates as permitted under the proposed rule, this proposed rule would tend to have a positive economic impact because it would increase the amount of withdrawal liability collected, which could improve the plan's ability to remain solvent and to continue paying participants' benefits. For the few small plans expected to switch assumptions, PBGC estimates that, in the 20 years following the final rule's effective date, the nominal increase in cumulative withdrawal liability payments would not exceed $1 million. It could also deter employer withdrawals, however, as discussed in the Regulatory Impact Analysis, it will do so only at the margin, and this impact is difficult to estimate. There would be a higher 
                    <PRTPAGE P="62322"/>
                    likelihood that plans that do not use 4044 rates provided by this proposed rule would eventually be unable to pay full benefits at current accrual rates. Plans would also see administrative savings in the form of reduced arbitration and litigation costs because some arbitrations and litigation would be avoided entirely, and others would be less complex because they would not include disputes over interest assumptions. As discussed in the Regulatory Impact Analysis, these savings could be as much as $82,500 to $222,000 for reduced arbitration costs and $1 million in reduced litigation costs for a plan when an arbitration or litigation is avoided. This proposed rule would not have negative impacts or costs on small plans because plans could choose whether to use interest assumptions prescribed by the regulation. PBGC expects the administrative costs, if any, associated with the proposed rule would be de minimis. Accordingly, as provided in section 605 of the Regulatory Flexibility Act (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ), sections 603 and 604 do not apply.
                </P>
                <P>Though this proposed rule would directly regulate plans, as discussed in the Regulatory Impact Analysis, it would indirectly impact employers, including small employers. This is because, for plans that switch assumptions, it would tend to increase the amount of withdrawal liability assessed by plans and withdrawing employers would pay the increases if they were to withdraw. The statutory process for allocating unfunded vested benefits to a withdrawing employer takes into account the employer's contribution history; employers with a history of higher contributions are allocated a larger share of UVBs while employers with a history of lower contributions are allocated a smaller share. Because small employers have small contribution levels, they would see smaller dollar increases in withdrawal liability than employers with large contribution levels. In addition, as discussed, if plans adopt the prescribed assumptions, employers in those plans may be less likely to withdraw. This effect, in combination with the higher withdrawal liability payments for employers who do withdraw, could contribute to the long-term solvency of multiemployer plans. Extended plan solvency would help ensure that participants and beneficiaries would receive promised benefits, which would enhance their income security and benefit the communities, including small businesses within those communities, in which they live.</P>
                <P>PBGC considered declining to prescribe assumptions under section 4213, an alternative that would have less impact on small employers, but as discussed in the Regulatory Impact Analysis, doing so would contribute to plan underfunding. PBGC also considered issuing a proposed rule that would only authorize the use of 4044 rates, an alternative that would have resulted in higher withdrawal liability under section 4213(a)(2) of ERISA in comparison to the proposed rule, and thereby a larger impact on small employers who participate in plans that adopt that approach (but would likely have a smaller adoption rate than the section 4213(a)(2) assumptions in the proposed rule).</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 29 CFR 4213</HD>
                    <P>Employee benefit plans, Pension insurance, Pensions.</P>
                </LSTSUB>
                <AMDPAR>For the reasons set forth in the preamble, PBGC proposes to amend 29 CFR chapter XL by adding part 4213 to read as follows:</AMDPAR>
                <PART>
                    <HD SOURCE="HED">PART 4213—ACTUARIAL ASSUMPTIONS</HD>
                    <CONTENTS>
                        <SECHD>Sec.</SECHD>
                        <SECTNO>4213.1</SECTNO>
                        <SUBJECT>Purpose and organization.</SUBJECT>
                        <SECTNO>4213.2</SECTNO>
                        <SUBJECT>Definitions.</SUBJECT>
                        <SECTNO>4213.11</SECTNO>
                        <SUBJECT>Section 4213(a)(2) assumptions.</SUBJECT>
                    </CONTENTS>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>29 U.S.C. 1302(b)(3), 1393.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 4213.1</SECTNO>
                        <SUBJECT>Purpose and organization.</SUBJECT>
                        <P>This part sets forth actuarial assumptions and methods under section 4213(a)(2) of ERISA as an alternative to the assumptions and methods under section 4213(a)(1) of ERISA for determining withdrawal liability.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 4213.2</SECTNO>
                        <SUBJECT>Definitions.</SUBJECT>
                        <P>For the purposes of this part:</P>
                        <P>
                            <E T="03">Single effective interest rate</E>
                             means for a given interest assumption, the single rate of interest which, if used to determine the present value of the plan's liabilities, would result in an amount equal to the present value of the plan's liabilities determined using the given assumption, holding all other assumptions and methods constant.
                        </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 4213.11</SECTNO>
                        <SUBJECT>Section 4213(a)(2) assumptions.</SUBJECT>
                        <P>(a) In general. Withdrawal liability may be determined using actuarial assumptions and methods that satisfy the requirements of this section. Such actuarial assumptions and methods need not satisfy any other requirement under title IV of ERISA.</P>
                        <P>(b) Interest assumption (1) General rule. To satisfy the requirements of this section, the single effective interest rate for the interest assumption used to determine the present value of the plan's liabilities must be the rate in paragraph (b)(2) of this section, the rate in paragraph (b)(3) of this section, or a rate between those two rates.</P>
                        <P>(2) The rate in this paragraph (b)(2) is the single effective interest rate for the interest assumption prescribed in § 4044.52 of this chapter for the date as of which withdrawal liability is determined.</P>
                        <P>(3) The rate in this paragraph (b)(3) is the single effective interest rate for the interest assumption under section 304(b)(6) of ERISA for the plan year within which the date in paragraph (b)(2) of this section falls.</P>
                        <P>(c) Other assumptions. The assumptions and methods (other than the interest assumption) satisfy the requirements of this section if—</P>
                        <P>(1) Each is reasonable (taking into account the experience of the plan and reasonable expectations), and</P>
                        <P>(2) In combination, they offer the actuary's best estimate of anticipated experience under the plan.</P>
                    </SECTION>
                    <SIG>
                        <P>Signed in Washington, DC.</P>
                        <NAME>Gordon Hartogensis,</NAME>
                        <TITLE>Director, Pension Benefit Guaranty Corporation.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22304 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7709-02-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <CFR>40 CFR Parts 51 and 52</CFR>
                <DEPDOC>[EPA-HQ-OAR-2004-0014; FRL-4940.2-03-OAR]</DEPDOC>
                <RIN>RIN 2060-AQ47</RIN>
                <SUBJECT>Prevention of Significant Deterioration (PSD) and Nonattainment New Source Review (NNSR): Reconsideration of Fugitive Emissions Rule</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Environmental Protection Agency (EPA) is proposing to repeal regulatory amendments promulgated through a final rule adopted in 2008 under the Clean Air Act (CAA or Act) that addressed the consideration of “fugitive” emissions of air pollutants from stationary sources when determining the applicability of certain permitting requirements under the Act. Those amendments have been stayed as a result of the reconsideration process. To bring closure to the reconsideration proceeding, the EPA is proposing to fully repeal the 2008 rule by removing 
                        <PRTPAGE P="62323"/>
                        the stayed provisions of the regulatory amendments adopted in 2008. The EPA is also proposing to remove a related exemption for modifications that would be considered major solely due to the inclusion of fugitive emissions. As a result of the proposed changes, all existing major stationary sources would be required to include fugitive emissions in determining whether a physical or operational change constitutes a “major modification,” requiring a permit under the Prevention of Significant Deterioration (PSD) or Nonattainment New Source Review (NNSR) programs.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P/>
                    <P>
                        <E T="03">Comments:</E>
                         Comments must be received on or before December 13, 2022.
                    </P>
                    <P>
                        <E T="03">Public hearing:</E>
                         If anyone contacts EPA requesting a public hearing by October 19, 2022, the EPA will hold a virtual public hearing. See 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         for information on requesting and registering for a public hearing.
                    </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        <E T="03">Comments:</E>
                         You may send comments, identified by Docket ID No. EPA-HQ-OAR-2004-0014, by any of the following methods:
                    </P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: https://www.regulations.gov/</E>
                         (our preferred method). Follow the online instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Email: a-and-r-docket@epa.gov.</E>
                         Include Docket ID No. EPA-HQ-OAR-2004-0014 in the subject line of the message.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (202) 566-9744. Attention Docket ID No. EPA-HQ-OAR-2004-0014.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the Docket ID No. EPA-HQ-OAR-2004-0014 for this rulemaking. Comments received may be posted without change to 
                        <E T="03">https://www.regulations.gov/,</E>
                         including any personal information provided. For detailed instructions on sending comments and additional information on the rulemaking process, see the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this document. For further information on EPA Docket Center services and the current status, please visit us online at 
                        <E T="03">https://www.epa.gov/dockets.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For information about this proposed rule, contact Mr. Matthew Spangler, Air Quality Policy Division, Office of Air Quality Planning and Standards (C504-05), Environmental Protection Agency, Research Triangle Park, NC; telephone number: (919) 541-0327; email address: 
                        <E T="03">spangler.matthew@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The information presented in this document is organized as follows:</P>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. General Information</FP>
                    <FP SOURCE="FP1-2">A. Entities Potentially Affected by This Action</FP>
                    <FP SOURCE="FP1-2">B. Obtaining a Copy of This Document and Other Related Information</FP>
                    <FP SOURCE="FP1-2">C. Preparing Comments for the EPA</FP>
                    <FP SOURCE="FP1-2">D. Participation in Virtual Public Hearing</FP>
                    <FP SOURCE="FP-2">II. Background</FP>
                    <FP SOURCE="FP1-2">A. New Source Review Program</FP>
                    <FP SOURCE="FP1-2">B. Applicability of the Major NSR Program</FP>
                    <FP SOURCE="FP1-2">C. Treatment of “Fugitive Emissions” in the Major NSR Program</FP>
                    <FP SOURCE="FP1-2">D. Fugitive Emissions in Major Modification Determinations</FP>
                    <FP SOURCE="FP1-2">E. Petition for Reconsideration and Administrative Stays of the Fugitive Emissions Rule</FP>
                    <FP SOURCE="FP-2">III. Proposed Action</FP>
                    <FP SOURCE="FP1-2">A. Results of the EPA's Reconsideration</FP>
                    <FP SOURCE="FP1-2">B. Proposed Revisions to Regulations</FP>
                    <FP SOURCE="FP-2">IV. Interpretation of CAA Sections 302(j) and 111(a)(4)</FP>
                    <FP SOURCE="FP1-2">A. Previous EPA Interpretations</FP>
                    <FP SOURCE="FP1-2">B. NRDC's Petition for Reconsideration</FP>
                    <FP SOURCE="FP1-2">C. Proposed Interpretation of CAA Sections 302(j) and 111(a)(4)</FP>
                    <FP SOURCE="FP-2">V. Policy Considerations and Impact on Regulated Entities</FP>
                    <FP SOURCE="FP1-2">A. Purposes of NSR</FP>
                    <FP SOURCE="FP1-2">B. Increasing Clarity</FP>
                    <FP SOURCE="FP1-2">C. Previous Policy Considerations</FP>
                    <FP SOURCE="FP1-2">D. Impacts on Regulated Entities</FP>
                    <FP SOURCE="FP-2">VI. SIP Minimum Program Elements</FP>
                    <FP SOURCE="FP-2">VII. Definition of “Fugitive Emissions”</FP>
                    <FP SOURCE="FP-2">VIII. Environmental Justice Considerations</FP>
                    <FP SOURCE="FP-2">IX. Statutory and Executive Order Reviews</FP>
                    <FP SOURCE="FP1-2">A. Executive Order 12866: Regulatory Planning and Review and Executive Order 13563: Improving Regulation and Regulatory Review</FP>
                    <FP SOURCE="FP1-2">B. Paperwork Reduction Act (PRA)</FP>
                    <FP SOURCE="FP1-2">C. Regulatory Flexibility Act (RFA)</FP>
                    <FP SOURCE="FP1-2">D. Unfunded Mandates Reform Act (UMRA)</FP>
                    <FP SOURCE="FP1-2">E. Executive Order 13132: Federalism</FP>
                    <FP SOURCE="FP1-2">F. Executive Order 13175: Consultation and Coordination With Indian Tribal Governments</FP>
                    <FP SOURCE="FP1-2">G. Executive Order 13045: Protection of Children From Environmental Health and Safety Risks</FP>
                    <FP SOURCE="FP1-2">H. Executive Order 13211: Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use</FP>
                    <FP SOURCE="FP1-2">I. National Technology Transfer and Advancement Act (NTTA)</FP>
                    <FP SOURCE="FP1-2">J. Executive Order 12898: Federal Actions To Address Environmental Justice in Minority Populations and Low-Income Populations</FP>
                    <FP SOURCE="FP-2">X. Statutory Authority</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. General Information</HD>
                <HD SOURCE="HD2">A. Entities Potentially Affected by This Action</HD>
                <P>Entities potentially affected by this action include sources that do not belong to a source category listed in 40 Code of Federal Regulations (CFR) 52.21(b)(1)(iii) (and other identical provisions in other sections of the CFR). Entities potentially affected by this proposed action also include state and local air pollution control agencies responsible for permitting sources pursuant to the New Source Review (NSR) program.</P>
                <HD SOURCE="HD2">B. Obtaining a Copy of This Document and Other Related Information</HD>
                <P>
                    The EPA has established a docket for this rulemaking under Docket ID No. EPA-HQ-OAR-2004-0014. All documents in the dockets are listed in 
                    <E T="03">https://www.regulations.gov/.</E>
                     Although listed, some information is not publicly available, 
                    <E T="03">e.g.,</E>
                     Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, is not placed on the internet and will be publicly available only in hard copy. Publicly available docket materials are available either in the docket for this action, Docket ID No. EPA-HQ-OAR-2004-0014, or electronically at 
                    <E T="03">https://www.regulations.gov/.</E>
                </P>
                <P>
                    In addition to being available in the docket, an electronic copy of this 
                    <E T="04">Federal Register</E>
                     document will be posted at 
                    <E T="03">https://www.epa.gov/nsr.</E>
                </P>
                <HD SOURCE="HD2">C. Preparing Comments for the EPA</HD>
                <P>
                    <E T="03">Instructions.</E>
                     Submit your comments, identified by Docket ID No. EPA-HQ-OAR-2004-0014, at 
                    <E T="03">https://www.regulations.gov</E>
                     (our preferred method), or the other methods identified in the 
                    <E T="02">ADDRESSES</E>
                     section. Once submitted, comments cannot be edited or removed from the docket. The EPA may publish any comment received to its public docket. Do not submit to EPA's docket at 
                    <E T="03">https://www.regulations.gov</E>
                     any information you consider to be CBI or other information whose disclosure is restricted by statute. This type of information should be submitted by mail as discussed below.
                </P>
                <P>
                    Multimedia submissions (audio, video, etc.) must be accompanied by a written comment. The written comment is considered the official comment and should include discussion of all points you wish to make. The EPA will generally not consider comments or comment contents located outside of the primary submission (
                    <E T="03">i.e.,</E>
                     on the web, cloud, or other file sharing system). For additional submission methods, the full EPA public comment policy, information about CBI or multimedia submissions, and general guidance on making effective comments, please visit 
                    <E T="03">https://www.epa.gov/dockets/commenting-epa-dockets.</E>
                     For further information and updates on EPA Docket 
                    <PRTPAGE P="62324"/>
                    Center services, please visit us online at 
                    <E T="03">https://www.epa.gov/dockets.</E>
                </P>
                <P>
                    <E T="03">Submitting CBI.</E>
                     Do not submit information containing CBI to the EPA through 
                    <E T="03">https://www.regulations.gov/</E>
                     or email. Clearly mark the part or all the information that you claim to be CBI. For CBI information on any digital storage media that you mail to the EPA, mark the outside of the digital storage media as CBI and then identify electronically within the digital storage media the specific information that is claimed as CBI. In addition to one complete version of the comments that includes information claimed as CBI, you must submit a copy of the comments that does not contain the information claimed as CBI directly to the public docket through the procedures outlined in 
                    <E T="03">Instructions</E>
                     above. If you submit any digital storage media that does not contain CBI, mark the outside of the digital storage media clearly that it does not contain CBI. Information not marked as CBI will be included in the public docket and the EPA's electronic public docket without prior notice. Information marked as CBI will not be disclosed except in accordance with procedures set forth in 40 CFR part 2. Send or deliver information identified as CBI only to the following address: OAQPS Document Control Officer (C404-02), OAQPS, U.S. Environmental Protection Agency, Research Triangle Park, North Carolina 27711, Attention Docket ID No. EPA-HQ-OAR-2004-0014. Note that written comments containing CBI and submitted by mail may be delayed and no hand deliveries will be accepted.
                </P>
                <HD SOURCE="HD2">D. Participation in Virtual Public Hearing</HD>
                <P>
                    To request a virtual public hearing, contact Ms. Pamela Long at (919) 541-0641 or by email at 
                    <E T="03">long.pam@epa.gov.</E>
                     If requested, the virtual hearing will be held on October 31, 2022. The hearing will convene at 9:00 a.m. Eastern Time (ET) and will conclude at 3:00 p.m. ET. The EPA may close a session 15 minutes after the last pre-registered speaker has testified if there are no additional speakers. The EPA will announce further details at 
                    <E T="03">https://www.epa.gov/nsr.</E>
                </P>
                <P>
                    Upon publication of this document in the 
                    <E T="04">Federal Register</E>
                    , the EPA will begin pre-registering speakers for the hearing, if a hearing is requested. To register to speak at the virtual hearing, please use the online registration form available at 
                    <E T="03">https://www.epa.gov/nsr</E>
                     or contact Ms. Pamela Long at (919) 541-0641 or by email at 
                    <E T="03">long.pam@epa.gov.</E>
                     The last day to pre-register to speak at the hearing will be October 26, 2022. Prior to the hearing, the EPA will post a general agenda that will list pre-registered speakers in approximate order at: 
                    <E T="03">https://www.epa.gov/nsr.</E>
                </P>
                <P>The EPA will make every effort to follow the schedule as closely as possible on the day of the hearing; however, please plan for the hearings to run either ahead of schedule or behind schedule.</P>
                <P>
                    Each commenter will have 3 minutes to provide oral testimony. The EPA encourages commenters to provide the EPA with a copy of their oral testimony electronically (via email) by emailing it to 
                    <E T="03">long.pam@epa.gov.</E>
                     The EPA also recommends submitting the text of your oral testimony as written comments to the rulemaking docket.
                </P>
                <P>The EPA may ask clarifying questions during the oral presentations but will not respond to the presentations at that time. Written statements and supporting information submitted during the comment period will be considered with the same weight as oral testimony and supporting information presented at the public hearing.</P>
                <P>
                    Please note that any updates made to any aspect of the hearing will be posted online at 
                    <E T="03">https://www.epa.gov/nsr.</E>
                     While the EPA expects the hearing to go forward as set forth above, please monitor our website or contact Ms. Pamela Long at (919) 541-0641 or by email at 
                    <E T="03">long.pam@epa.gov</E>
                     to determine if there are any updates. The EPA does not intend to publish a document in the 
                    <E T="04">Federal Register</E>
                     announcing updates.
                </P>
                <P>If you require the services of a translator or special accommodations such as audio description, please pre-register for the hearing with Ms. Pamela Long and describe your needs by October 21, 2022. The EPA may not be able to arrange accommodations without advanced notice.</P>
                <HD SOURCE="HD1">II. Background</HD>
                <HD SOURCE="HD2">A. New Source Review Program</HD>
                <P>
                    The NSR program was designed to protect public health and welfare from the effects of air pollution and to preserve and/or improve air quality throughout the nation. 
                    <E T="03">See</E>
                     42 U.S.C. 7470(1), (2), (4). The NSR program requires certain stationary sources of air pollution to obtain air pollution permits prior to beginning construction. Construction of new sources with emissions above statutory thresholds, and modifications of existing sources emitting above those thresholds, that increase emissions of “regulated NSR pollutants” by more than amounts specified in the EPA's NSR regulations are subject to “major source” NSR requirements. New construction or modifications of smaller emitting sources and modifications of existing major sources that do not increase emissions by more than the thresholds in the major NSR regulations may be subject to minor NSR requirements or excluded from NSR altogether.
                </P>
                <P>The major source NSR program includes two distinct programs that each have unique requirements for new or modified sources. The applicability of these two programs depends on whether the area where the source is located is exceeding the National Ambient Air Quality Standards (NAAQS). The PSD program, based on requirements in Part C of title I of the CAA, applies to pollutants for which the area is not exceeding the NAAQS (areas designated as attainment or unclassifiable) and to regulated NSR pollutants for which there are no NAAQS. The NNSR program, based on Part D of title I of the CAA, applies to pollutants for which the area is not meeting the NAAQS (areas designated as nonattainment).</P>
                <P>To implement the requirements of the CAA for these programs, most states have EPA-approved State Implementation Plans (SIPs) containing PSD and NNSR preconstruction permitting programs that meet the minimum requirements reflected in the EPA's major NSR program regulations at 40 CFR 51.166 and 51.165. Upon EPA approval of a SIP, the state or local air agency becomes the permitting authority for major NSR permits for sources within its boundaries and issues permits under state law. Currently, state and local air agencies issue the vast majority of major NSR permits each year. When a state or local air agency does not have an approved NSR program, federal regulations apply and either the EPA issues the major NSR permits or a state or local air agency issues the major NSR permits on behalf of the EPA by way of a delegation agreement. For sources located in Indian Country, 18 U.S.C. 1151, the EPA is the permitting authority for major NSR.</P>
                <P>
                    The permitting program for construction of new non-major sources and minor modifications to major sources is known as the minor NSR program. CAA section 110(a)(2)(C) requires states to develop a program to regulate the construction and modification of any stationary source “as necessary to assure that [NAAQS] are achieved.” 42 U.S.C. 7410(a)(2)(C). The CAA and the EPA's regulations are less prescriptive regarding minimum requirements for minor NSR, so air agencies generally have more flexibility in designing minor NSR programs in their EPA-approved SIPs. Minor NSR 
                    <PRTPAGE P="62325"/>
                    permits are almost exclusively issued by state and local air agencies, although the EPA issues minor NSR permits in many areas of Indian Country.
                </P>
                <P>The applicability of the PSD, NNSR, and/or minor NSR programs to a stationary source must be determined in advance of construction and is a pollutant-specific determination. Thus, a stationary source may be subject to the PSD program for certain pollutants, NNSR for some pollutants, and minor NSR for others.</P>
                <HD SOURCE="HD2">B. Applicability of the Major NSR Program</HD>
                <P>
                    Major NSR applies to (1) construction of new major sources and (2) major modifications of existing major sources. In either case, the initial step in assessing applicability is to determine whether the new or modified source in question qualifies as a “major stationary source.” A new or existing source qualifies as a major stationary source if it “emits or has the potential to emit” a regulated NSR pollutant in an amount greater than the specified annual thresholds. For the PSD program, the major source threshold is 100 tons per year (tpy) for sources in certain source categories listed in the regulations, and 250 tpy for any other type of source. 
                    <E T="03">See</E>
                     40 CFR 51.166(b)(1)(i)(
                    <E T="03">a</E>
                    ) and 52.21(b)(1)(i)(
                    <E T="03">a</E>
                    ). The major source threshold for NNSR is generally 100 tpy for all source categories but is lower for some pollutants in nonattainment areas classified as Serious, Severe, or Extreme. 
                    <E T="03">See</E>
                     40 CFR 51.165(a)(1)(iv).
                </P>
                <P>
                    If a proposed 
                    <E T="03">new</E>
                     source's actual or potential emissions of a regulated NSR pollutant 
                    <SU>1</SU>
                    <FTREF/>
                     are at or above the applicable major source threshold, it is subject to preconstruction review under major NSR for that pollutant.
                    <SU>2</SU>
                    <FTREF/>
                     Furthermore, under PSD, the proposed new source would also be subject to major NSR review for any other regulated NSR pollutant that it emits at or above the pollutant's “significant” emissions rate as defined in 40 CFR 51.166(b)(23) and 52.21(b)(23).
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         40 CFR 52.21(b)(50) defines the term “regulated NSR pollutant” for purposes of PSD. The term generally includes pollutants for which a NAAQS has been promulgated and other pollutants subject to regulation under the CAA. This “regulated NSR pollutant” definition, however, excludes the Hazardous Air Pollutants regulated under section 112 of the CAA. For purposes of NNSR, “regulated NSR pollutant” is defined at 40 CFR 51.165(a)(1)(xxxvii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Physical changes at an existing non-major source can also establish a “major stationary source” if the physical change by itself would exceed the applicable major stationary source threshold. 
                        <E T="03">E.g.,</E>
                         40 CFR 52.21(b)(1)(i)(
                        <E T="03">c</E>
                        ).
                    </P>
                </FTNT>
                <P>
                    An 
                    <E T="03">existing</E>
                     major stationary source can be subject to major NSR when a proposed physical change or a change in the method of operation qualifies as a “major modification.” 
                    <SU>3</SU>
                    <FTREF/>
                     A major modification occurs when a physical or operational change (
                    <E T="03">i.e.,</E>
                     a construction project) would result in (1) a significant emissions increase of a regulated NSR pollutant, considering emissions increases and decreases from the project alone, and (2) a significant net emissions increase of a regulated NSR pollutant, considering the project as well as other contemporaneous emissions increases and decreases at the source. 
                    <E T="03">See, e.g.,</E>
                     40 CFR 52.21(b)(2)(i) and (b)(52). As noted in the previous paragraph, the NSR regulations define the annual emissions rate considered “significant” for each regulated NSR pollutant. 
                    <E T="03">See</E>
                     40 CFR 51.165(a)(1)(x), 51.166(b)(23), and 52.21(b)(23). In determining the increase in emissions from a physical or operational change, new emissions units are evaluated at their potential emissions, while existing and replacement units are generally evaluated by comparing their baseline actual emissions before the physical or operational change to their projected actual emissions after the change. 
                    <E T="03">See, e.g.,</E>
                     40 CFR 52.21(a)(2)(iv)(
                    <E T="03">c-f</E>
                    ), (b)(7), and (b)(33).
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Notably, modifications to existing non-major sources cannot be considered major modifications. However, as described in footnote 2, a physical change at an existing minor source that itself exceeds the major source thresholds would establish a major stationary source.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Treatment of “Fugitive Emissions” in the Major NSR Program</HD>
                <P>
                    For purposes of major NSR, “fugitive emissions” are defined as “emissions which could not reasonably pass through a stack, chimney, vent, or other functionally equivalent opening.” 
                    <E T="03">E.g.,</E>
                     40 CFR 52.21(b)(20). Examples of fugitive emissions include windblown dust from surface mines and volatile organic compounds (VOCs) emitted from leaking pipes and fittings at petroleum refineries. Section VII of this preamble further discusses the definition of “fugitive emissions.”
                </P>
                <P>For certain types of sources, fugitive emissions are treated differently from non-fugitive emissions in determining whether major NSR applies to a source. Fugitive emissions may be relevant to determining whether a source triggers major NSR in two distinct contexts.</P>
                <P>
                    First, for purposes of determining whether a new or existing source is a “major stationary source,” 
                    <SU>4</SU>
                    <FTREF/>
                     quantifiable fugitive emissions are included in calculating a source's emissions only if the source belongs to one of the source categories specifically listed in the major NSR regulations. 
                    <E T="03">See, e.g.,</E>
                     40 CFR 52.21(b)(1)(iii).
                    <SU>5</SU>
                    <FTREF/>
                     Thus, fugitive emissions from sources not belonging to a listed category are generally not included in determining whether a source is a major stationary source. The treatment of fugitive emissions in determining whether a new or existing source is a major source is well-established and is not impacted by this proposed action.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The relevant statutory provisions use the terms “major stationary source” and “major emitting facility” interchangeably. 
                        <E T="03">See</E>
                         42 U.S.C. 7479(1), 7602(j). The EPA uses the shorthand phrase “major source” to refer to this concept, and any reference to a “major source” in this preamble refers to the concept of “major stationary source” under NSR.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         A single stationary source may be comprised of multiple different pollutant-emitting activities. 
                        <E T="03">See, e.g.,</E>
                         40 CFR 52.21(b)(5) and (6) (requiring the aggregation of all pollutant-emitting activities that belong to the same major industrial grouping, are located on one or more contiguous or adjacent properties, and are under the control of the same person (or persons under common control)). Although these activities might be assigned different source categories if viewed in isolation, EPA's longstanding approach is to examine the source as a whole and assign it to a single source category based on its “primary activity.” 
                        <E T="03">See, e.g.,</E>
                         54 FR 48870, 48881 (November 28, 1989). Under this approach, if the source's primary activity is determined to be one of the listed source categories, then fugitive emissions from 
                        <E T="03">all</E>
                         pollutant-emitting activities that are part of that stationary source are considered in determining whether the source as a whole exceeds the relevant major source threshold. 
                        <E T="03">See, e.g.,</E>
                         54 FR 48882; Letter from Cheryl Newton, EPA Region 5, to Janet McCabe, Indiana Department of Environmental Management (March 6, 2003) (
                        <E T="03">Newton Letter</E>
                        ). Even if the primary activity of a source does not fit within a listed source category, fugitive emissions should be quantified from emission units within the source that do belong to a listed category (
                        <E T="03">e.g.,</E>
                         a boiler of sufficient size, or a coal cleaning plant); this is sometimes referred to as a “nested” or “embedded” source. 
                        <E T="03">See, e.g., Newton Letter.</E>
                         In this case, fugitive emissions from the “nested” portion of the source belonging to a listed source category 
                        <E T="03">would</E>
                         be included in determining whether (1) the “nested” portion of the source exceeded the relevant major source threshold (generally 100 tons per year), and whether (2) the source as a whole exceeded the relevant major source threshold (generally 250 tons per year for PSD).
                    </P>
                </FTNT>
                <P>
                    Second, the inclusion of fugitive emissions may impact whether a physical or operational change at a major stationary source results in a “major modification.” This proposed action addresses the treatment of fugitive emissions in this second context. As discussed further in Sections III and IV of this preamble, the EPA proposes to affirm its longstanding position that all existing major sources (regardless of source category) must include fugitive emissions when determining if a modification is major. A summary of the relevant history of the treatment of fugitive emissions in the context of modifications is presented in Section II.D of this preamble; additional discussion of the legal and policy considerations underlying this history is included in Section IV.A of this preamble.
                    <PRTPAGE P="62326"/>
                </P>
                <P>
                    Once a source is subject to the major NSR program, fugitive emissions are generally treated the same as stack emissions in determining which substantive requirements apply to the source.
                    <SU>6</SU>
                    <FTREF/>
                     Specifically, for PSD, once a new source is determined to be “major” (
                    <E T="03">i.e.,</E>
                     over the 100 or 250 tpy threshold) for a particular pollutant, all emissions (including fugitive emissions) are included in all subsequent analysis, including PSD applicability for other individual pollutants (
                    <E T="03">i.e.,</E>
                     comparing emissions to the significant emission rates), Best Available Control Technology (BACT) analyses, and air quality impact analyses. 
                    <E T="03">E.g.,</E>
                     40 CFR 52.21(j)(2); 
                    <E T="03">see also</E>
                     54 FR 48871 n.2. Similarly, once a modification is determined to be major with respect to at least one regulated NSR pollutant (and provided an exemption discussed in Section II.D of this preamble does not apply), fugitive emissions are included in all subsequent analyses. 
                    <E T="03">E.g.,</E>
                     40 CFR 52.21(j)(3); 
                    <E T="03">see also</E>
                     54 FR 48871 n.2; 
                    <E T="03">In re Masonite Corp.,</E>
                     5 EAD 551, 582-83 (EAB 1994).
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See generally Alabama Power</E>
                         v. 
                        <E T="03">Costle,</E>
                         636 F.2d 323, 369 (D.C. Cir. 1979) (“The terms of section 165, which detail the preconstruction review and permit requirements for each new or modified `major emitting facility' apply with equal force to fugitive emissions and emissions from industrial point sources . . . . EPA is correct that a major emitting facility is subject to the requirements of section 165 for each pollutant it emits irrespective of the manner in which it is emitted.”).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">D. Fugitive Emissions in Major Modification Determinations</HD>
                <P>
                    Following the 1977 CAA Amendments, the EPA's initial 1978 regulations implementing the major NSR program required that fugitive emissions from sources in all source categories be included in the first instance in calculating whether a new source or modification of an existing source was major.
                    <SU>7</SU>
                    <FTREF/>
                     However, in its 1979 
                    <E T="03">Alabama Power</E>
                     decision that reviewed the 1978 regulations,
                    <SU>8</SU>
                    <FTREF/>
                     the D.C. Circuit held that CAA section 302(j) requires a rulemaking to identify the sources that must include fugitive emissions in determining whether a source is a “major emitting facility” (
                    <E T="03">i.e.,</E>
                     “major stationary source”). In response, in 1980 the EPA promulgated a list of source categories, along with a provision exempting sources not belonging to one of those listed source categories from substantive major NSR requirements if the source 
                    <E T="03">or modification</E>
                     would be considered “major” solely due to the inclusion of fugitive emissions. 45 FR 52676 (August 7, 1980) (promulgating, 
                    <E T="03">e.g.,</E>
                     40 CFR 52.21(i)(4)(vii), which was later recodified at 40 CFR 52.21(i)(1)(vii) in 2002).
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See, e.g.,</E>
                         43 FR 26380, 26403-04 (June 19, 1978); 
                        <E T="03">see also</E>
                         48 FR 38742, 38743 (August 25, 1983) (discussing history of the EPA's treatment of fugitive emissions in the 1978 rule and related rules); 49 FR 43202 (October 26, 1984) (same). These initial regulations excluded “fugitive dust” from air quality impact assessments, but this exclusion was vacated by the D.C. Circuit court. 
                        <E T="03">See Alabama Power,</E>
                         636 F.2d at 370.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">Alabama Power,</E>
                         636 F.2d 323.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         The 1980 rule also added this exemption to EPA's NSR regulations in 40 CFR 51.18 (later recodified in 40 CFR 51.165), 40 CFR 51.24 (later recodified in 40 CFR 51.166), and 40 CFR part 51 appendix S. Collectively, these four nearly identical provisions are referred to as the “1980 exemption.” For an illustration of how the 1980 exemption has functioned in the major modification context, see 
                        <E T="03">In re Masonite Corp.,</E>
                         5 EAD 551, 581-83 (EAB 1994).
                    </P>
                </FTNT>
                <P>
                    In 1984, the EPA finalized revisions to the NSR regulations that were intended to better implement CAA section 302(j), the statutory provision on which the 1980 exemption was based. In the context of major source determinations, the EPA revised the definition of “major source” such that sources in non-listed source categories need not include fugitive emissions in the first instance in determining whether their emissions exceed major source thresholds. 49 FR 43202 (October 26, 1984). This reflected a more straightforward approach for major source determinations than the one established in the 1980 exemption.
                    <SU>10</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Under the 1980 exemption, all sources were still required to include fugitive emissions in the first instance when calculating whether a new source or modification would be major. As a result, a non-listed source or modification could theoretically be classified as a major source but nonetheless exempt from substantive major NSR requirements if the terms of the exemption were met. In 1981, the EPA granted a petition for reconsideration of this aspect of the 1980 rules and clarified that the regulations were not intended to function this way. Instead, the intent was that any source in a non-listed category that would be “major” only if fugitive emissions were taken into account should not be considered “major.” 
                        <E T="03">See</E>
                         Letter from Douglas M. Costle, Administrator, EPA, to Robert T. Connery (January 19, 1981). The EPA's 1984 amendments to the “major source” definition codified this intent by excluding fugitive emissions from the major source calculation in the first instance. 
                        <E T="03">See</E>
                         49 FR 43202 at 43204 and 43208-09 (October 26, 1984).
                    </P>
                </FTNT>
                <P>
                    The EPA declined at that time to finalize a similar revision for major modifications. Instead, in a companion document to the 1984 final rule, the EPA proposed an “interpretive ruling” reevaluating and reversing the EPA's prior assumption that fugitive emissions should be treated the same in major source and major modification contexts. 49 FR 43211 (October 26, 1984). For major modification determinations, the EPA proposed to include quantifiable fugitive emissions from sources in 
                    <E T="03">all</E>
                     source categories when determining whether a physical or operational change meets the significance thresholds for a major modification. This was based on the EPA's interpretation that CAA section 302(j) does not apply in the major modification context, and that CAA section 111(a)(4), which defines “modification,” requires consideration of all types of emissions (as discussed further in Section IV.A of this preamble). Along with this interpretation, the EPA proposed to remove the 1980 exemption, which was no longer needed in the major source context after the 1984 revisions and which conflicted with the agency's proposed interpretation in the major modification context. In 1986, the EPA again solicited comment on the 1984 “interpretive ruling.” 51 FR 7090 (February 28, 1986).
                </P>
                <P>
                    The EPA ultimately “retain[ed]” and “reaffirm[ed]” the EPA's 1984 interpretive ruling in a 1989 action finalizing certain other rule revisions. 54 FR 48870 (November 28, 1989).
                    <SU>11</SU>
                    <FTREF/>
                     This interpretation—that all sources must include fugitive emissions in the major modification context—remained the EPA's position until 2008.
                    <SU>12</SU>
                    <FTREF/>
                     The EPA inadvertently failed to remove the 1980 exemption in the 1989 rule, creating an apparent conflict between the EPA's interpretation and the legacy regulatory text.
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Subsequent EPA rules have referred to this 1989 rule as “finalizing” the EPA's 1984 interpretive ruling. 
                        <E T="03">E.g.,</E>
                         73 FR 77884 (December 19, 2008).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         In October 1990, the EPA released a draft New Source Review Workshop Manual, in which the agency stated that fugitive emissions “are included in the potential to emit (and increases in the same due to modification)” if they occur at one of the source categories listed pursuant to section 302(j). DRAFT NSR Workshop Manual at A.9 (1990). This phrasing seemingly contradicted the 1989 interpretive ruling, although the EPA later acknowledged that this language was not intended to change the EPA's policy in this area. 73 FR 77885 (December 19, 2008). A 1994 EPA Environmental Appeals Board decision, 
                        <E T="03">In re. Masonite Corp.,</E>
                         considered the existing regulatory text addressing the treatment of fugitive emissions in major modification determinations but did not evaluate or disturb the 1989 interpretation. 
                        <E T="03">See</E>
                         5 EAD at 581-83.
                    </P>
                </FTNT>
                <P>
                    In 2002, the EPA finalized major revisions to its NSR regulations. 67 FR 80186 (December 31, 2002) (“NSR Reform Rule”). Among many other changes, and consistent with the 1989 interpretive ruling, this 2002 rule explicitly required the inclusion of fugitive emissions in calculating emissions increases for purposes of determining whether a physical or operational change constitutes a major modification for all major sources, regardless of source category.
                    <FTREF/>
                    <SU>13</SU>
                      
                    <PRTPAGE P="62327"/>
                    Notwithstanding this affirmation and codification of the agency's longstanding position, the EPA again inadvertently left the 1980 exemption in the CFR.
                    <SU>14</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See, e.g.,</E>
                         40 CFR 52.21(b)(41)(ii)(b) and 52.21(b)(48)(i)(a) (definitions of “projected actual emissions” and “baseline actual emissions,” both of which include fugitive emissions to the extent quantifiable).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         Although the 1980 exemption was renumbered from 40 CFR 52.21(i)(4)(vii) to 40 CFR 52.21(i)(1)(vii) in the 2002 NSR Reform Rule, its content was not altered. As a result, the 1980 exemption—which speaks in terms of calculating 
                        <E T="03">potential</E>
                         emissions increases—does not align with the other changes effectuated in the 2002 rule, which focus on calculating or projecting 
                        <E T="03">actual</E>
                         emissions increases in determining whether a project is a major modification.
                    </P>
                </FTNT>
                <P>
                    In 2003, the EPA received a petition from Newmont USA Ltd., dba Newmont Mining Corporation, requesting that the EPA reconsider the treatment of fugitive emissions in the provisions adopted in the 2002 NSR Reform Rule.
                    <SU>15</SU>
                    <FTREF/>
                     After granting the petition for reconsideration in 2004,
                    <SU>16</SU>
                    <FTREF/>
                     the EPA proposed in 2007 and finalized in 2008 a rule titled “Prevention of Significant Deterioration (PSD) and Nonattainment New Source Review (NSR): Reconsideration of Inclusion of Fugitive Emissions” (the Fugitive Emissions Rule). 72 FR 63850 (November 13, 2007); 73 FR 77882 (December 19, 2008). The Fugitive Emissions Rule, which became effective on January 20, 2009, reversed the EPA's position as set forth in the 1984 and 1989 interpretive rulings concerning the treatment of fugitive emissions for major modification purposes. Under the Fugitive Emissions Rule, only sources in listed source categories designated through rulemaking pursuant to section 302(j) of the Act needed to include fugitive emissions in determining whether a change is a major modification. Thus, the Fugitive Emissions Rule adopted the same approach for considering fugitive emissions when determining whether a change is a major modification as has been used since 1984 for determining whether a source is a major stationary source. Because the 2008 Fugitive Emissions Rule rendered the 1980 exemption obsolete in the major modification context, the EPA also removed the 1980 exemption in the 2008 rule.
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         Newmont Mining Corporation, EPA-HQ-OAR-2004-0014-0005.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         Jeffrey R. Holmstead, EPA, EPA-HQ-OAR-2004-0014-0014.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">E. Petition for Reconsideration and Administrative Stays of the Fugitive Emissions Rule</HD>
                <P>
                    On February 17, 2009, the Natural Resources Defense Council (NRDC) submitted a petition for reconsideration of the 2008 Fugitive Emissions Rule under CAA 307(d)(7)(B).
                    <SU>17</SU>
                    <FTREF/>
                     On April 24, 2009, the EPA responded by letter indicating that the EPA was convening a reconsideration proceeding and granting a 3-month administrative stay of the rule.
                    <SU>18</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         John Walke, NRDC, EPA-HQ-OAR-2004-0014-0060.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         Lisa Jackson, EPA, EPA-HQ-OAR-2004-0014-0062.
                    </P>
                </FTNT>
                <P>The initial 3-month administrative stay of the Fugitive Emissions Rule became effective on September 30, 2009. 74 FR 50115 (September 30, 2009). An interim final rule extending the stay for an additional 3 months became effective on December 31, 2009. 74 FR 65692 (December 11, 2009). An additional 18-month stay became effective on April 1, 2010. 75 FR 16012 (March 31, 2010). In each of these stay actions (beginning on September 30, 2009), the EPA not only stayed the CFR paragraphs added or changed by the Fugitive Emissions Rule, but also amended the CFR to temporarily reinstate the 1980 exemption (which had been removed by the 2008 rule).</P>
                <P>
                    These initial administrative stays were intended to “effectuate this stay of the December 19, 2008, rule [by] reinstating previous provisions on a temporary basis.” 74 FR 50115. However, in several cases, paragraphs of the affected regulations were stayed in their entirety, unintentionally staying existing regulatory provisions unrelated to those that were revised by the Fugitive Emissions Rule. To correct this error, on March 30, 2011, the EPA published an “interim rule” to more precisely effectuate the stay of the Fugitive Emissions Rule itself (
                    <E T="03">i.e.,</E>
                     to stay only those portions of the NSR regulations that were added or revised by the 2008 rule, without staying other unrelated portions of the NSR regulations). 76 FR 17548 (March 30, 2011). In order to do this, the interim rule revised 47 paragraphs of the regulatory text that were changed by the Fugitive Emissions Rule, reverting these paragraphs to the regulatory text that existed prior to the Fugitive Emissions Rule.
                    <SU>19</SU>
                    <FTREF/>
                     And, as with the 2009 and 2010 actions, in the 2011 action, the EPA again added the 1980 exemption back to the four relevant sections of the CFR. The interim rule also extended the stay of seven other provisions indefinitely until the EPA completed its reconsideration of the Fugitive Emissions Rule.
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         For a complete list of these provisions, 
                        <E T="03">see</E>
                         76 FR 17551.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         Although the 2011 interim rule was effective immediately, the EPA also provided a public comment period. 76 FR 17551. This solicitation of comments pertained to the procedural action undertaken in the 2011 interim rule—measures to stay the effectiveness of the 2008 Fugitive Emissions Rule—and did not extend to the substance of the EPA's reconsideration of the 2008 Fugitive Emissions Rule. Nonetheless, several comments on the 2011 interim rule addressed substantive topics related to the EPA's reconsideration. The current proposed rule generally addresses those substantive comments as well as substantive comments provided during earlier regulatory actions. Commenters are welcome to submit or re-submit any comments relevant to the content of this proposed rule.
                    </P>
                </FTNT>
                <P>In summary, due to the EPA's stay actions described in this section, the Fugitive Emissions Rule only briefly took effect between January 20, 2009, and September 30, 2009. Since 2009, the regulations that predated the 2008 Fugitive Emissions Rule have been the operative regulations governing the treatment of fugitive emissions in the major modification context.</P>
                <HD SOURCE="HD1">III. Proposed Action</HD>
                <HD SOURCE="HD2">A. Results of the EPA's Reconsideration</HD>
                <P>This proposed rule seeks to close out the reconsideration process initiated in 2009 in a manner that better aligns with the structure and purpose of the NSR program and that minimizes confusion for all stakeholders. After reevaluating the legal and policy bases of the Fugitive Emissions Rule, the EPA no longer considers that rule's treatment of fugitive emissions in the context of major modifications to be appropriate. Instead, for the reasons described further in Sections IV and V of this preamble, the EPA is proposing to reaffirm the EPA's longstanding interpretation of CAA sections 302(j) and 111(a)(4). Specifically, the EPA proposes to reaffirm its interpretation that the language in CAA section 302(j) regarding fugitive emissions applies only in the major source context, and not in the major modification context. The EPA proposes to interpret CAA section 111(a)(4) to require that all sources consider increases in all types of emissions (including fugitive emissions) in determining whether a proposed change would constitute a major modification. Accordingly, the EPA is proposing to repeal the 2008 Fugitive Emissions Rule by removing the portions of the 2008 rule that remain in the agency's NSR regulations.</P>
                <P>
                    Additionally, in light of the statutory interpretation presented in Section IV.C of this preamble, the EPA is proposing to remove the “major solely due to the inclusion of fugitive emissions” exemption first promulgated in 1980 and reinstated in 2009. As described in Section II.D of this preamble, this 1980 exemption was inadvertently left in the EPA's regulations from 1989 to 2008 despite the fact that the agency had interpreted the statute in that period (as EPA proposes now) to provide no such exemption in the context of 
                    <PRTPAGE P="62328"/>
                    modifications. This inconsistency, along with other issues related to the 1980 exemption, has created significant uncertainty about the EPA's treatment of fugitive emissions in the major modification context.
                </P>
                <HD SOURCE="HD2">B. Proposed Revisions to Regulations</HD>
                <P>The Fugitive Emissions Rule revised similar regulatory text in all four sections of the CFR associated with the major NSR program, including 40 CFR 51.165, 51.166, 52.21, and appendix S to part 51. This proposed action would revise the text in each of these four sections in order to fully repeal the 2008 rule.</P>
                <P>As discussed in Section II.E of this preamble, the EPA's March 2011 interim rule revised 47 paragraphs of the regulatory text that had been changed by the Fugitive Emissions Rule, reverting these paragraphs back to the text that existed prior to the Fugitive Emissions Rule. These paragraphs need not be revised further in this action in order to repeal the Fugitive Emissions Rule. To the extent necessary, the EPA proposes in this action to affirm those changes to the regulatory text effectuated in the March 2011 interim rule and lift the “interim” label from those aspects of the 2011 rule.</P>
                <P>
                    Seven additional paragraphs that were added (instead of revised) by the Fugitive Emissions Rule were stayed in the EPA's 2009, 2010, and 2011 actions, but still exist within the EPA's NSR regulations. 40 CFR 51.165(a)(1)(v)(G), 51.165(a)(1)(vi)(C)(
                    <E T="03">3</E>
                    ), 51.166(b)(2)(v), 51.166(b)(3)(iii)(
                    <E T="03">d</E>
                    ), part 51 appx. S II.A.5(vii), 52.21(b)(2)(v), 52.21(b)(3)(iii)(
                    <E T="03">c</E>
                    ). These provisions are accompanied by a notation in the CFR (at the end of each CFR section) that these provisions are stayed and have no current legal effect. For these paragraphs, the EPA is proposing to concurrently lift the existing stay and remove these provisions from the regulations (the only way to remove these provisions is to lift the stay). In so doing, the EPA intends to permanently restore the relevant regulatory text that existed before the Fugitive Emissions Rule was promulgated.
                </P>
                <P>Four paragraphs embodying the 1980 exemption were removed by the Fugitive Emissions Rule, but were reinstated in the EPA's 2009, 2010, and 2011 actions in order to effectuate a stay of the Fugitive Emissions Rule. 40 CFR 51.165(a)(4), 51.166(i)(1)(ii), 52.21(i)(1)(vii), and part 51 appx. S II.F. In light of the interpretation advanced in Section IV.C of this preamble—that all sources must account for fugitive emissions in determining whether a modification is major—the EPA is also proposing to remove these provisions embodying the 1980 exemption.</P>
                <P>Given the number and complexity of the regulatory provisions impacted by the Fugitive Emissions Rule and the current proposal, the EPA specifically seeks comment on whether the proposed changes to the regulatory text, in addition to those changes previously made in 2011, will fully effectuate the repeal of the Fugitive Emissions Rule and conform the EPA's regulations to the interpretation described in Section IV.C of this preamble.</P>
                <HD SOURCE="HD1">IV. Interpretation of CAA Sections 302(j) and 111(a)(4)</HD>
                <P>The plain language of CAA sections 302(j) and 111(a)(4), as well as the legislative history and case law involving these provisions, supports requiring that all existing major sources include fugitive emissions when determining whether a modification at the source requires a major NSR permit. This view is consistent with the approach the EPA has applied in the NSR program for most of the past 4 decades, but the EPA has inadvertently fostered uncertainty on this subject through its rulemaking actions and omissions. To end this uncertainty and better align the regulations with the structure and purpose of the NSR program, the EPA proposes to affirm the longstanding interpretation that fugitive emissions must be counted from all existing major sources when determining whether a modification is major. As discussed in Section V of this preamble, this approach properly accommodates the relevant policy considerations associated with balancing the potential air quality benefits that could result from this action with the potential impacts on a limited subset of sources.</P>
                <HD SOURCE="HD2">A. Previous EPA Interpretations</HD>
                <P>
                    When the EPA established the foundation for the current NSR program in response to the 1977 CAA Amendments, the EPA required all quantifiable emissions (including fugitive emissions) to be considered in determining whether sources are subject to major NSR. 43 FR 26388, 26395 (June 19, 1978) (“[T]he regulations do not exclude fugitive dust from the determination of potential emissions.”).
                    <SU>21</SU>
                    <FTREF/>
                     However, in recognition of concerns from the surface coal mining industry, the EPA's 1978 regulations excluded “fugitive dust” from air quality impact assessments for new and modified sources. 
                    <E T="03">See, e.g.,</E>
                     40 CFR 52.21(k)(5) (1978); 43 FR 26395.
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         As the EPA later explained, prior to 1980, the “EPA considered 
                        <E T="03">all</E>
                         reasonably quantifiable emissions of a pollutant—including both point emissions (
                        <E T="03">e.g.,</E>
                         from a stack or chimney) and fugitive emissions—on the ground[s] that the emissions deteriorate air quality regardless of how they emanate.” 45 FR 52690 (August 7, 1980).
                    </P>
                </FTNT>
                <P>
                    In its 1979 
                    <E T="03">Alabama Power</E>
                     decision, the U.S. Court of Appeals for the D.C. Circuit considered various challenges to the 1978 NSR regulations, including those related to the treatment of fugitive emissions. In relevant part, the D.C. Circuit stated that it had “reason to doubt whether EPA possesses the statutory authority to promulgate the [fugitive dust] exception in this manner.” 
                    <E T="03">Id.</E>
                     at 370.
                    <SU>22</SU>
                    <FTREF/>
                     Although the court did not specifically resolve the matter, it nonetheless vacated and remanded the 1978 fugitive dust exemption “[i]n light of [the court's] interpretation of section 302(j), and in accordance with [the court's] discussion as to the limits of EPA general exemption authority.”
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         In suggesting this, the court referred to another section of its opinion, where the court identified “principles pertinent to an agency's authority to adopt general exemptions to statutory requirements.” 
                        <E T="03">Id.</E>
                         at 357; 
                        <E T="03">see id.</E>
                         at 357-361.
                    </P>
                </FTNT>
                <P>
                    The D.C. Circuit's discussion of CAA section 302(j) was particularly noteworthy. CAA section 302(j) defines “major stationary source” and “major emitting facility” as “any stationary facility or source of air pollutants which directly emits, or has the potential to emit, one hundred tons per year or more of any air pollutant (including any major emitting facility or source of fugitive emissions of any such pollutant, as determined by rule by the Administrator).” 42 U.S.C. 7602(j). The D.C. Circuit held that CAA “section 302(j) specifically attaches a rulemaking requirement for the inclusion of fugitive emissions in the threshold calculation” of determining whether a source is a “major emitting facility.” 636 F.2d at 369.
                    <SU>23</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         The D.C. Circuit found that the general definition of “major stationary source” or “major emitting facility” in CAA section 302(j) was not expressly modified by the PSD-specific definition of “major emitting facility” in CAA section 169(1) (which is silent with respect to fugitive emissions), and accordingly that CAA section 302(j)'s rulemaking requirement for fugitive emissions controlled with respect to the PSD program. 636 F.2d at 370.
                    </P>
                </FTNT>
                <P>
                    In response to the 
                    <E T="03">Alabama Power</E>
                     decision, in its 1980 revisions to the NSR regulations, the EPA removed the 1978 partial exclusion for fugitive dust. In order to implement the CAA section 302(j) rulemaking requirement, the EPA also listed, by rule, a number of source categories for which fugitive emissions were to be considered in threshold determinations. 
                    <E T="03">See</E>
                     45 FR 52676 (August 7, 1980) (promulgating, 
                    <E T="03">e.g.,</E>
                     40 
                    <PRTPAGE P="62329"/>
                    CFR 52.21(i)(4)(vii), which was later recodified at 40 CFR 52.21(i)(1)(vii) in 2002). Specifically, although the 1980 regulations required all sources to include fugitive emissions in the first instance when determining whether a new source or modification was considered major, the 1980 rule provided an exemption from substantive major NSR requirements for sources that did not belong to a listed source category if the source or modification would be considered “major” solely due to the inclusion of fugitive emissions. This 1980 exemption did not differentiate between “major source” and “major modification” inquiries. However, the EPA did not discuss this lack of differentiation, nor did the EPA suggest that this result was required by CAA section 302(j) or the 
                    <E T="03">Alabama Power</E>
                     decision.
                    <SU>24</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         The EPA's 1980 preamble discussion spoke generally of “threshold determinations” or “threshold calculations” but did not specifically evaluate whether or how both the major source and major modification inquiries were implicated by CAA section 302(j) and the 
                        <E T="03">Alabama Power</E>
                         decision. Where the EPA did speak more specifically to one of these inquiries, it spoke only to “major emitting facility” (
                        <E T="03">i.e.,</E>
                         “major source”) determinations under CAA sections 169(1) and 302(j). 
                        <E T="03">See, e.g.,</E>
                         45 FR 52690.
                    </P>
                </FTNT>
                <P>
                    When the EPA revised the NSR regulations in 1984 to better implement the CAA section 302(j) rulemaking requirement, it finalized regulatory text within the definition of “major source” that more directly excluded fugitive emissions from major source calculations for sources not in the listed source categories. 49 FR 43202 (October 26, 1984). However, the EPA decided not to finalize similar revisions with respect to major modifications. Instead, in a companion document accompanying the 1984 rule, the EPA for the first time took a closer look at the applicability of section 302(j) and the 
                    <E T="03">Alabama Power</E>
                     decision in the context of major modifications. The EPA explained that in its 1980 and 1983 regulatory actions, the “EPA 
                    <E T="03">assumed</E>
                     that the rulemaking requirement in section 302(j) applies to modifications as well as to sources.” 49 FR 43213 (October 26, 1984) (emphasis added).
                    <SU>25</SU>
                    <FTREF/>
                     The EPA further explained that the litigants and commenters on those 1980 and 1983 actions similarly “carried that assumption into their communications, without evidencing any examination of it.” 
                    <E T="03">Id.</E>
                     After examining the assumption for the first time in 1984, the EPA “concluded that it appears to be incorrect.” 
                    <E T="03">Id.</E>
                     Accordingly, the EPA proposed an “interpretive rule” outlining its interpretation that CAA section 302(j) did 
                    <E T="03">not</E>
                     apply in the major modification context, and that all sources (not just those in a listed source category) should include fugitive emissions in the major modification context. The 1984 proposed interpretive rule, summarized in the following paragraphs, explained the basis for the decision in considerable detail. 
                    <E T="03">See</E>
                     49 FR 43213.
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         Put another way, the EPA's 1980 interpretation “took it for granted” that fugitive emissions would be treated the same for major source and major modification determinations. 72 FR 63857 (November 13, 2007).
                    </P>
                </FTNT>
                <P>
                    First, the EPA explained that the plain language of the Act strongly suggests that Congress did not intend the rulemaking requirement in section 302(j) to apply to modifications. The EPA noted that CAA section 302(j) on its face defines major source and does not speak to modifications of those sources. By contrast, the EPA noted that the definition of “modification” in CAA section 111(a)(4) (which is incorporated by the statutory provisions for major NSR 
                    <SU>26</SU>
                    <FTREF/>
                    ) appears to require the inclusion of fugitive emissions in threshold applicability determinations for modifications. CAA section 111(a)(4) provides that “the term `modification' means any physical change in, or change in the method of operation of, a stationary source which increases the amount of any air pollutant emitted by such source or which results in the emissions of any air pollutant not previously emitted.” 42 U.S.C. 7411(a)(4). The EPA indicated that, in defining “modification” solely in terms of the total amount of pollution that a source change would produce, section 111(a)(4) suggests that Congress intended to establish here no qualitative distinction between different types of emissions (
                    <E T="03">e.g.,</E>
                     fugitive or non-fugitive). Thus, the EPA concluded that Congress intended to require the inclusion of fugitive emissions for modifications without any intermediate rulemaking step. 49 FR 43213.
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         CAA section 169(2)(C), 42 U.S.C. 7479(2)(C), which governs the PSD program, states: “The term `construction' when used in connection with any source or facility, includes the modification (as defined in section 111(a) of this title) of any source or facility.” CAA section 171(4), 42 U.S.C. 7501(4), which governs the NNSR program, states: “The terms `modification' and `modified' mean the same as the term `modification' as used in section 111(a)(4) of this title.”
                    </P>
                </FTNT>
                <P>
                    Next, the EPA's 1984 interpretive rule examined the legislative history surrounding these statutory provisions. With respect to CAA section 302(j), the EPA noted that the passages in the relevant House and conference reports that focus on CAA section 302(j) (as well as CAA section 302(j) itself) refer only to major sources, and not to modifications of these sources. 49 FR 43213 (citing H.R. Report No. 95-294, 95th Cong., 1st Sess. 4, 9, 144 (1977); H.S. Rep. No. 95-564, 95th Cong., 1st Sess. 172 (1977)). With respect to the reference to “modification” in the PSD provisions of the Act, the EPA indicated that the conference committee said that it “[i]mplements conference agreement to cover `modification' as well as `construction' by defining `construction' in Part C to conform to usage in other parts of the Act.” 
                    <E T="03">Id.</E>
                     (quoting 123 Cong. Rec. H. 11957. col. 3 (daily ed.) (November 1, 1977)). The EPA posited that the phrase “usage in other parts of the Act,” most likely refers not only to CAA section 111(a)(4), but also to the EPA regulations implementing section 111 that were in effect at the time. 
                    <E T="03">Id.</E>
                     The EPA explained that those regulations (as well as CAA section 111(a)(4) itself) on their face require the inclusion of fugitive emissions in CAA section 111 applicability determinations, inasmuch as they concern themselves only with the quantity of the emissions in question. 
                    <E T="03">Id.</E>
                     (citing 40 CFR 60.14(a) (1977)). Moreover, the EPA explained that prior to the enactment of CAA section 302(j) in 1977, both the EPA and states made no distinction between fugitive and non-fugitive emissions in threshold applicability determinations. 
                    <E T="03">Id.</E>
                     (citing 40 CFR 51.18, 52.21(d)(1) (1977); 41 FR 55528 (December 21, 1976)). Given that CAA section 302(j) ran against longstanding practice throughout the agency's implementation of the CAA, the EPA suggested that if Congress had intended a change as to modifications, it probably would have said so explicitly, yet Congress said nothing. 
                    <E T="03">Id.</E>
                </P>
                <P>
                    The 1984 interpretive rule also addressed practical issues related to the inclusion or exclusion of fugitive emissions in major modification determinations and concluded that including fugitive emissions in this context would be consistent with Congress's purposes, including the potential relief from the burdens of NSR afforded by the CAA section 302(j) rulemaking requirement. Given that the EPA's regulations did not require unlisted sources with predominantly fugitive emissions (
                    <E T="03">e.g.,</E>
                     surface coal mines) to count fugitive emissions towards major source thresholds, the EPA noted that it is unlikely that those sources would be considered major sources in the first instance. And, because only modifications to an existing major source can be considered major modifications, the EPA concluded that it would be unlikely for sources of predominantly fugitive emissions to be subject to major NSR due to a 
                    <PRTPAGE P="62330"/>
                    modification, even under the EPA's proposed interpretation. 49 FR 43214.
                </P>
                <P>
                    When the EPA “affirmed” the 1984 interpretive rule in a related 1989 rulemaking, it did so based on the justifications presented in 1984, with some additional discussion based on comments received from stakeholders. 
                    <E T="03">See</E>
                     54 FR 48882 (November 28, 1989). Specifically, commenters argued: (1) that congressional silence on the subject indicated a lack of guidance (rather than support for the EPA's position) and (2) because new sources and modifications are generally treated the same in most respects under the Act, there is no basis to treat them differently under CAA section 302(j). The EPA was not persuaded by these comments. The EPA concluded that its interpretation was both reasonable and proper, warranting deference under 
                    <E T="03">Chevron, U.S.A. Inc.</E>
                     v. 
                    <E T="03">Natural Resources Defense Council,</E>
                     467 U.S. 837 (1984). Additionally, the EPA reiterated and elaborated on its view that the agency's interpretation should have little general impact on sources of predominantly fugitive emissions like surface coal mines. This remained the EPA's interpretation of CAA sections 302(j) and 111(a)(4) until the Fugitive Emissions Rule was proposed in 2007 and finalized in 2008.
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         None of the EPA documents or actions that followed the 1989 interpretive ruling (
                        <E T="03">e.g.,</E>
                         the EPA's 1990 DRAFT NSR workshop manual, the 1995 
                        <E T="03">Masonite</E>
                         EAB decision, or the 2002 NSR Reform Rule) addressed the substance of the interpretations presented in 1989. As noted in the preamble to the 2008 rule, potentially conflicting statements in the 1990 DRAFT NSR workshop manual were not intended to reflect a change in position from the 1989 interpretive rule. 
                        <E T="03">See</E>
                         73 FR 77885 (December 19, 2008). The 1995 
                        <E T="03">Masonite</E>
                         EAB decision considered how the 1980 exemption (which, as noted in Section II.D of this preamble, was inadvertently not removed from the EPA's regulations in 1989) functioned in practice, and did not evaluate the EPA's 1989 interpretive rule or the statutory bases underlying the agency's 1989 interpretation. 
                        <E T="03">See</E>
                         5 EAD at 581-83. The 2002 NSR Reform Rule explicitly codified the position expressed in the 1989 interpretive rule, without further discussion of the EPA's interpretation of the relevant statutory provisions.
                    </P>
                </FTNT>
                <P>The Fugitive Emissions Rule represented a significant shift in the EPA's treatment of fugitive emissions. This 2008 rule was the first time the EPA had, after focused deliberation, applied the CAA section 302(j) rulemaking requirement to major modifications, such that only sources in categories listed by rule would need to account for fugitive emissions when determining whether a project constituted a major modification.</P>
                <P>
                    To justify this changed interpretation, the EPA argued that the lack of any reference in CAA section 302(j) to “major modification,” in addition to a scant legislative history, created ambiguity and room for the EPA to extend CAA section 302(j) to the context of major modifications.
                    <FTREF/>
                    <SU>28</SU>
                      
                    <E T="03">See</E>
                     73 FR 77888 (December 19, 2008). The EPA stated that it could not conclude from the statutory text or legislative history what Congress specifically intended on this point.
                    <SU>29</SU>
                    <FTREF/>
                     Accordingly, the EPA suggested that Congress simply did not know enough to make the critical decisions regarding the treatment of fugitive emissions in the major source and major modification contexts, instead assigning resolution of these complex issues to the EPA. The EPA additionally posited that CAA “section 302(j) evinces, at a minimum, an intent by Congress to require a special look at fugitive emissions for purposes of calculating a source's emissions for NSR purposes.” 73 FR 77888.
                    <SU>30</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         Notably, even as the EPA reversed its prior interpretation of CAA 302(j), it nonetheless maintained that the EPA's historical interpretation finalized in 1989 remained a reasonable construction of the statute.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         The EPA indicated that no authoritative conference or committee report addressed the issue of how fugitive emission should be addressed in NSR permitting. The EPA nonetheless addressed portions of the legislative history reflecting industry testimony detailing concerns with the feasibility of controlling or measuring fugitive emissions.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         The EPA's rationale in the Fugitive Emissions Rule focused on CAA section 302(j) and largely did not address CAA section 111(a)(4). After summarizing the EPA's prior interpretation (and public comments) relating to the CAA section 111(a)(4) definition of “modification,” the EPA simply asserted that this statutory provision does not “address the issue” without further discussion. 73 FR 77888.
                    </P>
                </FTNT>
                <P>
                    The EPA then explained the policy and programmatic reasons supporting its shift in approach. First, the EPA stated that its new position was most consistent with its earliest and most nearly contemporaneous construction of the statute in the 1980 NSR rules. The EPA argued that providing a more uniform approach—
                    <E T="03">i.e.,</E>
                     treating fugitive emissions the same in both major source and major modification contexts—more accurately reflected the original intent of Congress in establishing CAA section 302(j) and the resulting EPA rules that followed. Second, the EPA said that the revised position better addressed an additional regulatory burden that had not been adequately recognized in the past. Specifically, the EPA asserted that the EPA's policies discussed in 1984 and 1989 would have imposed a new burden on major sources in unlisted source categories, “since their fugitive emissions would be counted in determining whether they had made a change constituting a major modification and thus possibly subjecting those modifications to NSR review.” 73 FR 77889.
                </P>
                <HD SOURCE="HD2">B. NRDC's Petition for Reconsideration</HD>
                <P>
                    NRDC's 2009 petition for reconsideration argued that the Fugitive Emissions Rule was unlawful and urged the EPA to return to its prior interpretation concerning fugitive emissions. NRDC's petition focused largely on the definition of “modification” in CAA section 111(a)(4). Citing CAA section 111(a)(4) and the D.C. Circuit's 2005 
                    <E T="03">New York</E>
                     v. 
                    <E T="03">EPA</E>
                     decision (
                    <E T="03">New York I</E>
                    ),
                    <SU>31</SU>
                    <FTREF/>
                     NRDC emphasized that the definition of modification focuses exclusively on increases in “actual” emissions. NRDC asserted that the EPA's prior interpretations echoed this focus and did not differentiate between stack emissions and fugitive emissions, instead focusing on the total amount of pollution that a change at a source would produce. Citing the D.C. Circuit's 2006 
                    <E T="03">New York</E>
                     v. 
                    <E T="03">EPA</E>
                     decision (
                    <E T="03">New York II</E>
                    ),
                    <SU>32</SU>
                    <FTREF/>
                     NRDC further asserted that the coverage of CAA section 111(a)(4) is broad—including 
                    <E T="03">any</E>
                     physical change that increases emissions—and subject only to narrow 
                    <E T="03">de minimis</E>
                     exceptions.
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         413 F.3d 3, 40 (D.C. Cir. 2005).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         443 F.3d 880, 885 (D.C. Cir. 2006).
                    </P>
                </FTNT>
                <P>
                    NRDC claimed that, in promulgating the Fugitive Emissions Rule, the EPA failed to address the definition of modification in CAA section 111(a)(4), explain its reversal of its interpretation of this statutory provision, or respond to comments concerning this provision. Moreover, NRDC claimed that the Fugitive Emissions Rule created an impermissible exemption to the definition of “modification” because the EPA did not (and could not) claim (1) that the exemption was supported by the 
                    <E T="03">de minimis</E>
                     doctrine, (2) that increased fugitive emissions do not qualify as “the amount of any air pollutant emitted by such source” under CAA section 111(a)(4), or (3) that exempt fugitive emissions increases do not fall within the meaning of “any physical change” or “any” change in the method of operation under CAA section 111(a)(4).
                    <SU>33</SU>
                    <FTREF/>
                     As noted previously, on April 24, 2009, the EPA responded by letter indicating that the EPA was convening a reconsideration proceeding.
                </P>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         The NRDC petition also raised other arguments, including a discussion of the legislative history of CAA section 302(j) and other concerns related to the implementation of the Fugitive Emissions Rule by state and local air agencies.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Proposed Interpretation of CAA Sections 302(j) and 111(a)(4)</HD>
                <P>
                    After reconsidering the 2008 Fugitive Emissions Rule, the EPA proposes to return to the position first articulated in 1984, adopted in a final action in 1989, 
                    <PRTPAGE P="62331"/>
                    and which remained the EPA's interpretation until revisited in 2008. Given CAA section 302(j)'s silence with respect to modifications, in conjunction with the definition of “modification” in CAA section 111(a)(4), the EPA does not believe the CAA section 302(j) rulemaking requirement applies to major modification determinations. Moreover, the EPA does not consider it appropriate to allow existing major sources in non-listed source categories to omit increases and decreases in fugitive emissions when evaluating whether a physical or operational change constitutes a major modification. All major sources should include both stack and fugitive emissions in the major modification context.
                </P>
                <P>
                    The EPA considers this a prudent change in position. The EPA's treatment of fugitive emissions in modifications has a complicated history, particularly during the early years of the NSR program following the 1977 CAA Amendments. However, the interpretation advanced now most closely aligns with the interpretation of CAA section 302(j) originally proposed in 1984 and adopted in 1989. This interpretation was more thoughtful and fully developed than the one the EPA had followed from 1980 until 1984,
                    <SU>34</SU>
                    <FTREF/>
                     and has reflected the EPA's position for the majority of the NSR program's existence.
                    <SU>35</SU>
                    <FTREF/>
                     More importantly, the legal and policy reasoning advanced in the 1984 and 1989 actions (summarized in Section IV.A of this preamble), in light of more recent case law (
                    <E T="03">New York I</E>
                     and 
                    <E T="03">II</E>
                    ), reflects a more complete depiction of the relevant statutory authorities than the reasoning articulated in the 2008 Fugitive Emissions Rule. The EPA also believes this approach fully accommodates congressional intent and the practical and policy considerations surrounding this issue. Therefore, for the reasons detailed later in this preamble, the EPA is well-justified in returning to its longest-standing view concerning the treatment of fugitive emissions in the major modification context.
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         As noted in the EPA's 1984 action (and acknowledged in the Fugitive Emissions Rule itself), the EPA's interpretations prior to 1984 “assumed” and “took for granted” that fugitive emissions should be treated the same for major source and major modification decisions, without evaluating whether CAA section 302(j) or the D.C. Circuit's 
                        <E T="03">Alabama Power</E>
                         decision lent themselves to this result. 
                        <E T="03">See</E>
                         49 FR 43213 (October 26, 1984); 72 FR 63857 (November 13, 2007). Thus, the EPA's claim in 2008 that the Fugitive Emissions Rule was “most consistent with EPA's earliest and most nearly contemporaneous construction of the statute” was not entirely accurate. 73 FR 77888 (December 19, 2008). By the EPA's 2008 logic, one could just as easily describe the EPA's 1978 approach—which considered fugitive emissions from all sources for both major source and major modification purposes—as the “most nearly contemporaneous construction of the statute.” However, both the EPA's 1978 and 1980-1983 approaches similarly neglected to fully consider of the specific text of CAA sections 302(j) and 111(a)(4).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         The EPA's alternate interpretation—proposed in 2007 and finalized in the 2008 Fugitive Emissions Rule—was effective for only a short period of time between the Fugitive Emissions Rule's effective date of January 20, 2009, and when the first stay of the rule became effective on September 30, 2009.
                    </P>
                </FTNT>
                <P>
                    CAA section 302(j), as interpreted by the 
                    <E T="03">Alabama Power</E>
                     court, restricts the EPA's consideration of fugitive emissions in certain situations, requiring a rulemaking before the EPA can consider such emissions towards major stationary source thresholds. In extending this rulemaking requirement to major modifications, the 2008 rule focused largely on the fact that both CAA section 302(j) and the accompanying legislative history were silent with respect to the treatment of fugitive emissions for major modification purposes. The EPA concluded that CAA section 302(j) indicates congressional intent “to require a special look at fugitive emissions for purposes of calculating a source's emissions for NSR purposes.” 73 FR 77888 (December 19, 2008). This conclusion, while true to an extent, reflected an overbroad understanding of the “special look” required by CAA section 302(j), which is not specific to NSR 
                    <SU>36</SU>
                    <FTREF/>
                     and only explicitly addresses one aspect of the expansive NSR program (major source determinations).
                    <SU>37</SU>
                    <FTREF/>
                     Notwithstanding this “special look,” the EPA did 
                    <E T="03">not</E>
                     in 2008 interpret CAA section 302(j) as 
                    <E T="03">requiring</E>
                     the EPA to conduct rulemaking to identify source categories prior to including fugitive emissions in the major modification context. Instead, the EPA determined that the congressional silence gave the agency the discretion to “apply” the CAA section 302(j) methodology to major modifications.
                    <SU>38</SU>
                    <FTREF/>
                     Moreover, in the final Fugitive Emissions Rule in 2008, the EPA acknowledged that its prior interpretation remained a permissible construction of the Act (as the agency had previously asserted in 1989). 73 FR 77888; 
                    <E T="03">see</E>
                     54 FR 48883 (November 28, 1989).
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         For example, the definition of “major stationary source” in CAA section 302(j) is also implicated by the title V operating permits program. 
                        <E T="03">See, e.g.,</E>
                         42 U.S.C. 7661(2)(B).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         Most aspects of the NSR program treat fugitive and non-fugitive emissions similarly. 
                        <E T="03">See supra</E>
                         note 6 and accompanying text.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         
                        <E T="03">Compare</E>
                         73 FR 77889 (December 19, 2008) (final rule, described in text) 
                        <E T="03">with</E>
                         72 FR 63857 (November 13, 2007) (proposed rule, which had proposed to “conclude that it is reasonable to interpret section 302(j) to 
                        <E T="03">require</E>
                         EPA to conduct rulemaking to identify source categories that should include their fugitive emissions for all threshold applicability purposes.” (emphasis added)).
                    </P>
                </FTNT>
                <P>Moreover, the EPA's 2008 conclusion that Congress “simply did not know enough to make the critical decisions regarding the extent to which fugitive emissions should be included in threshold applicability determinations” for both major source and major modification determinations is undermined by the fact that Congress chose to explicitly provide special treatment of fugitive emissions in the relevant definition of major source, while declining to do so in the relevant definition of major modification. As the EPA first explained in 1984, because the special treatment of fugitive emissions in CAA section 302(j) “ran against the grain of longstanding practice[, i]f Congress had intended a change as to modifications, it probably would have said so explicitly, yet it said nothing.” 49 FR 43213 (October 26, 1984).</P>
                <P>
                    On its face, CAA section 302(j) only applies to determining what constitutes a “major stationary source.” CAA section 302(j) does not merely reference this concept, but literally 
                    <E T="03">defines</E>
                     this specific term (along with the interchangeable term, “major emitting facility”), and this term alone. Nothing in the definition of “major stationary source” in CAA section 302(j)—or its usage elsewhere in the NSR-relevant statutory provisions 
                    <SU>39</SU>
                    <FTREF/>
                    —suggests that its restriction on counting fugitive emissions was intended to be extended to other, distinct definitions or inquiries, such as the operative definition of “modification” in CAA section 111(a)(4). Rather than expand this principle to other contexts, the silence in CAA section 302(j) with 
                    <PRTPAGE P="62332"/>
                    respect to anything other than “major source” inquiries suggests Congress's intent to confine the fugitive emissions rulemaking requirement to major source determinations. The EPA's authority to apply a similar treatment in another, different context depends on the operative statutory provisions governing that context.
                    <SU>40</SU>
                    <FTREF/>
                     As discussed in the following paragraphs, in the context of determining whether a major modification has occurred, the EPA does not interpret CAA section 111(a)(4) as providing a basis for restricting consideration of fugitive emissions in such a manner.
                </P>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         The definitions of “major stationary source” (or “major emitting facility”) in CAA section 302(j) and “modification” in CAA section 111(a)(4) are related in that both are implicated by the statutory provisions governing NSR applicability. For example, CAA section 165 states that the “construction” of a “major emitting facility” triggers PSD, and “construction” is defined by CAA section 169 to include both new construction as well as modifications, as defined in section 111(a). 42 U.S.C. 7475(a), 7479(2)(C). However, the fact that PSD can be triggered either by the construction of a new major source or by the modification of a major source does not mean that the restrictions in defining what constitutes a major source also apply to determining whether a modification has occurred to such a major source. The distinction between these two concepts is apparent throughout the EPA's NSR regulations, which apply different rules to new major sources and modified major sources. And, while the definition of “major source” and the restrictions in CAA section 302(j) continue to be relevant to major modifications to a certain extent—since only existing major sources can undergo a major modification—this preliminary inquiry into whether an existing source is a major source is distinct from the inquiry of whether a change at such a source amounts to a major modification.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         Notably, the D.C. Circuit has emphasized the limited reach of CAA section 302(j) with respect to other areas of the CAA, such as the EPA's regulation of hazardous air pollutants under CAA section 112. 
                        <E T="03">See NMA</E>
                         v. 
                        <E T="03">EPA,</E>
                         59 F.3d 1351, 1360-61 (D.C. Cir. 1995).
                    </P>
                </FTNT>
                <P>
                    The EPA's 1984 and 1989 interpretations of the definition of “modification” in CAA section 111(a)(4) formed a central tenet of the agency's prior position that 
                    <E T="03">all</E>
                     emissions—both stack and fugitive—must be accounted for in the modification context. CAA section 111(a)(4) provides that “the term `modification' means any physical change in, or change in the method of operation of, a stationary source which increases the amount of any air pollutant emitted by such source or which results in the emissions of any air pollutant not previously emitted.” 42 U.S.C. 7411(a)(4).
                    <SU>41</SU>
                    <FTREF/>
                     As first stated in 1984, the EPA proposes to reaffirm in this rule that, in defining “modification” solely in terms of the total 
                    <E T="03">amount</E>
                     of pollution that a change would produce, Congress did not make a distinction between different types of emissions—stack or fugitive—in the context of modifications under the major NSR program. CAA section 111(a)(4)'s discussion of “any” physical or operational change, and its focus on increases in “any air pollutant,” further support this position. This is consistent with the EPA's historical interpretation of CAA section 111(a)(4) in other relevant contexts, namely the NSPS program. 
                    <E T="03">See, e.g.,</E>
                     49 FR 43213 (October 26, 1984).
                </P>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         The Fugitive Emissions Rule did not engage with this definition; instead, the EPA asserted simply that CAA section 111(a)(4) does not “address the issue.” Given that Congress was clearly able to provide special consideration for fugitive emissions in CAA section 302(j), the fact that CAA section 111(a)(4) does not specifically address fugitive emissions actually undercuts, rather than supports, the argument that fugitive emissions should be treated in a special way for purposes of determining whether a change is a major modification.
                    </P>
                </FTNT>
                <P>
                    This interpretation is also consistent with case law discussing the boundaries on the EPA's authority to establish exemptions to major NSR. As early as 1979, the 
                    <E T="03">Alabama Power</E>
                     court expressed skepticism of the EPA's authority to promulgate its initial 1978 exemption for fugitive dust—remanding that provision and providing extensive discussion of the limits on EPA's general exemption authority. 636 F.2d at 370; 
                    <E T="03">see id.</E>
                     at 357-61. More recently, as noted in NRDC's petition for reconsideration, the D.C. Circuit's 
                    <E T="03">New York I</E>
                     and 
                    <E T="03">New York II</E>
                     decisions further explored the EPA's limited ability to establish exemptions to the definition of “modification” in the context of major NSR. In 
                    <E T="03">New York I,</E>
                     the court “conclude[d] that the CAA unambiguously defines `increases' in terms of actual emissions,” explaining that the phrase “ `the 
                    <E T="03">amount</E>
                     of any air pollutant 
                    <E T="03">emitted</E>
                     by [the] source' [in CAA section 111(a)(4)] plainly refers to actual emissions.” 413 F.3d at 40. In 
                    <E T="03">New York II,</E>
                     the court stated the following: “Because Congress used the word `any,' EPA must apply NSR whenever a source conducts an emission-increasing activity that fits within one of the ordinary meanings of `physical change.' ” 443 F.3d at 885. Additionally, in vacating an exclusion from NSR applicability, the court concluded, “only physical changes that do not result in emission increases are excused from NSR.” 
                    <E T="03">Id.</E>
                     at 887. Thus, allowing certain sources to omit fugitive emissions in determining whether a change is a major modification would run counter to the D.C. Circuit's direction that modifications must account for all actual emissions increases from “any” physical change (
                    <E T="03">i.e.,</E>
                     not just changes that increase non-fugitive emissions), subject only to 
                    <E T="03">de minimis</E>
                     exceptions.
                </P>
                <P>In summary, for purposes of major NSR, the EPA proposes to affirm that CAA section 302(j) requires rulemaking before considering a source's fugitive emissions only in the major source context, and not in the major modification context. The EPA proposes to restore its longest-standing interpretation that CAA section 111(a)(4) requires that all major sources consider increases in all types of emissions (including fugitive emissions) in determining whether a proposed change would constitute a major modification.</P>
                <P>The EPA has considered the legal issues underlying the treatment of fugitive emissions in major modifications in multiple actions over the past 4 decades. During these prior actions, the EPA has also received and considered a substantial amount of feedback from stakeholders, upon which the conclusions in this proposal are based. However, the EPA solicits comment concerning the interpretation of CAA sections 302(j) and 111(a)(4) described in this section, in light of the authorities and considerations discussed in this Section. The EPA seeks comment on whether this interpretation supports repealing the 2008 Fugitive Emissions Rule, as well as removing the similar “major solely due to the inclusion of fugitive emissions” exemption first established in 1980.</P>
                <HD SOURCE="HD1">V. Policy Considerations and Impact on Regulated Entities</HD>
                <P>Through this proposal, the EPA seeks to realign its NSR regulations to better reflect the purpose of the NSR program and to end the regulatory uncertainty that has surrounded the EPA's treatment of fugitive emissions in the major modification context over the past four decades. The EPA expects any impacts of this proposed action on a limited subset of the regulated community to be manageable.</P>
                <HD SOURCE="HD2">A. Purposes of NSR</HD>
                <P>
                    The NSR program was designed to protect public health and welfare from the effects of air pollution and to preserve and/or improve air quality throughout the nation. 
                    <E T="03">See</E>
                     42 U.S.C. 7470(1), (2), (4). As the EPA has recognized since the early days of the NSR program, emissions deteriorate air quality regardless of how they emanate—whether stack or fugitive. 45 FR 52690 (August 7, 1980). Fugitive emissions in particular are more likely to have localized impacts on the air quality of communities located near these sources of pollution. The EPA welcomes comments from affected communities and other stakeholders on this topic and the broader air quality impacts of this rule.
                </P>
                <P>
                    Allowing large, existing sources of pollution to ignore increases in fugitive emissions when determining whether a project is a major modification, as the EPA did in its 2008 Fugitive Emissions Rule, could reduce the likelihood that projects would be subject to careful evaluation through the major NSR permitting process, notwithstanding significant increases in actual air pollution. This would undermine an important tool that the EPA and state and local air agencies use to preserve and improve air quality. Thus, the EPA's proposal seeks to preserve the ability to evaluate all increases of air pollution at existing major sources, regardless of origin, consistent with the purposes of NSR.
                    <PRTPAGE P="62333"/>
                </P>
                <HD SOURCE="HD2">B. Increasing Clarity</HD>
                <P>By removing outdated and conflicting provisions from the CFR and aligning the regulatory text with the EPA's stated interpretation, the agency seeks to restore clarity, certainty, and consistency to the regulations. The proposed approach reflects a more straightforward, simplified test for determining whether a change at an existing source is a major modification. Collectively, the EPA expects these changes to assist existing major sources to better understand the requirements that might be applicable to planned modifications, and to streamline the permitting process.</P>
                <P>
                    First, the proposed rule would eliminate uncertainty caused by the EPA's stay of the 2008 rule and the revisions to the regulatory text made in 2011 to effectuate the stay. Viewing the current text of the CFR, it is difficult to understand the proper treatment of fugitive emissions. The CFR is currently a patchwork of regulations that includes some of the paragraphs promulgated by the 2008 rule (which are stayed, although this may not be readily apparent from the paragraphs themselves) 
                    <SU>42</SU>
                    <FTREF/>
                     alongside reinstated paragraphs that predated, and conflict with, the stayed paragraphs from the 2008 rule. The proposed changes to remove the remaining stayed portions of the 2008 rule would restore much-needed clarity to the CFR.
                </P>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         The CFR notations indicating that these provisions are stayed are located at the end of each CFR section, relatively far from the stayed paragraphs themselves.
                    </P>
                </FTNT>
                <P>
                    Second, the proposed changes would eliminate uncertainty caused by inconsistencies between the EPA's longstanding interpretation of CAA sections 302(j) and 111(a)(4) and the 1980 exemption. As discussed in Section IV.A of this preamble, from 1989 through 2008, the EPA interpreted CAA sections 302(j) and 114(a)(4) to require all existing major sources to include fugitive emissions when determining whether a modification is major. Nonetheless, since 1980 (excepting a brief period in 2009), the NSR regulations have included an exemption allowing certain types of sources to avoid substantive major NSR requirements if a modification would be considered major solely due to the inclusion of fugitive emissions. The EPA's failure to remove this 1980 exemption in 1989 (and in subsequent actions) in light of the agency's interpretation has led to significant confusion for both permitting authorities and the regulated community. Additional confusion has resulted from the imprecise drafting of the 1980 exemption 
                    <SU>43</SU>
                    <FTREF/>
                     and the fact that this regulatory text reflects outdated applicability procedures.
                    <SU>44</SU>
                    <FTREF/>
                     The EPA expects that removing the 1980 exemption to align the regulations with the EPA's longstanding interpretation (which the EPA proposes to affirm in the current action) will further eliminate uncertainty.
                </P>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         
                        <E T="03">See supra</E>
                         note 10 and accompanying text.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         
                        <E T="03">See supra</E>
                         note 14 and accompanying text.
                    </P>
                </FTNT>
                <P>
                    The proposed changes provide a more straightforward method for accounting emissions increases and decreases in the context of modifications, which could potentially reduce the administrative burden for certain sources affected by these changes and for permitting authorities processing permit applications. Specifically, if the 2008 rule is repealed and the 1980 exemption is removed, major sources in non-listed categories would no longer have to distinguish between fugitive and non-fugitive emissions in determining whether a future modification is major. Removing this potentially complicated and contentious analytical step from the permitting process would provide greater certainty for sources contemplating modifications and ease the administrative burden for both sources and permitting authorities.
                    <SU>45</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         These changes would not impact previously issued permits, and would only apply to permits issued after the finalization of this rule or the approval of a SIP reflecting similar changes, depending on the permitting authority.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Previous Policy Considerations</HD>
                <P>
                    After reevaluating the policy and programmatic reasons that motivated the 2008 Fugitive Emissions Rule, the EPA no longer views these considerations as warranting the same approach. First, in the 2008 rule, the EPA suggested—without explanation—that it is better to adopt a uniform approach to major source and major modification determinations (that is, to allow the same sources to exclude fugitive emissions from both types of determinations). 73 FR 77888 (December 19, 2008). Upon reflection, the EPA sees little benefit in pursuing this type of “uniformity” for uniformity's sake. Most elements of the NSR program make no distinction between stack and fugitive emissions; the ability for non-listed sources to exclude fugitive emissions in initially determining whether they constitute a major source is the unique exception. At a certain point in the NSR applicability evaluation process, 
                    <E T="03">all</E>
                     sources (including those in non-listed categories) must account for 
                    <E T="03">all</E>
                     emissions (including fugitive emissions) in determining which substantive requirements apply.
                    <SU>46</SU>
                    <FTREF/>
                     Thus, “uniformity” in the treatment of fugitive emissions is ultimately illusory. The more pertinent issue is whether the EPA's approach to determining what constitutes a “major modification” should align more closely with the preliminary determination of whether a non-listed source is a “major source” (where fugitive emissions are excluded), or with consequent determinations concerning the application of substantive major NSR requirements to a major source or modification (where fugitive emissions are included). For the reasons presented in this section, the EPA believes the latter reflects better policy.
                    <SU>47</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         
                        <E T="03">See supra</E>
                         note 6 and accompanying text. Notably, the 2008 Fugitive Emissions Rule itself further codified this principle. 
                        <E T="03">See, e.g.,</E>
                         40 CFR 52.21(b)(20)(vii) (2009) (“For all other purposes of this section, fugitive emissions are treated in the same manner as other, non-fugitive emissions. This includes, but is not limited to, the treatment of fugitive emissions for the application of best available control technology (see paragraph (j) of this section), source impact analysis (see paragraph (k) of this section), additional impact analyses (see paragraph (o) of this section), and PALs (see paragraph (aa)(4)(i)(d) of this section).”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         The proposed approach also establishes “uniformity” in that all existing major sources are treated the same in the modification context, regardless of source type.
                    </P>
                </FTNT>
                <P>
                    The EPA also said in 2008 that its prior approaches had not adequately recognized the regulatory burden associated with requiring all sources to consider fugitive emissions in the major modification context. For support, the EPA explained: “our interpretation proposed in 1984 and finalized in 1989 imposed a new regulatory burden on major sources in a source category on the section 302(j) list, since their fugitive emissions would be counted in determining whether they had made a change constituting a major modification and thus possibly subjecting those modifications to NSR review.” 73 FR 77889 (December 19, 2008). While this was a concise summary of the potential effect of the EPA's pre-2008 interpretations (and the one proposed in the current action), this statement did not address or contradict the EPA's more extensive consideration and discussion of the same issue in the interpretive rule proposed in 1984 and finalized in 1989. In these prior documents, the EPA explained that few sources would likely be impacted by the interpretation. 
                    <E T="03">See</E>
                     54 FR 48882 (November 28, 1989). The following subsection addresses these potential impacts.
                    <PRTPAGE P="62334"/>
                </P>
                <HD SOURCE="HD2">D. Impacts on Regulated Entities</HD>
                <P>After reevaluating currently available information, the EPA expects that the proposed interpretation, and the resulting revocation of the 2008 Fugitive Emissions Rule and removal of the 1980 exemption will have a limited practical impact and result in limited increased burden for regulated entities, for the following reasons. First, revoking the 2008 Fugitive Emissions Rule should have almost no appreciable impact on the status quo, given that the 2008 rule has been stayed (in some form) since September 2009 (less than a year after becoming effective).</P>
                <P>
                    Second, removing the 1980 exemption from the regulations should also have a limited impact. To the EPA's knowledge, the exemption has generally not been relied on by sources, and the population of sources that could invoke the exemption is limited. The changes proposed in this rule would only impact sources that do not belong to a listed source category (as listed sources have to include fugitive emissions for major modification purposes under any scenario). More importantly, it would only impact those non-listed sources that are already considered existing major stationary sources (as major modifications can only occur at existing major sources).
                    <SU>48</SU>
                    <FTREF/>
                     Given that non-listed sources do not count fugitive emissions towards major source thresholds, the EPA understands the universe of such sources to be relatively small, particularly for sources of predominantly fugitive emissions that might be most concerned with the EPA's proposed changes. As explained in the EPA's 1989 interpretive rule, the EPA expects that major NSR applicability for sources of predominantly fugitive emissions would, in most situations, be attributable to other existing EPA regulations and policies—such as those defining the scope of a stationary source—and not to the EPA's interpretation of CAA section 302(j) with respect to modifications. 
                    <E T="03">See</E>
                     54 FR 48883 (November 28, 1989); 
                    <E T="03">see also</E>
                     51 FR 7092 (February 28, 1986). Non-listed sources with large quantities of non-fugitive (stack) emissions are more likely to be considered major sources, and thus could be impacted by this rule. However, the likelihood that such a source (with large amounts of non-fugitive emissions) would undertake a modification that would be major solely due to consideration of the source's fugitive emissions seems remote. In any case, as described in the following paragraphs, the EPA expects that any entities that are affected are likely well-positioned to handle the additional obligations of major NSR review.
                </P>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         Although physical changes to existing non-major sources could trigger major NSR if the physical change itself exceeded major source thresholds, this would not be considered a “major modification,” but rather, a new “major source.” 
                        <E T="03">See, e.g.,</E>
                         40 CFR 52.21(b)(1)(i)(
                        <E T="03">c</E>
                        ). Thus, consideration of fugitive emissions in this context would be governed by the EPA's long-standing regulations governing the treatment of fugitive emissions in major source determinations, and non-listed sources would not count fugitive emissions towards the threshold.
                    </P>
                </FTNT>
                <P>
                    The policy considerations that may have motivated Congress to enact CAA section 302(j), and which motivated the EPA's listing of certain source categories but not others in its definition of “major source,” are already effectively accomplished by allowing sources in non-listed categories to exclude fugitive emissions when determining whether they constitute a “major source.” As discussed in Section IV of this preamble, the sparse legislative history does not express a clear purpose for the treatment of fugitive emissions in CAA section 302(j). However, as the 
                    <E T="03">Alabama Power</E>
                     court suggested, CAA section 302(j) “may well define a legislative response to the policy considerations presented by the regulation of sources where the predominant emissions are fugitive in origin, particularly fugitive dust.” 636 F.2d at 369. The court also noted that the provision “gives EPA flexibility to provide industry-by-industry consideration and appropriate tailoring of coverage.” 
                    <E T="03">Id.</E>
                     The EPA believes that the industry-specific coverage afforded by allowing sources in non-listed source categories to omit fugitive emissions in determining whether they are a “major source” is sufficient coverage for NSR purposes. As noted in the preceding paragraph, by omitting fugitive emissions in determining whether a non-listed source is a major source, this significantly reduces the possibility that such a source of predominantly fugitive emissions would be considered major, accordingly limiting the possibility that future modifications at such a source would trigger major source NSR.
                </P>
                <P>
                    To the extent that any sources are impacted by this rule, such sources will, by definition, be existing major stationary sources. In the specific context at issue here, these sources are likely to be large, relatively well-resourced operations, given that their emissions will necessarily generally exceed 250 tons per year for at least one pollutant 
                    <E T="03">even before considering fugitive emissions.</E>
                     Thus, although these major sources do not belong to a listed source category, they nonetheless represent the type of “facilities, which, due to their size, are financially able to bear the substantial regulatory costs imposed by the PSD provisions and which . . . are primarily responsible for emissions of the deleterious pollutants that befoul our nation's air.” 
                    <SU>49</SU>
                    <FTREF/>
                     If these facilities were constructed anew, they would be subject to the major NSR program (and, presumably, many if not most of these sources have already been through the major NSR permitting process). These sources should be familiar with the NSR program and able to manage any additional obligations imposed by this proposed regulatory change.
                </P>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         
                        <E T="03">Alabama Power,</E>
                         636 F.2d at 353 (explaining Congress's intention in establishing the definition of “major emitting facility” and “major stationary source” for PSD purposes in CAA section 169(1)). As the court stated, “the Act does not give the agency a free hand authority to grant broad exemptions. Though the costs of compliance with section 165 [PSD] requirements are substantial, they can reasonably be borne by facilities that actually emit, or would actually emit when operating at full capacity, the large tonnage thresholds [for major stationary sources] specified in section 169(1).” 
                        <E T="03">Id.</E>
                         at 354.
                    </P>
                </FTNT>
                <P>Accordingly, in light of these policy considerations and the legal constraints discussed in Section IV.C of this preamble, the EPA does not consider it necessary or prudent to extend a second, additional exemption to these existing major sources that are contemplating modifications, as the EPA did in the Fugitive Emissions Rule. Doing so would unnecessarily render future modifications less likely to trigger major NSR review, even in cases where a modification would significantly increase actual air pollution, frustrating the ultimate goals of the major NSR program (as discussed in Section V.A of this preamble). Overall, the EPA believes the interpretation and regulatory approach proposed in the current action strikes the appropriate balance to protect air quality while ensuring “that economic growth will occur in a manner consistent with the preservation of existing clean air resources.” 42 U.S.C. 7470(3).</P>
                <P>
                    The EPA's proposed conclusions regarding the limited potential impact of this action are based on the agency's experience over the past 4 decades as well as feedback received from stakeholders on prior actions. However, the EPA solicits additional comments from stakeholders on the practical impact of the proposed action, including the scope of overall programmatic impacts (
                    <E T="03">e.g.,</E>
                     how many sources might be affected). Specifically, the EPA seeks information on the types and numbers of existing major sources that do not belong to a listed source category and that have predominantly fugitive emissions, or which might otherwise be affected by this rule. As 
                    <PRTPAGE P="62335"/>
                    noted in the previous paragraphs, the EPA expects the number of such sources to be relatively small, but the EPA would welcome more quantitative information on this topic. Relatedly, the EPA solicits information about specific real-world or hypothetical examples of situations where a particular type of source might be affected by the proposed changes (
                    <E T="03">e.g.,</E>
                     how the changes might impact a regulated entity's behavior in considering whether to undertake a modification).
                </P>
                <HD SOURCE="HD1">VI. SIP Minimum Program Elements</HD>
                <P>
                    If the EPA affirms the interpretation of CAA sections 302(j) and 111(a)(4) discussed in Section IV.C of this preamble—
                    <E T="03">i.e.,</E>
                     that all existing major sources must account for fugitive emissions in determining whether a modification is major—the EPA proposes that the changes to the EPA regulations reflected in this rule would also be minimum program elements for SIPs. If this rule is finalized as proposed, it is likely that any SIPs containing an exemption for fugitive emissions in the major modification context will be less stringent than the minimum program elements specified in the EPA's regulations and would therefore need to be revised. The scope of necessary SIP revisions would be a case-specific inquiry and would depend on the nature of any final changes to the EPA's regulations as well as the nature of existing SIP provisions. Based on a preliminary review of existing EPA-approved SIPs, the EPA observes that very few state or local agencies have EPA-approved SIP provisions based on, or incorporating, the 2008 Fugitive Emissions Rule. This makes sense considering that the EPA stayed and amended the 2008 rule shortly after it became effective, leaving a relatively small window of time for states to adopt revisions based on the 2008 rule. However, the EPA understands that significantly more SIPs contain provisions based on, or incorporating, the 1980 exemption (as recodified in the 2002 NSR Reform Rule). Accordingly, if the EPA finalizes a rule that not only repeals the 2008 rule, but also removes the 1980 exemption from the EPA's regulations, a larger number of permitting authorities may be required to submit SIP revisions. If the EPA determines that conforming SIP revisions are necessary, states would be required to submit SIP revisions no later than three years after the final rule amending the EPA's regulations publishes in the 
                    <E T="04">Federal Register</E>
                    . 40 CFR 51.166(a)(6)(i). The EPA is soliciting comment on the need to establish the proposed changes as minimum program elements and the consequent potential for SIP revisions.
                </P>
                <HD SOURCE="HD1">VII. Definition of “Fugitive Emissions”</HD>
                <P>
                    Fugitive emissions, for purposes of both the NSR and title V permitting programs, are defined as “emissions which could not reasonably pass through a stack, chimney, vent, or other functionally equivalent opening.” 
                    <E T="03">E.g.,</E>
                     40 CFR 52.21(b)(20), 70.2. The 2008 Fugitive Emissions Rule did not change this regulatory definition, but the preamble to that rule did include a discussion of “guiding principles” based on the EPA's interpretation of this regulatory definition. 
                    <E T="03">See</E>
                     73 FR 77891 (December 19, 2008). Most of the principles articulated in the 2008 preamble simply restated or summarized prior EPA letters and memoranda expressing the EPA's interpretations and policies on the issue.
                    <SU>50</SU>
                    <FTREF/>
                     The EPA continues to follow its interpretations and policies concerning the definition of “fugitive emissions” that predated the 2008 rule, including those that were restated and summarized in the 2008 rule preamble. These positions were not affected by the 2008 rule or the stays of the 2008 rule. The EPA is providing the following summary of these interpretations and policies in order to provide clarity and certainty about how EPA intends to approach these issues.
                </P>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         For examples of these prior guidance documents, please see the EPA's online NSR and title V guidance databases, each of which include a topic page containing guidance related specifically to fugitive emissions: 
                        <E T="03">https://www.epa.gov/nsr/new-source-review-policy-and-guidance-document-index</E>
                         and 
                        <E T="03">https://www.epa.gov/title-v-operating-permits/title-v-operating-permit-policy-and-guidance-document-index.</E>
                    </P>
                </FTNT>
                <P>
                    Determining whether certain emissions are fugitive or non-fugitive at a particular source is inherently a fact-specific inquiry. All emissions which do actually pass through a stack, chimney, vent, or other functionally equivalent opening at a facility are non-fugitive. If emissions do not currently pass through such an opening, then one must evaluate whether such emissions could reasonably pass.
                    <SU>51</SU>
                    <FTREF/>
                     The EPA interprets the phrase “reasonably pass” by determining whether emissions could reasonably be collected or captured and discharged through a stack, chimney, vent, or functionally equivalent opening. Various criteria guide this case-by-case analysis, and no single criterion should be considered determinative. Relevant considerations include whether and to what extent similar facilities collect or capture similar emissions (including how common this practice is, and whether the EPA has established a national emissions standard or regulation that requires some sources in the source category to collect or capture the emissions) and the technical and economic feasibility (
                    <E T="03">e.g.,</E>
                     cost) of collecting or capturing the emissions.
                </P>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         When the EPA finalized the definition of “fugitive emissions” in the 1980 PSD rulemaking to include the words “reasonably pass,” the agency explained that it did so in order to narrow the proposed definition of fugitive emissions to exclude not only those emissions that currently do pass through a stack, chimney, vent, or functionally equivalent opening, but also to those that do not currently pass but which could reasonably be made to pass through such an opening. The EPA explained: “This change will ensure that sources will not discharge as fugitive emissions those emissions which would ordinarily be collected and discharged through stacks or other functionally equivalent openings, and will eliminate disincentives for the construction of ductwork and stacks for the collection of emissions.” 45 FR 52693 (August 7, 1980).
                    </P>
                </FTNT>
                <P>
                    In addition to outlining these longstanding interpretations and policies, the preamble to the 2008 Fugitive Emissions Rule also expanded some of the factors that permitting authorities may consider when assessing whether certain emissions are fugitive or non-fugitive. Notably, the EPA said for the first time in the 2008 preamble that permitting authorities could consider the cost of 
                    <E T="03">controlling</E>
                     emissions when determining whether such emissions “could not reasonably pass” and accordingly whether such emissions should be considered fugitive or non-fugitive. The EPA understands that the stay of the 2008 rule left a question of whether EPA continued to support considering the cost of control in identifying whether emissions are fugitive. The EPA intended the initial 2009 stay (and all subsequent stays) of the 2008 Fugitive Emissions Rule to apply to the entire rulemaking effort, including the discussion of the definition of “fugitive emissions” contained within the rule's preamble. Thus, the EPA statements regarding the cost of control were also stayed and were not applied by EPA thereafter. Likewise, these statements regarding cost of control do not reflect the EPA's current thinking and should not be relied upon by states or sources in making permitting decisions. Instead, the EPA continues to apply the longstanding interpretations and policies that predated the 2008 rule, as summarized in the preceding paragraphs.
                </P>
                <P>
                    Although the EPA does not propose in this action to revise its longstanding approach for evaluating this issue, the EPA welcomes public comment on how to interpret and apply the definition of “fugitive emissions” in the NSR and 
                    <PRTPAGE P="62336"/>
                    title V regulations. To the extent that the EPA seeks to provide additional guidance on applying the definition of “fugitive emissions” in the future, any such guidance may be provided alongside, or separate from, any final action in this rulemaking concerning the treatment of fugitive emissions for major modifications. In the meantime, the EPA will continue to be responsive to case-specific inquiries from permitting authorities and regulated entities requesting the EPA's views on whether certain emissions should be considered fugitive or non-fugitive.
                </P>
                <HD SOURCE="HD1">VIII. Environmental Justice Considerations</HD>
                <P>The proposed changes are not expected to have any effect or increased burden on communities with environmental justice concerns. Although the impact of this proposal is expected to be limited, requiring all existing major sources to include fugitive emissions in determining whether a change constitutes a major modification could potentially result in more projects subject to major NSR and installing pollution controls, improving the air quality for all communities, particularly those located near major sources with a large proportion of fugitive emissions.</P>
                <HD SOURCE="HD1">IX. Statutory and Executive Order Reviews</HD>
                <P>
                    Additional information about these statutes and Executive Orders can be found at 
                    <E T="03">https://www.epa.gov/laws-regulations/laws-and-executive-orders.</E>
                </P>
                <HD SOURCE="HD2">A. Executive Order 12866: Regulatory Planning and Review and Executive Order 13563: Improving Regulation and Regulatory Review</HD>
                <P>This action is a significant regulatory action that was submitted to the Office of Management and Budget (OMB) for review. Pursuant to E.O. 12866, the EPA has assessed the potential costs and benefits of this regulatory action. EPA believes the rule will have a limited practical impact and result in limited increased burden for regulated entities, as discussed in Section V.D. Any changes made in response to OMB recommendations have been documented in the docket.</P>
                <HD SOURCE="HD2">B. Paperwork Reduction Act (PRA)</HD>
                <P>This action does not impose any new information collection burden under the PRA. OMB has previously approved the information collection activities contained in the existing regulations and has assigned OMB control numbers 2060-0003 for the PSD and NNSR permit programs. The burden associated with obtaining an NSR permit for a major stationary source undergoing a major modification is already accounted for under the approved information collection requests. A federal agency may not conduct or sponsor, and a person is not required to respond to, nor shall a person be subject to a penalty for failure to comply with, a collection of information subject to the requirements of the PRA unless that collection of information displays a currently valid OMB control number.</P>
                <HD SOURCE="HD2">C. Regulatory Flexibility Act (RFA)</HD>
                <P>I certify that this action will not have a significant economic impact on a substantial number of small entities under the RFA. This action will not impose any requirements on small entities. In general, major stationary sources undergoing major modifications are not small entities, as discussed in Section V of this preamble. State and local air agencies that could be affected by this rule do not qualify as small entities under the RFA.</P>
                <HD SOURCE="HD2">D. Unfunded Mandates Reform Act (UMRA)</HD>
                <P>This action does not contain an unfunded federal mandate as described in UMRA, 2 U.S.C. 1531-1538, and does not significantly or uniquely affect small governments. This action imposes no enforceable duty on any state, local or tribal governments or the private sector. Nonetheless, if this rule is finalized as proposed, it is possible that some state and local air agencies will need to submit a small, one-time revision to their SIP. However, the rule could ultimately reduce regulatory impacts for these state and local agencies (and potentially affected sources) because they would no longer have to expend resources differentiating between fugitive and non-fugitive emissions when assessing whether a project constitutes a major modification.</P>
                <HD SOURCE="HD2">E. Executive Order 13132: Federalism</HD>
                <P>This action does not have federalism implications. It will not have substantial direct effects on the states, on the relationship between the national government and the states, or on the distribution of power and responsibilities among the various levels of government.</P>
                <HD SOURCE="HD2">F. Executive Order 13175: Consultation and Coordination With Indian Tribal Governments</HD>
                <P>This action does not have tribal implications as specified in Executive Order 13175. The EPA is currently the reviewing authority for PSD and NNSR permits issued in tribal lands and, as such, the revisions being proposed will not impose direct burdens on tribal authorities. Thus, Executive Order 13175 does not apply to this action.</P>
                <HD SOURCE="HD2">G. Executive Order 13045: Protection of Children From Environmental Health and Safety Risks</HD>
                <P>The EPA interprets Executive Order 13045 as applying only to those regulatory actions that concern environmental health or safety risks that the EPA has reason to believe may disproportionately affect children, per the definition of “covered regulatory action” in section 2-202 of the Executive Order. This action is not subject to Executive Order 13045 because it does not concern an environmental health risk or safety risk.</P>
                <HD SOURCE="HD2">H. Executive Order 13211: Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use</HD>
                <P>
                    This action is not a “significant energy action” because it is not likely to have a significant adverse effect on the supply, distribution or use of energy. Industries directly involved in energy production (
                    <E T="03">e.g.,</E>
                     fossil fuel-fired power plants) will not be affected by this rule because they belong to a listed source category, and this rule only pertains to sources in non-listed source categories. As discussed in Section V of this preamble, the EPA considers it unlikely that this rule would affect other industries involved in energy supply that do not belong to a listed source category (
                    <E T="03">e.g.,</E>
                     surface coal mining).
                </P>
                <HD SOURCE="HD2">I. National Technology Transfer and Advancement Act (NTTA)</HD>
                <P>This rulemaking does not involve technical standards.</P>
                <HD SOURCE="HD2">J. Executive Order 12898: Federal Actions To Address Environmental Justice in Minority Populations and Low-Income Populations</HD>
                <P>The EPA believes that this action does not have disproportionately high and adverse human health or environmental effects on minority populations, low-income populations and/or indigenous peoples, as specified in Executive Order 12898 (59 FR 7629, February 16, 1994). The basis for this decision is contained in Section VIII of this preamble.</P>
                <HD SOURCE="HD1">X. Statutory Authority</HD>
                <P>
                    The statutory authority for this action is provided by 42 U.S.C. 7401 
                    <E T="03">et seq.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>40 CFR Part 51</CFR>
                    <P>
                        Environmental protection, Administrative practice and procedure, 
                        <PRTPAGE P="62337"/>
                        Air pollution control, Carbon monoxide, Fees, Intergovernmental relations, Lead, Nitrogen oxides, Ozone, Reporting and recordkeeping requirements, Sulfur oxides, Transportation, Volatile organic compounds.
                    </P>
                    <CFR>40 CFR Part 52</CFR>
                    <P>Environmental protection, Administrative practice and procedure, Air pollution control, Ammonia, Carbon monoxide, Greenhouse gases, Intergovernmental relations, Lead, Nitrogen dioxide, Nitrogen oxides, Ozone, Reporting and recordkeeping requirements, Sulfur dioxide, Sulfur oxides, Volatile organic compounds.</P>
                </LSTSUB>
                <SIG>
                    <NAME>Michael S. Regan,</NAME>
                    <TITLE>Administrator.</TITLE>
                </SIG>
                <P>For the reasons stated in the preamble, title 40, chapter I of the Code of Federal Regulations is proposed to be amended as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 51—REQUIREMENTS FOR PREPARATION, ADOPTION, AND SUBMITTAL OF IMPLEMENTATION PLANS</HD>
                </PART>
                <AMDPAR>1. The authority citation for part 51 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>23 U.S.C. 101; 42 U.S.C. 7401-7671q.</P>
                </AUTH>
                <SECTION>
                    <SECTNO>§ 51.165</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <AMDPAR>2. Amend § 51.165 by:</AMDPAR>
                <AMDPAR>
                    a. Lifting the stay on paragraphs (a)(1)(v)(G) and (a)(1)(vi)(C)(
                    <E T="03">3</E>
                    );
                </AMDPAR>
                <AMDPAR>
                    b. Removing paragraphs (a)(1)(v)(G) and (a)(1)(vi)(C)(
                    <E T="03">3</E>
                    ); and
                </AMDPAR>
                <AMDPAR>c. Removing and reserving paragraph (a)(4).</AMDPAR>
                <SECTION>
                    <SECTNO>§ 51.166</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <AMDPAR>3. Amend § 51.166 by:</AMDPAR>
                <AMDPAR>
                    a. Lifting the stay on paragraphs (b)(2)(v) and (b)(3)(iii)(
                    <E T="03">d</E>
                    );
                </AMDPAR>
                <AMDPAR>
                    b. Removing paragraphs (b)(2)(v) and (b)(3)(iii)(
                    <E T="03">d</E>
                    ); and
                </AMDPAR>
                <AMDPAR>c. Removing and reserving paragraph (i)(1)(ii).</AMDPAR>
                <HD SOURCE="HD1">Appendix S to Part 51 [Amended]</HD>
                <AMDPAR>4. Amend appendix S to part 51 by:</AMDPAR>
                <AMDPAR>a. Lifting the stay on paragraph II.A.5(vii);</AMDPAR>
                <AMDPAR>b. Removing paragraph II.A.5(vii); and</AMDPAR>
                <AMDPAR>c. Removing and reserving paragraph II.F.</AMDPAR>
                <PART>
                    <HD SOURCE="HED">PART 52—APPROVAL AND PROMULGATION OF IMPLEMENTATION PLANS</HD>
                </PART>
                <AMDPAR>5. The authority citation for part 52 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>
                        42 U.S.C. 7401 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SECTION>
                    <SECTNO>§ 52.21</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <AMDPAR>6. Amend § 52.21 by:</AMDPAR>
                <AMDPAR>
                    a. Lifting the stay on paragraphs (b)(2)(v) and (b)(3)(iii)(
                    <E T="03">c</E>
                    );
                </AMDPAR>
                <AMDPAR>
                    b. Removing paragraphs (b)(2)(v) and (b)(3)(iii)(
                    <E T="03">c</E>
                    ); and
                </AMDPAR>
                <AMDPAR>c. Removing and reserving paragraph (i)(1)(vii).</AMDPAR>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22259 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <CFR>40 CFR Part 52</CFR>
                <DEPDOC>[EPA-R09-OAR-2022-0503; FRL-9936-01-R9]</DEPDOC>
                <SUBJECT>Air Plan Approval; California; Innovative Clean Transit Regulation</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Environmental Protection Agency (EPA) is proposing to approve a revision to the California State Implementation Plan (SIP) concerning particulate matter (PM) and oxides of nitrogen (NO
                        <E T="52">X</E>
                        ) emissions from public transit buses. We are proposing to approve State rules that regulate these emission sources under the Clean Air Act (CAA or the Act). We are taking comments on this proposal and plan to follow with a final action.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before November 14, 2022.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit your comments, identified by Docket ID No. EPA-R09-OAR-2022-0503 at 
                        <E T="03">https://www.regulations.gov.</E>
                         For comments submitted at 
                        <E T="03">Regulations.gov</E>
                        , follow the online instructions for submitting comments. Once submitted, comments cannot be edited or removed from 
                        <E T="03">Regulations.gov</E>
                        . The EPA may publish any comment received to its public docket. Do not submit electronically any information you consider to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Multimedia submissions (audio, video, etc.) must be accompanied by a written comment. The written comment is considered the official comment and should include discussion of all points you wish to make. The EPA will generally not consider comments or comment contents located outside of the primary submission (
                        <E T="03">i.e.,</E>
                         on the web, cloud, or other file sharing system). For additional submission methods, please contact the person identified in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section. For the full EPA public comment policy, information about CBI or multimedia submissions, and general guidance on making effective comments, please visit 
                        <E T="03">https://www.epa.gov/dockets/commenting-epa-dockets.</E>
                         If you need assistance in a language other than English or if you are a person with disabilities who needs a reasonable accommodation at no cost to you, please contact the person identified in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jeffrey Buss, EPA Region IX, 75 Hawthorne St., San Francisco, CA 94105. By phone: (415) 947-4152 or by email at 
                        <E T="03">buss.jeffrey@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Throughout this document, “we,” “us” and “our” refer to the EPA.</P>
                <HD SOURCE="HD1">Table of Contents</HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. The State's Submission</FP>
                    <FP SOURCE="FP1-2">A. What rules did the State submit?</FP>
                    <FP SOURCE="FP1-2">B. Are there other versions of these rules?</FP>
                    <FP SOURCE="FP1-2">C. What is the purpose of the submitted rules?</FP>
                    <FP SOURCE="FP1-2">D. What requirements does the regulation establish?</FP>
                    <FP SOURCE="FP-2">II. The EPA's Evaluation and Action</FP>
                    <FP SOURCE="FP1-2">A. How is the EPA evaluating the regulation?</FP>
                    <FP SOURCE="FP1-2">B. Does the regulation meet the evaluation criteria?</FP>
                    <FP SOURCE="FP1-2">C. The EPA's Recommendations To Further Improve the Rules</FP>
                    <FP SOURCE="FP1-2">D. Public Comment and Proposed Action</FP>
                    <FP SOURCE="FP-2">III. Incorporation by Reference</FP>
                    <FP SOURCE="FP-2">IV. Statutory and Executive Order Reviews</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. The State's Submission</HD>
                <HD SOURCE="HD2">A. What rules did the State submit?</HD>
                <P>
                    On December 14, 2018, the California Air Resources Board (CARB) adopted a set of rules referred to as the Innovative Clean Transit (ICT) regulation. On August 13, 2019, the California Office of Administrative Law (OAL) approved the ICT regulation, effective October 1, 2019. On February 13, 2020, CARB submitted the ICT regulation to the EPA as a revision to the California SIP.
                    <SU>1</SU>
                    <FTREF/>
                     Table 1 lists the specific sections of Title 13, Division 3, Chapter 1, Article 4.3 of the California Code of Regulations (CCR) that comprise the ICT regulation.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         CARB submitted the ICT Regulation electronically to the EPA on February 13, 2020 as an attachment to a letter dated February 12, 2020.
                    </P>
                </FTNT>
                <PRTPAGE P="62338"/>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="xs60,xs60,r50,12,12">
                    <TTITLE>Table 1—Submitted Rules</TTITLE>
                    <BOXHD>
                        <CHED H="1">Agency</CHED>
                        <CHED H="1">Section No. 13 CCR</CHED>
                        <CHED H="1">Rule title</CHED>
                        <CHED H="1">
                            State
                            <LI>effective date</LI>
                        </CHED>
                        <CHED H="1">Submission date</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>2023</ENT>
                        <ENT>Innovative Clean Transit Regulations Applicability and Scope</ENT>
                        <ENT>10/01/2019</ENT>
                        <ENT>02/13/2020</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>2023.1</ENT>
                        <ENT>Zero-Emission Bus Requirements</ENT>
                        <ENT>10/01/2019</ENT>
                        <ENT>02/13/2020</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>2023.2</ENT>
                        <ENT>Compliance Option for Joint Zero-Emission Bus Groups</ENT>
                        <ENT>10/01/2019</ENT>
                        <ENT>02/13/2020</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>2023.3</ENT>
                        <ENT>Zero-Emission Bus Bonus Credits</ENT>
                        <ENT>10/01/2019</ENT>
                        <ENT>02/13/2020</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>2023.4</ENT>
                        <ENT>Provisions for Exemption of a Zero-Emission Bus Purchase</ENT>
                        <ENT>10/01/2019</ENT>
                        <ENT>02/13/2020</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>2023.5</ENT>
                        <ENT>Zero-Emission Mobility Option</ENT>
                        <ENT>10/01/2019</ENT>
                        <ENT>02/13/2020</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>2023.6</ENT>
                        <ENT>
                            Low-NO
                            <E T="0732">X</E>
                             Engine Purchase Requirements
                        </ENT>
                        <ENT>10/01/2019</ENT>
                        <ENT>02/13/2020</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>2023.7</ENT>
                        <ENT>Requirements to Use Renewable Fuels</ENT>
                        <ENT>10/01/2019</ENT>
                        <ENT>02/13/2020</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>2023.8</ENT>
                        <ENT>Reporting Requirements for Transit Agencies</ENT>
                        <ENT>10/01/2019</ENT>
                        <ENT>02/13/2020</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>2023.9</ENT>
                        <ENT>Record Keeping Requirements</ENT>
                        <ENT>10/01/2019</ENT>
                        <ENT>02/13/2020</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>2023.10</ENT>
                        <ENT>Authority to Suspend, Revoke or Modify</ENT>
                        <ENT>10/01/2019</ENT>
                        <ENT>02/13/2020</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>2023.11</ENT>
                        <ENT>Severability</ENT>
                        <ENT>10/01/2019</ENT>
                        <ENT>02/13/2020</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    In addition to the Final Regulation Order and documentation of OAL approval, CARB's February 13, 2020 SIP submission includes CARB Staff Report: Initial Statement of Reasons (August 7, 2018) and related appendices; the Notice of Public Hearing, dated July 24, 2018, for a hearing on September 27, 2018; CARB Resolution 18-60 (December 14, 2018) through which CARB adopted the ICT regulation; and the Final Statement of Reasons (June 2019) and related appendices. On August 13, 2019, the submission from CARB was deemed by operation of law to meet the completeness criteria in 40 CFR part 51, appendix V.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         CAA section 110(k)(1)(B).
                    </P>
                </FTNT>
                <P>
                    On August 11, 2022, CARB supplemented the February 13, 2020 SIP submission.
                    <SU>3</SU>
                    <FTREF/>
                     The August 11, 2022 supplement includes certain additional definitions codifed in the CCR or California Health &amp; Safety Code (CH&amp;SC) that are relied upon in the ICT regulation. The specific definitions submitted on August 11, 2022 are listed in table 2.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Shirin Barfjani, Air Pollution Specialist, CARB, email correspondence to Jeffrey Buss, EPA Region 9, August 11, 2022.
                    </P>
                </FTNT>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="xs60,r25,r50,12">
                    <TTITLE>Table 2—Submitted Additional Definitions Relied Upon by the ICT Regulation</TTITLE>
                    <BOXHD>
                        <CHED H="1">Agency</CHED>
                        <CHED H="1">CCR, CH&amp;SC or CVC section</CHED>
                        <CHED H="1">Title</CHED>
                        <CHED H="1">
                            State
                            <LI>effective date</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>CH&amp;SC 39012</ENT>
                        <ENT>Air Basin</ENT>
                        <ENT>01/01/1976</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>17 CCR 95481(a)(30)</ENT>
                        <ENT>Untitled but defines the term “compressed natural gas (CNG)”</ENT>
                        <ENT>07/01/2020</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>13 CCR 2208(c)(18)</ENT>
                        <ENT>
                            Untitled but defines the term “Low-NO
                            <E T="0732">X</E>
                             engine”
                        </ENT>
                        <ENT>10/16/2017</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>17 CCR 60100(e)</ENT>
                        <ENT>Untitled but defines the Sonoma County portion of the North Coast Basin</ENT>
                        <ENT>07/05/1978</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>17 CCR 60013</ENT>
                        <ENT>Lake Tahoe Air Basin</ENT>
                        <ENT>01/30/1976</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>17 CCR 95481(a)(130)</ENT>
                        <ENT>Untitled but defines the term “Renewable hydrocarbon diesel”</ENT>
                        <ENT>07/01/2020</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>17 CCR 95481(a)(22)</ENT>
                        <ENT>Untitled but defines the term “Biomethane”</ENT>
                        <ENT>07/01/2020</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARB</ENT>
                        <ENT>13 CCR 2020(b)</ENT>
                        <ENT>Definitions</ENT>
                        <ENT>01/02/2010</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD2">B. Are there other versions of these rules?</HD>
                <P>The ICT regulation replaces an earlier CARB regulation referred to as the Fleet Rule for Transit Agencies. CARB originally adopted the Fleet Rule for Transit Agencies in 2000, and amended the rule in 2004 and 2006. The Fleet Rule for Transit Agencies was never submitted or approved as part of the California SIP.</P>
                <HD SOURCE="HD2">C. What is the purpose of the submitted rules?</HD>
                <P>
                    Emissions of PM, including PM equal to or less than 2.5 microns in diameter (PM
                    <E T="52">2.5</E>
                    ) and PM equal to or less than 10 microns in diameter (PM
                    <E T="52">10</E>
                    ), contribute to effects that are harmful to human health and the environment, including premature mortality, aggravation of respiratory and cardiovascular disease, decreased lung function, visibility impairment, and damage to vegetation and ecosystems. Additionally, emissions of NO
                    <E T="52">X</E>
                     contribute to the production of ground-level ozone, which harms human health and the environment. Section 110(a) of the CAA requires states to submit regulations that control PM and NO
                    <E T="52">X</E>
                     emissions.
                </P>
                <P>
                    The purpose of the ICT regulation is to transition California public transit bus fleets to zero-emission technologies by 2040. The ICT regulation was developed to ensure transit service integrity and program feasibility through this transformation. The ICT regulation was included as one of the regulatory measures adopted by CARB in the 2016 State SIP Strategy to achieve emissions reductions of NO
                    <E T="52">X</E>
                     and PM emissions needed to attain the National Ambient Air Quality Standard (NAAQS), particularly in the South Coast and San Joaquin Valley air quality planning areas.
                    <SU>4</SU>
                    <FTREF/>
                     Furthermore, CARB notes that the ICT regulation furthers state environmental justice goals by transitioning to clean transportation modes in low-income and disadvantaged communities.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         CARB, Revised Proposed 2016 State Strategy for the State Implementation Plan, March 7, 2017, pages 69-71. The EPA approved the 2016 State SIP Strategy as a revision to the California SIP at February 12, 2019, 84 FR 3302; corrected at May 3, 2019, 84 FR 19680; and at October 1, 2019, 84 FR 52005.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         CARB; Public Hearing to Consider the Proposed Innovative Clean Transit Regulation, a Replacement of the Fleet Rule for Public Agencies; Staff Report: Initial Statement of Reasons; Date of Release: August 7, 2018 (“CARB's ICT Staff Report”); chapter 7 (“Environmental Justice”).
                    </P>
                </FTNT>
                <P>
                    As adopted, CARB estimates that the ICT regulation will reduce NO
                    <E T="52">X</E>
                     and PM emissions by approximately 7,032 and 39.4 tons, respectively, on a statewide 
                    <PRTPAGE P="62339"/>
                    basis between 2020 and 2050.
                    <SU>6</SU>
                    <FTREF/>
                     In addition, CARB anticipates that the Zero-Emission Bus (ZEB) technologies deployed under the ICT regulation will assist the future advanced technology deployment in other heavy-duty on-road sectors to further help achieve the emission reduction goals identified in the 2016 State SIP Strategy.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         CARB's ICT Staff Report, page IV-2.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">D. What requirements does the regulation establish?</HD>
                <P>
                    The ICT regulation applies to any public transit agency that owns, operates, leases, rents, or contracts with another entity to operate buses in California, but the term “transit agency” does not mean a correctional facility, airport, college or university, national park, tour bus service provider, or an entity that provide shuttle services solely for patrons of its organization.
                    <SU>7</SU>
                    <FTREF/>
                     The regulation also does not apply to school buses, vehicles on rails, or trolleybuses even if operated by a public transit agency and does not apply to Caltrans, Caltrain, Amtrak, or any local school district.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         13 CCR 2023(a)(1) and (b)(51).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         13 CCR 2023(a)(2).
                    </P>
                </FTNT>
                <P>
                    CARB's ICT regulation requires public transit agencies to submit a ZEB Rollout Plan approved by the applicable governing board that demonstrates how the agency plans for ZEB purchase and infrastructure buildout, and associated financial planning and workforce training by certain deadlines established in the regulation.
                    <SU>9</SU>
                    <FTREF/>
                     The regulation also establishes ZEB purchase requirements that provide for an increasing percentage of new buses 
                    <SU>10</SU>
                    <FTREF/>
                     to be ZEBs such that, by January 1, 2029, all new bus purchases must be ZEBs.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         13 CCR 2023 and 2023.1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Under the ICT regulation, the term “bus” means a rubber-tire vehicle designed to transport passengers by road with gross vehicle weight rating (GVWR) greater than 14,000 pounds. See 13 CCR 2023(b)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         13 CCR 2023.1.
                    </P>
                </FTNT>
                <P>
                    The regulation also provides for waivers for early compliance and provides certain compliance flexibility through provisions allowing pooling of resources among multiple transit agencies, establishing options for other, zero-emission transit services and allowing extensions or exemptions from ZEB purchase requirements for circumstances outside the transit agency's control.
                    <SU>12</SU>
                    <FTREF/>
                     The ICT regulation also requires generally that, when new conventional internal combustion engine bus or hybrid bus purchases are made, transit agencies must purchase buses with low-NO
                    <E T="52">X</E>
                     engines that meet certain criteria if low-NO
                    <E T="52">X</E>
                     engines are available for the bus type and propulsion system type being purchased.
                    <SU>13</SU>
                    <FTREF/>
                     For large transit agencies, the ICT regulation requires them to use renewable diesel or natural gas to fuel their buses that have not yet converted to ZEBs.
                    <SU>14</SU>
                    <FTREF/>
                     Finally, the ICT regulation includes reporting and recordkeeping requirements to ensure compliance with the regulation.
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         13 CCR 2023.1, 2023.2 and 2023.4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         13 CCR 2023.6
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         13 CCR 2023.7.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         13 CCR 2023.8 and 2023.9.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. The EPA's Evaluation and Action</HD>
                <HD SOURCE="HD2">A. How is the EPA evaluating the regulation?</HD>
                <P>
                    The EPA has evaluated the ICT regulation against the applicable procedural and substantive requirements of the CAA for SIPs and SIP revisions and has concluded that the ICT regulation meets all of the applicable requirements. Generally, SIPs must include enforceable emission limitations and other control measures, means, or techniques, as well as schedules and timetables for compliance, as may be necessary to meet the requirements of the Act [see CAA section 110(a)(2)(A)]; must provide necessary assurances that the state will have adequate personnel, funding, and authority under state law to carry out such SIP (and is not prohibited by any provision of federal or state law from carrying out such SIP) [see CAA section 110(a)(2)(E)]; must be adopted by a state after reasonable notice and public hearing [see CAA section 110(l)], and must not interfere with any applicable requirement concerning attainment and reasonable further progress, or any other applicable requirement of the Act [see CAA section 110(l)].
                    <SU>16</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         CAA section 193, which prohibits any pre-1990 SIP control requirement relating to nonattainment pollutants in nonattainment areas from being modified unless the SIP is revised to insure equivalent or greater emission reductions of such air pollutants, does not apply to the ICT rgulation because it does not represent pre-1990 SIP control requirements.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Does the regulation meet the evaluation criteria?</HD>
                <HD SOURCE="HD3">1. Did the State provide for reasonable public notice and hearing prior to adoption?</HD>
                <P>
                    Under CAA section 110(l), SIP revisions must be adopted by the State, and the State must provide for reasonable public notice and hearing prior to adoption. In 40 CFR 51.102(d), we specify that reasonable public notice in this context refers to at least 30 days. The ICT regulation was adopted by the CARB Board on December 14, 2018, through Resolution 18-60 following a public hearing held on that same day.
                    <SU>17</SU>
                    <FTREF/>
                     Prior to adoption, CARB published notice of a September 27, 2018 public hearing on July 24, 2018, and provided a 45-day comment period.
                    <SU>18</SU>
                    <FTREF/>
                     CARB subsequently provided public notice and a 15-day comment period on modifications made to the original draft regulation that was the subject of the September 27, 2018 hearing. The CARB Executive Officer submitted the final ICT rulemaking package to the California Office of Administrative Law (OAL) on July 3, 2019. OAL approved the rulemaking and filed with the California Secretary of State on August 13, 2019. The effective date under State law is October 1, 2019. CARB submitted the OAL-approved Final Regulation Order to the EPA on February 13, 2020, along with various other materials comprising the SIP submission package, including copies of public comments received during the two comment periods and CARB's responses to the comments.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         CARB Resolution 18-60 (page 4) states: “WHEREAS, In March 2017, the Board adopted the State Strategy for the State Implementation Plan, which identifies the deployment of zero-emission buses as a necessary component for California to achieve established near- and long-term air quality and climate mitigation targets (Resolution 17-7, March 23, 2017).”
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         The July 24, 2018 public notice (page 20) states: “If adopted by CARB, CARB plans to submit the proposed regulatory action to the United States Environmental Protection Agency (U.S. EPA) for approval as a revision to the California State Implementation Plan (SIP) required by the federal Clean Air Act (CAA). The adopted regulatory action would be submitted as a SIP revision because it amends regulations intended to reduce emissions of air pollutants in order to attain and maintain the National Ambient Air Quality Standards promulgated by U.S. EPA pursuant to the CAA.”
                    </P>
                </FTNT>
                <P>Based on the materials provided in the February 13, 2020 SIP submission and summarized above, we find that CARB has met the procedural requirements for adoption and submission of SIPs and SIP revisions under CAA section 110(l) and 40 CFR 51.102.</P>
                <HD SOURCE="HD3">2. Does the State have adequate legal authority to implement the regulation?</HD>
                <P>
                    CARB has been granted both general and specific authority under the CH&amp;SC to adopt and implement these regulations. CH&amp;SC sections 39600 (“Acts required”) and 39601 (“Adoption of regulation; Conformance to federal law”) confer on CARB the general authority and obligation to adopt regulations and measures necessary to execute CARB's powers and duties imposed by State law. CH&amp;SC sections 43013(a) and 43018 provide broad authority to achieve the maximum feasible and cost-effective emission 
                    <PRTPAGE P="62340"/>
                    reductions from all mobile source categories, including both on-road and off-road diesel engines.
                </P>
                <P>
                    Moreover, we know of no obstacle under Federal or State law in CARB's ability to implement the regulations. As a general matter, the CAA assigns mobile source regulation to the EPA through title II of the Act and assigns stationary source regulation and SIP development responsibilities to the states through title I of the Act. More specifically, with respect to new motor vehicles, CAA section 209(a) provides that no state or any political subdivision may adopt or attempt to enforce any standard relating to the control of emissions from new motor vehicles or new motor vehicle engines. CAA section 209(b) provides that the EPA must issue waivers to California for standards otherwise preempted under CAA section 209(a) if certain criteria are met. However, in this instance, CARB is setting forth requirements related to transit bus purchases directed at public transit agencies and has not adopted or attempted to enforce a “standard” relating to the control of emissions from new motor vehicles for the purposes of CAA section 209(a) (
                    <E T="03">e.g.,</E>
                     CARB has not set a regulatory requirement on private fleet operator purchases within the State).
                    <SU>19</SU>
                    <FTREF/>
                     Consequently, the ICT regulation is not preempted under CAA section 209(a) and does not require an EPA waiver under CAA section 209(b). The ICT regulation, however, does reduce emissions from a certain class of public vehicles and therefore is more stringent than the otherwise applicable State or Federal standards.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         See 
                        <E T="03">Engine Manufacturers Ass'n</E>
                         v. 
                        <E T="03">South Coast Air Quality Management District,</E>
                         541 U.S. 246 (2004) and subsequent history at 2005 WL 1163437 (C.D. Cal. 2005) and 498 F.3d. 1031 (9th Cir. 2007).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">3. Is the regulation enforceable as required under CAA section 110(a)(2)?</HD>
                <P>
                    We have evaluated the enforceability of the ICT regulation with respect to applicability and exemptions; standard of conduct and compliance dates; sunset provisions; discretionary provisions; and test methods, recordkeeping and reporting,
                    <SU>20</SU>
                    <FTREF/>
                     and have concluded for the reasons given below that the regulation is enforceable for the purposes of CAA section 110(a)(2).
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         These concepts are discussed in detail in an EPA memorandum from J. Craig Potter, EPA Assistant Administrator for Air and Radiation, et al., titled “Review of State Implementation Plans and Revisions for Enforceability and Legal Sufficiency,” dated September 23, 1987.
                    </P>
                </FTNT>
                <P>
                    First, with respect to applicability, we generally find that the ICT regulation is sufficiently clear as to which entities are subject to the requirements in the regulation and which entities are exempt.
                    <SU>21</SU>
                    <FTREF/>
                     Second, we find that the ICT regulation is, as a general matter, sufficiently specific so that the persons affected by the regulation are fairly on notice as to what the requirements and related compliance dates are.
                    <SU>22</SU>
                    <FTREF/>
                     To a large extent, we have already described the substantive requirements and compliance dates set forth in the ICT regulation in section I.D of this document. We note, however, that the definitions set forth in the ICT regulation cite to other sections of California code or regulation, and thus, the definitions in the ICT regulation would be ambiguous for the purposes of enforcement of the SIP unless the other sections of California code or regulation on which the ICT regulation relies are submitted and approved into the SIP along with the ICT regulation. On August 11, 2022, CARB supplemented the original SIP submission with additional sections of California code or regulation on which the ICT regulation relies (see table 2, above) to the EPA for SIP approval to avoid the potential ambiguity in the ICT regulation. With respect to compliance dates, we note that no compliance date in the ICT regulation extends past January 1, 2029, which is consistent with the attainment needs for California with respect to the attainment deadline for the South Coast and San Joaquin Valley “Extreme” nonattainment areas for the 2008 ozone NAAQS.
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         13 CCR 2023.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         13 CCR 2023.1.
                    </P>
                </FTNT>
                <P>Third, the ICT regulation does not include sunset provisions. Fourth, we note that the ICT regulation does not contain provisions that allow for discretion on the part of CARB's Executive Officer. Such “director's discretion” provisions can undermine enforceability of a SIP regulation, and thus prevent full approval by EPA. In the case of the ICT regulation, the regulation allows transit agencies to request an exemption from the ZEB requirement under certain specified circumstances. Specifically, under 13 CCR 2023.4, transit agencies may request an exemption from purchasing ZEBs under any of five circumstances, all of which must be outside the transit agencies' control. Exemptions are allowed when:</P>
                <P>1. a delay in bus delivery is caused by a setback in the construction of infrastructure needed for the ZEB;</P>
                <P>2. available ZEBs cannot meet a transit agency's daily mileage needs;</P>
                <P>3. available ZEBs do not have adequate gradeability performance to meet the transit agency's daily needs for any bus in its fleet;</P>
                <P>4. a required ZEB type for the applicable weight class (based on gross vehicle weight rating (GVWR)) is unavailable for purchase; or</P>
                <P>
                    5. the ZEB purchase requirements in section 2023.1(a) cannot be met due to financial hardship.
                    <SU>23</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         Financial hardship would be granted if a fiscal emergency is declared under a resolution by a transit agency's governing body following a public hearing, a transit agency can demonstrate that it cannot offset the incremental cost of purchasing all available zero-emission buses when compared to the cost of the same type of conventional bus, or a transit agency can demonstrate that it cannot offset the managed, net electricity cost for depot charging battery electric buses when compared to the fuel cost of the same type of conventional internal combustion engine buses. 13 CCR 2023.4(c)(5)(A).
                    </P>
                </FTNT>
                <P>
                    In each instance, the regulation sets forth the documentation required to establish an exemption, and, if fulfilled, the CARB Executive Officer must issue the exemption, thereby avoiding problematic “director's discretion” with respect to the issuance of exemptions by the CARB Executive Officer. Lastly, the ICT regulation includes recordkeeping and reporting requirements that are sufficient to ensure compliance with the applicable requirements.
                    <SU>24</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         13 CCR 2023.8 and 2023.9.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">4. Do the regulations interfere with reasonable further progress (RFP) and attainment or any other applicable requirement of the Act?</HD>
                <P>The ICT regulation is an outgrowth of a commital measure for further deployment of zero-emission bus technologies in the public transit sector that was adopted by CARB in the 2016 State SIP Strategy. The ICT regulation would achieve incremental emissions reductions needed to attain the NAAQS, particularly in the South Coast and San Joaquin Valley air quality planning areas. Thus, we find that the approval of the ICT regulation is consistent with CAA section 110(l) and would not interfere with RFP, attainment or any other applicable requirement of the Act.</P>
                <HD SOURCE="HD3">5. Will the State have adequate personnel and funding for the regulations?</HD>
                <P>
                    Chapter XIII of CARB's ICT Staff Report addresses economic impacts associated with the ICT regulation, including personnel requirements for CARB and fiscal impacts to public transit agencies. CARB's economic impacts assessment concludes that the ICT regulation would require only one additional person-year for developing a reporting system and updating fleet information prior to initial reporting in 2020, assisting transit agencies with compliance and annual reporting, 
                    <PRTPAGE P="62341"/>
                    disseminating information to transit fleets, and enforcement (including auditing reported information, and site visits to confirm vehicle equipment).
                    <SU>25</SU>
                    <FTREF/>
                     As such, we find that CARB has adequate personnel and funding for the ICT regulation.
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         CARB's ICT Staff Report, page VIII-28.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">6. EPA's Regulation Evaluation Conclusion</HD>
                <P>Based on the above discussion, we believe these regulations are consistent with the relevant CAA requirements, policies and guidance.</P>
                <HD SOURCE="HD2">C. The EPA's Recommendations To Further Improve the Rules</HD>
                <P>Several of the defined terms in the ICT regulation reference definitions set forth in paragraphs of other CCR sections that have been renumbered since the ICT regulation was adopted. The cross-references should be updated when CARB next considers amendments to the ICT regulation. The specific defined terms with the outdated CCR references include: (1) the term “compressed natural gas (CNG),” which should be updated to cite 17 CCR 95481(a)(30) rather than 17 CCR 95481(a)(27); (2) the term “renewable hydrocarbon diesel,” which should be updated to cite 17 CCR 95481(a)(130) rather than 17 CCR 95481(a)(123); and (3) the term “biomethane,” which should be updated to cite 17 CCR 95481(a)(22) rather than 17 CCR 95481(a)(20).</P>
                <HD SOURCE="HD2">D. Public Comment and Proposed Action</HD>
                <P>As authorized in section 110(k)(3) of the Act, the EPA proposes to fully approve the submitted ICT regulation because it fulfills all relevant requirements. We will accept comments from the public on this proposal until November 14, 2022. If we take final action to approve the submitted ICT regulation, our final action will incorporate the associated rules into the federally enforceable SIP.</P>
                <HD SOURCE="HD1">III. Incorporation by Reference</HD>
                <P>
                    In this rule, the EPA is proposing to include in a final EPA rule regulatory text that includes incorporation by reference. In accordance with requirements of 1 CFR 51.5, the EPA is proposing to incorporate by reference the California rules listed in tables 1 and 2 and discussed in Section I of this preamble. The EPA has made, and will continue to make, these materials available through 
                    <E T="03">https://www.regulations.gov</E>
                     and at the EPA Region IX Office (please contact the person identified in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this preamble for more information).
                </P>
                <HD SOURCE="HD1">IV. Statutory and Executive Order Reviews</HD>
                <P>Under the CAA, the Administrator is required to approve a SIP submission that complies with the provisions of the Act and applicable Federal regulations. 42 U.S.C. 7410(k); 40 CFR 52.02(a). Thus, in reviewing SIP submissions, the EPA's role is to approve state choices, provided that they meet the criteria of the CAA. Accordingly, this proposed action merely proposes to approve state law as meeting Federal requirements and does not impose additional requirements beyond those imposed by state law. For that reason, this proposed action:</P>
                <P>• Is not a “significant regulatory action” subject to review by the Office of Management and Budget under Executive Orders 12866 (58 FR 51735, October 4, 1993) and 13563 (76 FR 3821, January 21, 2011);</P>
                <P>
                    • Does not impose an information collection burden under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    );
                </P>
                <P>
                    • Is certified as not having a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    );
                </P>
                <P>• Does not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4);</P>
                <P>• Does not have federalism implications as specified in Executive Order 13132 (64 FR 43255, August 10, 1999);</P>
                <P>• Is not an economically significant regulatory action based on health or safety risks subject to Executive Order 13045 (62 FR 19885, April 23, 1997);</P>
                <P>• Is not a significant regulatory action subject to Executive Order 13211 (66 FR 28355, May 22, 2001);</P>
                <P>• Is not subject to requirements of Section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) because application of those requirements would be inconsistent with the CAA; and</P>
                <P>In addition, the SIP is not approved to apply on any Indian reservation land or in any other area where the EPA or an Indian tribe has demonstrated that a tribe has jurisdiction. In those areas of Indian country, the proposed rule does not have tribal implications and will not impose substantial direct costs on tribal governments or preempt tribal law as specified by Executive Order 13175 (65 FR 67249, November 9, 2000).</P>
                <P>The Innovative Clean Transit regulation furthers state environmental justice goals by transitioning to clean transportation modes in low-income and disadvantaged communities. There is no information in the record inconsistent with the stated goals of E.O. 12898 of achieving environmental justice for people of color, low-income populations, and indigenous peoples.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 40 CFR Part 52</HD>
                    <P>Environmental protection, Air pollution control, Incorporation by reference, Intergovernmental relations, Nitrogen dioxide, Ozone, Particulate matter, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>
                        42 U.S.C. 7401 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: October 3, 2022.</DATED>
                    <NAME>Martha Guzman Aceves,</NAME>
                    <TITLE>Regional Administrator, Region IX.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-21910 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL MARITIME COMMISSION</AGENCY>
                <CFR>46 CFR Part 541</CFR>
                <DEPDOC>[Docket No. FMC-2022-0066]</DEPDOC>
                <RIN>RIN 3072-AC90</RIN>
                <SUBJECT>Demurrage and Detention Billing Requirements</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Maritime Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Maritime Commission (Commission) is seeking public comment on a proposed rule that requires common carriers and marine terminal operators to include specific minimum information on demurrage and detention invoices and outlines certain billing practices relevant to appropriate timeframes for issuing invoices, disputing charges with the billing party, and resolving such disputes. The proposed rule addresses considerations identified in the Ocean Shipping Reform Act of 2022. The proposed rule would adopt minimum information that common carriers must include in a demurrage or detention invoice; add to this list additional information that must be included in or with a demurrage or detention invoice; further define prohibited practices by clarifying which parties may be appropriately billed for demurrage or detention charges; and establish billing practices that billing parties must follow when invoicing for demurrage or detention charges.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments on or before December 13, 2022.</P>
                </EFFDATE>
                <ADD>
                    <PRTPAGE P="62342"/>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments by using the Federal eRulemaking Portal at 
                        <E T="03">www.regulations.gov,</E>
                         under Docket No. FMC-2022-0066, Demurrage and Detention Billing Requirements. Please refer to the “Public Participation” heading under the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this notice for detailed instructions on how to submit comments, including instructions on how to request confidential treatment and additional information on the rulemaking process.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        William Cody, Secretary; Phone: (202) 523-5908; Email: 
                        <E T="03">secretary@fmc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Table of Contents</HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. Introduction and Background</FP>
                    <FP SOURCE="FP-2">II. Summary of Comments</FP>
                    <FP SOURCE="FP-2">III. Ocean Shipping Reform Act of 2022</FP>
                    <FP SOURCE="FP-2">IV. Discussion of Proposed Rule</FP>
                    <FP SOURCE="FP1-2">A. General Provisions</FP>
                    <FP SOURCE="FP1-2">1. Purpose of Rule</FP>
                    <FP SOURCE="FP1-2">2. Scope and Applicability</FP>
                    <FP SOURCE="FP1-2">3. Definitions</FP>
                    <FP SOURCE="FP1-2">4. Properly Issued Invoices</FP>
                    <FP SOURCE="FP1-2">B. Required Billing Information</FP>
                    <FP SOURCE="FP1-2">1. Identifying Information</FP>
                    <FP SOURCE="FP1-2">2. Timing Information</FP>
                    <FP SOURCE="FP1-2">3. Rate Information</FP>
                    <FP SOURCE="FP1-2">4. Dispute Information</FP>
                    <FP SOURCE="FP1-2">5. Certifications</FP>
                    <FP SOURCE="FP1-2">C. Billing Practices</FP>
                    <FP SOURCE="FP1-2">1. 30-Day Timeframe To Issue Demurrage or Detention Invoices</FP>
                    <FP SOURCE="FP1-2">2. Timeframes for Disputing Charges and Resolving Disputes</FP>
                    <FP SOURCE="FP-2">V. Public Participation</FP>
                    <FP SOURCE="FP-2">VI. Rulemaking Analyses</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Introduction and Background</HD>
                <P>
                    As rising cargo volumes have increasingly put pressure on common carrier, port and terminal performance, demurrage and detention charges have for a variety of reasons substantially increased. For example, over a two-year period between 2020 and 2022, nine of the largest carriers serving the U.S. liner trades individually charged a total of approximately $8.9 billion in demurrage and detention charges and collected roughly $6.9 billion.
                    <SU>1</SU>
                    <FTREF/>
                     On July 28, 2021, Commissioner Rebecca F. Dye, the Fact Finding Officer for Fact Finding Investigation No. 29, 
                    <E T="03">International Ocean Transportation Supply Chain Engagement</E>
                     (Fact Finding No. 29), recommended, among other things, that the Commission “[i]ssue an [Advance Notice of Proposed Rulemaking (ANPRM)] seeking industry input on whether the Commission should require common carriers 
                    <SU>2</SU>
                    <FTREF/>
                     and marine terminal operators (MTOs) to include certain minimum information on or with demurrage and detention billings and adhere to certain practices regarding the timing of demurrage and detention billings.” 
                    <SU>3</SU>
                    <FTREF/>
                     The Fact Finding Officer expressed concern about certain demurrage and detention billing practices and a need to ensure that it is clear to shippers “what is being billed by whom” so that they can understand the charges.
                    <SU>4</SU>
                    <FTREF/>
                     The Commission approved this Fact Finding 29 recommendation on September 15, 2021.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Fed. Mar. Comm'n, Detention and Demurrage (accessed on September 8, 2022), 
                        <E T="03">https://www.fmc.gov/detention-and-demurrage/#:~:text=In%20dollar%20terms%2C%20the%20nine,over%20the%20two%2Dyear%20period.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         There are two types of common carriers—vessel-operating common carriers, also called ocean common carriers, and non-vessel-operating common carriers. 46 U.S.C. 40102(7), (17), (18).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See Fact Finding Investigation No. 29, Interim Recommendations</E>
                         at 6 (July 28, 2021) (Fact Finding 29 Interim Recommendations), available at: 
                        <E T="03">https://www2.fmc.gov/ReadingRoom/docs/FFno29/FF29%20Interim%20Recommendations.pdf/.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Fact Finding 29 Interim Recommendations at 7.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Fed. Mar. Comm'n, Press Release, FMC to Issue Guidance on Complaint Proceedings and Seek Comments on Demurrage and Detention Billings (Sept. 15, 2021), 
                        <E T="03">https://www.fmc.gov/fmc-to-issue-guidance-on-complaint-proceedings-and-seek-comments-ondemurrage-and-detention-billings/.</E>
                    </P>
                </FTNT>
                <P>
                    On February 15, 2022, the Commission issued an ANPRM to request industry views on potential demurrage and detention billing requirements.
                    <SU>6</SU>
                    <FTREF/>
                     Specifically, the Commission requested comments on whether a proposed regulation on demurrage and detention billing practices should apply to non-vessel-operating common carriers (NVOCCs) as well as vessel-operating common carriers (VOCCs), and whether the regulations should differ based on whether the billing party is a NVOCC or a VOCC.
                    <SU>7</SU>
                    <FTREF/>
                     The Commission also requested comments on whether proposed regulations on demurrage and detention billings should apply to MTOs.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Advance Notice of Proposed Rulemaking on Demurrage and Detention Billing Requirements, 87 FR 8506 (Feb. 15, 2022). 
                        <E T="03">See</E>
                         Docket No. 22-04, Demurrage and Detention Billing Requirements.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         87 FR at 8507, 8508-8509 (Questions 1 and 7).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         87 FR at 8507, 8509 (Questions 2 and 3).
                    </P>
                </FTNT>
                <P>
                    In addition to requesting comments regarding the applicability of demurrage and detention billing requirements to parties such as NVOCCs and MTOs, the Commission also requested comments on what information should be required in demurrage and detention invoices.
                    <SU>9</SU>
                    <FTREF/>
                     In addition to information necessary to identify the shipment (bill of lading number, container number, etc.), the Commission asked whether bills should include information on how the billing party calculated demurrage and detention charges.
                    <SU>10</SU>
                    <FTREF/>
                     For example, the Commission requested comments on whether it should require the billing party to include the following information: identifying clear and concise container availability dates in addition to vessel arrival dates for import shipments; and, for export shipments, the earliest return dates (and any modifications to those dates) as well as the availability of return locations and appointments, where applicable.
                    <SU>11</SU>
                    <FTREF/>
                     The Commission also requested comments on whether the bills should include information on any events (
                    <E T="03">e.g.,</E>
                     container unavailability, lack of return locations, appointments, or other force-majeure reasons) that would justify stopping the clock on charges.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         87 FR at 8508.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         87 FR at 8508.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         87 FR at 8509 (Question 6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         87 FR at 8509 (Question 6).
                    </P>
                </FTNT>
                <P>
                    In the ANPRM, the Commission stated that it was considering whether it should require common carriers and MTOs to adhere to certain practices regarding the timing of demurrage and detention billings. The Commission sought comments on whether the Commission should require billing parties to issue demurrage or detention invoices within 60 days after the charges stopped accruing.
                    <SU>13</SU>
                    <FTREF/>
                     The Commission stated that the Uniform Intermodal Interchange Agreement (UIIA) 
                    <SU>14</SU>
                    <FTREF/>
                     on which the industry relies currently requires that invoices be issued within 60 days and asked whether the 60-day timeframe was effective in addressing concerns raised by billing parties, or whether a longer or shorter time period would be more appropriate.
                    <SU>15</SU>
                    <FTREF/>
                     In addition, the Commission requested comments on whether it should regulate the timeframe for refunds and, if so, what would be an appropriate timeframe.
                    <SU>16</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         87 FR at 8508, 8509 (Question 12).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         The UIIA is a standard industry contract that provides rules for the interchange of equipment between motor carriers and equipment providers, such as VOCCs. Participation is voluntary.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         87 FR at 8508.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         87 FR at 8508, 8509 (Question 14).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Summary of Comments</HD>
                <HD SOURCE="HD2">A. General Summary</HD>
                <P>
                    The Commission received 82 comments in response to the ANPRM from 81 commenters.
                    <SU>17</SU>
                    <FTREF/>
                     The commenters represent the following interest groups: 
                    <PRTPAGE P="62343"/>
                    VOCCs; MTOs; NVOCCs, freight forwarders, and customs brokers; motor carriers; and beneficial cargo owners (BCOs). The Commission also received comments from five entities with unknown affiliations, and three other commenters that did not fit into the above categories.
                    <SU>18</SU>
                    <FTREF/>
                     Comments from these eight entities were consistent with other commenter categories and are captured in the discussions below. All comments are identified below and are available on the docket at 
                    <E T="03">https://www.regulations.gov</E>
                     by their document number (Doc. No.). They are also available in the Commission's Reading Room, at: 
                    <E T="03">https://www2.fmc.gov/readingroom/proceeding/22-04/.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         The Commission received two comments from the Los Angeles Customs Brokers and Freight Forwarders Association (LACBFFA) filed on April 15, 2022 and April 22, 2022. The comments filed on April 22, 2022, incorporated a new section, “5. Multiple Parties and Invoiced Party Identity,” into the comments that LACBFFA filed on April 15, 2022. 
                        <E T="03">Compare</E>
                         Comments of the Los Angeles Customs Brokers and Freight Forwarders Association (Doc. No. 57) at 3 
                        <E T="03">with</E>
                         Comments of the Los Angeles Customs Brokers and Freight Forwarders Association (Doc. No. 83) at 3-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         Comments of Ellen Baicher-Armstrong (Doc. No 39); Comments of RPM Warehouse and Transportation (Doc. No 32); Comments of J. Peter Hinge (Doc. No. 9); Comments of Ocean Logistics (Doc. No. 27); Comments of Naomi Hime (Doc. No. 18); Comments of the International Warehouse Logistics Association (Doc. No. 81); Comments of Veconinter USA LLC (Doc. No. 63); Comments of Weber Distribution LLC (Doc. No. 17).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. VOCCs</HD>
                <P>
                    The Commission received comments from an individual VOCC and from two trade organizations that represent most of the largest VOCCs operating in U.S.-foreign ocean trade (collectively VOCC commenters).
                    <SU>19</SU>
                    <FTREF/>
                     In general, VOCC commenters cautioned the Commission against pursuing regulation in this area. There was an overall concern that such a regulation could overreach and ultimately create more harm than good. For example, WSC warned the Commission to “focus on preventing what is unreasonable as opposed to seeking to re-make the waterfront in the image that it believes is most desirable.” 
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         Comments of Crowley Lain America Services, LLC (Doc. No. 25); Comments of the Ocean Carrier Equipment Management Association, Inc. (Doc. No. 78); Comments of the World Shipping Council (Doc. No. 61). Ocean Carrier Equipment Management Association (OCEMA) and the World Shipping Council (WSC) represent 22 VOCCs, including: APL, CMA-CGM, COSCO, Evergreen, Hamburg Sud, Hapag Lloyd, HMM, Maersk, MSC, ONE, Wan Hai, and Zim.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         Doc. No. 61 at 2.
                    </P>
                </FTNT>
                <P>
                    VOCC commenters noted the existing commercial relationships and how solutions to issues and innovation best develop through these natural relationships without outside parties, such as the Commission.
                    <SU>21</SU>
                    <FTREF/>
                     The existence of commercial relationships meant issues could be resolved in contractual relations and that regulations were generally unnecessary. VOCC commenters expressed concern about the Commission creating an environment where the Commission would create an unbalanced negotiation sphere.
                    <SU>22</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 61 at 2 (“To the extent disagreements do arise, all parties are best served if those disagreements can be resolved promptly and amicably by the parties involved without the need for an outside adjudicator such as the FMC or an arbitrator.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 78 at 2 (“the FMC should not seek to right every perceived wrong or to balance every unfavorable commercial term in a contract by placing its thumb on the scales to balance the results of legitimate commercial negotiations.”).
                    </P>
                </FTNT>
                <P>
                    VOCC commenters asserted that the existence of commercial relationships lends itself to innovation. These commenters expressed concern that regulation in this area could stifle innovation. For example, WSC stated, “a fixed form and process for invoices could stifle digital innovation to include initiatives to do business electronically, including automated invoices, use of block chain technology, and more broadly efforts to digitize the supply chain.” 
                    <SU>23</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         Doc. No. 61 at 3.
                    </P>
                </FTNT>
                <P>
                    Finally, VOCC commenters also stressed that implementation of these changes may prove difficult. These commenters noted that they have developed their own billing systems and because these systems must exchange information, any required changes would be significantly difficult.
                    <SU>24</SU>
                    <FTREF/>
                     OCEMA noted that it is important for “the FMC to first consider technological feasibility, the scope and required time for systems development work that would be required to support any new requirements, and whether the proposed change would burden the ability to resolve items as part of a pre-pay process rather than a post-pay transaction.” 
                    <SU>25</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 61 at 3 (“Every carrier and every MTO has its own systems, and to the extent that those systems must exchange information (as would be the case for many of the data elements/scenarios described in question 6 below), the complexity is multiplied by the required interactions between systems. Many of the billing systems involved are global systems, adding complexity to any required changes.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         Doc. No. 78 at 1-2.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. MTOs</HD>
                <P>
                    The Commission received comments from an MTO and from three MTO trade organizations (collectively MTO commenters).
                    <SU>26</SU>
                    <FTREF/>
                     Like VOCC commenters, MTO commenters generally argued against any new regulation, particularly if such regulation would apply to MTOs.
                    <SU>27</SU>
                    <FTREF/>
                     One commenter observed that the Commission may already consider billing in evaluating demurrage and detention practices and so additional regulation was unnecessary.
                    <SU>28</SU>
                    <FTREF/>
                     Commenters claimed that current Commission regulations adequately protect the industry.
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         Comments of the American Association of Port Authorities (Doc. No. 52); Comments of Maher Terminals LLC (Doc. No. 49); Comments of National Association of Waterfront Employers (Doc. No. 26); Comments of the Port of NY/NJ Sustainable Services Agreement (Doc. No. 68).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 49 at 2. (“Maher believes that the Shipping Act of 1984, as amended . . . , and the Commission's regulations thereunder, particularly 46 U.S.C. 41102(c) and 46 CFR 545.4 and 545.5, provide a sufficient and flexible legal framework for determining the reasonableness of MTO demurrage billing practices.”)
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         Doc. No. 26 at 2 (noted that the Interpretive Rule expressly recognizes the multitude of varying factors that influence the reasonableness of demurrage and detention charges. 
                        <E T="03">See</E>
                         46 CFR 545.5(f) (“Nothing in this rule precludes the Commission from considering factors, arguments, and evidence in addition to those specifically listed in this rule.”)).
                    </P>
                </FTNT>
                <P>
                    MTO commenters also noted the unique aspects of individual terminals. MTO commenters expressed concern about applying a “one size fits all” approach and cautioned the Commission about the unintended consequences and technological difficulties of pursuing this type of regulation.
                    <SU>29</SU>
                    <FTREF/>
                     For example, the National Association of Waterfront Employees (NAWE) expressed concern that establishing billing requirements “will inevitably disrupt existing commercial relationships and could impact the competitiveness of MTOs that continue to face competition from neighboring foreign ports.” 
                    <SU>30</SU>
                    <FTREF/>
                     Other MTO commenters shared this view and asserted that compliance with any changes would create administrative burdens that could worsen current supply chain issues.
                    <SU>31</SU>
                    <FTREF/>
                     MTO commenters argued the costs of any new regulation would outweigh any benefits and cited technological limitations, international competition, and security concerns as reasons why the Commission should limit any regulation it decides to adopt.
                    <SU>32</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 26 at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         Doc. No. 26 at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 52 at 6-7 (“Additional information may be attainable, but would demand ports engage in costly, administrative data collection. These efforts would significantly undermine streamlined operations at ports and terminals and in turn, generate substantial congestion and backlogs.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 52 at 10 (If ports are required to include extensive and detailed information on every billing, there is a national security risk that the aggregated data can be exploited by bad actors or competitors. Further, information regarding ports and terminal pricing, dwell times, and maritime practices risks the disclosure of business-sensitive proprietary information.).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">D. NVOCCs, Freight Forwarders, and Customs Brokers</HD>
                <P>
                    The Commission received comments from ten NVOCCs, freight forwarders, and customs brokers, and five trade organizations that represent such entities (collectively ocean transportation intermediary (OTI) 
                    <PRTPAGE P="62344"/>
                    commenters).
                    <SU>33</SU>
                    <FTREF/>
                     OTI commenters supported the Commission pursuing this regulation, but NVOCC commenters did not uniformly support applying any adopted regulation to NVOCCs.
                    <SU>34</SU>
                    <FTREF/>
                     Most NVOCCs argued that the regulation should not apply to NVOCCs because NVOCCs do not determine demurrage or detention rates.
                    <SU>35</SU>
                    <FTREF/>
                     Two NVOCCs indicated that the demurrage and detention billing requirements should apply to NVOCCs, but did not provide further explanation. However, one of these commenters stated that any new requirements that would apply to NVOCCs should differ from those that would apply to VOCCs because NVOCCs serve as an intermediary between the VOCCs and shippers.
                    <SU>36</SU>
                    <FTREF/>
                     In contrast, freight forwarders and customs brokers indicated that any proposed demurrage and detention billing requirements should apply to VOCCs and NVOCCs equally as they both charge demurrage and detention fees.
                    <SU>37</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         Comments of Combined Freight International KAM (Doc. No. 16); Comments of Lance Sales, Inc. (Doc. No. 20); Comments of A Custom Brokerage, Inc. (Doc. No. 70); Comments of the International Association of Movers (Doc. No. 74); Comments of J &amp; K Fresh LLC (Doc. No. 29); Comments of the Los Angeles Customs Brokers and Freight Forwarders Association (Doc. No 83); Comments of Mode Transportation, LLC (Doc. No. 13); Comments of the National Customs Brokers &amp; Forwarders Association of America, Inc. (Doc. No. 62); Comments of the New York New Jersey Foreign Freight Forwarders and Brokers Association, Inc. (Doc. No. 76); Comments of the Pacific Coast Council of Customs Brokers and Freight Forwarders (Doc. No. 82); Comments of Page International (Doc. No. 19); Comments of Mohawk Global Logistics Corporation (Doc. No. 69); Comments of Thunder Bolt Logistics, LLC (Doc. No. 77); Comments of the Transportation Intermediaries Association (Doc. No. 48); Comments of John S. Connor Global Logistics (Doc. No. 75).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         One commenter did not support demurrage and detention billing requirements regulations to address the issues, but instead favored an industry solution. Doc. No. 20 at 1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         Doc. No. 16 at 1; Doc. No. 13 at 3; Doc. No. 69 at 3; Doc. No. 70 at 2; Doc. No. 75; Doc. No. 75 at 2; Doc. No. 76 at 2; Doc. No. 77 at 2. 
                        <E T="03">See</E>
                         Doc. No. 62 and Doc. No. 83 (both discuss the regulations as applying to VOCCs and MTOs as the billing parties). Some of these commenters stated that the regulations should apply to NVOCCs if they “mark up” the charge. Doc. No. 13 at 3; Doc. No. 69 at 3; Doc. No. 75 at 2; Doc. No. 76 at 2; Doc. No. 77 at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         Doc. No. 19 at 1; Doc. No. 48 at 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         Doc. No. 29 at 1; Doc. No. 74 at 1.
                    </P>
                </FTNT>
                <P>
                    OTI commenters generally agreed on other questions posed in the ANPRM. For example, OTI commenters responded that the proposed regulations should apply to MTOs because they issue demurrage and detention charges.
                    <SU>38</SU>
                    <FTREF/>
                     In addition, these commenters supported requiring billing parties to provide all information identified in Question 6 of the ANPRM as well as information on how to dispute charges to the billing party.
                    <SU>39</SU>
                    <FTREF/>
                     Some OTI commenters stated that the Commission should also require billing parties to certify that the charges comply with the Shipping Act of 1984, as amended.
                    <SU>40</SU>
                    <FTREF/>
                     These commenters were generally supportive of requiring billing parties to issue invoices within a specific timeframe (with most agreeing that the timeframe should be 30 days or less) and requiring billing parties to issue refunds within a specified timeframe.
                    <SU>41</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         Doc. No. 29 at 1; Doc. No. 74 at 1; Doc. No. 16 at 1; Doc. No. 13 at 4; Doc. No. 69 at 1; Doc. No. 70 at 2; Doc. No. 75 at 1; Doc. No. 62 at 4; Doc. No. 76 at 2; Doc. No. 19 at 1; Doc. No. 77 at 3; Doc. No. 48 at 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         Doc. No. 29 at 2-3; Doc. No. 74 at 1; Doc. No. 82 at 1; Doc. No. 16 at 2-3; Doc. No. 13 at 5, 7; Doc. No. 69 at 5, 7-8; Doc. No. 70 at 3, 5; Doc. No. 75 at 3-4; Doc. No. 83 at 2; Doc. No. 62 at 4; Doc. No. 76 at 4-5; Doc. No. 19 at 2-3; Doc. No. 77 at 5, 7; Doc. No. 48 at 4-7. Question 6 requested comments on whether billing parties should be required to provide the following information on demurrage and detention invoices: Bill of lading number; container number; billing date; payment due date; start/end of free time; start/end of demurrage/detention/per diem clock; demurrage/detention/per diem rate schedule; location of the notice of the charge (
                        <E T="03">i.e.,</E>
                         tariff, service contract number and section, or MTO schedule); container availability dates and vessel arrival dates for import shipments; for export shipments, the earliest return dates (and any modifications to those dates); any intervening clock-stopping events, and whether the charge is a pass-through of charges levied by the MTO or port. 87 FR at 8509.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         
                        <E T="03">See</E>
                         Doc. No. 77 at 5; Doc. No. 69 at 5; Doc. No. 75 at 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         Doc. No. 29 at 3; Doc. No. 19 at 3; Doc. No. 77 at 7; Doc. No. 48 at 6; Doc. No. 82 at 2; Doc. No. 83 at 2; Doc. No. 62 at 5; Doc. No. 70 at 5; Doc. No. 69 at 7; Doc. No. 75 at 4; Doc. No. 16 at 3; Doc. No. 13 at 7.
                    </P>
                </FTNT>
                <P>
                    These commenters also stated that if the billing party invoices multiple parties, that the invoice should identify all billed parties and the basis for billing each. Furthermore, several commenters, especially customs brokers, asserted that they should not receive demurrage and detention invoices. For example, Los Angeles Customs Brokers and Freight Forwarders Association (LACBFFA) observed that shippers often name the customs broker as the “notify party” for customs purposes, and, as a result, custom brokers may receive demurrage or detention invoices.
                    <SU>42</SU>
                    <FTREF/>
                     Such commenters argued that customs brokers should not receive invoices because they have no part in the transportation, negotiation, handling, or inland transport, and that the Commission should prohibit common carriers and MTOs from billing parties only shown as a notify party on the Bills of Lading.
                    <SU>43</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         Doc. No. 83 at 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         Doc. No. 83 at 3; Doc. No. 82 at 2-3.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">E. BCOs</HD>
                <P>
                    The Commission received comments from 26 BCOs and 15 trade organizations that represent these entities (collectively BCO commenters).
                    <SU>44</SU>
                    <FTREF/>
                     BCO commenters generally agreed on issues raised in the ANPRM. For example, BCO commenters responded that the regulations should apply to VOCCs, NVOCCs, and MTOs equally. The majority of BCO commenters stated that if the entity issued demurrage or detention charges, then the regulation should apply.
                    <SU>45</SU>
                    <FTREF/>
                     BCO commenters cited the need for uniform requirements to apply to all demurrage and detention invoices they receive, regardless of whether the billing party is 
                    <PRTPAGE P="62345"/>
                    a VOCC, NVOCC, or MTO. However, many of these BCOs preferred not to receive invoices from MTOs because they have no contractual relationship with the MTO.
                    <SU>46</SU>
                    <FTREF/>
                     Several BCO commenters expressed the opposite view and supported a requirement that MTOs bill the BCO directly to avoid additional fees from VOCCs when they pass through such charges.
                    <SU>47</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         Comments of the Agriculture Transportation Coalition (Doc. No. 84); Comments of the American Association of Exporters and Importers (Doc. No. 65); Comments of the American Chemistry Council (Doc. No. 54); Comments of the American Coffee Corporation (Doc. No. 73); Comments of Association of California Recycling Industries (Doc. No. 21); Comments of the Auto Care Association (Doc. No. 79); Comments of Bostock North America (Doc. No. 30); Comments of BassTech International (Doc. No. 72); Comments of Calpine Containers, Inc. (Doc. No. 50); Comments of Jean-Luc Carriere (Doc. No. 5); Comments of the Consumer Technology Association (Doc. No. 67); Comments of Lani Ellingsworth (Doc. No. 11); Comments of Flooring One Source (Doc. No. 3); Comments of Braun Export (Doc. No. 14); Comments of The Grape Company (Doc. No. 42); Comments of LG Electronics USA, Inc. (Doc. No. 44); Comments of The Meadows Group, LLC (Doc. No. 22); Comments of the Meat Import Council of America, North American Meat Institute, and U.S. Meat Export Federation (Doc. No. 64); Comments of National Association of Chemical Distributors (Doc. No. 58); Comments of National Association of Manufacturers (Doc. No. 55); Comments of the National Industrial Transportation League (Doc. No. 60); Comments of National Milk Producers Federation and U.S. Dairy Export Council (Doc. No. 43); Comments of the National Retail Federation (Doc. No. 53); Comments of the North American Home Furnishings Association (Doc. No. 80); Comments of David Oppenheimer and Company, I, LLC (Doc. No. 40); Comments of Pacific Trellis Fruit (Doc. No. 71); Comments of Pinnacle Fresh USA, LLC (Doc. No. 31); Comments of TBC Corporation (Doc. No. 6); Comments of Potential Industries, Inc. (Doc. No. 4); Comments of Sbrocco International, Inc. (Doc. No. 66); Comments of Sony Electronics Inc. (Doc. No. 37); Comments of Streamlight, Inc. (Doc. No. 35); Comments of Suntreat Packing &amp; Shipping Co. (Doc. No. 38); Comments of The Toy Association (Doc. No. 41); Comments of Trelleborg Wheel Systems Americas, Inc. (Doc. No. 34); Comments of USA Rice (Doc. No. 28); Comments of Vivion, Inc. (Doc. No. 8); Comments of Westco Chemicals, Inc. (Doc. No. 36); Comments of Green Fresh Imports (Doc. No. 85); Comments of United Furniture Industries, Inc./Lane Home Furnishing (Doc. No. 86).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 67 at 2 (“[Consumer Technology Association] encourages the Commission to impose the same requirements as to minimum billing information on VOCCs, NVOCCs, and MTOs to facilitate industry-wide transparency.”); Doc. No. 58 at 2 (“[VOCCs, NVOCCs, and MTOs] all charge detention and demurrage fees, and [the National Association of Chemical Distributors] strongly recommends that each be included in any proposed detention and demurrage billing regulation.”); Doc. No. 55 at 1-2 (“These requirements should apply to all parties that may be involved in submitting demurrage and detention bills to shippers and BCOs, including VOCCs, NVOCCs, and MTOs.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 65 at 5 (“Without a contractual connection between the MTO and the shipper, [American Association of Exporters and Importers] members don't see how this would work, and forcing shippers to have a contractual agreement with an MTO is not a good idea.”); Doc. No. 54 at 4 (“Without a contractual connection between the MTO and the shipper, such a requirement would be unworkable.”). Some BCO commenters noted, however, the invoice carriers send to shippers should identify the demurrage charges levied by the MTO to the carrier. 
                        <E T="03">See e.g.,</E>
                         Doc. No. 84 at 5; Doc. No. 64 at 6.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 41 at 4 (its members pay demurrage to MTOs and detention to the carriers); Doc. No. 53 at 4 (supported this practice because it would help avoid VOCCs charging more than MTOs charge); Doc. No. 28 at 3 (over half of its survey respondents supported MTOs charging demurrage directly to shippers).
                    </P>
                </FTNT>
                <P>
                    BCO commenters generally supported requiring billing parties to provide all information identified in Question 6 of the ANPRM and information on how to dispute charges to the billing party. Specifically, BCO commenters cited that requiring such information would put the burden to support the charge on the carrier and would, hopefully, limit the need to dispute charges.
                    <SU>48</SU>
                    <FTREF/>
                     They noted that the most helpful data to address disputed charges would be information related to stop-the-clock events, free time or charges applied when containers are not available for pickup, or when BCOs are unable to drop off containers at a terminal.
                    <SU>49</SU>
                    <FTREF/>
                     BCO commenters asserted that having access to the type of information listed in the ANPRM would help them verify the charges.
                    <SU>50</SU>
                    <FTREF/>
                     Some BCO commenters stated that the Commission should also require billing parties to certify that the charges comply with the Shipping Act of 1984, as amended.
                    <SU>51</SU>
                    <FTREF/>
                     In addition, they also supported the requirement that if the billing party invoices more than one party, then the invoice must identify all billed parties and the basis for billing each party.
                </P>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 64 at 5 (the minimum requirements would put “the burden on the common carrier to ensure more accurate, timely billing, which should, in theory, minimize superfluous charges and improve business practices.”); Doc. No. 67 at 2 (minimum billing requirements “will promote transparency for all parties involved in shipping transactions, help ensure accountability, and deter unfair business practices[.]”); Doc. No. 58 at 2 (“A requirements for all relevant information . . . . would hold billing parties more accountable. It would prevent the VOCCs, NVOCCs, and MTOs from charging erroneous fees that shippers have little or no opportunities to contest.”); Doc. No. 43 at 4 (“Shippers need a full set of details about the containers subject to detention or demurrage charges to effectively assure they are properly assessed charges.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         Commenters report that most disputed charges include when free time starts and stops; countable days and whether the “clock stopping” events, such as there were no appointments, container was unavailable, terminal equipment, such as chassis, was unavailable, etc., should reduce the charges.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 60 at 5 (including clock stopping events will “facilitate the carrier to fulfill their responsibility to bill demurrage and detention charges to meet the incentivizing principle[.]”); Doc. No. 22 at 2-3 (omission of event that should stop the clock from invoices “makes it impossible for shippers to verify whether they are actually accounted for when the final total is calculated.”); Doc. No. 8 at 2 (omission of minimum information “makes it extremely difficult for shippers to be able to verify the amount charged are correct.”). 
                        <E T="03">See also</E>
                         Doc. No. 3 at 2; Doc. No. 44 at 2; Doc. No. 40 at 2; Doc. No. 35 at 2; Doc. No. 34 at 2; Doc. No. 64 at 5; Doc. No. 58 at 2; Doc. No. 55 at 2; Doc. No. 43 at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 65 at 4; Doc. No. 84 at 4; Doc. No. 43 at 5.
                    </P>
                </FTNT>
                <P>
                    BCO commenters were generally supportive of requiring billing parties to include specific information regarding how the billed party may dispute a charge. Specifically, they supported requiring billing parties to provide contact information for disputes and instructions on how to file disputes or information applicable to the dispute process, such as when a charge may be waived or what documentation the billed party must submit with its request.
                    <SU>52</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 60 at 8; Doc. No. 28 at 3; Doc. No. 53 at 5; Doc. No. 43 at 5; Doc. No. 64 at 7; Doc. No. 67 at 6; Doc. No. 84 at 5; Doc. No. 21 at 4; Doc. No. 54 at 5; Doc. No. 79 at 5.
                    </P>
                </FTNT>
                <P>
                    Many BCO commenters supported requiring billing parties to issue demurrage or detention invoices within 60 days of when the charges stop accruing; many commenters supported a timeframe of 30 days or less.
                    <SU>53</SU>
                    <FTREF/>
                     As discussed below, BCO commenters supported a shorter timeframe for issuing demurrage and detention invoices because it is more likely that billed parties will have the information and documents necessary to verify the charges. They also complained that demurrage and detention invoices arrive months after the charges accrued and that billed parties lacked the documentation necessary to verify the charge due to passage of time.
                </P>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         A more detailed discussion of the timeframes supported by specific commenters is found in section IV.C.1, which discusses the proposed timeframe for billing parties to issue demurrage and detention invoices.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">F. Motor Carriers</HD>
                <P>
                    The Commission received comments from six motor carriers and four motor carrier trade organizations (collectively Motor Carrier commenters).
                    <SU>54</SU>
                    <FTREF/>
                     For the most part, the Motor Carrier commenters expressed similar views as the BCO commenters. For example, the Motor Carrier commenters generally supported applying the demurrage and detention billing requirements to VOCCs, NVOCCs, and MTOs; requiring billing parties to provide all information listed in the ANPRM; requiring billing parties to identify all billed parties and the basis for each billed party; and requiring billing parties to issue invoices within a specific timeframe.
                </P>
                <FTNT>
                    <P>
                        <SU>54</SU>
                         Comments of Association of Bi-State Motor Carriers (Doc. No. 51); Comments of Harbor Trucking Association (Doc. No. 33); Comments of MTI, Inc. (Doc. No. 46); Comments of Golden State Logistics (Doc. No. 59); Comments of IMC Companies (Doc. No. 7); Comments of Intermodal Association of North America (Doc. No. 24); Comments of Intermodal Motor Carriers Conference (Doc. No. 47); Comments of William H. Kopke Jr. Inc. (Doc. No. 56); Comments of Marine Container Services LLC (Doc. No. 45); Comments of 1634, A Florida LLC (Doc. No. 15).
                    </P>
                </FTNT>
                <P>
                    In addition, the Motor Carrier commenters expressed concern that billing parties frequently invoiced motor carriers, who have no contractual relationship with the billing parties. For example, the Association of Bi-State Motor Carriers (Bi-State) argued that “motor carriers are not privy to the specifics of the contractual agreements between the shipper and billing parties, and should not be dragged into billing disputes.” 
                    <SU>55</SU>
                    <FTREF/>
                     However, Bi-State noted that billing parties sometimes threatened to prevent motor carriers from picking up or dropping off containers due to disputes with one of the motor carrier's customers.
                    <SU>56</SU>
                    <FTREF/>
                     As a result, Motor Carrier commenters alleged that they must cover the disputed charges in order to serve their other customers.
                    <SU>57</SU>
                    <FTREF/>
                     Accordingly, the Motor Carrier commenters encouraged the Commission to adopt an approach that would require the billing party to bill the customers (BCOs or shippers) directly, as they are the parties who have a contractual relationship with the billing parties.
                    <SU>58</SU>
                    <FTREF/>
                     As a result they said, motor carriers would no longer be responsible to pay such charges or risk business relationships with their other customers if one customer disputes those charges.
                </P>
                <FTNT>
                    <P>
                        <SU>55</SU>
                         Doc. No. 51 at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>56</SU>
                         Doc. No. 51 at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>57</SU>
                         Doc. No. 51 at 2; Doc. No. 47 at 2, 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>58</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 51 at 1 (VOCCs should bill shippers directly); Doc. No. 47 at 2 (supported MTOs billing shippers directly because motor carriers “are not aware of separate contractual arrangements.”); Doc. No. 33 at 8 (their members indicated that demurrage and detention should be billed directly to contracting party).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Ocean Shipping Reform Act of 2022</HD>
                <P>
                    After the Commission issued the ANPRM and received comments, on June 16, 2022, the President signed the 
                    <PRTPAGE P="62346"/>
                    Ocean Shipping Reform Act of 2022 (OSRA 2022) into law.
                    <SU>59</SU>
                    <FTREF/>
                     In OSRA 2022, Congress amended various statutory provisions contained in Part A of Subtitle IV of Title 46, U.S. Code. Specifically, OSRA 2022 prohibits common carriers from issuing an invoice for demurrage or detention charges unless the invoice includes specific information to show that the charges comply with part 545 of title 46, Code of Federal Regulations and applicable provisions and regulations.
                    <SU>60</SU>
                    <FTREF/>
                     OSRA 2022 then lists the minimum information that common carriers must include in a demurrage or detention invoice:
                </P>
                <FTNT>
                    <P>
                        <SU>59</SU>
                         Public Law 117-146, 136 Stat. 1272 (2022).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>60</SU>
                         Public Law 117-146 at Sec. 7(a)(1), 136 Stat. at 1274 (codified at 46 U.S.C. 41104(a)(15)).
                    </P>
                </FTNT>
                <P>(A) date that container is made available.</P>
                <P>(B) the port of discharge.</P>
                <P>(C) the container number or numbers.</P>
                <P>(D) for exported shipments, the earliest return date.</P>
                <P>(E) the allowed free time in days.</P>
                <P>(F) the start date of free time.</P>
                <P>(G) the end date of free time.</P>
                <P>(H) the applicable detention or demurrage rule on which the daily rate is based.</P>
                <P>(I) the applicable rate or rates per the applicable rule.</P>
                <P>(J) the total amount due.</P>
                <P>(K) the email, telephone number, or other appropriate contact information for questions or requests for mitigation of fees.</P>
                <P>(L) a statement that the charges are consistent with any of Federal Maritime Commission rules with respect to detention and demurrage.</P>
                <P>
                    (M) a statement that the common carrier's performance did not cause or contribute to the underlying invoiced charges.
                    <SU>61</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>61</SU>
                         Public Law 117-146 at Sec. 7(a)(2), 136 Stat. at 1275 (codified at 46 U.S.C. 41104(d)(2)).
                    </P>
                </FTNT>
                <P>
                    Failure to include the required information on a demurrage or detention invoice eliminates any obligation of the billed party to pay the applicable charge.
                    <SU>62</SU>
                    <FTREF/>
                     In addition, OSRA 2022 also authorizes the Commission to revise the minimum information that common carriers must include on demurrage or detention invoices in future rulemakings. The Commission addresses this minimum information in this proposed rule.
                    <SU>63</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>62</SU>
                         Public Law 117-146 at Sec. 7(a)(2), 136 Stat. at 1275 (codified at 46 U.S.C. 41104(f)).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>63</SU>
                         Public Law 117-146 at Sec. 7(a)(2), 136 Stat. at 1275 (codified at 46 U.S.C. 41104(d)(2)).
                    </P>
                </FTNT>
                <P>
                    OSRA 2022 requires the Commission to initiate a rulemaking further defining prohibited practices by common carriers, marine terminal operators, shippers, and OTIs regarding the assessment of demurrage or detention charges.
                    <SU>64</SU>
                    <FTREF/>
                     OSRA 2022 also provides that such rulemaking must “only seek to further clarify reasonable rules and practices 
                    <E T="03">related</E>
                     to the assessment of detention and demurrage charges to address the issues identified in the final rule published on May 18, 2020, entitled `Interpretive Rule on Demurrage and Detention Under the Shipping Act' (or successor rule)[.]” 
                    <SU>65</SU>
                    <FTREF/>
                     Specifically, the Commission's rulemaking must clarify “which parties may be appropriately billed for any demurrage, detention, or other similar per container charges.” 
                    <SU>66</SU>
                    <FTREF/>
                     The Commission offers that clarification in this proposed rule.
                </P>
                <FTNT>
                    <P>
                        <SU>64</SU>
                         Public Law 117-146 at Sec. 7(b)(1), 136 Stat. at 1275.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>65</SU>
                         Public Law 117-146 at Sec. 7(b)(2), 136 Stat. at 1275 (emphasis added).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>66</SU>
                         Public Law 117-146 at Sec. 7(b)(2), 136 Stat. at 1275.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Discussion of Proposed Rule</HD>
                <HD SOURCE="HD2">A. General Provisions</HD>
                <HD SOURCE="HD3">1. Purpose of Rule</HD>
                <P>This proposed rule would (1) adopt minimum information that common carriers must include in a demurrage or detention invoice that is listed in 46 U.S.C. 41104(d)(2); (2) add to this list additional information that must be included in or with a demurrage or detention invoice; (3) further define prohibited practices by clarifying which parties may be appropriately billed for demurrage or detention charges; and (4) establish billing practices that billing parties must follow when invoicing for demurrage or detention charges.</P>
                <HD SOURCE="HD3">2. Scope and Applicability</HD>
                <P>This subpart sets forth regulations governing any invoice issued by an ocean common carrier, MTO, or NVOCC to a billed party or their designated agent for the collection of demurrage or detention charges. This regulation does not govern the billing relationships among and between ocean common carriers and MTOs.</P>
                <P>As a preliminary matter, the Commission sought comment on to whom this rule should apply. Specifically, the Commission asked whether NVOCCs and MTOs should be bound by the requirements of the rule. The majority of commenters supported applying the rule to both NVOCCs and MTOs. The Commission has determined that the proposed rule would apply to MTOs and NVOCCs, as well as VOCCs, but will not regulate the billing arrangements between VOCCs and MTOs for the reasons discussed below.</P>
                <HD SOURCE="HD3">a. Inclusion of NVOCCs</HD>
                <P>
                    Fact Finding No. 29 recommended that the Commission regulate the demurrage and detention billings and billing practices of both common carriers and MTOs.
                    <SU>67</SU>
                    <FTREF/>
                     In its opening question to the ANPRM's list of requested information, the Commission asked if both NVOCCs and VOCCs should be included in the regulation.
                    <SU>68</SU>
                    <FTREF/>
                     Most commenters supported applying the regulations to NVOCCs. Generally, these commenters noted the importance of consistency across the industry and the need for everyone to adhere to uniform standards.
                    <SU>69</SU>
                    <FTREF/>
                     As described by the WSC, “[t]he need for predictable and clear billing does not change on the basis of whether the billing entity does or does not operate ships—the distinction between VOCCs and NVOCCs. The customer benefits of transparent and timely billing apply equally in both instances[.]” 
                    <SU>70</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>67</SU>
                         Fact Finding No. 29 Interim Report at 6.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>68</SU>
                         87 FR at 8509.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>69</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 29 at 1 (stressed that “there must be uniformity (One rule for demurrage and detention billing, no matter who bills it.)”); Doc. No. 60 at 3 (“[BCOs] are entitled to receive timely, accurate and explanatory billing from their contracted carrier whether the carriage is contracted pursuant to a bill of lading issued by an NVOCC or by a VOCC.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>70</SU>
                         Doc. No. 61 at 4.
                    </P>
                </FTNT>
                <P>
                    Few commenters opposed applying any proposed billing requirements to NVOCCs. The most common objection was that NVOCCs do not control any physical assets (
                    <E T="03">i.e.,</E>
                     equipment or land) to be subject to the rule and that usually NVOCCs treat demurrage and detention charges as a pass-through cost.
                    <SU>71</SU>
                    <FTREF/>
                     One commenter noted that because a NVOCC has to pay a VOCC or MTO for these types of charges, an NVOCC has no reason to hold back sending an invoice to a BCO because that will leave the NVOCC with outstanding charges to the carrier.
                    <SU>72</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>71</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 69 at 3 (“NVOCCs do not generally file [demurrage and detention] schedules in their tariffs and do not generate [demurrage and detention] charges on their own. Instead, [these] charges originate with VOCCs and MTOs, and are merely passed through by NVOCCs as facilitators of the transaction.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>72</SU>
                         Doc. No. 13 at 4 (“there is no logic in the NVOCC unreasonably delaying billing or notifying the customer. The NVOCC is the party who is being billed by the carrier/terminal and will have the outstanding payables due to the carrier, so clearly, there is no general logic that encourages them to delay billing to their end customer.”).
                    </P>
                </FTNT>
                <P>
                    Although most NVOCCs are only passing through charges to BCOs, that does not change the fact that some NVOCCs invoice BCOs for demurrage and detention.
                    <SU>73</SU>
                    <FTREF/>
                     BCOs employing an 
                    <PRTPAGE P="62347"/>
                    NVOCC generally do not interact with VOCCs and, as a result, the demurrage or detention invoice BCOs receive from an NVOCC may be their only notice about the origin and breakout of these charges. Additionally, because of its contractual relationship with the BCO, an NVOCC is often the only party in this transaction able to inform BCOs as to the nature of these charges. Furthermore, there is a greater need for transparency when the NVOCCs markup demurrage or detention charges assessed by VOCCs or MTOs or when NVOCCs charge demurrage or detention based on their own tariff rules or negotiated agreements.
                </P>
                <FTNT>
                    <P>
                        <SU>73</SU>
                         NVOCCs may also issue invoices that charge demurrage or detention based on their own tariff rules or negotiated rates. In addition, NVOCCs may 
                        <PRTPAGE/>
                        also mark-up the demurrage or detention charge assessed by a VOCC or MTO.
                    </P>
                </FTNT>
                <P>
                    Ultimately, this regulation is an outgrowth of the work done in Fact Finding No. 29. As noted in the Final Report, “[t]hroughout the Fact Finding, industry members reported confusion about the information contained in invoices.” 
                    <SU>74</SU>
                    <FTREF/>
                     As discussed below, the intent of this rulemaking is to ensure that the person receiving the bill understands the charges regardless of whether the billing party is a VOCC, NVOCC, or an MTO.
                    <SU>75</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>74</SU>
                         
                        <E T="03">Fact Finding Investigation 29: Final Report</E>
                         at 51 (May 31, 2022) (Fact Finding 29 Final Report), available at: 
                        <E T="03">https://www.fmc.gov/wp-content/uploads/2022/06/FactFinding29FinalReport.pdf.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>75</SU>
                         
                        <E T="03">See</E>
                         Fact Finding 29 Interim Recommendations at 6 (recommending a rulemaking on demurrage and detention billing requirements so that the person receiving the bill understands “what is being billed and by whom.”).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">b. Inclusion of MTOs</HD>
                <P>
                    MTOs often do not have direct contractual relationships with shippers. Instead, MTOs usually have contractual relationships with VOCCs, such as through terminal services agreements.
                    <SU>76</SU>
                    <FTREF/>
                     However, an MTO may separately assess demurrage as an implied contract in a court of law, provided that demurrage rates are published as part of the MTO's rate schedule.
                    <SU>77</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>76</SU>
                         
                        <E T="03">See</E>
                         46 CFR 535.309.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>77</SU>
                         46 U.S.C. 40501(f); 46 CFR 525.2.
                    </P>
                </FTNT>
                <P>
                    Commenters overwhelmingly argued that the proposed rule should apply to MTOs. Again, while the most common practice is for the MTO to invoice the VOCC and the VOCC to send a combined invoice to the shipper, several commenters also noted that in some cases MTOs bill shippers directly.
                    <SU>78</SU>
                    <FTREF/>
                     MTOs were generally opposed to the proposed regulations, citing that traditionally they do not invoice shippers directly, but instead work with VOCCs.
                    <SU>79</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>78</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 61 at 4 (“MTOs can and do bill for demurrage, and there are multiple business models at ports around the country under which carriers bill on behalf of MTOs and vice versa.”)
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>79</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 49 at 2; Doc. No. 26 at 3.
                    </P>
                </FTNT>
                <P>The Commission's primary concern with this proposed regulation is to ensure billed parties understand the demurrage or detention invoices they receive. Although, at least under the traditional process, it appears that MTOs rarely interact with anyone other than the VOCC, in those cases where an MTO invoices a shipper, the MTO should be subject to the same regulations that apply to VOCCs and NVOCCs.</P>
                <HD SOURCE="HD3">c. MTO and VOCC Relationships</HD>
                <P>
                    This proposed regulation does not govern the billing relationships among and between VOCCs and MTOs. As noted earlier, the purpose of the proposed rule is to identify the minimum information billing parties must include on demurrage and detention invoices, and to improve the invoices' clarity. Although the Fact Finding No. 29 Final Report noted that shippers reported confusion about information contained in demurrage and detention invoices, the Fact-Finding Officer did not receive similar concerns from VOCCs about invoices they were receiving from MTOs.
                    <SU>80</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>80</SU>
                         Fact Finding 29 Final Report at 51. 
                        <E T="03">See e.g.,</E>
                         Coalition for Fair Port Practices Petition for Rulemaking, FMC Docket No. P4-16, (Dec. 7, 2016); 
                        <E T="03">Fact Finding Investigation No. 28: Final Report,</E>
                         (Sep. 4, 2018), available at: 
                        <E T="03">https://www2.fmc.gov/readingroom/docs/FF%20No.%2028/FF28_int_rpt2.pdf/.</E>
                    </P>
                </FTNT>
                <P>
                    The ANPRM specifically asked whether the proposed regulation should apply to the format in which MTOs bill VOCCs.
                    <SU>81</SU>
                    <FTREF/>
                     Most OTI, BCO, and Motor Carrier commenters answered this question by discussing invoices they receive from carriers and the need to have charges originating from an MTO and charges originating from a VOCC distinguished.
                    <SU>82</SU>
                    <FTREF/>
                     This fact suggests that the primary concern that needs to be addressed in this proposed regulation is not the billing interactions between MTOs and VOCCs, but rather transparency and clarity on invoices issued to OTIs, shippers, and motor carriers.
                </P>
                <FTNT>
                    <P>
                        <SU>81</SU>
                         87 FR at 8509.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>82</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 37 at 2 (noted that “charges should be properly distinguished and identified so that by reviewing a bill the invoiced party can determine which charges are being passed along by VOCCs and which charges are being billed directly to the invoiced party in the first instance.”).
                    </P>
                </FTNT>
                <P>
                    Further, many MTOs and MTO trade organizations also argued that regulations in this realm were not warranted. For example, the NAWE explained, “[t]he unique commercial relationships negotiated between VOCCs and MTOs have not been the source of demurrage complaints.” 
                    <SU>83</SU>
                    <FTREF/>
                     Other commenters cited the close commercial relationship shared by MTOs and VOCCs, which, they argued, made additional regulation unnecessary.
                    <SU>84</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>83</SU>
                         Doc. No. 26 at 3. 
                        <E T="03">See</E>
                         Doc. No. 60 at 3 (“the assessment of the terms and charges by [MTOs] on [VOCCs] has not so far been a part of the scope of Fact Finding Investigation 28”); Doc. No. 49 at 3 (“Maher has not received any feedback from its carrier customers and other Terminal users that its free time and demurrage policies and practices are unclear or confusing, or that further regulations are necessary to improve clarity with respect to such policies and practices.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>84</SU>
                         Doc. No. 49 at 3 (“The Commission should not adopt a demurrage billing regulation that includes MTOs, let alone one that regulates the format in which MTOs charge demurrage to VOCCs. To the extent that Maher charges demurrage directly to its VOCC customers, as opposed to other Terminal users, those arrangements are set forth in privately negotiated, arms-length terminal service agreements, which are subject to tailored governing law and dispute resolution provisions.”).
                    </P>
                </FTNT>
                <P>
                    The Commission received a few comments from VOCCs who favored extending regulations to cover the invoicing from MTOs to VOCCs. These comments were generally about maintaining accurate information throughout the process.
                    <SU>85</SU>
                    <FTREF/>
                     VOCC commenters stressed the importance of applying consistent information requirements at each stage in the supply chain.
                    <SU>86</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>85</SU>
                         Doc. No. 61 at 4 (“It would be impractical if charges originating with MTOs, but potentially collected by common carriers, were not subject to the same minimum standards regarding included information. To the extent that a charge may be handled by multiple parties—whether on an agency basis or as a pass-through—it is critical that the relevant information be available to all parties in the chain.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>86</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 78 at 3 (“OCEMA has no position on this issue at this time. However, OCEMA stresses the importance of consistency and transparency throughout the supply chain with respect to any information requirements imposed on VOCCs.”).
                    </P>
                </FTNT>
                <P>
                    Notwithstanding the comments from OCEMA and WSC, the Commission has not received comments responding to the ANPRM or elsewhere that expressed concerns about the relationships or interactions between VOCCs and MTOs that warrant regulating the format used by MTOs to bill VOCCs. The Commission notes the strong commercial relationships between MTOs and VOCCs and is confident that these current contractual relationships will continue to ensure that the proper information is shared and that the party who ultimately receives the invoice is receiving accurate information. Thus, the Commission concludes that at this time it is not necessary to impose minimum billing information requirements for MTO invoices issued to VOCCs.
                    <PRTPAGE P="62348"/>
                </P>
                <HD SOURCE="HD3">3. Definitions</HD>
                <HD SOURCE="HD3">a. Demurrage or Detention</HD>
                <P>For purposes of this proposed rule, the Commission defines the terms “demurrage or detention” broadly to include any charge assessed by common carriers and marine terminal operators related to the use of marine terminal space or shipping containers. This proposed definition is the same as the scope used in 46 CFR 545.5(b). The goal is to encompass all charges having the purpose or effect of demurrage or detention regardless of the labels given to those charges. Under this definition, for instance, a charge assessed by a common carrier for the use of containers outside a marine terminal would fall within the scope of this rule regardless of whether the charge was called “detention” or “per diem.” Similarly, a charge assessed because a container is taking up terminal space would fall within the scope of this rule even if the billing party called the charge something other than “demurrage.” Like the scope denoted in 46 CFR 545.5, the proposed rule specifically limits these definitions to “shipping containers” and excludes charges related to other equipment, such as chassis, because depending on the context, “per diem” can refer to containers, chassis, or both.</P>
                <P>
                    As previously expressed during the Commission's interpretive rulemaking at 46 CFR 545.5, the Commission supports defining demurrage and detention charges based on what asset is the source of the charge (land or container) as opposed to the location of a container (inside or outside a terminal).
                    <SU>87</SU>
                    <FTREF/>
                     In that prior rulemaking, the Commission discouraged use of terms such as “storage” and “per diem” as synonyms for demurrage and detention because these terms add additional complexity. The Commission reiterates those statements here and notes that, despite how it may be used in the industry, to ensure clarity the Commission generally favors using the term “per diem” to refer to the use of chassis.
                </P>
                <FTNT>
                    <P>
                        <SU>87</SU>
                         Interpretive Rule on Demurrage and Detention Under the Shipping Act Final Rule, 85 FR 29638, 29666 (May 18, 2020) (codified at 46 CFR 545.5).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">b. Demurrage or Detention Invoice</HD>
                <P>The Commission proposes to broadly defining the term “demurrage or detention invoice” as meaning any statement, printed, written, or accessible online, that documents an assessment of demurrage or detention charges. By proposing a broad definition, the Commission intends the definition to include the existing variety of methods employed by common carriers and MTOs to invoice shippers, and to leave room for improvement of existing systems or adopting of any new, innovative invoicing methods.</P>
                <P>
                    The Commission received a few comments asking it to institute requirements on how invoices are displayed or presented to shippers.
                    <SU>88</SU>
                    <FTREF/>
                     Although there are a variety of existing methods to display and deliver this information, the Commission does not perceive a problem necessitating a regulatory solution at this time. The Commission intends the proposed definition to encompass the many existing and potential future methods that a bill might be presented and does not indicate a preference or requirement.
                </P>
                <FTNT>
                    <P>
                        <SU>88</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 62 at 4-5 (“One way to make invoices more accessible is to provide recipients with a digital copy of the invoice (for example, through an electronic portal or online source) rather than solely by hardcopy.”); Doc. No. 81 at 2 (“Invoices should be readily available (
                        <E T="03">i.e.</E>
                         online) so NVOCCs can provide statements to their customers.”).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">c. Billed Party</HD>
                <P>The Commission is proposing to define “billed party” as meaning the person receiving the demurrage or detention invoice and who is responsible for the payment of any incurred demurrage or detention charge. In the Commission's view, this proposed definition would best capture the intended scope of this term and eliminate any potential ambiguity as to its coverage.</P>
                <HD SOURCE="HD3">d. Billing Party</HD>
                <P>This proposed rule would define the term “billing party” as meaning the VOCC, NVOCC, or MTO who issues a demurrage or detention invoice. The Commission acknowledges that, currently, in most circumstances the billing party will be a VOCC. For purposes of this proposed rule, this term is defined broadly to incorporate the occasions when an MTO or an NVOCC may issue a demurrage or detention invoice.</P>
                <HD SOURCE="HD3">e. Billing Dispute</HD>
                <P>The term “billing dispute” would mean any disagreement with respect to the validity of the charges, or the method of their invoicing raised by the billed party or their agent to the billing party. This proposed definition, and more generally, this proposed rule, does not indicate a preference or requirement for the format in which a dispute may be raised. Instead, the Commission proposes a broad definition that incorporates all types of disputes raised by a billed party upon receiving a demurrage or detention invoice.</P>
                <HD SOURCE="HD3">4. Properly Issued Invoices</HD>
                <P>
                    OSRA 2022 directs the Commission to initiate a rulemaking that seeks to “further clarify reasonable rules and practices related to the assessment of detention and demurrage charges[.]” 
                    <SU>89</SU>
                    <FTREF/>
                     Specifically, OSRA 2022 instructs the Commission to address “which parties may be appropriately billed for any demurrage, detention, or other similar per container charge.” 
                    <SU>90</SU>
                    <FTREF/>
                     Under the proposed rule, a properly issued invoice is an invoice that is only issued to the person that has contracted with the billing party for the carriage of goods or space to store cargo, and is therefore the person responsible for the payment of any incurred demurrage or detention charge. This is often the shipper of record. The proposed rule would prohibit billing parties from issuing demurrage and detention invoices to persons other than the person for whose account the billing party provided ocean transportation or storage.
                </P>
                <FTNT>
                    <P>
                        <SU>89</SU>
                         OSRA 2022, Section 7(b)(2).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>90</SU>
                         OSRA 2022, Section 7(b)(2).
                    </P>
                </FTNT>
                <P>
                    As a result of anecdotal reports indicating that billing parties sometimes sent invoices to multiple parties for the same shipments, the Commission asked whether this practice occurred regularly.
                    <SU>91</SU>
                    <FTREF/>
                     Many commenters described a current, wide-spread practice where the billing party sends the invoice to multiple parties, most of whom are not the recipient of the service giving rise to the invoiced charge.
                    <SU>92</SU>
                    <FTREF/>
                     The current system, in which parties who did not negotiate contract terms with the billing party are nonetheless bound by them, creates additional confusion and hardship and exacerbates problems in the supply chain. For example, one commenter noted that this practice often results in disputes among the parties.
                    <SU>93</SU>
                    <FTREF/>
                     Other commenters noted that invoicing multiple parties results in duplicative payments, which further complicates resolving invoice disputes.
                    <SU>94</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>91</SU>
                         87 FR at 8508-8509.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>92</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 44 at 3; Doc. No. 37 at 2; Doc. No. 19 at 2; Doc. No. 15 at 3; Doc. No. 13 at 5-6; Doc. No. 8 at 3; Doc. No. 47 at 6; Doc. No. 48 at 5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>93</SU>
                         Doc. No. 53 at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>94</SU>
                         Doc. No. 28 at 2 (“According to most survey respondents, common carriers invoice multiple parties for demurrage and/or detention charges sometimes resulting in duplicative payments”); Doc. No. 13 at 6 (“We also see invoices being sent on the same container to multiple parties, and at times, it is paid more than once[.]”).
                    </P>
                </FTNT>
                <P>
                    Although the Commission did not specifically request comments on prohibiting billing parties from 
                    <PRTPAGE P="62349"/>
                    invoicing anyone except the party who contracted for the service (usually the shipper), the Commission received many comments urging it to adopt such regulations.
                    <SU>95</SU>
                    <FTREF/>
                     Commenters expressed frustration at the practice of billing demurrage and detention charges to parties who have not agreed to the charges or are not otherwise liable.
                    <SU>96</SU>
                    <FTREF/>
                     Other commenters suggested that common carriers bill third parties to shield customer relationships.
                    <SU>97</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>95</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 82 at 4; Doc. No. 56 at 3; Doc. No. 33 at 3; Doc. No. 51 at 1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>96</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 84 at 5 (“The carrier may not invoice a party merely because the carrier has expanded the list of parties which it includes as a merchant in its B/L”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>97</SU>
                         
                        <E T="03">See</E>
                         Doc. No. 82 at 4 (“The carriers are billing the party of least resistance. It appears the first and easiest choice under the “Merchant Clause” is to bill the US customs broker on import shipments as there would be minimal effort on the carrier's part (since the carrier's shipper may be based overseas), and the carrier prefers to avoid imposing detention/demurrage on a current or future customer BCO. Instead, the carrier lawyers pursue a small US customs broker with whom the carrier has not had, and likely will never have, any commercial relationship.”).
                    </P>
                </FTNT>
                <P>
                    Commenters who supported such a regulation generally agreed with the concept that only the parties to the contract (usually the shipper and common carrier), have insight into the contractual agreements between the shipper and common carrier.
                    <SU>98</SU>
                    <FTREF/>
                     Because third parties lack direct involvement and information, most would not be privy to the demurrage and detention terms negotiated by the parties to the original contractual agreement, and therefore are at a disadvantage if pulled into a dispute over such charges. One specific instance where not being a party to the contract is a disadvantage is in determining free time. As one commenter explained:
                </P>
                <FTNT>
                    <P>
                        <SU>98</SU>
                         Doc. No. 51 at 1 (“Members feel strongly that the VOCC should bill the customers directly, as they are the parties who formed the agreement. This would remove the drayage carrier from the equation, reduce confusion, and keep the business relationships clear.”).
                    </P>
                </FTNT>
                <P>
                    “Motor carriers are not a party to contracts and may not be aware of contractual allowances for free time. Yet motor carriers receive these invoices and are then responsible for working with ocean carriers and shippers to determine which contract the shipment was under and whether it allowed for additional free time beyond what has been billed.” 
                    <SU>99</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>99</SU>
                         Doc. No. 47 at 2.
                    </P>
                </FTNT>
                <P>
                    Other commenters also described the difficulty of verifying the accuracy of charges when they were not party to the agreements that determine the allotted free time.
                    <SU>100</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>100</SU>
                         
                        <E T="03">See</E>
                         Doc. No. 33 at 3 (“If a motor carrier is paying demurrage, it is impossible to know if the billing is accurate since the motor carrier is not party to the contractual arrangements and agreed upon free time. On detention and per diem, since Motor Carriers are in possession of the containers under the interchange, they are constantly surveying the restrictions that exist for return of the container. However, motor carriers are still not party to the contract and subsequent free time agreements and therefore must work with shippers to determine which contract the shipment was under and if there was additional free time available from what was billed. This is another reason why only billing between contracting parties should be allowed. Motor carriers are not party to these contracts and therefore should not be billed.”).
                    </P>
                </FTNT>
                <P>
                    The Commission understands the concerns with invoices being sent to those individuals without a contractual relationship and acknowledges that this practice exacerbates dispute resolution and efficient movement of cargo. As was pointed out in the Final Report of the Supply Chain Innovation Team Initiative, the “United States international supply chain is a complex, dynamic ecosystem” and the “lack of direct customer relationships between actors in this system (such as shippers and terminals) impedes cooperative problem-solving, exacerbates disruptions . . . and makes recovering from disruptions more difficult[.]” 
                    <SU>101</SU>
                    <FTREF/>
                     This is exactly the case here where motor carriers, custom brokers, and others who do not have customer relationships with common carriers are being asked to resolve disputes.
                </P>
                <FTNT>
                    <P>
                        <SU>101</SU>
                         
                        <E T="03">Supply Chain Innovation Initiative: Final Report</E>
                         at 3 (Dec. 5, 2017), available at: 
                        <E T="03">https://www.fmc.gov/assets/1/Page/SCITFinalReport-reduced.pdf.</E>
                    </P>
                </FTNT>
                <P>
                    Many commenters also acknowledged the value of commercial relationships within the system. For example, many commenters opposed requiring MTOs to bill shippers directly because of a lack of direct commercial relationship.
                    <SU>102</SU>
                    <FTREF/>
                     Other commenters cited the value of the existing relationships between MTOs and VOCCs and the benefit it brings to the supply chain. For example, the National Industrial Transportation League noted, “[t]he commercial relationship between [VOCCs] and their MTO partners should be valued for its ability to bring benefit to the ocean delivery system and, by extension, to the shipping public in a way that the transactional relationship between [BCOs] and [MTOs] cannot.” 
                    <SU>103</SU>
                    <FTREF/>
                     Parties involved in a continuous commercial relationship have made an investment in that relationship and are highly motivated to timely and effectively resolve problems as they arise in order to maintain a mutually beneficial, ongoing relationship.
                </P>
                <FTNT>
                    <P>
                        <SU>102</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 52 at 8 (“Ports and MTOs do not bill directly to shippers or cargo owners; their strongest relationship lies with ocean carriers, whom they enter into contracts and interface with daily.”); Doc. No. 54 at 4 (“Without a contractual connection between the MTO and the shipper, such a requirement would be unworkable.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>103</SU>
                         Doc. No. 60 at 6. 
                        <E T="03">See</E>
                         Doc. No. 72 at 6.
                    </P>
                </FTNT>
                <P>The Commission believes that prohibiting billing parties from issuing demurrage and detention invoices to persons with whom they do not have a genuine commercial relationship will similarly benefit the supply chain. If the billed party has firsthand knowledge of the terms of its service contract with a common carrier, then they are in a better position to ensure that both they and the carrier are abiding by those terms. When demurrage or detention invoice disputes do arise, the billed party is in a better position than third parties such as truckers and customs brokers to analyze the accuracy of the charge. Further, when the billed party disputes a charge, they have an existing commercial relationship with the billing party and are in a better position to resolve the dispute.</P>
                <P>
                    Practically, the proposed rule would prohibit billing parties from invoicing motor carriers or customs brokers. If adopted, the proposed rule would not prevent motor carriers from paying on behalf of the billed party. Although a motor carrier could pay on behalf of a billed party, the motor carrier would not be liable for these charges and could not be penalized for nonpayment of charges. Although this arrangement is different from many of the billing systems currently employed, it would not be unprecedented. During Fact Finding Investigation No. 28, the Commission sought information on how contractual relationships, policies, and practices regarding demurrage and detention in the United States differ from those in other maritime nations. The Commission received information that, in other nations, VOCCs collect demurrage and detention charges (often combined), directly from shippers rather than motor carriers.
                    <SU>104</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>104</SU>
                         Fact Finding Investigation No. 28 Final Report at 3, Fed. Mar. Comm'n (Sep. 4, 2018), available at: 
                        <E T="03">https://www2.fmc.gov/readingroom/docs/FF%20No.%2028/FF28_int_rpt2.pdf/.</E>
                    </P>
                </FTNT>
                <P>
                    Under the proposed rule, only the person who contracted with the common carrier for the carriage or storage of goods may be issued an invoice. The Commission is aware that there are a variety of shipping arrangements that allocate risks, obligations, and costs between the shipper and the consignee named on the bill of lading. Considering these arrangements, the Commission is specifically seeking comment on whether it would be appropriate to also include the consignee named on the bill of lading as another person who may 
                    <PRTPAGE P="62350"/>
                    receive a demurrage or detention invoice. Including the consignee named on the bill of lading as an appropriately billed party for demurrage or detention charges in the Commission's proposed rule would memorialize an existing industry practice and allow the common carrier to bill either the person who contracted for the shipment of the cargo or consignee named on the bill of lading.
                </P>
                <P>In sum, the proposed rule should simplify the current system and ensure that only the person with the most knowledge about the shipment and who is in the best position to understand and dispute the charge receives a demurrage or detention invoice. The Commission views the practice of sending an invoice to multiple parties involved in the shipping transaction rather than sending an invoice for demurrage or detention charges to only the person that has contracted with the billing party for the carriage or storage of goods as untenable. Therefore, the proposed rule would prohibit such a practice and require that only the person that has contracted with the billing party for the carriage or storage of goods receive an invoice for incurred demurrage or detention charges.</P>
                <HD SOURCE="HD2">B. Required Billing Information</HD>
                <P>
                    In the ANPRM, the Commission requested comment on the minimum information that should be required on billings.
                    <SU>105</SU>
                    <FTREF/>
                     Specifically, the ANPRM requested comment on whether it should require demurrage and detention invoices to include information necessary to identify the shipment (bill of lading number, container number, etc.); information on how the chargers were calculated (container availability date, vessel arrival dates for import shipments and earliest return date for export shipments, etc.); and information on events that justify stopping the clock on charges (
                    <E T="03">e.g.,</E>
                     container unavailability, lack of return locations, lack of appointments, other force majeure reasons).
                    <SU>106</SU>
                    <FTREF/>
                     An overwhelming number of commenters supported the Commission requiring all of the information listed under Question 6 of the ANPRM. However, a small number of commenters opposed such a requirement. For example, NAWE, American Association of Port Authorities, and Port of NY/NJ Sustainable Services Agreement commented that some information listed in the ANPRM may be extremely burdensome or impossible to provide.
                    <SU>107</SU>
                    <FTREF/>
                     In addition, Maher believed that marine terminals should provide basic information on demurrage charges but did not support requiring one-size-fits-all billing information.
                    <SU>108</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>105</SU>
                         87 FR at 8508-8509.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>106</SU>
                         87 FR at 8508. 
                        <E T="03">See</E>
                         Question 6, 87 FR at 8509.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>107</SU>
                         Doc. No. 26 at 5; Doc. No. 52 at 7; Doc. No. 68 at 1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>108</SU>
                         Doc. No. 49 at 3.
                    </P>
                </FTNT>
                <P>
                    OSRA 2022 requires common carriers to include the following information on demurrage and detention invoices: the date that the container is made available; the port of discharge; the container number or numbers; for exported shipments, the earliest return date; the allowed free time in days; the start date of free time; the end date of free time; the applicable detention or demurrage rule on which the daily rate is based; the applicable rate or rates per the applicable rule; the total amount due; the email, telephone number, or other appropriate contact information for questions or requests for mitigation of fees; a statement that the charges are consistent with any of Federal Maritime Commission rules with respect to detention and demurrage; and a statement that the common carrier's performance did not cause or contribute to the underlying invoiced charges.
                    <SU>109</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>109</SU>
                         Public Law 117-146 at Sec. 7(a)(2), 136 Stat. at 1275 (codified at 46 U.S.C. 41104(d)(2)).
                    </P>
                </FTNT>
                <P>The proposed rule would require common carriers and MTOs to include all the information required in 46 U.S.C. 41104(d)(2), listed above on demurrage or detention invoices. The proposed rule also would require billing parties to include minimum information in addition to the information listed in 46 U.S.C. 41104(d)(2) to include specific identifying, timing, rate, and dispute resolution information, discussed in detail below. The Commission requests comments on whether it should require billing parties to include all the proposed information in demurrage and detention invoices. If the commenter opposes any of the proposed requirements, they should identify the information and the obstacles or burden to including such information on demurrage or detention invoices. If the commenter supports the proposed required information, they should explain how the specific information will assist them in verifying the accuracy of the charge or ascertaining how the charge was calculated.</P>
                <HD SOURCE="HD3">1. Identifying Information</HD>
                <P>
                    Under the proposed rule, the invoice must contain sufficient information to enable the billed party to identify the container(s) to which the charges apply, including: the bill of lading number(s); the container number(s); for imports, the port(s) of discharge; and the basis for why the invoiced party is the proper party of interest and thus liable for the charge. OSRA 2022 requires that invoices include the port of discharge and the container number.
                    <SU>110</SU>
                    <FTREF/>
                     The proposed rule clarifies that billing parties must only include ports of discharge for import shipments because providing the port of discharge on a demurrage or detention invoice would be less useful in the context of export shipments. The proposed rule would also require billing parties to include the bill of lading number and the basis for why the billed party was invoiced. Commenters expressed support for requiring billing parties to include the container number, bill of lading number, and basis for why the billed party is the proper party in interest. The ANPRM did not request comments on whether the invoice should include the port of discharge for import shipments.
                </P>
                <FTNT>
                    <P>
                        <SU>110</SU>
                         46 U.S.C. 41104(d)(2)(B) and (C).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">a. Bill of Lading Number</HD>
                <P>
                    The Commission received many comments in favor of including the bill of lading number as required information. Several commenters noted that without the bill of lading number it would be difficult to determine which shipment is being charged and to verify the accuracy of the charge.
                    <SU>111</SU>
                    <FTREF/>
                     However, the Commission received one comment that opposed such a requirement. OCEMA stated that the bill of lading number is not provided to billed parties that are not party to the transportation contract because disclosure may present a risk of violating legal or contractual non-disclosure requirements.
                    <SU>112</SU>
                    <FTREF/>
                     In response to this comment, the Commission notes that bill of lading numbers are available through publicly accessible import and export data systems, such as PIERS. In addition, the proposed rule would prohibit the billing party from issuing demurrage or detention invoices to a person other than the person for whose account the billing party provided ocean transportation or space to store goods. Further, commenters observed that demurrage and detention invoices already include bill of lading numbers.
                    <SU>113</SU>
                    <FTREF/>
                     Because the bill of lading number provides valuable identifying information to the billed party, the Commission proposes requiring this information on demurrage and detention invoices.
                </P>
                <FTNT>
                    <P>
                        <SU>111</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 22 at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>112</SU>
                         Doc. No. 78 at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>113</SU>
                         Doc. No. 52 at 7; Doc. No. 49 at 4.
                    </P>
                </FTNT>
                <PRTPAGE P="62351"/>
                <HD SOURCE="HD3">b. Basis for Why Party Was Invoiced</HD>
                <P>
                    The Commission received numerous comments asserting that billing parties issue invoices to multiple parties for the same charges and this sometimes results in duplicative payments.
                    <SU>114</SU>
                    <FTREF/>
                     Many commenters supported requiring billing parties to include the basis for why a party has been invoiced and is thus liable for the charge. Requiring billing parties to identify the basis for why billed parties are liable for the charge would enable billed parties to confirm that they are correctly billed the invoiced charges. The proposed rule is consistent with proposed § 541.4 that would prohibit billing parties from issuing demurrage and detention invoices to persons other than the person for whose account the billing party provided ocean transportation or space to store goods. Because the invoice would identify the basis for why the billed party is liable for the charge, they would be able to confirm that the billing party could issue an invoice to them under proposed § 541.4.
                </P>
                <FTNT>
                    <P>
                        <SU>114</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 13 at 5-6; Doc. No. 15 at 3; Doc. No. 18 at 2; Doc. No. 19 at 2; Doc. No. 37 at 2; Doc. No. 28 at 2.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Timing Information</HD>
                <P>
                    The invoice must contain sufficient information to enable the billed party to identify the relevant time for which the charges apply and the applicable due date for the invoiced charges, including: the billing date; the billing due date; the allowed free time in days; the start date of free time; the end date of free time; for imports, the container availability date; for exports, the earliest return date; and the specific date(s) for which demurrage or detention were charged. OSRA 2022 requires that invoices include the date the container is made available; for exported shipments, the earliest return date; the allowed free time in days; the start date of free time; and the end date of free time.
                    <SU>115</SU>
                    <FTREF/>
                     The proposed rule clarifies that the billing parties must only provide container availability date for import shipments. The proposed rule would also require billing parties to specify the dates for which demurrage and/or detention charges accrued, the billing date, and the billing due date.
                </P>
                <FTNT>
                    <P>
                        <SU>115</SU>
                         46 U.S.C. 41104(d)(2)(A), (E)-(G).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">a. Dates Demurrage or Detention Charges Accrued</HD>
                <P>
                    The Commission received numerous comments in response to the ANPRM that indicated that invoices should reflect any “clock-stopping” events that would prevent the return of equipment, such as container unavailability or lack of return locations or appointment times.
                    <SU>116</SU>
                    <FTREF/>
                     OCEMA, however, opposed such a requirement and stated that this type of information is not always known at the time of invoicing and would therefore pose a risk of delaying the payment process and disrupt the flow of cargo.
                    <SU>117</SU>
                    <FTREF/>
                     Further, OCEMA asserted that information such as container and appointment availability are sourced from third party systems and therefore the timing and feasibility of providing this information is unknown.
                    <SU>118</SU>
                    <FTREF/>
                     WSC noted that carriers do not have visibility to such “clock-stopping” events and that shippers or motor carriers are more aware of challenges to container pick-up and drop-off.
                    <SU>119</SU>
                    <FTREF/>
                     Maher also commented that it does not provide “clock-stopping events” on their invoices because of the cost and administrative burden to providing such information.
                    <SU>120</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>116</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 13 at 5; Doc. No. 14 at 2; Doc. No. 15 at 2; Doc. No. 16 at 2; Doc. No. 17 at 2; Doc. No. 18 at 2; Doc. No. 19 at 2; Doc. No. 21 at 3; Doc. No. 29 at 2; Doc. No. 30 at 1; Doc. No. 44 at 2; Doc. No. 83 at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>117</SU>
                         Doc. No. 78 at 5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>118</SU>
                         Doc. No. 78 at 5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>119</SU>
                         Doc. No. 61 at 7.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>120</SU>
                         Doc. No. 49 at 4.
                    </P>
                </FTNT>
                <P>Instead of requiring billing parties to identify specific “clock-stopping” events on demurrage and detention invoices, the proposed rule would require the billing party to identify the specific dates on which they charged demurrage or detention. The proposed rule permits billing parties to take into account any intervening events that affected the charges, if known, and enables billed parties to confirm or dispute the validity of charges on specific dates. The proposed rule incorporates the intent of OSRA 2022 to shift the burden to billing parties to justify the demurrage or detention charges while allowing billing parties to correct invoices when the intervening events are not initially known to them.</P>
                <HD SOURCE="HD3">b. Billing Date and Payment Due Date</HD>
                <P>The proposed rule would require the billing party to include the invoice billing date and payment due date. The proposed requirement to include the billing date and the payment due date will enable the billed party and the Commission to confirm that the billing parties are adhering to the proposed billing practices outlined in proposed § 541.7. If the billed party has the billing date information, they can confirm that the billed party issued the invoice within 30 days from when the charge was last incurred. In addition, providing the payment due date would notify the billed party of when they must pay the invoiced charges.</P>
                <HD SOURCE="HD3">3. Rate Information</HD>
                <P>
                    The invoice must contain sufficient information to enable the billed party to identify the amount due and readily ascertain how that amount was calculated, including: the total amount due; the applicable detention or demurrage rule (
                    <E T="03">i.e.,</E>
                     the tariff name and rule number or applicable service contract number and section) on which the daily rate is based; and the specific rate or rates per the applicable tariff rule or service contract. The proposed rule incorporates the rate information requirements contained in OSRA 2022.
                    <SU>121</SU>
                    <FTREF/>
                     It also clarifies that when billing parties provide the applicable detention or demurrage rule on which the daily rate is based, the billing party should provide sufficient detail so that the billed party is able to locate the specific rate that should apply and confirm that the invoice includes the correct rate. Under the proposed rule, demurrage and detention invoices would include information necessary to ascertain the rate that the billing party applied, grounds for applying that rate, dates for which the billing party charged the rate, and the total amount due. This enhanced transparency will enable billed parties to efficiently confirm the charges and decide whether to dispute the invoiced charges.
                </P>
                <FTNT>
                    <P>
                        <SU>121</SU>
                         46 U.S.C. 41104(d)(2)(H)-(J).
                    </P>
                </FTNT>
                <P>
                    A commenter expressed concern that providing the applicable detention or demurrage rule on which the daily rate is based could “undermine service contract confidentiality.” 
                    <SU>122</SU>
                    <FTREF/>
                     However, because the proposed rule would prohibit billing parties from issuing a demurrage or detention invoice to a person other than the person for whose account the billing party provided ocean transportation or space to store goods, the billed party is already privy to the confidential contract or negotiated terms, including the specific agreed upon rate.
                </P>
                <FTNT>
                    <P>
                        <SU>122</SU>
                         Doc. No. 61 at 5.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">4. Dispute Information</HD>
                <P>
                    Under the proposed rule, the invoice must contain sufficient information to enable the billed party to readily identify a contact to whom they may direct questions or concerns related to the invoice and understand the process to request fee mitigation, refund, or waiver. The proposed rule would require the invoice to include: an email, telephone number, or other appropriate contact information for questions or request for fee mitigation, refund, or waiver; an URL address of a publicly-accessible portion of the billing party's website that provides a detailed 
                    <PRTPAGE P="62352"/>
                    description of information or documentation that the billed party must provide to successfully request fee mitigation, refund, or waiver; and defined timeframes that comply with the billing practices in this part, during which the billed party must request fee mitigation, refunds, or waivers and within which the billing party will resolve such requests. OSRA 2022 requires that the invoice include contact information for questions or requests for mitigation of fees.
                    <SU>123</SU>
                    <FTREF/>
                     The proposed rule would also require that the invoice include the URL address where billed parties can obtain a detailed description of the information or documentation that must be provided with a request for fee mitigation, refunds, or waivers. In addition, the proposed rule would require that the invoice provide defined timeframes by which the billed party must request fee mitigation, refunds, or waivers, and the timeframe by which the billing party would resolve such requests.
                </P>
                <FTNT>
                    <P>
                        <SU>123</SU>
                         46 U.S.C. 41104(d)(2)(K).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">a. Website Address That Describes Information Required for Dispute Resolution</HD>
                <P>
                    The proposed regulation would require the invoice to provide the URL address of a publicly-accessible portion of the billing party's website that describes the information that the billed party must provide to successfully request fee mitigation, refund, or waiver. Commenters indicated that shippers lack awareness regarding what information they should include when they request fee mitigation, refunds, or waivers.
                    <SU>124</SU>
                    <FTREF/>
                     Knowing what information or documentation must be filed with requests for fee mitigation, refunds, and waivers, will improve efficiency within the dispute process. Parties will not need to exchange communications that inform billed parties what information to include with their requests, notify billed parties that they did not file all the required information, or supplement pending requests with additional information. In addition, awareness of what information must be provided with any request for fee mitigation, refund, or waiver, will enable billed parties to collect the necessary information and decrease the number of requests denied on technicalities.
                </P>
                <FTNT>
                    <P>
                        <SU>124</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 8 at 3; Doc. No. 13 at 7; Doc. No. 41 at 4; Doc. No. 43 at 5; Doc. No. 53 at 5; Doc. No. 65 at 5; Doc. No. 61 at 10; Doc. No. 63 at 4; Doc. No. 64 at 7; Doc. No. 67 at 6.
                    </P>
                </FTNT>
                <P>
                    The Commission acknowledges that a billing party should require the same information to be submitted with requests for fee mitigation, refund, or waiver, regardless of which billed party is making the request. Thus, it is not necessary to include a detailed description of information or documents that the billed party must provide to successfully request a fee mitigation, refund, or waiver on each individual demurrage or detention invoice. However, it is important that billed parties can easily locate this information. To ensure that billed parties are able to find this vital information, the proposed rule would require the invoice to include the URL address for a publicly-accessible portion of the billing party's website that describes the required information. The Commission encourages billing parties to provide a URL address that is specific (
                    <E T="03">i.e.,</E>
                     providing the billing party's homepage when there is no clear indication where this information can be found would be insufficient).
                </P>
                <HD SOURCE="HD3">b. Defined Timeframes</HD>
                <P>The proposed rule would also require the invoice to include specific timeframes within which the billed party must submit a fee mitigation, refund, or waiver request and for when the billing party will resolve such requests. This proposed rule would require the timeframes to comply with the proposed billing practices in §§ 541.7 and 541.8. As a result, demurrage or detention invoices would notify the billed party of these key timeframes and required billing practices and the billed party would not need to be familiar with the Commission's regulations to know these key dates.</P>
                <HD SOURCE="HD3">5. Certifications</HD>
                <P>
                    Under the proposed rule, the invoice must contain a statement from the billing party that the demurrage or detention charge is consistent with any of the Commission's rules related to demurrage and detention, including the proposed rule and 46 CFR 545.5.
                    <SU>125</SU>
                    <FTREF/>
                     In addition, the proposed rule would require the invoice to include a statement from the billing party that their performance did not cause or contribute to the underlying invoiced charges. OSRA 2022 requires billing parties to include both statements on demurrage and detention invoices.
                    <SU>126</SU>
                    <FTREF/>
                     The proposed rule would incorporate these required statements. In addition, the proposed rule clarifies that the Commission's rules related to demurrage and detention include the proposed rule and the interpretive rule on demurrage and detention at 46 CFR 545.5. Although the ANPRM did not request comments on whether billing parties include such statements on demurrage and detention invoices, several commenters supported requiring such statements or similar statements.
                    <SU>127</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>125</SU>
                         46 U.S.C. 41104(d)(2)(L).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>126</SU>
                         46 U.S.C. 41104(d)(2)(M).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>127</SU>
                         
                        <E T="03">See e.g.,</E>
                         Doc. No. 75 at 3; Doc. No. 43 at 5; Doc. No. 77 at 5; Doc. No. 69 at 5; Doc. No. 84 at 4.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Billing Practices</HD>
                <HD SOURCE="HD3">1. 30-Day Timeframe To Issue Demurrage or Detention Invoices</HD>
                <P>
                    In the ANPRM, the Commission noted concerns from stakeholders regarding the lack of clearly defined timeframes for the issuance of demurrage or detention invoices.
                    <SU>128</SU>
                    <FTREF/>
                     In Docket No. 19-05, several commenters asserted that billing parties should issue demurrage or detention invoices within specific timeframes.
                    <SU>129</SU>
                    <FTREF/>
                     When issuing the Interpretive Rule in May 2020, the Commission determined not to take action regarding deadlines for demurrage or detention invoices but stated that it reserved the right to address the issue at a later date.
                    <SU>130</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>128</SU>
                         87 FR at 8508.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>129</SU>
                         85 FR at 29662.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>130</SU>
                         85 FR at 29662.
                    </P>
                </FTNT>
                <P>
                    In the ANPRM, the Commission stated that it continued to receive reports of delays in receiving demurrage or detention invoices and the difficulties in validating the accuracy of the charges contained in invoices received months after the occurrence of the charges.
                    <SU>131</SU>
                    <FTREF/>
                     The Commission requested comments on whether it should require billing parties issue demurrage or detention invoices within 60 days of the occurrence of the charge, noting that this approach would align with the UIIA.
                    <SU>132</SU>
                    <FTREF/>
                     Specifically, the Commission stated that it was interested in whether the UIIA timeframe is effective and whether a longer or shorter deadline would be appropriate.
                    <SU>133</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>131</SU>
                         87 FR at 8508.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>132</SU>
                         87 FR at 8508.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>133</SU>
                         87 FR at 8508.
                    </P>
                </FTNT>
                <P>
                    Many commenters responded to the question of whether the Commission should require that billing parties issue demurrage or detention invoices within 60 days of when the charge stops accruing. Four commenters opposed requiring billing parties issue a demurrage or detention invoice within a specified timeframe.
                    <SU>134</SU>
                    <FTREF/>
                     Two commenters, WSC and OCEMA, asserted that the Commission should 
                    <PRTPAGE P="62353"/>
                    not regulate when billing parties issue demurrage or detention invoices because these timeframes should be set by contractual terms or commercial negotiations.
                    <SU>135</SU>
                    <FTREF/>
                     If, however, the Commission decides to require billing parties to issue demurrage or detention invoices within a specific timeframe, WSC and OCEMA stated the timeframe should be no shorter than 60 days.
                    <SU>136</SU>
                    <FTREF/>
                     In addition, both WSC and OCEMA noted that any such timeframe for issuing demurrage or detention invoices should allow for nuanced application of the deadline.
                    <SU>137</SU>
                    <FTREF/>
                     For example, both parties raised questions regarding how the deadline would apply to third-parties that pass through demurrage and detention charges.
                    <SU>138</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>134</SU>
                         Doc. No. 61 at 9-10; Doc. No. 26 at 7; Doc. No. 68 at 1 (incorporates NAWE Comments); Doc. No. 78 at 6-7. WSC and OCEMA are associations that represent ocean common carriers. 
                        <E T="03">See</E>
                         Doc. No. 78 at 1. NAWE and PONYNJSSA are associations that represent marine terminal operators. Doc. No. 26 at 1; Doc. No. 68 at 1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>135</SU>
                         Doc. No. 61 at 9-10; Doc. No. 78 at 6-7.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>136</SU>
                         Doc. No. 61 at 10; Doc. No. 78 at 7.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>137</SU>
                         Doc. No. 61 at 10; Doc. No. 78 at 7.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>138</SU>
                         Doc. No. 61 at 10; Doc. No. 78 at 7.
                    </P>
                </FTNT>
                <P>
                    NAWE asserted that it is unnecessary for the Commission to regulate timeframes for billing parties, especially MTOs, to issue demurrage or detention invoices.
                    <SU>139</SU>
                    <FTREF/>
                     Specifically, NAWE observed that most MTOs use electronic data interchanges and electronic payment methods and are able to “invoice” demurrage or detention charges immediately after these charges stop accruing.
                    <SU>140</SU>
                    <FTREF/>
                     Because there are no delays for such MTOs in issuing demurrage or detention invoices, NAWE commented that there is no need for such regulations with regard to MTOs.
                    <SU>141</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>139</SU>
                         Doc. No. 26 at 7.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>140</SU>
                         Doc. No. 26 at 7.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>141</SU>
                         Doc. No. 26 at 7.
                    </P>
                </FTNT>
                <P>
                    The remaining commenters supported mandating a deadline within which a billing party must issue a demurrage or detention invoice. These include comments submitted by a customs broker; 10 motor carriers and motor carrier organizations; 
                    <SU>142</SU>
                    <FTREF/>
                     14 OTI and OTI organizations; 
                    <SU>143</SU>
                    <FTREF/>
                     31 BCOs and BCO trade organizations; 
                    <SU>144</SU>
                    <FTREF/>
                     and five with unknown affiliations.
                    <SU>145</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>142</SU>
                         
                        <E T="03">See</E>
                         Doc. No. 51; Doc. No. 56; Doc. No. 46; Doc. No. 56; Doc. No. 7; Doc. No. 15; Doc. No. 24; Doc. No. 33; Doc. No. 47; Doc. No. 17.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>143</SU>
                         
                        <E T="03">See</E>
                         Doc. No. 13; Doc. No. 75; Doc. No. 70; Doc. No. 82; Doc. No. 69; Doc. No. 83; Doc. No. 60; Doc. No. 62; Doc. No. 19; Doc. No. 77; Doc. No. 48; Doc. No. 76; Doc. No. 63, Doc. No. 81.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>144</SU>
                         
                        <E T="03">See</E>
                         Doc. No. 79; Doc. No. 3; Doc. No. 67; Doc. No. 6; Doc. No. 14; Doc. No. 8; Doc. No. 30; Doc. No. 38; Doc. No. 34; Doc. No. 22; Doc. No. 40; Doc. No. 42; Doc. No. 66; Doc. No. 37; Doc. No. 72; Doc. No. 71; Doc. No. 44; Doc. No. 21; Doc. No. 28; Doc. No. 41; Doc. No. 43; Doc. No. 64; Doc. No. 33; Doc. No. 53; Doc. No. 54; Doc. No. 65; Doc. No. 55; Doc. No. 58; Doc. No. 73; Doc. No. 35; Doc. No. 84.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>145</SU>
                         
                        <E T="03">See</E>
                         Doc. No. 9; Doc. No. 18; Doc. No. 27; Doc.; Doc. No. 32.
                    </P>
                </FTNT>
                <P>
                    These commenters cited several reasons in support of an invoice deadline. For example, several commenters asserted that having a deadline will provide billed parties with predictability and transparency regarding when they will receive their invoices.
                    <SU>146</SU>
                    <FTREF/>
                     In the ANPRM, the Commission requested information on how long it typically takes to receive a demurrage or detention invoice.
                    <SU>147</SU>
                    <FTREF/>
                     Responses to this question vary greatly. For example, some commenters stated that billed parties receive demurrage or detention invoices within several days after the charges stop accruing.
                    <SU>148</SU>
                    <FTREF/>
                     Other commenters claimed that it may take between 2-4 weeks to receive demurrage or detention invoices.
                    <SU>149</SU>
                    <FTREF/>
                     Most commenters however, stated that the time varies greatly and could range from 30 days to 24 months.
                    <SU>150</SU>
                    <FTREF/>
                     For example, the Meadows Group reported that it received demurrage and detention invoices an average of 120 days after the charge accrued, but that it also received invoices 24 months after the fact.
                    <SU>151</SU>
                    <FTREF/>
                     In addition, National Association of Manufacturers (NAM) stated that its members report a wide range of invoice delivery times, from as short as 30 days to as long as nearly 24 months.
                    <SU>152</SU>
                    <FTREF/>
                     In addition, commenters noted that the time it takes for a billing party to issue a demurrage or detention invoice varies on the charges assessed. For example, one commenter stated that billing parties invoice import demurrage before releasing containers, but that billing parties may take as long as 30 days to invoice export demurrage charges and 60 days to invoice import and export detention charges.
                    <SU>153</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>146</SU>
                         Doc. No. 67 at 5; Doc. No. 24 at 4; Doc. No. 83 at 3; Doc. No. 62 at 5; Doc. No. 8 at 2-3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>147</SU>
                         87 FR at 8509.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>148</SU>
                         Doc. No. 19 at 3; Doc. No. 37 at 3; Doc. No. 26 at 4; Doc. No. 49 at 5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>149</SU>
                         Doc. No. 18 at 3; Doc. No. 25 at 2; Doc. No. 32 at 3; Doc. No. 44 at 4; Doc No. 14 at 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>150</SU>
                         Doc. No. 17 at 3 (3-6 months); Doc. No. 22 at 3 (120-day average, but have received invoices 24 months after); Doc. No. 33 at 9 (average is 30-60 days, but sometimes up to six months); Doc. No. 28 at 3 (average of 30-60 days but sometimes up to six months); Doc. No. 48 at 6 (members received invoices 180 days after a transaction took place); Doc. No. 54 at 4 (takes up to 6 months to receive an invoice); Doc. No. 55 at 2 (up to 24 months); Doc. No. 53 at 5 (averages 60-90 days, but as long as 8 months); Doc. No. 67 at 2, 5 (typically receive billings within 30 days, but sometimes 60 days or more); Doc. No. 3 at 3 (averaging 6-12 months). 
                        <E T="03">See</E>
                         Doc. No. 27 at 3; Doc. No. 46 at 2; Doc. No. 41 at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>151</SU>
                         Doc. No. 22 at 3
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>152</SU>
                         Doc. No. 55 at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>153</SU>
                         Doc. No. 9 at 3; 
                        <E T="03">see</E>
                         Doc. No. 39 at 2; Doc. No. 56 at 2; Doc. No. 67 at 3; Doc. No. 60 at 8; Doc. No. 65 at 5; Doc. No. 64 at 6.
                    </P>
                </FTNT>
                <P>
                    In addition to providing transparency and predictability for when billing parties must issue demurrage or detention invoices, commenters noted that an invoicing deadline will ensure that billed parties will have the information readily available to verify the accuracy of the charges.
                    <SU>154</SU>
                    <FTREF/>
                     Similarly, many commenters claimed that timely billing will reduce costly and time-consuming research to verify charges, particularly when received months after the fact.
                    <SU>155</SU>
                    <FTREF/>
                     NAM explains that shippers and BCOs regularly receive costly bills months after the fact and that responding to such bills require diverting staff hours and attention away from cargo delivery and efficient logistics operations.
                    <SU>156</SU>
                    <FTREF/>
                     Furthermore, NAM asserted that instituting an invoice deadline will “ensure that shippers and BCOs will be able to accurately maintain shipping information and records to validate any demurrage or detention bills[.]” 
                    <SU>157</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>154</SU>
                         Doc. No. 67 at 5; Doc. No. 58 at 3; Doc. No. 22 at 3; Doc. No. 84 at 4-5; Doc. No. 28 at 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>155</SU>
                         Doc. No. 13 at 7; Doc. No. 3 at 2; Doc. No. 54 at 5; Doc. No. 58 at 3; Doc. No. 55 at 2; Doc. No. 53 at 5; Doc. No. 65 at 4; Doc. No. 79 at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>156</SU>
                         Doc. No. 55 at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>157</SU>
                         Doc. No. 55 at 2.
                    </P>
                </FTNT>
                <P>
                    Most commenters agreed that billing parties should issue demurrage or detention invoices within a specific timeframe but disagreed on what that timeframe should be. Three commenters did not indicate a specific deadline in their comments but stressed the need for a timeliness standard.
                    <SU>158</SU>
                    <FTREF/>
                     Among the remaining commenters, 23 commenters supported a 60-day timeframe; 
                    <SU>159</SU>
                    <FTREF/>
                     25 commenters supported a 30-day timeframe; 
                    <SU>160</SU>
                    <FTREF/>
                     and 11 commenters favored shorter timeframes ranging from five to twenty-one days.
                    <SU>161</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>158</SU>
                         Doc. No. 51 at 2; Doc. No. 34 at 2; Doc. No. 35 at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>159</SU>
                         Doc. No. 76 at 7; Doc. No. 65 at 5; Doc. No. 54 at 4; Doc. No. 39 at 2; Doc. No. 46 at 2; Doc. No. 32 at 2; Doc. No. 33 at 9; Doc. No. 9 at 3; Doc. No. 24 at 4; Doc. No. 81 at 4; Doc. No. 44 at 4; Doc. No. 58 at 3; Doc. No. 55 at 2; Doc. No. 43 at 5; Doc. No. 56 at 2; Doc. No. 53 at 5; Doc. No. 22 at 3; Doc. No. 37 at 3; Doc. No. 48 at 6; Doc. No. 28 at 3; Doc. No. 63 at 4; Doc. No. 8 at 3; Doc. No. 17 at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>160</SU>
                         Doc. No. 3 at 2-3; Doc. No. 6 at 2; Doc. No. 7 at 4; Doc. No. 13 at 7; Doc. No. 14 at 4; Doc. No. 15 at 3; Doc. No. 29 at 3; Doc. No. 30 at 2; Doc. No. 40 at 3; Doc. No. 42 at 1 (citing Doc. No. 29); Doc. No. 47 at 3; Doc. No. 67 at 3; Doc. No. 66 at 1 (citing Doc. No. 29); Doc. No. 83 at 5; Doc. No. 60 at 8; Doc. No. 62 at 5; Doc. No. 64 at 6; Doc. No. 67 at 4-5; Doc. No. 72 at 7; Doc. No. 71 at 1 (citing Doc. No. 29); Doc. No. 75 at 3, 4; Doc. No. 70 at 5; Doc. No. 84 at 5; Doc. No. 82 at 2. Many of these commenters supported shorter timeframes as well. 
                        <E T="03">See</E>
                         Doc. No. 70 (supported 7 days); Doc. No. 60 at 8 (supported 5-15 days); Doc. No. 72 at 7 (supported 5-15 days); Doc. No. 64 at 6 (supported 14 days); Doc. No. 75 at 4 (supported 15 days); Doc. No. 82 at 2 (supported 21 days).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>161</SU>
                         Doc. No. 27 at 3 (5-10 days); Doc. No. 38 at 4 (10 days); Doc. No. 73 at 3-4 (10 days); Doc. No. 41 at 4 (10 days); Doc. No. 18 at 3 (10 days); Doc. No. 79 at 4 (10-14 days); Doc. No. 56 at 2-3 (14 days); Doc. No. 69 at 5, 7 (14 days); Doc. No. 77 
                        <PRTPAGE/>
                        at 7 (14-21 days); Doc. No. 21 at 3-4 (15 days); Doc. No. 19 at 3 (21 days).
                    </P>
                </FTNT>
                <PRTPAGE P="62354"/>
                <P>
                    Two commenters who supported the 60-day timeframe stated that this timeframe is reasonable and aligns with the UIIA timeframe.
                    <SU>162</SU>
                    <FTREF/>
                     For example, Intermodal Association of North America (IANA) asserted that the 60-day timeframe provided in the UIIA represents an industry standard because this requirement has been in effect for over 25 years.
                    <SU>163</SU>
                    <FTREF/>
                     Additionally, IANA opined that adopting the 60-day timeframe “will reinforce, rather than disrupt, long-standing industry practices.” 
                    <SU>164</SU>
                    <FTREF/>
                     However, many commenters who supported the 60-day timeframe also urged the Commission to consider shorter timeframes.
                    <SU>165</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>162</SU>
                         Doc. No. 43 at 5; Doc. No. 24 at 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>163</SU>
                         Doc. No. 24 at 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>164</SU>
                         Doc. No. 24 at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>165</SU>
                         Doc. No. 65 at 5; Doc. No. 54 at 4; Doc. No. 81 at 4; Doc. No. 28 at 3.
                    </P>
                </FTNT>
                <P>
                    Many commenters also supported an invoice deadline shorter than 60 days for a variety of reasons. For example, commenters asserted that 60 days is too long and that, with billing parties using automated systems, 30 days is more than adequate time for billing parties to issue demurrage or detention invoices.
                    <SU>166</SU>
                    <FTREF/>
                     Moreover, commenters observed that several billing parties currently issue invoices within 30 days after the charges stop accruing.
                    <SU>167</SU>
                    <FTREF/>
                     In addition, OTI commenters stated that receiving demurrage and detention invoices from VOCCs and MTOs in a timely manner will allow OTIs to bill their clients within a reasonable timeframe which will hopefully facilitate collection of these charges.
                    <SU>168</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>166</SU>
                         Doc. No. 29 at 2; Doc. No. 30 at 2; Doc. No. 38 at 4; Doc. No. 67 at 3; Doc. No. 73 at 4; Doc. No. 40 at 3; Doc. No. 56 at 3. 
                        <E T="03">See</E>
                         Doc. No. 60 at 8.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>167</SU>
                         
                        <E T="03">See</E>
                         Doc. No. 29 at 2-3 (immediate billing is an industry standard for the perishable produce industry). 
                        <E T="03">See also</E>
                         Doc. No. 67 at 5; Doc. No. 30 at 2; Doc. No. 40 at 3; Doc. No. 38 at 4. Commenters report that they receive demurrage or detention invoices several days to one month after charges stop accruing. Doc. No. 19 at 3; Doc. No. 37 at 3; Doc. No. 26 at 4; Doc. No. 49 at 5; Doc. No. 18 at 3; Doc. No. 25 at 2; Doc. No. 32 at 3; Doc. No. 44 at 4; Doc. No. 14 at 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>168</SU>
                         Doc. No. 32 at 3; Doc. No. 69 at 5; Doc. No. 70 at 3, 5; Doc. No. 76 at 7; Doc. No. 77 at 5.
                    </P>
                </FTNT>
                <P>
                    The Commission is proposing to require billing parties to issue demurrage or detention invoices to billed parties within 30 days from the date charges stop accruing. Although the proposed 30-day timeframe is shorter than the 60-day timeframe contained in the UIIA, commenters reported that demurrage or detention invoices generally arrive within the 30-day timeframe.
                    <SU>169</SU>
                    <FTREF/>
                     For example, MTOs indicated that, because of customer portals and electronic payment systems, invoices are available immediately when the charges stop accruing.
                    <SU>170</SU>
                    <FTREF/>
                     Because it appears that billing parties are capable of issuing demurrage or detention invoices, on average, within 30 days, applying this timeframe does not appear to be unreasonable. In addition, a 30-day deadline, which provides billing parties sufficient time to prepare an invoice, will also permit billed parties to verify the charges more efficiently. As commenters noted, the more time that passes between when the charges stop accruing and when the billed party receives an invoice, it is more difficult for the billed party to verify the charge because it is less likely that they have the necessary information or documentation to confirm a charge.
                </P>
                <FTNT>
                    <P>
                        <SU>169</SU>
                         Doc. No. 29 at 2-3; Doc. No. 67 at 5; Doc. No. 30 at 2; Doc. No. 40 at 3; Doc. No. 38 at 4; Doc. No. 19 at 3; Doc. No. 37 at 3; Doc. No. 26 at 4; Doc. No. 49 at 5; Doc. No. 18 at 3; Doc. No. 25 at 2; Doc. No. 32 at 3; Doc. No. 44 at 4; Doc. No. 14 at 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>170</SU>
                         Doc. No. 26 at 7; Doc. No. 49 at 4.
                    </P>
                </FTNT>
                <P>
                    The Commission also proposes to excuse billed parties from paying assessed charges contained in invoices issued after the 30-day timeframe. If a billing party does not issue a demurrage or detention invoice within the required timeframe, then the charge would be void and the billed party would not be required to pay. Without such a provision, there would be no consequence for not meeting the 30-day timeframe. In addition, this proposed rule is consistent with the UIIA and supported by commenters.
                    <SU>171</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>171</SU>
                         UIIA at E.6.c; Doc. No. 84 at 5; Doc. No. 77 at 7; Doc. No. 69 at 5, 7; Doc. 75 at 4; Doc. No. 43 at 5.
                    </P>
                </FTNT>
                <P>
                    The 30-day timeframe would apply to VOCCs, MTOs, and NVOCCs. In the ANPRM, the Commission requested comments on whether the Commission should require different timeframes for VOCC and NVOCC demurrage and detention invoices.
                    <SU>172</SU>
                    <FTREF/>
                     Most commenters responded that the same timelines should apply to VOCCs and NVOCCs.
                    <SU>173</SU>
                    <FTREF/>
                     However, when NVOCCs pass through demurrage or detention charges assessed against them to their customers, it may be difficult for NVOCCs to issue a demurrage or detention invoice within the required timeframe if it does not receive the initial invoice in a timely manner.
                    <SU>174</SU>
                    <FTREF/>
                     In addition, OCEMA suggested that the invoice deadlines should “allow nuance in the application of the deadline for factors that may justify delay[.]” 
                    <SU>175</SU>
                    <FTREF/>
                     The Commission requests comments discussing how it can best reflect the application of the deadline to NVOCCs that pass through demurrage or detention charges.
                </P>
                <FTNT>
                    <P>
                        <SU>172</SU>
                         87 FR at 8509.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>173</SU>
                         Doc. No. 3 at 2; Doc. No. 41 at 3; Doc. No. 64 at 5; Doc. No. 28 at 2; Doc. No. 43 at 4; Doc. No. 53 at 4; Doc. No. 51 at 2; Doc. No. 80 at 1; Doc. No. 61 at 8; Doc. No. 15 at 2; Doc. No. 22 at 3; Doc. No. 46 at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>174</SU>
                         
                        <E T="03">See</E>
                         Doc. No. 32 at 3; Doc. No. 69 at 5; Doc. No. 70 at 3, 5; Doc. No. 76 at 7; Doc. No. 77 at 5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>175</SU>
                         Doc. No. 78 at 7. 
                        <E T="03">See</E>
                         Doc. No. 13 at 4; Doc. No. 61 at 10.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Timeframes for Disputing Charges and Resolving Disputes</HD>
                <P>
                    The Commission proposes that billed parties submit any requests for fee mitigation, refund, or waiver to billing parties within 30 days of receiving a demurrage or detention invoice.
                    <SU>176</SU>
                    <FTREF/>
                     The proposed rule would provide billed parties 30 days to verify the invoiced charges; decide whether they would like to request fee mitigation, refund, or waiver; and collect the documentation to support its request. The proposed timeframe protects billed parties against unreasonable deadlines that billing parties may impose upon their customers. At the same time, the 30-day dispute timeframe would notify billed parties that, if they plan to request fee mitigation, refund, or waiver, they have a limited amount of time within which they must submit such a request and it would protect billing parties from untimely requests.
                </P>
                <FTNT>
                    <P>
                        <SU>176</SU>
                         The proposed 30-day deadline would apply to requests for fee mitigation, refunds, or waivers submitted by the billed party to the billing party through the billing parties' dispute process. The proposed rule does not apply to “charge complaints” authorized by section 10 of OSRA 2022 (codified in 46 U.S.C. 41310).
                    </P>
                </FTNT>
                <P>
                    The 30-day timeframe for disputing charges is consistent with the timeframe for billed parties to dispute charges in the UIIA and is supported by commenters.
                    <SU>177</SU>
                    <FTREF/>
                     One commenter suggested extending the current dispute deadline from 30 to 60 days to allow carriers more time to audit and pay per diem invoices accordingly.
                    <SU>178</SU>
                    <FTREF/>
                     The Commission is proposing this timeframe in conjunction with its proposed 30-day timeframe for billing parties to issue demurrage or detention invoices. Because the proposed rules would require billing parties to issue invoices in a timelier manner, one anticipated benefit is that billed parties would be able to more quickly verify the charges as the documents necessary to confirm the charges would be more readily available. Accordingly, in the Commission's view, the 30-day timeframe is a reasonable one that permits billed parties to review the charges and request fee mitigation, refund, or waiver as necessary that they can meet readily.
                </P>
                <FTNT>
                    <P>
                        <SU>177</SU>
                         UIIA at E.6.f; Doc. No. 84 at 4; Doc. No. 64 at 7; Doc. No. 43 at 5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>178</SU>
                         Doc. No. 59 at 2.
                    </P>
                </FTNT>
                <PRTPAGE P="62355"/>
                <P>
                    The Commission proposes that, after receiving a fee mitigation, refund, or waiver request, a billing party must resolve the request within 30 days. This proposed deadline is consistent with the response deadline contained in the UIIA and supported by several commenters.
                    <SU>179</SU>
                    <FTREF/>
                     The proposed rule would require a billing party, after receiving a request to mitigate, refund, or waive a charge on a demurrage or detention invoice, to determine whether to grant or deny the request within 30 days of receiving the request. Resolution of a request also includes billing parties to mitigate, refund, or waive a charge, if appropriate, within the 30-day timeframe. If the billing party does not resolve the fee mitigation, refund, or waiver request within 30 days, then the charge at issue must be mitigated, refunded, or waived.
                </P>
                <FTNT>
                    <P>
                        <SU>179</SU>
                         UIIA at H.1; Doc. No. 63 at 4; Doc. No. 43 at 5; Doc. No. 64 at 7; Doc. No. 41 at 4; Doc. No. 54 at 5; Doc. No. 33 at 11; Doc. No. 74 at 5. 
                        <E T="03">See</E>
                         Doc. No. 25, Attachment at 1 (states that the company aspires to address disputes within 30 days). Several commenters supported shorter timeframes; however, it appears that these commenters were discussing timeframes for when billing parties should issue refunds 
                        <E T="03">after</E>
                         they dismiss the charges at issue. 
                        <E T="03">See</E>
                         Doc. No. 39 at 3; Doc. No. 69 at 8; Doc. No. 46 at 3; Doc. No. 84 at 5; Doc. No. 75 at 5; Doc. No. 79 at 4; Doc. No. 3 at 3; Doc. No. 72 at 8; Doc. No. 60 at 9; Doc. No. 28 at 3; Doc. No. 21 at 4.
                    </P>
                </FTNT>
                <P>
                    The proposed deadline would provide billed parties with certainty that it will receive a response to its fee mitigation, refund, or waiver request within a specific timeframe. Like receiving demurrage or detention invoices, commenters reported that the time it takes for billed parties to receive a refund varies greatly. For example, one commenter claimed that “[r]efunds are paid when the carrier or terminal operator wants to do it” and that it can take up to six months to receive a refund.
                    <SU>180</SU>
                    <FTREF/>
                     Commenters generally supported having a deadline for resolving requests for fee mitigation, refund, or waiver. As one commenter succinctly stated, “just as bills must be paid within a certain amount of time, it seems only fair that refunds should be issued within a set time frame.” 
                    <SU>181</SU>
                    <FTREF/>
                     In that vein, proposing to require billing parties to resolve requests for fee mitigation, refunds, or waivers within 30 days of receipt ensures that such requests are not pending for an indefinite period of time.
                </P>
                <FTNT>
                    <P>
                        <SU>180</SU>
                         Doc. No. 77 at 8. 
                        <E T="03">See</E>
                         Doc. No. 33 at 11; 
                        <E T="03">see also</E>
                         Doc. No. 22 at 4 (typically takes six months to receive a refund, may take as long as two years).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>181</SU>
                         Doc. No. 51 at 4. 
                        <E T="03">See</E>
                         Doc. No. 44 at 4 (“[r]efunds should be issued in a timely manner, certainly within a specified number of days”).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">V. Public Participation</HD>
                <HD SOURCE="HD2">How do I prepare and submit comments?</HD>
                <P>
                    You may submit comments by using the Federal eRulemaking Portal at 
                    <E T="03">www.regulations.gov,</E>
                     under Docket No. 2022-0066, Demurrage and Detention Billing Requirements. Please follow the instructions provided on the Federal eRulemaking Portal to submit comments.
                </P>
                <HD SOURCE="HD2">How do I submit confidential business information?</HD>
                <P>
                    The Commission will provide confidential treatment for identified confidential information to the extent allowed by law. If you would like to request confidential treatment, pursuant to 46 CFR 502.5, you must submit the following, by email, to 
                    <E T="03">secretary@fmc.gov:</E>
                </P>
                <P>• A transmittal letter that identifies the specific information in the comments for which protection is sought and demonstrates that the information is a trade secret or other confidential research, development, or commercial information.</P>
                <P>• A confidential copy of your comments, consisting of the complete filing with a cover page marked “Confidential-Restricted,” and the confidential material clearly marked on each page.</P>
                <P>• A public version of your comments with the confidential information excluded. The public version must state “Public Version—confidential materials excluded” on the cover page and on each affected page and must clearly indicate any information withheld.</P>
                <HD SOURCE="HD2">Will the Commission consider late comments?</HD>
                <P>
                    The Commission will consider all comments received before the close of business on the comment closing date indicated above under 
                    <E T="02">DATES</E>
                    . To the extent possible, we will also consider comments received after that date.
                </P>
                <P>How can I read comments submitted by other people?</P>
                <P>
                    You may read the comments received by the Commission at 
                    <E T="03">www.regulations.gov,</E>
                     under Docket No. 2022-0066, Demurrage and Detention Billing Requirements.
                </P>
                <HD SOURCE="HD1">VI. Rulemaking Analyses</HD>
                <HD SOURCE="HD2">Regulatory Flexibility Act</HD>
                <P>The Regulatory Flexibility Act, 5 U.S.C. 601-612, provides that whenever an agency is required to publish a notice of proposed rulemaking under the Administrative Procedure Act (APA), 5 U.S.C. 553, the agency must prepare and make available for public comment an initial regulatory flexibility analysis (IRFA) describing the impact of the proposed rule on small entities, unless the head of the agency certifies that the rulemaking will not have a significant economic impact on a substantial number of small entities. 5 U.S.C. 603, 605.</P>
                <P>The proposed rule would require VOCCs, NVOCCs, and MTOs to including minimum billing information on detention and demurrage invoices. The rulemaking additionally requires billing parties that issue demurrage and detention invoices to follow certain billing practices; specifically, billed parties must issue demurrage and detention invoices within 30 days from when charges stop accruing.</P>
                <P>
                    The Commission presumes that VOCCs and MTOs generally do not qualify as small entities under the guidelines of the Small Business Administration (SBA).
                    <SU>182</SU>
                    <FTREF/>
                     The Commission previously stated that VOCCs and MTOs generally are large companies that exceed the employee (500) and/or annual revenue ($21.5 million) thresholds to be considered small business entities. However, the Commission presumes that NVOCCs are small business entities.
                </P>
                <FTNT>
                    <P>
                        <SU>182</SU>
                         FMC Policy and Procedures regarding Proper Consideration of Small Entities in Rulemakings (Feb. 7, 2003), available at: 
                        <E T="03">https://www.fmc.gov/wp-content/uploads/2018/10/SBREFA_Guidelines_2003.pdf.</E>
                    </P>
                </FTNT>
                <P>There are likely two types of costs imposed by the proposed rulemaking on the affected businesses. The imposition of a 30-day deadline to issue an invoice from when demurrage and detention charges stop accruing could result in a loss of revenue to the billing party. In additional, the minimum billing information requirements imposed by the proposed rule may require the billing party to collect additional information and change its billing information technology system to include all the required information on invoices.</P>
                <P>
                    Most of the costs of the rulemaking will be borne by VOCCs and MTOs as they generally assess demurrage and detention charges, and not NVOCCs. As discussed above, in most cases, NVOCCs pass through detention and demurrage charges billed to them on invoices generated by VOCCs or MTOs. Accordingly, NVOCCs should receive the minimum billing information required by the proposed rule from either the VOCC or MTO issuing the invoice. For these reasons, the Chairman of the Federal Maritime Commission certifies that if this rule is promulgated, it would not have a significant 
                    <PRTPAGE P="62356"/>
                    economic impact on a substantial number of small entities.
                </P>
                <HD SOURCE="HD2">National Environmental Policy Act</HD>
                <P>The National Environmental Policy Act of 1969 (NEPA) (42 U.S.C. 4321-4347) requires Federal agencies to consider the environmental impacts of proposed major Federal actions significantly affecting the quality of the human environment, as well as the impacts of alternatives to the proposed action. When a Federal agency prepares an environmental assessment, the Council on Environmental Quality (CEQ) NEPA implementing regulations (40 CFR parts 1500 through 1508) require the Federal agency to “include brief discussions of the need for the proposal, of alternatives [. . .], of the environmental impacts of the proposed action and alternatives, and a listing of agencies and persons consulted.” 40 CFR 1508.9(b). This section serves as the Commission's Draft Environmental Assessment (Draft EA) for the proposed changes to 46 CFR part 541.</P>
                <P>
                    Upon completion of an environmental assessment, it was determined that the proposed rule will not constitute a major Federal action significantly affecting the quality of the human environment within the meaning of the National Environmental Policy Act of 1969, 42 U.S.C. 4321 
                    <E T="03">et seq.,</E>
                     and that preparation of an environmental impact statement is not required. This Finding of No Significant Impact (“FONSI”) will become final within 10 days of publication of this notice in the 
                    <E T="04">Federal Register</E>
                     unless a petition for review is filed by any of the methods described in the 
                    <E T="02">ADDRESSES</E>
                     section of the document. The FONSI and environmental assessment are available for inspection on the docket at 
                    <E T="03">https://www.regulations.gov.</E>
                </P>
                <HD SOURCE="HD2">Paperwork Reduction Act</HD>
                <P>The Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3521) (PRA) requires an agency to seek and receive approval from the Office of Management and Budget (OMB) before collecting information from the public. The agency must submit collections of information in proposed rules to OMB in conjunction with the publication of the notice of proposed rulemaking. In compliance with the PRA, the Commission has submitted the proposed information collection to the Office of Management and Budget and is requesting comment on the proposed revision.</P>
                <P>With the proposed addition of 46 CFR part 541, the Commission has identified specific billing information required on demurrage and detention invoices. Although some entities issue demurrage and detention invoices that contain most of the required information, many entities will likely need to revise their practices to include the required information. The Commission believes that the addition of 46 CFR part 541 will likely increase the overall industry burden, but that it will not have a significant impact on members of the shipping public.</P>
                <HD SOURCE="HD3">Title: 46 CFR Part 541—Demurrage and Detention Billing Requirements</HD>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3072-XXXX.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     46 U.S.C. 41104(a)(15) and (d)(2) and 46 CFR part 541 subpart A, if adopted, require demurrage and detention invoices to contain certain additional information to increase transparency so that billed parties can identify the containers at issue, the applicable rate, dates for which charges accrued, and how to dispute charges. Further, 46 U.S.C. 41104(d)(2) and 46 CFR part 541, if adopted, also require demurrage and detention invoices to certify that the charges comply with applicable regulatory provisions and that the invoicing party's behavior did not contribute to the charges.
                </P>
                <P>
                    <E T="03">Current Action:</E>
                     The proposed rule implements statutory text that identifies the minimum information that billing parties must include on demurrage and detention invoices, identifies additional information that billing parties must include on demurrage and detention invoices, and clarifies which entities may receive demurrage and detention invoices.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Approve information collection.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     The Commission identifies information that entities must include on demurrage and detention invoices to ensure compliance with the Shipping Act of 1984, as amended. Specifically, proposed 46 CFR part 541 subpart A implements the billing information requirements contained in 46 U.S.C. 41104(d)(2) and adds additional minimum information that billing parties must include on demurrage and detention invoices.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     The frequency of demurrage and detention invoices is determined by the billing party. It is the billing entity's responsibility to ensure that their demurrage and detention charges comply with applicable statutory and regulatory provisions. The Commission estimates that between five and ten percent of all containers moving in U.S.-foreign trade will receive a demurrage and/or detention invoice or an estimated range of 1,135,000 and 2,270,000 invoices annually.
                </P>
                <P>
                    <E T="03">Type of Respondents:</E>
                     VOCCs, MTOs, and NVOCCs are required to include specific information on their demurrage and detention invoices sent to billed parties.
                </P>
                <P>
                    <E T="03">Number of Annual Respondents:</E>
                     The Commission anticipates an annual respondent universe of 354 VOCCs and MTOs. The Commission did not include NVOCCs in its annual respondent universe because in most, if not all cases, NVOCCs pass through the demurrage and detention charges it receives to their customers. Because NVOCCs are passing through the charges they are not collecting the required minimum information themselves.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     The Commission estimates a one-time burden of an estimated 25 hours per respondent to integrate the required billing information elements into their existing invoicing system. After this initial burden, the Commission anticipates that the estimated time to create and retain each demurrage or detention invoice to be six minutes or 0.1 hours.
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     The Commission estimates a one-time burden for respondents to integrate the additional billing information elements, required by OSRA 2022 and by the proposed rule, into their existing invoicing system to be 8,850 person-hours and $882,522. After this initial integration, the Commission estimates the total annual burden to provide demurrage and detention invoices and to ensure accuracy to be 113,500-227,000 person-hours and $6,339,020-$12,678,040.
                </P>
                <P>Comments are invited on:</P>
                <P>• Whether the collection of information is necessary for the proper performance of the functions of the Commission, including whether the information will have practical utility;</P>
                <P>• Whether the Commission's estimate for the burden of the information collection is accurate;</P>
                <P>• Ways to enhance the quality, utility, and clarity of the information to be collected;</P>
                <P>• Ways to minimize the burden of the collection of information on respondents, including the use of automated collection techniques or other forms of information technology.</P>
                <P>
                    Please submit any comments, identified by the docket number in the heading of this document, by the methods described in the 
                    <E T="02">ADDRESSES</E>
                     section of this document.
                    <PRTPAGE P="62357"/>
                </P>
                <HD SOURCE="HD2">Executive Order 12988 (Civil Justice Reform)</HD>
                <P>This proposed rule meets the applicable standards in E.O. 12988 titled, “Civil Justice Reform,” to minimize litigation, eliminate ambiguity, and reduce burden.</P>
                <HD SOURCE="HD2">Regulation Identifier Number</HD>
                <P>
                    The Commission assigns a regulation identifier number (RIN) to each regulatory action listed in the Unified Agenda of Federal Regulatory and Deregulatory Actions (Unified Agenda). The Regulatory Information Service Center publishes the Unified Agenda in April and October of each year. You may use the RIN contained in the heading at the beginning of this document to find this action in the Unified Agenda, available at 
                    <E T="03">https://www.reginfo.gov/public/do/eAgendaMain.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 46 CFR Part 541</HD>
                    <P>Demurrage and detention; Common carriers; Exports; Imports; Marine terminal operators.</P>
                </LSTSUB>
                <AMDPAR>For the reasons set forth in the preamble, the Federal Maritime Commission proposes to add 46 CFR part 541 as follows:</AMDPAR>
                <PART>
                    <HD SOURCE="HED">PART 541—DEMURRAGE AND DETENTION</HD>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart A—Demurrage and Detention Billing Requirements</HD>
                    </SUBPART>
                    <CONTENTS>
                        <SECHD>Sec.</SECHD>
                        <SECTNO>541.1</SECTNO>
                        <SUBJECT>Purpose</SUBJECT>
                        <SECTNO>541.2</SECTNO>
                        <SUBJECT>Scope and applicability</SUBJECT>
                        <SECTNO>541.3</SECTNO>
                        <SUBJECT>Definitions</SUBJECT>
                        <SECTNO>541.4</SECTNO>
                        <SUBJECT>Properly issued invoices</SUBJECT>
                        <SECTNO>541.5</SECTNO>
                        <SUBJECT>Failure to include required information</SUBJECT>
                        <SECTNO>541.6</SECTNO>
                        <SUBJECT>Contents of invoice</SUBJECT>
                        <SECTNO>541.7</SECTNO>
                        <SUBJECT>Issuance of demurrage and detention invoices</SUBJECT>
                        <SECTNO>541.8</SECTNO>
                        <SUBJECT>Requests for fee mitigation, refund, or waiver</SUBJECT>
                        <SECTNO>541.9-541.98</SECTNO>
                        <SUBJECT>[Reserved]</SUBJECT>
                        <SECTNO>541.99</SECTNO>
                        <SUBJECT>OMB control number assigned pursuant to the Paperwork Reduction Act</SUBJECT>
                    </CONTENTS>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart B [Reserved]</HD>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P> 5 U.S.C. 553; 46 U.S.C. 40307, 40501-40503, 41101-41106, 40901-40904, and 46105; and 46 CFR 515.23.</P>
                        </AUTH>
                    </SUBPART>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart A—Billing Requirements and Practices</HD>
                        <SECTION>
                            <SECTNO>§ 541.1</SECTNO>
                            <SUBJECT>Purpose</SUBJECT>
                            <P>This part establishes the minimum information that must be included on or with demurrage and detention invoices. It also establishes procedures that must be adhered to when invoicing for demurrage or detention.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 541.2</SECTNO>
                            <SUBJECT>Scope and applicability</SUBJECT>
                            <P>(a) This part sets forth regulations governing any invoice issued by an ocean common carrier, marine terminal operator, or non-vessel operating common carrier to a billed party or their designated agent for the collection of demurrage or detention charges.</P>
                            <P>(b) This regulation does not govern the billing relationships among and between ocean common carriers and marine terminal operators.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 541.3</SECTNO>
                            <SUBJECT>Definitions</SUBJECT>
                            <P>In addition to the definitions set forth in 46 U.S.C. 40102, when used in this part:</P>
                            <P>
                                <E T="03">Billing dispute</E>
                                 means any disagreement with respect to the validity of the charges, or the method of invoicing raised by the billed party or its agent to the billing party.
                            </P>
                            <P>
                                <E T="03">Billed party</E>
                                 means the person receiving the demurrage or detention invoice and who is responsible for the payment of any incurred demurrage or detention charge.
                            </P>
                            <P>
                                <E T="03">Billing party</E>
                                 means the ocean common carrier, marine terminal operator, or non-vessel operating common carrier who issues a demurrage or detention invoice.
                            </P>
                            <P>
                                <E T="03">Demurrage or detention</E>
                                 mean any charges, including “per diem” charges, assessed by ocean common carriers, marine terminal operators, or non-vessel operating common carriers related to the use of marine terminal space (
                                <E T="03">e.g.,</E>
                                 land) or shipping containers, but not including freight charges.
                            </P>
                            <P>
                                <E T="03">Demurrage or detention invoice</E>
                                 means any statement of charges printed, written, or accessible online that documents an assessment of demurrage or detention charges.
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 541.4</SECTNO>
                            <SUBJECT>Properly issued invoices</SUBJECT>
                            <P>A properly issued invoice is a demurrage or detention invoice issued by a billing party to the person for whose account the billing party provided ocean transportation or storage.</P>
                            <P>(a) This person must have contracted with the billing party for the carriage or storage of goods and is therefore responsible for the payment of any incurred demurrage or detention charge.</P>
                            <P>(b) A billing party cannot issue an invoice to any other person.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 541.5</SECTNO>
                            <SUBJECT>Failure to include required information</SUBJECT>
                            <P>Failure to include any of the required minimum information in this part in a demurrage or detention invoice eliminates any obligation of the billed party to pay the applicable invoice.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 541.6</SECTNO>
                            <SUBJECT>Contents of invoice.</SUBJECT>
                            <P>At a minimum, an invoice for demurrage or detention charges must include the following information:</P>
                            <P>
                                (a) 
                                <E T="03">Identifying information.</E>
                                 The invoice must contain sufficient information to enable the billed party to identify the container(s) to which the charges apply, including:
                            </P>
                            <P>(1) The Bill of Lading number(s);</P>
                            <P>(2) The container number(s);</P>
                            <P>(3) For imports, the port(s) of discharge; and</P>
                            <P>(4) The basis for why the invoiced party is the proper party of interest and thus liable for the charge.</P>
                            <P>
                                (b) 
                                <E T="03">Timing information.</E>
                                 The invoice must contain sufficient information to enable the billed party to identify the relevant time for which the charges apply, and the applicable due date for invoiced charges, including:
                            </P>
                            <P>(1) The billing date;</P>
                            <P>(2) The billing due date;</P>
                            <P>(3) The allowed free time in days;</P>
                            <P>(4) The start date of free time;</P>
                            <P>(5) The end date of free time;</P>
                            <P>(6) For imports, the container availability date;</P>
                            <P>(7) For exports, the earliest return date; and</P>
                            <P>(8) The specific date(s) for which demurrage and/or detention were charged.</P>
                            <P>
                                (c) 
                                <E T="03">Rate information.</E>
                                 The invoice must contain sufficient information to enable the billed party to identify the amount due and readily ascertain how that amount was calculated, including:
                            </P>
                            <P>(1) The total amount due;</P>
                            <P>
                                (2) The applicable detention or demurrage rule (
                                <E T="03">i.e.,</E>
                                 the tariff name and rule number, applicable service contract number and section, or applicable negotiated arrangement) on which the daily rate is based; and
                            </P>
                            <P>(3) The specific rate or rates per the applicable tariff rule or service contract.</P>
                            <P>
                                (d) 
                                <E T="03">Dispute information.</E>
                                 The invoice must contain sufficient information to enable the billed party to readily identify a contact to whom they may direct questions or concerns related to the invoice and understand the process to request fee mitigation, refund, or waiver, including:
                            </P>
                            <P>(1) The email, telephone number, or other appropriate contact information for questions or request for fee mitigation, refund, or waiver;</P>
                            <P>
                                (2) The URL address of a publicly-accessible portion of the billing party's website that provides a detailed description of information or documentation that the billed party must provide to successfully request fee mitigation, refund, or waiver; and
                                <PRTPAGE P="62358"/>
                            </P>
                            <P>(3) Defined timeframes that comply with the billing practices in this part, during which the billed party must request a fee mitigation, refund, or waiver and within which the billing party will resolve such requests.</P>
                            <P>
                                (e) 
                                <E T="03">Certifications.</E>
                                 The invoice must contain statements from the billing party that:
                            </P>
                            <P>(1) The charges are consistent with any of the Federal Maritime Commission's rules related to demurrage and detention, including, but not limited to, this part and 46 CFR 545.5; and</P>
                            <P>(2) The billing party's performance did not cause or contribute to the underlying invoiced charges.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 541.7</SECTNO>
                            <SUBJECT>Issuance of demurrage and detention invoices.</SUBJECT>
                            <P>(a) A billing party must issue a demurrage or detention invoice within thirty (30) days from the date on which the charge was last incurred. If the billing party does not issue demurrage or detention invoices within the required timeframe, then the billed party is not required to pay the charge.</P>
                            <P>(b) If the billing party invoices the incorrect party, the correct billed party must receive an invoice within thirty (30) days from the date the incorrect party disputes the charges with the billing party. An invoice to the correct billed party must be issued within sixty (60) days after the charges were last incurred. If the billed party does not receive demurrage or detention invoices within the required timeframe, then it is not required to pay the charge.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 541.8</SECTNO>
                            <SUBJECT>Requests for fee mitigation, refund, or waiver.</SUBJECT>
                            <P>(a) If a billed party requests mitigation, refund, or waiver of fees from the billing party, it must submit the request within thirty (30) days of receiving the invoice.</P>
                            <P>(b) If a billing party receives a fee mitigation, refund, or waiver request from a billed party, the billing party must resolve the request within thirty (30) days of receiving such a request. If the billing party fails to resolve the fee mitigation, refund, or waiver request within the 30-day deadline, the billed party is not required to pay the charge at issue.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 541.9-541.98</SECTNO>
                            <SUBJECT>[Reserved]</SUBJECT>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 541.99</SECTNO>
                            <SUBJECT>OMB control number assigned pursuant to the Paperwork Reduction Act.</SUBJECT>
                            <P>The Commission has received Office of Management and Budget approval for this collection of information pursuant to the Paperwork Reduction Act of 1995, as amended. In accordance with that Act, agencies are required to display a currently valid control number. In this regard, the valid control number for this collection of information is 3072-XXXX.</P>
                        </SECTION>
                    </SUBPART>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart B [Reserved]</HD>
                    </SUBPART>
                    <SIG>
                        <P>By the Commission.</P>
                        <NAME>William Cody,</NAME>
                        <TITLE>Secretary.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22290 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6730-02-P</BILCOD>
        </PRORULE>
    </PRORULES>
    <VOL>87</VOL>
    <NO>198</NO>
    <DATE>Friday, October 14, 2022</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NOTICES>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="62359"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <DEPDOC>[Docket Number: USDA-2022-0015]</DEPDOC>
                <SUBJECT>Notice of Request for Public Comment on Providing Financial Assistance for Producers and Landowners Determined To Have Experienced Discrimination</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Secretary, U.S. Department of Agriculture.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for information.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Section 22007 of the Inflation Reduction Act of 2022 (“section 22007”) directs the U.S. Department of Agriculture (USDA) to provide financial assistance for producers and landowners determined to have experienced discrimination in the Department of Agriculture's farm lending programs. To help us design and implement policy to best provide the direct support called for by this provision, USDA is seeking input from the public to ensure that relevant information is considered. Accordingly, USDA is interested in your comments in response to the topics, categories, and questions presented in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this document.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Interested persons are invited to submit comments on or before 11:59 p.m. Eastern Time November 14, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments may be submitted online via the Federal eRulemaking Portal. Go to 
                        <E T="03">https://www.regulations.gov</E>
                         and search for the Docket No. USDA-2022-0015. Follow the online instructions for submitting comments. All comments received will be posted without change and publicly available on 
                        <E T="03">www.regulations.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Liz Archuleta; telephone: (202) 720-7095; Email: 
                        <E T="03">EquityRFI@usda.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Section 22007 provides $2.2 billion for financial assistance for producers determined to have experienced discrimination in the Department of Agriculture's farm lending programs prior to January 1, 2021.</P>
                <P>When USDA commits acts of discrimination, it not only hurts the individuals and entities directly impacted, it also breaks a trust with those directly affected and the communities of which they are part. This program provides USDA the ability to provide financial assistance for those who have been harmed in USDA's farm lending programs, but more fundamentally is about providing USDA the tools to rebuild that trust by directly acknowledging the wrongs that have been committed and taking concrete actions to offset those wrongs. It is critical that USDA restore and maintain the trust of individuals and communities where trust has been broken. A trusting and mutually supportive relationship between agricultural producers and USDA is essential to a safe and secure food supply chain and our nation's ability to produce food, feed, and fiber that is key to our daily lives and the US economy. USDA is seeking input from individuals, stakeholder organizations, and others on the options for implementation of this provision.</P>
                <P>In doing so, USDA also aims to continue to demonstrate its commitment to upholding civil rights and making progress towards establishing and maintaining trust with agricultural producers.</P>
                <P>The purpose of this notice is to request information and input on how USDA should implement this transformative authority. The input received relating to implementation of this program may inform future USDA equity activities.</P>
                <P>Specifically, USDA is requesting public comment on the following issues and on other implementation issues that are not included on this list.</P>
                <HD SOURCE="HD1">Issues for Consideration</HD>
                <P>The first issue in implementing section 22007 is the identification of those who are eligible for financial assistance. By the terms of the statute, relief under this provision is for “farmers, ranchers, or forest landowners determined to have experienced discrimination prior to January 1, 2021, in Department of Agriculture farm lending programs.” USDA specifically requests input from the public on this issue, including on questions such as:</P>
                <P>• How should USDA identify those who have experienced discrimination under the USDA farm loan programs?</P>
                <P>• What kind of documentation or evidence should be submitted in support of a determination of discrimination?</P>
                <P>The second issue in implementing section 22007 is for those determined eligible, what factors should be considered in determining the amount and type of financial assistance provided. Under section 22007, “the amount of financial assistance provided to a recipient may be not more than $500,000, as determined to be appropriate based on any consequences experienced from the discrimination.” USDA specifically requests input from the public on this issue, including on questions such as:</P>
                <P>• Should USDA attempt to estimate only economic losses or also non-economic losses of those who have suffered discrimination in USDA farm loan programs when calculating the amount of financial assistance provided? Alternatively, should USDA apply a fixed, uniform formula for calculating the amount of financial assistance provided? In any case, how should that calculation be done?</P>
                <P>• Should previous payments received for past claims of discrimination be considered in determining financial assistance available under section 22007?</P>
                <P>• Are there forms of non-monetary equitable relief that can be used in conjunction with the financial assistance provided under section 22007 for those who have experienced discrimination and who continue to farm or continue to participate in USDA farm loan programs?</P>
                <P>• How, if at all, should USDA consider the recency of the discrimination as determined by the Secretary when determining appropriate level of financial assistance?</P>
                <P>
                    The third issue concerns the administration of the financial assistance program, including the role of the third-party entity (or entities) versus the role of USDA, selection of the third-party entity (or entities), and key components relating to the process of determining delivery of financial assistance. Section 22007 provides that the “program shall be administered 
                    <PRTPAGE P="62360"/>
                    through 1 or more qualified nongovernmental entities selected by the Secretary subject to standards set and enforced by the Secretary.” USDA specifically requests input from the public on this issue, including on questions such as:
                </P>
                <P>• What specific functions should the third-party entity (or entities) perform in assisting USDA in delivering financial assistance provided for under section 22007 to those who suffered discrimination under the USDA farm loan programs?</P>
                <P>• What criteria should USDA use in the selection of the third-party entity (or entities)?</P>
                <P>• What guidance should USDA provide to the selected entity (or entities)?</P>
                <P>The fourth issue is the linkage or leveraging, if any, between the financial assistance provided in this program and other USDA programs. USDA specifically requests input from the public on this issue, including on questions such as:</P>
                <P>• How should USDA use programs, funding, financial support, and other authorities, in conjunction with section 22007 financial assistance, to provide support for those who have experienced discrimination under the USDA farm loan programs?</P>
                <HD SOURCE="HD1">Civil Rights Complaint</HD>
                <P>Information submitted through this document will not be processed as a civil rights complaint and will not be considered a complaint for determining whether a complaint was timely submitted.</P>
                <P>
                    To file a discrimination complaint on interactions with USDA, you can complete the form: 
                    <E T="03">https://www.usda.gov/sites/default/files/documents/Complain_combined_6_8_12_508.pdf.</E>
                </P>
                <P>You may submit the discrimination complaint to USDA by any of the following methods:</P>
                <P>
                    <E T="03">Mail:</E>
                     U.S. Department of Agriculture, Director, Center for Civil Rights Enforcement, 1400 Independence Avenue SW, Washington, DC 20250-9410.
                </P>
                <P>
                    <E T="03">Fax:</E>
                     (202) 690-7442; or
                </P>
                <P>
                    <E T="03">Email: program.intake@usda.gov.</E>
                </P>
                <P>If you need any assistance completing the form, call the following phone numbers:</P>
                <P>• (202) 260-1026 (Local),</P>
                <P>• (866) 632-9992 (Toll-free Customer Service),</P>
                <P>• (800) 877-8339 (Local or Federal relay), or</P>
                <P>• (866) 377-8642 (Relay voice users).</P>
                <HD SOURCE="HD1">USDA Non-Discrimination Policy</HD>
                <P>In accordance with Federal civil rights law and U.S. Department of Agriculture (USDA) civil rights regulations and policies, USDA, its Agencies, offices, and employees, and institutions participating in or administering USDA programs are prohibited from discriminating based on race, color, national origin, religion, sex, gender identity (including gender expression), sexual orientation, disability, age, marital status, family or parental status, income derived from a public assistance program, political beliefs, or reprisal or retaliation for prior civil rights activity, in any program or activity conducted or funded by USDA (not all bases apply to all programs). Remedies and complaint filing deadlines vary by program or incident.</P>
                <P>Persons with disabilities who require alternative means of communication for program information (for example, braille, large print, audiotape, American Sign Language, etc.) should contact the responsible agency or USDA TARGET Center at (202) 720-2600 or 844-433-2774 (toll-free nationwide). Additionally, program information may be made available in languages other than English.</P>
                <P>
                    To file a program discrimination complaint, complete the USDA Program Discrimination Complaint Form, AD-3027, found online at 
                    <E T="03">https://www.usda.gov/oascr/how-to-file-a-program-discrimination-complaint</E>
                     and at any USDA office or write a letter addressed to USDA and provide in the letter all the information requested in the form. To request a copy of the complaint form, call (866) 632-9992. Submit your completed form or letter to USDA by mail to: U.S. Department of Agriculture, Office of the Assistant Secretary for Civil Rights, 1400 Independence Avenue SW, Washington, DC 20250-9410 or email: 
                    <E T="03">OAC@usda.gov.</E>
                </P>
                <P>USDA is an equal opportunity provider, employer, and lender.</P>
                <SIG>
                    <NAME>Elizabeth Archuleta,</NAME>
                    <TITLE>Director, Office of Intergovernmental &amp; External Affairs, U.S. Department of Agriculture.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22435 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-90-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">COMMISSION ON CIVIL RIGHTS</AGENCY>
                <SUBJECT>Notice of Public Meeting of the Nevada Advisory Committee to the U.S. Commission on Civil Rights</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Commission on Civil Rights.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Announcement of virtual business meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Notice is hereby given, pursuant to the provisions of the rules and regulations of the U.S. Commission on Civil Rights (Commission) and the Federal Advisory Committee Act, that the Nevada Advisory Committee (Committee) to the U.S. Commission on Civil Rights will hold a virtual business meeting via 
                        <E T="03">ZoomGov</E>
                         at 3:00 p.m. Pacific on Monday, December 12, 2022. The purpose of the meeting is to begin planning upcoming web hearings on civil rights and teacher shortages.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will take place on Monday, December 12, 2022, from 3:00 p.m.-4:30 p.m. PT.</P>
                    <P>
                        <E T="03">Link To Join (Audio/Visual): https://tinyurl.com/pm669pht.</E>
                    </P>
                    <P>
                        <E T="03">Telephone (Audio Only):</E>
                         Dial (833) 435-1820 USA Toll Free; Meeting ID: 160 798 5959.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ana Fortes, Designated Federal Officer, at 
                        <E T="03">afortes@usccr.gov</E>
                         or (202) 519-2938.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Committee meetings are available to the public through the conference link above. Any interested member of the public may listen to the meeting. An open comment period will be provided to allow members of the public to make a statement as time allows. If joining via phone, callers can expect to incur regular charges for calls they initiate over wireless lines, according to their wireless plan. The Commission will not refund any incurred charges. Individuals who are deaf, deafblind, and hard of hearing may also follow the proceedings by first calling the Federal Relay Service at (800) 877-8339 and providing the Service with the conference details found through registering at the web link above. To request additional accommodations, please email 
                    <E T="03">afortes@usccr.gov</E>
                     at least ten (10) days prior to the meeting.
                </P>
                <P>
                    Members of the public are also entitled to submit written comments; the comments must be received within 30 days following the meeting. Written comments may be emailed to Angelica Trevino at 
                    <E T="03">atrevino@usccr.gov.</E>
                     Persons who desire additional information may contact the Regional Programs Coordination Unit at (312) 353-8311.
                </P>
                <P>
                    Records generated from this meeting may be inspected and reproduced at the Regional Programs Coordination Unit Office, as they become available, both before and after the meeting. Records of the meeting will be available via 
                    <E T="03">www.facadatabase.gov</E>
                     under the Commission on Civil Rights, Nevada Advisory Committee link. Persons 
                    <PRTPAGE P="62361"/>
                    interested in the work of this Committee are directed to the Commission's website, 
                    <E T="03">http://www.usccr.gov,</E>
                     or may contact the Regional Programs Coordination Unit at the above phone number.
                </P>
                <HD SOURCE="HD1">Agenda</HD>
                <FP SOURCE="FP-2">I. Welcome, Roll Call, and Announcements</FP>
                <FP SOURCE="FP-2">II. Review Project Proposal</FP>
                <FP SOURCE="FP-2">III. Plan for Web Hearings</FP>
                <FP SOURCE="FP1-2">a. Speakers</FP>
                <FP SOURCE="FP1-2">b. Dates</FP>
                <FP SOURCE="FP-2">IV. Public Comment</FP>
                <FP SOURCE="FP-2">V. Discuss Next Steps</FP>
                <FP SOURCE="FP-2">VI. Adjournment</FP>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>David Mussatt,</NAME>
                    <TITLE>Supervisory Chief, Regional Programs Unit.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22374 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">COMMISSION ON CIVIL RIGHTS</AGENCY>
                <SUBJECT>Notice of Public Meeting of the Nevada Advisory Committee to the U.S. Commission on Civil Rights</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Commission on Civil Rights.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Announcement of virtual business meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Notice is hereby given, pursuant to the provisions of the rules and regulations of the U.S. Commission on Civil Rights (Commission) and the Federal Advisory Committee Act, that the Nevada Advisory Committee (Committee) to the U.S. Commission on Civil Rights will hold a virtual business meeting via 
                        <E T="03">ZoomGov</E>
                         at 3 p.m. Pacific on Thursday, October 20, 2022. The purpose of the meeting is to narrow down and discuss details of project proposal on civil rights and teacher shortages.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will take place on Thursday, October 20, 2022, from 3 p.m.-4:30 p.m. PT.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P> </P>
                    <P>
                        <E T="03">Link to Join (Audio/Visual): https://tinyurl.com/3tp9bpec.</E>
                    </P>
                    <P>
                        <E T="03">Telephone (Audio Only):</E>
                         Dial (833) 435-1820 USA Toll Free; Meeting ID: 160 889 4050
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ana Fortes, Designated Federal Officer, at 
                        <E T="03">afortes@usccr.gov</E>
                         or (202) 519-2938.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Committee meetings are available to the public through the conference link above. Any interested member of the public may listen to the meeting. An open comment period will be provided to allow members of the public to make a statement as time allows. If joining via phone, callers can expect to incur regular charges for calls they initiate over wireless lines, according to their wireless plan. The Commission will not refund any incurred charges. Individuals who are deaf, deafblind, and hard of hearing may also follow the proceedings by first calling the Federal Relay Service at (800) 877-8339 and providing the Service with the conference details found through registering at the web link above. To request additional accommodations, please email 
                    <E T="03">afortes@usccr.gov</E>
                     at least ten (10) days prior to the meeting.
                </P>
                <P>
                    Members of the public are also entitled to submit written comments; the comments must be received within 30 days following the meeting. Written comments may be emailed to Angelica Trevino at 
                    <E T="03">atrevino@usccr.gov.</E>
                     Persons who desire additional information may contact the Regional Programs Coordination Unit at (312) 353-8311.
                </P>
                <P>
                    Records generated from this meeting may be inspected and reproduced at the Regional Programs Coordination Unit Office, as they become available, both before and after the meeting. Records of the meeting will be available via 
                    <E T="03">www.facadatabase.gov</E>
                     under the Commission on Civil Rights, Nevada Advisory Committee link. Persons interested in the work of this Committee are directed to the Commission's website, 
                    <E T="03">http://www.usccr.gov,</E>
                     or may contact the Regional Programs Coordination Unit at the above phone number.
                </P>
                <HD SOURCE="HD1">Agenda</HD>
                <FP SOURCE="FP-2">I. Welcome, Roll Call, and Announcements</FP>
                <FP SOURCE="FP-2">II. Discuss Civil Rights Topics</FP>
                <FP SOURCE="FP-2">III. Discuss Scope of Selected Topic</FP>
                <FP SOURCE="FP-2">IV. Public Comment</FP>
                <FP SOURCE="FP-2">V. Discuss Next Steps</FP>
                <FP SOURCE="FP-2">VI. Adjournment</FP>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>David Mussatt,</NAME>
                    <TITLE>Supervisory Chief, Regional Programs Unit.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22379 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">COMMISSION ON CIVIL RIGHTS</AGENCY>
                <SUBJECT>Notice of Public Meetings of the Virginia Advisory Committee to the U.S. Commission on Civil Rights</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Commission on Civil Rights.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Announcement of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given, pursuant to the provisions of the rules and regulations of the U.S. Commission on Civil Rights (Commission) and the Federal Advisory Committee Act, that the Virginia Advisory Committee (Committee) will hold a web meeting via Zoom on Tuesday, November 1, 2022, at 12:00 p.m. Eastern Time. The purpose of the meeting is to discuss identified findings and recommendations from previous panels on police oversight and accountability in Virginia.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be held on: Tuesday, November 1, 2022, at 12:00 p.m. Eastern Time.</P>
                    <P>
                        <E T="03">Meeting Link: https://www.zoomgov.com/j/1602995985.</E>
                    </P>
                    <P>
                        <E T="03">Join by Phone:</E>
                         1-551-285-1373 US; Meeting ID: 160 299 5985.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Melissa Wojnaroski, DFO, at 
                        <E T="03">mwojnaroski@usccr.gov</E>
                         or 1-202-618-4158.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Members of the public may listen to this discussion through the above call-in number (audio only) or online registration link (audio/visual). An open comment period will be provided to allow members of the public to make a statement as time allows. Callers can expect to incur regular charges for calls they initiate over wireless lines, according to their wireless plan. The Commission will not refund any incurred charges. Callers will incur no charge for calls they initiate over land-line connections to the toll-free telephone number. Individual who is deaf, deafblind, and hard of hearing may also follow the proceedings by first calling the Federal Relay Service at 1-800-877-8339 and providing the Service with the conference call number and conference ID number.</P>
                <P>
                    Members of the public are entitled to submit written comments; the comments must be received in the regional office within 30 days following the meeting. Written comments may be emailed to Melissa Wojnaroski at 
                    <E T="03">mwojnaroski@usccr.gov.</E>
                </P>
                <P>
                    Records generated from this meeting may be inspected and reproduced at the Regional Programs Unit Office, as they become available, both before and after the meeting. Records of the meeting will be available via 
                    <E T="03">www.facadatabase.gov</E>
                     under the Commission on Civil Rights, Virginia Advisory Committee link. Persons interested in the work of this Committee are directed to the Commission's website, 
                    <E T="03">http://www.usccr.gov,</E>
                     or may contact the Regional Programs Unit at the above email or street address.
                </P>
                <HD SOURCE="HD1">Agenda</HD>
                <FP SOURCE="FP-2">
                    I. Welcome &amp; Roll Call
                    <PRTPAGE P="62362"/>
                </FP>
                <FP SOURCE="FP-2">II. Approval of Minutes</FP>
                <FP SOURCE="FP-2">III. Announcements and Updates</FP>
                <FP SOURCE="FP-2">IV. Discussion: Report Draft</FP>
                <FP SOURCE="FP-2">V. Next Steps</FP>
                <FP SOURCE="FP-2">VI. Public Comments</FP>
                <FP SOURCE="FP-2">VII. Adjournment</FP>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>David Mussatt,</NAME>
                    <TITLE>Supervisory Chief, Regional Programs Unit.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22380 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">COMMISSION ON CIVIL RIGHTS</AGENCY>
                <SUBJECT>Notice of Public Meetings of the Pennsylvania Advisory Committee to the U.S. Commission on Civil Rights</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Commission on Civil Rights.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Announcement of meetings.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given, pursuant to the provisions of the rules and regulations of the U.S. Commission on Civil Rights (Commission) and the Federal Advisory Committee Act that the Pennsylvania Advisory Committee (Committee) to the U.S. Commission on Civil Rights will hold series of web-based panel discussions on Friday October 28, 2022 from 12 p.m.-2 p.m. eastern time, and Tuersday November 2, 2022 from 12 p.m.-2 p.m. eastern time. The purpose of these meetings is for the Committee to hear testimony regarding civil rights and fair housing in the state.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P> </P>
                    <P>
                        • 
                        <E T="03">Panel VI:</E>
                         Friday October 28, 2022 from 12 p.m.-2 p.m. eastern time.
                    </P>
                    <P>
                        <E T="03">Link To Join (Audio/Visual): https://www.zoomgov.com/j/1607360741.</E>
                    </P>
                    <P>
                        <E T="03">Telephone (Audio Only):</E>
                         (833) 435-1820 Toll Free; Meeting ID: 160 736 0741.
                    </P>
                    <P>
                        • 
                        <E T="03">Panel VII:</E>
                         Tuesday November 2, 2022 from 12 p.m.-2 p.m. eastern time.
                    </P>
                    <P>
                        <E T="03">Link To Join (Audio/Visual): https://www.zoomgov.com/j/1616092536.</E>
                    </P>
                    <P>
                        <E T="03">Telephone (Audio Only):</E>
                         (833) 435-1820; Toll Free Meeting ID: 161 609 2536.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Melissa Wojnaroski, DFO, at 
                        <E T="03">mwojnaroski@usccr.gov</E>
                         or (202) 618-4158.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Members of the public may listen to these discussions.</P>
                <P>
                    Committee meetings are available to the public through the above listed online registration link. Telephone access will be provided upon registration for those who are unavailable to join the meeting online. An open comment period will be provided to allow members of the public to make a statement as time allows. Callers can expect to incur regular charges for calls they initiate over wireless lines, according to their wireless plan. The Commission will not refund any incurred charges. American Sign Language interpretation will be provided. Indivudals with disabilities requiring other accommodations may contact Corrine Sanders at 
                    <E T="03">csanders@usccr.gov</E>
                     10 days prior to the meeting to make their request.
                </P>
                <P>
                    Members of the public are also entitled to submit written comments; the comments must be received in the regional office within 30 days following the meeting. Written comments may be emailed to 
                    <E T="03">csanders@usccr.gov.</E>
                     Persons who desire additional information may contact the Regional Programs Unit at (202) 618-4158.
                </P>
                <P>
                    Records generated from this meeting may be inspected and reproduced at the Regional Programs Unit Office, as they become available, both before and after the meeting. Records of the meeting will be available via 
                    <E T="03">www.facadatabase.gov</E>
                     under the Commission on Civil Rights, Pennsylvania Advisory Committee link. Persons interested in the work of this Committee are directed to the Commission's website, 
                    <E T="03">http://www.usccr.gov,</E>
                     or may contact the Regional Programs Unit at the above email address.
                </P>
                <HD SOURCE="HD1">Agenda</HD>
                <FP SOURCE="FP-1">Welcome and Roll Call</FP>
                <FP SOURCE="FP-1">Panel Discussion: Civil Rights and Fair Housing in Pennsylvania</FP>
                <FP SOURCE="FP-1">Public Comment</FP>
                <FP SOURCE="FP-1">Adjournment</FP>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>David Mussatt,</NAME>
                    <TITLE>Supervisory Chief, Regional Programs Unit.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22383 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">COMMISSION ON CIVIL RIGHTS</AGENCY>
                <SUBJECT>Notice of Public Meeting of the Indiana Advisory Committee to the U.S. Commission on Civil Rights</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Commission on Civil Rights.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Announcement of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given, pursuant to the provisions of the rules and regulations of the U.S. Commission on Civil Rights (Commission) and the Federal Advisory Committee Act that the Indiana Advisory Committee (Committee) to the U.S. Commission on Civil Rights will hold planning meetings via Zoom on Tuesday, November 1, 2022, and December 6, 2022 at 1 p.m. (ET) to discuss and select the topic for the Committee's civil rights project; votes may be taken.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will take place on Tuesday, November 1, 2022, and December 6, 2022, from 1 p.m.-2 p.m. (ET).</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P> </P>
                    <P>
                        <E T="03">Meeting Link (Audio/Visual): https://www.zoomgov.com/j/1601951921.</E>
                    </P>
                    <P>
                        <E T="03">Telephone (Audio Only):</E>
                         Dial 833-435-1820 USA Toll Free; Meeting ID: 160 195 1921
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ivy Davis, DFO, at 
                        <E T="03">idavis@usccr.gov</E>
                         or 202- 376-7533, or email Sarah Villanueva, Support Specialist, at 
                        <E T="03">svillanueva@usccr.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Members of the public can listen to these discussions. Committee meetings are available to the public through the above call-in number. Any interested member of the public may call this number and listen to the meeting. An open comment period will be provided to allow members of the public to make a statement as time allows. Callers can expect to incur regular charges for calls they initiate over wireless lines, according to their wireless plan. The Commission will not refund any incurred charges. Callers will incur no charge for calls they initiate over land-line connections to the toll-free telephone number. Individuals who are deaf, deafblind and hard of hearing may follow the proceedings by first calling the Federal Relay Service at 800-877-8339 and providing the Service with the conference call number and conference ID number.</P>
                <P>
                    Members of the public are also entitled to submit written comments; the comments must be received in the regional office within 30 days following the meeting. Written comments may be emailed to Sarah Villanueva at 
                    <E T="03">svillanueva@usccr.gov.</E>
                     Persons who desire additional information may contact Ivy Davis at 202-539-8468.
                </P>
                <P>
                    Records generated from this meeting may be inspected and reproduced at the Regional Programs Unit Office, as they become available, both before and after the meeting. Records of the meeting will be available via 
                    <E T="03">www.facadatabase.gov</E>
                     under the Commission on Civil Rights, Indiana Advisory Committee link. Persons interested in the work of this Committee are directed to the Commission's website, 
                    <E T="03">http://www.usccr.gov,</E>
                     or may contact the Regional Programs Unit at the above email or street address.
                </P>
                <HD SOURCE="HD1">Agenda</HD>
                <FP SOURCE="FP-2">
                    I. Roll Call
                    <PRTPAGE P="62363"/>
                </FP>
                <FP SOURCE="FP-2">II. Welcome</FP>
                <FP SOURCE="FP-2">III. Project Planning</FP>
                <FP SOURCE="FP-2">IV. Other Business</FP>
                <FP SOURCE="FP-2">V. Next Meeting</FP>
                <FP SOURCE="FP-2">VI. Public Comments</FP>
                <FP SOURCE="FP-2">VII. Adjourn</FP>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>David Mussatt,</NAME>
                    <TITLE>Supervisory Chief, Regional Programs Unit.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22384 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">COMMISSION ON CIVIL RIGHTS</AGENCY>
                <SUBJECT>Notice of Public Meeting of the Nevada Advisory Committee to the U.S. Commission on Civil Rights</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Commission on Civil Rights.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Announcement of virtual business meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Notice is hereby given, pursuant to the provisions of the rules and regulations of the U.S. Commission on Civil Rights (Commission) and the Federal Advisory Committee Act, that the Nevada Advisory Committee (Committee) to the U.S. Commission on Civil Rights will hold a virtual business meeting via 
                        <E T="03">ZoomGov</E>
                         at 3:00 p.m. Pacific on Monday, November 14, 2022. The purpose of the meeting is to review and vote on project proposal on civil rights and teacher shortages.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will take place on Monday, November 14, 2022, from 3:00 p.m.-4:30 p.m. PT.</P>
                    <P>
                        <E T="03">Link to Join (Audio/Visual): https://tinyurl.com/yc4vfbpj</E>
                    </P>
                    <P>
                        <E T="03">Telephone (Audio Only):</E>
                         Dial (833) 435-1820 USA Toll Free; Meeting ID: 160 932 8862
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ana Fortes, Designated Federal Officer, at 
                        <E T="03">afortes@usccr.gov</E>
                         or (202) 519-2938.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Committee meetings are available to the public through the conference link above. Any interested member of the public may listen to the meeting. An open comment period will be provided to allow members of the public to make a statement as time allows. If joining via phone, callers can expect to incur regular charges for calls they initiate over wireless lines, according to their wireless plan. The Commission will not refund any incurred charges. Individuals who are deaf, deafblind, and hard of hearing may also follow the proceedings by first calling the Federal Relay Service at (800) 877-8339 and providing the Service with the conference details found through registering at the web link above. To request additional accommodations, please email 
                    <E T="03">afortes@usccr.gov</E>
                     at least ten (10) days prior to the meeting.
                </P>
                <P>
                    Members of the public are also entitled to submit written comments; the comments must be received within 30 days following the meeting. Written comments may be emailed to Angelica Trevino at 
                    <E T="03">atrevino@usccr.gov.</E>
                     Persons who desire additional information may contact the Regional Programs Coordination Unit at (312) 353-8311.
                </P>
                <P>
                    Records generated from this meeting may be inspected and reproduced at the Regional Programs Coordination Unit Office, as they become available, both before and after the meeting. Records of the meeting will be available via 
                    <E T="03">www.facadatabase.gov</E>
                     under the Commission on Civil Rights, Nevada Advisory Committee link. Persons interested in the work of this Committee are directed to the Commission's website, 
                    <E T="03">http://www.usccr.gov,</E>
                     or may contact the Regional Programs Coordination Unit at the above phone number.
                </P>
                <HD SOURCE="HD1">Agenda</HD>
                <FP SOURCE="FP-2">I. Welcome, Roll Call, and Announcements</FP>
                <FP SOURCE="FP-2">II. Review Project Proposal</FP>
                <FP SOURCE="FP-2">III. Public Comment</FP>
                <FP SOURCE="FP-2">IV. Discuss Next Steps</FP>
                <FP SOURCE="FP-2">V. Adjournment</FP>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>David Mussatt,</NAME>
                    <TITLE>Supervisory Chief, Regional Programs Unit.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22375 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Census Bureau</SUBAGY>
                <SUBJECT>Agency Information Collection Activities; Submission to the Office of Management and Budget (OMB) for Review and Approval; Comment Request; Generic Clearance for Questionnaire Pretesting Research</SUBJECT>
                <P>
                    The Department of Commerce will submit the following information collection request to the Office of Management and Budget (OMB) for review and clearance in accordance with the Paperwork Reduction Act of 1995, on or after the date of publication of this notice. We invite the general public and other Federal agencies to comment on proposed, and continuing information collections, which helps us assess the impact of our information collection requirements and minimize the public's reporting burden. Public comments were previously requested via the 
                    <E T="04">Federal Register</E>
                     on 06/29/2022 during a 60-day comment period. This notice allows for an additional 30 days for public comments.
                </P>
                <P>
                    <E T="03">Agency:</E>
                     U.S. Census Bureau, Department of Commerce.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Generic Clearance for Questionnaire Pretesting Research.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0607-0725.
                </P>
                <P>
                    <E T="03">Form Number(s):</E>
                     Various.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Regular submission, Request for an Extension, without Change, of a Currently Approved Collection.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     5,500 per year.
                </P>
                <P>
                    <E T="03">Average Hours per Response:</E>
                     1 hour.
                </P>
                <P>
                    <E T="03">Burden Hours:</E>
                     5,500 hours annually.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     The information collected in this program of developing and testing questionnaires will be used by staff from the Census Bureau and sponsoring agencies to evaluate and improve the quality of the data in the surveys and censuses that are ultimately conducted.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals or households, businesses or other for profit, farms.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     TBD.
                </P>
                <P>
                    <E T="03">Respondent's Obligation:</E>
                     Voluntary.
                </P>
                <P>
                    <E T="03">Legal Authority:</E>
                     Data collection for this project is authorized under the authorizing legislation for the questionnaire being tested. This may be Title 13, Sections 131, 141, 161, 181, 182, 193, and 301 for Census Bureau-sponsored surveys, and Title 13, Section 8(b) for surveys sponsored by other Federal agencies. We do not now know what other titles will be referenced, since we do not know what survey questionnaires will be pretested during the course of the clearance.
                </P>
                <P>
                    This information collection request may be viewed at 
                    <E T="03">www.reginfo.gov.</E>
                     Follow the instructions to view the Department of Commerce collections currently under review by OMB.
                </P>
                <P>
                    Written comments and recommendations for the proposed information collection should be submitted within 30 days of the publication of this notice on the following website 
                    <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                     Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function and entering either the title of the collection or the OMB Control Number 0607-0725.
                </P>
                <SIG>
                    <NAME>Sheleen Dumas,</NAME>
                    <TITLE>Department PRA Clearance Officer, Office of the Chief Information Officer, Commerce Department.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22362 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-07-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="62364"/>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <DEPDOC>[RTID 0648-XC359]</DEPDOC>
                <SUBJECT>Takes of Marine Mammals Incidental to Specified Activities; Taking Marine Mammals Incidental to Tugs Towing Drill Rig in Cook Inlet, 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>Notice; issuance of incidental harassment authorizations.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the regulations implementing the Marine Mammal Protection Act (MMPA) as amended, notification is hereby given that NMFS has issued two incidental harassment authorizations (IHAs) to Hilcorp Alaska LLC to incidentally harass, by Level B harassment only, marine mammals during tugs towing jack-up rig activity in Cook Inlet, Alaska.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>These authorizations are effective from September 14, 2022 through September 13, 2023 and September 14, 2023 through September 13, 2024.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Sara Young, Office of Protected Resources, NMFS, (301) 427-8401. Electronic copies of the application and supporting documents, as well as a list of the references cited in this document, may be obtained online at: 
                        <E T="03">https://www.fisheries.noaa.gov/permit/incidental-take-authorizations-under-marine-mammal-protection-act.</E>
                         In case of problems accessing these documents, please call the contact listed above.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The MMPA prohibits the “take” of marine mammals, with certain exceptions. Sections 101(a)(5)(A) and (D) of the MMPA (16 U.S.C. 1361 
                    <E T="03">et seq.</E>
                    ) direct the Secretary of Commerce (as delegated to NMFS) to allow, upon request, the incidental, but not intentional, taking of small numbers of marine mammals by U.S. citizens who engage in a specified activity (other than commercial fishing) within a specified geographical region if certain findings are made and either regulations are proposed or, if the taking is limited to harassment, a notice of a proposed incidental harassment authorization is provided to the public for review.
                </P>
                <P>Authorization for incidental takings shall be granted if NMFS finds 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 taking for subsistence uses (where relevant). Further, NMFS must prescribe the permissible methods of taking and other “means of effecting the least practicable adverse impact” on the affected species or stocks and their habitat, paying particular attention to rookeries, mating grounds, and areas of similar significance, and on the availability of the species or stocks for taking for certain subsistence uses (referred to in shorthand as “mitigation”); and requirements pertaining to the mitigation, monitoring and reporting of the takings are set forth. The definitions of all applicable MMPA statutory terms cited above are included in the relevant sections below.</P>
                <HD SOURCE="HD1">Summary of Request</HD>
                <P>NMFS previously issued Incidental Take Regulations (ITRs) to Hilcorp for a suite of oil and gas activities in Cook Inlet, Alaska (84 FR 37442, July 31, 2019) and issued three letters of authorization (LOAs) under those ITRs. The ITRs covered activities including: two-dimensional (2D) and three-dimensional (3D) seismic surveys, geohazard surveys, and vibratory sheet pile driving. On September 17, 2019, Cook Inletkeeper and the Center for Biological Diversity filed suit in the District of Alaska challenging NMFS's issuance of the ITRs and LOAs and supporting documents (the Environmental Assessment (EA) and Endangered Species Act (ESA) Biological Opinion). In a decision issued on March 30, 2021, the court ruled largely in NMFS's favor, but found a lack of adequate support in NMFS's record for the agency's determination that tug towing of drill rigs in connection with production activity will not cause take of beluga whales and remanded back to NMFS for further analysis of tug use under the MMPA, ESA, and National Environmental Policy Act (NEPA).</P>
                <P>Hilcorp notified NMFS that all activities described in their initial ITR application (2018) and for which incidental take was authorized have already been completed or will not be completed under the ITRs. Accordingly, NMFS has begun the process of withdrawing the 2019 ITRs. As a result, the only remaining activity to be analyzed for incidental take and authorization thereof is the use of tugs towing a jack-up rig.</P>
                <P>On January 13, 2022, NMFS received a request from Hilcorp for two back-to-back IHAs to take marine mammals incidental to tugs towing a drill rig in Cook Inlet, Alaska. The application was deemed adequate and complete on March 8, 2022. Hilcorp's request is for take of small numbers of 12 species of marine mammals by Level B harassment only. Neither Hilcorp nor NMFS expects serious injury or mortality to result from this activity and, therefore, IHAs are appropriate.</P>
                <P>
                    As described in our 
                    <E T="04">Federal Register</E>
                     notice of proposed IHAs (87 FR 27597, May 9, 2022), NMFS considered the potential effects of tug towing a jack-up rig on marine mammals. The slow, predictable, and generally straight path of this tug configuration makes it unlikely that marine mammals would be exposed to the tugs towing a jack-up rig such that harassment would occur. However, there is overall potential for exposure in combination with the nature of the tug and jack-up rig configuration (
                    <E T="03">e.g.,</E>
                     difficult to maneuver, potential need to operate at night), making it possible that take could occur over the total estimated period of tug activities. Because of this possibility, NMFS proposed take by Level B harassment from Hilcorp's use of tugs towing a jack-up rig in Cook Inlet, Alaska.
                </P>
                <P>In a letter dated April 28, 2022, Hilcorp notified NMFS of their need to begin tugging the jack-up rig in May due to depleted energy reserves for the Southcentral Alaska region. NMFS concurred with Hilcorp's assessment that take of marine mammals by Level B harassment was unlikely to occur incidental to the transport of the jack-up rig from the Rig Tender's Dock in Nikiski to the Tyonek platform in middle Cook Inlet, as described in Hilcorp's letter. Hilcorp completed one move of their jack-up rig during the time that NMFS processed the request for IHAs; this rig move was included in Hilcorp's original application and was factored into our exposure estimate calculations accordingly. We have therefore removed that portion of the rig move from our analysis as it was already completed. Please refer to the Changes from Proposed IHAs to Final IHAs section later in this document for additional discussion. Below we discuss the IHAs as issued.</P>
                <HD SOURCE="HD1">Description of Activity</HD>
                <HD SOURCE="HD2">Overview</HD>
                <P>
                    Hilcorp Alaska, LLC (Hilcorp) plans to carry out activities that will occur during two separate consecutive one-year IHA periods—from September 1, 2022, to August 31, 2023 (Year 1), and from September 1, 2023, to August 31, 2024 (Year 2). Hilcorp plans to use three 
                    <PRTPAGE P="62365"/>
                    ocean-going tugs to tow a jack-up rig in support of plugging and abandonment (P&amp;A) of an existing well and to support production drilling at other locations in middle Cook Inlet and Trading Bay over the course of 2 years.
                </P>
                <HD SOURCE="HD2">Dates and Duration</HD>
                <P>The schedule for Hilcorp's P&amp;A and production drilling activities is provided in Table 1 below. The noise-producing rig-towing activities for which take is authorized would occur in between those activities, for approximately 14 days per year for Year 1 and 16 days for Year 2.</P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,r50,r50,xs50">
                    <TTITLE>Table 1—Dates and Durations of Planned Activities in Cook Inlet</TTITLE>
                    <BOXHD>
                        <CHED H="1">Project type</CHED>
                        <CHED H="1">Cook Inlet region</CHED>
                        <CHED H="1">Timing</CHED>
                        <CHED H="1">
                            Duration of
                            <LI>activity *</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">Year 1:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Plug and Abandonment of Well 17589</ENT>
                        <ENT>Middle Cook Inlet</ENT>
                        <ENT>April-November</ENT>
                        <ENT>30 days.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Production Drilling</ENT>
                        <ENT>Middle Cook Inlet Trading Bay</ENT>
                        <ENT>April-November</ENT>
                        <ENT>180 days.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Year 2:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Production Drilling</ENT>
                        <ENT>Middle Cook Inlet Trading Bay</ENT>
                        <ENT>April-November</ENT>
                        <ENT>180 days.</ENT>
                    </ROW>
                    <TNOTE>* Duration is in reference to the supported activity that requires the jack-up rig to be in a specific location. It is not reflective of the duration or the number of days the jack-up rig is towed.</TNOTE>
                </GPOTABLE>
                <HD SOURCE="HD2">Specific Geographic Region</HD>
                <P>Hilcorp's activities will take place in Cook Inlet, Alaska. For the purposes of this project, lower Cook Inlet refers to waters south of the East and West Forelands; middle Cook Inlet refers to waters north of the East and West Forelands and south of Threemile River on the west and Point Possession on the east; Trading Bay refers to waters from approximately the Granite Point Tank Farm on the north to the West Foreland on the south; and upper Cook Inlet refers to waters north and east of Beluga River on the west and Point Possession on the east. A map of the specific area in which Hilcorp plans to operate is provided in Figure 1 below.</P>
                <BILCOD>BILLING CODE 3510-22-P</BILCOD>
                <GPH SPAN="3" DEEP="611">
                    <PRTPAGE P="62366"/>
                    <GID>EN14OC22.069</GID>
                </GPH>
                <BILCOD>BILLING CODE 3510-22-C</BILCOD>
                <HD SOURCE="HD2">Detailed Description of Specific Activity</HD>
                <P>
                    Hilcorp plans to use three tugs to pull and position a jack-up rig in support of well plugging and abandonment (P&amp;A) and support of production drilling by using the rig as a temporary drilling platform. Hilcorp plans to use the jack-up rig Spartan 151, or similar. A jack-up rig is a type of mobile offshore drill unit used in offshore oil and gas drilling activities. It is comprised of a buoyant mobile platform or hull with moveable legs that are adjusted to raise and lower 
                    <PRTPAGE P="62367"/>
                    the hull over the surface of the water. The Spartan 151 (or similar) will be towed via three ocean-going tugs. The horsepower (hp) of each of the three tugs used to tow the jack-up rig may range between 4,000 and 8,000. Three tugs are needed to safely and effectively pull the jack-up rig into the correct position where it can be temporarily secured to the seafloor. Specifications of the tugs anticipated for use are provided in Table 2 below. If these specific tugs are not available, the tugs contracted would be of similar size and power to those listed in Table 2.
                </P>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s25,r50">
                    <TTITLE>Table 2—Description of Tugs Towing the Jack-Up Rig</TTITLE>
                    <BOXHD>
                        <CHED H="1">Vessel name</CHED>
                        <CHED H="1">Specifications</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">M/V Bering Wind</ENT>
                        <ENT>22-m length x 10-m breadth, 144 gross tonnage.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M/V Anna T</ENT>
                        <ENT>32-m length x 11-m breadth, 160 gross tonnage.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M/V Bob Franco</ENT>
                        <ENT>37-m length x 11-m breadth, 196 gross tonnage.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The amount of time the tugs are under load transiting, holding, and positioning the jack-up rig in Cook Inlet is tide-dependent. The power output of the tugs depends on whether the tugs are towing with or against the tide and can vary across a tide cycle as the current increases or decreases in speed over time. Hilcorp will make every effort to transit with the tide (which requires lower power output) and minimize transit against the tide (which requires higher power output).</P>
                <P>The jack-up rig will be transported via towing by three ocean-going tugs, with final demobilization at the Rig Tenders Dock in Nikiski, Alaska (where mobilization began). Towing the jack-up rig northward with an incoming tide or southward with an outgoing tide requires less than half power, generally only 20 to 30 percent of total power output (Durham 2021, pers. comm.). A high slack tide is preferred to position the jack-up rig on an existing platform or well site. The relatively slow current and calm conditions at a slack tide enable the tugs to perform the fine movements necessary to safely position the jack-up rig within several feet of the platform. Positioning and securing the jack-up rig is generally performed at high slack tide rather than low slack tide to pin the legs down at an adequate height to ensure the hull of the jack-up rig remains above the water level of the subsequent incoming high tide. Because 12 hours elapse between each high slack tide, tugs are generally under load for those 12 hours during rig mobilization and demobilization, even if the towed distance is small, as high slack tides are preferred to both attach and detach the jack-up rig from the tugs. Once the tugs are on location with the jack-up rig at high slack tide (12 hours from the previous departure), there is a 1 to 2-hour window when the tide is slow enough for the tugs to initiate positioning the jack-up rig and pin the legs to the seafloor on location. The tugs are estimated to be under load, generally at half-power conditions or less, for up to 14 hours from the time of departure through the initial positioning attempt of the jack-up rig. If the first positioning attempt takes longer than anticipated, the increasing current speed prevents the tugs from safely positioning the jack-up rig on location. If the first positioning attempt is not successful, the jack-up rig will be pinned down at a nearby location and the tugs will be released from the jack-up rig and no longer under load. The tugs will remain nearby, generally floating with the current. Approximately an hour before the next high slack tide, the tugs will re-attach to the jack-up rig and reattempt positioning over a period of 2 to 3 hours. Positioning activities are generally at half power. If a third attempt is needed, the tugs would be under load holding or positioning the jack-up rig on a second day for up to 5 hours. The vast majority of the time, the jack-up rig can be successfully positioned over the platform in one or two attempts.</P>
                <P>
                    A location-to-location transport (
                    <E T="03">e.g.,</E>
                     platform-to-platform) of a jack-up rig is conducted similarly to the mobilization from the Rig Tenders Dock described above with one main difference. In a location-to-location transport in middle Cook Inlet or Trading Bay, there is no harbor available for temporary staging to avoid transiting against the tide. Maintaining position of the jack-up rig against the tidal current can require more than half power (up to 90 percent power at the peak tidal outflow). However, greater than half power effort is only needed for short periods of time during the maximum tidal current, expected to be no more than 3 hours maximum. During a location-to-location transport, the tugs will transport the jack-up rig traveling with the tide in nearly all circumstances except in situations that threaten human safety and/or infrastructure integrity. There may be a situation wherein the tugs pulling the jack-up rig begin transiting with the tide to their next location, miss the tide window to safely set the jack-up rig on the platform or pin it nearby, and so have to transport the jack-up rig against the tide to a safe harbor. Tugs may also need to transport the jack-up rig against the tide if large pieces of ice or extreme wind events threaten the stability of the jack-up rig on the platform.
                </P>
                <P>Although the variability in power output from the tugs can range from an estimated 20 percent to 90 percent throughout the hours under load with the jack-up rig, as described above, the majority of the hours (spent transiting, holding, and positioning) occur at half power or less. See the Estimated Take section below for more detail on assumptions related to power output.</P>
                <P>
                    Year 1—For the first year of activity, Hilcorp will use three tugs to pull the jack-up rig for P&amp;A of Well 17589, which began in 2021 but was not completed due to equipment sourcing issues. Prior to pinning the jack-up rig legs to the seafloor, a multi-beam sonar may be used to ensure the seafloor is clear of debris that may impact the ability to pin down the legs of the platform. The multi-beam echosounder emits high frequency (240 kilohertz (kHz)) energy in a fan-shaped pattern of equidistant or equiangular beam spacing. The multi-beam sonar operates at a frequency outside of marine mammal hearing range and is not addressed further in our analysis. After the rig is secure, divers enter the water and use hand tools to complete the P&amp;A process. In addition to the hand tools, the divers will also use water jets to wash away debris and marine growth on the structure (
                    <E T="03">e.g.,</E>
                     a CaviDyne CaviBlaster). Based on measurements conducted by Hilcorp during 2017 use of water jets, the source level for the CaviBlaster® was estimated as 176 decibels (dB) re 1 micropascal (μPa) root mean square (rms) with a Level B harassment threshold of 860 m, with most energy concentrated above 500 Hz with a dominant tone near 2 kHz. Hilcorp plans to put a protected species observer (PSO) on watch to monitor the full extent of the harassment zone and shutdown when a marine mammal approaches the zone during water jet use. Because of this, Hilcorp is not requesting take associated with water jet use and it is not considered further in our analysis.
                </P>
                <P>
                    Hilcorp also plans to tug the jack-up rig to existing platforms in middle Cook Inlet and Trading Bay in support of production drilling activities from existing platforms and wellbores. Production drilling itself creates some small level of noise due to the use of generators and other potentially noise-generating equipment. Furie Operating Alaska, LLC, performed detailed underwater acoustic measurements in the vicinity of the Spartan 151 in 2011 
                    <PRTPAGE P="62368"/>
                    (Marine Acoustics Inc., 2011) northeast of Nikiski Bay in water depths of 24.4 to 27.4 m (80 to 90 ft). Primary sources of rig-based acoustic energy were identified as coming from the D399/D398 diesel engines, the PZ-10 mud pump, ventilation fans, and electrical generators. The source level of one of the loudest acoustic sources, the diesel engines, was estimated to be 137 dB re 1 μPa rms at 1 m in the 141 to 178 Hz frequency range. Based on this measured level, the 120 dB rms acoustic received level isopleth would be approximately 50 m away from where the energy enters the water (jack-up leg or drill riser). Sound source levels were also measured by JASCO (a company) for drilling and mud pumping from the Yost jack-up rig in 2016. The primary sources of continuous sounds measured from the Yost were drilling (158 dB) and mu167d pumping (148.4 dB), producing 120 dB isopleths of 330 and 225 meters, respectively. The acoustic energy of drilling noise was found to be predominantly under 500 Hz (Denes and Austin, 2016a). Denes and Austin (2016) did not record other rig-based activities including cementing, running casing, and tripping in and out of the hole with drill string; however, these activities may also produce sounds similar to mud pumping. There is open water in all directions from the drilling location. Additionally, Hilcorp plans to monitor the area around the drilling platform for 30 minutes prior to starting drilling activities and delay their activity if marine mammals are seen close to the platform. Any marine mammal approaching the rig would be fully aware of its presence long before approaching or entering the zone of influence for behavioral harassment, and we are unaware of any specifically important habitat features (
                    <E T="03">e.g.,</E>
                     concentrations of prey or refuge from predators) within the rig's zone of influence that would encourage marine mammal use and exposure to higher levels of noise closer to the source. Given the absence of any activity-, location-, or species-specific circumstances or other contextual factors that would increase concern, we do not expect routine drilling noise to result in the take of marine mammals.
                </P>
                <P>
                    In support of these activities, helicopters and support vessels transit from the mainland to the production sites to mobilize personnel and supplies. Helicopters will fly at 1,500 ft (457 m) or higher unless human safety is at risk or it is operationally impossible (
                    <E T="03">e.g.,</E>
                     takeoff and landing points are so close together the aircraft cannot reach 1,500 ft or 30 m). During take-off and landing of a helicopter, it is expected that only a small amount of sound would penetrate the water because the helicopter will be moving vertically over the helipad and most of the sound is reflected and does not penetrate at angles greater than 13 degrees from vertical. Additionally, the platforms that helicopters are navigating to/from are already 100 or more feet above sea level, further reducing potential for harassment of marine mammals such that take is not requested nor authorized. Vessel trips to and from the location of the jack-up rig are expected to increase by two trips per day above normal activity levels. Hilcorp plans to maintain watch for marine mammals during supply vessel trips, stay at least 100 yards (91 m) away from marine mammals, reduce speed in poor visibility, and handle supply vessels such that an encounter with a marine mammal is unlikely and additional take for supply vessel activities is not requested nor authorized.
                </P>
                <P>Year 2—For the second year of activity, Hilcorp does not plan to conduct P&amp;A activities with the jack-up rig and will only be tugging the jack-up rig in support of production drilling activities.</P>
                <P>
                    The specific configuration of tugs towing the jack-up-rig as used by Hilcorp has not been analyzed previously. Hilcorp contracted JASCO Applied Sciences to conduct a sound source verification (SSV) of their tugs in operation in Cook Inlet during October 2021. This SSV measured tugs pulling the jack-up-rig at various power outputs (Lawrence 
                    <E T="03">et al.,</E>
                     2022). This SSV returned a source level of 167.3 dB re 1 μPa for the 20 percent power scenario and a source level of 205.9 dB re 1 μPa for the 85 percent power scenario. Assuming a linear scaling of tug power, a source level of 185 dB re 1 μPa was then calculated as a single point source level for three tugs operating at 50 percent power output. This is approximately five dB higher than the literature summary described below.
                </P>
                <P>Hilcorp conducted a literature review of available source level data for tugs under load in varying power output scenarios. Table 3 below provides values of measured source levels for tugs varying from 2,000 to 8,200 horsepower. For the purposes of this table, berthing activities could include tugs either pushing or pulling a load. The sound source levels appear correlated to speed and power output, with full power output and higher speeds generating more propeller cavitation and greater sound source levels than lower power output and lower speeds. Additional tug source levels are available from the literature, but they are not specific to tugs under load (rather they measured values for tugs during activities such as transiting, docking, and anchor pulling). For a summary of these additional tug values, see Table 7 in Hilcorp's application.</P>
                <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="s50,12,12,r50,12,12,r50">
                    <TTITLE>Table 3—Literature Values of Measured Tug Source Levels</TTITLE>
                    <BOXHD>
                        <CHED H="1">Vessel</CHED>
                        <CHED H="1">Vessel length (m)</CHED>
                        <CHED H="1">Speed (knots)</CHED>
                        <CHED H="1">Activity</CHED>
                        <CHED H="1">
                            Source level @1 m
                            <LI>(re: 1 µPa)</LI>
                        </CHED>
                        <CHED H="1">Horsepower</CHED>
                        <CHED H="1">Reference</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Eagle</ENT>
                        <ENT>32</ENT>
                        <ENT>9.6</ENT>
                        <ENT>Towing barge</ENT>
                        <ENT>173</ENT>
                        <ENT>6,770</ENT>
                        <ENT>
                            Bassett 
                            <E T="03">et al.,</E>
                             2012.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Valor</ENT>
                        <ENT>30</ENT>
                        <ENT>8.4</ENT>
                        <ENT>Towing barge</ENT>
                        <ENT>168</ENT>
                        <ENT>2,400</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Lela Joy</ENT>
                        <ENT>24</ENT>
                        <ENT>4.9</ENT>
                        <ENT>Towing barge</ENT>
                        <ENT>172</ENT>
                        <ENT>2,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pacific Eagle</ENT>
                        <ENT>28</ENT>
                        <ENT>8.2</ENT>
                        <ENT>Towing barge</ENT>
                        <ENT>165</ENT>
                        <ENT>2,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Shannon</ENT>
                        <ENT>30</ENT>
                        <ENT>9.3</ENT>
                        <ENT>Towing barge</ENT>
                        <ENT>171</ENT>
                        <ENT>2,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">James T Quigg</ENT>
                        <ENT>30</ENT>
                        <ENT>7.9</ENT>
                        <ENT>Towing barge</ENT>
                        <ENT>167</ENT>
                        <ENT>2,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Island Scout</ENT>
                        <ENT>30</ENT>
                        <ENT>5.8</ENT>
                        <ENT>Towing barge</ENT>
                        <ENT>174</ENT>
                        <ENT>4,800</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Chief</ENT>
                        <ENT>34</ENT>
                        <ENT>11.4</ENT>
                        <ENT>Towing barge</ENT>
                        <ENT>174</ENT>
                        <ENT>8,200</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Lauren Foss</ENT>
                        <ENT>45</ENT>
                        <ENT>N/A</ENT>
                        <ENT>Berthing barge</ENT>
                        <ENT>167</ENT>
                        <ENT>8,200</ENT>
                        <ENT>
                            Austin 
                            <E T="03">et al.,</E>
                             2013.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Seaspan Resolution</ENT>
                        <ENT>30</ENT>
                        <ENT>N/A</ENT>
                        <ENT>Berthing at half power</ENT>
                        <ENT>180</ENT>
                        <ENT>6,000</ENT>
                        <ENT>Roberts Bank Terminal 2 Technical Report, 2014.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Seaspan Resolution</ENT>
                        <ENT>30</ENT>
                        <ENT>N/A</ENT>
                        <ENT>Berthing at full power</ENT>
                        <ENT>200</ENT>
                        <ENT>6,000</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="62369"/>
                <P>The Roberts Bank Terminal 2 Technical Report (2014), although not in Cook Inlet, includes repeated measurements of the same tug operating under different speeds and loads. This allows for a comparison of source levels from the same vessel at half power versus full power, which is an important distinction for Hilcorp's activities, as a small fraction of the total time spent by tugs under load will be at greater than 50 percent power. The Seaspan Resolution's half-power berthing scenario has a sound source level of 180 dB re 1 μPa at 1 m. In addition, the Roberts Bank Report (2014) analyzed 650 tug transits under varying load and speed conditions and reported mean tug source levels of 179.3 dB re 1 μPa at 1 m, the 25th percentile was 179.0 dB re 1 μPa at 1 m, and 5th percentile source levels were 184.9 dB re 1 μPa at 1 m.</P>
                <P>Based solely on the literature review, a source level of 180 dB for a tug under load would be appropriate. However, Hilcorp's use of a three tug configuration would increase the literature source level to approximately 185dB. As one or two tugs are primarily under load, the third tug sits off to the side. NMFS still considers these tugs to be simultaneous sources. When considered in conjunction with the additional tugs present in the configuration as well as the SSV conducted by JASCO for Hilcorp's specific configuration, a source level of 185 dB for tugs towing a jack-up rig was carried forward for analysis.</P>
                <P>
                    Mitigation, monitoring, and reporting measures are described in detail later in this document (please see 
                    <E T="04">Mitigation</E>
                     and 
                    <E T="04">Monitoring</E>
                     and 
                    <E T="04">Reporting</E>
                    ).
                </P>
                <HD SOURCE="HD1">Comments and Responses</HD>
                <P>
                    A notice of NMFS's proposal to issue IHAs to Hilcorp was published in the 
                    <E T="04">Federal Register</E>
                     on May 9, 2022 (87 FR 27597). That notice described, in detail, Hilcorp's activity, the marine mammal species that may be affected by the activity, and the anticipated effects on marine mammals. During the 30-day public comment period, NMFS received comments from Hilcorp, the Bureau of Ocean Energy Management (BOEM), and the Center for Biological Diversity (CBD) in conjunction with Cook Inletkeeper and Kachemak Bay Conservation Society (this group comment letter is referenced as CBD throughout this notice). These letters are available online at: 
                    <E T="03">https://www.fisheries.noaa.gov/action/incidental-take-authorization-hilcorp-alaska-llc-oil-and-gas-activities-cook-inlet-alaska-0.</E>
                     A summary of the commenters' recommendations as well as NMFS' responses is below.
                </P>
                <P>
                    <E T="03">Comment 1:</E>
                     NMFS received comments about how the proposed IHAs would relate to the Incidental Take Regulations (ITRs) NMFS issued to Hilcorp in 2019 (84 FR 37442, July 30, 2019). CBD commented that NMFS cannot “segment” its MMPA analysis for the activities proposed under the IHAs from its authorization of Hilcorp's oil and gas activities under the 5-year ITRs. Additionally, Hilcorp requested that NMFS withdraw the ITRs.
                </P>
                <P>
                    <E T="03">Response:</E>
                     The activities for which take was analyzed in the ITRs have already occurred or, per Hilcorp, will not occur during the remaining period of the ITR, which currently expires on July 30, 2024. Because none of the activity for which take was authorized under the ITRs is planned to occur under the ITRs, NMFS and Hilcorp determined there would be no benefit to undertaking the process of re-evaluating the ITRs. Instead it was determined that IHAs under section 101(a)(5)(D) would be an efficient vehicle for addressing incidental take from tug activities in a timely fashion, should authorization be needed, particularly compared to the process for rulemaking under section 101(a)(5)(A).
                </P>
                <P>Hilcorp accordingly applied for two IHAs and NMFS evaluated the potential for take of marine mammals incidental to the tug activity Hilcorp included in its application. Given the type of activity Hilcorp plans to conduct, the fact that any potential take would be in the form of Level B harassment, only, and the timeframe of those activities, IHAs are appropriate. This is the course of action NMFS would advise for any applicant planning to conduct 2 years of approximately 14 days and 16 days of take-related activity per year, respectively, with the potential to result in take by harassment only.</P>
                <P>As indicated above, and at Hilcorp's request, NMFS is undertaking the process to withdraw the ITRs to reduce any confusion. NMFS will not issue any more LOAs pursuant to the ITRs to authorize take incidental to Hilcorp's tug towing activities. Thus there is no possibility for NMFS to authorize incidental take of beluga whales simultaneously through an IHA and the ITRs.</P>
                <P>
                    <E T="03">Comment 2:</E>
                     BOEM commented that NMFS' 
                    <E T="04">Federal Register</E>
                     (FR) notice did not discuss potential effects of helicopters and support vessels described in Hilcorp's application for IHAs and that NMFS may benefit from analysis of effects to marine mammals from these activities.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS briefly discussed these activities in the Detailed Description of Specific Activity in the notice of proposed IHAs, following the discussion of water jets. That paragraph includes a discussion of why these activities were not considered further.
                </P>
                <P>
                    <E T="03">Comment 3:</E>
                     BOEM commented that NMFS could add clarity as to why 185 dB was used as an estimated source level for the multi-tug configuration by referring readers to the JASCO monitoring report for the sound source verification of Hilcorp's sources.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS omitted this source inadvertently. We have now included Lawrence 
                    <E T="03">et al.</E>
                     (2022) in our references for further information regarding the sound source verification used to derive a source level of 185 dB for the three-tug combination.
                </P>
                <P>
                    <E T="03">Comment 4:</E>
                     BOEM commented that NMFS may want to consider effects to Pacific white-sided dolphins based on an acoustics report (Castellote 
                    <E T="03">et al.,</E>
                     2020).
                </P>
                <P>
                    <E T="03">Response:</E>
                     Based on this report and other information described below, NMFS has added take of Pacific white-sided dolphins to our analysis and authorizations. See 
                    <E T="04">Description of Marine Mammals in the Area of Specified Activities</E>
                     section for more discussion of the species and why they are included in our analysis.
                </P>
                <P>
                    <E T="03">Comment 5:</E>
                     BOEM noted page 27621 of the notice of proposed IHAs listed requirements for monitoring of pile driving activities.
                </P>
                <P>
                    <E T="03">Response:</E>
                     These requirements were included in error and have been removed from the final notice.
                </P>
                <P>
                    <E T="03">Comment 6:</E>
                     Hilcorp commented that the notice of proposed IHAs and draft EA incorrectly refers to Hilcorp's planned tugging activities as the “proposed activity” when the proposed activity from NMFS' perspective is the proposed issuance of IHAs to take marine mammals incidental to Hilcorp's planned activities.
                </P>
                <P>
                    <E T="03">Response:</E>
                     Hilcorp is correct and NMFS has clarified Hilcorp's planned activities from NMFS' activities in all documents.
                </P>
                <P>
                    <E T="03">Comment 7:</E>
                     Hilcorp contests NMFS' characterization of the project area as a “non-industrial setting” prior to the onset of Hilcorp's tugging activities. The oil and gas facilities in Cook Inlet, including Hilcorp's platforms, have been active, with daily activities, for the past 60 years.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS agrees that this area is not pristine, as Hilcorp's platforms and development structures are already in existence. However, Hilcorp's activities will introduce additional anthropogenic activity into the area, 
                    <PRTPAGE P="62370"/>
                    such as increased vessels around the platforms, helicopter trips for personnel, supplies, 
                    <E T="03">etc.</E>
                     NMFS has clarified the characterization of the action area accordingly.
                </P>
                <P>
                    <E T="03">Comment 8:</E>
                     Hilcorp recommended that NMFS more clearly describe why any incidental marine mammal harassment related to tug-towing activities is likely to be very low due to the characteristics of those activities in the notice of issuance of IHAs and final EA.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS agrees with Hilcorp's characterization that a multi-tug configuration under load moves in a slow, predictable pattern that is unlikely to surprise marine mammals in the area and, further, animals near industrial activities may become habituated to regular activities in the area, as has been shown for Cook Inlet belugas around the Port of Anchorage, for example (61 North Environmental, 2020). However, given the sources levels, there is still the potential that some belugas may behaviorally respond in a manner that would qualify as a take. NMFS characterizes the type of harassment (behavioral disturbance only) that may occur from tugs in this 
                    <E T="04">Federal Register</E>
                     notice and has authorized Level B harassment out of caution due to several combined factors, as described in the 
                    <E T="04">Potential Effects of Specified Activities on Marine Mammals and their Habitat</E>
                     section.
                </P>
                <P>
                    <E T="03">Comment 9:</E>
                     Hilcorp recommends that NMFS clearly express its finding that the incidental harassment levels for each IHA constitutes a “small number” for each marine mammal stock regardless of NMFS's “one-third” standard.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS has made a small numbers finding for each IHA individually. The quantitative rationale for determining these numbers are “small” is put forth in Table 15 below.
                </P>
                <P>
                    <E T="03">Comment 10:</E>
                     Hilcorp requests that NMFS clarify that the renewal process is not necessary for the Year 2 IHA to become effective. Hilcorp specifically applied for, and NMFS proposed to issue, two separate, stand-alone IHAs. The Year 2 IHA would not be a “renewed” version of the Year 1 IHA. Hilcorp anticipates no need for renewal of the Year 1 IHA and requests removal of the renewal provision from the IHAs.
                </P>
                <P>
                    <E T="03">Response:</E>
                     Hilcorp is correct that the Year 2 IHA is not dependent upon a renewal of Year 1 and is a completely separate authorization from the Year 1 IHA. NMFS issued the Year 1 IHA to Hilcorp effective through September 13, 2023. NMFS has also issued a Year 2 IHA to Hilcorp with effective dates from September 14, 2023 to August 13, 2024. Further, at Hilcorp's request, NMFS will not consider a renewal of the Year 1 IHA and has removed the renewal provision from these IHAs.
                </P>
                <P>
                    <E T="03">Comment 11:</E>
                     Hilcorp recommends that NMFS clarify whether or not the EA relies upon the NEPA regulatory amendments recently adopted by the Council for Environmental Quality (CEQ) that became effective on May 20, 2022 (87 FR 2,453, April 20, 2022).
                </P>
                <P>
                    <E T="03">Response:</E>
                     Per NMFS' internal guidance dated June 17, 2022, NEPA reviews for actions initiated after September 14, 2020, but prior to May 20, 2022, will be conducted according to the 2020 CEQ regulations. In accordance with this guidance, NMFS' Environmental Assessment for this action references the 2020 CEQ regulations.
                </P>
                <P>
                    <E T="03">Comment 12:</E>
                     Hilcorp suggested several corrections or changes for clarity or to improve accuracy throughout the FR notice. Hilcorp commented that NFMS incorrectly characterized the straight line towing distance in the Marine Mammal Hearing section of the proposed IHA notice as 37 km when the distance used in the analysis was 64 km (40 mi). Hilcorp also comments that use of the phrase “approximately 7 km” was confusing as that was an estimation of the diameter of the ensonified area and that 3.8 km radius is a more precise characterization of the analysis of the ensonified area.
                </P>
                <P>
                    <E T="03">Response:</E>
                     These errors and clarifications have been fixed for this notice of the final IHAs.
                </P>
                <P>
                    <E T="03">Comment 13:</E>
                     The Center for Biological Diversity (CBD) recommended that NMFS stop allowing take of Cook Inlet beluga whales unless and until the agency conducts a comprehensive evaluation of the numerous threats. They note that NMFS developed 5-year action plans for each of the “Species in the Spotlight” that outline short-term efforts vital for stabilizing their populations and preventing their extinction. The first of the “Key Actions Needed 2016-2020” in NMFS's Species on the Spotlight Cook Inlet Beluga Whale 5-Year Action Plan is “Reduce the Threat of Anthropogenic Noise in Cook Inlet Beluga Whale Habitat.” They further note that the NMFS' Recovery Plan for Cook Inlet beluga whales (2016) (Recovery Plan) lists tugboats as the highest noise threat to critically endangered species.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS shares CBD's concern regarding the impacts of human activities on Cook Inlet beluga whales and is committed to supporting the conservation and recovery of the species. Under section 101(a)(5)(D) of the MMPA, NMFS considers the at risk status of Cook Inlet beluga whales (and other species) in both the negligible impact analysis and through our consideration of impact minimization measures that will support the least practicable adverse impact on those species. For example, the Hilcorp final rule included shutdown zones for Cook Inlet beluga whales that extended well beyond standard shutdown zones all the way to the Level B harassment isopleth. However section 101(a)(5)(D) also mandates that NMFS “shall issue” an IHA if we are able to make the necessary findings for any specified activity for which incidental take is requested.
                </P>
                <P>In accordance with our implementing regulations at 50 CFR 216.104(c), we use the best available scientific evidence to determine whether the taking by the specified activity within the specified geographic region will have a negligible impact on the species or stock and will not have an unmitigable adverse impact on the availability of such species or stock for subsistence uses. Based on the scientific evidence available, NMFS determined that the take incidental to Hilcorp's tugging of the jack-up rig, which is primarily acoustic in nature, transient, and of a low level, would have no more than a negligible impact and no unmitigable adverse impact on availability of marine mammals for subsistence uses. Moreover, Hilcorp proposed and NMFS has required in the IHAs a rigorous mitigation plan to further reduce potential impacts to Cook Inlet beluga whales and other marine mammals to the lowest level practicable. Protected species observers are required to conduct monitoring during all jack-up rig towing activity. Since publication of the proposed IHAs, aerial surveys have been incorporated to monitor for beluga presence when towing to or from the Tyonek platform as the more northern location is approaching an area of known Cook Inlet beluga whale use.</P>
                <P>
                    Our analysis indicates that issuance of these IHAs will not contribute to or worsen the observed decline of the Cook Inlet beluga whale population. Additionally, the ESA Biological Opinion determined that the issuance of these IHAs is not likely to jeopardize the continued existence of the Cook Inlet beluga whales or the western distinct population segment of Steller sea lions or to destroy or adversely modify Cook Inlet beluga whale critical habitat. The Biological Opinion also outlined Terms and Conditions and Reasonable and Prudent Measures to reduce impacts, which have been incorporated into the IHAs, including the aerial surveys discussed in the 
                    <E T="04">Mitigation</E>
                     section 
                    <PRTPAGE P="62371"/>
                    below. Therefore, based on the analysis of potential effects, the parameters of the activity, and the rigorous mitigation and monitoring program, NMFS determined that the taking from the specified activity for Year 1 and for Year 2 would have a negligible impact on the Cook Inlet beluga whale stock.
                </P>
                <P>
                    Moreover, Hilcorp's jack-up rig towing activity would take only small numbers of marine mammals relative to their population sizes. Further, these takes represent one annual disturbance event for each of these individuals, or perhaps a few individuals could be disturbed a few times, in which case the number of impacted individual whales is even lower. As described in the 
                    <E T="04">Federal Register</E>
                     notice of proposed IHAs, NMFS used a method that incorporates density of marine mammals overlaid with the anticipated ensonified area to calculate an estimated number of takes for belugas, which was estimated to be less than 8 percent of the stock abundance, which NMFS considers small.
                </P>
                <P>
                    Regarding CBD's comment about tugboat noise, NMFS' Recovery Plan ranks noise from tugboats as the most important source that could potentially interfere with Cook Inlet beluga whale recovery based on signal characteristics and spatio-temporal acoustic footprint. However, notably, the Recovery Plan is referencing tugboat noise as a whole across all vessels and the entirety of Cook Inlet, not Hilcorp's specified activity in the specified location and geographic region, which is likely a small portion of overall tugboat use in Cook Inlet throughout the year. NMFS' biological opinion on NMFS' IHAs for Hilcorp's activity addressed the impacts of the marine mammal take NMFS is authorizing in the context of both the environmental baseline and the cumulative effects (including tugboats) and found that it likely would not jeopardize Cook Inlet beluga whales or destroy or adversely modify their Critical Habitat. In the MMPA analysis, NMFS addresses the signal characteristics and spatio-temporal overlap of Hilcorp's specific tug activity in the 
                    <E T="04">Federal Register</E>
                     notice and has authorized take accordingly.
                </P>
                <P>In addition to implementing mitigation and measures to minimize the impact of Hilcorp's activity, more broadly NMFS is taking several proactive steps to address the decline of the species. NMFS provides online platforms that allow public access to search for and review NOAA Fisheries permits and authorizations, as well as consultations under section 7 of the ESA. Additionally, NMFS is supporting the development of a population consequences of disturbance model to further refine information about the effects of stressors on Cook Inlet beluga whale behavior, energetic costs, and vital rates. NMFS continues to conduct outreach and education to various stakeholders to minimize the potential for unauthorized take of Cook Inlet beluga whales. Lastly, NMFS is developing site-specific stranding response and disaster response guidelines for Cook Inlet, which could inform responses and further reduce impacts to Cook Inlet beluga whales.</P>
                <P>
                    <E T="03">Comment 14:</E>
                     CBD commented that the Recovery Plan recommends a review of the current system of allocation of takes by harassment of beluga whales to better reduce cumulative effects of harassment takes by numerous projects. CBD provides examples for the number of takes authorized by NMFS for various time periods, citing Migura and Bollini (2021).
                </P>
                <P>
                    <E T="03">Response:</E>
                     We note first that the Migura and Bollini (2021) paper cited by CBD seems to have led to a misunderstanding of the takes authorized or permitted by NMFS. In summary, CBD asserts that NMFS authorized nearly 120,000 takes of Cook Inlet belugas from 2017 to 2025 and that in 2020 alone, NMFS authorized the equivalent of 50 percent of the entire Cook Inlet beluga whale population to be “incidentally” harassed by industrial projects in the Inlet, such as oil and gas development and pile driving activities.
                </P>
                <P>
                    The vast majority of the asserted ~120,000 total takes (99 percent), including all of the very small amount of take by Level A harassment, were authorized under directed research or enhancement permits, which support research or actions identified in the Recovery Plan to address Cook Inlet beluga whale recovery goals. Further, the vast majority (~99 percent) of the total permitted research or enhancement take numbers cited by CBD are low-level MMPA Level B harassment from remote or non-invasive procedures that are considered not likely to adversely affect listed species pursuant to the ESA (
                    <E T="03">i.e.,</E>
                     no associated take under the ESA is either expected to occur or exempted for those specific activities). We further note that based on the required post-research reporting from this 9-year period, an average of 25 percent of the permitted takes actually occurred. For the Directed Take Program, scientific research and enhancement permits authorize intentional close approaches that target marine mammals and that may result in harassment. These permitted takes generally are a larger number than the actual takes that occur because researchers need the ability to work in the field without running out of takes mid-season when optimal conditions and opportunities arise to meet their stated research objectives. Factors such as weather, funding, the pandemic, 
                    <E T="03">etc.,</E>
                     affect whether takes can be used.
                </P>
                <P>Regarding the comprehensive evaluation and minimization of permitted takes, we reference the analysis that has already been completed through NMFS' 2019 Biological and Conference Opinion on the Proposed Implementation of a Program for the Issuance of Permits for Research and Enhancement Activities on Cetaceans in the Arctic, Atlantic, Indian, Pacific, and Southern Oceans (NMFS, 2019), which determined that the research and enhancement takes permitted by the program would not jeopardize the existence of any of the affected species. As part of our programmatic framework for permitting directed take of ESA species, the Permits and Conservation Division will continue to closely evaluate the number and manner of Cook Inlet beluga whale takes requested by each applicant, how the proposed research ties to recovery plan goals, and the collective number of authorized and requested takes to consider the potential cumulative impact of the activities to the population. Each directed take annual report is reviewed to understand how authorized takes were actually used and to closely monitor the impacts that permitted research methods are having on the target animals.</P>
                <P>NMFS also has an active role on the Research subcommittee of the Cook Inlet Beluga Whale Recovery Implementation Task Force. Starting in 2021 the subcommittee increased efforts to monitor and coordinate research undertaken on Cook Inlet beluga whales each year. This effort includes pre- and post-season meetings with all parties conducting these studies to (1) coordinate field efforts and minimize harassment of whales, (2) learn of the latest findings by these groups and others. The subcommittee also plans to review new findings about threats listed in the Recovery Plan (NMFS, 2016) and identify data gaps as potential avenues for future research.</P>
                <P>
                    Regarding the incidental takes authorized for 2020, those takes represent instances of exposure above the Level B harassment threshold that could occur within a day. In other words, if those approximately 130 takes were assumed to be 130 separate individual whales, it would mean that those individual whales were each behaviorally disturbed on one day in that year. The more likely scenario is 
                    <PRTPAGE P="62372"/>
                    that some of those 130 exposures were takes of the same whale on a few different days, and in fact a lesser number of individuals were taken, but still on only a few days within a year. In all cases, the necessary findings under MMPA and ESA were made prior to the authorization of the take. Further, ITAs issued for activities that may take Cook Inlet beluga whales typically include enhanced protective measures for beluga whales that include delaying the activity or shutting down if a beluga is sighted within the Level B harassment zone and avoiding activities in important feeding areas, such as the Susitna Delta. These measures ensure that in the unlikely event that a beluga whale is harassed by activities covered by an ITA, the impacts are expected to be of a comparatively low level of severity.
                </P>
                <P>
                    <E T="03">Comment 15:</E>
                     CBD commented that NMFS' actions contradict the recommendations of the Marine Mammal Commission, which has repeatedly urged NMFS to stop issuing authorizations until the agency better understands the decline in abundance.
                </P>
                <P>
                    <E T="03">Response:</E>
                     CBD cites letters NMFS received from the Marine Mammal Commission (MMC) for previous proposed incidental take authorizations before 2021 recommending NMFS refrain from authorizing take of Cook Inlet beluga whales until more is understood about the decline in abundance. NMFS responded to those comment letters (
                    <E T="03">e.g.,</E>
                     84 FR 37451, July 31, 2019) and we incorporate that response by reference. NMFS did not receive a comment letter from the MMC regarding the proposed IHAs for Hilcorp, but we refer the reader to the responses to comments 13 and 14 above.
                </P>
                <P>
                    <E T="03">Comment 16:</E>
                     CBD commented that the MMPA states that IHAs are valid for periods of not more than 1 year, but that NMFS is proposing a series of IHAs for the next 3 years without conducting a comprehensive analysis of take across all 3 years.
                </P>
                <P>
                    <E T="03">Response:</E>
                     Incidental harassment authorizations issued under section 101(a)(5)(D) for a specified activity are limited to periods of 1 year or less. Each IHA must satisfy the negligible impact standard for the authorized taking and include the means of effecting the least practicable adverse impact on the species or stock and its habitat and, where relevant, on the availability of such species or stock for taking for subsistence uses (
                    <E T="03">i.e.,</E>
                     mitigation). NMFS considered Hilcorp's request for two IHAs for two distinct specified activities (identified as Year 1 and Year 2 activities) and, therefore, performed two distinct negligible impact analyses (because NMFS removed the possibility of a renewal of the IHAs at Hilcorp's request, there will not be a possibility for a third year). NMFS has a documented history of issuing consecutive IHAs to the same applicant, including sequential IHAs authorizing take of Cook Inlet beluga whales (85 FR 19294, April 6, 2020; 85 FR 1140, January 9, 2020; 85 FR 68291, October 28, 2020). Although it is not clear what is meant by a “comprehensive” analysis, under NMFS' implementing regulations for the MMPA, our negligible impact analyses take into account the “baseline”; moreover, under NEPA, NMFS' EA considers all anthropogenic activities that NMFS is aware of, including those for which take is not authorized in the cumulative effects section and incorporates where appropriate into the environmental baseline under the ESA, NMFS' biological opinion considered the same types of activities in their environmental baseline and cumulative effects discussions.
                </P>
                <P>Regarding the potential for a third year of activities through the issuance of a renewal at a later date, please see the response to comment 17.</P>
                <P>
                    <E T="03">Comment 17:</E>
                     CBD commented that issuance of renewals of IHAs via an expedited process is unlawful as it circumvents public comment timing laid out in the MMPA.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS' IHA renewal process meets all statutory requirements. All IHAs issued, whether an initial IHA or a renewal, are valid for a period of not more than 1 year; the public has 30 days to comment on proposed IHAs, with a cumulative total of 45 days for IHA renewals. The Request for Public Comments section in the notice of proposed IHA made clear that the agency was seeking comment on both the initial proposed IHA for this project and the potential issuance of a renewal. Because any renewal (as explained in the Request for Public Comments section) is limited to another year of identical or nearly identical activities (as described in the Description of Proposed Activity) or the same activities that were not completed within the 1-year period of the initial IHA, reviewers have the information needed to effectively comment on both the immediate proposed IHA and a possible 1-year renewal, should the IHA holder choose to request one in the coming months.
                </P>
                <P>
                    In prior responses to comments about IHA Renewals (
                    <E T="03">e.g.,</E>
                     84 FR 52464, October 02, 2019; 85 FR 53342, August 28, 2020), NMFS has explained how the Renewal process, as implemented, is consistent with the statutory requirements contained in section 101(a)(5)(D) of the MMPA, provides additional efficiencies beyond the use of abbreviated notices, and, further, promotes NMFS' goals of improving conservation of marine mammals and increasing efficiency in the MMPA compliance process. Therefore, we intend to continue implementing the Renewal process.
                </P>
                <P>In this case, as already stated, at Hilcorp's request NMFS removed the renewal provision from these IHAs.</P>
                <P>
                    <E T="03">Comment 18:</E>
                     CBD commented that NMFS' interpretation of “small” as it pertains to the small numbers analysis is unreasonable, and that a number may be considered small only if it is “little or close to zero” or “limited in degree.”
                </P>
                <P>
                    <E T="03">Response:</E>
                     In NMFS' Final Rule for taking of marine mammals incidental to geophysical surveys in the Gulf of Mexico (86 FR 5322, January 19, 2021), NMFS fully describes its interpretation and implementation of “small numbers”. Included as part of that discussion, NMFS explains the concept of “small numbers” in recognition that there could also be quantities of individuals taken that would correspond with “medium” and “large” numbers. As such, NMFS has established that one-third of the most appropriate population abundance number—as compared with the assumed number of individuals taken—is an appropriate limit with regard to “small numbers.” This relative approach is consistent with the statement from the legislative history that “[small numbers] is not capable of being expressed in absolute numerical limits” (H.R. Rep. No. 97-228, at 19 (September 16, 1981)), and relevant case law (
                    <E T="03">Center for Biological Diversity</E>
                     v. 
                    <E T="03">Salazar,</E>
                     695 F.3d 893, 907 (9th Cir. 2012) (holding that the U.S. Fish and Wildlife Service reasonably interpreted “small numbers” by analyzing take in relative or proportional terms)).
                </P>
                <P>
                    We note that the comment selectively includes a definition in support of CBD's favored position. For example, the definition of “small” in Webster's New Collegiate Dictionary (1981) included “having little size, esp. as compared with other similar things.” See also 
                    <E T="03">www.merriam-webster.com/dictionary/</E>
                     small (defining “small” as “having comparatively little size”). These definitions comport with the small numbers interpretation developed by NMFS, which utilizes a proportionality approach.
                </P>
                <P>
                    <E T="03">Comment 19:</E>
                     CBD claims that NMFS's proposed IHAs failed to account for all sources of take.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS acknowledges that Hilcorp's overall activity in Cook Inlet 
                    <PRTPAGE P="62373"/>
                    includes more than the activities for which take is authorized under these IHAs. Firstly, ITAs under the MMPA are a request-based authorization by which NMFS analyzes the potential for incidental harassment at the request of the applicant for the activities described. NMFS also considers other related activities by the applicant to assess whether they, alone or in combination with the specified activity for which take was requested, may result in take, and will advise if they should be included in the take application. In the specific example used by CBD that vessel trips may increase by two trips per day from normal platform operations, there is no indication that take is likely to occur nor has Hilcorp requested take due to supply vessel trips. While vessel noise can contribute to masking and is a contributor to elevated noise in the area, the manner in which Hilcorp plans to operate their support vessel (with inherent mitigation to avoid the presence of marine mammals) supports the assessment that an encounter with a marine mammal, let alone a disruption of their behavioral pattern, is unlikely to occur.
                </P>
                <P>
                    <E T="03">Comment 20:</E>
                     CBD commented that NMFS failed to consider noise from water jets, production drilling, helicopters, and vessel traffic.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS considered these additional sources and did not find authorization of take was warranted for these activities. Additional detail about these sources and NMFS' rationale is provided in the 
                    <E T="03">Detailed Description of Specific Activity</E>
                     section of this notice.
                </P>
                <P>NMFS also disagrees with CBD's characterization that the MMPA definition of harassment “includes not only those activities that will or are likely to cause take but those that `ha[ve] the potential to injure . . . or . . . disturb a marine mammal.' ” This is an incomplete recitation of the statutory definition of harassment. Level B harassment refers to an act of pursuit, torment, or annoyance that 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.” This requires that an act have “the potential to disturb by causing disruption of behavioral patterns,” not simply result in a detectable change in motion or vocalization. See 84 FR 63268, 63285 (December 7, 2018).</P>
                <P>
                    <E T="03">Comment 21:</E>
                     CBD commented that NMFS is artificially lowering take estimates “by calculating the number of harassments per activity by days of exposure rather than the instances of harassment.”
                </P>
                <P>
                    <E T="03">Response:</E>
                     In order to provide a practical, consistent, biology-based (
                    <E T="03">i.e.,</E>
                     the Diel Cycle) currency for impact assessment across the wide range of take calculation methods applicants may use—for years NMFS has recommended that for the purposes of counting instances of take—we do not consider one individual as taken more than one time in a day, even if that an individual could be exposed to sound or other stressors multiple separate times in one day. For the purposes of the negligible impact analysis of the effects of the enumerated takes on any individuals and the stock, though, it is important to understand the likely nature of these enumerated instances of take (
                    <E T="03">e.g.,</E>
                     momentary exposure versus multiple hours, high level versus low level), and that is how the potential for multiple exposures in a day (if expected) or longer duration exposures are appropriately considered in the analysis.
                </P>
                <P>
                    For Hilcorp, NMFS used the best available science to arrive at the most realistic characterization of potential harassment possible. In this instance, NMFS calculated the area likely to be ensonified above 120 dB and applied the best available density values for species in Cook Inlet to arrive at a number of individuals exposed in a single day. This is then multiplied by the number of days to result in the number of exposures across the entire duration of the activity (
                    <E T="03">e.g.,</E>
                     14 or 16 days, respectively). If anything, this calculation may be an overestimate as animals are not uniformly distributed across the action area, and the same individual animals may be exposed to sound levels greater than 120 dB several times over the duration of the activity but due to the constraints of our calculations, they are being considered as separate animals in our estimations.
                </P>
                <P>
                    <E T="03">Comment 22:</E>
                     CBD commented that NMFS' small numbers determination for Cook Inlet beluga whales fails to consider the status of the species. CBD claims that “small” must be considered against the status of the species and whether the percentage of take for each affected species will ensure that population levels are maintained at or restored to heathy numbers.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS disagrees with CBD's assertion. The argument to establish a small numbers threshold on the basis of stock-specific context is unnecessarily duplicative of the required negligible impact finding, in which relevant biological and contextual factors are considered in conjunction with the amount of take and would risk conflating the two standards. Similarly, CBD's assertion that NMFS' small numbers analysis must consider whether the percentage of take would restore a population to “healthy number” is not required by section 101(a)(5)(D) of the MMPA.
                </P>
                <P>
                    <E T="03">Comment 23:</E>
                     CBD commented that NMFS has no basis on which to conclude that additional harassment by noise has a negligible impact on Cook Inlet beluga whales as a species, given the population's lack of recovery and continued decline.
                </P>
                <P>
                    <E T="03">Response:</E>
                     In the Negligible Impact Analysis and Determination section, we describe how the take predicted and authorized for Hilcorp's tugboat activity (not additional harassment by noise at large), which is 11 in Year 1 and 22 in Year 2 for beluga whales, will have a negligible impact on all of the affected species. In summary, this determination is based upon the small numbers of beluga whales that might be exposed briefly during the 16 days of the activity, the comparatively low degree of behavioral harassment that might result from any one of the 11 or 22 instances of take that occur within a year, and the likelihood that the mitigation measures further lessen the likelihood of exposures. NMFS has considered the status and decline of Cook Inlet beluga whales in its analysis, as well as the importance of reducing impacts from anthropogenic noise, but nonetheless, there is no indication that brief exposure to low level noise not causing greater than Level B harassment would have a greater than negligible impact on Cook Inlet beluga whales.
                </P>
                <P>
                    <E T="03">Comment 24:</E>
                     CBD claims that NMFS incorrectly stated that Cook Inlet beluga whales are not known to engage in critical behaviors in the area where Hilcorp's project is planned.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS acknowledges observation of one potential but unconfirmed incidence of mating behavior in the Trading Bay area, but the extent to which critical behaviors occur in Hilcorp's project area is still unknown. (Lomac-Macnair 
                    <E T="03">et al.,</E>
                     2016). Such behaviors have not been reported since. Surveys by NMFS or McGuire 
                    <E T="03">et al.</E>
                     (2020) with concentrated effort on the western coast of Cook Inlet have not yielded a comparable sighting. Other key behaviors, such as calving and feeding, are described in more detail below but are thought to occur primarily in other concentrated areas outside of Hilcorp's action area.
                </P>
                <P>
                    We are unaware of any information regarding areas where Cook Inlet belugas are more likely to engage in mating behavior, however, what is known about calving suggests that it is 
                    <PRTPAGE P="62374"/>
                    most concentrated in the upper Inlet, north of Hilcorp's project area. McGuire 
                    <E T="03">et al.</E>
                     (2020) characterizes habitat use by age class in northern Cook Inlet and documented the majority of calves in the northernmost parts of Cook Inlet (
                    <E T="03">e.g.,</E>
                     Susitna Delta) despite concentrated survey effort in areas along the west part of the Inlet heading south toward the Forelands. NMFS acknowledges that Cook Inlet beluga whales use the area, especially in spring and fall months, but their habitat range at those times is not nearly as constricted as their summer habitat, which is concentrated in a small area with high anthropogenic activity.
                </P>
                <P>
                    Cook Inlet beluga whales may well occur in the project area, which is why a small amount of take by Level B harassment is authorized for this species incidental to Hilcorp's jack-up rig towing. Tagging data, acoustic studies, and opportunistic sightings indicate that Cook Inlet belugas continue to occur in the upper inlet throughout the winter months, in particular the coastal areas from Trading Bay to Little Susitna River, with foraging behavior detected in lower Knik Arm and Chickaloon Bay, and also detected in several areas of the lower inlet such as the Kenai River, Tuxedni Bay, Big River, and NW Kalgin Island (Castellote 
                    <E T="03">et al.,</E>
                     2011, 2020, 2021; C. Garner, pers. comm.; Shelden 
                    <E T="03">et al.,</E>
                     2015, 2018). Belugas were historically seen in and around the Kenai and Kasilof rivers during June aerial surveys conducted by ADFG in the late 1970s and early 1980s and by NMFS starting in 1993 (Shelden 
                    <E T="03">et al.,</E>
                     2015b), and throughout the summer by other researchers and local observers. In recent years, sightings in and near these rivers have been more typical in the spring and fall (Ovitz, 2019). It is unknown if this is due to increased monitoring efforts in the area or an increase in belugas using this area. While visual sightings indicate peaks in spring and fall, acoustic detections indicate that belugas can be present in the Kenai River throughout the winter (Castellote 
                    <E T="03">et al.,</E>
                     2016). Despite the historic sightings (1970s-1990s) of belugas throughout the summer (June-August) in the area, recent acoustic detections and visual sightings indicate that there appears to be a steep decline in beluga presence in the Kenai River during the summer, despite an annual return in recent years of 1-1.8 million sockeye salmon, which are important beluga prey.
                </P>
                <P>As described above, we have no reason to expect beluga whales to be concentrated in the path of Hilcorp's tug boats for the purposes of reproductive or feeding behaviors, but even if one or more of the 11 (Year 1) or 22 (Year 2) instances in which the brief tugboat operations intersects with an individual beluga is engaged in these behaviors, the anticipated short duration and low level disturbance of any such encounter would not be likely to impact reproductive or foraging success of any individuals.</P>
                <P>
                    <E T="03">Comment 25:</E>
                     CBD comments that NMFS' negligible impact determination relies largely on mitigation measures required under the IHAs that require visual observations, which it claims are ineffective.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS disagrees with this characterization of the negligible impact determination. Our discussion in the Negligible Impact Analysis and Determination section below contains the factors NMFS considered in reaching its negligible impact determinations. Although NMFS' implementing regulations at 50 CFR 216.104 (c) state that NMFS may incorporate successful implementation of mitigation measures to arrive at a negligible impact determination, for issuance of IHAs for Hilcorp's tug towing rig activity, NMFS did rely upon an assumption of set level of effectiveness in mitigation to make our negligible impact determinations. That said, based on prior monitoring efforts in Cook Inlet, it is clearly possible to detect and identify marine mammals to the species level at kilometers away from the source level, including beluga whales. This is dependent on several factors such as visual acuity, sea state, glare, animal behavior/body type, speed of travel for vessel and animal, 
                    <E T="03">etc..</E>
                     NMFS does not assume total effectiveness of monitoring, but the demonstrated record of protected species observer sightings for activities in Cook Inlet illustrate that visual monitoring is appropriate for implementing mitigation such as avoidance in this case.
                </P>
                <P>
                    <E T="03">Comment 26:</E>
                     CBD commented that NMFS relied on Hilcorp's commitment to operate with the favorable tide to reduce the power output of the tugs without including the requirement in the IHAs.
                </P>
                <P>
                    <E T="03">Response:</E>
                     The requirement to use a favorable tide and operate at night if a favorable tide fell during nighttime hours was included in the Proposed IHAs Year 1 and Year 2 that were available on our website (
                    <E T="03">https://www.fisheries.noaa.gov/action/incidental-take-authorization-hilcorp-alaska-llc-oil-and-gas-activities-cook-inlet-alaska-0</E>
                    ) as measures 4.f and 4.g. It is also in the final IHAs.
                </P>
                <P>
                    <E T="03">Comment 27:</E>
                     CBD commented that NMFS failed to ensure the least practicable adverse impact on Cook Inlet beluga whales by failing to consider requiring the use of passive acoustic monitors to detect the presence of marine mammals.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS considered the use of passive acoustic monitoring for mitigation purposes in the rulemaking for Hilcorp's oil and gas activities in Cook Inlet. As we stated in the notice of proposed rulemaking, passive acoustic monitoring for previous activities in Cook Inlet where incidental take was authorized by NMFS has not been an effective mitigation or monitoring measure due to environmental conditions (84 FR 12330, 12368; April 1, 2019 (incorporating by reference discussion of limited effectiveness of passive acoustic monitoring for survey mitigation in Hilcorp's petition for rulemaking)). For the same reasons, we have determined passive acoustic monitoring is not likely to be sufficiently effective at detection for real-time mitigation for Hilcorp's tug towing activities and is not included in the IHAs.
                </P>
                <P>
                    As CBD notes, academic researchers have begun to implement more effective passive acoustic monitors for research purposes at several places in Cook Inlet (Castellote 
                    <E T="03">et al.,</E>
                     2020). However, the framework used by those researchers is impractical, particularly for Hilcorp's planned activity, which primarily involves straight-line transit. An article on NOAA's website (
                    <E T="03">https://www.fisheries.noaa.gov/science-blog/beluga-whale-acoustic-monitoring-survey-post-3</E>
                    ) clearly illustrates the level of customization, expertise, and difficulty required to assemble a passive acoustic mooring to then deploy in the Inlet. Additionally, these instruments are stationary, which means to effectively use these monitors as a means of avoiding harassment of marine mammals during Hilcorp's activity, Hilcorp would need to build and successfully deploy dozens (or more) of stationary monitors along a route of travel that is subject to change depending upon weather or other environmental and shipping restrictions. Additionally, the data stored on these types of moorings is not accessible until they are retrieved by the researcher who deployed them. In the future, if an established network of passive acoustic monitors with shared access to the data is available, this could be a useful tool for implementing mitigation measures, but is currently not practicable.
                </P>
                <P>
                    <E T="03">Comment 28:</E>
                     CBD commented that NMFS failed to consider time-area restrictions for tugs such as Trading Bay in April and May and a prohibition on 
                    <PRTPAGE P="62375"/>
                    activities from July through September (CBD did not specify a location for this proposed measure).
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS did consider such a time-area restriction and does not agree that these proposed restrictions are appropriate under the least practicable adverse impact standard. Hilcorp's activity in Trading Bay would be either a single day of transit or several hours of positioning the jack-up rig at an existing well site. As discussed in our above comment response, there has been one published observation of potential (not confirmed) mating behavior of Cook Inlet beluga whales in Trading Bay. Surveys by NMFS or McGuire 
                    <E T="03">et al.</E>
                     with concentrated effort on the western coast of Cook Inlet have not yielded a comparable sighting. Closure of the entire area for two months is not practicable as Hilcorp would not be able to access the well sites that are part of the intended activity. As discussed above and in the species-specific section of the proposed IHAs, Cook Inlet belugas are highly concentrated in the upper Cook Inlet especially in the summer months (Goetz 
                    <E T="03">et al.,</E>
                     2012; McGuire 
                    <E T="03">et al.,</E>
                     2020). In the past, Cook Inlet beluga whales used the Kenai area in summer months but that trend has shifted in recent decades to occasional spring and fall sightings (Ovitz, 2019). Throughout the Inlet, mean group sizes during the summer and fall were largest in July and smallest in October, with the largest groups seen during mid-July and early August in the Susitna River Delta, while the smallest group sizes were in the Kenai River Delta. These patterns of high seasonal concentrations have continued to be documented since 2012 (
                    <E T="03">e.g.,</E>
                     McGuire 
                    <E T="03">et al.,</E>
                     2020). In reflection of this information, NMFS has imposed time area restrictions in the Susitna River Delta from April to November to reduce effects of Hilcorp's activity to the greatest extent practicable. In the case of the Tyonek platform, which lies within 10 miles of the mean lower-low water line of the Little Susitna and Beluga Rivers, Hilcorp will conduct aerial surveys to clear the Tyonek platform of Cook Inlet beluga whales to the greatest extent practicable. This evidence further suggests a closure in the middle Inlet during the summer months, in the season with longest daylight hours and best conditions for visual observations to implement mitigation and monitoring, is not appropriate under the least practicable adverse impact standard.
                </P>
                <P>See also response to comment 24.</P>
                <P>
                    <E T="03">Comment 29:</E>
                     CBD stated that NMFS failed to consider noise-quieting engines such as electric tugboats.
                </P>
                <P>
                    <E T="03">Response:</E>
                     The citation provided by CBD regarding electric tugboats was a link to a concept drawing of a boat that is not expected to be on the seas in the U.S. until at least 2023. NMFS is not aware of any commercially available seaworthy tug vessels that are used in tandem (
                    <E T="03">e.g.,</E>
                     three tug configuration) with effective quieting technologies or of any company or entity with electric tug fleets able to use them in tandem as required for Hilcorp's activities.
                </P>
                <P>
                    <E T="03">Comment 30:</E>
                     CBD commented that NMFS did not meaningfully consider the chosen clearance zone distance of 1,500 meters and that it is not equivalent to the Level B harassment zone.
                </P>
                <P>
                    <E T="03">Response:</E>
                     CBD is correct that the clearance zone required under the IHAs (1,500 m) is not equivalent to the Level B harassment zone (3,850 m). There is no requirement that the clearance zone be equal to or greater than the Level B harassment zone. Using the Level B harassment zone as the clearance zone would be impractical as identification of certain species may be unreliable at such distance in Cook Inlet's environmental conditions. The 1,500 m distance ensures more effective monitoring closest to the vessels, where any potential impact to animals is anticipated to be the greatest. While underway, protected species observers will observe for marine mammals to the greatest extent possible (and they are not limited to observing within 1,500 m of the vessel). Any marine mammal sighted by PSOs at any distance is noted and reported to NMFS, per the reporting requirements of the IHAs.
                </P>
                <P>
                    <E T="03">Comment 31:</E>
                     CBD comments that NMFS defines its purpose and need in the Environmental Assessment too narrowly, making issuance of successive IHAs the only option.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS disagrees with this characterization of purpose and need. Under section 101(a)(5)(D) of the MMPA, NMFS has an obligation to consider and grant requests for the taking of marine mammals incidental to a specified activity, provided they satisfy the relevant requirements. Hilcorp submitted an application for two IHAs, each covering 1 year of tug towing rig activity. Once deemed adequate and complete, NMFS had an obligation to consider and respond to these requests in the manner described in the implementing regulations. While Hilcorp's request for two IHAs did not guarantee that they would be issued (
                    <E T="03">i.e.,</E>
                     if one or both years of the specified activity did not satisfy the relevant MMPA standards, NMFS would not issue the IHA(s)), characterizing the purpose and need to include issuance of only one IHA would not be in accordance with our requirement to consider both adequate and complete requests submitted by Hilcorp.
                </P>
                <P>
                    <E T="03">Comment 32:</E>
                     CBD commented that NMFS segmented its analysis of the impacts of Hilcorp's activities under these IHAs from the activities authorized under the ITRs.
                </P>
                <P>
                    <E T="03">Response:</E>
                     As explained earlier (see Comment 1), NMFS is in the process of withdrawing the ITRs based on Hilcorp's representations that they will not be undertaking any further activities for which take was authorized under the ITR during the remaining period of effectiveness. The only take currently authorized by NMFS incidental to Hilcorp's activities in Cook Inlet, Alaska, over the next 2 years is through the two IHAs for the take incidental to tugs towing the jack-up rig, as described in this notice.
                </P>
                <P>
                    <E T="03">Comment 33:</E>
                     CBD commented that NMFS failed to consider several additional alternatives under NEPA including: requiring the use of passive acoustic monitoring to detect the presence of marine mammals; requiring the use of drones to detect the presence of marine mammals; requiring the use of electric tugboats; restrictions on the timing of activities when Cook Inlet belugas are less likely to be present; restrictions on the overall amount of authorized activity, and authorizing take incidental to decommissioning activity but not production activity.
                </P>
                <P>
                    <E T="03">Response:</E>
                     Under NEPA, NMFS is required to consider a reasonable range of alternatives. Our EA considered the preferred alternative, which satisfied our purpose and need, and the no-action alternative. We also considered, but rejected from further consideration, two variations of the preferred alternative, including alternative technologies (such as electric tugboats). Similarly, as explained in a previous response, NMFS is not requiring mitigation such as passive acoustic monitoring or electric tugboats because they do not satisfy the MMPA's least practicable adverse impact standard. NMFS is requiring a time-area closure specifically to enhance protection for Cook Inlet beluga whales based on the best available science. This mitigation measure to protect Cook Inlet beluga whales in a biologically important area at times of known high density of whales was included in the preferred alternative. NMFS did not explore “restrictions on the overall amount of authorized activity” because NMFS does not authorize the underlying activity, and restricting the amount would have changed the applicant's specified activity (and further was not necessary 
                    <PRTPAGE P="62376"/>
                    to reach our negligible impact determinations). NMFS did not consider authorizing take incidental to decommissioning (P&amp;A) activity but not production activity because for purposes of our MMPA analyses of the impacts of the tug activities, these are exactly the same activity—the same three tugboats pulling and positioning one jack-up rig for the time windows provided in the project description. NMFS is not authorizing any take of marine mammals incidental to production drilling itself or decommissioning itself, but rather the moving of the jack-up rig into position, which will then be used to complete those activities. Authorizing take incidental to tugs towing the jack-up rig to be used only for decommissioning purposes would be arbitrary and capricious.
                </P>
                <P>
                    <E T="03">Comment 34:</E>
                     CBD commented that NMFS' EA failed to consider impacts from vessels and other sources associated with Hilcorp's activity, even if they do not rise to the level of take.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS disagrees with this characterization. In the description of the activity in NMFS' EA, as in the 
                    <E T="04">Federal Register</E>
                     notice of proposed IHAs, NMFS includes a discussion of other activity associated with Hilcorp's rig-towing and why it does not rise to the level of take. NMFS has included that discussion in this 
                    <E T="04">Federal Register</E>
                     notice as well with further detail about the way Hilcorp plans to conduct those activities that means take is unlikely. Aspects of these sources, such as increased vessel traffic or helicopter traffic to the area, are addressed in the EA in the Cumulative Effects section.
                </P>
                <P>
                    <E T="03">Comment 35:</E>
                     CBD commented that NMFS' EA relies on mitigation measures required in the IHAs to dismiss the significance of impacts from Hilcorp's activity, claiming that the mitigation measures rely on marine mammals being detected by observers which CBD considers ineffective. CBD did not provide any examples or citations of this in their description.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS does not rely on ineffective mitigation measures to dismiss the significance of impacts—as described in the EA, the primary reason the impacts are considered insignificant are because of the limited duration of the activity (14 and 16 days respectively), the low level of noise created by the tug configuration, and the low density of marine mammals in the action area resulting in small exposure estimates. Further, NMFS disagrees with the characterization that the mitigation measures are “ineffective” because they rely on visual detection. NMFS has received many marine mammal monitoring reports over the years demonstrating that visual observers for marine mammals are effective in Cook Inlet. At no point in the MMPA or NEPA analysis does NMFS assume that mitigation is 100 percent effective, as environmental conditions can confound monitoring effort, but there is a spectrum of effectiveness when implementing mitigation, and visual observation in Cook Inlet is an appropriate means for detecting marine mammals to implement mitigation zones.
                </P>
                <P>
                    <E T="03">Comment 36:</E>
                     CBD comments that NMFS' EA fails to properly analyze the current state of climate change and how new fossil fuel production contributes to climate change. CBD claims that NMFS must consider and disclose how facilitating fossil fuel production and total greenhouse gas emissions associated with the project will exacerbate climate change. As part of this analysis, CBD contends that NMFS must consider downstream greenhouse gas emissions.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS considers climate change in its EA. However, as described previously, NMFS does not authorize production drilling or any of Hilcorp's activities but rather take of marine mammals incidental to Hilcorp's activities. In Federal waters, BOEM conducts lease sales that provide qualified bidders the opportunity to bid on blocks of the outer continental shelf to gain conditional rights to explore, develop, and produce oil and natural gas in those blocks. BOEM's consideration of climate change for its lease sales is found in the agency's environmental compliance documents, such as the EIS written for Lease Sale 244 (BOEM, 2016), the most recent lease sale in Cook Inlet, Alaska. Of note, for Alaska state waters, Hilcorp would obtain necessary permits for production drilling from Alaska Department of Environmental Conservation. NMFS' IHAs cover take of marine mammals incidental to tugs towing and positioning a jack-up rig, which may occur even if Hilcorp produces no natural gas or oil from their wells with the jack-up rig.
                </P>
                <P>
                    <E T="03">Comment 37:</E>
                     CBD commented that NMFS failed to properly consider impacts to subsistence use as Hilcorp's activity would impede the recovery of Cook Inlet beluga whales, which in turn affects the beluga harvest.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS considered impacts on subsistence users, especially for species such as harbor seals, which are harvested by communities along Cook Inlet. NMFS found that take of Cook Inlet beluga whales incidental to Hilcorp's tug towing activity would have a negligible impact on the stock and there is no evidence to suggest that the impacts of 14 or 16 days of rig towing per year for 2 years (resulting in 11 and 22 low-level behavioral disturbance events, respectively), would impact the reproductive success or survival of any individual in any way, much less impede the recovery or impact the availability of Cook Inlet beluga whales for subsistence harvest were a harvest to occur.
                </P>
                <P>
                    <E T="03">Comment 38:</E>
                     CBD also commented that NMFS failed to take a hard look at cumulative impacts of the IHAs, specifically with respect to Cook Inlet beluga whales.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS disagrees with the assertion that cumulative impacts were not adequately considered, especially with respect to Cook Inlet beluga whales. Cook Inlet beluga whales are frequently discussed together with the other 11 species of marine mammal for which take is authorized, as cited in CBD's example regarding vessel noise, because effects of vessel noise on Cook Inlet beluga whales are expected to be highly similar to the effects of vessel noise on other marine mammals, except in that the number of takes is different (and lower) than some other species due to their likely distribution in the area. As described in Castellote 
                    <E T="03">et al.</E>
                     (2019), Cook Inlet beluga whales are one of the species that exhibits high site fidelity with a strong temporal correlation. Because of this, there is strong evidence that Cook Inlet beluga whales are not expected to occur in the project area during the ice-free season when Hilcorp would be towing the rigs in a largely offshore environment. While Cook Inlet beluga whales exhibit high site fidelity, it is not fidelity to the project area at the time of year and location of Hilcorp's platforms. They may be affected by other activities in the area where they would be expected to occur in ice-free seasons, such as the Port of Anchorage, and those activities are discussed in our Cumulative Effects section of the EA.
                </P>
                <P>
                    Cumulative impacts have been adequately addressed under NEPA in the final environmental assessment (EA) supporting NMFS' determination. In the final EA, we reviewed potential direct, indirect, and cumulative impacts to protected species and their environment, associated with NMFS' proposed action and alternatives. Separately, cumulative effects were analyzed as required through NMFS' required intra-agency consultation under section 7 of the ESA. The Biological Opinion (BiOp) that NMFS Alaska Region issued on September 9, 2022, determined that NMFS' action of issuing the IHAs is not likely to 
                    <PRTPAGE P="62377"/>
                    jeopardize the continued existence of listed marine mammals or result in the destruction or adverse modification of critical habitat of such species, including Cook Inlet beluga whales.
                </P>
                <P>
                    <E T="03">Comment 39:</E>
                     CBD commented that NMFS' cumulative impacts analysis ignores the impacts of take of Cook Inlet beluga whales already authorized or occurring, including take from other ITAs, research permits, and unpermitted takes from vessel noise, water pollution, and other impacts. Further, CBD commented that NMFS should attempt to quantify take and analyze impacts to the species in the EA.
                </P>
                <P>
                    <E T="03">Response:</E>
                     NMFS agrees with CBD that a quantification of take may be helpful to the public and has included those numbers in the appropriate section of the EA's cumulative effects discussion. However, these take numbers are frequently taken out of context when purely summed. Takes of marine mammals, including Cook Inlet beluga whales, through other ITAs is considered in NMFS' environmental baseline when conducting the necessary analysis for issuance of these IHAs. There are other takes of Cook Inlet beluga whales authorized for scientific research and enhancement of the species. While they are all considered “take” for purposes of issuing an authorization or permit under the MMPA in advance of an activity, the context of these takes is important (see responses to Comments 13 and 14). Authorized takes, in the research context, are what allow researchers frequently cited by NMFS and CBD (
                    <E T="03">e.g.,</E>
                     Castellote 
                    <E T="03">et al.,</E>
                     McGuire 
                    <E T="03">et al.,</E>
                     Shelden 
                    <E T="03">et al.,</E>
                     Hobbs 
                    <E T="03">et al.</E>
                    ) to collect the scientific data necessary to inform their publications. Researchers' interactions with marine mammals are carefully controlled through permit conditions and reporting requirements, which often require research efforts to cease if any effects to important biological functions are detected by qualified researchers that are skilled at observing marine mammal behavior (NMFS, 2019).
                </P>
                <P>The context of the take is of the utmost importance when cumulatively evaluating takes of marine mammals, as the intensity of impacts from a given activity can vary widely. For example, an animal exposed to noise levels just above our harassment threshold in a non-critical area may experience a small change in a behavioral pattern with no biological consequence while an animal exposed to very loud noise levels in an area where active critical foraging occurs could result in behavioral changes that may be more likely to impact fitness. While both of these examples would be characterized as Level B harassment, the resulting impact on the population could be different. Context differences such as these are analyzed in our negligible impact analysis for each application under the MMPA.</P>
                <P>Furthermore, NMFS does not consider unpermitted “takes” explicitly in its analysis. It is difficult to determine if a take has occurred without monitoring in place to assess the effects of a particular activity. However, NMFS broadly and qualitatively addresses potential effects from other types of activity or development without distinguishing if any potential “take” is permitted. For example, NMFS considers potential effects of construction activities, some of which have the potential to result in take, in the Cumulative Effects section of the EA. NMFS discusses the overall effects of construction without discerning individual takes due to construction or attributing takes to a “permitted” or “unpermitted” status.</P>
                <P>
                    <E T="03">Comment 40:</E>
                     CBD commented that NMFS failed to consider Hilcorp's poor track record of environmental and safety violations and accidents and how this may affect the environmental impacts of Hilcorp's activities under the IHAs.
                </P>
                <P>
                    <E T="03">Response:</E>
                     Oil spills, accidents, or other disasters stemming from man-made structures in Cook Inlet are not considered, as they are not authorized and are a breach of authorizations and perhaps of other agencies' regulations. It is the responsibility of the applicants to comply with all additional regulations, and to work with the state to obtain approval of their Oil Discharge Prevention and Contingency Plans (ODPCP).
                </P>
                <P>
                    <E T="03">Comment 41:</E>
                     CBD commented that NMFS should reinitiate and complete consultation on the 5-year take regulations and issue a biological opinion that properly analyzes the impacts of all of Hilcorp's activities on threatened and endangered species and their habitats, including from tugs towing rigs.
                </P>
                <P>
                    <E T="03">Response:</E>
                     As described above, NMFS is in the process of withdrawing the incidental take regulations issued to Hilcorp in 2019, as none of the activity for which incidental take was authorized is planned to occur in the foreseeable future. The remaining take of marine mammals incidental to Hilcorp's activity is solely from Hilcorp's tug-towing activities, which are covered by these IHAs and for which consultation was completed. The resulting Biological Opinion was issued on September 9, 2022.
                </P>
                <HD SOURCE="HD1">Changes From Proposed IHAs to Final IHAs</HD>
                <P>There are several changes from the proposed IHAs, starting with the timing of the activity. The Year 1 and Year 2 IHAs were initially proposed to become effective in April 2022 and April 2023, respectively. This timeline has been delayed during the course of processing the IHA requests. Hilcorp now requests that the Year 1 IHA be effective September 2022 and the Year 2 IHA become effective on September 2023. Since the conclusion of the public comment period in June 2022, NMFS has reviewed newly available information, including recent draft Stock Assessment Reports, information on relevant Unusual Mortality Events, and other scientific literature, and incorporated this information into our analysis of impacts on marine mammals and their habitat. Additionally, NMFS removed the consideration of renewals of the IHAs at Hilcorp's request.</P>
                <P>During the processing of the IHA requests, Hilcorp notified NMFS of the need to conduct the initial rig tow in June 2022. On April 28, 2022, Hilcorp sent a letter to NMFS describing the need to move the jack-up rig as well as the mitigation and monitoring Hilcorp planned to employ during the rig move to avoid take. In a letter dated May 17, 2022, in consideration of the low likelihood of exposures above the 120 dB harassment threshold, the short duration of the jack-up rig move, the further reduced likelihood of exposure above 120 dB supported by the expanded mitigation, and further, the reduced probability that an animal exposed to a received level above 120 dB tugboat noise would respond in a manner that qualifies as a take under the MMPA, NMFS concurred with Hilcorp's assessment that take of marine mammals by Level B harassment is unlikely to occur during the transport of the jack-up rig from the Rig Tender's Dock in Nikiski to the Tyonek platform in middle Cook Inlet. NMFS' concurrence letter did not authorize any take of marine mammals under the MMPA or ESA incidental to the rig move. As a result of this initial move, Hilcorp's planned Year 1 activities have been reduced to approximately 14 days of tug towing and positioning. This reduction in activity duration under the IHA, and appropriate reductions in take estimates, have been made throughout this notice and the Year 1 IHA.</P>
                <P>
                    Hilcorp began the mobilization process in June 2022 as described in their April 28, 2022, letter and fully abided by all of the minimization measures described therein. Three 
                    <PRTPAGE P="62378"/>
                    ocean-going tugs towed the jack-up rig for 32.2 miles and the approximate total time under load including transiting, holding and positioning amounted to 27 hours. The jack-up rig was positioned at the Tyonek platform where it has remained since that mobilization. During the rig move, Hilcorp observed 14 harbor porpoises and six harbor seals at distances ranging from 75 meters to 4,960 meters from the tug towing jack-up rig configuration, and no beluga whales. Based on the distance at which some animals were observed and our assumed source levels, it is possible individual animals received sound levels greater than 120 dB, which is NMFS' current threshold for estimating when Level B harassment is predicted to occur, though there are other qualitative factors that may be considered. There are certain characteristics of tugging that reduce the probability that being exposed to received levels above 120 dB will result in disruption of behavioral patterns. Tugboats under load, especially a multi-tug configuration, are slow-moving as compared to typical recreational and commercial vessel traffic. Assuming an animal was stationary, exposure from the moving tug configuration would be on the order of minutes in any particular location. Hilcorp's monitoring report indicates these animals were traveling or swimming, with three animals changing their course of direction when approaching the tug configuration, suggesting their exposure time could have been even shorter. The slow, predictable, and generally straight path of this tug configuration further lessened the likelihood that exposures at the expected levels resulted in the harassment of marine mammals. The slow transit along a predictable path occurred in an area of routine vessel traffic where many large vessels move in slow straight-line paths, and some individuals are expected to be habituated to these sorts of exposures.
                </P>
                <P>NMFS made two changes with respect to species and stocks included in the final IHAs. During the course of consultation under the ESA, it was brought to NMFS' attention that humpback whales in Cook Inlet could potentially belong to the Western North Pacific stock as well as the Central North Pacific stock. NMFS has considered both stocks in our analysis for the final IHAs. Additionally, BOEM suggested that Pacific white-sided dolphins be included based on acoustic detection data. They have been included in our analysis and take authorized in the final IHAs.</P>
                <P>During the process of section 7 consultation under the ESA, Hilcorp notified NMFS that complying with the Susitna Delta mitigation zone as proposed would not be practicable for operations at their Tyonek platform because the location of the platform is within the Susitna Delta exclusion zone. The dates and applicability of the Susitna Delta exclusion zone have been changed from the proposed to final IHAs. The changes, as well as additional protective measures associated with the change, are described in more detail in the Mitigation section below.</P>
                <HD SOURCE="HD1">Description of Marine Mammals in the Area of Specified Activities</HD>
                <P>
                    Sections 3 and 4 of the application summarize available information regarding status and trends, distribution and habitat preferences, and behavior and life history of the potentially affected species. Additional information regarding population trends and threats may be found in NMFS's Stock Assessment Reports (SARs; 
                    <E T="03">https://www.fisheries.noaa.gov/national/marine-mammal-protection/marine-mammal-stock-assessments</E>
                    ) and more general information about these species (
                    <E T="03">e.g.,</E>
                     physical and behavioral descriptions) may be found on NMFS's website (
                    <E T="03">https://www.fisheries.noaa.gov/find-species</E>
                    ).
                </P>
                <P>Table 4 lists all species or stocks for which take is expected and authorized for this action, and summarizes information related to the population or stock, including regulatory status under the MMPA and Endangered Species Act (ESA) and potential biological removal (PBR), where known. For taxonomy, we follow the Committee on Taxonomy (2021). PBR is defined by the MMPA as the maximum number of animals, not including natural mortalities, that may be removed from a marine mammal stock while allowing that stock to reach or maintain its optimum sustainable population (as described in NMFS's SARs). While no mortality is anticipated or authorized here, PBR and annual serious injury and mortality from anthropogenic sources are included here as gross indicators of the status of the species and other threats.</P>
                <P>
                    Marine mammal abundance estimates presented in this document represent the total number of individuals that make up a given stock or the total number estimated within a particular study or survey area. NMFS's stock abundance estimates for most species represent the total estimate of individuals within the geographic area, if known, that comprises that stock. For some species, this geographic area may extend beyond U.S. waters. All managed stocks in this region are assessed in NMFS's U.S. 2021 SARs (
                    <E T="03">e.g.,</E>
                     Muto 
                    <E T="03">et al.,</E>
                     2022). All values presented in Table 4 are the most recent available at the time of publication and are available in the 2021 SARs (Muto 
                    <E T="03">et al.</E>
                     2022) (available online at: 
                    <E T="03">https://www.fisheries.noaa.gov/national/marine-mammal-protection/draft-marine-mammal-stock-assessment-reports</E>
                    ).
                </P>
                <GPOTABLE COLS="7" OPTS="L2,p7,7/8,i1" CDEF="s50,r50,r50,xls30,r40,8,8">
                    <TTITLE>Table 4—Marine Mammal Species or Stocks for Which Take Is Expected and Authorized</TTITLE>
                    <BOXHD>
                        <CHED H="1">Common name</CHED>
                        <CHED H="1">Scientific name</CHED>
                        <CHED H="1">Stock</CHED>
                        <CHED H="1">
                            ESA/MMPA status; strategic
                            <LI>
                                (Y/N) 
                                <SU>1</SU>
                            </LI>
                        </CHED>
                        <CHED H="1">
                            Stock abundance
                            <LI>
                                (CV, N
                                <E T="0732">min</E>
                                , most recent abundance survey) 
                                <SU>2</SU>
                            </LI>
                        </CHED>
                        <CHED H="1">PBR</CHED>
                        <CHED H="1">
                            Annual M/SI 
                            <SU>3</SU>
                        </CHED>
                    </BOXHD>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Order Cetartiodactyla—Cetacea—Superfamily Mysticeti (baleen whales)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="22">Family Eschrichtiidae:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Gray whale</ENT>
                        <ENT>
                            <E T="03">Eschrichtius robustus</E>
                        </ENT>
                        <ENT>Eastern North Pacific</ENT>
                        <ENT>-, -, N</ENT>
                        <ENT>26,960 (0.05, 25,849, 2016)</ENT>
                        <ENT>801</ENT>
                        <ENT>131</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Family Balaenidae:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Humpback whale</ENT>
                        <ENT>
                            <E T="03">Megaptera novaeangliae</E>
                        </ENT>
                        <ENT>Western North Pacific</ENT>
                        <ENT>E, D, Y</ENT>
                        <ENT>1,107 (0.3, 865, 2006)</ENT>
                        <ENT>3</ENT>
                        <ENT>2.8</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Humpback whale</ENT>
                        <ENT>
                            <E T="03">Megaptera novaeangliae</E>
                        </ENT>
                        <ENT>Central North Pacific</ENT>
                        <ENT>E, D, Y</ENT>
                        <ENT>10,103 (0.3, 7,890, 2006)</ENT>
                        <ENT>83</ENT>
                        <ENT>26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Minke whale</ENT>
                        <ENT>
                            <E T="03">Balaenoptera acutorostrata</E>
                        </ENT>
                        <ENT>Alaska</ENT>
                        <ENT>-, -, N</ENT>
                        <ENT>N/A (see SAR, N/A, see SAR)</ENT>
                        <ENT>UND</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Family Balaenopteridae (rorquals):</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">Fin whale</ENT>
                        <ENT>
                            <E T="03">Balaenoptera physalus</E>
                        </ENT>
                        <ENT>Northeast Pacific</ENT>
                        <ENT>E, D, Y</ENT>
                        <ENT>see SAR (see SAR, see SAR, 2013)</ENT>
                        <ENT>see SAR</ENT>
                        <ENT>0.6</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <PRTPAGE P="62379"/>
                        <ENT I="21">
                            <E T="02">Superfamily Odontoceti (toothed whales, dolphins, and porpoises)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="22">Family Delphinidae:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Beluga whale</ENT>
                        <ENT>
                            <E T="03">Delphinapterus leucas</E>
                        </ENT>
                        <ENT>Cook Inlet</ENT>
                        <ENT>E, D, Y</ENT>
                        <ENT>279 (0.061, 267, 2018)</ENT>
                        <ENT>0.53</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Killer whale</ENT>
                        <ENT>
                            <E T="03">Orcinus orca</E>
                        </ENT>
                        <ENT>Alaska Resident</ENT>
                        <ENT>-, -, N</ENT>
                        <ENT>2,347 c (N/A, 2347, 2012)</ENT>
                        <ENT>24</ENT>
                        <ENT>1</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Killer whale</ENT>
                        <ENT>
                            <E T="03">Orcinus orca</E>
                        </ENT>
                        <ENT>Gulf of Alaska, Aleutian Islands, and Bering Sea Transient</ENT>
                        <ENT>-, -, N</ENT>
                        <ENT>587 c (N/A, 587, 2012)</ENT>
                        <ENT>5.87</ENT>
                        <ENT>0.8</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Pacific white-sided dolphin</ENT>
                        <ENT>
                            <E T="03">Lagenorhynchus obliquidens</E>
                        </ENT>
                        <ENT>North Pacific</ENT>
                        <ENT>-, -, N</ENT>
                        <ENT>26,880 (N/A, unknown, 1998)</ENT>
                        <ENT>UND</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Family Phocoenidae (porpoises):</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Harbor porpoise</ENT>
                        <ENT>
                            <E T="03">Phocoena phocoena</E>
                        </ENT>
                        <ENT>Gulf of Alaska</ENT>
                        <ENT>-, -, Y</ENT>
                        <ENT>31,046 (0.21, N/A, 1998)</ENT>
                        <ENT>UND</ENT>
                        <ENT>72</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">Dall's porpoise</ENT>
                        <ENT>
                            <E T="03">Phocoenoides dalli</E>
                        </ENT>
                        <ENT>Alaska</ENT>
                        <ENT>-, -, N</ENT>
                        <ENT>see SAR (0.097, see SAR, 2015)</ENT>
                        <ENT>131</ENT>
                        <ENT>37</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Order Carnivora—Superfamily Pinnipedia</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="22">Family Otariidae (eared seals and sea lions):</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Steller sea lion</ENT>
                        <ENT>
                            <E T="03">Eumetopias jubatus</E>
                        </ENT>
                        <ENT>Western</ENT>
                        <ENT>E, D, Y</ENT>
                        <ENT>52,932 a (see SAR, 52,932, 2019)</ENT>
                        <ENT>318</ENT>
                        <ENT>254</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">California sea lion</ENT>
                        <ENT>
                            <E T="03">Zalophus californianus</E>
                        </ENT>
                        <ENT>U.S.</ENT>
                        <ENT>-, -, N</ENT>
                        <ENT>257,606 (N/A, 233,515, 2014)</ENT>
                        <ENT>14,011</ENT>
                        <ENT>&gt;320</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Family Phocidae (earless seals):</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Harbor seal</ENT>
                        <ENT>
                            <E T="03">Phoca vitulina</E>
                        </ENT>
                        <ENT>Cook Inlet/Shelikof</ENT>
                        <ENT>-, -, N</ENT>
                        <ENT>28,411 (see SAR, 26,907, 2018)</ENT>
                        <ENT>807</ENT>
                        <ENT>107</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         Endangered Species Act (ESA) status: Endangered (E), Threatened (T)/MMPA status: Depleted (D). A dash (-) indicates that the species is not listed under the ESA or designated as depleted under the MMPA. Under the MMPA, a strategic stock is one for which the level of direct human-caused mortality exceeds PBR or which is determined to be declining and likely to be listed under the ESA within the foreseeable future. Any species or stock listed under the ESA is automatically designated under the MMPA as depleted and as a strategic stock.
                    </TNOTE>
                    <TNOTE>
                        <SU>2</SU>
                         NMFS marine mammal stock assessment reports online at: 
                        <E T="03">www.nmfs.noaa.gov/pr/sars/.</E>
                         CV is coefficient of variation; Nmin is the minimum estimate of stock abundance. In some cases, CV is not applicable depending on the methodology described in the stock assessment report (SAR) and the date of last available survey data. Where necessary, NMFS refers reader to the SAR for more detail.
                    </TNOTE>
                    <TNOTE>
                        <SU>3</SU>
                         These values, found in NMFS's SARs, represent annual levels of human-caused mortality plus serious injury from all sources combined (
                        <E T="03">e.g.,</E>
                         commercial fisheries, ship strike). Annual mortality and serious injury often cannot be determined precisely and is in some cases presented as a minimum value or range.
                    </TNOTE>
                </GPOTABLE>
                <P>As indicated above, all 12 species (with 14 managed stocks) in Table 4 temporally and spatially co-occur with the activity to the degree that take could reasonably occur, and we have authorized it. In addition, the northern sea otter may be found in Cook Inlet, Alaska. However, sea otters are managed by the U.S. Fish and Wildlife Service and are not considered further in this document.</P>
                <HD SOURCE="HD2">Pacific White-Sided Dolphin</HD>
                <P>
                    Pacific white-sided dolphins are a pelagic species. They are found throughout the temperate North Pacific Ocean, north of the coasts of Japan and Baja California, Mexico (Muto 
                    <E T="03">et al.,</E>
                     2018). They are most common between the latitudes of 38° North and 47° North (from California to Washington). The distribution and abundance of Pacific white-sided dolphins may be affected by large-scale oceanographic occurrences, such as El Niño, and by underwater acoustic deterrent devices (NPS, 2018a).
                </P>
                <P>
                    Scientific studies and data are lacking relative to the presence or abundance of Pacific white-sided dolphins in or near Cook Inlet, Alaska. Most observations of Pacific white-sided dolphins occur off the outer coast or in inland waterways near entrances to the open ocean. A report of acoustic monitoring efforts during Hilcorp's 3D seismic survey in 2020 concluded that Pacific white-sided dolphins were briefly detected near Iniskin Bay in Cook Inlet. Detections of vocalizations typically lasted on the order of minutes, suggesting the animals did not remain in the area and/or continue vocalizing for extended durations. These observational data, combined with anecdotal information, indicate that there is a small potential for Pacific white-sided dolphins to occur in the Project area. On May 7, 2014, Apache Alaska observed three Pacific white-sided dolphins during an aerial survey near Kenai. This is one of the only recorded visual observations of Pacific white-sided dolphins in Cook Inlet; they have not been reported in groups as large as those estimated in other parts of Alaska (
                    <E T="03">e.g.,</E>
                     92 animals in NMFS' IHAs for Tongass Narrows). Due to the cryptic nature of the species and the lack of maneuverability of the tug configuration, take of Pacific white-sided dolphins was added to the proposed authorizations for Year 1 and Year 2.
                </P>
                <HD SOURCE="HD2">Humpback whale</HD>
                <P>
                    Humpback whales are found throughout southern Alaska in a variety of marine environments, including open-ocean, near-shore waters, and areas with strong tidal currents (Dahlheim 
                    <E T="03">et al.,</E>
                     2009). Most humpback whales are migratory and spend winters in the breeding grounds off either Hawaii or Mexico. Humpback whales are regularly present and feeding in Cook Inlet in the summer. Current threats to humpback whales include vessel strikes, spills, climate change, and commercial fishing operations (Muto 
                    <E T="03">et al.,</E>
                     2021).
                </P>
                <P>
                    Humpback whales worldwide were designated as “endangered” under the Endangered Species Conservation Act in 1970, and were listed under the ESA at its inception in 1973. However, on September 8, 2016, NMFS published a final decision that changed the status of humpback whales under the ESA (81 FR 62259), effective October 11, 2016. The decision recognized the existence of 14 distinct population segments (DPSs) based on distinct breeding areas in tropical and temperate waters. Five of the 14 DPSs were classified under the ESA (4 endangered and 1 threatened), 
                    <PRTPAGE P="62380"/>
                    while the other 9 DPSs were delisted. Humpback whales found in the project area are predominantly members of the Hawaii DPS, which is not listed under the ESA. However, based on analyses of photo-identification studies in Alaska, members of the Mexico DPS and the Western North Pacific DPS, which are listed as threatened and endangered respectively, are thought to occur in Cook Inlet. Approximately 1 percent of all humpback whales in Cook Inlet are thought to belong to the endangered Western North Pacific DPS and 11 percent are thought to belong to the threatened Mexico DPS. All other humpback whales present are thought to belong to the non-listed Hawaii DPS (Wade 
                    <E T="03">et al.,</E>
                     2021). Members of different DPSs are known to intermix on feeding grounds; therefore, all waters off the coast of Alaska should be considered to have ESA-listed humpback whales. Critical habitat was recently designated near the entrance of lower Cook Inlet for Western North Pacific DPS and Mexico DPS humpback whales (86 FR 21082, April 21, 2021); however, Hilcorp's action area does not spatially overlap with any critical habitat designated for humpback whale DPS.
                </P>
                <P>
                    The DPSs of humpback whales that were identified through the ESA listing process do not necessarily equate to the existing MMPA stocks. The stock delineations of humpback whales under the MMPA are currently under review. Until this review is complete, NMFS considers humpback whales in Cook Inlet to primarily be part of the Central North Pacific stock, with a status of endangered under the ESA and designations of strategic and depleted under the MMPA (Muto 
                    <E T="03">et al.,</E>
                     2021). As described in the above Changes from Proposed IHAs to Final IHAs, during the course of consultation under the Endangered Species Act, it was brought to NMFS' attention that humpback whales in Cook Inlet could occasionally be from the Western North Pacific stock, and therefore have been included as a potential stock in the Final IHAs.
                </P>
                <P>
                    In the summer, humpback whales are regularly present and feeding in the Cook Inlet region, including Shelikof Strait, Kodiak Island bays, and the Barren Islands, in addition to Gulf of Alaska regions adjacent to the southeast side of Kodiak Island (especially Albatross Banks), the Kenai and Alaska peninsulas, Elizabeth Island, as well as south of the Aleutian Islands. Humpbacks also may be present in some of these areas throughout autumn (Muto 
                    <E T="03">et al.,</E>
                     2017).
                </P>
                <P>
                    Humpback whales have been observed during marine mammal surveys conducted in Cook Inlet; however, their presence is largely confined to lower Cook Inlet. During SAExploration's 2015 seismic program, three humpback whales were observed in Cook Inlet; two near the Forelands and one in Kachemak Bay (Kendall 
                    <E T="03">et al.,</E>
                     2015). During NMFS Cook Inlet beluga whale aerial surveys from 2000 to 2018, there were 88 sightings of 191 estimated individual humpback whales in lower Cook Inlet (Shelden 
                    <E T="03">et al.,</E>
                     2017). They have been regularly seen near Kachemak Bay during the summer months (Rugh 
                    <E T="03">et al.,</E>
                     2005). There are observations of humpback whales as far north as Anchor Point, with recent summer observations extending to Cape Starichkof (Owl Ridge, 2014). Several humpback whale sightings occurred lower Cook Inlet between Iniskin Peninsula and Kachemak Bay near Augustine, Barren, and Elizabeth Islands (Shelden 
                    <E T="03">et al.,</E>
                     2013, 2015, 2017). There were two sightings of three humpback whales observed near Ladd Landing north of the Forelands on the recent Harvest Alaska Cook Inlet Pipeline Extension (CIPL) project (Sitkiewicz 
                    <E T="03">et al.,</E>
                     2018). There were 14 sightings of 38 humpback whales observed in the 2019 Hilcorp lower Cook Inlet seismic survey in the fall (Fairweather Science, 2020). This higher number of humpback whales was expected in the lower Cook Inlet region than Hilcorp's proposed work in the late summer/fall period.
                </P>
                <P>
                    Ferguson 
                    <E T="03">et al.</E>
                     (2015) identified a biologically important area (BIA), in which humpback whales are known to concentrate for feeding, in the Gulf of Alaska region. The BIA encompasses the waters east of Kodiak Island (the Albatross and Portlock Banks), a target for historical commercial whalers based out of Port Hobron, Alaska (Ferguson 
                    <E T="03">et al.,</E>
                     2015; Reeves 
                    <E T="03">et al.,</E>
                     1985; Witteveen 
                    <E T="03">et al.,</E>
                     2007). This BIA also includes waters along the southeastern side of Shelikof Strait and in the bays along the northwestern shore of Kodiak Island. The highest densities of humpback whales around the Kodiak Island BIA occur from July-August (Ferguson 
                    <E T="03">et al.,</E>
                     2015). This BIA lies directly south but does not spatially overlap with Hilcorp's proposed action area.
                </P>
                <P>
                    A detailed description of the of the other species likely to be affected by Hilcorp's tug towing jack-up rig activity, including brief introductions to the species and relevant stocks as well as available information regarding population trends and threats, and information regarding local occurrence, were provided in the 
                    <E T="04">Federal Register</E>
                     notice for the proposed IHA (87 FR 27597, May 9, 2022); since that time, we are not aware of any changes in the status of these species and stocks; therefore, detailed descriptions are not provided here. Please refer to that 
                    <E T="04">Federal Register</E>
                     notice for these descriptions. Please also refer to NMFS' website (
                    <E T="03">https://www.fisheries.noaa.gov/find-species</E>
                    ) for generalized species accounts.
                </P>
                <HD SOURCE="HD2">Marine Mammal Hearing</HD>
                <P>
                    Hearing is the most important sensory modality for marine mammals underwater, and exposure to anthropogenic sound can have deleterious effects. To appropriately assess the potential effects of exposure to sound, it is necessary to understand the frequency ranges marine mammals are able to hear. Not all marine mammal species have equal hearing capabilities (
                    <E T="03">e.g.,</E>
                     Richardson 
                    <E T="03">et al.,</E>
                     1995; Wartzok and Ketten, 1999; Au and Hastings, 2008). To reflect this, Southall 
                    <E T="03">et al.</E>
                     (2007, 2019) recommended that marine mammals be divided into hearing groups based on directly measured (behavioral or auditory evoked potential techniques) or estimated hearing ranges (behavioral response data, anatomical modeling, 
                    <E T="03">etc.</E>
                    ). Note that no direct measurements of hearing ability have been successfully completed for mysticetes (
                    <E T="03">i.e.,</E>
                     low-frequency cetaceans). Subsequently, NMFS (2018) described generalized hearing ranges for these marine mammal hearing groups. Generalized hearing ranges were chosen based on the approximately 65 decibel (dB) threshold from the normalized composite audiograms, with the exception for lower limits for low-frequency cetaceans where the lower bound was deemed to be biologically implausible and the lower bound from Southall 
                    <E T="03">et al.</E>
                     (2007) retained. Marine mammal hearing groups and their associated hearing ranges are provided in Table 5.
                    <PRTPAGE P="62381"/>
                </P>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s100,xs72">
                    <TTITLE>Table 5—Marine Mammal Hearing Groups</TTITLE>
                    <TDESC>[NMFS, 2018]</TDESC>
                    <BOXHD>
                        <CHED H="1">Hearing group</CHED>
                        <CHED H="1">Generalized hearing range *</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Low-frequency (LF) cetaceans (baleen whales)</ENT>
                        <ENT>7 Hz to 35 kHz.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mid-frequency (MF) cetaceans (dolphins, toothed whales, beaked whales, bottlenose whales)</ENT>
                        <ENT>150 Hz to 160 kHz.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            High-frequency (HF) cetaceans (true porpoises,
                            <E T="03"> Kogia,</E>
                             river dolphins, cephalorhynchid, 
                            <E T="03">Lagenorhynchus cruciger</E>
                             &amp; 
                            <E T="03">L. australis</E>
                            )
                        </ENT>
                        <ENT>275 Hz to 160 kHz.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Phocid pinnipeds (PW) (underwater) (true seals)</ENT>
                        <ENT>50 Hz to 86 kHz.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Otariid pinnipeds (OW) (underwater) (sea lions and fur seals)</ENT>
                        <ENT>60 Hz to 39 kHz.</ENT>
                    </ROW>
                    <TNOTE>
                        * Represents the generalized hearing range for the entire group as a composite (
                        <E T="03">i.e.,</E>
                         all species within the group), where individual species' hearing ranges are typically not as broad. Generalized hearing range chosen based on ~65 dB threshold from normalized composite audiogram, with the exception for lower limits for LF cetaceans (Southall 
                        <E T="03">et al.,</E>
                         2007) and PW pinniped (approximation).
                    </TNOTE>
                </GPOTABLE>
                <P>
                    The pinniped functional hearing group was modified from Southall 
                    <E T="03">et al.</E>
                     (2007) on the basis of data indicating that phocid species have consistently demonstrated an extended frequency range of hearing compared to otariids, especially in the higher frequency range (Hemilä 
                    <E T="03">et al.,</E>
                     2006; Kastelein 
                    <E T="03">et al.,</E>
                     2009; Reichmuth and Holt, 2013).
                </P>
                <P>For more detail concerning these groups and associated frequency ranges, please see NMFS (2018) for a review of available information.</P>
                <HD SOURCE="HD1">Potential Effects of Specified Activities on Marine Mammals and Their Habitat</HD>
                <P>The underwater noise from Hilcorp's tug towing jack-up rig activity has the potential to result in behavioral harassment of marine mammals in the vicinity of the survey area. The notice of proposed IHA (87 FR 27597, May 9, 2022) included a discussion of the effects of anthropogenic noise on marine mammals and the potential effects of underwater noise from Hilcorp's tug towing jack-up rig activity on marine mammals and their habitat. The effects described in the notice of proposed IHAs are expected to be the same on Western North Pacific stock of humpback whales and Pacific white-sided dolphins as for the other species and stocks considered in the proposed IHAs. That information and analysis is incorporated by reference into this final IHA determination and is not repeated here; please refer to the notice of proposed IHA (87 FR 27597, May 9, 2022).</P>
                <HD SOURCE="HD1">Estimated Take</HD>
                <P>This section provides an estimate of the number of incidental takes authorized through these IHAs, which informs both NMFS' consideration of “small numbers” and the negligible impact determinations.</P>
                <P>Harassment is the only type of take reasonably expected to result from these activities. Except with respect to certain activities not pertinent here, section 3(18) of 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>Authorized takes would be by Level B harassment only, in the form of disruption of behavioral patterns for individual marine mammals resulting from exposure to the tugs towing and positioning the jack-up rig. Based on the nature of the activity, Level A harassment is neither anticipated nor authorized.</P>
                <P>As described previously, no serious injury or mortality is anticipated or authorized for this activity. Below we describe how the authorized take numbers are estimated.</P>
                <P>
                    For acoustic impacts, generally speaking, we estimate take by considering: (1) acoustic thresholds above which NMFS believes the best available science indicates marine mammals will be behaviorally harassed or incur some degree of permanent hearing impairment; (2) the area or volume of water that will be ensonified above these levels in a day; (3) the density or occurrence of marine mammals within these ensonified areas; and, (4) the number of days of activities. We note that while these factors can contribute to a basic calculation to provide an initial prediction of potential takes, additional information that can qualitatively inform take estimates is also sometimes available (
                    <E T="03">e.g.,</E>
                     previous monitoring results or average group size). Below, we describe the factors considered here in more detail and present the take estimates.
                </P>
                <HD SOURCE="HD2">Acoustic Thresholds</HD>
                <P>NMFS recommends the use of acoustic thresholds that identify the received level of underwater sound above which exposed marine mammals would be reasonably expected to be behaviorally harassed (equated to Level B harassment) or to incur permanent threshold shift (PTS) of some degree (equated to Level A harassment).</P>
                <P>
                    <E T="03">Level B Harassment</E>
                    —Though significantly driven by received level, the onset of behavioral disturbance or harassment from anthropogenic noise exposure is also informed to varying degrees by other factors related to the source or exposure context (
                    <E T="03">e.g.,</E>
                     frequency, predictability, duty cycle, duration of the exposure, signal-to-noise ratio, distance to the source), the environment (
                    <E T="03">e.g.,</E>
                     bathymetry, other noises in the area, predators in the area), and the receiving animals (hearing, motivation, experience, demography, life stage, depth) and can be difficult to predict (
                    <E T="03">e.g.,</E>
                     Southall 
                    <E T="03">et al.,</E>
                     2007, 2021, Ellison 
                    <E T="03">et al.,</E>
                     2012). Accordingly, based on what the available science indicates and the practical need to use a threshold based on a metric that is both predictable and measurable for most activities, NMFS typically uses a generalized acoustic threshold based on received level to reasonably estimate the onset of behavioral harassment. NMFS generally predicts that marine mammals are likely to be behaviorally affected in a manner considered to be Level B harassment when exposed to underwater anthropogenic noise above root-mean-squared pressure received levels (RMS SPL) of 120 dB (referenced to 1 micropascal (re 1 μPa)) for continuous (
                    <E T="03">e.g.,</E>
                     vibratory pile-driving, drilling) and above RMS SPL, 160 dB re 1 μPa (rms) for non-explosive impulsive (
                    <E T="03">e.g.,</E>
                     seismic airguns) or intermittent (
                    <E T="03">e.g.,</E>
                     scientific sonar) sources.
                </P>
                <P>Hilcorp's activity includes the use of continuous (tug towing and positioning the rig) sources, and therefore the RMS SPL 120 dB re 1 μPa is applicable.</P>
                <P>
                    <E T="03">Level A harassment for non-explosive sources</E>
                    —NMFS' Technical Guidance for Assessing the Effects of Anthropogenic Sound on Marine 
                    <PRTPAGE P="62382"/>
                    Mammal Hearing (Version 2.0) (Technical Guidance, 2018) identifies dual criteria to assess auditory injury (Level A harassment) to five different marine mammal groups (based on hearing sensitivity) as a result of exposure to noise from two different types of sources (impulsive or non-impulsive). Hilcorp's activity includes the use of non-impulsive (tugs towing rig) sources.
                </P>
                <P>
                    These thresholds are provided in the table below. The references, analysis, and methodology used in the development of the thresholds are described in NMFS 2018 Technical Guidance, which may be accessed at 
                    <E T="03">https://www.fisheries.noaa.gov/national/marine-mammal-protection/marine-mammal-acoustic-technical-guidance.</E>
                </P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s50,r50p,xs100">
                    <TTITLE>Table 6—Thresholds Identifying the Onset of Permanent Threshold Shift</TTITLE>
                    <BOXHD>
                        <CHED H="1">Hearing group</CHED>
                        <CHED H="1">
                            PTS onset acoustic thresholds *
                            <LI>(received level)</LI>
                        </CHED>
                        <CHED H="2">Impulsive</CHED>
                        <CHED H="2">Non-impulsive</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Low-Frequency (LF) Cetaceans</ENT>
                        <ENT>
                            <E T="03">Cell 1: L</E>
                            <E T="0732">pk,flat</E>
                            : 219 dB; 
                            <E T="03">L</E>
                            <E T="0732">E,LF,24h</E>
                            : 183 dB
                        </ENT>
                        <ENT>
                            <E T="03">Cell 2: L</E>
                            <E T="0732">E,LF,24h</E>
                            : 199 dB.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mid-Frequency (MF) Cetaceans</ENT>
                        <ENT>
                            <E T="03">Cell 3: L</E>
                            <E T="0732">pk,flat</E>
                            : 230 dB; 
                            <E T="03">L</E>
                            <E T="0732">E,MF,24h</E>
                            : 185 dB
                        </ENT>
                        <ENT>
                            <E T="03">Cell 4: L</E>
                            <E T="0732">E,MF,24h</E>
                            : 198 dB.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">High-Frequency (HF) Cetaceans</ENT>
                        <ENT>
                            <E T="03">Cell 5: L</E>
                            <E T="0732">pk,flat</E>
                            : 202 dB; 
                            <E T="03">L</E>
                            <E T="0732">E,HF,24h</E>
                            : 155 dB
                        </ENT>
                        <ENT>
                            <E T="03">Cell 6: L</E>
                            <E T="0732">E,HF,24h</E>
                            : 173 dB.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Phocid Pinnipeds (PW)(Underwater)</ENT>
                        <ENT>
                            <E T="03">Cell 7: L</E>
                            <E T="0732">pk,flat</E>
                            : 218 dB; 
                            <E T="03">L</E>
                            <E T="0732">E,PW,24h</E>
                            : 185 dB
                        </ENT>
                        <ENT>
                            <E T="03">Cell 8: L</E>
                            <E T="0732">E,PW,24h</E>
                            : 201 dB.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Otariid Pinnipeds (OW)(Underwater)</ENT>
                        <ENT>
                            <E T="03">Cell 9: L</E>
                            <E T="0732">pk,flat</E>
                            : 232 dB; 
                            <E T="03">L</E>
                            <E T="0732">E,OW,24h</E>
                            : 203 dB
                        </ENT>
                        <ENT>
                            <E T="03">Cell 10: L</E>
                            <E T="0732">E,OW,24h</E>
                            : 219 dB.
                        </ENT>
                    </ROW>
                    <TNOTE>* Dual metric acoustic thresholds for impulsive sounds: Use whichever results in the largest isopleth for calculating PTS onset. If a non-impulsive sound has the potential of exceeding the peak sound pressure level thresholds associated with impulsive sounds, these thresholds should also be considered.</TNOTE>
                    <TNOTE>
                        <E T="02">Note:</E>
                         Peak sound pressure (
                        <E T="03">L</E>
                        <E T="0732">pk</E>
                        ) has a reference value of 1 μPa, and cumulative sound exposure level (
                        <E T="03">L</E>
                        <E T="0732">E</E>
                        ) has a reference value of 1μPa
                        <SU>2</SU>
                        s. In this Table, thresholds are abbreviated to reflect American National Standards Institute standards (ANSI, 2013). However, peak sound pressure is defined by ANSI as incorporating frequency weighting, which is not the intent for this Technical Guidance. Hence, the subscript “flat” is being included to indicate peak sound pressure should be flat weighted or unweighted within the generalized hearing range. The subscript associated with cumulative sound exposure level thresholds indicates the designated marine mammal auditory weighting function (LF, MF, and HF cetaceans, and PW and OW pinnipeds) and that the recommended accumulation period is 24 hours. The cumulative sound exposure level thresholds could be exceeded in a multitude of ways (
                        <E T="03">i.e.,</E>
                         varying exposure levels and durations, duty cycle). When possible, it is valuable for action proponents to indicate the conditions under which these acoustic thresholds will be exceeded.
                    </TNOTE>
                </GPOTABLE>
                <HD SOURCE="HD2">Ensonified Area</HD>
                <P>Here, we describe operational and environmental parameters of the activity that will feed into identifying the area ensonified above the acoustic thresholds, which include source levels and transmission loss coefficient.</P>
                <P>As described above in the Detailed Description of Specific Activity, based on in situ measurements of Hilcorp's tug and a review of the available literature of tugs under load, a source level of 185 dB re 1 μPa was used for Hilcorp's three tug configuration for towing the jack-up-rig. Hilcorp contracted SLR Consulting to model the extent of the Level B harassment isopleth as well as the extent of the PTS isopleth for their activity.</P>
                <P>
                    Rather than applying practical spreading loss, SLR created a more detailed propagation loss model in an effort to improve the accuracy of the results by considering the influence of environmental variables (
                    <E T="03">e.g.</E>
                     bathymetry) at the specific well sites, as Hilcorp's operational locations are known in advance. Modeling was conducted using dBSea software. The fluid parabolic equation modeling algorithm was used with 5 Padé terms (see pg. 57 in Hilcorp's application for more detail) to calculate the transmission loss between the source and the receiver at low frequencies (
                    <FR>1/3</FR>
                    -octave bands, 31.5 Hz up to 1 kHz). For higher frequencies (1 kHz up to 8 kHz) the ray tracing model was used with 1,000 reflections for each ray. Sound sources were assumed to be omnidirectional and modeled as points. The received sound levels for the project were calculated as follows: (1) One-third octave source spectral levels were obtained via reference spectral curves with subsequent corrections based on their corresponding overall source levels; (2) Transmission loss was modeled at one-third octave band central frequencies along 100 radial paths at regular increments around each source location, out to the maximum range of the bathymetry data set or until constrained by land; (3) The bathymetry variation of the vertical plane along each modeling path was obtained via interpolation of the bathymetry dataset which has 83 m grid resolution; (4) The one-third octave source levels and transmission loss were combined to obtain the received levels as a function of range, depth, and frequency; and (5) The overall received levels were calculated at a 1-m depth resolution along each propagation path by summing all frequency band spectral levels.
                </P>
                <P>
                    <E T="03">Model Inputs</E>
                    —Bathymetry data used in the model was collected from the NOAA National Centers for Environmental Information (AFSC, 2019). Using NOAA's temperature and salinity data, sound speed profiles were computed for depths from 0 to 100 meters for May, July, and October to capture the range of possible sound speed depending on the time of year Hilcorp's work could be conducted. These sound speed profiles were compiled using the Mackenzie Equation (1981) and are presented in Table 8 of Hilcorp's application. Geoacoustic parameters were also incorporated into the model. The parameters were based on substrate type and their relation to depth. These parameters are presented in Table 9 of Hilcorp's application.
                </P>
                <P>Detailed broadband sound transmission loss modeling in dBSea used the source level of 185 dB re 1 μPa at 1 m calculated in one-third octave band levels (31.5 Hz to 64,000 Hz) for frequency dependent solutions. The frequencies associated with tug sound sources occur within the hearing range of marine mammals in Cook Inlet. Received levels for each hearing marine mammal group based on one-third octave auditory weighting functions were also calculated and integrated into the modeling scenarios of dBSea. For modeling the distances to relevant PTS thresholds, a weighting factor adjustment was not used; instead, the data on the spectrum associated with their source was used and incorporated the full auditory weighting function for each marine mammal hearing group.</P>
                <P>
                    Because Hilcorp plans to use the tugs towing the jack-up-rig for essentially two functions (positioning and towing), the activity was divided into two parts (stationary and mobile) and two approaches were taken for modeling the relevant isopleths.
                    <PRTPAGE P="62383"/>
                </P>
                <P>
                    <E T="03">Stationary</E>
                    —For stationary activity, two locations representative of where tugs will be stationary positioning the jack-up rig were selected for the model. These locations are in middle Cook Inlet near the Tyonek platform, and in lower Trading Bay where the production platforms are located, with water depths of 40 m and 20 m respectively. The modeling at these locations assumed a stationary 5-hour exposure to a broadband spectrum of 185 dB as described above. A 5-hour exposure duration was chosen to account for the up to 5-hour positioning attempts on individual days as well as events where the tugs need to hold the jack-up rig while waiting for a following tide. Stationary model results are presented in Table 7.
                </P>
                <P>
                    <E T="03">Mobile</E>
                    —For the mobile portion of the activity, a representative route was used from the Rig Tender's dock in Nikiski to the Tyonek platform, the northernmost platform in Cook Inlet (representing Middle Cook Inlet), as well as from the Tyonek Platform to the Dolly Varden platform in lower Trading Bay and then from the Dolly Varden platform back to the Rig Tender's Dock in Nikiski. This route is representative of a typical route the tugs may take; the specific route is not yet known because the order in which platforms will be drilled with the jack-up rig is not yet known. The lowest threshold for the onset of PTS is for high frequency cetaceans at 173 dB. Based on a source level of 185 dB, and assuming practical spreading, the high frequency cetacean PTS threshold of 173 dB would be reached at 6.3 meters away from the source. The mobile source modeling assumed a transit speed of 2.06 m/s for the tug configuration. With an assumed vessel speed of 2.06 m/s, it would take the vessel 6.11 seconds to traverse a distance of two times the radius, with two times the radius used because the source is omnidirectional and the ship is moving in a straight line. Although a source level of 185 dB incorporates the use of three tugs simultaneously, because the three tugs will likely not be perfectly aligned in space (
                    <E T="03">e.g.,</E>
                     one could lag slightly behind the forward two), three separate six second exposures were summed (one for each tug passing in space) to arrive at a total duration of exposure of 18 seconds. While it is possible the duration of exposure could be as short as six seconds if all tugs were perfectly aligned, separate exposures for each tug were considered as the exact formation of the tugging vessels at any given time is unknown. Mobile source model results are presented in Table 8.
                </P>
                <P>Because there is no temporal component associated with NMFS' current Level B threshold, making it a potentially conservative assumption given the transitory nature of the rig towing activity, the results of the modeled distance to the 120 dB threshold for both stationary and mobile tug use are presented in Table 9 below. The average of these distances was used for calculation of estimated exposure to Level B harassment (3,850 m).</P>
                <P>The locations used in the stationary and mobile source models are depicted in Figure 2 below.</P>
                <BILCOD>BILLING CODE 3510-22-P</BILCOD>
                <GPH SPAN="3" DEEP="623">
                    <PRTPAGE P="62384"/>
                    <GID>EN14OC22.070</GID>
                </GPH>
                <BILCOD>BILLING CODE 3510-22-C</BILCOD>
                <P>
                    The outputs of the mobile and stationary models as distances to the relevant threshold (in meters) are presented below in Tables 7-9.
                    <PRTPAGE P="62385"/>
                </P>
                <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="s50,r50,12,12,12,12,12">
                    <TTITLE>Table 7—Average Distances to PTS Thresholds for Stationary Activity</TTITLE>
                    <BOXHD>
                        <CHED H="1">Location</CHED>
                        <CHED H="1">Season</CHED>
                        <CHED H="1">Average distances (m) to PTS threshold by functional hearing group</CHED>
                        <CHED H="2">LF</CHED>
                        <CHED H="2">MF</CHED>
                        <CHED H="2">HF</CHED>
                        <CHED H="2">PW</CHED>
                        <CHED H="2">OW</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Trading Bay</ENT>
                        <ENT>May</ENT>
                        <ENT>100</ENT>
                        <ENT>72</ENT>
                        <ENT>716</ENT>
                        <ENT>59</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Trading Bay</ENT>
                        <ENT>July</ENT>
                        <ENT>122</ENT>
                        <ENT>73</ENT>
                        <ENT>697</ENT>
                        <ENT>63</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Trading Bay</ENT>
                        <ENT>October</ENT>
                        <ENT>98</ENT>
                        <ENT>72</ENT>
                        <ENT>694</ENT>
                        <ENT>59</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Middle Cook Inlet</ENT>
                        <ENT>May</ENT>
                        <ENT>83</ENT>
                        <ENT>83</ENT>
                        <ENT>643</ENT>
                        <ENT>77</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Middle Cook Inlet</ENT>
                        <ENT>July</ENT>
                        <ENT>89</ENT>
                        <ENT>85</ENT>
                        <ENT>664</ENT>
                        <ENT>78</ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">Middle Cook Inlet</ENT>
                        <ENT>October</ENT>
                        <ENT>80</ENT>
                        <ENT>84</ENT>
                        <ENT>661</ENT>
                        <ENT>78</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Average</ENT>
                        <ENT/>
                        <ENT>95</ENT>
                        <ENT>78</ENT>
                        <ENT>679</ENT>
                        <ENT>69</ENT>
                        <ENT>0</ENT>
                    </ROW>
                </GPOTABLE>
                <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="s50,r50,12,12,12,12,12">
                    <TTITLE>Table 8—Average Distances to PTS Thresholds for Mobile Activity</TTITLE>
                    <BOXHD>
                        <CHED H="1">Location</CHED>
                        <CHED H="1">Season</CHED>
                        <CHED H="1">Average distances (m) to PTS threshold by functional hearing group</CHED>
                        <CHED H="2">LF</CHED>
                        <CHED H="2">MF</CHED>
                        <CHED H="2">HF</CHED>
                        <CHED H="2">PW</CHED>
                        <CHED H="2">OW</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">M2</ENT>
                        <ENT>May</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>10</ENT>
                        <ENT/>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">M2</ENT>
                        <ENT>July</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>5</ENT>
                        <ENT/>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">M2</ENT>
                        <ENT>October</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>10</ENT>
                        <ENT/>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">M11</ENT>
                        <ENT>May</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>10</ENT>
                        <ENT/>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">M11</ENT>
                        <ENT>July</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>5</ENT>
                        <ENT/>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">M11</ENT>
                        <ENT>October</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>10</ENT>
                        <ENT/>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">M22</ENT>
                        <ENT>May</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>10</ENT>
                        <ENT/>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">M22</ENT>
                        <ENT>July</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>5</ENT>
                        <ENT/>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">M22</ENT>
                        <ENT>October</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>10</ENT>
                        <ENT/>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Average</ENT>
                        <ENT/>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>8</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                </GPOTABLE>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,12,12,12,12">
                    <TTITLE>Table 9—Average Distances to Level B Threshold </TTITLE>
                    <TDESC>[stationary and mobile] </TDESC>
                    <TDESC>[120 dB]</TDESC>
                    <BOXHD>
                        <CHED H="1">Waypoint</CHED>
                        <CHED H="1">
                            Average distance to 120 dB threshold
                            <LI>(m)</LI>
                        </CHED>
                        <CHED H="2">May</CHED>
                        <CHED H="2">July</CHED>
                        <CHED H="2">October</CHED>
                        <CHED H="1">
                            Season
                            <LI>average</LI>
                            <LI>distance to threshold</LI>
                            <LI>(m)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">M1</ENT>
                        <ENT>4,215</ENT>
                        <ENT>3,911</ENT>
                        <ENT>4,352</ENT>
                        <ENT>4,159</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M2</ENT>
                        <ENT>3,946</ENT>
                        <ENT>3,841</ENT>
                        <ENT>4,350</ENT>
                        <ENT>4,046</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M3</ENT>
                        <ENT>4,156</ENT>
                        <ENT>3,971</ENT>
                        <ENT>4,458</ENT>
                        <ENT>4,195</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M4</ENT>
                        <ENT>4,040</ENT>
                        <ENT>3,844</ENT>
                        <ENT>4,364</ENT>
                        <ENT>4,083</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M5</ENT>
                        <ENT>4,053</ENT>
                        <ENT>3,676</ENT>
                        <ENT>4,304</ENT>
                        <ENT>4,011</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M6</ENT>
                        <ENT>3,716</ENT>
                        <ENT>3,445</ENT>
                        <ENT>3,554</ENT>
                        <ENT>3,572</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M7</ENT>
                        <ENT>2,947</ENT>
                        <ENT>2,753</ENT>
                        <ENT>2,898</ENT>
                        <ENT>2,866</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M8</ENT>
                        <ENT>3,270</ENT>
                        <ENT>3,008</ENT>
                        <ENT>3,247</ENT>
                        <ENT>3,175</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M9</ENT>
                        <ENT>3,567</ENT>
                        <ENT>3,359</ENT>
                        <ENT>3,727</ENT>
                        <ENT>3,551</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M10</ENT>
                        <ENT>3,600</ENT>
                        <ENT>3,487</ENT>
                        <ENT>3,691</ENT>
                        <ENT>3,593</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M11</ENT>
                        <ENT>3,746</ENT>
                        <ENT>3,579</ENT>
                        <ENT>4,214</ENT>
                        <ENT>3,846</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M12</ENT>
                        <ENT>3,815</ENT>
                        <ENT>3,600</ENT>
                        <ENT>3,995</ENT>
                        <ENT>3,803</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M13</ENT>
                        <ENT>4,010</ENT>
                        <ENT>3,831</ENT>
                        <ENT>4,338</ENT>
                        <ENT>4,060</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M14</ENT>
                        <ENT>3,837</ENT>
                        <ENT>3,647</ENT>
                        <ENT>4,217</ENT>
                        <ENT>3,900</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M15</ENT>
                        <ENT>3,966</ENT>
                        <ENT>3,798</ENT>
                        <ENT>4,455</ENT>
                        <ENT>4,073</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M16</ENT>
                        <ENT>3,873</ENT>
                        <ENT>3,676</ENT>
                        <ENT>4,504</ENT>
                        <ENT>4,018</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M18</ENT>
                        <ENT>5,562</ENT>
                        <ENT>3,893</ENT>
                        <ENT>4,626</ENT>
                        <ENT>4,694</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M20</ENT>
                        <ENT>5,044</ENT>
                        <ENT>3,692</ENT>
                        <ENT>4,320</ENT>
                        <ENT>4,352</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M22</ENT>
                        <ENT>4,717</ENT>
                        <ENT>3,553</ENT>
                        <ENT>4,067</ENT>
                        <ENT>4,112</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M24</ENT>
                        <ENT>4,456</ENT>
                        <ENT>3,384</ENT>
                        <ENT>4,182</ENT>
                        <ENT>4,007</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M25</ENT>
                        <ENT>3,842</ENT>
                        <ENT>3,686</ENT>
                        <ENT>4,218</ENT>
                        <ENT>3,915</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M26</ENT>
                        <ENT>3,690</ENT>
                        <ENT>3,400</ENT>
                        <ENT>3,801</ENT>
                        <ENT>3,630</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M27</ENT>
                        <ENT>3,707</ENT>
                        <ENT>3,497</ENT>
                        <ENT>3,711</ENT>
                        <ENT>3,638</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M28</ENT>
                        <ENT>3,546</ENT>
                        <ENT>3,271</ENT>
                        <ENT>3,480</ENT>
                        <ENT>3,432</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M29</ENT>
                        <ENT>3,618</ENT>
                        <ENT>3,279</ENT>
                        <ENT>3,646</ENT>
                        <ENT>3,514</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Average</ENT>
                        <ENT>3,958</ENT>
                        <ENT>3,563</ENT>
                        <ENT>4,029</ENT>
                        <ENT>3,850</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="62386"/>
                <HD SOURCE="HD2">Marine Mammal Occurrence</HD>
                <P>In this section we provide the information about the presence, density, or group dynamics of marine mammals that will inform the take calculations.</P>
                <P>
                    Densities for marine mammals in Cook Inlet were derived from NMFS' Marine Mammal Laboratory (MML) aerial surveys, typically flown in June, from 2000 to 2018 (Rugh 
                    <E T="03">et al.,</E>
                     2005; Shelden 
                    <E T="03">et al.,</E>
                     2013, 2015, 2017, 2019). A survey was also conducted in 2021 but density information is not yet available. While the surveys are concentrated for a few days in June annually, which may skew densities for seasonally present species, they are still the best available long-term dataset of marine mammal sightings available in Cook Inlet. Density was calculated by summing the total number of animals observed and dividing the number sighted by the area surveyed. The total number of animals observed accounts for both lower and upper Cook Inlet. There are no density estimates available for California sea lions and Pacific white-sided dolphins in Cook Inlet, as they are so infrequently sighted. Densities are presented in Table 10 below.
                </P>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s150,12">
                    <TTITLE>Table 10—Densities of Marine Mammals in Cook Inlet</TTITLE>
                    <BOXHD>
                        <CHED H="1">Species</CHED>
                        <CHED H="1">
                            Density
                            <LI>
                                (indiv/km
                                <SU>2</SU>
                                )
                            </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Humpback whale</ENT>
                        <ENT>0.001770</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Minke whale</ENT>
                        <ENT>0.000009</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Gray whale</ENT>
                        <ENT>0.000075</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fin whale</ENT>
                        <ENT>0.000311</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Killer whale</ENT>
                        <ENT>0.000601</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Beluga whale (MML lower CI)</ENT>
                        <ENT>0.000023</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Beluga whale (MML middle CI)</ENT>
                        <ENT>0.001110</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Goetz beluga—LCI</ENT>
                        <ENT>0.011106</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Goetz beluga—NCI</ENT>
                        <ENT>0.001664</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Goetz beluga—TB</ENT>
                        <ENT>0.015053</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dall's porpoise</ENT>
                        <ENT>0.000154</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Harbor porpoise</ENT>
                        <ENT>0.004386</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pacific white-sided dolphin</ENT>
                        <ENT>0.000000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Harbor seal</ENT>
                        <ENT>0.241401</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Steller sea lion</ENT>
                        <ENT>0.007609</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">California sea lion</ENT>
                        <ENT>0.000000</ENT>
                    </ROW>
                </GPOTABLE>
                <P>For beluga whales, two densities were considered as a comparison of available data. The first source considered was directly from the MML aerial surveys, as described above. Sighting data collected during aerial surveys is collected and then several correction factors are applied to address perception, availability, and proximity bias. These corrected sightings totals are then divided by the total area covered during the survey to arrive at a density value. Densities were derived for the entirety of Cook Inlet as well as for middle and lower Cook Inlet. Densities across all three regions are low and there is a known effect of seasonality on the distribution of the whales. Thus, densities derived directly from surveys flown in June might underestimate the density of beluga whales in lower Cook Inlet at other ice-free times of the year.</P>
                <P>
                    The other mechanism for arriving at beluga whale density considered here is the Goetz 
                    <E T="03">et al.</E>
                     (2012) habitat-based model. This model is derived from sightings and incorporates depth soundings, coastal substrate type, environmental sensitivity index, anthropogenic disturbance, and anadromous fish streams to predict densities throughout Cook Inlet. The output of this model is a beluga density map of Cook Inlet, which predicts spatially explicit density estimates for Cook Inlet belugas. Using the resulting grid densities, average densities were calculated for two regions applicable to Hilcorp's operations. The densities applicable to the area of activity (
                    <E T="03">i.e.,</E>
                     the North Cook Inlet Unit density for middle Cook Inlet activities and the Trading Bay density for activities in Trading Bay) are provided in Table 11 below and were carried forward to the exposure estimates. Likewise, when a range is given, the higher end of the range was used out of caution to calculate exposure estimates (
                    <E T="03">i.e.,</E>
                     Trading Bay in the Goetz model has a range of 0.004453 to 0.015053; 0.015053 was used for the exposure estimates).
                </P>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s150,20">
                    <TTITLE>
                        Table 11—Cook Inlet Beluga Whale Densities Based on Goetz 
                        <E T="03">et al.</E>
                         (2012) Habitat Model
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">Project Location</CHED>
                        <CHED H="1">
                            Beluga whale density
                            <LI>
                                (ind/km
                                <SU>2</SU>
                                )
                            </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">North Cook Inlet Unit (middle Cook Inlet)</ENT>
                        <ENT>0.001664</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Trading Bay Area</ENT>
                        <ENT>0.004453-0.015053</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD2">Take Calculation and Estimation</HD>
                <P>Here we describe how the information provided above is brought together to produce a quantitative take estimate for each of the two IHAs.</P>
                <P>
                    <E T="03">Year 1 IHA</E>
                    —As described above, Hilcorp's tug towing rig activity was divided into two portions for the purpose of take estimation: stationary and mobile activity. For stationary activity, 5 hours of sound production per day was assumed for up to 14 days (seven moves or segments consisting of 2 days each). For the mobile portion of the activity, 1 day of 9 hours of mobile activity (assuming a source velocity of 2.06 m/s) and 6 days of 6 hours of mobile activity were assumed, for a total of 7 rig moves. The first 5 stationary hours are assumed to occur on the same day as the mobile hours, the second 5 stationary hours will occur the following day. The first 5 stationary 
                    <PRTPAGE P="62387"/>
                    hours are assumed to occur on the same day as the mobile hours, the second 5 stationary hours will occur the following day.
                </P>
                <P>
                    <E T="03">Year 2 IHA</E>
                    —For stationary activity, 5 hours of sound production per day was assumed for up to 16 days. For mobile activity, 9 hours of sound production was assumed for 2 days, as well as 6 hours of sound production for 6 days, for a total of eight rig moves.
                </P>
                <P>
                    The ensonified areas calculated per activity type (stationary and mobile) for a single day were multiplied by marine mammal densities to get an estimate of exposures per day. This was then multiplied by the number of days of that type of activity (stationary or mobile) to arrive at the number of estimated exposures per year per activity type. These exposures by activity type were then summed to result in a number of exposures per year for all tug towing rig activity. The estimated exposures are provided below in Tables 12 and 13 for Year 1 and Year 2 of activity, respectively. As we are now considering one less rig mobilization in Year 1 than was considered in the notice of proposed IHAs, the calculated exposures for Year 1 are slightly lower than those of Year 2. There are two estimates for beluga whales provided in the tables below to demonstrate the difference in the calculations based on the chosen density value. As exposure estimates were calculated based on specific potential rig moves or well locations, the density value for beluga whales that was carried through the estimate was the higher density value for that particular location. There are no estimated exposures based on this method of calculation for Pacific white-sided dolphins and California sea lions because the assumed density is 0 animals/km
                    <SU>2</SU>
                    .
                </P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,r50,12,12">
                    <TTITLE>Table 12—Total Calculated Exposures for Year 1</TTITLE>
                    <BOXHD>
                        <CHED H="1">Group</CHED>
                        <CHED H="1">Species</CHED>
                        <CHED H="1">Level A</CHED>
                        <CHED H="1">Level B</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">LF Cetaceans</ENT>
                        <ENT>Humpback whale</ENT>
                        <ENT>0.000</ENT>
                        <ENT>3.065</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Minke whale</ENT>
                        <ENT>0.000</ENT>
                        <ENT>0.016</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Gray whale</ENT>
                        <ENT>0.000</ENT>
                        <ENT>0.129</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Fin whale</ENT>
                        <ENT>0.000</ENT>
                        <ENT>0.538</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MF Cetaceans</ENT>
                        <ENT>Killer whale</ENT>
                        <ENT>0.000</ENT>
                        <ENT>1.041</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Beluga whale NMFS</ENT>
                        <ENT>0.000</ENT>
                        <ENT>1.922</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Beluga whale Goetz</ENT>
                        <ENT>0.000</ENT>
                        <ENT>9.411</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Pacific white-sided dolphin</ENT>
                        <ENT>0.000</ENT>
                        <ENT>0.000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HF Cetaceans</ENT>
                        <ENT>Dall's porpoise</ENT>
                        <ENT>0.001</ENT>
                        <ENT>0.266</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Harbor porpoise</ENT>
                        <ENT>0.031</ENT>
                        <ENT>7.595</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Phocids</ENT>
                        <ENT>Harbor seal</ENT>
                        <ENT>0.011</ENT>
                        <ENT>418.051</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Otariids</ENT>
                        <ENT>Steller sea lion</ENT>
                        <ENT>0.000</ENT>
                        <ENT>13.176</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>California sea lion</ENT>
                        <ENT>0.000</ENT>
                        <ENT>0.000</ENT>
                    </ROW>
                </GPOTABLE>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,r50,12,12">
                    <TTITLE>Table 13—Total Calculated Exposures for Year 2</TTITLE>
                    <BOXHD>
                        <CHED H="1">Group</CHED>
                        <CHED H="1">Species</CHED>
                        <CHED H="1">Level A</CHED>
                        <CHED H="1">Level B</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">LF Cetaceans</ENT>
                        <ENT>Humpback whale</ENT>
                        <ENT>0.000</ENT>
                        <ENT>4.058</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Minke whale</ENT>
                        <ENT>0.000</ENT>
                        <ENT>0.021</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Gray whale</ENT>
                        <ENT>0.000</ENT>
                        <ENT>0.171</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Fin whale</ENT>
                        <ENT>0.000</ENT>
                        <ENT>0.712</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MF Cetaceans</ENT>
                        <ENT>Killer whale</ENT>
                        <ENT>0.000</ENT>
                        <ENT>1.379</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Beluga whale NMFS</ENT>
                        <ENT>0.000</ENT>
                        <ENT>2.545</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Beluga whale Goetz</ENT>
                        <ENT>0.000</ENT>
                        <ENT>11.651</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Pacific white-sided dolphin</ENT>
                        <ENT>0.000</ENT>
                        <ENT>0.000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HF Cetaceans</ENT>
                        <ENT>Dall's porpoise</ENT>
                        <ENT>0.001</ENT>
                        <ENT>0.353</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Harbor porpoise</ENT>
                        <ENT>0.038</ENT>
                        <ENT>10.057</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Phocids</ENT>
                        <ENT>Harbor seal</ENT>
                        <ENT>0.012</ENT>
                        <ENT>553.565</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Otariids</ENT>
                        <ENT>Steller sea lion</ENT>
                        <ENT>0.000</ENT>
                        <ENT>17.448</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>California sea lion</ENT>
                        <ENT>0.000</ENT>
                        <ENT>0.000</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Based on the analysis described above, NMFS has not authorized take via Level A harassment related to Hilcorp's tug towing drill rig activity. For mobile tugging, the distances to the PTS thresholds for high frequency cetaceans (the only functional hearing group of concern based on the model results) are smaller than the overall size of the tug and rig configuration, making it unlikely a cetacean would remain close enough to the tug engines to incur PTS. For stationary positioning of the jack up rig, the PTS isopleths are up to 679 m for high frequency cetaceans, but calculated on the assumption that an animal would remain within several hundred meters of the jack-up rig for the full 5 hours of noise-producing activity. Given the location of the activity is not in an area known to be essential habitat for any marine mammal species with extreme site fidelity over the course of 2 days, the occurrence of PTS is unlikely. A table indicating the number of takes, by Level B harassment, authorized is provided below.</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,xs60,15,xs60,15">
                    <TTITLE>Table 14—Takes (by Level B Harassment) Calculated and Authorized for Year 1 IHA and Year 2 IHA</TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">
                            Year 1
                            <LI>calculated</LI>
                        </CHED>
                        <CHED H="1">
                            Year 1
                            <LI>authorized</LI>
                        </CHED>
                        <CHED H="1">
                            Year 2
                            <LI>calculated</LI>
                        </CHED>
                        <CHED H="1">
                            Year 2
                            <LI>authorized</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Humpback whale</ENT>
                        <ENT>3.065</ENT>
                        <ENT>5</ENT>
                        <ENT>4.058</ENT>
                        <ENT>6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Minke whale</ENT>
                        <ENT>0.016</ENT>
                        <ENT>6</ENT>
                        <ENT>0.021</ENT>
                        <ENT>6</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="62388"/>
                        <ENT I="01">Gray whale</ENT>
                        <ENT>0.129</ENT>
                        <ENT>2</ENT>
                        <ENT>0.171</ENT>
                        <ENT>2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fin whale</ENT>
                        <ENT>0.538</ENT>
                        <ENT>4</ENT>
                        <ENT>0.712</ENT>
                        <ENT>4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Killer whale</ENT>
                        <ENT>1.041</ENT>
                        <ENT>10</ENT>
                        <ENT>1.379</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Beluga whale</ENT>
                        <ENT>1.922 (MML), 9.411 (Goetz)</ENT>
                        <ENT>11</ENT>
                        <ENT>2.545 (MML), 11.651 (Goetz)</ENT>
                        <ENT>22</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pacific white-sided dolphin</ENT>
                        <ENT>0</ENT>
                        <ENT>3</ENT>
                        <ENT>0</ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dall's porpoise</ENT>
                        <ENT>0.266</ENT>
                        <ENT>6</ENT>
                        <ENT>0.353</ENT>
                        <ENT>6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Harbor porpoise</ENT>
                        <ENT>7.595</ENT>
                        <ENT>44</ENT>
                        <ENT>10.057</ENT>
                        <ENT>44</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Harbor seal</ENT>
                        <ENT>418.051</ENT>
                        <ENT>418</ENT>
                        <ENT>553.565</ENT>
                        <ENT>554</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Steller sea lion</ENT>
                        <ENT>13.176</ENT>
                        <ENT>13</ENT>
                        <ENT>17.448</ENT>
                        <ENT>17</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">California sea lion</ENT>
                        <ENT>0</ENT>
                        <ENT>2</ENT>
                        <ENT>0</ENT>
                        <ENT>2</ENT>
                    </ROW>
                </GPOTABLE>
                <P>As illustrated by the table above, the estimated exposures for several species are less than one. While uncommon, these species have been previously sighted in Cook Inlet and some are unlikely to appear as solitary individuals when sighted.</P>
                <P>
                    For humpback whales, the number of takes authorized is increased from the calculated estimate of four to six individuals. There were two sightings of three humpback whales observed near Ladd Landing north of the Forelands during the Harvest Alaska CIPL project (Sitkiewicz 
                    <E T="03">et al.,</E>
                     2018). Based on documented observations during the CIPL survey (the survey nearest the Action Area), Hilcorp requested six takes of humpback whales to allow for up to two sightings of three individuals, consistent with what was observed during the CIPL project. We expect a small number of humpback whale groups will be exposed, with most of these groups consisting of one or two animals. There is a small probability more humpbacks are exposed than the calculated, three humpbacks in Year 1 and four in Year 2, therefore, we added an additional median group size of two humpback whales to each year resulting in an exposure estimate of five humpbacks in Year 1 and six in Year 2.
                </P>
                <P>Minke whale takes authorized are increased from the calculated less than one individual to five. Minke whales are commonly sighted in groups of two or three, as well as sightings of individuals. There were eight sightings of eight minke whales observed during the 2019 Hilcorp lower Cook Inlet seismic survey (Fairweather Science, 2020). As the occurrence of minke whales is expected to be less in middle Cook Inlet than lower Cook Inlet and considering the observed group sizes, Hilcorp is requesting six takes of minke whale to allow for the possibility of two sightings of a group of three individuals, both in Year 1 and again in Year 2.</P>
                <P>
                    During Apache's 2012 seismic program, nine gray whales were observed in June and July (Lomac-MacNair 
                    <E T="03">et al.,</E>
                     2013). During Apache's seismic program in 2014, one gray whale was observed (Lomac-MacNair 
                    <E T="03">et al.,</E>
                     2014). During SAExploration's seismic survey in 2015, the 2018 CIPL project, and Hilcorp's 2019 seismic survey, no gray whales were observed (Kendall 
                    <E T="03">et al.,</E>
                     2015; Sitkiewicz 
                    <E T="03">et al.,</E>
                     2018; Fairweather Science, 2020). Considering the Action Area is in middle Cook Inlet where sightings of gray whales are less common, Hilcorp is requesting two takes of gray whales to allow for the potential occurrence of two individual gray whales both in Year 1 and again in Year 2.
                </P>
                <P>
                    The number of fin whale takes authorized is increased from one to four individuals, as they may be seen in groups of two to seven individuals. During seismic surveys conducted in 2019 by Hilcorp in the lower Cook Inlet, fin whales were recorded in groups ranging in size from one to 15 individuals (Fairweather, 2020). During the NMFS aerial surveys in Cook Inlet from 2000 to 2018, 10 sightings of 26 estimated individual fin whales in lower Cook Inlet were observed (Shelden 
                    <E T="03">et al.,</E>
                     2013, 2015, 2016, 2019). A total authorized take of four fin whales would account for two sightings of two animals, which is the lower end of the range of common group size. Exposure of up to four fin whales could occur in Year 1 and again in Year 2.
                </P>
                <P>The number of authorized killer whale takes is increased to 10 from the calculated exposure of one. Killer whales are typically sighted in pods of a few animals to 20 or more (NOAA, 2022b). During seismic surveys conducted in 2019 by Hilcorp in the lower Cook Inlet, 21 killer whales were observed, either as single individuals or in groups ranging in size from 2 to 5 individuals (Fairweather, 2020). Based on documented sightings, Hilcorp requested 10 takes of killer whales to allow for 2 sightings with a group size of 5 individuals in Year 1 and again in Year 2.</P>
                <P>
                    Depending on the density data used for each activity, the estimated annual exposures for beluga whales is 3 to 10 animals. The number of takes authorized for beluga whales is 11 animals for Year 1 and 22 animals in Year 2 to allow for the possibility that more than one observation of typical Cook Inlet beluga groups occurs. The 2018 MML aerial survey (Shelden and Wade, 2019) estimated a median group size of approximately 11 beluga whales, although group sizes were highly variable (2 to 147 whales) as was the case in previous survey years (Boyd 
                    <E T="03">et al.,</E>
                     2019). We are not accounting for multiple groups of 11 belugas for Year 1 given that a large portion of the total mobilization distance has already been traveled, making an encounter with multiple beluga groups less likely. Additionally, vessel-based surveys in 2019 observed beluga whale groups in the Susitna River Delta (roughly 24 km [15 miles] north of the Tyonek Platform) that ranged from 5 to 200 animals (McGuire 
                    <E T="03">et al.,</E>
                     2021). The very large groups seen in the Susitna River Delta are not expected near Hilcorp's platforms, however, smaller groups (
                    <E T="03">i.e.,</E>
                     around the median group size) could be traveling through to access the Susitna River Delta and other nearby coastal locations, particularly in the shoulder seasons when belugas are more likely to occur in middle Cook Inlet.
                </P>
                <P>
                    The number of Dall's porpoise takes authorized is increased from less than one estimated individual to six. Dall's porpoises are usually found in groups averaging between two and 12 individuals (NOAA, 2022c). During seismic surveys conducted in 2019 by Hilcorp in the lower Cook Inlet, Dall's porpoises were recorded in groups 
                    <PRTPAGE P="62389"/>
                    ranging in size from two to seven individuals (Fairweather, 2020). The 2012 Apache survey recorded two groups of three individual Dall's porpoises (Lomac-MacNair, 2014). Because occurrence of Dall's porpoise is anticipated to be less in middle Cook Inlet than lower Cook Inlet, the smaller end of documented group sizes (three individuals) is used, and Hilcorp requests six takes of Dall's porpoise to allow for two sightings of three individuals similar to the numbers observed during the 2012 Apache survey. The same number of takes are authorized in Year 1 and Year 2 because the calculated exposure for each year is less than one, making the group size methodology equally applicable to Year 1 and Year 2.
                </P>
                <P>
                    Harbor porpoise takes are increased from an estimated 10 takes to 44 takes. Shelden 
                    <E T="03">et al.</E>
                     (2014) compiled historical sightings of harbor porpoises from lower to upper Cook Inlet that spanned from a few animals to 92 individuals. The 2018 CIPL project that occurred just north of the Action Area in Cook Inlet reported 29 sightings of 44 individuals (Sitkiewicz 
                    <E T="03">et al.,</E>
                     2018). While the duration of days that the tugs are towing a jack-up rig will be less than the CIPL project, given the increase in sightings of harbor porpoise in recent years, the sighting of harbor porpoise during Hilcorp's rig move in June 2022, and the inability to shut down the tugs, Hilcorp requests 44 takes of harbor porpoise, commensurate with the number observed in the nearby CIPL project. Once the rig move to Tyonek is removed from the calculation, as Hilcorp completed that work before issuance of these IHAs, calculated exposure of harbor porpoise is less in Year 1 than in Year 2. However, based on Hilcorp's monitoring report during their initial rig move, more harbor porpoises were seen than expected, so NMFS did not reduce the authorized take for Year 1 from what was originally requested (which included the Tyonek rig move in the calculation). As a result, 44 takes of harbor porpoise are authorized for both Year 1 and Year 2.
                </P>
                <P>Take of harbor seal and Steller sea lion authorized for Year 1 and Year 2 is based on the calculated exposure. Because Hilcorp already completed a rig move to Tyonek and that effort has been removed from the calculation, take for both species in Year 1 is less than in Year 2.</P>
                <P>
                    Calculated take of Pacific white-sided dolphins and California sea lions was zero because the assumed density in Cook Inlet is zero. For California sea lions, any potential sightings would likely be lone out of habitat individuals. Two solitary individuals were seen during the 2012 Apache seismic survey in Cook Inlet (Lomac-MacNair 
                    <E T="03">et al.,</E>
                     2013). Two takes are authorized based on the potential that two lone animals could be sighted over a year of work, as was seen during Apache's year of work. For Pacific white-sided dolphins, the only reported visual sightings that NMFS is aware of was three dolphins from Apache's monitoring efforts in 2014 in Kenai, which is in the general vicinity of Hilcorp's planned activities. Therefore, NMFS authorized three takes of Pacific white-sided dolphins annually in case a repeated group of similar size is encountered. For both species, the same number of takes are authorized for Year 1 and Year 2 because the calculated exposure for each year would be zero given the lack of density data, making the group size methodology equally applicable to Year 1 and Year 2.
                </P>
                <HD SOURCE="HD1">Mitigation</HD>
                <P>In order to issue an IHA under section 101(a)(5)(D) of the MMPA, NMFS must set forth the permissible methods of taking pursuant to the activity, and other means of effecting the least practicable impact on the species or stock and its habitat, paying particular attention to rookeries, mating grounds, and areas of similar significance, and on the availability of the species or stock for taking for certain subsistence uses. NMFS regulations require applicants for incidental take authorizations to include information about the availability and feasibility (economic and technological) of equipment, methods, and manner of conducting the activity or other means of effecting the least practicable adverse impact upon the affected species or stocks and their habitat (50 CFR 216.104(a)(11)).</P>
                <P>In evaluating how mitigation may or may not be appropriate to ensure the least practicable adverse impact on species or stocks and their habitat, as well as subsistence uses where applicable, we carefully consider two primary factors:</P>
                <P>(1) The manner in which, and the degree to which, the successful implementation of the measure(s) is expected to reduce impacts to marine mammals, marine mammal species or stocks, and their habitat, as well as subsistence uses. This considers the nature of the potential adverse impact being mitigated (likelihood, scope, range). It further considers the likelihood that the measure will be effective if implemented (probability of accomplishing the mitigating result if implemented as planned), the likelihood of effective implementation (probability implemented as planned), and;</P>
                <P>(2) The practicability of the measures for applicant implementation, which may consider such things as cost, impact on operations, and, in the case of a military readiness activity, personnel safety, practicality of implementation, and impact on the effectiveness of the military readiness activity.</P>
                <HD SOURCE="HD2">Mitigation for Marine Mammals and Their Habitat</HD>
                <P>
                    NMFS anticipates the project, in both of the two IHAs, will create an acoustic footprint above ambient sound levels of approximately 45 km
                    <SU>2</SU>
                     around the tugs positioning the jack-up rig or for approximately 3.8 km in all directions along a towing trajectory of approximately 64 km (40 mi). There is a discountable potential for marine mammals to incur PTS from the project, as source levels are relatively low, non-impulsive, and animals would have to remain at very close distances for multiple hours to accumulate acoustic energy at levels that could damage hearing. Therefore, we do not believe there is potential for Level A harassment. However, Hilcorp will implement a number of mitigation measures designed to reduce the potential for and severity of Level B harassment, protect belugas in important beluga whale habitat, and minimize the acoustic footprint of the project.
                </P>
                <P>
                    The tugs towing a jack-up rig are not able to shut down while transiting or positioning the rig. Hilcorp will maneuver the tugs towing the jack-up rig such that they maintain a consistent speed (approximately 4 knots) and avoid multiple changes of speed and direction to make the course of the vessels as predictable as possible to marine mammals in the surrounding environment, characteristics that are expected to be associated with a lower likelihood of disturbance. Hilcorp will implement a clearance zone of 1,500 meters around the centerpoint of the three tug configuration and will employ two NMFS-approved protected species observers (PSOs) to conduct marine mammal monitoring for all mobile and stationary activity involving tugs towing attached to the jack-up rig. Prior to commencing activities during daylight hours or if there is a 30-minute lapse in operational activities, the PSOs will monitor the clearance zone for marine mammals for 30 minutes. If no marine mammals are observed, operations may commence. If a marine mammal(s) is observed within the clearance zone during the clearing, the PSOs will 
                    <PRTPAGE P="62390"/>
                    continue to watch until either: (1) the animal(s) is outside of and on a path away from the clearance zone; or (2) 15 minutes have elapsed if the species was a pinniped or small cetacean, or 30 minutes for large cetaceans whales. Once the PSOs have determined one of those conditions are met, operations may commence.
                </P>
                <P>Should a marine mammal be observed during towing or positioning, the PSOs will monitor and carefully record any reactions observed until the jack-up rig has reached its intended position. No new operational activities would be started until the animal leaves the area; transitioning from tugging to positioning without shutting down is not considered a new operational activity. PSOs will also collect behavioral information on marine mammals sighted during monitoring efforts.</P>
                <P>Hilcorp will make every effort to operate with the tide, resulting in a low power output from the tugs towing the jack-up rig. If human safety or equipment integrity is at risk, Hilcorp may necessarily operate in an unfavorable tidal state. Due to the nature of tidal cycles in Cook Inlet, it is possible the most favorable tide for the towing operation will occur during nighttime hours. Hilcorp will operate the tugs towing the jack-up rigs at night if the nighttime operations result in a lower power output from the tugs by operating with a favorable tide.</P>
                <P>
                    In low-light conditions, night-vision devices shown to be effective at detecting marine mammals in low-light conditions (
                    <E T="03">e.g.,</E>
                     PVS-7 night-vision devices or similar) will be provided to PSOs to aid in low-light visibility. Every effort will be made to observe that the clearance zone is free of marine mammals by using night-vision devices, however it may not always be possible to see and clear the entire clearance zone prior to nighttime transport. PSOs will monitor the greatest extent feasible for 30 minutes immediately prior to the start of load bearing activities. If no marine mammals are observed, operations may commence. If a marine mammal is observed within the during the clearing, the PSOs will continue to watch until either: (1) the animal(s) is outside of and on a path away from the clearance zone; or (2) 15 minutes have elapsed if the species was a pinniped or small cetacean, or 30 minutes for large cetaceans whales. Once the PSOs have determined one of those conditions are met, operations may commence.
                </P>
                <P>Out of concern for potential disturbance to Cook Inlet beluga whales in sensitive and essential habitat, Hilcorp will not conduct noise-producing activity within 16 km (10 miles) of the mean lower-low water (MLLW) line of the Susitna River Delta (Beluga River to the Little Susitna River) between April 15 and November 15 with the exception of work conducted at the Tyonek platform. The dates of applicability of this exclusion zone have been expanded based on new available science, including visual surveys and acoustic studies, which indicate that substantial numbers of Cook Inlet beluga whales continue to occur in the Susitna Delta area through at least mid-November (M. Castellote, pers. comm., T. McGuire, pers. comm.). As the MLLW is not a straight line but rather a jagged contour following the coastline, it is difficult to determine the southernmost extent of the zone during operations. For ease of implementation, the southernmost extent of the Susitna Delta exclusion zone will be considered a straight line from Tyonek at the west to Point Possession at the east (see Figure 3 below).</P>
                <BILCOD>BILLING CODE 3510-22-P</BILCOD>
                <GPH SPAN="3" DEEP="347">
                    <PRTPAGE P="62391"/>
                    <GID>EN14OC22.071</GID>
                </GPH>
                <BILCOD>BILLING CODE 3510-22-C</BILCOD>
                <P>During the course of consultation under section 7 of the ESA, Hilcorp notified NMFS that adhering to the exclusion zone for the Tyonek platform would not be practicable given the operational and human safety concerns of accessing the platform outside of the open water season. Prior to tugging the jack-up rig to and from the Tyonek platform, Hilcorp will conduct a systematic aerial survey of all marine waters within a 10 mile radius of the Tyonek platform that intersects with the Susitna Delta exclusion zone, termed the aerial survey area (see Figure 3) to ensure the area is clear of beluga whales. Aerial surveys will be flown with a PSO observing for beluga whales at an altitude of approximately 1,000 ft (305 m). This survey will be conducted no more than 12 hours (one half of one tide cycle) prior to the proposed departure of the rig from its moored or anchored location. If beluga whales are observed during the aerial survey prior to mobilizing the jack-up rig to or from the Tyonek platform, Hilcorp will not begin mobilization of the rig until a subsequent aerial survey indicates the aerial survey area contains no beluga whales. Starting from the proposed departure date, Hilcorp will conduct aerial surveys as described above and if belugas are seen in the aerial survey area will defer moving the jack-up rig if there is another departure date that fits the tide/tug criteria for moving onto and off of the dock within 8 days. If the rig move is deferred until the next departure window occurring within 8 days of the first proposed departure date, Hilcorp will again conduct aerial surveys and will defer moving the rig until the last available tide for departure that allows the tugs to complete the transport in that second departure time frame. If beluga whales are observed in the aerial survey area prior to the last available tide in the already deferred second departure time-frame, Hilcorp will move the jack-up rig to its next location. If there is not another departure date within 8 days of the first proposed departure date, Hilcorp will conduct multiple aerial surveys (weather permitting) as described above and if belugas are seen in the aerial survey area will defer moving the rig until the last available tide in that initial departure window that fits with the tugs availability to complete the rig transport. If ice or other safety conditions exist that require the tugs to move the jack-up rig to preserve human safety, Hilcorp will move the jack-up rig to its next location even if belugas are observed in the aerial survey area.</P>
                <P>Based on our evaluation of these measures, for both IHAs, NMFS has determined that the mitigation measures provide the means of effecting the least practicable impact on the affected species or stocks and their habitat, paying particular attention to rookeries, mating grounds, and areas of similar significance and on the availability of such species or stock for subsistence uses.</P>
                <HD SOURCE="HD1">Monitoring and Reporting</HD>
                <P>
                    In order to issue an IHA for an activity, section 101(a)(5)(D) of the MMPA states that NMFS must set forth requirements pertaining to the monitoring and reporting of such taking. The MMPA implementing regulations at 50 CFR 216.104 (a)(13) indicate that requests for authorizations must include the suggested means of accomplishing the necessary monitoring and reporting that will result in increased knowledge of the species and of the level of taking or impacts on populations of marine mammals that are expected to be 
                    <PRTPAGE P="62392"/>
                    present in the action area. Effective reporting is critical both to compliance as well as ensuring that the most value is obtained from the required monitoring.
                </P>
                <P>Monitoring and reporting requirements prescribed by NMFS should contribute to improved understanding of one or more of the following:</P>
                <P>
                    • Occurrence of marine mammal species or stocks in the area in which take is anticipated (
                    <E T="03">e.g.,</E>
                     presence, abundance, distribution, density).
                </P>
                <P>
                    • Nature, scope, or context of likely marine mammal exposure to potential stressors/impacts (individual or cumulative, acute or chronic), through better understanding of: (1) action or environment (
                    <E T="03">e.g.,</E>
                     source characterization, propagation, ambient noise); (2) affected species (
                    <E T="03">e.g.,</E>
                     life history, dive patterns); (3) co-occurrence of marine mammal species with the action; or (4) biological or behavioral context of exposure (
                    <E T="03">e.g.,</E>
                     age, calving or feeding areas).
                </P>
                <P>• Individual marine mammal responses (behavioral or physiological) to acoustic stressors (acute, chronic, or cumulative), other stressors, or cumulative impacts from multiple stressors.</P>
                <P>• How anticipated responses to stressors impact either: (1) long-term fitness and survival of individual marine mammals; or (2) populations, species, or stocks.</P>
                <P>
                    • Effects on marine mammal habitat (
                    <E T="03">e.g.,</E>
                     marine mammal prey species, acoustic habitat, or other important physical components of marine mammal habitat).
                </P>
                <P>• Mitigation and monitoring effectiveness.</P>
                <P>Hilcorp will abide by all monitoring and reporting measures contained within their Marine Mammal Monitoring and Mitigation Plan, dated March 7, 2022. A summary of those measures and additional requirements required by NMFS is provided below.</P>
                <P>A minimum of two NMFS-approved PSOs will be on-watch during all activities wherein the jack-up rig is attached to the tugs for the duration of the project. Minimum requirements for a PSO include:</P>
                <P>(a) Visual acuity in both eyes (correction is permissible) sufficient for discernment of moving targets at the water's surface with ability to estimate target size and distance; use of binoculars may be necessary to correctly identify the target;</P>
                <P>(b) Advanced education in biological science or related field (undergraduate degree or higher required)—PSOs may also substitute Alaska native traditional knowledge for experience;</P>
                <P>(c) Experience and ability to conduct field observations and collect data according to assigned protocols (this may include academic experience);</P>
                <P>(d) Experience or training in the field identification of marine mammals, including the identification of behaviors;</P>
                <P>(e) Sufficient training, orientation, or experience with the activity to provide for personal safety during observations;</P>
                <P>(f) Writing skills sufficient to prepare a report of observations including but not limited to the number and species of marine mammals observed; dates and times when tugging activities were conducted; dates and times when tugging activities were suspended; and marine mammal behavior; and</P>
                <P>(g) Ability to communicate orally, by radio or in person, with project personnel to provide real-time information on marine mammals observed in the area as necessary.</P>
                <P>PSOs will be stationed aboard a tug or the jack-up rig, work in shifts lasting no more than 4 hours without a minimum of a 1 hour break, and will not be on-watch for more than 12 hours within a 24-hour period.</P>
                <P>Hilcorp will submit monthly reports for all months in which tugs towing or positioning the jack-up rig occurs. A draft marine mammal monitoring report would be submitted to NMFS within 90 days after the completion of the tug towing jack-up rig activities for the year. It will include an overall description of work completed, a narrative regarding marine mammal sightings, and associated marine mammal observation data sheets. Specifically, the report must include:</P>
                <P>• Date and time that monitored activity begins or ends;</P>
                <P>• Construction activities occurring during each observation period;</P>
                <P>
                    • Weather parameters (
                    <E T="03">e.g.,</E>
                     percent cover, visibility);
                </P>
                <P>
                    • Water conditions (
                    <E T="03">e.g.,</E>
                     sea state, tide state);
                </P>
                <P>• Species, numbers, and, if possible, sex and age class of marine mammals;</P>
                <P>• Description of any observable marine mammal behavior patterns, including bearing and direction of travel and distance from tugging activity;</P>
                <P>• Distance from tugging activities to marine mammals and distance from the marine mammals to the observation point;</P>
                <P>• Locations of all marine mammal observations; and</P>
                <P>• Other human activity in the area.</P>
                <P>If no comments are received from NMFS within 30 days, the draft final report will constitute the final report. If NMFS submits comments, Hilcorp will submit a final report addressing NMFS comments within 30 days after receipt of comments.</P>
                <P>In the unanticipated event that the specified activity clearly causes the take of a marine mammal in a manner prohibited by the IHAs (if issued), such as an injury, serious injury or mortality, Hilcorp would immediately cease the specified activities and report the incident to the Chief of the Permits and Conservation Division, Office of Protected Resources, NMFS, and the Alaska Regional Stranding Coordinator. The report would include the following information:</P>
                <P>• Description of the incident;</P>
                <P>
                    • Environmental conditions (
                    <E T="03">e.g.,</E>
                     Beaufort sea state, 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>Activities would not resume until NMFS is able to review the circumstances of the prohibited take. NMFS would work with Hilcorp to determine what is necessary to minimize the likelihood of further prohibited take and ensure MMPA compliance. Hilcorp would not be able to resume their activities until notified by NMFS via letter, email, or telephone.</P>
                <P>
                    In the event that Hilcorp discovers an injured or dead marine mammal, and the lead PSO determines that the cause of the injury or death is unknown and the death is relatively recent (
                    <E T="03">e.g.,</E>
                     in less than a moderate state of decomposition as described in the next paragraph), Hiclrop would immediately report the incident to the Chief of the Permits and Conservation Division, Office of Protected Resources, NMFS, and the NMFS Alaska Stranding Hotline and/or by email to the Alaska Regional Stranding Coordinator. The report would include the same information identified in the paragraph above. Activities would be able to continue while NMFS reviews the circumstances of the incident. NMFS would work with Hilcorp to determine whether modifications in the activities are appropriate.
                </P>
                <P>
                    In the event that Hilcorp discovers an injured or dead marine mammal and the lead PSO determines that the injury or death is not associated with or related to the activities authorized in the IHAs (
                    <E T="03">e.g.,</E>
                     previously wounded animal, carcass with moderate to advanced decomposition, or scavenger damage), Hilcorp would report the incident to the 
                    <PRTPAGE P="62393"/>
                    Chief of the Permits and Conservation Division, Office of Protected Resources, NMFS, and the NMFS Alaska Stranding Hotline and/or by email to the Alaska Regional Stranding Coordinator, within 24 hours of the discovery. Hilcorp would provide photographs or video footage (if available) or other documentation of the stranded animal sighting to NMFS and the Marine Mammal Stranding Network.
                </P>
                <HD SOURCE="HD1">Negligible Impact Analysis and Determination</HD>
                <P>
                    NMFS has defined negligible impact 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 (50 CFR 216.103). A negligible impact finding is based on the lack of likely adverse effects on annual rates of recruitment or survival (
                    <E T="03">i.e.,</E>
                     population-level effects). An estimate of the number of takes alone is not enough information on which to base an impact determination. In addition to considering estimates of the number of marine mammals that might be “taken” through harassment, NMFS considers other factors, such as the likely nature of any impacts or responses (
                    <E T="03">e.g.,</E>
                     intensity, duration), the context of any impacts or responses (
                    <E T="03">e.g.,</E>
                     critical reproductive time or location, foraging impacts affecting energetics), as well as effects on habitat, and the likely effectiveness of the mitigation. We also assess the number, intensity, and context of estimated takes by evaluating this information relative to population status. Consistent with the 1989 preamble for NMFS' implementing regulations (54 FR 40338, September 29, 1989), the impacts from other past and ongoing anthropogenic activities are incorporated into this analysis via their impacts on the baseline (
                    <E T="03">e.g.,</E>
                     as reflected in the regulatory status of the species, population size and growth rate where known, ongoing sources of human-caused mortality, or ambient noise levels).
                </P>
                <P>To avoid repetition, the discussion of our analysis applies to all the species listed in Table 15, given that the anticipated effects of this activity on these different marine mammal stocks are expected to be similar in nature. There is little information about the nature or severity of the impacts, or the size, status, or structure of any of these species or stocks that would lead to a different analysis for this activity. Where there are meaningful differences between species or stocks, or groups of species, in anticipated individual responses to activities, impact of expected take on the population due to differences in population status, or impacts on habitat, they are described independently in the analysis below.</P>
                <P>
                    The project would create an acoustic footprint around the project area for a total of 14 to 16 days per year from approximately April through October, though not necessarily in the same calendar year. Noise levels within the footprint would reach or exceed 120 dB rms. We anticipate the 120 dB footprint to be limited to no more than 45 km
                    <SU>2</SU>
                     around the tugs positioning the jackup rig or approximately 3.8 km in all directions along a towing trajectory of approximately 64 km. The habitat within the footprint is not heavily used by marine mammals during the project time frame (
                    <E T="03">e.g.,</E>
                     Cook Inlet beluga whale Critical Habitat Area 2, within which the activity resulting in the take of marine mammals is anticipated to potentially occur, is designated for beluga fall and winter use) and marine mammals are not known to engage in critical behaviors associated with this portion of Cook Inlet (
                    <E T="03">e.g.,</E>
                     no known breeding grounds, foraging habitat, 
                    <E T="03">etc.</E>
                    ). Most animals will likely be transiting through the area; therefore, exposure would be brief. The tugs would be moving at a relatively slow speed and in a predictable manner that is not expected to result in more severe behavioral responses. Animals may swim around the project area, avoiding closer approaches to the boats, but we do not expect them to abandon any intended path.
                </P>
                <P>Feeding behavior is not likely to be significantly impacted, as no areas of biological significance for marine mammal feeding are known to exist in the project area and individual marine mammals are not expected to be exposed to the noise from the activities repeatedly or in long durations. We also expect the number of animals exposed to be small relative to population sizes. Finally, Hilcorp will minimize potential exposure of marine mammals to elevated noise levels by not commencing tugging activities if marine mammals are observed within the immediate starting area. Hilcorp is also able to reduce the impact of their activity by conducting tugging operations with favorable tides whenever feasible. Given this, any behavioral disturbance is expected to be comparatively low level and unlikely to affect the reproduction success or survival of any individuals, much less the population or stock.</P>
                <P>Potential impacts to marine mammal habitat were discussed previously in this document (see Potential Effects of Specified Activities on Marine Mammals and their Habitat). Marine mammal habitat may be impacted by elevated sound levels, but these impacts would be temporary. In addition to being temporary and short in overall duration, the acoustic footprint of both years of activity is small relative to the overall distribution of the animals in the area and their use of the area.</P>
                <P>In summary and as described above, the following factors primarily support our determinations that the impacts resulting from the activities described for these two IHAs are not expected to adversely affect the species or stock through effects on annual rates of recruitment or survival:</P>
                <P>• No mortality, serious injury, or injury is anticipated or authorized;</P>
                <P>• The mobile portion of the project does not involve noise sources capable of inducing PTS in any species other than high frequency cetaceans, and due to the small size of the PTS isopleth for high frequency cetaceans (6 meters), it is unlikely to occur;</P>
                <P>• Exposure would likely be brief given transiting behavior of marine mammals in the action area and the small number of days on which the activity is occurring;</P>
                <P>• Marine mammal densities are low in the project area; therefore, there will not be substantial numbers of marine mammals exposed to the noise from the project compared to the affected population sizes; and</P>
                <P>• Hilcorp will monitor for marine mammals daily and minimize exposure to operational activities.</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 monitoring and mitigation measures, NMFS finds that the total marine mammal take from the activity described in the Year 1 IHA will have a negligible impact on all affected marine mammal species or stocks. Also, separately, NMFS finds that the total marine mammal take from the activity described in the Year 2 IHA will have a negligible impact on all affected marine mammal species or stocks.</P>
                <HD SOURCE="HD1">Small Numbers</HD>
                <P>
                    As noted above, only small numbers of incidental take may be authorized under sections 101(a)(5)(A) and (D) of the MMPA for specified activities other than military readiness activities. The MMPA does not define small numbers and so, in practice, where estimated numbers are available, NMFS compares the number of individuals taken to the most appropriate estimation of 
                    <PRTPAGE P="62394"/>
                    abundance of the relevant species or stock in our determination of whether an authorization is limited to small numbers of marine mammals. When the predicted number of individuals to be taken is fewer than one third of the species or stock abundance (as it is for all stocks in both the Year 1 and Year 2 IHAs), the take is considered to be of small numbers. Additionally, other qualitative factors may be considered in the analysis, such as the temporal or spatial scale of the activities.
                </P>
                <P>Table 15 provides the quantitative analysis informing our small numbers determinations for the Year 1 and Year 2 IHAs. For most species, the amount of take authorized represents less than approximately two percent of the population for each IHA. For beluga whales, the amount of take authorized represents slightly under 8 percent of the population for each IHA.</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,r50,12,12,12">
                    <TTITLE>Table 15—Percent of Stock Authorized To Be Taken by Level B Harassment Under Each IHA</TTITLE>
                    <BOXHD>
                        <CHED H="1">Species</CHED>
                        <CHED H="1">Stock</CHED>
                        <CHED H="1">
                            Abundance
                            <LI>(Nbest)</LI>
                        </CHED>
                        <CHED H="1">
                            Authorized take
                            <LI>(Level B)</LI>
                        </CHED>
                        <CHED H="1">Percent of stock</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">Year 1:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Humpback whale</ENT>
                        <ENT>Western North Pacific; Central North Pacific</ENT>
                        <ENT>1,107; 10,103</ENT>
                        <ENT>5</ENT>
                        <ENT>0.45; 0.05</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Minke whale</ENT>
                        <ENT>Alaska</ENT>
                        <ENT>1,233</ENT>
                        <ENT>6</ENT>
                        <ENT>0.49</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Gray whale</ENT>
                        <ENT>Eastern Pacific</ENT>
                        <ENT>26,960</ENT>
                        <ENT>2</ENT>
                        <ENT>0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Fin whale</ENT>
                        <ENT>Northeastern Pacific</ENT>
                        <ENT>2,554</ENT>
                        <ENT>4</ENT>
                        <ENT>0.16</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Killer whale</ENT>
                        <ENT>Alaska Resident, Gulf of Alaska, Aleutian Islands, and Bering Sea Transient</ENT>
                        <ENT>587; 2,347</ENT>
                        <ENT>10</ENT>
                        <ENT>1.7; 0.43</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Beluga whale</ENT>
                        <ENT>Cook Inlet</ENT>
                        <ENT>279</ENT>
                        <ENT>11</ENT>
                        <ENT>3.94</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Pacific white-sided dolphin</ENT>
                        <ENT>North Pacific</ENT>
                        <ENT>26,880</ENT>
                        <ENT>3</ENT>
                        <ENT>0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Dall's porpoise</ENT>
                        <ENT>Alaska</ENT>
                        <ENT>83,400</ENT>
                        <ENT>6</ENT>
                        <ENT>0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Harbor porpoise</ENT>
                        <ENT>Gulf of Alaska</ENT>
                        <ENT>31,046</ENT>
                        <ENT>44</ENT>
                        <ENT>0.14</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Harbor seal</ENT>
                        <ENT>Cook Inlet/Shelikof</ENT>
                        <ENT>26,907</ENT>
                        <ENT>418</ENT>
                        <ENT>1.55</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Steller sea lion</ENT>
                        <ENT>Western</ENT>
                        <ENT>53,624</ENT>
                        <ENT>13</ENT>
                        <ENT>0.02</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">California sea lion</ENT>
                        <ENT>U.S.</ENT>
                        <ENT>233,515</ENT>
                        <ENT>2</ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Year 2:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Humpback whale</ENT>
                        <ENT>Western North Pacific; Central North Pacific</ENT>
                        <ENT>1,107; 10,103</ENT>
                        <ENT>6</ENT>
                        <ENT>0.5; 0.06</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Minke whale</ENT>
                        <ENT>Alaska</ENT>
                        <ENT>1,233</ENT>
                        <ENT>6</ENT>
                        <ENT>0.49</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Gray whale</ENT>
                        <ENT>Eastern Pacific</ENT>
                        <ENT>26,960</ENT>
                        <ENT>2</ENT>
                        <ENT>0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Fin whale</ENT>
                        <ENT>Northeastern Pacific</ENT>
                        <ENT>2,554</ENT>
                        <ENT>4</ENT>
                        <ENT>0.16</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Killer whale</ENT>
                        <ENT>Alaska Resident Gulf of Alaska, Aleutian Islands, and Bering Sea Transient</ENT>
                        <ENT>587</ENT>
                        <ENT>10</ENT>
                        <ENT>1.7; 0.43</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Beluga whale</ENT>
                        <ENT>Cook Inlet</ENT>
                        <ENT>279</ENT>
                        <ENT>22</ENT>
                        <ENT>7.89</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Pacific white-sided dolphin</ENT>
                        <ENT>North Pacific</ENT>
                        <ENT>26,880</ENT>
                        <ENT>3</ENT>
                        <ENT>0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Dall's porpoise</ENT>
                        <ENT>Alaska</ENT>
                        <ENT>83,400</ENT>
                        <ENT>6</ENT>
                        <ENT>0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Harbor porpoise</ENT>
                        <ENT>Gulf of Alaska</ENT>
                        <ENT>31,046</ENT>
                        <ENT>44</ENT>
                        <ENT>0.14</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Harbor seal</ENT>
                        <ENT>Cook Inlet/Shelikof</ENT>
                        <ENT>26,907</ENT>
                        <ENT>554</ENT>
                        <ENT>2.06</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Steller sea lion</ENT>
                        <ENT>Western</ENT>
                        <ENT>53,624</ENT>
                        <ENT>17</ENT>
                        <ENT>0.03</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">California sea lion</ENT>
                        <ENT>U.S.</ENT>
                        <ENT>233,515</ENT>
                        <ENT>2</ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Based on the analysis contained herein of the activity (including the mitigation and monitoring measures) and the anticipated take of marine mammals, NMFS finds that small numbers of marine mammals will be taken relative to the population size of the affected species or stocks for the Year 1 IHA. Separately, NMFS also finds that small numbers of marine mammals will be taken relative to the population size of the affected species or stocks for the Year 2 IHA.</P>
                <HD SOURCE="HD1">Unmitigable Adverse Impact Analysis and Determination</HD>
                <P>In order to issue an IHA, NMFS must find that the specified activity will not have an unmitigable adverse impact on the availability of such species or stock for taking for subsistence uses by Alaska Natives. NMFS has defined “unmitigable adverse impact” in 50 CFR 216.103 as an impact resulting from the specified activity: (1) That is likely to reduce the availability of the species to a level insufficient for a harvest to meet subsistence needs by: (i) Causing the marine mammals to abandon or avoid hunting areas; (ii) Directly displacing subsistence users; or (iii) Placing physical barriers between the marine mammals and the subsistence hunters; and (2) That cannot be sufficiently mitigated by other measures to increase the availability of marine mammals to allow subsistence needs to be met.</P>
                <P>To further minimize any potential effects of their action on subsistence activities, Hilcorp has outlined their communication plan for engaging with subsistence users in their Stakeholder Engagement Plan (Appendix B of Hilcorp's application). Hilcorp will be required to abide by this plan and update the plan accordingly.</P>
                <P>
                    Subsistence communities identified as project stakeholders near Hilcorp's middle Cook Inlet and Trading Bay activities include the Village of Salamatof and the Native Village of Tyonek. The ADF&amp;G Community Subsistence Information System does not contain data for Salamatof. For the purposes of our analyses for the Year 1 and Year 2 IHAs, we can assume the subsistence uses are similar to those of nearby communities such as Kenai. At 3.5 km away from the closest point of approach, Tyonek is the closest subsistence community to Hilcorp's planned tug route. Tyonek, on the western side of lower Cook Inlet, has a subsistence harvest area that extends from the Susitna River south to Tuxedni Bay (BOEM, 2016). In Tyonek, harbor seals were harvested between June and September by 6 percent of the households (Jones 
                    <E T="03">et al.,</E>
                     2015). Seals were harvested in several areas, encompassing an area stretching 32.2 km (20 miles) along the Cook Inlet coastline from the McArthur Flats north to the Beluga River. Seals were searched for or harvested in the Trading Bay areas as well as from the beach adjacent to Tyonek (Jones 
                    <E T="03">et al.,</E>
                     2015).
                </P>
                <P>
                    Cook Inlet beluga whale subsistence harvest discontinued in 1999 as a result of both a voluntary moratorium by the 
                    <PRTPAGE P="62395"/>
                    hunters that spring, and the passage of Public Law 106-31, section 3022 (later made permanent by Pub. L. 106-553, section 627), requiring any taking of Cook Inlet beluga whales by Alaska Natives to occur pursuant to a cooperative agreement between NMFS and affected Alaska Native organizations. A co-management agreement allowed the harvest of two whales in 2005 and one whale in 2006; however, no whales were taken in 2006 due to poor weather and the avoidance of females with calves. In 2008, NMFS issued regulations (73 FR 60976, October 15, 2008) establishing long-term limits on the maximum number of Cook Inlet beluga whales that may be taken for subsistence by Alaska Natives. These long-term harvest limits, developed for 5-year intervals, require that the abundance estimates reach a minimum 5-year average of 350 belugas (50 CFR 216.23(f)(2)(v)). No hunt has been authorized since 2006.
                </P>
                <P>Subsistence hunting of whales is not known to currently occur in Cook Inlet. Hilcorp's tug towing jack-up rig activities may overlap with subsistence hunting of seals. However, these activities typically occur along the shoreline or very close to shore near river mouths, whereas most of Hilcorp's tugging is in the middle of the Inlet and rarely near the shoreline or river mouths. Any harassment to harbor seals is anticipated to be short-term, mild, and not result in any abandonment or behaviors that would make the animals unavailable to Alaska Natives.</P>
                <P>Based on the description of the specified activity, the measures described to minimize adverse effects on the availability of marine mammals for subsistence purposes, and the mitigation and monitoring measures, NMFS has determined that there will not be an unmitigable adverse impact on subsistence uses from Hilcorp's activities under the Year 1 IHA. Separately, NMFS has also determined that there will not be an unmitigable adverse impact on subsistence uses from Hilcorp's activities under the Year 2 IHA.</P>
                <HD SOURCE="HD1">National Environmental Policy Act</HD>
                <P>NMFS prepared an Environmental Assessment (EA) and analyzed the potential impacts to marine mammals that would result from the Hilcorp tug towing jack-up rig activity. A Finding of No Significant Impact (FONSI) was signed on September 14, 2022. A copy of the EA and FONSI is available upon request.</P>
                <HD SOURCE="HD1">Endangered Species Act</HD>
                <P>NMFS authorized take of humpback whales (Mexico DPS, Western North Pacific DPS), fin whales (Northeastern Pacific stock), beluga whales (Cook Inlet stock), and Steller sea lion (Western DPS), which are listed under the ESA. The NMFS Alaska Regional Office Protected Resources Division issued a Biological Opinion on September 9, 2022 under section 7 of the ESA, on the issuance of an IHA to Hilcorp under section 101(a)(5)(D) of the MMPA by the NMFS Permits and Conservation Division. The Biological Opinion concluded that the action is not likely to jeopardize the continued existence of these populations, and is not likely to destroy or adversely modify critical habitat.</P>
                <HD SOURCE="HD1">Authorization</HD>
                <P>NMFS has issued two IHAs to Hilcorp for the potential harassment of small numbers of 12 marine mammal species incidental to tugging a jack-up rig in Cook Inlet, Alaska, that include the aforementioned mitigation, monitoring and reporting requirements.</P>
                <SIG>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <NAME>Catherine G. Marzin,</NAME>
                    <TITLE>Deputy Director, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22343 Filed 10-13-22; 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>
                <DEPDOC>[RTID 0648-XC442]</DEPDOC>
                <SUBJECT>Fisheries of the South Atlantic, Gulf of Mexico, and Caribbean; Southeast Data, Assessment, and Review (SEDAR) Public Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of SEDAR Procedural Workshop 8: Fishery Independent Index Development under Changing Survey Design.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The SEDAR Procedural Workshop 8 for Fishery Independent Index Development will consist of a series of webinars, and an in-person workshop. See 
                        <E T="02">SUPPLEMENTARY INFORMATION.</E>
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The SEDAR Procedural Workshop 8 will be held Wednesday, November 2, 2022, from 9 a.m. until 5 p.m., Eastern; Thursday, November 3, 2022, from 9 a.m. until 5 p.m., Eastern; and Friday, November 4, 2022, from 9 a.m. until 3 p.m., Eastern. The established times may be adjusted as necessary to accommodate the timely completion of discussion relevant to the SEDAR process. Such adjustments may result in the meeting being extended from or completed prior to the time established by this notice.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P> </P>
                    <P>
                        <E T="03">Meeting address:</E>
                         The SEDAR Procedural Workshop 8 meeting will be held at the Gulf of Mexico Fishery Management Council Office, 4107 West Spruce Street Suite 200, Tampa, FL 33607; phone: (888) 833-1844.
                    </P>
                    <P>
                        <E T="03">SEDAR address:</E>
                         4055 Faber Place Drive, Suite 201, N. Charleston, SC 29405; 
                        <E T="03">www.sedarweb.org.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Julie A. Neer, SEDAR Program Manager, 4055 Faber Place Drive, Suite 201, North Charleston, SC 29405; phone: (843) 571-4366 or toll free: (866)/SAFMC-10; fax: (843) 769-4520; email: 
                        <E T="03">Julie.neer@safmc.net.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>SEDAR procedural workshops provide an opportunity for focused discussion and deliberation on topics that arise in multiple assessments and are structured to develop best practices for addressing common issues across assessments. The SEDAR Steering Committee agreed that previously completed procedural workshops were effective and that similar workshops should be held to address other issues that affect multiple assessments. Continuing to address such global issues is recognized as important to continuing improvements in efficiency and quality.</P>
                <P>The 8th procedural workshop will consider methods of addressing the development for fishery-independent indices of abundance under changing survey designs. Participants will prepare a SEDAR procedures document addressing their recommendations that will be used to guide future SEDAR assessments.</P>
                <P>
                    Although non-emergency issues not contained in this agenda may come before this group for discussion, those issues may not be the subject of formal action during this meeting. Action will be restricted to those issues specifically identified in this notice and any issues arising after publication of this notice that require emergency action under section 305(c) of the Magnuson-Stevens Fishery Conservation and Management Act, provided the public has been notified of the intent to take final action to address the emergency.
                    <PRTPAGE P="62396"/>
                </P>
                <HD SOURCE="HD1">Special Accommodations</HD>
                <P>
                    This meeting is accessible to people with disabilities. Requests for auxiliary aids should be directed to the SEDAR office (see 
                    <E T="02">ADDRESSES</E>
                    ) at least 5 business days prior to the meeting.
                </P>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>The times and sequence specified in this agenda are subject to change.</P>
                </NOTE>
                <P>
                    <E T="03">Authority:</E>
                     16 U.S.C. 1801 
                    <E T="03">et seq.</E>
                </P>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>Rey Israel Marquez,</NAME>
                    <TITLE>Acting Deputy Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22389 Filed 10-13-22; 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>
                <DEPDOC>[RTID 0648-XC436]</DEPDOC>
                <SUBJECT>South Atlantic Fishery Management Council; Public Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of a public meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The South Atlantic Fishery Management Council (Council) will hold a meeting of its Habitat Protection and Ecosystem-Based Management Advisory Panel (Habitat AP).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The Habitat AP will meet on Tuesday, November 1, 2022, from 1 p.m. until 4 p.m., Wednesday, November 2, 2022, from 9 a.m. to 4 p.m., and Thursday, November 3, 2022, from 9 a.m. to 12 p.m. The meetings will be held in Charleston, SC.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P> </P>
                    <P>
                        <E T="03">Meeting address:</E>
                         The meeting will be held at the Town and Country Inn, 2008 Savannah Highway, Charleston, SC 29407; phone: (843) 571-1000.
                    </P>
                    <P>
                        The meeting is open to the public and will also be available via webinar. Registration is required. Webinar registration, an online public comment form, and briefing book materials will be available two weeks prior to the meeting at: 
                        <E T="03">https://safmc.net/advisory-council-meetings/.</E>
                    </P>
                    <P>
                        <E T="03">Council address:</E>
                         South Atlantic Fishery Management Council, 4055 Faber Place Drive, Suite 201, N Charleston, SC 29405.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kim Iverson, Public Information Officer, SAFMC; phone: (843) 571-4366 or toll free: (866) SAFMC-10; fax: (843) 769-4520; email: 
                        <E T="03">kim.iverson@safmc.net.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Habitat AP meeting agenda includes the following: NOAA overview of Deep Water Coral Mapping and Characterization in the South Atlantic Region; review and input on revisions to the Council's Beach Dredge and Fill and Large-Scale Coastal Engineering Policy Statement; initial discussion and guidance on updating the Council's energy policy; and an overview of the East Coast Climate Change Scenario Planning initiative.</P>
                <P>The AP will also receive updates on Renewable Energy (Offshore Wind) Development in the South Atlantic; NOAA Fisheries Habitat Conservation Division's Essential Fish Habitat (EFH) 5-year review and EFH consultations over the past year; and other items.</P>
                <P>The AP will develop recommendations for consideration by the Council's Habitat Protection and Ecosystem-Based Management Committee.</P>
                <HD SOURCE="HD1">Special Accommodations</HD>
                <P>
                    These meetings are physically accessible to people with disabilities. Requests for auxiliary aids should be directed to the Council office (see 
                    <E T="02">ADDRESSES</E>
                    ) 5 days prior to the meeting.
                </P>
                <NOTE>
                    <HD SOURCE="HED">Note: </HD>
                    <P>The times and sequence specified in this agenda are subject to change.</P>
                </NOTE>
                <P>
                    <E T="03">Authority:</E>
                     16 U.S.C. 1801 
                    <E T="03">et seq.</E>
                </P>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>Rey Israel Marquez,</NAME>
                    <TITLE>Acting Deputy Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22388 Filed 10-13-22; 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>
                <DEPDOC>[RTID 0648-XC459]</DEPDOC>
                <SUBJECT>Pacific Fishery Management Council; Public Meetings</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of public meetings.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Pacific Fishery Management Council (Pacific Council) and its advisory entities will hold online and in-person public meetings.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The Pacific Council and selected advisory committees will meet November 2-8, 2022 in Garden Grove, CA. The Pacific Council meeting will begin on Thursday, November 3, 2022, at 8 a.m. Pacific Time (PT), reconvening at 8 a.m. on Friday, November 4 through Tuesday, November 8, 2022. All meetings are open to the public, except for a Closed Session held from 8 a.m. to 9 a.m., Thursday, November 3, to address national security matters, international negotiations, litigation, or personnel matters including appointments to advisory bodies. The Pacific Council will meet as late as necessary each day to complete its scheduled business. The Pacific Council meeting will be held in a hybrid format with remote and in-person participation. The Council's Budget, Legislative, Scientific and Statistical, Enforcement Consultants, Highly Migratory Species, and Groundfish Committee meetings will occur in-person only in Garden Grove. All other advisory entities will meet by webinar only.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Meetings of the Pacific Council and aforementioned Committees will be held at the Hyatt Regency Orange County, 11999 Harbor Boulevard, Garden Grove, CA 92840; telephone: (714) 750-1234. The Council meetings will be held in-person and online. Specific meeting information, including directions on joining meetings, connecting to the live stream broadcast, and system requirements will be provided in the meeting materials on the Pacific Council's website (see 
                        <E T="03">www.pcouncil.org</E>
                        ). You may send an email to Mr. Kris Kleinschmidt (
                        <E T="03">kris.kleinschmidt@noaa.gov</E>
                        ) or contact him at (503) 820-2412 for technical assistance.
                    </P>
                    <P>
                        <E T="03">Council address:</E>
                         Pacific Fishery Management Council, 7700 NE Ambassador Place, Suite 101, Portland, OR 97220-1384.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Merrick Burden, Executive Director, Pacific Council; telephone: (503) 820-2418 or (866) 806-7204 toll-free, or access the Pacific Council website, 
                        <E T="03">www.pcouncil.org,</E>
                         for the proposed agenda and meeting briefing materials.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The November 2022 meeting of the Pacific Council will be in person and streamed live on the internet. The broadcasts begin initially at 9 a.m., PT Thursday, November 3, 2022 through Tuesday, November 8, 2022. Broadcasts end when business for the day is complete. Only the audio portion and presentations displayed on the screen at the Pacific Council meeting will be broadcast. The audio portion for the public is listen-only except that an opportunity for oral public comment will be provided prior to Council Action on each agenda item. Additional information and instructions on joining or listening to the meeting 
                    <PRTPAGE P="62397"/>
                    can be found on the Pacific Council's website (see 
                    <E T="03">www.pcouncil.org</E>
                    ).
                </P>
                <P>
                    The following items are on the Pacific Council agenda, but not necessarily in this order. Agenda items noted as “Final Action” refer to actions requiring the Council to transmit a proposed fishery management plan, proposed plan amendment, or proposed regulations to the U.S. Secretary of Commerce, under Sections 304 or 305 of the Magnuson-Stevens Fishery Conservation and Management Act. Additional detail on agenda items, Council action, and advisory entity meeting times, are described in Agenda Item A.4, Proposed Council Meeting Agenda, and will be in the advance briefing materials and posted on the Pacific Council website at 
                    <E T="03">www.pcouncil.org</E>
                     no later than Friday, October 14, 2022.
                </P>
                <FP SOURCE="FP-2">A. Call to Order</FP>
                <FP SOURCE="FP1-2">1. Opening Remarks</FP>
                <FP SOURCE="FP1-2">2. Roll Call</FP>
                <FP SOURCE="FP1-2">3. Executive Director's Report</FP>
                <FP SOURCE="FP1-2">4. Approve Agenda</FP>
                <FP SOURCE="FP-2">B. Open Comment Period</FP>
                <FP SOURCE="FP1-2">1. Comments on Non-Agenda Items</FP>
                <FP SOURCE="FP-2">C. Administrative Matters</FP>
                <FP SOURCE="FP1-2">1. Council Coordination Committee Report</FP>
                <FP SOURCE="FP1-2">2. National Marine Fisheries Service National Policy for Saltwater Recreational Fisheries</FP>
                <FP SOURCE="FP1-2">3. Legislative Matters</FP>
                <FP SOURCE="FP1-2">4. Chumash Heritage National Marine Sanctuary Designation</FP>
                <FP SOURCE="FP1-2">5. National Marine Fisheries Service Accomplishments and Priorities</FP>
                <FP SOURCE="FP1-2">6. Marine Planning</FP>
                <FP SOURCE="FP1-2">7. Fiscal Matters</FP>
                <FP SOURCE="FP1-2">8. Approval of Council Meeting Record</FP>
                <FP SOURCE="FP1-2">9. Membership Appointments and Council Operating Procedures</FP>
                <FP SOURCE="FP1-2">10. Future Council Meeting Agenda and Workload Planning</FP>
                <FP SOURCE="FP-2">D. Salmon Management</FP>
                <FP SOURCE="FP1-2">1. National Marine Fisheries Service Report</FP>
                <FP SOURCE="FP1-2">2. Final Methodology Review</FP>
                <FP SOURCE="FP1-2">3. 2023 Preseason Management Schedule</FP>
                <FP SOURCE="FP-2">E. Pacific Halibut Management</FP>
                <FP SOURCE="FP1-2">1. 2023 Catch Sharing Plan and Annual Regulations—Final Action</FP>
                <FP SOURCE="FP1-2">2. 2023 Commercial-Directed Fishery Regulations—Final Action</FP>
                <FP SOURCE="FP-2">F. Habitat Issues</FP>
                <FP SOURCE="FP1-2">1. Current Habitat Issues</FP>
                <FP SOURCE="FP-2">G. Highly Migratory Species Management</FP>
                <FP SOURCE="FP1-2">1. National Marine Fisheries Service Report</FP>
                <FP SOURCE="FP1-2">2. International Management Activities</FP>
                <FP SOURCE="FP1-2">3. Drift Gillnet Fishery Hard Caps—Final Action</FP>
                <FP SOURCE="FP1-2">4. Biennial Harvest Specifications and Management Measures—Preliminary</FP>
                <FP SOURCE="FP-2">H. Groundfish Management</FP>
                <FP SOURCE="FP1-2">1. National Marine Fisheries Service Report</FP>
                <FP SOURCE="FP1-2">2. Trawl Catch Share Program and Inter-Sector Allocation Review— Hearing Schedule</FP>
                <FP SOURCE="FP1-2">3. Sablefish Gear Switching</FP>
                <FP SOURCE="FP1-2">4. Methodology Review—Final Fishery Impact Model Topics and  Final Assessment Methodologies</FP>
                <FP SOURCE="FP1-2">5. Stock Definitions</FP>
                <FP SOURCE="FP1-2">6. Inseason Adjustments Including Pacific Whiting Set-Asides—Final Action</FP>
                <FP SOURCE="FP1-2">7. Electronic Monitoring</FP>
                <FP SOURCE="FP-2">I. Coastal Pelagic Species Management</FP>
                <FP SOURCE="FP1-2">1. National Marine Fisheries Service Report</FP>
                <FP SOURCE="FP1-2">2. Preliminary Review of Exempted Fishing Permits for 2023</FP>
                <FP SOURCE="FP1-2">3. Fishery Management Plan Housekeeping Amendment</FP>
                <FP SOURCE="FP1-2">4. Stock Assessment Terms of Reference—Final Action</FP>
                <FP SOURCE="FP1-2">5. Stock Assessment Prioritization</FP>
                <HD SOURCE="HD1">Advisory Body Agendas</HD>
                <P>
                    Advisory body agendas will include discussions of relevant issues that are on the Pacific Council agenda for this meeting and may also include issues that may be relevant to future Council meetings. Proposed advisory body agendas for this meeting will be available on the Pacific Council website, 
                    <E T="03">www.pcouncil.org,</E>
                     no later than Friday, October 14, 2022.
                </P>
                <GPOTABLE COLS="2" OPTS="L2,p1,8/9,i1" CDEF="s150,r25">
                    <TTITLE>Schedule of Ancillary Meetings</TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">
                            <E T="03">Day 1—Wednesday, November 2, 2022.</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Groundfish Advisory Subpanel </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Groundfish Management Team </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Habitat Committee </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Highly Migratory Species Advisory Subpanel </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Highly Migratory Species Management Team </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Scientific and Statistical Committee </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Salmon Technical Team </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Legislative Committee </ENT>
                        <ENT>10 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Salmon Advisory Subpanel </ENT>
                        <ENT>1 p.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Budget Committee </ENT>
                        <ENT>1 p.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Enforcement Consultants </ENT>
                        <ENT>2 p.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">
                            <E T="03">Day 2—Thursday, November 3, 2022.</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">California State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Oregon State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Washington State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Groundfish Advisory Subpanel </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Groundfish Management Team </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Habitat Committee </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Highly Migratory Species Advisory Subpanel </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Highly Migratory Species Management Team </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Scientific and Statistical Committee </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Enforcement Consultants </ENT>
                        <ENT>As needed</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">
                            <E T="03">Day 3—Friday, November 4, 2022.</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">California State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Oregon State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Washington State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Groundfish Advisory Subpanel </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Groundfish Management Team </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Highly Migratory Species Advisory Subpanel </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Highly Migratory Species Management Team </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Enforcement Consultants </ENT>
                        <ENT>As needed</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">
                            <E T="03">Day 4—Saturday, November 5, 2022.</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="62398"/>
                        <ENT I="03">California State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Oregon State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Washington State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Groundfish Advisory Subpanel </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Groundfish Management Team </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Coastal Pelagic Species Advisory Subpanel </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Coastal Pelagic Species Management Team </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Enforcement Consultants </ENT>
                        <ENT>As needed</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">
                            <E T="03">Day 5—Sunday, November 6, 2022.</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">California State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Oregon State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Washington State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Groundfish Advisory Subpanel </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Groundfish Management Team </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Coastal Pelagic Species Advisory Subpanel </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Coastal Pelagic Species Management Team </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Enforcement Consultants </ENT>
                        <ENT>As needed</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">
                            <E T="03">Day 6—Monday, November 7, 2022.</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">California State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Oregon State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Washington State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Groundfish Advisory Subpanel </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Groundfish Management Team </ENT>
                        <ENT>8 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Enforcement Consultants </ENT>
                        <ENT>As needed</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">
                            <E T="03">Day 7—Tuesday, November 8, 2022.</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">California State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Oregon State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Washington State Delegation </ENT>
                        <ENT>7 a.m.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Although non-emergency issues not contained in the meeting agenda may be discussed, those issues may not be the subject of formal action during these meetings. Action will be restricted to those issues specifically listed in this document and any issues arising after publication of this document that require emergency action under section 305(c) of the Magnuson-Stevens Fishery Conservation and Management Act, provided the public has been notified of the intent to take final action to address the emergency.</P>
                <HD SOURCE="HD1">Special Accommodations</HD>
                <P>
                    Requests for sign language interpretation or other auxiliary aids should be directed to Mr. Kris Kleinschmidt (
                    <E T="03">kris.kleinschmidt@noaa.gov;</E>
                     (503) 820-2412) at least 10 business days prior to the meeting date.
                </P>
                <P>
                    <E T="02">Authority:</E>
                     16 U.S.C. 1801 
                    <E T="03">et seq.</E>
                </P>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>Rey Israel Marquez,</NAME>
                    <TITLE>Acting Deputy Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22390 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">COMMISSION OF FINE ARTS</AGENCY>
                <SUBJECT>Notice of Meeting</SUBJECT>
                <P>The next meeting of the U.S. Commission of Fine Arts is scheduled for October 20, 2022, at 9 a.m. and will be held via online videoconference. Items of discussion may include buildings, infrastructure, parks, memorials, and public art.</P>
                <P>
                    Draft agendas, the link to register for the online public meeting, and additional information regarding the Commission are available on our website: 
                    <E T="03">www.cfa.gov.</E>
                     Inquiries regarding the agenda, as well as any public testimony, should be addressed to Thomas Luebke, Secretary, U.S. Commission of Fine Arts, at the above address; by emailing 
                    <E T="03">cfastaff@cfa.gov;</E>
                     or by calling 202-504-2200. Individuals requiring sign language interpretation for the hearing impaired should contact the Secretary at least 10 days before the meeting date.
                </P>
                <SIG>
                    <DATED>Dated: 11 October in Washington, DC.</DATED>
                    <NAME>Susan Raposa,</NAME>
                    <TITLE>Technical Information Specialist.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22403 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6330-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <SUBJECT>Defense Innovation Board, Notice of Federal Advisory Committee Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Under Secretary of Defense for Research and Engineering, Department of Defense (DoD).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Federal Advisory Committee meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The DoD is publishing this notice to announce that the following Federal Advisory Committee meeting of the Defense Innovation Board (DIB) will take place.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Closed to the public, Monday, October 17, 2022 from 12 p.m. to 3:45 p.m. Open to the public virtually, Monday, October 17, 2022 from 4 p.m. to 5 p.m.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The address of the meeting is Room 3E188 in the Pentagon, Washington, DC 20301.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ms. Colleen Laughlin, (703) 697-7020 (voice), 
                        <E T="03">colleen.r.laughlin.civ@mail.mil</E>
                         or 
                        <E T="03">osd.innovation@mail.mil</E>
                         (email). Mailing address is Defense Innovation Board, 4800 Mark Center Drive, Suite 16F09-02, Alexandria, VA 22350-3600. The most current meeting agenda can be found on the DIB website at: 
                        <E T="03">https://innovation.defense.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This meeting is being held under the provisions of the Federal Advisory Committee Act (FACA) (5 U.S.C.), the Government in the Sunshine Act (5 U.S.C. 552b), and 41 CFR 102-3.140 and 102-3.150.</P>
                <P>
                    Due to circumstances beyond the control of the Designated Federal Officer, the Defense Innovation Board was unable to provide public notification required by 41 CFR 102-3.150(a) concerning its October 17, 2022 meeting. Accordingly, the Advisory Committee Management Officer for the 
                    <PRTPAGE P="62399"/>
                    Department of Defense, pursuant to 41 CFR 102-3.150(b), waives the 15-calendar day notification requirement.
                </P>
                <P>
                    <E T="03">Purpose of the Meeting:</E>
                     The mission of the DIB is to provide the Secretary of Defense and the Deputy Secretary of Defense independent advice and strategic insights on the emerging technologies landscape, adoption of commercial sector innovation best practices, and the impact of disruptive and emerging technologies and their relevance to DoD. The DIB focuses on (a) technology and capabilities, (b) practices and operations, (c) people and culture, and (d) other research and analysis of topics raised by the Secretary of Defense, the Deputy Secretary of Defense, or the Under Secretary of Defense for Research and Engineering towards achieving National Defense goals. The objective of the meeting is to obtain, review, and evaluate information related to the DIB's mission.
                </P>
                <P>
                    <E T="03">Agenda:</E>
                     The DIB's meeting will begin in closed session on October 17, 2022 at 12 p.m. eastern time with opening remarks by Ms. Colleen Laughlin, the Executive Director and Designated Federal Officer (DFO) and Mr. Michael Bloomberg, the DIB Chair. The DIB will participate in classified discussions on matters related to national defense. These discussions will focus on senior DoD leader's defense innovation priorities and challenges and the broader innovation and national security landscape. The DFO will then adjourn the closed board meeting at 3:45 p.m.
                </P>
                <P>
                    The DFO will reconvene the DIB in an open meeting from 4 p.m. to 5 p.m., with opening remarks by the DFO and the DIB Chair. The DIB will then do member introductions, followed by a discussion of DIB tasks and mandate. The DFO will review comments submitted by the public; those will be provided to the DIB Chair and Members in advance and will be posted to the DIB website as part of the public record. The meeting will conclude with closing remarks by the DIB Chair and adjournment of the open meeting by the Designated Federal Officer at 5 p.m. The latest version of the agenda will be available on the Board's website at: 
                    <E T="03">https://innovation.defense.gov.</E>
                </P>
                <P>
                    <E T="03">Meeting Accessibility:</E>
                     In accordance with Section 10(d) of the FACA and 41 CFR 102-3.155, it is hereby determined that portions of the October 17, 2022 meeting of the DIB will include classified information and other matters covered by 5 U.S.C. 552b(c)(1) and that, accordingly, the meeting will be closed to the public on October 17, 2022 from 12 p.m. to 3:45 p.m. This determination was made in writing by the Under Secretary of Defense for Research and Engineering, in consultation with the DoD Office of General Counsel, based on the consideration that it is expected that discussions throughout this period will involve classified matters of national security. Such classified material is so intertwined with the unclassified material that it cannot reasonably be segregated into separate discussions without defeating the effectiveness and meaning of these portions of the meeting. To permit these portions of the meeting to be open to the public would preclude discussion of such matters and would greatly diminish the ultimate utility of the DIB's findings and recommendations to the Secretary of Defense, the Deputy Secretary of Defense, and the Under Secretary of Defense for Research and Engineering.
                </P>
                <P>
                    Pursuant to section 10(a)(1) of the FACA and 41 CFR 102-3.140, the portion of the meeting on October 17, 2022 from 4 p.m. to 5 p.m. is open to the public virtually. Members of the public wishing to receive a link to the livestream webcast should register on the DIB website listed in this notice no later than October 14, 2022. Members of the media should RSVP to the Office of the Assistant to the Secretary of Defense (Public Affairs), at 
                    <E T="03">osd.pentagon.pa.list.dop-atl@mail.mil.</E>
                     Requests to attend the virtual public session must be received no later than 12 p.m. on Friday, October 14, 2022.
                </P>
                <P>
                    <E T="03">Special Accommodations:</E>
                     Individuals requiring special accommodations to access the public meeting should contact the DFO (see the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section for contact information) no later than Friday, October 14, 2022 so that appropriate arrangements can be made.
                </P>
                <P>
                    <E T="03">Written Comments and Statements:</E>
                     Pursuant to 41 CFR 102-3.105(j) and 102-3.140 and section 10(a)(3) of the FACA, the public or interested organizations may submit written comments or statements to the DIB in response to the stated agenda of the meeting or in regard to the DIB's mission in general. Written comments may be submitted to the DFO via electronic mail (the preferred mode of submission) to the address 
                    <E T="03">osd.innovation@mail.mil</E>
                     in either Adobe Acrobat Portable Document Format (PDF) or Microsoft Word format. Each page of the comment or statement must include the author's name, title or affiliation, address, and daytime phone number. The DFO will compile all written submissions and provide them to DIB members for consideration. Written comments or statements received after 12 p.m. October 14, 2022 may not be provided to the DIB until its next scheduled meeting. Please note that because the DIB operates under the provisions of the FACA, all submitted comments and statements will be treated as public documents and will be made available for public inspection, including but not limited to being posted on the DIB's website.
                </P>
                <P>
                    <E T="03">Oral Presentations:</E>
                     Individuals wishing to make an oral statement to the DIB at the virtual public meeting may be permitted to speak for up to two minutes. Anyone wishing to speak to the DIB should submit a request by email at 
                    <E T="03">osd.innovation@mail.mil</E>
                     no later than October 14, 2022 for planning purposes. Requests for making oral comments should include a copy or summary of planned remarks for archival purposes and must include the author's name, title or affiliation, address, and daytime phone number. Individuals may also be permitted to submit a comment request at the public meeting; however, depending on the number of individuals making prior requests to speak, the schedule may limit participation. Webcast attendees will be provided instructions with the livestream link if they wish to submit comments during the open meeting.
                </P>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>Aaron T. Siegel,</NAME>
                    <TITLE>Alternate Federal Register Liaison Officer, Department of Defense.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22377 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 5001-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Department of the Navy</SUBAGY>
                <SUBJECT>Notice of Availability and Virtual Public Meetings for the Draft Environmental Impact Statement for Proposed Land Acquisition at the Washington Navy Yard, Washington, District of Columbia</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of the Navy (DoN), Department of Defense (DoD).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Pursuant to the National Environmental Policy Act (NEPA) of 1969, as implemented by the Council on Environmental Quality Regulations, the DoN prepared and filed with the United States Environmental Protection Agency (U.S. EPA), a Draft Environmental Impact Statement (EIS) that evaluates the potential environmental effects associated with the acquisition of land at the Southeast Federal Center (SEFC), at the Washington Navy Yard (WNY), Washington, DC. The Navy proposes to obtain 6 acres of land on the SEFC (the SEFC E Parcels) to improve the overall Antiterrorism (AT) posture of the WNY. 
                        <PRTPAGE P="62400"/>
                        By obtaining the SEFC E Parcels, the Navy would: (1) improve the WNY AT posture by reducing the encroachment threat posed by planned, private development on the SEFC E Parcels; (2) protect mission-critical activities conducted at the WNY from visual surveillance, and acoustic and electronic eavesdropping; and (3) enhance the overall safety of personnel, facilities, and infrastructure at the WNY.
                    </P>
                    <P>Should the Navy obtain ownership of the SEFC E Parcels, the Navy is considering three alternative uses for the acquired property: construction and operation of a relocated Navy Museum, construction of administrative facilities, or maintaining the status quo (no new development).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The DoN is initiating a public comment period beginning on October 14, 2022 and extending through December 2, 2022. Comments submitted during the public comment period, including comments on alternatives, information and analysis, and the summary thereof, will become part of the public record, and substantive comments will be considered in the Final EIS. All comments must be postmarked or received electronically by 11:59 p.m. eastern standard time (EST) on December 2, 2022, for consideration in the Final EIS. The Navy will hold two virtual public meetings to receive comments on the Draft EIS. In addition, per section 106 of the National Historic Preservation Act (NHPA) (36 CFR part 800.2(5)(d)), this undertaking has the potential to have effects on historic resources associated with the WNY. The public will be able to submit comments on the analysis pursuant to section 106 of the NHPA.</P>
                    <P>The meetings will be held:</P>
                    <P>• November 15, 2022, 6 p.m. to 7 p.m.</P>
                    <P>• November 16, 2022, 1 p.m. to 2 p.m.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Information on how to participate in the virtual public meetings is available on the Navy project website at: 
                        <E T="03">https://ndw.cnic.navy.mil/WNY-Land-Acquisition/1/.</E>
                    </P>
                    <P>Notices of the virtual public meetings will also be published in The Washington Post and through a press release.</P>
                    <P>The Navy will receive comments on the Draft EIS and pursuant to section 106 of the National Historic Preservation Act:</P>
                    <P>• Verbally during each of the two virtual public meetings.</P>
                    <P>
                        • Electronically via email: 
                        <E T="03">NAVFACWashNEPA1@navy.mil.</E>
                    </P>
                    <P>• By mail, postmarked no later than December 2, 2022, to the following address: Naval Facilities Engineering Systems Command Washington, Washington Navy Yard, ATTN: Navy EIS Project Manager, 1314 Harwood Street SE, Washington, DC 20374.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Naval Facilities Engineering Systems Command Washington, Washington Navy Yard, ATTN: Nik Tompkins-Flagg, Navy EIS Project Manager, 1314 Harwood Street SE, Washington, DC 20374, 202-685-8437, 
                        <E T="03">NAVFACWashNEPA1@navy.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    A Notice of Intent to prepare this EIS was published in the 
                    <E T="04">Federal Register</E>
                     on February 18, 2022 (
                    <E T="04">Federal Register</E>
                     (FR) Document Number 2022-03632). The WNY continues to be the “Quarterdeck of the Navy” and serves as the Headquarters for Naval District Washington, where it houses numerous support activities for fleet and aviation communities. The purpose of the Proposed Action is to improve the overall WNY AT posture (
                    <E T="03">i.e.,</E>
                     increase physical security and antiterrorism mitigation measures), as well as protect mission-critical activities at the WNY from visual surveillance, and acoustic and electronic eavesdropping. The need for the Proposed Action is to protect the WNY from encroachment that would result from proposed private development located adjacent to the northwest perimeter of the WNY.
                </P>
                <P>The DoN is considering two action alternatives that meet the purpose of and need for the proposed action, as well as a no action alternative. The two action alternatives are: Alternative 1, Land Acquisition through Land Exchange, and Alternative 2, Direct Land Acquisition. Both action alternatives have the same three sub-alternatives that address reuse of the acquired property. The three sub-alternatives are: (A) construct and operate a relocated National Museum of the United States Navy; (B) construct and operate Navy administrative facilities; and (C) bring property within the WNY fence line, but leave the parcels in their current underdeveloped state.  </P>
                <P>Under the No Action Alternative, the Proposed Action would not occur. The Navy would not acquire or reuse the SEFC E Parcels. Instead, the private development on the SEFC E Parcels would proceed as planned. Private development on the SEFC E Parcels has already been approved by local government in accordance with zoning ordinances and is currently scheduled to begin construction as early as 2023.</P>
                <P>Under Alternative 1, the Navy would exchange certain underutilized properties within the WNY Southeast Corner with a private developer to obtain acquisition rights and ownership of the approximately 6-acre SEFC E Parcels. GSA would then transfer ownership of the SEFC E parcels to the Navy via a federal-to-federal transfer. In exchange for acquisition rights, the Navy would transfer and/or lease underutilized assets (approximately 15 acres) at the WNY Southeast Corner to the developer. Land exchange of the SEFC E Parcels for the WNY Southeast Corner would require relocation of functions, including the Hazardous Waste Storage Site from the WNY Southeast Corner to other areas on the WNY. This alternative would also include future development on the WNY Southeast Corner by the private developer, and in-kind considerations at the WNY to be provided by the developer.</P>
                <P>Under Alternative 2, the Navy would acquire the rights to the SEFC E Parcels from the developer through purchase or condemnation, and would receive the SEFC E Parcels from GSA through a federal-to-federal transfer. No WNY property would transfer to the developer, and no missions or tenants would need to be relocated under this alternative.</P>
                <P>In the EIS, the DoN analyzes potential environmental impacts of the alternatives. Additionally, the DoN will conduct all coordination and consultation activities required by the National Historic Preservation Act and other laws, regulations, and Executive Orders determined to be applicable to the project. The DoN could implement mitigation and monitoring measures to avoid or reduce environmental impacts, as determined in cooperation with the appropriate regulatory agencies and consulting parties.</P>
                <P>
                    The DoN distributed the Draft EIS to federal agencies, other parties with which the DoN is consulting, and to other stakeholders, in accordance with 40 CFR 1503.1. Further, the DoN provided a press release to the local newspaper and distributed letters to stakeholders and other interested parties. The Draft EIS is also available for electronic viewing or download at: 
                    <E T="03">https://ndw.cnic.navy.mil/WNY-Land-Acquisition/1/.</E>
                </P>
                <SIG>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <NAME>B.F. Roach,</NAME>
                    <TITLE>Commander, Judge Advocate General's Corps, U.S. Navy, Federal Register Liaison Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22261 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3810-FF-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="62401"/>
                <AGENCY TYPE="N">DEPARTMENT OF EDUCATION</AGENCY>
                <SUBJECT>Reopening; Applications for New Awards; Promise Neighborhoods Program</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Elementary and Secondary Education, Department of Education.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; reopening of application period.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On June 29, 2022, the Department of Education (Department) published in the 
                        <E T="04">Federal Register</E>
                         a notice inviting applications (NIA) for the fiscal year (FY) 2022 Promise Neighborhoods competition, Assistance Listing Number 84.215N. The NIA established a deadline date of September 27, 2022, for transmittal of applications, which was subsequently extended until October 7, 2022. This notice reopens this competition to allow more time for the preparation and submission of applications by eligible applicants that are affected applicants (as described in Eligibility below), located in Puerto Rico, portions of Alaska covered by a Presidential major disaster declaration, and areas under a Presidential major disaster or emergency declaration resulting from Hurricane Ian, which includes Florida, the Seminole Tribe of Florida, North Carolina, and South Carolina.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Deadline for Transmittal of Applications for Affected Applicants:</E>
                         October 21, 2022.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Rich Wilson, U.S. Department of Education, 400 Maryland Avenue SW, Room 3W101, Washington, DC 20202-6450. Telephone: (202) 453-6709. Email: 
                        <E T="03">Richard.Wilson@ed.gov.</E>
                    </P>
                    <P>If you are deaf, hard of hearing, or have a speech disability and wish to access telecommunications relay services, please dial 7-1-1.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On June 29, 2022, we published the NIA for the FY 2022 Promise Neighborhoods competition in the 
                    <E T="04">Federal Register</E>
                     (87 FR 38719). On July 25, 2022, we published an extension notice in the 
                    <E T="04">Federal Register</E>
                     (87 FR 44107) because 
                    <E T="03">Grants.gov</E>
                    , the system used to submit applications electronically, was closed for site maintenance from September 23-29, 2022. We are reopening this competition for affected applicants described below to allow them more time—until October 21, 2022—to prepare and submit their applications.
                </P>
                <P>
                    <E T="03">Eligibility:</E>
                     The reopening of this competition applies to eligible applicants under the Promise Neighborhoods program that are affected applicants. An eligible applicant for this competition is defined in the NIA. To qualify as an affected applicant, the applicant must have a mailing address that is located in a jurisdiction that is part of one of the applicable federally declared disaster areas and must provide appropriate supporting documentation, if requested.
                </P>
                <P>The affected areas are those in which assistance to individuals or public assistance has been authorized under the following FEMA declarations:</P>
                <P>
                    • Puerto Rico (
                    <E T="03">https://www.fema.gov/disaster/4671</E>
                    );
                </P>
                <P>
                    • Portions of Alaska covered by a Presidential major disaster declaration (
                    <E T="03">https://www.fema.gov/disaster/4672</E>
                    );
                </P>
                <P>
                    • Florida (
                    <E T="03">https://www.fema.gov/disaster/4673</E>
                    );
                </P>
                <P>
                    • The Seminole Tribe of Florida (
                    <E T="03">https://www.fema.gov/disaster/4675</E>
                    );
                </P>
                <P>
                    • North Carolina (
                    <E T="03">https://www.fema.gov/disaster/3586</E>
                    ); and • South Carolina (
                    <E T="03">https://www.fema.gov/disaster/3585</E>
                    ).
                </P>
                <P>
                    Affected applicants that have already timely submitted applications under the FY 2022 Promise Neighborhood competition may submit a new application on or before the new application deadline of October 21, 2022, but they are not required to do so. If a new application is not submitted, the Department will use the application that was submitted by the original (or first extended) deadline. If a new application is submitted, the Department will consider the application that is last submitted and timely received by 11:59:59 p.m., Eastern Time, on October 21, 2022. Any application submitted by an affected applicant under the new deadline must contain evidence (
                    <E T="03">e.g.,</E>
                     the applicant organization mailing address) that the applicant is located in one of the applicable federally declared disaster areas and, if requested, must provide appropriate supporting documentation.
                </P>
                <P>We are not reopening the application period for all applicants. Applications from applicants that are not affected, as defined above, will not be accepted past the October 7, 2022, deadline.</P>
                <P>
                    <E T="03">Note:</E>
                     All information in the NIA for this competition remains the same, except for the deadline date for affected applicants.
                </P>
                <P>
                    <E T="03">Program Authority:</E>
                     20 U.S.C. 7273-7274.
                </P>
                <P>
                    <E T="03">Accessible Format:</E>
                     On request to the program contact person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    , individuals with disabilities can obtain this document and a copy of the application package in an accessible format. The Department will provide the requestor with an accessible format that may include Rich Text Format (RTF) or text format (txt), a thumb drive, an MP3 file, braille, large print, audiotape, or compact disc, or other accessible format.
                </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>
                    . You may access the official edition of the 
                    <E T="04">Federal Register</E>
                     and the Code of Federal Regulations at 
                    <E T="03">www.govinfo.gov.</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 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>James F. Lane,</NAME>
                    <TITLE>Senior Advisor, Office of the Secretary, Delegated the Authority to Perform the Functions and Duties of the Assistant Secretary for the Office, Elementary and Secondary Education.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22424 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4000-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <SUBJECT>Combined Notice of Filings #1</SUBJECT>
                <P>Take notice that the Commission received the following electric corporate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EC23-4-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Bitter Ridge Wind Farm, LLC, Persimmon Creek Wind Farm 1, LLC, BGTF Zeus Holdings LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Joint Application for Authorization Under Section 203 of the Federal Power Act of Bitter Ridge Wind Farm, LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/6/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221006-5177.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/27/22.
                </P>
                <P>Take notice that the Commission received the following exempt wholesale generator filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EG23-5-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     RWE Renewables Americas, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Baron Winds LLC submits Notice of Self-Certification of Exempt Wholesale Generator Status.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/7/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221007-5005.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/28/22.
                </P>
                <PRTPAGE P="62402"/>
                <P>Take notice that the Commission received the following Complaints and Compliance filings in EL Dockets:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EL23-2-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Pacific Gas and Electric Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Petition for Declaratory Order of Pacific Gas and Electric Company.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/3/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221003-5359.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 11/2/22.
                </P>
                <P>Take notice that the Commission received the following electric rate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER20-1954-002.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     ITC Great Plains, LLC, Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: ITC Great Plains, LLC submits tariff filing per 35: ITC Great Plains, LLC Second Revised Order No. 864 Compliance Filing to be effective 1/27/2020.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/7/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221007-5091.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/28/22.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER22-469-002.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: 1148R21 American Electric Power Service Corporation—Deficiency Response to be effective 12/1/2021.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/5/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221005-5133.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/26/22.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER22-643-002.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: 3881SO Southwestern Power Admin &amp; AEP OK—Deficiency Response to be effective 12/31/9998.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/5/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221005-5134.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/26/22.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER22-644-002.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: 3882SO Southwestern Power Admin&amp;Publ Ser—Deficiency Response to be effective 12/31/9998.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/5/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221005-5137.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/26/22.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER22-2660-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: SPS Amended Formula Rate Revisions to Incorporate Changes Accepted in Er22-201 to be effective 5/19/2021.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/7/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221007-5017.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/28/22.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER22-2690-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PPL Electric Utilities Corporation, PJM Interconnection, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: PPL Services Corporation submits tariff filing per 35.17(b): PJM TOs Response to Deficiency Letter in ER22-2690 to be effective 10/19/2022.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/5/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221005-5140.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/26/22.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER23-32-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Duke Energy Florida, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: DEF-ECOGEN Notice of Cancellation of LGIA SA No. 180 to be effective 12/6/2022.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/6/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221006-5135.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/27/22.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER23-33-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Tri-State Generation and Transmission Association, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Amendment to Rate Schedule FERC No. 13 to be effective 10/3/2022.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/6/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221006-5138.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/27/22.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER23-34-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Pacific Gas and Electric Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: LS Power Grid California LLC (Gates 500kV) IA (TO SA 447) to be effective 10/7/2022.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/6/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221006-5143.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/27/22.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER23-35-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PJM Interconnection, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Original ISA/CSA, Service Agreement Nos. 6651/6652; Queue No. AG1-080 to be effective 9/7/2022.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/7/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221007-5011.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/28/22.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER23-36-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PJM Interconnection, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Cost Responsibility Agreement, SA No. 6614; Non-Queue No. NQ-187 to be effective 9/12/2022.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/7/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221007-5014.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/28/22.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER23-37-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PacifiCorp.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Deseret TSOA Rev 9 to be effective 12/7/2022.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/7/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221007-5034.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/28/22.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER23-38-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 2022-10-07_SA 3142 Termination of ITC Midwest-EDF Renewables E&amp;P (J495) to be effective 10/8/2022.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/7/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221007-5039.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/28/22.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER23-39-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 2022-10-07_SA 3129 Termination of MidAmerican-Glaciers Edge Wind E&amp;P (J506) to be effective 10/8/2022.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/7/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221007-5041.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/28/22.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER23-40-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc., Otter Tail Power Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Midcontinent Independent System Operator, Inc. submits tariff filing per 35.13(a)(2)(iii: 2022-10-07_SA 3913 3914 OTP-NSP FCA &amp; FSA (Forman-Canby-Fergus MPFP) to be effective 12/7/2022.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/7/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221007-5051.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/28/22.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER23-41-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Duke Energy Business Services LLC, PJM Interconnection, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: Duke Energy Business Services LLC submits tariff filing per 35.15: Notice of Termination of Amended and Restated IA, PJM SA No. 3137 to be effective 12/7/2022.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/7/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20221007-5059.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/28/22.
                </P>
                <P>Take notice that the Commission received the following electric reliability filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RD22-5-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     North American Electric Reliability Corporation.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Application of the North American Electric Reliability Corporation for approval of FAC-001-4 and FAC-002-4.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/14/22.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20220614-5204.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 10/28/22.
                </P>
                <P>
                    The filings are accessible in the Commission's eLibrary system (
                    <E T="03">https://elibrary.ferc.gov/idmws/search/fercgensearch.asp</E>
                    ) by querying the docket number.
                </P>
                <P>
                    Any person desiring to intervene or protest in any of the above proceedings 
                    <PRTPAGE P="62403"/>
                    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: October 7, 2022.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22350 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. TX23-2-000]</DEPDOC>
                <SUBJECT>EnerSmart Imperial Beach BESS LLC; Notice of Filing</SUBJECT>
                <P>
                    Take notice that on October 6, 2022, pursuant to section 211 of the Federal Power Act,
                    <SU>1</SU>
                    <FTREF/>
                     and Section 9.3.3 of the San Diego Gas &amp; Electric Company (SDG&amp;E) Transmission Owner Tariff (SDG&amp;E TO Tariff), and Section 4 of the SDG&amp;E Wholesale Distribution Open Access Tariff (SDG&amp;E Tariffs), EnerSmart Imperial Beach BESS LLC (EnerSmart Imperial Beach) filed an application requesting that the Federal Energy Regulatory Commission (Commission) issue an order requiring SDG&amp;E to provide interconnection and transmission service for the proposed Imperial Beach BESS battery energy storage facility under the terms and conditions of the Transmission Control Agreement between SDG&amp;E and the California Independent System Operator Corporation (CAISO), the SDG&amp;E Tariffs, CAISO's Fifth Replacement FERC Electric Tariff, and the Small Generator Interconnection Agreements between EnerSmart Imperial Beach and SDG&amp;E, dated May 31, 2022, as it may be in effect from time to time.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         16 U.S.C. 824j (2018).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The SGIA is associated with application numbers W192 and W193 for two 3 MW battery energy storage facilities, interconnecting at two points of interconnection, specified as (i) an extension of Imperial Beach circuit 158 from the manhole M1528073924 and (ii) an extension of Imperial Beach circuit 532 from the manhole M1526873925.
                    </P>
                </FTNT>
                <P>Any person desiring to intervene or to protest this filing must file in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214). Protests will be considered by the Commission in determining the appropriate action to be taken, but will not serve to make protestants parties to the proceeding. Any person wishing to become a party must file a notice of intervention or motion to intervene, as appropriate. Such notices, motions, or protests must be filed on or before the comment date. Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant. On or before the comment date, it is not necessary to serve motions to intervene or protests on persons other than the Applicant.</P>
                <P>
                    In addition to publishing the full text of this document in the 
                    <E T="04">Federal Register</E>
                    , the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the internet through the Commission's Home Page (
                    <E T="03">http://ferc.gov</E>
                    ) using the “eLibrary” link. Enter the docket number excluding the last three digits in the docket number field to access the document. At this time, the Commission has suspended access to the Commission's Public Reference Room, due to the proclamation declaring a National Emergency concerning the Novel Coronavirus Disease (COVID-19), issued by the President on March 13, 2020. For assistance, contact FERC at 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                     or call toll-free, (886) 208-3676 or TYY, (202) 502-8659.
                </P>
                <P>
                    The Commission strongly encourages electronic filings of comments, protests and interventions in lieu of paper using the “eFiling” link at 
                    <E T="03">http://www.ferc.gov.</E>
                     Persons unable to file electronically may mail similar pleadings to the Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426. Hand delivered submissions in docketed proceedings should be delivered to Health and Human Services, 12225 Wilkins Avenue, Rockville, Maryland 20852.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5:00 p.m. Eastern Time on November 7, 2022.
                </P>
                <SIG>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22351 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. CP22-2-000]</DEPDOC>
                <SUBJECT>Gas Transmission Northwest LLC; Notice of Revised Schedule for Environmental Review of the GTN XPress Project</SUBJECT>
                <P>This notice provides the Federal Energy Regulatory Commission staff's revised schedule for completion of the environmental impact statement (EIS) for Gas Transmission Northwest LLC's (GTN) GTN XPress Project. The Notice of Intent issued on January 21, 2022 identified October 14, 2022 as the final EIS issuance date. However, numerous comments filed during the draft EIS comment period require additional time for Commission staff's analysis. As a result, staff has revised the schedule for issuance of the final EIS.</P>
                <HD SOURCE="HD1">Schedule for Environmental Review</HD>
                <FP SOURCE="FP-1">Issuance of the Notice of Availability of the final EIS—November 18, 2022</FP>
                <FP SOURCE="FP-1">
                    90-day Federal Authorization Decision Deadline 
                    <SU>1</SU>
                    <FTREF/>
                    —February 16, 2023
                </FP>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The Commission's deadline applies to the decisions of other federal agencies, and state agencies acting under federally delegated authority, that are responsible for federal authorizations, permits, and other approvals necessary for proposed projects under the Natural Gas Act. Per 18 CFR 157.22(a), the Commission's deadline for other agency's decisions applies unless a schedule is otherwise established by federal law.
                    </P>
                </FTNT>
                <P>If a schedule change becomes necessary, an additional notice will be provided so that the relevant agencies are kept informed of the project's progress.</P>
                <HD SOURCE="HD1">Additional Information</HD>
                <P>
                    In order to receive notification of the issuance of the EIS and to keep track of all formal issuances and submittals in specific dockets, the Commission offers a free service called eSubscription. This can reduce the amount of time you spend researching proceedings by automatically providing you with notification of these filings, document summaries, and direct links to the documents. Go to 
                    <E T="03">https://www.ferc.gov/ferc-online/overview</E>
                     to register for eSubscription.
                </P>
                <P>
                    Additional information about the Project is available from the Commission's Office of External Affairs at (866) 208-FERC or on the FERC website (
                    <E T="03">www.ferc.gov</E>
                    ). Using the “eLibrary” link, select “General Search” from the eLibrary menu, enter the selected date range and “Docket Number” excluding the last three digits (
                    <E T="03">i.e.,</E>
                     CP22-2), and follow the 
                    <PRTPAGE P="62404"/>
                    instructions. For assistance with access to eLibrary, the helpline can be reached at (866) 208-3676, TTY (202) 502-8659, or at 
                    <E T="03">FERCOnlineSupport@ferc.gov.</E>
                     The eLibrary link on the FERC website also provides access to the texts of formal documents issued by the Commission, such as orders, notices, and rule makings.
                </P>
                <SIG>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22365 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. TX23-1-000]</DEPDOC>
                <SUBJECT>EnerSmart Mesa Heights BESS LLC; Notice of Filing</SUBJECT>
                <P>
                    Take notice that on October 6, 2022, pursuant to section 211 of the Federal Power Act,
                    <SU>1</SU>
                    <FTREF/>
                     and Section 9.3.3 of the San Diego Gas &amp; Electric Company (SDG&amp;E) Transmission Owner Tariff (SDG&amp;E TO Tariff), and Section 4 of the SDG&amp;E Wholesale Distribution Open Access Tariff (SDG&amp;E Tariffs), EnerSmart Mesa Heights BESS LLC (EnerSmart Mesa Heights) filed an application requesting that the Federal Energy Regulatory Commission (Commission) issue an order requiring SDG&amp;E to provide interconnection and transmission service for the proposed Mesa Heights BESS battery energy storage facility under the terms and conditions of the Transmission Control Agreement between SDG&amp;E and the California Independent System Operator Corporation (CAISO), the SDG&amp;E Tariffs, CAISO's Fifth Replacement FERC Electric Tariff, and the Small Generator Interconnection Agreement between EnerSmart Mesa Heights and SDG&amp;E, dated May 31, 2022, as it may be in effect from time to time.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         16 U.S.C. 824j (2018).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The SGIA is associated with application number W162 for the 3 MW battery energy storage facility, interconnecting at a single point of interconnection, specified as an extension of Mesa Heights circuit 1286 from the nearby pole P95664. SGIA at Attachment 2.
                    </P>
                </FTNT>
                <P>Any person desiring to intervene or to protest this filing must file in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214). Protests will be considered by the Commission in determining the appropriate action to be taken, but will not serve to make protestants parties to the proceeding. Any person wishing to become a party must file a notice of intervention or motion to intervene, as appropriate. Such notices, motions, or protests must be filed on or before the comment date. Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant. On or before the comment date, it is not necessary to serve motions to intervene or protests on persons other than the Applicant.</P>
                <P>
                    In addition to publishing the full text of this document in the 
                    <E T="04">Federal Register</E>
                    , the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the internet through the Commission's Home Page (
                    <E T="03">http://ferc.gov</E>
                    ) using the “eLibrary” link. Enter the docket number excluding the last three digits in the docket number field to access the document. At this time, the Commission has suspended access to the Commission's Public Reference Room, due to the proclamation declaring a National Emergency concerning the Novel Coronavirus Disease (COVID-19), issued by the President on March 13, 2020. For assistance, contact FERC at 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                     or call toll-free, (886) 208-3676 or TYY, (202) 502-8659.
                </P>
                <P>
                    The Commission strongly encourages electronic filings of comments, protests and interventions in lieu of paper using the “eFiling” link at 
                    <E T="03">http://www.ferc.gov.</E>
                     Persons unable to file electronically may mail similar pleadings to the Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426. Hand delivered submissions in docketed proceedings should be delivered to Health and Human Services, 12225 Wilkins Avenue, Rockville, Maryland 20852.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5:00 p.m. Eastern Time on November 7, 2022.
                </P>
                <SIG>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22349 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. IC22-22-000]</DEPDOC>
                <SUBJECT>Commission Information Collection Activities (Ferc-539), Comment Request; Extension</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Energy Regulatory Commission, DOE.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of information collection and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In compliance with the requirements of the Paperwork Reduction Act of 1995, the Federal Energy Regulatory Commission (Commission or FERC) is soliciting public comment on the currently approved information collection, FERC-539 (Gas Pipeline Certificates: Import &amp; Export Related Applications), which will be submitted to the Office of Management and Budget (OMB). The Commission published a 60-day notice in the 
                        <E T="04">Federal Register</E>
                         on August 1, 2022 and received no comments on the 60-day notice.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on the collection of information are due November 14, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Send written comments on FERC 539 to OMB through 
                        <E T="03">www.reginfo.gov/public/do/PRAMain,</E>
                         Attention: Federal Energy Regulatory Commission Desk Officer. Please identify the OMB Control Number 1902-0062 (Gas Pipeline Certificates: Import &amp; Export Related Applications) in the subject line. Your comments should be sent within 30 days of publication of this notice in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                    <P>
                        Please submit copies of your comments (identified by Docket No. IC22-22-000 and the form) to the Commission as noted below. Electronic filing through 
                        <E T="03">https://www.ferc.gov,</E>
                         is preferred.
                    </P>
                    <P>
                        • 
                        <E T="03">Electronic Filing:</E>
                         Documents must be filed in acceptable native applications and print-to-PDF, but not in scanned or picture format.
                    </P>
                    <P>• For those unable to file electronically, comments may be filed by USPS mail or by hand (including courier) delivery.</P>
                    <P>
                        ○ 
                        <E T="03">Mail via U.S. Postal Service only, addressed to:</E>
                         Federal Energy Regulatory Commission, Secretary of the Commission, 888 First Street NE, Washington, DC 20426.
                    </P>
                    <P>
                        ○ 
                        <E T="03">Hand (including courier) delivery to:</E>
                         Federal Energy Regulatory Commission, Secretary of the Commission, 12225 Wilkins Avenue, Rockville, MD 20852.
                    </P>
                    <P>Please reference the specific collection number(s) and/or title(s) in your comments.</P>
                    <P>
                        <E T="03">Instructions:</E>
                         OMB submissions must be formatted and filed in accordance with submission guidelines at: 
                        <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                         Using the search function under the “Currently Under Review field,” select Federal Energy Regulatory Commission; click “submit” and select “comment” to the right of the subject collection. FERC submissions must be formatted and filed 
                        <PRTPAGE P="62405"/>
                        in accordance with submission guidelines at: 
                        <E T="03">https://www.ferc.gov.</E>
                         For user assistance contact FERC Online Support by email at 
                        <E T="03">ferconlinesupport@ferc.gov,</E>
                         or by phone at (866) 208-3676 (toll-free).
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         Users interested in receiving automatic notification of activity in this docket or in viewing/downloading comments and issuances in this docket may do so at 
                        <E T="03">https://www.ferc.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ellen Brown may be reached by email at 
                        <E T="03">DataClearance@FERC.gov</E>
                         and telephone at (202) 502-8663.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <P>
                    <E T="03">Title:</E>
                     FERC-539 (Gas Pipeline Certificates: Import &amp; Export Related Applications).
                </P>
                <P>
                    <E T="03">OMB Control No.:</E>
                     1902-0062.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Three-year extension of the FERC-539 with no changes to the current reporting requirements.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The purpose of FERC-539 is to implement information collections pursuant to Section 3 of the Natural Gas Act (NGA).
                    <SU>1</SU>
                    <FTREF/>
                     This statute provides, in part, that “. . . no person shall export any natural gas from the United States to a foreign country or import any natural gas from a foreign country without first having secured an order from the Commission authorizing it to do so.” 
                    <SU>2</SU>
                    <FTREF/>
                     This statute applies not only to natural gas imported and/or exported via pipeline but also to any import and/or export of liquefied natural gas via a liquefied natural gas terminal. The 1992 amendments to Section 3 of the NGA concern importation or exportation from/to a nation which has a free trade agreement with the United States, and requires that such importation or exportation: (1) Shall be deemed to be a “first sale”, 
                    <E T="03">i.e.,</E>
                     not a sale for a resale, and (2) Shall be deemed to be consistent with the public interest, and applications for such importation or exportation shall be granted without modification or delay.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 717-717w
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         15 U.S.C. 717b
                    </P>
                </FTNT>
                <P>
                    <E T="03">Estimate of Annual Burden:</E>
                     
                    <SU>3</SU>
                    <FTREF/>
                     The Commission estimates the annual public reporting burden for the information collection as:
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Burden is defined as the total time, effort, or financial resources expended by persons to generate, maintain, retain, or disclose or provide information to or for a federal agency. See 5 CFR 1320 for additional information on the definition of information collection burden.
                    </P>
                </FTNT>
                <GPOTABLE COLS="6" OPTS="L2(,0,),i1" CDEF="s50,12C,12C,r50,r50,12C">
                    <TTITLE>FERC-539, Gas Pipeline Certificates: Import &amp; Export Related Applications</TTITLE>
                    <BOXHD>
                        <CHED H="1">Number of respondents</CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses per respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Total number
                            <LI>of responses</LI>
                        </CHED>
                        <CHED H="1">
                            Average burden hours &amp; 
                            <LI>
                                average cost 
                                <SU>4</SU>
                                 per response
                            </LI>
                            <LI>($)</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual burden hours &amp; total annual cost
                            <LI>($)</LI>
                        </CHED>
                        <CHED H="1">
                            Cost per
                            <LI>respondent</LI>
                            <LI>($)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW RUL="s">
                        <ENT I="25">(1)</ENT>
                        <ENT>(2)</ENT>
                        <ENT>(1) * (2) = (3)</ENT>
                        <ENT>(4)</ENT>
                        <ENT>(3) * (4) = (5)</ENT>
                        <ENT>(5) ÷ (1) = (6)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">6</ENT>
                        <ENT>2</ENT>
                        <ENT>12</ENT>
                        <ENT>15 hours; $1,305</ENT>
                        <ENT>180 hours; $15,660</ENT>
                        <ENT>$2,610</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Comments:</E>
                    <FTREF/>
                     Comments are invited on: (1) whether the collections of information are necessary for the proper performance of the functions of the Commission, including whether the information will have practical utility; (2) the accuracy of the agency's estimates of the burden and cost of the collections of information, including the validity of the methodology and assumptions used; (3) ways to enhance the quality, utility and clarity of the information collections; and (4) ways to minimize the burden of the collections of information on those who are to respond, including the use of automated collection techniques or other forms of information technology.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The Commission staff estimates that industry is similarly situated in terms of hourly cost (for wages plus benefits). Based on the Commission's FY (Fiscal Year) 2021 average cost (for wages plus benefits), $87.00/hour is used.
                    </P>
                </FTNT>
                <SIG>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22364 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Project No. 349-157]</DEPDOC>
                <SUBJECT>Alabama Power Company; Notice of Application Accepted for Filing and Soliciting Comments, Motions To Intervene, and Protests</SUBJECT>
                <P>Take notice that the following hydroelectric application has been filed with the Commission and is available for public inspection:</P>
                <P>
                    a. 
                    <E T="03">Type of Application:</E>
                     Non-Project Use of Project Lands and Waters.
                </P>
                <P>
                    b. 
                    <E T="03">Project No.:</E>
                     349-157.
                </P>
                <P>
                    c. 
                    <E T="03">Date Filed:</E>
                     July 21, 2022, as supplemented on September 23, 2022.
                </P>
                <P>
                    d. 
                    <E T="03">Applicant:</E>
                     Alabama Power Company.
                </P>
                <P>
                    e. 
                    <E T="03">Name of Project:</E>
                     Martin Dam Hydroelectric Project.
                </P>
                <P>
                    f. 
                    <E T="03">Location:</E>
                     The Martin Dam Hydroelectric Project is located on the Tallapoosa River (Lake Martin), in Tallapoosa, Elmore, and Coosa counties, Alabama, and occupies federal land administered by the U.S. Bureau of Land Management; the non-project use is located in Elmore County.
                </P>
                <P>
                    g. 
                    <E T="03">Filed Pursuant to:</E>
                     Federal Power Act, 16 U.S.C. 791a-825r.
                </P>
                <P>
                    h. 
                    <E T="03">Applicant Contact:</E>
                     Unzell Kelley, Alabama Power Company at (205) 517-0885 or 
                    <E T="03">ukelley@southernco.com</E>
                    .
                </P>
                <P>
                    i. 
                    <E T="03">FERC Contact:</E>
                     Shana High at (202) 502-8674 or 
                    <E T="03">shana.high@ferc.gov</E>
                    .
                </P>
                <P>
                    j. 
                    <E T="03">Deadline for filing motions to intervene and protests:</E>
                     November 7, 2022.
                </P>
                <P>
                    The Commission strongly encourages electronic filing. Please file comments, motions to intervene, and protests using the Commission's eFiling system at 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling.asp.</E>
                     Commenters can submit brief comments up to 6,000 characters, without prior registration, using the eComment system at 
                    <E T="03">http://www.ferc.gov/docs-filing/ecomment.asp.</E>
                     You must include your name and contact information at the end of your comments. For assistance, please contact FERC Online Support at 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     (866) 208-3676 (toll free), or (202) 502-8659 (TTY). In lieu of electronic filing, you may submit a paper copy. Submissions sent via the U.S. Postal Service must be addressed to: Kimberly D. Bose, Secretary, Federal Energy Regulatory Commission, 888 First Street NE, Room 1A, Washington, DC 20426. Submissions sent via any other carrier must be addressed to: Kimberly D. Bose, 
                    <PRTPAGE P="62406"/>
                    Secretary, Federal Energy Regulatory Commission, 12225 Wilkins Avenue, Rockville, Maryland 20852. The first page of any filing should include docket number P-349-157. Comments emailed to Commission staff are not considered part of the Commission record.
                </P>
                <P>The Commission's Rules of Practice and Procedure require all intervenors filing documents with the Commission to serve a copy of that document on each person whose name appears on the official service list for the project. Further, if an intervenor files comments or documents with the Commission relating to the merits of an issue that may affect the responsibilities of a particular resource agency, they must also serve a copy of the document on that resource agency.</P>
                <P>
                    k. 
                    <E T="03">Description of Request:</E>
                     Alabama Power Company is requesting Commission authorization to permit Russell Lands, Inc. to expand Kowaliga Marina. As proposed, Kowaliga Marina would include 13 docks that would accommodate 258 boats and 45 personal watercraft, two forklift piers, a boat ramp, four breakwaters, a seawall, and riprap.
                </P>
                <P>
                    l. 
                    <E T="03">Locations of the Application:</E>
                     This filing may be viewed on the Commission's website at 
                    <E T="03">http://www.ferc.gov</E>
                     using the “eLibrary” link. Enter the docket number excluding the last three digits in the docket number field to access the document. You may also register online at 
                    <E T="03">http://www.ferc.gov/docs-filing/esubscription.asp</E>
                     to be notified via email of new filings and issuances related to this or other pending projects. For assistance, call 1-866-208-3676 or email 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     for TTY, call (202) 502-8659. Agencies may obtain copies of the application directly from the applicant.
                </P>
                <P>m. Individuals desiring to be included on the Commission's mailing list should so indicate by writing to the Secretary of the Commission.</P>
                <P>
                    n. 
                    <E T="03">Comments, Protests, or Motions to Intervene:</E>
                     Anyone may submit comments, a protest, or a motion to intervene in accordance with the requirements of Rules of Practice and Procedure, 18 CFR 385.210, .211, .214, respectively. In determining the appropriate action to take, the Commission will consider all protests or other comments filed, but only those who file a motion to intervene in accordance with the Commission's Rules may become a party to the proceeding. Any comments, protests, or motions to intervene must be received on or before the specified comment date for the particular application.
                </P>
                <P>
                    o. 
                    <E T="03">Filing and Service of Documents:</E>
                     Any filing must (1) bear in all capital letters the title “COMMENTS”, “PROTEST”, or “MOTION TO INTERVENE” as applicable; (2) set forth in the heading the name of the applicant and the project number of the application to which the filing responds; (3) furnish the name, address, and telephone number of the person commenting, protesting or intervening; and (4) otherwise comply with the requirements of 18 CFR 385.2001 through 385.2005. All comments, motions to intervene, or protests must set forth their evidentiary basis. Any filing made by an intervenor must be accompanied by proof of service on all persons listed in the service list prepared by the Commission in this proceeding, in accordance with 18 CFR 385.2010.
                </P>
                <SIG>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22367 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. CP17-40-006]</DEPDOC>
                <SUBJECT>Spire STL Pipeline LLC; Notice of Availability of the Final Environmental Impact Statement for the Spire STL Pipeline Project</SUBJECT>
                <P>The staff of the Federal Energy Regulatory Commission (FERC or Commission) has prepared a final environmental impact statement (EIS) for the continued operation of the Spire STL Pipeline Project (Spire STL), proposed by Spire STL Pipeline LLC (Spire) in the above-referenced docket. Spire requests the Commission to reissue a Certificate of Public Convenience and Necessity authorizing operation of the Spire STL.</P>
                <P>The final EIS assesses the continued operation of the Spire STL in accordance with the requirements of the National Environmental Policy Act (NEPA). FERC staff concludes that impacts from the continued operation of the Spire STL would be less than significant, with the exception of climate change impacts resulting from GHG emissions that are not characterized as significant or insignificant.</P>
                <P>The final EIS addresses the potential environmental effects of the continued operation of the following project facilities:</P>
                <P>• 59.2 miles of 24-inch-diameter pipeline in Scott, Greene, and Jersey Counties, Illinois and St. Charles and St. Louis Counties, Missouri;</P>
                <P>• 6.0 miles of 24-inch-diameter pipeline (the North County Extension) in St. Louis County, Missouri; and</P>
                <P>• three new meter stations—the Rockies Express Pipeline LLC (REX) Receipt Station in Scott County, Illinois and the Laclede/Lange Delivery Station and Chain of Rocks station in St. Louis County, Missouri.</P>
                <P>
                    The Commission mailed a copy of the 
                    <E T="03">Notice of Availability</E>
                     of the final EIS to federal, state, and local government representatives and agencies; elected officials; environmental and public interest groups; Native American tribes; potentially affected landowners and other interested individuals and groups; and newspapers and libraries in the project area. The final EIS is only available in electronic format. It may be viewed and downloaded from the FERC's website (
                    <E T="03">www.ferc.gov</E>
                    ), on the natural gas environmental documents page (
                    <E T="03">https://www.ferc.gov/industries-data/natural-gas/environment/environmental-documents</E>
                    ). In addition, the final EIS may be accessed by using the eLibrary link on the FERC's website. Click on the eLibrary link (
                    <E T="03">https://elibrary.ferc.gov/eLibrary/search</E>
                    ) select “General Search” and enter the docket number in the “Docket Number” field, excluding the last three digits (
                    <E T="03">i.e.,</E>
                     CP17-40). Be sure you have selected an appropriate date range. For assistance, please contact FERC Online Support at 
                    <E T="03">FercOnlineSupport@ferc.gov</E>
                     or toll free at (866) 208-3676, or for TTY, contact (202) 502-8659.
                </P>
                <P>
                    Additional information about the project is available from the Commission's Office of External Affairs, at (866) 208-FERC, or on the FERC website (
                    <E T="03">www.ferc.gov</E>
                    ) using the eLibrary link. The eLibrary link also provides access to the texts of all formal documents issued by the Commission, such as orders, notices, and rulemakings.
                </P>
                <P>
                    In addition, the Commission offers a free service called eSubscription that allows you to keep track of all formal issuances and submittals in specific dockets. This can reduce the amount of time you spend researching proceedings by automatically providing you with notification of these filings, document summaries, and direct links to the documents. Go to 
                    <E T="03">https://www.ferc.gov/ferc-online/overview</E>
                     to register for eSubscription.
                </P>
                <SIG>
                    <PRTPAGE P="62407"/>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22366 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <DEPDOC>[FRL OP-OFA-039] </DEPDOC>
                <SUBJECT>Environmental Impact Statements; Notice of Availability</SUBJECT>
                <P>
                    <E T="03">Responsible Agency:</E>
                     Office of Federal Activities, General Information 202-564-5632 or 
                    <E T="03">https://www.epa.gov/nepa.</E>
                </P>
                <FP SOURCE="FP-1">Weekly receipt of Environmental Impact Statements (EIS) </FP>
                <FP SOURCE="FP-1">Filed October 3, 2022 10 a.m. EST Through October 7, 2022 10 a.m. EST Pursuant to 40 CFR 1506.9.</FP>
                <HD SOURCE="HD1">Notice</HD>
                <P>
                    Section 309(a) of the Clean Air Act requires that EPA make public its comments on EISs issued by other Federal agencies. EPA's comment letters on EISs are available at: 
                    <E T="03">https://cdxapps.epa.gov/cdx-enepa-II/public/action/eis/search.</E>
                </P>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 20220145, Final, FHWA, SC,</E>
                     I-526 Lowcountry Corridor West,  Contact: Jeffrey (Shane) Belcher 803-253-3187. 
                </FP>
                <P>Under 23 U.S.C. 139(n)(2), FHWA has issued a single document that consists of a final environmental impact statement and record of decision. Therefore, the 30-day wait/review period under NEPA does not apply to this action.</P>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 20220146, Final, USN, HI,</E>
                     Pearl Harbor Naval Shipyard and Intermediate Maintenance Facility Dry Dock and Waterfront Production Facility at Joint Base Pearl Harbor-Hickam, Oahu, Hawaii,  Review Period Ends: 11/14/2022, Contact: Andrea Von Burg Hall 808-472-1425.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 20220147, Draft, USN, DC,</E>
                     Proposed Land Acquisition at Washington Navy Yard, Washington, DC,  Comment Period Ends: 11/28/2022, Contact: Nik Tompkins-Flagg 202-685-8437.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 20220148, Draft, TxDOT, TX,</E>
                     Spur 399 Extension,  Comment Period Ends: 12/09/2022, Contact: Doug Booher 512-416-2663.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 20220149, Final, FERC, MO,</E>
                     Spire STL Pipeline Project,  Review Period Ends: 11/14/2022, Contact: Office of External Affairs 1-866-208-3372.
                </FP>
                <SIG>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <NAME>Marthea Rountree,</NAME>
                    <TITLE>Acting Director, NEPA Compliance Division, Office of Federal Activities.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22360 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[FRL-10283-01-OMS]</DEPDOC>
                <SUBJECT>Cross-Media Electronic Reporting: Authorized Program Revision Approval, Maine Department of Environmental Protection</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 the Environmental Protection Agency's (EPA) approval of the Maine Department of Environmental Protection (ME DEP) request to revise/modify certain of its EPA-authorized programs to allow electronic reporting.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>EPA approves the authorized program revisions/modifications as of October 14, 2022.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Shirley M. Miller, U.S. Environmental Protection Agency, Office of Information Management, Mail Stop 2824T, 1200 Pennsylvania Avenue NW, Washington, DC 20460, (202) 566-2908, 
                        <E T="03">miller.shirley@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On October 13, 2005, the final Cross-Media Electronic Reporting Rule (CROMERR) was published in the 
                    <E T="04">Federal Register</E>
                     (70 FR 59848) and codified as part 3 of title 40 of the CFR. CROMERR establishes electronic reporting as an acceptable regulatory alternative to paper reporting and establishes requirements to assure that electronic documents are as legally dependable as their paper counterparts. Subpart D of CROMERR requires that state, tribal or local government agencies that receive, or wish to begin receiving, electronic reports under their EPA-authorized programs must apply to EPA for a revision or modification of those programs and obtain EPA approval. Subpart D provides standards for such approvals based on consideration of the electronic document receiving systems that the state, tribe, or local government will use to implement the electronic reporting. Additionally, § 3.1000(b) through (e) of 40 CFR part 3, subpart D provides special procedures for program revisions and modifications to allow electronic reporting, to be used at the option of the state, tribe or local government in place of procedures available under existing program-specific authorization regulations. An application submitted under the subpart D procedures must show that the state, tribe or local government has sufficient legal authority to implement the electronic reporting components of the programs covered by the application and will use electronic document receiving systems that meet the applicable subpart D requirements.
                </P>
                <P>
                    On June 29, 2022, the Maine Department of Environmental Protection (ME DEP) submitted an application titled shared services integrated into CDX system for revisions/modifications to its EPA-approved programs under title 40 CFR to allow new electronic reporting. EPA reviewed ME DEP's request to revise/modify its EPA-authorized programs and, based on this review, EPA determined that the application met the standards for approval of authorized program revisions/modifications set out in 40 CFR part 3, subpart D. In accordance with 40 CFR 3.1000(d), this notice of EPA's decision to approve ME DEP's request to revise/modify its following EPA-authorized programs to allow electronic reporting under 40 CFR is being published in the 
                    <E T="04">Federal Register</E>
                    :
                </P>
                <P>• Part 52: Approval and Promulgation of Implementation Plans (SIP/Clean Air Act Title II) Reporting under 40 CFR 50 through 52.</P>
                <P>ME DEP was notified of EPA's determination to approve its application with respect to the authorized programs listed above.</P>
                <SIG>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <NAME>Jennifer Campbell,</NAME>
                    <TITLE>Director, Office of Information Management.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22286 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">EXPORT-IMPORT BANK</AGENCY>
                <DEPDOC>[Public Notice: 2022-3029]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Comment Request; Form Title: EIB 12-01 Medium-Term Master Guarantee Agreement Disbursement Approval 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>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Export-Import Bank of the United States (EXIM Bank), as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal Agencies to comment on the 
                        <PRTPAGE P="62408"/>
                        proposed information collection, as required by the Paperwork Reduction Act of 1995. EXIM Bank has 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 EXIM Bank and legal documentation has been completed, the lender will obtain and review the required disbursement documents (
                        <E T="03">e.g.,</E>
                         invoices, bills of lading, Exporter's Certificate, 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 EXIM Bank's online application system (EXIM Online). Using the form, the lender will input key data and request EXIM Bank's approval of the disbursement. EXIM Bank's action (approved or denied) is posted on the lender's history page. The information collected in the questionnaire will assist EXIM Bank in determining that each disbursement under a Medium-Term Guarantee meets all the terms and conditions for approval. The information collection tool can be reviewed at: 
                        <E T="03">http://exim.gov/sites/default/files/pub/pending/eib12-01.pdf.</E>
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before November 14, 2022 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments may be submitted electronically on 
                        <E T="03">WWW.REGULATIONS.GOV</E>
                        or by mail to Office of Information and Regulatory Affairs, 725 17th Street NW, Washington, DC 20038, Attn: OMB 3048-0049.
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <P>
                    <E T="03">Title and Form Number:</E>
                     EIB 12-01 Medium-Term Master Guarantee Agreement Disbursement Approval Request.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     3048-0049.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Regular.
                </P>
                <P>
                    <E T="03">Need and Use:</E>
                     The information requested enables EXIM Bank to determine that a disbursement under a Medium-Term Guarantee meets all of the terms and conditions for approval.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                </P>
                <P>This form affects lenders involved in the financing of U.S. goods and services exports.</P>
                <P>
                    <E T="03">Annual Number of Respondents:</E>
                     150.
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     30 minutes.
                </P>
                <P>
                    <E T="03">Annual Burden Hours:</E>
                     75 hours.
                </P>
                <P>
                    <E T="03">Frequency of Reporting of Use:</E>
                     Annual.
                </P>
                <P>
                    <E T="03">Government Expenses:</E>
                </P>
                <P>
                    <E T="03">Reviewing time per year:</E>
                     38 hours.
                </P>
                <P>
                    <E T="03">Average Wages per Hour:</E>
                     $42.50.
                </P>
                <P>
                    <E T="03">Average Cost per Year:</E>
                     $1,615.00 (time*wages).
                </P>
                <P>
                    <E T="03">Benefits and Overhead:</E>
                     20%.
                </P>
                <P>
                    <E T="03">Total Government Cost:</E>
                     $1,938.
                </P>
                <SIG>
                    <NAME>Andy Chang,</NAME>
                    <TITLE>Director, IT Records Management.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22328 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6690-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">EXPORT-IMPORT BANK</AGENCY>
                <DEPDOC>[Public Notice: 2022-3030]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Comment Request; Form Title: EIB 12-02 Credit Guarantee Facility Disbursement Approval 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>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Export-Import Bank of the United States (EXIM Bank), as part of its continuing effort to reduce paperwork and respondent burden, invites the public and other Federal Agencies to comment on the proposed information collection, as required by the Paperwork Reduction Act of 1995.</P>
                    <P>
                        EXIM Bank has an electronic disbursement approval processing system for guaranteed lenders with Credit Guarantee Facilities. After a Credit Guarantee Facility (CGF) has been authorized by EXIM Bank and legal documentation has been completed, the lender will obtain and review the required disbursement documents (
                        <E T="03">e.g.,</E>
                         invoices, bills of lading, Exporter's Certificate, 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 EXIM Bank's online application system (EXIM Online). Using the form, the lender will input key data and request EXIM Bank's approval of the disbursement. EXIM Bank's action (approved or denied) is posted on the lender's history page. The information collected in the questionnaire will assist EXIM Bank in determining that each disbursement under a Medium-Term Guarantee meets all the terms and conditions for approval. The information collection tool can be reviewed at: 
                        <E T="03">http://exim.gov/sites/default/files/pub/pending/eib12-02.pdf.</E>
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before November 14, 2022 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments may be submitted electronically on 
                        <E T="03">WWW.REGULATIONS.GOV</E>
                         or by mail to Office of Information and Regulatory Affairs, 725 17th Street NW, Washington, DC 20038, Attn: OMB 3048-0046.
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <P>
                    <E T="03">Title and Form Number:</E>
                     EIB 12-02 Credit Guarantee Facility Disbursement Approval Request.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     3048-0046.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Regular.
                </P>
                <P>
                    <E T="03">Need and Use:</E>
                     The information requested enables EXIM Bank to determine that a disbursement under a Credit Guarantee Facility meets all of the terms and conditions for approval.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                </P>
                <P>This form affects lenders involved in the financing of U.S. goods and services exports.</P>
                <P>
                    <E T="03">Annual Number of Respondents:</E>
                     50.
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     60 minutes.
                </P>
                <P>
                    <E T="03">Annual Burden Hours:</E>
                     50 hours.
                </P>
                <P>
                    <E T="03">Frequency of Reporting of Use:</E>
                     Annual.
                </P>
                <P>
                    <E T="03">Government Expenses:</E>
                </P>
                <P>
                    <E T="03">Reviewing time per year:</E>
                     25 hours.
                </P>
                <P>
                    <E T="03">Average Wages per Hour:</E>
                     $42.50.
                </P>
                <P>
                    <E T="03">Average Cost per Year:</E>
                     $1,062.50 (time*wages).
                </P>
                <P>
                    <E T="03">Benefits and Overhead:</E>
                     20%.
                </P>
                <P>
                    <E T="03">Total Government Cost:</E>
                     $1,275.
                </P>
                <SIG>
                    <NAME>Andy Chang,</NAME>
                    <TITLE>Director, IT Records Management.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22324 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6690-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">EXPORT-IMPORT BANK</AGENCY>
                <DEPDOC>[Public Notice: 2022-3032]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Comment Request; Form Title: EIB 15-04 Exporter's Certificate for Co-Financed Loan, Guarantee &amp; MT Insurance Programs</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Export-Import Bank of the United States.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Renewal submission for OMB review and Final comments request.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Export-Import Bank of the United States (EXIM Bank), as 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. EXIM Bank's borrowers, financial institution policy holders and guaranteed lenders provide this form to U.S. exporters, who certify to the eligibility of their exports for Ex-Im 
                        <PRTPAGE P="62409"/>
                        Bank support. For direct loans and loan guarantees, the completed form is required to be submitted at time of disbursement and held by either the guaranteed lender or EXIM Bank. For MT insurance, the completed forms are held by the financial institution, only to be submitted to Ex-Im Bank in the event of a claim filing. EXIM Bank uses the referenced form to obtain exporter certifications regarding the export transaction, content sourcing, and their eligibility to participate in USG programs with respect to co-financed transactions. These details are necessary to determine the value and legitimacy of EXIM Bank financing support and claims submitted. It also provides the financial institutions a check on the export transaction's eligibility at the time it is fulfilling a financing request. The information collection tool can be reviewed at: 
                        <E T="03">http://www.exim.gov/sites/default/files/pub/pending/eib15-04.pdf</E>
                        .
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before November 14, 2022 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments may be submitted electronically on 
                        <E T="03">WWW.REGULATIONS.GOV</E>
                         or by mail to Office of Information and Regulatory Affairs, 725 17th Street NW, Washington, DC 20038 Attn: OMB 3048-0052 EIB15-04.
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <P>
                    <E T="03">Title and Form Number:</E>
                     EIB 15-04 Exporter's Certificate for Co-Financing Transactions.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     3048-0052.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Regular.
                </P>
                <P>
                    <E T="03">Need and Use:</E>
                     The information collected will allow EXIM Bank to determine compliance and content for transaction requests submitted to EXIM Bank under its co-financed insurance and guarantee programs.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                </P>
                <P>This form affects entities involved in the export of U.S. goods and services.</P>
                <P>
                    <E T="03">Annual Number of Respondents:</E>
                     30.
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     30 minutes.
                </P>
                <P>
                    <E T="03">Annual Burden Hours:</E>
                     15 hours.
                </P>
                <P>
                    <E T="03">Frequency of Reporting of Use:</E>
                     As required.
                </P>
                <P>
                    <E T="03">Government Expenses:</E>
                </P>
                <P>
                    <E T="03">Reviewing time per year:</E>
                     2.5 hours.
                </P>
                <P>
                    <E T="03">Average Wages per Hour:</E>
                     $42.50.
                </P>
                <P>
                    <E T="03">Average Cost per Year:</E>
                     $106.25 (time*wages).
                </P>
                <P>
                    <E T="03">Benefits and Overhead:</E>
                     20%.
                </P>
                <P>
                    <E T="03">Total Government Cost:</E>
                     $127.50.
                </P>
                <SIG>
                    <NAME>Andy Chang,</NAME>
                    <TITLE>Director, IT Records Management.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22323 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6690-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">EXPORT-IMPORT BANK</AGENCY>
                <DEPDOC>[Public Notice: 2021-3031]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Comment Request; Form Title: EIB 03-02 Application for Medium Term Insurance, Direct Loan or Guarantee</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 final comments request.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Export-Import Bank of the United States (EXIM), 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. The purpose of this collection is to gather information necessary to make a determination of eligibility of a transaction for EXIM assistance under its medium-term guarantee and insurance program.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments should be received on or before November 14, 2022 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments may be submitted electronically on 
                        <E T="03">WWW.REGULATIONS.GOV</E>
                         (EIB 03-02) or by mail to Office of Information and Regulatory Affairs, 725 17th Street NW, Washington, DC 20038, Ave. NW Washington, DC The application tool can be reviewed at: 
                        <E T="03">http://www.exim.gov/sites/default/files/pub/pending/eib03-02_0.pdf.</E>
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <P>
                    <E T="03">Titles and Form Number:</E>
                     EIB 03-02 Application for Medium Term Insurance, Direct Loan or Guarantee.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     3048-0014.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Update &amp; Renewal.
                </P>
                <P>
                    <E T="03">Need and Use:</E>
                     The purpose of this collection is to gather information necessary to make a determination of eligibility of a transaction for EXIM assistance under its medium-term guarantee and insurance program.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                </P>
                <P>This form affects entities involved in the export of U.S. goods and services.</P>
                <P>
                    <E T="03">Annual Number of Respondents:</E>
                     200.
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     2 hours.
                </P>
                <P>
                    <E T="03">Annual Burden Hours:</E>
                     400 hours.
                </P>
                <P>
                    <E T="03">Frequency of Reporting or Use:</E>
                     As needed.
                </P>
                <P>
                    <E T="03">Government Expenses:</E>
                </P>
                <P>
                    <E T="03">Reviewing Time per Year:</E>
                     200 hours.
                </P>
                <P>
                    <E T="03">Average Wages per Hour:</E>
                     $42.50.
                </P>
                <P>
                    <E T="03">Average Cost per Year:</E>
                     $8,500 (time*wages).
                </P>
                <P>
                    <E T="03">Benefits and Overhead:</E>
                     20%.
                </P>
                <P>
                    <E T="03">Total Government Cost:</E>
                     $10,200.
                </P>
                <SIG>
                    <NAME>Andy Chang,</NAME>
                    <TITLE>Director, IT Records Management.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22325 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6690-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">EXPORT-IMPORT BANK</AGENCY>
                <DEPDOC>[Public Notice: 2022-3030]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Comment Request; Form Title: EIB 12-02 Credit Guarantee Facility Disbursement Approval 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>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Export-Import Bank of the United States (EXIM Bank), as part of its continuing effort to reduce paperwork and respondent burden, invites the public and other Federal Agencies to comment on the proposed information collection, as required by the Paperwork Reduction Act of 1995. EXIM Bank has an electronic disbursement approval processing system for guaranteed lenders with Credit Guarantee Facilities. After a Credit Guarantee Facility (CGF) has been authorized by EXIM Bank and legal documentation has been completed, the lender will obtain and review the required disbursement documents (
                        <E T="03">e.g.,</E>
                         invoices, bills of lading, Exporter's Certificate, 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 EXIM Bank's online application system (EXIM Online). Using the form, the lender will input key data and request EXIM Bank's approval of the disbursement. EXIM Bank's action (approved or denied) is posted on the lender's history page. The information collected in the questionnaire will assist EXIM Bank in determining that each disbursement under a Medium-Term Guarantee meets all the terms and conditions for approval. The information collection tool can be reviewed at: 
                        <E T="03">http://exim.gov/sites/default/files/pub/pending/eib12-02.pdf.</E>
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before November 14, 2022 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments may be submitted electronically on 
                        <E T="03">WWW.REGULATIONS.GOV</E>
                         or by mail to Office of Information and Regulatory Affairs, 725 17th Street NW, 
                        <PRTPAGE P="62410"/>
                        Washington, DC 20038, Attn: OMB 3048-0046.
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <P>
                    <E T="03">Title and Form Number:</E>
                     EIB 12-02 Credit Guarantee Facility Disbursement Approval Request.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     3048-0046.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Regular.
                </P>
                <P>
                    <E T="03">Need and Use:</E>
                     The information requested enables EXIM Bank to determine that a disbursement under a Credit Guarantee Facility meets all of the terms and conditions for approval.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                </P>
                <P>This form affects lenders involved in the financing of U.S. goods and services exports.</P>
                <P>
                    <E T="03">Annual Number of Respondents:</E>
                     50.
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     60 minutes.
                </P>
                <P>
                    <E T="03">Annual Burden Hours:</E>
                     50 hours.
                </P>
                <P>
                    <E T="03">Frequency of Reporting of Use:</E>
                     Annual.
                </P>
                <P>
                    <E T="03">Government Expenses:</E>
                </P>
                <P>
                    <E T="03">Reviewing time per year:</E>
                     25 hours.
                </P>
                <P>
                    <E T="03">Average Wages per Hour:</E>
                     $42.50.
                </P>
                <P>
                    <E T="03">Average Cost per Year:</E>
                     $1,062.50 (time*wages).
                </P>
                <P>
                    <E T="03">Benefits and Overhead:</E>
                     20%.
                </P>
                <P>
                    <E T="03">Total Government Cost:</E>
                     $1,275.
                </P>
                <SIG>
                    <NAME>Andy Chang,</NAME>
                    <TITLE>Director, IT Records Management.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22326 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6690-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">EXPORT-IMPORT BANK</AGENCY>
                <DEPDOC>[Public Notice 2022-3028]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Final Collection; Comment Request; Form Title: EIB 09-01 Payment Default Report OMB 3048-0028</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Export-Import Bank of the U.S.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Submission for OMB review and comments request.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Export-Import Bank of the United States (EXIM), as a part of its continuing effort to reduce paperwork and respondent burden, invites the public and other Federal Agencies to comment on the proposed information collection, as required by the Paperwork Reduction Act of 1995. This collection allows insured/guaranteed parties and insurance brokers to report overdue payments from the borrower and/or guarantor. To facilitate completion, the form includes many checkboxes and self-populating fields. Also, customers can submit it electronically through EXIM Online, replacing paper reporting. EXIM provides insurance, loans, and loan guarantees for the financing of exports of goods and services. The form can be viewed at: 
                        <E T="03">https://www.exim.gov/sites/default/files//forms/eib09-01_0.pdf</E>
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments should be received on or before November 14, 2022 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments may be submitted electronically on 
                        <E T="03">WWW.REGULATIONS.GOV</E>
                         or by mail to Office of Information and Regulatory Affairs, 725 17th Street NW, Washington, DC 20038, Attn: OMB 3048-0049.
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    <E T="03">Titles and Form Number:</E>
                     EIB 09-01, Payment Default Report.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     3048-0028.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Regular.
                </P>
                <P>
                    <E T="03">Need and Use:</E>
                     The information requested enables insured/guaranteed parties and insurance brokers to report overdue payments from the borrower and/or guarantor.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                </P>
                <P>This form affects Insured/guaranteed parties and brokers.</P>
                <P>
                    <E T="03">Annual Number of Respondents:</E>
                     500.
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     15 minutes.
                </P>
                <P>
                    <E T="03">Annual Burden Hours:</E>
                     125 hours.
                </P>
                <P>
                    <E T="03">Frequency of Reporting of Use:</E>
                     Annual.
                </P>
                <P>
                    <E T="03">Government Expenses:</E>
                </P>
                <P>
                    <E T="03">Reviewing time per year:</E>
                     8.3 hours.
                </P>
                <P>
                    <E T="03">Average Wages per Hour:</E>
                     $42.50.
                </P>
                <P>
                    <E T="03">Average Cost per Year:</E>
                     $354.02. (time*wages)
                </P>
                <P>
                    <E T="03">Benefits and Overhead:</E>
                     20%.
                </P>
                <P>
                    <E T="03">Total Government Cost:</E>
                     $424.83.
                </P>
                <SIG>
                    <NAME>Andy Chang,</NAME>
                    <TITLE>Director, IT Records Management.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22327 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6690-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <DEPDOC>[OMB 3060-1265; FR ID 108662]</DEPDOC>
                <SUBJECT>Information Collection Being Submitted for Review and Approval to Office of Management and Budget</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>As part of its continuing effort to reduce paperwork burdens, as required by the Paperwork Reduction Act (PRA) of 1995, the Federal Communications Commission (FCC or the Commission) invites the general public and other Federal Agencies to take this opportunity to comment on the following information collection. Pursuant to the Small Business Paperwork Relief Act of 2002, the FCC seeks specific comment on how it might “further reduce the information collection burden for small business concerns with fewer than 25 employees.” The Commission may not conduct or sponsor a collection of information unless it displays a currently valid Office of Management and Budget (OMB) control number. No person shall be subject to any penalty for failing to comply with a collection of information subject to the PRA that does not display a valid OMB control number.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments and recommendations for the proposed information collection should be submitted on or before November 14, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments should be sent to 
                        <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                         Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function. Your comment must be submitted into 
                        <E T="03">www.reginfo.gov</E>
                         per the above instructions for it to be considered. In addition to submitting in 
                        <E T="03">www.reginfo.gov</E>
                         also send a copy of your comment on the proposed information collection to Nicole Ongele, FCC, via email to 
                        <E T="03">PRA@fcc.gov</E>
                         and to 
                        <E T="03">Nicole.Ongele@fcc.gov.</E>
                         Include in the comments the OMB control number as shown in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         below.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For additional information or copies of the information collection, contact Nicole Ongele at (202) 418-2991. To view a copy of this information collection request (ICR) submitted to OMB: (1) go to the web page 
                        <E T="03">https://www.reginfo.gov/public/do/PRAMain,</E>
                         (2) look for the section of the web page called “Currently Under Review,” (3) click on the downward-pointing arrow in the “Select Agency” box below the “Currently Under Review” heading, (4) select “Federal Communications Commission” from the list of agencies presented in the “Select Agency” box, (5) click the “Submit” button to the right of the “Select Agency” box, (6) when the list of FCC ICRs currently under review appears, look for the Title of this ICR and then click on the ICR Reference Number. A copy of the FCC submission to OMB will be displayed.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    As part of its continuing effort to reduce paperwork burdens, as required by the Paperwork Reduction Act (PRA) of 1995 (44 U.S.C. 3501-3520), the FCC invited the general public and other Federal 
                    <PRTPAGE P="62411"/>
                    Agencies to take this opportunity to comment on the following information collection. Comments are requested concerning: (a) Whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; (b) the accuracy of the Commission's burden estimates; (c) ways to enhance the quality, utility, and clarity of the information collected; and (d) ways to minimize the burden of the collection of information on the respondents, including the use of automated collection techniques or other forms of information technology. Pursuant to the Small Business Paperwork Relief Act of 2002, Public Law 107-198, see 44 U.S.C. 3506(c)(4), the FCC seeks specific comment on how it might “further reduce the information collection burden for small business concerns with fewer than 25 employees.”
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3060-1265. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Connect America Fund—Performance Testing Measures. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     N/A.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit. 
                </P>
                <P>
                    <E T="03">Number of Respondents and Responses:</E>
                     1,677 unique respondents; 4,196 responses. 
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     16 hours—60 hours. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Biennial reporting requirements, quarterly reporting requirements and annual reporting requirements. 
                </P>
                <P>
                    <E T="03">Obligation to Respond:</E>
                     Required to obtain or retain benefits. Statutory authority for this information collection is contained in 47 U.S.C. 151-154, 155, 201-206, 214, 218-220, 251, 252, 254, 256, 303(r), 332, 403, 405, 410, and 1302. 
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     164,526 hours. 
                </P>
                <P>
                    <E T="03">Total Annual Cost:</E>
                     No Cost.
                </P>
                <P>
                    <E T="03">Privacy Act Impact Assessment:</E>
                     No impact(s).
                </P>
                <P>
                    <E T="03">Nature and Extent of Confidentiality:</E>
                     We note that the Universal Service Administrative Company (USAC) must preserve the confidentiality of certain data obtained from respondents; must not use the data except for purposes of administering the universal service programs or other purposes specified by the Commission; and must not disclose data in company-specific form unless directed to do so by the Commission. Materials or information submitted to the Commission or the Administrator will be confidential and not be available to the public.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     In the 
                    <E T="03">USF/ICC Transformation Order,</E>
                     the Commission laid the groundwork for today's universal service programs providing $4.5 billion in support for broadband internet deployment in high-cost areas. 
                    <E T="03">Connect America Fund, et al.,</E>
                     Report and Order and Further Notice of Proposed Rulemaking, WC Docket No. 10-90, et al., 26 FCC Rcd 17663 (2011) (
                    <E T="03">USF/ICC Transformation Order</E>
                    ). The 
                    <E T="03">USF/ICC Transformation Order</E>
                     required, among other things, that high-cost universal service recipients “test their broadband networks for compliance with speed and latency metrics and certify to and report the results to the Universal Service Administrative Company (USAC) on an annual basis.” 
                    <E T="03">Id.</E>
                     at 17705, para. 109. Pursuant to the Commission's direction in that Order, the Wireline Competition Bureau, the Wireless Telecommunications Bureau, and the Office of Engineering and Technology (the Bureaus and OET) adopted more specific methodologies for such testing in the 
                    <E T="03">Performance Measures Order. See generally Performance Measures Order. See also</E>
                     47 CFR 54.313(a)(6) (requiring that recipients of high-cost support provide “[t]he results of network performance tests pursuant to the methodology and in the format determined by the Wireline Competition Bureau, Wireless Telecommunications Bureau, and Office of Engineering and Technology”).
                </P>
                <P>
                    This collection includes requirements for testing speed and latency to ensure that carriers are meeting the public interest obligations associated with their receipt of high-cost universal service support. Carriers will identify, from among the locations they have already submitted and certified in USAC's High Cost Universal Broadband (HUBB) portal, the locations where they have an active subscriber (deployment locations are reported under OMB Control Number 3060-1228, and active locations will be reported under this control number). From those subscriber locations, USAC will then select a random sample from which the carrier will be required to perform testing for speed and latency. Carriers that do not provide location information in the HUBB will use a randomization tool provided by USAC to select a random sample of locations for testing. The carrier will then be required to submit to USAC the results of the testing on an annual basis. The annual filing will include the testing results for each quarter from the prior year. The carrier's sample for each service tier (
                    <E T="03">e.g.</E>
                     10 Mbps/1 Mbps, 25 Mbps/1 Mbps) shall be regenerated every two years. During the two-year cycle, carriers will have the ability to add and remove subscriber locations if necessary, 
                    <E T="03">e.g.,</E>
                     as subscribership changes. This information collection addresses the burdens associated with these requirements.
                </P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Marlene Dortch,</NAME>
                    <TITLE>Secretary, Office of the Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22373 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <DEPDOC>[OMB 3060-1238; FR ID 109145]</DEPDOC>
                <SUBJECT>Information Collection Being Reviewed by the Federal Communications Commission Under Delegated Authority</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>As part of its continuing effort to reduce paperwork burdens, and as required by the Paperwork Reduction Act of 1995 (PRA), the Federal Communications Commission (FCC or Commission) invites the general public and other Federal agencies to take this opportunity to comment on the following information collections. Comments are requested concerning: whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; the accuracy of the Commission's burden estimate; ways to enhance the quality, utility, and clarity of the information collected; ways to minimize the burden of the collection of information on the respondents, including the use of automated collection techniques or other forms of information technology; and ways to further reduce the information collection burden on small business concerns with fewer than 25 employees. The FCC may not conduct or sponsor a collection of information unless it displays a currently valid Office of Management and Budget (OMB) control number. No person shall be subject to any penalty for failing to comply with a collection of information subject to the PRA that does not display a valid OMB control number.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Written comments shall be submitted on or before December 13, 2022. If you anticipate that you will be 
                        <PRTPAGE P="62412"/>
                        submitting comments but find it difficult to do so within the period of time allowed by this notice, you should advise the contacts below as soon as possible.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all PRA comments to Cathy Williams, FCC, via email: 
                        <E T="03">PRA@fcc.gov</E>
                         and to 
                        <E T="03">Cathy.Williams@fcc.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For additional information about the information collection, contact Cathy Williams at (202) 418-2918.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3060-1238.
                </P>
                <P>
                    <E T="03">Title:</E>
                     First Amendment to Nationwide Programmatic Agreement for the Collocation of Wireless Antennas.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     Not applicable.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of an approved collection.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit entities, not-for-profit institutions, and State, local, or Tribal governments.
                </P>
                <P>
                    <E T="03">Number of Respondents and Responses:</E>
                     71 respondents; 765 responses.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     1 hour-5 hours.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Third party disclosure reporting requirement.
                </P>
                <P>
                    <E T="03">Obligation to Respond:</E>
                     Required to obtain or retain benefits. Statutory authority for this information collection is contained in Sections 1, 2, 4(i), 7, 301, 303, 309, and 332 of the Communications Act of 1934, as amended, 47 U.S.C. 151, 152, 154(i), 157, 301, 303, 309, 332, and Section 106 of the National Historic Preservation Act of 1966, 54 U.S.C. 306108.
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     2,869 hours.
                </P>
                <P>
                    <E T="03">Total Annual Cost:</E>
                     $82,285.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     The Commission will submit this information collection for approval after the comment period to obtain the full three-year clearance from the Office of Management and Budget (OMB). The Commission is requesting OMB approval for disclosure requirements pertaining to the 
                    <E T="03">First Amendment to Nationwide Programmatic Agreement for the Collocation of Wireless Antennas</E>
                     (First Amendment) to address the review of deployments of small wireless antennas and associated equipment under section 106 of the National Historic Preservation Act (NHPA) (54 U.S.C. 306108 (formerly codified at 16 U.S.C. 470f). The FCC, the Advisory Council on Historic Preservation (Council), and the National Conference of State Historic Preservation Officers (NCSHPO) amended the 
                    <E T="03">Nationwide Programmatic Agreement for the Collocation of Wireless Antennas</E>
                     (Collocation Agreement) to account for the limited potential of small wireless antennas and associated equipment, including Distributed Antenna Systems (DAS) and small cell facilities, to affect historic properties. The Collocation Agreement addresses historic preservation review for collocations on existing towers, buildings, and other non-tower structures. Under the Collocation Agreement, most antenna collocations on existing structures are excluded from Section 106 historic preservation review, with a few exceptions defined to address potentially problematic situations. On August 3, 2016, the Commission's Wireless Telecommunications Bureau, ACHP, and NCSHPO finalized and executed the First Amendment to the Collocation Agreement, to tailor the Section 106 process for small wireless deployments by excluding deployments that have minimal potential for adverse effects on historic properties.
                </P>
                <P>The following are the information collection requirements in connection with the amended provisions of appendix B of part 1 of the Commission's rules (47 CFR part 1, app. B):</P>
                <P>
                    • Stipulation VII.C of the amended Collocation Agreement provides that proposals to mount a small antenna on a traffic control structure (
                    <E T="03">i.e.,</E>
                     traffic light) or on a light pole, lamp post or other structure whose primary purpose is to provide public lighting, where the structure is located inside or within 250 feet of the boundary of a historic district, are generally subject to review through the section 106 process. These proposed collocations will be excluded from such review on a case-by-case basis, if (1) the collocation licensee or the owner of the structure has not received written or electronic notification that the FCC is in receipt of a complaint from a member of the public, an Indian Tribe, a SHPO or the Council, that the collocation has an adverse effect on one or more historic properties; and (2) the structure is not historic (not a designated National Historic Landmark or a property listed in or eligible for listing in the National Register of Historic Places) or considered a contributing or compatible element within the historic district, under certain procedures. These procedures require that applicant must request in writing that the SHPO concur with the applicant's determination that the structure is not a contributing or compatible element within the historic district, and the applicant's written request must specify the traffic control structure, light pole, or lamp post on which the applicant proposes to collocate and explain why the structure is not a contributing element based on the age and type of structure, as well as other relevant factors. The SHPO has thirty days from its receipt of such written notice to inform the applicant whether it disagrees with the applicant's determination that the structure is not a contributing or compatible element within the historic district. If within the thirty-day period, the SHPO informs the applicant that the structure is a contributing element or compatible element within the historic district or that the applicant has not provided sufficient information for a determination, the applicant may not deploy its facilities on that structure without completing the section 106 review process. If, within the thirty-day period, the SHPO either informs the applicant that the structure is not a contributing or compatible element within the historic district, or the SHPO fails to respond to the applicant within the thirty-day period, the applicant has no further Section 106 review obligations, provided that the collocation meets the certain volumetric and ground disturbance provisions.
                </P>
                <P>
                    The First Amendment to the Collocation Agreement established new exclusions from the Section 106 review process for physically small deployments like DAS and small cells, fulfilling a directive in the Commission's 
                    <E T="03">Infrastructure Report and Order,</E>
                     80 FR 1238, Jan. 8, 2015, to further streamline review of these installations. These exclusions will continue to reduce the cost, time, and burden associated with deploying small facilities in many settings and provide opportunities to increase densification at low cost and with very little impact on historic properties.
                </P>
                <P>Facilitating these deployments thus directly advances efforts to roll out 5G service in communities across the country.</P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Marlene Dortch,</NAME>
                    <TITLE>Secretary, Office of the Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22385 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <DEPDOC>[OMB 3060-1238; FR ID 109146]</DEPDOC>
                <SUBJECT>Information Collection Being Reviewed by the Federal Communications Commission Under Delegated Authority</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <PRTPAGE P="62413"/>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>As part of its continuing effort to reduce paperwork burdens, and as required by the Paperwork Reduction Act of 1995 (PRA), the Federal Communications Commission (FCC or Commission) invites the general public and other Federal agencies to take this opportunity to comment on the following information collections. Comments are requested concerning: whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; the accuracy of the Commission's burden estimate; ways to enhance the quality, utility, and clarity of the information collected; ways to minimize the burden of the collection of information on the respondents, including the use of automated collection techniques or other forms of information technology; and ways to further reduce the information collection burden on small business concerns with fewer than 25 employees. The FCC may not conduct or sponsor a collection of information unless it displays a currently valid Office of Management and Budget (OMB) control number. No person shall be subject to any penalty for failing to comply with a collection of information subject to the PRA that does not display a valid OMB control number.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments shall be submitted on or before December 13, 2022. If you anticipate that you will be submitting comments but find it difficult to do so within the period of time allowed by this notice, you should advise the contacts below as soon as possible.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all PRA comments to Cathy Williams, FCC, via email: 
                        <E T="03">PRA@fcc.gov</E>
                         and to 
                        <E T="03">Cathy.Williams@fcc.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For additional information about the information collection, contact Cathy Williams at (202) 418-2918.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <P>
                    <E T="03">OMB Control No.:</E>
                     3060-0695.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Section 87.219, Automatic Operations.
                </P>
                <P>
                    <E T="03">Form No.:</E>
                     N/A.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit entities.
                </P>
                <P>
                    <E T="03">Number of Respondents and Responses:</E>
                     55 respondents and 55 responses.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     0.7 hours.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion reporting requirement, recordkeeping requirement, and third party disclosure requirement.
                </P>
                <P>
                    <E T="03">Obligation to Respond:</E>
                     Required to obtain or retain benefits. The statutory authority for this collection of information is contained in 47 U.S.C. 154, 303 and 307.
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     39 hours.
                </P>
                <P>
                    <E T="03">Annual Cost Burden:</E>
                     $8,250.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     If airports have control towers of Federal Aviation Administration (FAA) flight service stations and more than one licensee, and wants to have an automated aeronautical advisory station (Unicom), this rule requires that they must write an agreement and keep a copy of the agreement with each licensee's station authorization. This information will be used by compliance personnel for enforcement purposes and by licensees to clarify responsibility in operating Unicom.
                </P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Marlene Dortch,</NAME>
                    <TITLE>Secretary, Office of the Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22382 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL DEPOSIT INSURANCE CORPORATION</AGENCY>
                <SUBJECT>Sunshine Act Meeting</SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">TIME AND DATE: </HD>
                    <P>10 a.m. on Tuesday, October 18, 2022.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PLACE: </HD>
                    <P>
                        The meeting is open to the public. Out of an abundance of caution related to current and potential coronavirus developments, the public's means to observe this Board meeting will be via a Webcast live on the internet and subsequently made available on-demand approximately one week after the event. Visit 
                        <E T="03">https://youtu.be/s7moPsvjKto</E>
                         to view the meeting. If you need any technical assistance, please visit our Video Help page at: 
                        <E T="03">https://www.fdic.gov/video.html.</E>
                    </P>
                    <P>
                        Observers requiring auxiliary aids (
                        <E T="03">e.g.,</E>
                         sign language interpretation) for this meeting should email 
                        <E T="03">DisabilityProgram@fdic.gov</E>
                         to make necessary arrangements.
                    </P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">STATUS: </HD>
                    <P>Open.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">MATTER TO BE CONSIDERED:</HD>
                    <P> Pursuant to the provisions of the “Government in the Sunshine Act” (5 U.S.C. 552b), notice is hereby given that the Federal Deposit Insurance Corporation's Board of Directors will meet in open session to consider the following matters:</P>
                </PREAMHD>
                <HD SOURCE="HD1">Summary Agenda</HD>
                <P>No substantive discussion of the following items is anticipated. These matters will be resolved with a single vote unless a member of the Board of Directors requests that an item be moved to the discussion agenda.</P>
                <P>Disposition of Minutes of a Board of Directors' Meeting Previously Distributed.</P>
                <P>Memorandum and resolution re: Final Rule on Assessments—Amendments to Incorporate Troubled Debt Restructuring Accounting Standards Update.</P>
                <P>Memorandum and resolution re: Designated Reserve Ratio for 2023.</P>
                <P>Summary report of actions taken pursuant to authority delegated by the Board of Directors.</P>
                <HD SOURCE="HD1">Discussion Agenda</HD>
                <P>Memorandum and resolution re: Final Rule on Assessments, Revised Deposit Insurance Assessment Rates.</P>
                <P>Memorandum and resolution re: Proposed Amendments to the Guidelines for Appeals of Material Supervisory Determinations.</P>
                <PREAMHD>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION: </HD>
                    <P>Requests for further information concerning the meeting may be directed to Debra A. Decker, Executive Secretary of the Corporation, at 202-898-8748.</P>
                </PREAMHD>
                <SIG>
                    <DATED>Dated at Washington, DC, on October 11, 2022.</DATED>
                    <FP>Federal Deposit Insurance Corporation.</FP>
                    <NAME>James P. Sheesley,</NAME>
                    <TITLE>Assistant Executive Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22434 Filed 10-12-22; 11:15 am]</FRDOC>
            <BILCOD>BILLING CODE 6714-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention</SUBAGY>
                <DEPDOC>[Docket No. CDC-2022-0014]</DEPDOC>
                <SUBJECT>Notice of Availability of the Final Supplemental Environmental Impact Statement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Disease Control and Prevention (CDC), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Centers for Disease Control and Prevention (CDC) within the Department of Health and Human Services (HHS) announces the availability of the Final Supplemental Environmental Impact Statement (SEIS) for CDC's Roybal Campus in Atlanta, Georgia. The Final SEIS was prepared to address changes proposed since completing the 2014 Final Environmental Impact Statement (EIS) for the CDC Roybal Campus 2025 Master Plan (2014 Final EIS) and issuing a 
                        <PRTPAGE P="62414"/>
                        Record of Decision (ROD) dated November 7, 2014. This announcement follows the requirements of the National Environmental Policy Act (NEPA) as implemented by the Council on Environmental Quality (CEQ) regulations and HHS environmental procedures.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The Final SEIS will be available October 14, 2022.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Thayra Riley, NEPA Coordinator, Office of Safety, Security, and Asset Management, Centers for Disease Control and Prevention, 1600 Clifton Road NE, Mailstop H20-4, Atlanta, Georgia 30329. Email: 
                        <E T="03">cdc-roybalga-seis@cdc.gov.</E>
                         Telephone: 770-488-8170.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In accordance with NEPA as implemented by CEQ regulations (40 CFR 1507.3) and HHS environmental procedures, CDC prepared a Final SEIS to analyze the effects of additional proposed components that were not analyzed in the 2014 Final EIS. The potential impacts of construction and operation of these components on the natural and built environment were evaluated.</P>
                <HD SOURCE="HD1">Alternatives Considered</HD>
                <P>CDC analyzed two alternatives in the Final SEIS: The Proposed Action (Alternative 1) and the No Action Alternative. Alternative 1 consists of the construction and operation of a Hospital, Medical, and Infectious Waste Incinerator (HMIWI) in a new laboratory building and the operation of two emergency standby power diesel generators. The construction of a new laboratory was included in the 2014 Final EIS and was not re-evaluated in the SEIS. The No Action Alternative consists of the construction of the new laboratory without the HMIWI and two emergency standby power generators.</P>
                <P>The Final SEIS evaluates the environmental impacts that may result from Alternative 1 and the No Action Alternative on the following resource categories: air quality, climate change and sustainability, environmental justice, and hazardous/medical/infectious waste. The Final SEIS identifies measures to mitigate potential adverse impacts.</P>
                <HD SOURCE="HD1">Public Involvement</HD>
                <P>
                    On January 28, 2022, CDC published a Notice of Intent to prepare a SEIS in the 
                    <E T="04">Federal Register</E>
                     (87 FR 4603). CDC announced a Notice of Availability (NOA) of the Draft SEIS on July 8, 2022 (87 FR 40844) and the public comment period ended August 22, 2022. During the public comment period, a virtual public meeting was held on July 27, 2022. Two participants attended the meeting.
                </P>
                <P>CDC received five public comments.</P>
                <P>• An individual submitted two comments stating they did not agree with the spending associated with the project.</P>
                <P>○ CDC acknowledges the comment.</P>
                <P>• A civic organization submitted one comment asking about noise or odors associated with lab operations and the stringency of the Georgia Department of Natural Resources, Environmental Protection Department (EPD) rules for handling, treating, and disposing of infectious waste.</P>
                <P>○ CDC's response is that noise and odors were determined not to be issues that needed to be included in the SEIS associated with the addition of a new HMIWI and two new emergency standby power generators. Noise levels will not be an issue and will be controlled/limited to levels below Occupational Safety and Health Administration criteria (60 dBA within 4 feet, which is a normal speaking level). No odors will be released from the new incinerator system during operations. The Georgia EPD rules for handling, treating, and disposing of infectious waste are sufficiently stringent and protective of the environment, workers, and public health. CDC has been operating other incinerators on site and the handling of solid waste, including hazardous and medical waste, will continue to comply with Georgia EPD rules and regulations.</P>
                <P>• A community advisory group submitted a request for CDC to present an update on the SEIS during the group's September 20, 2022 meeting.</P>
                <P>○ CDC declined the request and provided instructions to submit comments on the docket.</P>
                <P>• An individual submitted questions about the air quality modeling and cumulative impact analysis.</P>
                <P>○ For the analysis of the addition of the HMIWI and two emergency generators, CDC conducted a quantitative analysis of carbon monoxide based on the methodology used during the 2014 Final EIS. The SEIS states that further analysis of the criteria pollutants and hazardous air pollutants would be conducted to support the updated Title V operating permit that is required due to the addition of the HMIWI. Cumulative impacts for the overall implementation of the Roybal Campus 2025 Master Plan were included in the 2014 Final FEIS. Cumulative impacts were considered in the SEIS Air Quality and climate change analysis. Since there are no impacts to environmental justice and negligible impacts to hazardous, medical, infectious waste, these would not contribute to significant cumulative impacts.</P>
                <P>CDC made minor revisions to the SEIS based on these comments. The comments and CDC's responses are included in Appendix A of the Final SEIS.</P>
                <P>
                    <E T="03">Availability of the Final SEIS:</E>
                     The Final SEIS is available in the Supplemental Materials tab of the docket found on the Federal eRulemaking Portal: 
                    <E T="03">https://www.regulations.gov,</E>
                     identified by Docket No. CDC-2022-0014.
                </P>
                <P>
                    The NOA of the Final SEIS has been provided to Federal, State, and local agencies and organizations via mail and electronic mail to the interested parties list. The public is being notified of the availability of the Final SEIS through this 
                    <E T="04">Federal Register</E>
                     publication and a notice published in 
                    <E T="03">The Atlanta Journal-Constitution.</E>
                     CDC will finalize a ROD no sooner than November 7, 2022.
                </P>
                <SIG>
                    <NAME>Angela K. Oliver,</NAME>
                    <TITLE>Executive Secretary, Centers for Disease Control and Prevention.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22370 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4163-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2019-N-0305]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Submission for Office of Management and Budget Review; Comment Request; Tobacco Products Subject to the Federal Food, Drug, and Cosmetic Act</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA) is announcing that a proposed collection of information has been submitted to the Office of Management and Budget (OMB) for review and clearance under the Paperwork Reduction Act of 1995.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit written comments (including recommendations) on the collection of information by November 14, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        To ensure that comments on the information collection are received, OMB recommends that written comments be submitted to 
                        <E T="03">https://www.reginfo.gov/public/do/PRAMain.</E>
                         Find this particular information collection by selecting “Currently under 
                        <PRTPAGE P="62415"/>
                        Review—Open for Public Comments” or by using the search function. The OMB control number for this information collection is 0910-0768. Also include the FDA docket number found in brackets in the heading of this document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Domini Bean, Office of Operations, Food and Drug Administration, Three White Flint North, 10A-12M, 11601 Landsdown St., North Bethesda, MD 20852, 301-796-5733, 
                        <E T="03">PRAStaff@fda.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In compliance with 44 U.S.C. 3507, FDA has submitted the following proposed collection of information to OMB for review and clearance.</P>
                <HD SOURCE="HD1">Tobacco Products Subject to the Federal Food, Drug, and Cosmetic Act</HD>
                <HD SOURCE="HD2">OMB Control Number 0910-0768—Extension</HD>
                <P>Tobacco products are governed by chapter IX of the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) (sections 900 through 920) (21 U.S.C. 387 through 21 U.S.C. 387t). Implementing regulations are found in 21 CFR subchapter K (parts 1100 through 1150 (21 CFR parts 1100 through 1150)). This information collection supports the reporting, recordkeeping, and third-party disclosure requirements associated with statutory requirements applicable to tobacco products and set forth in Agency regulations. Section 910(a)(1) of the FD&amp;C Act defines a “new tobacco product” as a tobacco product that was not commercially marketed in the United States on February 15, 2007, or a modification (including a change in design, any component, any part, or any constituent, including a smoke constituent, or in the content, delivery, or form of nicotine, or any other additive or ingredient) of a tobacco product where the modified product was commercially marketed in the United States after February 15, 2007. An order under section 910(c)(1)(A)(i) of the FD&amp;C Act is required prior to marketing a new tobacco product. This requirement applies unless the product has been shown to be substantially equivalent to a valid predicate product or is exempt from substantial equivalence (21 CFR 1107.1).</P>
                <P>Section 910(b) of the FD&amp;C Act states that a premarket tobacco application (PMTA) (part 1114) shall contain full reports of all investigations of health risks; a full statement of all components, ingredients, additives, and properties, and of the principle or principles of operation of such tobacco product; a full description of methods of manufacturing and processing (which includes a listing of all manufacturing, packaging, and control sites for the product); an explanation of how the product complies with applicable tobacco product standards; samples of the product and its components; and labeling.</P>
                <P>
                    FDA also encourages persons who would like to study their new tobacco product to meet with the Office of Science (OS) in the Center for Tobacco Products (CTP) to discuss their investigational plan. The request for a meeting should be sent in writing to the Director of CTP's Office of Science and should include adequate information for FDA to assess the potential utility of the meeting and to identify FDA staff necessary to discuss agenda items. Details regarding the process for requesting a meeting with OS and how FDA will respond may be found at 
                    <E T="03">https://www.fda.gov/regulatory-information/search-fda-guidance-documents/meetings-industry-and-investigators-research-and-development-tobacco-products.</E>
                </P>
                <P>FDA efforts regarding issuance of a final guidance for Harmful and Potentially Harmful Constituent reporting (and later a testing and reporting regulation under section 915 of the FD&amp;C Act) is ongoing, and the guidance document will be issued consistent with our good guidance practice regulations found in 21 CFR 10.115, which provide for public comment at any time.</P>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of April 28, 2022 (87 FR 25280) we published a 60-day notice requesting public comment on the proposed collection of information. No comments were received.
                </P>
                <P>We estimate the burden of this collection of information as follows:</P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s100,12,12,12,12,12">
                    <TTITLE>
                        Table 1—Estimated Annual Reporting Burden 
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">Activity</CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>responses per respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual 
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">
                            Average 
                            <LI>burden per </LI>
                            <LI>response </LI>
                            <LI>(in hours)</LI>
                        </CHED>
                        <CHED H="1">Total hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Obtaining an FDA Order Authorizing Marketing of Tobacco Product (PMTA application) and 21 CFR 25.40 Environmental Assessments</ENT>
                        <ENT>200</ENT>
                        <ENT>3.75</ENT>
                        <ENT>750</ENT>
                        <ENT>1,713</ENT>
                        <ENT>1,284,750</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Request for Meeting with CTP's Office of Science to Discuss Investigational Plan</ENT>
                        <ENT>27</ENT>
                        <ENT>1</ENT>
                        <ENT>27</ENT>
                        <ENT>10</ENT>
                        <ENT>270</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">21 CFR part 1143 Cigar Warning Plans</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>1,285,021</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         There are no capital costs or operating and maintenance costs associated with this collection of information.
                    </TNOTE>
                </GPOTABLE>
                <P>
                    FDA estimates an average burden per respondent of 1,500 hours to prepare a PMTA seeking an order from FDA allowing the marketing of a new tobacco product. We assume, on average, an additional 213 hours is necessary to prepare an environmental assessment in accordance with the requirements of 21 CFR 25.40, for a total of 1,713 hours per PMTA application. This average represents a wide range of hours that will be required for these applications under different circumstances, with a small number requiring more hours (
                    <E T="03">e.g.,</E>
                     as many as 5,000 hours for early applications that involve complex products and for which the company has no experience conducting studies or preparing analysis of public health impacts, or for which reliance on master files is not possible) as well as many requiring fewer hours (
                    <E T="03">e.g.,</E>
                     as few as 50 hours for applications for products that are very similar to other new products). A PMTA may require one or more types of studies including chemical analysis, nonclinical studies, and clinical studies. FDA also estimates the number of PMTAs that FDA expects to receive annually will be 750 (642 electronic nicotine delivery systems (ENDS) Liquids and 108 ENDS Delivery Systems).
                    <PRTPAGE P="62416"/>
                </P>
                <P>FDA anticipates that the 27 potential respondents to this collection may need to meet with CTP's Office of Science to discuss their investigational plans. This number has been reduced based on the average number of meeting requests received over the past 3 years. To request this meeting, applicants should compile and submit information to FDA for meeting approval. FDA estimates that it will take approximately 270 hours to compile and request a meeting with OS. We have revised the hours per response to be consistent with the meetings information collection for originally regulated products (OMB control number 0910-0731).</P>
                <P>Based on the September 2020 order vacating the health warning requirements for cigars and pipe tobacco (set forth in 21 CFR 1143.3 and 1143.5) and remanding the Final Deeming Rule's warning requirements for cigars and pipe tobacco, we have removed the burden associated with this activity. We have included 1 token hour of burden associated with the requirements in part 1143 to acknowledge that the requirement remains in the regulations.</P>
                <P>We have adjusted our burden estimate, which has resulted in a decrease to the currently approved burden. The total estimated burden for this information collection is 1,285,021 reporting hours and 778 annual responses. Our estimated burden for the information collection reflects an overall decrease of 2,779 hours and a corresponding decrease of 262 responses. We attribute this adjustment to updated information in the number of meeting requests with CTP's Office of Science to discuss investigational plans, the removal of burden for the cigar warning plans, the removal of the small-scale manufacturer reporting, and have therefore revised the estimated burden and number of respondents to the information collection.</P>
                <SIG>
                    <DATED>Dated: October 5, 2022.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22299 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2022-N-2316]</DEPDOC>
                <SUBJECT>Discussion Paper: Distributed Manufacturing and Point-of-Care Manufacturing of Drugs; Request for Information and Comments</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; request for information and comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA or Agency) is announcing publication of a discussion paper providing information for stakeholders and soliciting public comments on specific areas of emerging and advanced manufacturing technologies. The discussion paper presents areas for consideration and policy development identified by the Center for Drug Evaluation and Research (CDER) scientific and policy experts associated with distributed manufacturing (DM) and point-of-care (POC) manufacturing for drugs, including biological products regulated by CDER and the Center for Biologics Evaluation and Research (CBER). FDA recognizes that regulatory policies and programs may need to evolve to enable the timely adoption of these technologies. The discussion paper includes a series of questions for each technology to stimulate feedback from the public.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Either electronic or written comments and information on the discussion paper must be submitted by December 13, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments as follows. Please note that late, untimely filed comments will not be considered. The 
                        <E T="03">https://www.regulations.gov</E>
                         electronic filing system will accept comments until 11:59 p.m. Eastern Time at the end of December 13, 2022. Comments received by mail/hand delivery/courier (for written/paper submissions) will be considered timely if they are received on or before that date.
                    </P>
                </ADD>
                <HD SOURCE="HD2">Electronic Submissions</HD>
                <P>Submit electronic comments in the following way:</P>
                <P>
                    • 
                    <E T="03">Federal eRulemaking Portal: https://www.regulations.gov.</E>
                     Follow the instructions for submitting comments. Comments submitted electronically, including attachments, to 
                    <E T="03">https://www.regulations.gov</E>
                     will be posted to the docket unchanged. Because your comment will be made public, you are solely responsible for ensuring that your comment does not include any confidential information that you or a third party may not wish to be posted, such as medical information, your or anyone else's Social Security number, or confidential business information, such as a manufacturing process. Please note that if you include your name, contact information, or other information that identifies you in the body of your comments, that information will be posted on 
                    <E T="03">https://www.regulations.gov.</E>
                </P>
                <P>• If you want to submit a comment with confidential information that you do not wish to be made available to the public, submit the comment as a written/paper submission and in the manner detailed (see “Written/Paper Submissions” and “Instructions”).</P>
                <HD SOURCE="HD2">Written/Paper Submissions</HD>
                <P>Submit written/paper submissions as follows:</P>
                <P>
                    • 
                    <E T="03">Mail/Hand delivery/Courier (for written/paper submissions):</E>
                     Dockets Management Staff (HFA-305), Food and Drug Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.
                </P>
                <P>• For written/paper comments submitted to the Dockets Management Staff, FDA will post your comment, as well as any attachments, except for information submitted, marked and identified, as confidential, if submitted as detailed in “Instructions.”</P>
                <P>
                    <E T="03">Instructions:</E>
                     All submissions received must include the Docket No. FDA-2022-N-2316 for “Discussion Paper: Distributed Manufacturing and Point-of-Care Manufacturing of Drugs; Request for Information and Comments.” Received comments, those filed in a timely manner (see 
                    <E T="02">ADDRESSES</E>
                    ), will be placed in the docket and, except for those submitted as “Confidential Submissions,” publicly viewable at 
                    <E T="03">https://www.regulations.gov</E>
                     or at the Dockets Management Staff between 9 a.m. and 4 p.m., Monday through Friday, 240-402-7500.
                </P>
                <P>
                    • Confidential Submissions: To submit a comment with confidential information that you do not wish to be made publicly available, submit your comments only as a written/paper submission. You should submit two copies total. One copy will include the information you claim to be confidential with a heading or cover note that states “THIS DOCUMENT CONTAINS CONFIDENTIAL INFORMATION.” The Agency will review this copy, including the claimed confidential information, in its consideration of comments. The second copy, which will have the claimed confidential information redacted/blacked out, will be available for public viewing and posted on 
                    <PRTPAGE P="62417"/>
                    <E T="03">https://www.regulations.gov.</E>
                     Submit both copies to the Dockets Management Staff. If you do not wish your name and contact information to be made publicly available, you can provide this information on the cover sheet and not in the body of your comments and you must identify this information as “confidential.” Any information marked as “confidential” will not be disclosed except in accordance with 21 CFR 10.20 and other applicable disclosure law. For more information about FDA's posting of comments to public dockets, see 80 FR 56469, September 18, 2015, or access the information at: 
                    <E T="03">https://www.govinfo.gov/content/pkg/FR-2015-09-18/pdf/2015-23389.pdf.</E>
                </P>
                <P>
                    <E T="03">Docket:</E>
                     For access to the docket to read background documents or the electronic and written/paper comments received, go to 
                    <E T="03">https://www.regulations.gov</E>
                     and insert the docket number, found in brackets in the heading of this document, into the “Search” box and follow the prompts and/or go to the Dockets Management Staff, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852, 240-402-7500.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Elizabeth Giaquinto Friedman, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, Rm. 4162, Silver Spring, MD 20993, 240-402-7930, 
                        <E T="03">Elizabeth.Giaquinto@fda.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>Advanced manufacturing is a general term for an innovative pharmaceutical manufacturing technology or approach that has the potential to improve the reliability and robustness of the manufacturing process and supply chain, and increase timely access to quality medicines for the American public. For the purposes of the discussion paper, all references to drugs include both human drugs and biological products (including those regulated by CBER), unless otherwise specified. Advanced manufacturing can: (1) integrate novel technological approaches, (2) use established techniques in an innovative way, or (3) apply production methods in a new domain. Advanced manufacturing can potentially be used for new or existing and large or small molecule drugs.</P>
                <P>FDA has recognized and embraced the potential of advanced manufacturing for many years. CDER established the Emerging Technology Program in 2014 to work collaboratively with companies to support the use of advanced manufacturing. CDER has observed a rapid emergence of advanced manufacturing technologies through the Emerging Technology Program and recognizes that regulatory policies and programs may need to evolve to enable the timely adoption of these technologies. The National Academies of Sciences, Engineering, and Medicine issued a 2021 report entitled “Innovation in Pharmaceutical Manufacturing on the Horizon: Technical Challenges, Regulatory Issues, and Recommendations”, noting potential innovations in integrated, flexible, and distributed manufacturing. These potential innovations include modular approaches to streamline drug development and production, and the deployment and use of highly portable manufacturing units. A range of drug manufacturers have recently engaged CDER through the Emerging Technology Program specifically regarding the development of portable and distributed manufacturing platforms.</P>
                <P>CBER established the CBER Advanced Technologies Team in 2019 to promote dialogue, education, and input between CBER and prospective innovators and developers of advanced manufacturing technologies. Through these interactions, CBER has observed interest from manufacturers in the implementation of novel manufacturing approaches for CBER-regulated products. CBER also recognizes the need to consider developing a regulatory framework to facilitate the adoption of these emerging technologies. CBER expects the development of advanced manufacturing technologies associated with DM and POC manufacturing for products that it regulates.</P>
                <P>
                    The discussion paper (available on FDA's website at: CDER's Framework for Regulatory Advanced Manufacturing Evaluation (FRAME) Initiative | FDA) presents areas for consideration and policy development identified by CDER scientific and policy experts associated with DM and POC manufacturing that would be valuable as FDA considers developing a regulatory framework that contemplates these technologies for CDER- and CBER-regulated drug and biological products. For the purposes of the discussion paper, CDER and CBER define DM to be a decentralized manufacturing strategy consisting of a manufacturing platform of manufacturing units deployed to multiple locations; POC manufacturing is defined as a subset of DM that uses manufacturing units distributed to host sites in proximity to patient care (
                    <E T="03">e.g.,</E>
                     healthcare facilities). Regulatory areas of consideration include applicable statutory provisions, regulations, and guidance related to quality assessment and inspections that could affect an applicant's ability to comply with the current regulatory framework or FDA's assessment of a marketing application.
                </P>
                <HD SOURCE="HD1">II. Requested Information and Comments</HD>
                <P>
                    Interested persons are invited to provide detailed comments to CDER and CBER (see 
                    <E T="02">ADDRESSES</E>
                    ) on all aspects described in the discussion paper. The discussion paper is available on FDA's website for the FRAME initiative at: CDER's Framework for Regulatory Advanced Manufacturing Evaluation (FRAME) Initiative | FDA. To facilitate input, FDA has developed a series of questions after each technology described in the discussion paper. The questions are not meant to be exhaustive, and FDA is also interested in any other pertinent information stakeholders would like to share on this topic. This feedback will help inform the Agency's policy development regarding the technologies described in the discussion paper. FDA encourages stakeholders to provide the specific rationale and basis for their comments, including any available supporting data and information.
                </P>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22386 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2016-D-0973]</DEPDOC>
                <SUBJECT>Comparability Protocols for Postapproval Changes to the Chemistry, Manufacturing, and Controls Information in a New Drug Application, Abbreviated New Drug Application, or Biologics License Application; Guidance for Industry; Availability</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Food and Drug Administration (FDA or Agency) is announcing the availability of a final guidance for industry entitled “Comparability Protocols for Postapproval Changes to the Chemistry, Manufacturing, and Controls Information in an NDA, ANDA, or BLA.” This final guidance is intended to assist original applicants and holders of approved new drug applications (NDAs), abbreviated new drug applications (ANDAs), and biologics 
                        <PRTPAGE P="62418"/>
                        license applications (BLAs) on implementing a chemistry, manufacturing, and controls (CMC) postapproval change(s) through the use of a comparability protocol (CP). In many cases, submission and approval of a CP will facilitate the subsequent implementation and reporting of CMC changes, which could result in moving a drug or biological product into distribution or facilitating a proactive approach to reinforcing the supply of a product sooner than if a CP were not used. This final guidance recommends a framework to promote continuous improvement in the manufacturing of quality drug and biological products. This document finalizes a revised draft guidance that published on April 20, 2016, entitled “Comparability Protocols for Human Drugs and Biologics: Chemistry, Manufacturing, and Controls Information.” A related draft guidance entitled “Comparability Protocols—Protein Drug Products and Biological Products—Chemistry, Manufacturing, and Controls Information” that published in September 2003, was withdrawn on May 6, 2015.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        The announcement of the guidance is published in the 
                        <E T="04">Federal Register</E>
                         on October 14, 2022.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit either electronic or written comments on Agency guidances at any time as follows:</P>
                </ADD>
                <HD SOURCE="HD2">Electronic Submissions</HD>
                <P>Submit electronic comments in the following way:</P>
                <P>
                    • 
                    <E T="03">Federal eRulemaking Portal: https://www.regulations.gov.</E>
                     Follow the instructions for submitting comments. Comments submitted electronically, including attachments, to 
                    <E T="03">https://www.regulations.gov</E>
                     will be posted to the docket unchanged. Because your comment will be made public, you are solely responsible for ensuring that your comment does not include any confidential information that you or a third party may not wish to be posted, such as medical information, your or anyone else's Social Security number, or confidential business information, such as a manufacturing process. Please note that if you include your name, contact information, or other information that identifies you in the body of your comments, that information will be posted on 
                    <E T="03">https://www.regulations.gov.</E>
                </P>
                <P>• If you want to submit a comment with confidential information that you do not wish to be made available to the public, submit the comment as a written/paper submission and in the manner detailed (see “Written/Paper Submissions” and “Instructions”).</P>
                <HD SOURCE="HD2">Written/Paper Submissions</HD>
                <P>Submit written/paper submissions as follows:</P>
                <P>
                    • 
                    <E T="03">Mail/Hand Delivery/Courier (for written/paper submissions):</E>
                     Dockets Management Staff (HFA-305), Food and Drug Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.
                </P>
                <P>• For written/paper comments submitted to the Dockets Management Staff, FDA will post your comment, as well as any attachments, except for information submitted, marked and identified, as confidential, if submitted as detailed in “Instructions.”</P>
                <P>
                    <E T="03">Instructions:</E>
                     All submissions received must include the Docket No. FDA-2016-D-0973 for “Comparability Protocols for Postapproval Changes to the Chemistry, Manufacturing, and Controls Information in an NDA, ANDA, or BLA.” Received comments will be placed in the docket and, except for those submitted as “Confidential Submissions,” publicly viewable at 
                    <E T="03">https://www.regulations.gov</E>
                     or at the Dockets Management Staff between 9 a.m. and 4 p.m., Monday through Friday, 240-402-7500.
                </P>
                <P>
                    • Confidential Submissions—To submit a comment with confidential information that you do not wish to be made publicly available, submit your comments only as a written/paper submission. You should submit two copies total. One copy will include the information you claim to be confidential with a heading or cover note that states “THIS DOCUMENT CONTAINS CONFIDENTIAL INFORMATION.” The Agency will review this copy, including the claimed confidential information, in its consideration of comments. The second copy, which will have the claimed confidential information redacted/blacked out, will be available for public viewing and posted on 
                    <E T="03">https://www.regulations.gov.</E>
                     Submit both copies to the Dockets Management Staff. If you do not wish your name and contact information to be made publicly available, you can provide this information on the cover sheet and not in the body of your comments and you must identify this information as “confidential.” Any information marked as “confidential” will not be disclosed except in accordance with 21 CFR 10.20 and other applicable disclosure law. For more information about FDA's posting of comments to public dockets, see 80 FR 56469, September 18, 2015, or access the information at: 
                    <E T="03">https://govinfo.gov/content/pkg/FR-2015-09-18/pdf/2015-23389.pdf.</E>
                </P>
                <P>
                    <E T="03">Docket:</E>
                     For access to the docket to read background documents or the electronic and written/paper comments received, go to 
                    <E T="03">https://www.regulations.gov</E>
                     and insert the docket number, found in brackets in the heading of this document, into the “Search” box and follow the prompts and/or go to the Dockets Management Staff, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852, 240-402-7500.
                </P>
                <P>You may submit comments on any guidance at any time (see 21 CFR 10.115(g)(5)).</P>
                <P>
                    Submit written requests for single copies of this guidance to the Division of Drug Information, Center for Drug Evaluation and Research, Food and Drug Administration, 10001 New Hampshire Ave., Hillandale Building, 4th Floor, Silver Spring, MD 20993-0002 or the Center for Biologics Evaluation and Research, Office of Communication, Outreach, and Development, 10903 New Hampshire Ave., WO71, Room 3128, Silver Spring, MD 20903. Send one self-addressed adhesive label to assist that office in processing your requests. See the 
                    <E T="02">SUPPLEMENTARY INFORMATION</E>
                     section for electronic access to the guidance document.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Stephen Moore, Center for Drug Evaluation and Research, Food and Drug Administration, Bldg. 51, Rm. 4159, 10903 New Hampshire Ave., Silver Spring, MD, 20993-0002, 301-796-7579 or Stephen Ripley, Center for Biologics Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 71, Rm. 7301, Silver Spring, MD 20993, 240-402-7911.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    FDA is announcing the availability of a guidance for industry entitled “Comparability Protocols for Postapproval Changes to the Chemistry, Manufacturing, and Controls Information in an NDA, ANDA, or BLA.” The final guidance is intended to assist original applicants and holders of approved applications for human drugs and biological products on implementing a CMC postapproval change(s) through the use of a CP. In this guidance, a comparability protocol is synonymous with a postapproval change management protocol in the International Council for Harmonisation (ICH) Q12 guidance “Technical and Regulatory Considerations for Pharmaceutical Product Lifecycle Management” (May 2021). The final guidance is not applicable to blood and blood components; biological products that also meet the definition of a device in section 201(h) of the Federal Food, 
                    <PRTPAGE P="62419"/>
                    Drug, and Cosmetic Act; or human cells, tissues, or cellular or tissue-based products regulated solely under section 361 of the Public Health Service Act (42 U.S.C. 264) and 21 CFR part 1271.
                </P>
                <P>On April 20, 2016, (81 FR 23303), FDA announced the availability of a revised draft guidance entitled “Comparability Protocols for Human Drugs and Biologics: Chemistry, Manufacturing, and Controls Information.” This was a revised draft of a draft guidance published in February 2003. We revised the February 2003 draft guidance in 2016 for the following reasons:</P>
                <P>• To include current pharmaceutical quality concepts.</P>
                <P>• To provide more flexibility regarding filing procedures for a notification of modifications to an approved CP in less burdensome reporting categories than a prior approval supplement.</P>
                <P>• To add an appendix to address commonly asked questions.</P>
                <P>The Center for Veterinary Medicine, which was included in the February 2003 draft guidance, published recommendations for animal drugs in a separate guidance.</P>
                <P>We received a number of comments on the revised draft guidance, which the Agency considered carefully as it prepared this final guidance. Additional information has been included in the final guidance on proposing an appropriate reporting category for implementation of changes under a CP once approved. Additional examples have been included for notification of modifications to an approved CP in less burdensome reporting categories than a prior approval supplement. Information has been included in the appendix on cross-referencing of a master file, including a Drug Master File, in a CP and submitting a CP to a master file. Also, the recommendations in the guidance for industry ICH Q12 have been carefully considered when revising this guidance to maximize consistency. We also have made clarifications and editorial changes to the final guidance document.</P>
                <P>This final guidance provides recommendations to original applicants and holders of approved applications for human drugs and certain biological products on implementing CMC postapproval change(s) through the use of a CP. In many cases, submission and approval of a CP will facilitate the subsequent implementation and reporting of CMC changes, which could result in moving a drug or biological product into distribution or facilitating a proactive approach to reinforcing the supply of a product sooner than if a CP were not used.</P>
                <P>The final guidance recommends a framework to promote continuous improvement in the manufacturing of quality drug and biological products by encouraging applicants to employ the following:</P>
                <P>• Effective use of knowledge and understanding of the product and manufacturing process;</P>
                <P>• Risk management activities over the life cycle of a product; and</P>
                <P>• An effective pharmaceutical quality system</P>
                <P>This final guidance incorporates the modern regulatory concepts stated in the guidance for industry entitled “PAT—A Framework for Innovative Pharmaceutical Development, Manufacturing, and Quality Assurance,” the Pharmaceutical Quality for the 21st Century—A Risk Based Approach, the Critical Path Initiative, and the quality by design principles described in the guidance for industry entitled “Q8(R2) Pharmaceutical Development.”</P>
                <P>This guidance is being issued consistent with FDA's good guidance practices regulation (21 CFR 10.115). The guidance represents the current thinking of FDA on “Comparability Protocols for Postapproval Changes to the Chemistry, Manufacturing, and Controls Information in an NDA, ANDA, or BLA.” It does not establish any rights for any person and, with the exception of section V, is not binding on FDA or the public. You can use an alternative approach if it satisfies the requirements of the applicable statutes and regulations.</P>
                <P>
                    As noted, insofar as section V of this guidance sets forth that certain modifications to an approved CP must be submitted in a changes being effected supplement or annual report rather than a prior approval supplement, it has binding effect, as indicated by the use of the words 
                    <E T="03">must, shall,</E>
                     or 
                    <E T="03">required.</E>
                     Such binding effect derives from section 506A of the FD&amp;C Act, as implemented in 21 CFR 314.70 and 601.12.
                </P>
                <HD SOURCE="HD1">II. Paperwork Reduction Act of 1995</HD>
                <P>While this guidance contains no collection of information, it does refer to previously approved FDA collections of information. Therefore, clearance by the Office of Management and Budget (OMB) under the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501-3521) is not required for this guidance. The previously approved collections of information are subject to review by OMB under the PRA. The collections of information in 21 CFR part 314 have been approved under OMB control number 0910-0001. The collections of information in 21 CFR part 601 have been approved under OMB control number 0910-0338. The collections of information in 21 CFR parts 210 and 211 relating to current good manufacturing practices have been approved under OMB control number 0910-0139. The collections of information relating to section 351(k) of the PHS Act have been approved under OMB control number 0910-0718.</P>
                <HD SOURCE="HD1">III. Electronic Access</HD>
                <P>
                    Persons with access to the internet may obtain the guidance at 
                    <E T="03">https://www.fda.gov/drugs/guidance-compliance-regulatory-information/guidances-drugs, https://www.fda.gov/regulatory-information/search-fda-guidance-documents,</E>
                     or 
                    <E T="03">https://www.regulations.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22334 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2022-N-2335]</DEPDOC>
                <SUBJECT>Prescription Drug User Fee Act VII; Independent Assessment of Communication Through Product Quality Information Requests During Application Review; Statement of Work; Request for Comments</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; establishment of a public docket; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Food and Drug Administration (FDA or Agency) is announcing an opportunity for public comment on the Statement of Work to assess communication between FDA and sponsors through product quality information requests during application review and to identify best practices and areas of improvement. The independent assessment is part of FDA performance commitments under the recent reauthorization of the Prescription Drug User Fee Act (PDUFA). The independent assessment of FDA and sponsors in communicating through product quality information requests is described in detail in the document entitled “PDUFA Reauthorization Performance Goals and Procedures Fiscal Years 2023 Through 2027.” As part of FDA performance commitments described in this document, the assessment will be conducted by an 
                        <PRTPAGE P="62420"/>
                        independent contractor. FDA is providing for public comment on the statement of work before revising as needed and requesting contractor proposals.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Either electronic or written comments on the statement of work must be submitted by November 14, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments as follows. Please note that late, untimely filed comments will not be considered. The 
                        <E T="03">https://www.regulations.gov</E>
                         electronic filing system will accept comments until 11:59 p.m. Eastern Time at the end of November 14, 2022. Comments received by mail/hand delivery/courier (for written/paper submissions) will be considered timely if they are received on or before that date.
                    </P>
                </ADD>
                <HD SOURCE="HD2">Electronic Submissions</HD>
                <P>Submit electronic comments in the following way:</P>
                <P>
                    • 
                    <E T="03">Federal eRulemaking Portal: https://www.regulations.gov.</E>
                     Follow the instructions for submitting comments. Comments submitted electronically, including attachments, to 
                    <E T="03">https://www.regulations.gov</E>
                     will be posted to the docket unchanged. Because your comment will be made public, you are solely responsible for ensuring that your comment does not include any confidential information that you or a third party may not wish to be posted, such as medical information, your or anyone else's Social Security number, or confidential business information, such as a manufacturing process. Please note that if you include your name, contact information, or other information that identifies you in the body of your comments, that information will be posted on 
                    <E T="03">https://www.regulations.gov.</E>
                </P>
                <P>• If you want to submit a comment with confidential information that you do not wish to be made available to the public, submit the comment as a written/paper submission and in the manner detailed (see “Written/Paper Submissions” and “Instructions”).</P>
                <HD SOURCE="HD2">Written/Paper Submissions</HD>
                <P>Submit written/paper submissions as follows:</P>
                <P>
                    • 
                    <E T="03">Mail/Hand Delivery/Courier (for written/paper submissions):</E>
                     Dockets Management Staff (HFA-305), Food and Drug Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.
                </P>
                <P>• For written/paper comments submitted to the Dockets Management Staff, FDA will post your comment, as well as any attachments, except for information submitted, marked and identified, as confidential, if submitted as detailed in “Instructions.”</P>
                <P>
                    <E T="03">Instructions:</E>
                     All submissions received must include the Docket No. FDA-2022-N-2335 for “Prescription Drug User Fee Act VII Commitment to Assess Current Practices of the Food and Drug Administration and Sponsors in Communicating Through Product Quality Information Requests During Application Review.” Received comments, those filed in a timely manner (see 
                    <E T="02">ADDRESSES</E>
                    ), will be placed in the docket and, except for those submitted as “Confidential Submissions,” publicly viewable at 
                    <E T="03">https://www.regulations.gov</E>
                     or at the Dockets Management Staff between 9 a.m. and 4 p.m., Monday through Friday, 240-402-7500.
                </P>
                <P>
                    • Confidential Submissions—To submit a comment with confidential information that you do not wish to be made publicly available, submit your comments only as a written/paper submission. You should submit two copies total. One copy will include the information you claim to be confidential with a heading or cover note that states “THIS DOCUMENT CONTAINS CONFIDENTIAL INFORMATION.” FDA will review this copy, including the claimed confidential information, in its consideration of comments. The second copy, which will have the claimed confidential information redacted/blacked out, will be available for public viewing and posted on 
                    <E T="03">https://www.regulations.gov.</E>
                     Submit both copies to the Dockets Management Staff. If you do not wish your name and contact information to be made publicly available, you can provide this information on the cover sheet and not in the body of your comments and you must identify this information as “confidential.” Any information marked as “confidential” will not be disclosed except in accordance with 21 CFR 10.20 and other applicable disclosure law. For more information about FDA's posting of comments to public dockets, see 80 FR 56469, September 18, 2015, or access the information at: 
                    <E T="03">https://www.govinfo.gov/content/pkg/FR-2015-09-18/pdf/2015-23389.pdf.</E>
                </P>
                <P>
                    <E T="03">Docket:</E>
                     For access to the docket to read background documents or the electronic and written/paper comments received, go to 
                    <E T="03">https://www.regulations.gov</E>
                     and insert the docket number, found in brackets in the heading of this document, into the “Search” box and follow the prompts and/or go to the Dockets Management Staff, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852, 240-402-7500.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Emily Ewing, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, Rm. 1148, Silver Spring, MD 20993-0002, 240-402-0196, 
                        <E T="03">Emily.Ewing@fda.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>PDUFA provides FDA with a source of stable, consistent funding that has made it possible for the Agency to focus on promoting innovative therapies and help bring to market critical products for patients. When PDUFA was originally authorized in 1992, it had a 5-year term. The program has been subsequently reauthorized every 5 years. To prepare for reauthorization of PDUFA for the next 5-year period (2023 to 2027), FDA conducted negotiations with the regulated industry and held regular consultations with public stakeholders, including patient advocates, consumer advocates, and healthcare professionals between September 2020 and February 2021.</P>
                <P>
                    Following these discussions, related public meetings, and Agency requests for public comment, FDA published the “PDUFA Reauthorization Performance Goals and Procedures Fiscal Years 2023 Through 2027” document, available at 
                    <E T="03">https://www.fda.gov/media/151712/download,</E>
                     also known as the PDUFA VII “goals letter,” to supplement the statute. The goals letter includes the performance goals, procedures, and commitments that apply to aspects of the human drug review program that are important for facilitating timely access to safe, effective, and innovative new medicines for patients. Several of these commitments aim to continue to enhance communication between FDA and sponsors during application review.
                </P>
                <P>FDA and sponsors interact in a variety of ways throughout application review. One such way is via a communication called an information request (IR), sent to an applicant as the discipline review occurs. FDA uses IRs to request further information or clarification that is needed or would be helpful to allow completion of the discipline review. IRs may be in the form of letters, emails, or faxes.</P>
                <P>
                    FDA uses product quality IRs to request further information or clarification needed for FDA's assessment of identity, strength, quality, purity, or potency of drug substances or drug products. Ensuring that patients can have confidence in the safety and effectiveness of their medications is a longstanding priority for FDA. The Center for Drug Evaluation and Research (CDER) and the Center for Biologics Evaluation and Research (CBER) have 
                    <PRTPAGE P="62421"/>
                    worked to address this priority in part by performing Chemistry, Manufacturing, and Controls (CMC) reviews for CDER-regulated and CBER-regulated products. CDER or CBER may issue a product quality, or CMC, IR as a result of CMC assessments conducted in support of the application.
                </P>
                <P>IRs from both CDER and CBER are expected to follow Four-Part Harmony in which reviewers are expected to communicate: (1) what was provided, (2) what is the issue or deficiency, (3) what is needed, and (4) why it is needed. This expectation can be found in CDER's Manual of Policies and Procedures (MAPP) 5016.8, “Communication Guidelines for Quality-Related Information Requests and Deficiencies.” As a result of FDA's implementation of Four-Part Harmony in CMC-IRs, sponsors should understand what information FDA needs to continue their review. The PDUFA VII goals letter includes commitments for FDA to update and conduct training on existing policies and procedures (MAPPs and Standard Operating Policy and Procedure (SOPPs)), to reflect Four-Part Harmony. CDER MAPP 5016.8, “Communication Guidelines for Quality-Related Information Requests and Deficiencies” will be revised and made public. CBER SOPP 8401.1, “Issuance of and Review of Responses to Information Request Communications to Pending Applications” will also be revised.</P>
                <P>In addition to updating the documents and conducting training, FDA is committed to contracting with an independent third party to assess current practices of CDER, CBER, and sponsors in communicating through product quality IRs during application review and effectiveness of Four-Part Harmony. This assessment will identify best practices and areas of improvement in communications between FDA review staff and sponsors through product quality IRs and is the subject of this task order.</P>
                <P>
                    The Statement of Work can be accessed at: 
                    <E T="03">https://www.fda.gov/industry/prescription-drug-user-fee-amendments/pdufa-vii-assessment-fda-and-sponsor-communications-through-product-quality-information-requests.</E>
                </P>
                <SIG>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22335 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2022-N-0008]</DEPDOC>
                <SUBJECT>Request for Nominations for Individuals and Consumer Organizations for Advisory Committees</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA or Agency) is requesting that any consumer organizations interested in participating in the selection of voting and/or nonvoting consumer representatives to serve on its advisory committees or panels notify FDA in writing. FDA is also requesting nominations for voting and/or nonvoting consumer representatives to serve on advisory committees and/or panels for which vacancies currently exist or are expected to occur in the near future. Nominees recommended to serve as a voting or nonvoting consumer representative may be self-nominated or may be nominated by a consumer organization. FDA seeks to include the views of individuals on its advisory committee regardless of their gender identification, religious affiliation, racial and ethnic identification, or disability status and, therefore, encourages nominations of appropriately qualified candidates from all groups.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Any consumer organization interested in participating in the selection of an appropriate voting or nonvoting member to represent consumer interests on an FDA advisory committee or panel may send a letter or email stating that interest to FDA (see 
                        <E T="02">ADDRESSES</E>
                        ) by November 28, 2022, for vacancies listed in this notice. Concurrently, nomination materials for prospective candidates should be sent to FDA (see 
                        <E T="02">ADDRESSES</E>
                        ) by November 28, 2022. Nominations will be accepted for current vacancies and for those that will or may occur through December 31, 2023.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        All statements of interest from consumer organizations interested in participating in the selection process should be submitted electronically to 
                        <E T="03">ACOMSSubmissions@fda.hhs.gov or</E>
                         by mail to Advisory Committee Oversight and Management Staff, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 32, Rm. 5122, Silver Spring, MD 20993-0002.
                    </P>
                    <P>
                        Consumer representative nominations should be submitted electronically by logging into the FDA Advisory Committee Membership Nomination Portal: 
                        <E T="03">https://www.accessdata.fda.gov/scripts/FACTRSPortal/FACTRS/index.cfm,</E>
                         or by mail to Advisory Committee Oversight and Management Staff, 10903 New Hampshire Ave., Bldg. 32, Rm. 5122, Silver Spring, MD 20993-0002. Additional information about becoming a member of an FDA advisory committee can also be obtained by visiting FDA's website at 
                        <E T="03">https://www.fda.gov/AdvisoryCommittees/default.htm.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P> </P>
                    <P>
                        <E T="03">For questions relating to participation in the selection process:</E>
                         Kimberly Hamilton, Advisory Committee Oversight and Management Staff, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 32, Rm. 5122, Silver Spring, MD 20993-0002, 301-796-8220, 
                        <E T="03">kimberly.hamilton@fda.hhs.gov.</E>
                    </P>
                    <P>For questions relating to specific advisory committees or panels, contact the appropriate contact person listed in table 1.</P>
                    <GPOTABLE COLS="2" OPTS="L2,nj,i1" CDEF="s100,r100">
                        <TTITLE>Table 1—Advisory Committee Contacts</TTITLE>
                        <BOXHD>
                            <CHED H="1">Contact person</CHED>
                            <CHED H="1">Committee/panel</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                Rakesh Raghuwanshi, Office of the Chief Scientist, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 1, Rm. 3309, Silver Spring, MD 20993-0002, 301-796-4769, 
                                <E T="03">Rakesh.Raghuwanshi@fda.hhs.gov</E>
                            </ENT>
                            <ENT>FDA Science Board Advisory Committee.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Prabhakara Atreya, Center for Biologics Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 71, Rm. 1226, Silver Spring, MD 20993-0002, 240-402-8006, 
                                <E T="03">Prabhakara.Altreya@fda.hhs.gov</E>
                            </ENT>
                            <ENT>Allergenic Products Advisory Committee.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="62422"/>
                            <ENT I="01">
                                Moon Hee Choi, Center for Drugs Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 31, Rm. 2434, Silver Spring, MD 20993-0002, 301-796-2894, 
                                <E T="03">MoonHee.Choi@fda.hhs.gov</E>
                            </ENT>
                            <ENT>Anesthetic and Analgesic Drug Products Advisory Committee, Non-Prescription Drugs Advisory Committee.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                She-Chia Chen, Center for Drugs Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 31 Rm. 2438, Silver Spring, MD 20993-0002, 240-402-5343, 
                                <E T="03">She-Chia.Chen@fda.hhs.gov</E>
                            </ENT>
                            <ENT>Antimicrobial Drugs Advisory Committee.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Jessica Seo, Center for Drugs Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 31, Rm. 2412, Silver Spring, MD 20993-0002, 301-796-7699, 
                                <E T="03">Jessica.Seo@fda.hhs.gov</E>
                            </ENT>
                            <ENT>Arthritis Advisory Committee, Peripheral and Central Nervous System Drugs Advisory Committee.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Yvette Staples, Center for Drugs Evaluation Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 31, Rm. 2438, Silver Spring, MD 20993-0002, 301-837-7126, 
                                <E T="03">Yvette.Staples@fda.hhs.gov</E>
                            </ENT>
                            <ENT>Cardiovascular and Renal Drugs Advisory Committee, Medical Imaging Drugs Advisory Committee.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                LaToya Bonner, Center for Drugs Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 31, Rm. 2428, Silver Spring, MD 20993-0002, 301-796-2855, 
                                <E T="03">LaToya.Bonner@fda.hhs.gov</E>
                            </ENT>
                            <ENT>Endocrinologic and Metabolic Drugs Advisory Committee.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Takyiah Stevenson, Center for Drugs Evaluation Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 31, Rm. 2406, Silver Spring, MD 20993-0002, 240-402-2507, 
                                <E T="03">Takyiah.Stevenson@fda.hhs.gov</E>
                            </ENT>
                            <ENT>Pharmacy Compounding Advisory Committee.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Joyce Frimpong, Center for Drugs Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 31, Rm. 2462, Silver Spring, MD 20993-0002, 301-796-7973, 
                                <E T="03">Joyce.Frimpong@fda.hhs.gov</E>
                            </ENT>
                            <ENT>Psychopharmacologic Drugs Advisory Committee.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Candace Nalls, Center for Devices and Radiological Health, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 66, Rm. 5211, Silver Spring, MD 20993-0002, 301-636-0510, 
                                <E T="03">Candace.Nalls@fda.hhs.gov</E>
                            </ENT>
                            <ENT>Anesthesiology and Respiratory Therapy Devices Panel; Clinical Chemistry and Clinical Toxicology Devices Panel; Ear, Nose and Throat Devices Panel; Gastroenterology-Urology Devices Panel; General and Plastic Surgery Devices Panel.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                James Swink, Center for Devices and Radiological Health, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 66, Rm. 5211, Silver Spring, MD 20993-0002, 301-796-6313, 
                                <E T="03">James.Swink@fda.hhs.gov</E>
                            </ENT>
                            <ENT>Circulatory System Devices Panel; Microbiology Devices Panel.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Akinola Awojope, Center for Devices and Radiological Health, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 66, Rm. 5216, Silver Spring, MD 20993-0002, 301-636-0512, 
                                <E T="03">Akinola.Awojope@fda.hhs.gov</E>
                            </ENT>
                            <ENT>Dental Products Panel; Obstetrics and Gynecology Devices Panel; Orthopaedic and Rehabilitation Devices Panel.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Jarrod Collier, Center for Devices and Radiological Health, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 66, Rm. 5211, Silver Spring, MD 20993-0002, 240-672-5763, 
                                <E T="03">Jarrod.Collier@fda.hhs.gov</E>
                            </ENT>
                            <ENT>General Hospital and Personal Use Devices Panel; Hematology and Pathology Devices Panel; Molecular and Clinical Genetics Panel; Ophthalmic Devices Panel; Radiological Devices Panel.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                James Swink, Center for Devices and Radiological Health, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 66, Rm. 5211, Silver Spring, MD 20993-0002, 301-796-6313, 
                                <E T="03">James.Swink@fda.hhs.gov</E>
                            </ENT>
                            <ENT>National Mammography Quality Assurance Advisory Committee.</ENT>
                        </ROW>
                    </GPOTABLE>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>FDA is requesting nominations for voting and/or nonvoting consumer representatives for the vacancies listed in table 2:</P>
                <GPOTABLE COLS="3" OPTS="L2,nj,i1" CDEF="s100,xs66,xs72">
                    <TTITLE>Table 2—Committee Descriptions, Type of Consumer Representative Vacancy, and Approximate Date Needed</TTITLE>
                    <BOXHD>
                        <CHED H="1">Committee/panel/areas of expertise needed</CHED>
                        <CHED H="1">Type of vacancy</CHED>
                        <CHED H="1">Approximate date needed</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">FDA Science Board Advisory Committee—The Science Board provides advice to the Commissioner of Food and Drugs Administration (Commissioner) and other appropriate officials on specific complex scientific and technical issues important to FDA and its mission, including emerging issues within the scientific community. Additionally, the Science Board provides advice that supports the Agency in keeping pace with technical and scientific developments, including in regulatory science; and input into the Agency's research agenda, and on upgrading its scientific and research facilities and training opportunities. It also provides, where requested, expert review of Agency-sponsored intramural and extramural scientific research programs</ENT>
                        <ENT>1—Voting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allergenic Products Advisory Committee—Knowledgeable in the fields of allergy, immunology, pediatrics, internal medicine, biochemistry, and related specialties</ENT>
                        <ENT>1—Voting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="62423"/>
                        <ENT I="01">Anesthetic and Analgesic Drug Products Advisory Committee—Knowledgeable in the fields of anesthesiology, surgery, epidemiology or statistics, and related specialties</ENT>
                        <ENT>1—Voting</ENT>
                        <ENT>April 1, 2023.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Non-Prescription Drugs Advisory Committee—Knowledgeable in the fields of internal medicine, family practice, clinical toxicology, clinical pharmacology, pharmacy, dentistry, and related specialties</ENT>
                        <ENT>1—Voting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Antimicrobial Drugs Advisory Committee—Knowledgeable in the fields of infectious disease, internal medicine, microbiology, pediatrics, epidemiology or statistics, and related specialties</ENT>
                        <ENT>1—Voting</ENT>
                        <ENT>May 1, 2023.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Arthritis Advisory Committee—Knowledgeable in the fields of arthritis, rheumatology, orthopedics, epidemiology or statistics, analgesics, and related specialties</ENT>
                        <ENT>1—Voting</ENT>
                        <ENT>December 1, 2023.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Peripheral and Central Nervous Systems Drugs Advisory Committee—Knowledgeable in the fields of neurology, neuropharmacology, neuropathology, otolaryngology, epidemiology or statistics, and related specialties</ENT>
                        <ENT>1—Voting</ENT>
                        <ENT>February 1, 2023.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cardiovascular and Renal Drugs Advisory Committee—Knowledgeable in the fields of cardiology, hypertension, arrhythmia, angina, congestive heart failure, diuresis, and biostatistics</ENT>
                        <ENT>1—Voting</ENT>
                        <ENT>July 1, 2023.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Medical Imaging Drugs Advisory Committee—Knowledgeable in the fields of nuclear medicine, radiology, epidemiology, statistics, and related specialties</ENT>
                        <ENT>1—Voting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Endocrinologic and Metabolic Drugs Advisory Committee—Knowledgeable in the fields of endocrinology, metabolism, epidemiology or statistics, and related specialties</ENT>
                        <ENT>1—Voting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pharmacy Compounding Advisory Committee—Knowledgeable in the fields of pharmaceutical compounding, pharmaceutical manufacturing, pharmacy, medicine, and other related specialties</ENT>
                        <ENT>1—Voting</ENT>
                        <ENT>October 1, 2023.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Psychopharmacologic Drugs Advisory Committee—Knowledgeable in the fields of psychopharmacology, psychiatry, epidemiology or statistics, and related specialties</ENT>
                        <ENT>1—Voting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Anesthesiology and Respiratory Therapy Devices Panel—Anesthesiologists, pulmonary medicine specialists, or other experts who have specialized interests in ventilator support, pharmacology, physiology, or the effects and complications of anesthesia</ENT>
                        <ENT>1—Nonvoting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Clinical Chemistry and Clinical Toxicology Devices Panel—Doctor of Medicine or Philosophy with experience in clinical chemistry (
                            <E T="03">e.g.,</E>
                             cardiac markers), clinical toxicology, clinical pathology, clinical laboratory medicine, and endocrinology
                        </ENT>
                        <ENT>1—Nonvoting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ear, Nose and Throat Devices Panel—Otologists, neurotologists, audiologists</ENT>
                        <ENT>1—Nonvoting</ENT>
                        <ENT>November 1, 2023.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Gastroenterology-Urology Devices Panel—Gastroenterologists, urologists, and nephrologists</ENT>
                        <ENT>1—Nonvoting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">General and Plastic Surgery Devices Panel—Surgeons (general, plastic, reconstructive, pediatric, thoracic, abdominal, pelvic, and endoscopic); dermatologists; experts in biomaterials, lasers, wound healing, and quality of life; and biostatisticians</ENT>
                        <ENT>1—Nonvoting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Circulatory System Devices Panel—Interventional cardiologists, electrophysiologists, invasive (vascular) radiologists, vascular and cardiothoracic surgeons, and cardiologists with special interest in congestive heart failure</ENT>
                        <ENT>1—Nonvoting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Microbiology Devices Panel—Clinicians with an expertise in infectious disease, 
                            <E T="03">e.g.,</E>
                             pulmonary disease specialists, sexually transmitted disease specialists, pediatric infectious disease specialists, experts in tropical medicine and emerging infectious diseases, mycologists; clinical microbiologists and virologists; clinical virology and microbiology laboratory directors, with expertise in clinical diagnosis and in vitro diagnostic assays, 
                            <E T="03">e.g.,</E>
                             hepatologists; molecular biologists
                        </ENT>
                        <ENT>1—Nonvoting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dental Products Panel—Dentists, engineers and scientists who have expertise in the areas of dental implants, dental materials, periodontology, tissue engineering, and dental anatomy</ENT>
                        <ENT>1—Nonvoting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Obstetrics and Gynecology Devices Panel—Experts in perinatology, embryology, reproductive endocrinology, pediatric gynecology, gynecological oncology, operative hysteroscopy, pelviscopy, electrosurgery, laser surgery, assisted reproductive technologies, contraception, postoperative adhesions, and cervical cancer and colposcopy; biostatisticians and engineers with experience in obstetrics/gynecology devices; urogynecologists; experts in breast care; experts in gynecology in the older patient; experts in diagnostic (optical) spectroscopy; experts in midwifery; labor and delivery nursing</ENT>
                        <ENT>1—Nonvoting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Orthopaedic and Rehabilitation Devices Panel—Orthopedic surgeons (joint spine, trauma, and pediatric); rheumatologists; engineers (biomedical, biomaterials, and biomechanical); experts in rehabilitation medicine, sports medicine, and connective tissue engineering; and biostatisticians</ENT>
                        <ENT>1—Nonvoting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">General Hospital and Personal Use Devices Panel—Internists, pediatricians, neonatologists, endocrinologists, gerontologists, nurses, biomedical engineers, or microbiologists/infection control practitioners or experts</ENT>
                        <ENT>1—Nonvoting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hematology and Pathology Devices Panel—Hematologists (benign and/or malignant hematology), hematopathologists (general and special hematology, coagulation and hemostasis, and hematological oncology), gynecologists with special interests in gynecological oncology, cytopathologists, and molecular pathologists with special interests in development of predictive biomarkers</ENT>
                        <ENT>1—Nonvoting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Molecular and Clinical Genetics Devices Panel—Experts in human genetics and in the clinical management of patients with genetic disorders, 
                            <E T="03">e.g.,</E>
                             pediatricians, obstetricians, neonatologists. The Agency is also interested in considering candidates with training in inborn errors of metabolism, biochemical and/or molecular genetics, population genetics, epidemiology, and related statistical training. Additionally, individuals with experience in genetic counseling, medical ethics, as well as ancillary fields of study will be considered
                        </ENT>
                        <ENT>1—Nonvoting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="62424"/>
                        <ENT I="01">Ophthalmic Devices Panel—Ophthalmists with expertise in corneal-external disease, vitreo-retinal surgery, glaucoma, ocular immunology, ocular pathology; optometrists; vision scientists; and ophthalmic professionals with expertise in clinical trial design, quality of life assessment, electrophysiology, low vision rehabilitation, and biostatistics</ENT>
                        <ENT>1—Nonvoting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Radiological Devices Panel—Physicians with experience in general radiology, mammography, ultrasound, magnetic resonance, computed tomography, other radiological subspecialties, and radiation oncology; scientists with experience in diagnostic devices, radiation physics, statistical analysis, digital imaging, and image analysis</ENT>
                        <ENT>1—Nonvoting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">National Mammography Quality Assurance Advisory Committee—Physician, practitioner, or other health professional whose clinical practice, research specialization, or professional expertise includes a significant focus on mammography</ENT>
                        <ENT>3—Voting</ENT>
                        <ENT>Immediately.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">I. Functions and General Description of the Committee Duties</HD>
                <HD SOURCE="HD2">A. FDA Science Board Advisory Committee</HD>
                <P>The Science Board Advisory Committee (Science Board) provides advice to the Commissioner of Food and Drugs (Commissioner) and other appropriate officials on specific complex scientific and technical issues important to FDA and its mission, including emerging issues within the scientific community. Additionally, the Science Board provides advice that supports the Agency in keeping pace with technical and scientific developments, including in regulatory science, and input into the Agency's research agenda and on upgrading its scientific and research facilities and training opportunities. It also provides, where requested, expert review of Agency-sponsored intramural and extramural scientific research programs.</P>
                <HD SOURCE="HD2">B. Allergenic Products Advisory Committee</HD>
                <P>Reviews and evaluates available data concerning the safety, effectiveness, and adequacy of labeling of marketed and investigational allergenic biological products or materials that are administered to humans for the diagnosis, prevention, or treatment of allergies and allergic disease and makes appropriate recommendations to the Commissioner regarding the affirmation or revocation of biological product licenses, on the safety, effectiveness, and labeling of the products, on clinical and laboratory studies of such products, on amendments or revisions to regulations governing the manufacture, testing, and licensing of allergenic biological products, and on the quality and relevance of FDA's research programs.</P>
                <HD SOURCE="HD2">C. Anesthetic and Analgesic Drug Products Advisory Committee</HD>
                <P>Reviews and evaluates available data concerning the safety and effectiveness of marketed and investigational human drug products for use in anesthesiology and surgery.</P>
                <HD SOURCE="HD2">D. Nonprescription Drugs Advisory Committee</HD>
                <P>Reviews and evaluates available data concerning the safety and effectiveness of over-the-counter (nonprescription) human drug products, or any other FDA-regulated product, for use in the treatment of a broad spectrum of human symptoms and diseases and advises the Commissioner either on the promulgation of monographs establishing conditions under which these drugs are generally recognized as safe and effective and not misbranded or on the approval of new drug applications for such drugs. The Committee serves as a forum for the exchange of views regarding the prescription and nonprescription status, including switches from one status to another, of these various drug products and combinations thereof. The Committee may also conduct peer review of Agency sponsored intramural and extramural scientific biomedical programs in support of FDA's mission and regulatory responsibilities.</P>
                <HD SOURCE="HD2">E. Antimicrobial Drugs Advisory Committee</HD>
                <P>Reviews and evaluates available data concerning the safety and effectiveness of marketed and investigational human drug products for use in the treatment of infectious diseases and disorders.</P>
                <HD SOURCE="HD2">F. Arthritis Advisory Committee</HD>
                <P>Reviews and evaluates data concerning the safety and effectiveness of marketed and investigational human drug products for use in the treatment of arthritis, rheumatism, and related diseases.</P>
                <HD SOURCE="HD2">G. Peripheral and Central Nervous System Drugs Advisory Committee</HD>
                <P>Reviews and evaluates data concerning the safety and effectiveness of marketed and investigational human drug products for use in the treatment of neurologic diseases.</P>
                <HD SOURCE="HD2">H. Cardiovascular and Renal Drugs Advisory Committee</HD>
                <P>Reviews and evaluates available data concerning the safety and effectiveness of marketed and investigational human drug products for use in the treatment of cardiovascular and renal disorders.</P>
                <HD SOURCE="HD2">I. Medical Imaging Drugs Advisory Committee</HD>
                <P>Reviews and evaluates data concerning the safety and effectiveness of marketed and investigational human drug products for use in diagnostic and therapeutic procedures using radioactive pharmaceuticals and contrast media used in diagnostic radiology.</P>
                <HD SOURCE="HD2">J. Endocrinologic and Metabolic Drugs Advisory Committee</HD>
                <P>Reviews and evaluates data concerning the safety and effectiveness of marketed and investigational human drug products for use in the treatment of endocrine and metabolic disorders.</P>
                <HD SOURCE="HD2">K. Pharmacy Compounding Advisory Committee</HD>
                <P>Provides advice on scientific, technical, and medical issues concerning drug compounding by pharmacists and licensed practitioners.</P>
                <HD SOURCE="HD2">L. Psychopharmacologic Drugs Advisory Committee</HD>
                <P>
                    Reviews and evaluates data concerning the safety and effectiveness of marketed and investigational human 
                    <PRTPAGE P="62425"/>
                    drug products for use in the practice of psychiatry and related fields.
                </P>
                <HD SOURCE="HD2">M. Medical Devices Advisory Committee Panels</HD>
                <P>The Medical Devices Advisory Committee has established certain panels to review and evaluate data on the safety and effectiveness of marketed and investigational devices and make recommendations for their regulation. With the exception of the Medical Devices Dispute Resolution Panel, each panel, according to its specialty area: (1) advises on the classification or reclassification of devices into one of three regulatory categories and advises on any possible risks to health associated with the use of devices; (2) advises on formulation of product development protocols; (3) reviews premarket approval applications for medical devices; (4) reviews guidelines and guidance documents; (5) recommends exemption of certain devices from the application of portions of the Federal Food, Drug, and Cosmetic Act; (6) advises on the necessity to ban a device; and (7) responds to requests from the Agency to review and make recommendations on specific issues or problems concerning the safety and effectiveness of devices. With the exception of the Medical Devices Dispute Resolution Panel, each panel, according to its specialty area, may also make appropriate recommendations to the Commissioner on issues relating to the design of clinical studies regarding the safety and effectiveness of marketed and investigational devices.</P>
                <P>The Dental Products Panel reviews and evaluates data concerning the safety and effectiveness of marketed and investigational products for use in dentistry, endodontics or bone physiology relative to the oral and maxillofacial area.</P>
                <P>The Medical Devices Dispute Resolution Panel provides advice to the Commissioner on complex or contested scientific issues between FDA and medical device sponsors, applicants, or manufacturers relating to specific products, marketing applications, regulatory decisions and actions by FDA, and Agency guidance and policies. The Panel makes recommendations on issues that are lacking resolution, are highly complex in nature, or result from challenges to regular advisory panel proceedings or Agency decisions or actions.</P>
                <HD SOURCE="HD2">N. National Mammography Quality Assurance Advisory Committee</HD>
                <P>Advises the Agency on the development of appropriate quality standards and regulations for mammography facilities; standards and regulations for bodies accrediting mammography facilities under this program; regulations with respect to sanctions; procedures for monitoring compliance with standards; establishing a mechanism to investigate consumer complaints; reporting new developments concerning breast imaging that should be considered in the oversight of mammography facilities. The Committee also advises on determining whether there exists a shortage of mammography facilities in rural and health professional shortage areas and determining the effects of personnel on access to the services of such facilities in such areas; determining whether there will be a sufficient number of medical physicists after October 1, 1999; and determining the costs and benefits of compliance with these requirements.</P>
                <HD SOURCE="HD1">II. Criteria for Members</HD>
                <P>Persons nominated for membership as consumer representatives on committees or panels should meet the following criteria: (1) demonstrate an affiliation with and/or active participation in consumer or community-based organizations, (2) be able to analyze technical data, (3) understand research design, (4) discuss benefits and risks, and (5) evaluate the safety and efficacy of products under review. The consumer representative should be able to represent the consumer perspective on issues and actions before the advisory committee; serve as a liaison between the committee and interested consumers, associations, coalitions, and consumer organizations; and facilitate dialogue with the advisory committees on scientific issues that affect consumers.</P>
                <HD SOURCE="HD1">III. Selection Procedures</HD>
                <P>
                    Selection of members representing consumer interests is conducted through procedures that include the use of organizations representing the public interest and public advocacy groups. These organizations recommend nominees for the Agency's selection. Representatives from the consumer health branches of Federal, State, and local governments also may participate in the selection process. Any consumer organization interested in participating in the selection of an appropriate voting or nonvoting member to represent consumer interests should send a letter stating that interest to FDA (see 
                    <E T="02">ADDRESSES</E>
                    ) within 30 days of publication of this document.
                </P>
                <P>Within the subsequent 45 days, FDA will compile a list of consumer organizations that will participate in the selection process and will forward to each such organization a ballot listing at least two qualified nominees selected by the Agency based on the nominations received, together with each nominee's current curriculum vitae or résumé. Ballots are to be filled out and returned to FDA within 30 days. The nominee receiving the highest number of votes ordinarily will be selected to serve as the member representing consumer interests for that particular advisory committee or panel.</P>
                <HD SOURCE="HD1">IV. Nomination Procedures</HD>
                <P>
                    Any interested person or organization may nominate one or more qualified persons to represent consumer interests on the Agency's advisory committees or panels. Self-nominations are also accepted. Nominations must include a current, complete résumé or curriculum vitae for each nominee and a signed copy of the 
                    <E T="03">Acknowledgement and Consent</E>
                     form available at the FDA Advisory Nomination Portal (see 
                    <E T="02">ADDRESSES</E>
                    ), and a list of consumer or community-based organizations for which the candidate can demonstrate active participation.
                </P>
                <P>Nominations must also specify the advisory committee(s) or panel(s) for which the nominee is recommended. In addition, nominations must also acknowledge that the nominee is aware of the nomination unless self-nominated. FDA will ask potential candidates to provide detailed information concerning such matters as financial holdings, employment, and research grants and/or contracts to permit evaluation of possible sources of conflicts of interest. Members will be invited to serve for terms of up to 4 years.</P>
                <P>FDA will review all nominations received within the specified timeframes and prepare a ballot containing the names of qualified nominees. Names not selected will remain on a list of eligible nominees and be reviewed periodically by FDA to determine continued interest. After selecting qualified nominees for the ballot, FDA will provide those consumer organizations that are participating in the selection process with the opportunity to vote on the listed nominees. Only organizations vote in the selection process. Persons who nominate themselves to serve as voting or nonvoting consumer representatives will not participate in the selection process.</P>
                <P>This notice is issued under the Federal Advisory Committee Act (5 U.S.C. app. 2) and 21 CFR part 14, relating to advisory committees.</P>
                <SIG>
                    <PRTPAGE P="62426"/>
                    <DATED>Dated: October 6, 2022.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22305 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2021-N-1026]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Submission for Office of Management and Budget Review; Comment Request; Text Analysis of Proprietary Drug Name Interpretations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA, Agency, or we) is announcing that a proposed collection of information has been submitted to the Office of Management and Budget (OMB) for review and clearance under the Paperwork Reduction Act of 1995.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit written comments (including recommendations) on the collection of information by November 14, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        To ensure that comments on the information collection are received, OMB recommends that written comments be submitted to 
                        <E T="03">https://www.reginfo.gov/public/do/PRAMain.</E>
                         Find this particular information collection by selecting “Currently under Review—Open for Public Comments” or by using the search function. The title of this information collection is “Text Analysis of Proprietary Drug Name Interpretations.” Also include the FDA docket number found in brackets in the heading of this document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        JonnaLynn Capezzuto, Office of Operations, Food and Drug Administration, Three White Flint North, 10A-12M, 11601 Landsdown St., North Bethesda, MD 20852, 301-796-3794, 
                        <E T="03">PRAStaff@fda.hhs.gov.</E>
                    </P>
                    <P>
                        <E T="03">For copies of the questionnaire:</E>
                         Office of Prescription Drug Promotion (OPDP) Research Team, 
                        <E T="03">DTCresearch@fda.hhs.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In compliance with 44 U.S.C. 3507, FDA has submitted the following proposed collection of information to OMB for review and clearance.</P>
                <HD SOURCE="HD1">Text Analysis of Proprietary Drug Name Interpretations</HD>
                <HD SOURCE="HD2">OMB Control Number 0910—NEW</HD>
                <P>Section 1701(a)(4) of the Public Health Service Act (42 U.S.C. 300u(a)(4)) authorizes FDA to conduct research relating to health information. Section 1003(d)(2)(C) of the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) (21 U.S.C. 393(d)(2)(C)) authorizes FDA to conduct research relating to drugs and other FDA-regulated products in carrying out the provisions of the FD&amp;C Act.</P>
                <P>The Office of Prescription Drug Promotion's (OPDP) mission is to protect the public health by helping to ensure that prescription drug promotion is truthful, balanced, and accurately communicated. OPDP's research program provides scientific evidence to help ensure that our policies related to prescription drug promotion will have the greatest benefit to public health. Toward that end, we have consistently conducted research to evaluate the aspects of prescription drug promotion that are most central to our mission. Our research focuses in particular on three main topic areas: advertising features, including content and format; target populations; and research quality. Through the evaluation of advertising features, we assess how elements such as graphics, format, and disease and product characteristics impact the communication and understanding of prescription drug risks and benefits. Focusing on target populations allows us to evaluate how understanding of prescription drug risks and benefits may vary as a function of audience, and our focus on research quality aims at maximizing the quality of research data through analytical methodology development and investigation of sampling and response issues. This study will inform all three topic areas.</P>
                <P>
                    Because we recognize the strength of data and the confidence in the robust nature of the findings are improved through the results of multiple converging studies, we continue to develop evidence to inform our thinking. We evaluate the results from our studies within the broader context of research and findings from other sources, and this larger body of knowledge collectively informs our policies as well as our research program. Our research is documented on our home page, which can be found at 
                    <E T="03">https://www.fda.gov/about-fda/center-drug-evaluation-and-research-cder/office-prescription-drug-promotion-opdp-research.</E>
                     The website includes links to the latest 
                    <E T="04">Federal Register</E>
                     notices and peer-reviewed publications produced by our office.
                </P>
                <P>
                    As part of the prescription drug regulatory review process, sponsors propose proprietary names for their products. These names undergo a proprietary name review that involves the Office of Surveillance and Epidemiology, the relevant medical office, and OPDP. OPDP reviews names to assess for alignment with the FD&amp;C Act, which provides, among other things, that labeling can misbrand a product if false or misleading representations are made (see 21 U.S.C. 321(n) and 352(a)). A proprietary name that appears in labeling could result in such misbranding if it is false or misleading. OPDP reviews, among other things, whether names: (1) overstate the efficacy or safety of the drug, (2) suggest drug indications that are not accurate, (3) suggest superiority without substantiation, or (4) are of a fanciful nature that misleadingly implies unique effectiveness or composition. It would be helpful in OPDP's review of promotional implications of proprietary names for data on consumer and prescriber interpretations of proposed proprietary names to be more readily available for consideration. The proposed research will use text analysis (
                    <E T="03">e.g.,</E>
                     topic modeling and sentiment analysis) to learn how consumer and primary care physician (PCP) populations interpret prescription drug names, which will assist OPDP's consideration of promotional implications.
                </P>
                <P>
                    This proposed research builds upon and extends OPDP's research entitled “Empirical Study of Promotional Implications of Proprietary Prescription Drug Names” (86 FR 14440; March 16, 2021). That research involves an experimental design intended to assess names that potentially overstate the efficacy of a product. In contrast, the proposed research involves a survey design that comprises primarily open-ended questions intended to generate text for analysis, an approach that is unrestricted in its ability to assess text with different types of promotional implications (
                    <E T="03">e.g.,</E>
                     minimization of risk and unsubstantiated claims of superiority, in addition to overstatement of efficacy). The proposed research will add to the depth and breadth of knowledge we can draw from during the review of proposed proprietary drug names.
                </P>
                <P>The key objectives of the proposed research are as follows:</P>
                <P>
                    1. To apply new techniques such as topic modeling and sentiment analysis (forms of text analysis) to answer OPDP's research questions about 
                    <PRTPAGE P="62427"/>
                    consumer and PCP interpretations of proprietary prescription drug names.
                </P>
                <P>2. To help develop a methodological approach for assessing consumer and prescriber interpretations of drug names, which can potentially be used in the future as a standard assessment tool.</P>
                <P>
                    Our methodological approach will involve nationally representative samples. Consumers will be recruited from Ipsos Public Affairs KNOWLEDGEPANEL. PCPs will be recruited using a two-stage approach that will begin with a purchased list of PCPs based on the American Medical Association Physician Masterfile. These members will then be matched to one or more sample provider lists to recruit PCP participants for this study. We propose a sample of 300 consumers and 300 PCPs for the main study. We have designed a within-subjects experiment in which participants will be exposed to multiple drug names to maximize power to find differences with this sample size. The stimuli will comprise 60 experimental names and 60 control names. Participants will be randomized to 1 of 10 groups so that no one responds to more than 12 names in total. Each participant will see six experimental names and six control names. The experimental names will be names with suspected promotional implications, whereas the control names will not have suspected promotional implications. Names will be viewed in random order. Participants will respond in open-ended text boxes about their perceptions of each drug name. Supplementary closed-ended questions may also be presented. We will conduct text analysis of the responses and present descriptive results for individual drug names by participant cohort (
                    <E T="03">i.e.,</E>
                     consumers versus PCPs), and we will also code and compare responses across types of drug names.
                </P>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of November 1, 2021 (86 FR 60254), FDA published a 60-day notice requesting public comment on the proposed collection of information. FDA received two comments that were Paperwork Reduction Act (PRA) related. Within those submissions, FDA received multiple comments that the Agency has addressed. For brevity, some public comments are paraphrased and therefore may not state the exact language used by the commenter. All comments were considered even if they were not fully captured by our paraphrasing in this document. Comments and responses are numbered here for organizational purposes only.
                </P>
                <P>
                    (Comment 1) One comment contended that FDA should revise the questionnaire to capture real-world conditions more closely in which PCPs and consumers form impressions of proprietary names. The comment suggested that while FDA stated that “[t]he experimental names will be names with suspected promotional implications” in the 
                    <E T="04">Federal Register</E>
                     notice, the Agency does not approve proprietary names with “suspected promotional implications.” The comment also stated that FDA's proposed approach would not mimic the real-world conditions in which mention of a drug's indication triggers a requirement to provide safety information as well. The comment suggested that either FDA could consider providing only the drug name in a way that is similar to the information provided in reminder advertising, or it could provide a balanced presentation as required under the relevant regulations.
                </P>
                <P>(Response 1) As previously described, sponsors propose proprietary names for their products, including those with promotional implications, as part of the prescription drug regulatory review process. One purpose of this study is to investigate methodological options for collecting insights from consumers and providers during the review process that might help FDA make determinations about whether drug names have promotional implications that misbrand a product. As for real-world conditions, our initial focus is on establishing correlation or causation in a more controlled setting—such as a randomized controlled trial or the type of rigorous experimental study we have planned.</P>
                <P>(Comment 2) One comment suggested that FDA does not state how the information obtained from the specified study will be useful or how it will be used to inform name reviews. The comment then asserted that the link between this information and the implementation of FDA's misbranding authorities and proprietary name review, and thus the practical utility of the survey, is unclear.</P>
                <P>
                    (Response 2) FDA's review of proprietary names is conducted to help ensure that proposed proprietary names do not contribute to misbranding a drug or to other violation(s) of the FD&amp;C Act and Agency regulations, particularly when that proprietary name appears in labeling. (See, 
                    <E T="03">e.g.,</E>
                     21 U.S.C. 321(n) and 352(a).) We conduct our review of proprietary names in accordance with applicable legal authorities.
                </P>
                <P>The existing study is a first step in exploring the utility of text analysis for collection of data on proprietary prescription drug names. Determining how names are processed and understood by consumers and healthcare providers (HCPs) is important information to be considered in the review of proposed prescription drug names. This program of research is being conducted to increase the body of evidence upon which experts can rely when assessing proposed proprietary names.</P>
                <P>(Comment 3) One comment stated that FDA should revise question 1. The comment advised that the instructions should make clear that the respondent can write “no impression” if the name does not, in the respondent's view, communicate any information related to the particular attribute of the drug. In addition, the comment stated that the last question, asking respondents to write a brief narrative, is confusing and unnecessary and that the objective and practical utility of this exercise are unclear.</P>
                <P>(Response 3) It was clear in our cognitive interviews that if respondents had no impression based on a drug name, they would be likely to type “nothing” or “no impression” as their response. The purpose of the last exercise is to examine the utility of an implicit measure of attitudes for comparison with the more explicit measures. If this measure proves to be unproductive in pre-testing, we may omit it from the main study. For instance, this implicit measure might be considered unproductive if it does not prompt any additional, unique text relative to what is offered in response to the earlier open-ended items.</P>
                <P>(Comment 4) Two comments similarly claimed that questions two through six are leading, potentially confusing, duplicative of another question, or otherwise unnecessary. One comment recommended removing these questions.</P>
                <P>(Response 4) These questions have been included as a way of validating the information recorded in question one. Based on other comments, such as one that challenged the use of yes/no questions, we have revised them to a 5-point Likert scale, ranging from strongly disagree to strongly agree. We will assess these questions further as part of pre-testing.</P>
                <P>
                    (Comment 5) One comment stated that FDA should limit patient and PCP participation to those who have experience with the fictitious drug indications. It further asserted that FDA should provide detail on how the patients and PCPs will be selected and how FDA will help ensure these participants have relevant experience. The comment suggested that FDA could add an open-ended question requesting that PCPs provide information about 
                    <PRTPAGE P="62428"/>
                    their experiences in the disease areas for which the fictitious drugs are intended, patient populations, and settings to understand the real-world value of the responses.
                </P>
                <P>(Response 5) Due to the large number of drug names and indications to be included in this study, the comment's suggestion is not feasible. However, we will add a measure to the screener to assess PCPs' and consumers' experiences with each of the indications. This variable can then be used as a covariate in analyses.</P>
                <P>(Comment 6) One comment suggested that to ensure that the survey isolates the impressions given by the proprietary name, FDA should use only fictitious names for the survey.</P>
                <P>(Response 6) We have removed all real drug names from the study and replaced them with fictitious names.</P>
                <P>(Comment 7) One comment recommended removing all yes/no questions from the survey.</P>
                <P>(Response 7) We have done so, changing the yes/no items to Likert scale items.</P>
                <P>(Comment 8) One comment recommended that FDA should acknowledge that proposed names may include “permissible suggestions” and should include such fictitious examples. The comment conjectured that the survey appears to focus only on potential impermissible suggestions that may result from a drug's proprietary name. The comment submitted that proposed names should also be included that, for example, suggest the dosage form, frequency of delivery, structure of the drug, or general category of the drug's indications.</P>
                <P>
                    (Response 8) A previous study by this research team did include names such as those suggested above (
                    <E T="03">e.g.,</E>
                     with the drug's indication embedded in the name). Those names are not included here to avoid duplication.
                </P>
                <P>(Comment 9) One comment stated that FDA should explain its methodology for the text analysis and allow for stakeholder feedback on the proposed text analysis methodology.</P>
                <P>(Response 9) We will examine and present descriptive results for individual names. However, given our goals of understanding promotional implications of prescription drug names across consumers and PCPs, we are also interested in whether there are differences in topic distributions across our treatment and control arms (control versus promotional implications) and between populations (consumers and PCPs). We will use topic modeling and sentiment analysis to answer those questions. We have described the purpose of the study, the design, and the population of interest, and we have provided the questionnaire to numerous individuals upon request.</P>
                <P>(Comment 10) One comment expressed concerns about how degrees or levels of misbranding may be established or standardized for evaluating proposed proprietary prescription drug names. It stated that no information has yet been provided by FDA to inform how such standardization will be developed.</P>
                <P>(Response 10) This study is not intended either to establish degrees or levels of misbranding or to standardize levels of misbranding for the evaluation of proposed drug names. The key objectives of the proposed research are to apply new techniques such as topic modeling and sentiment analysis to answer OPDP's research questions about consumer and PCP interpretations of proprietary prescription drug names and to help develop a methodological approach for assessing consumer and prescriber interpretations of drug names.</P>
                <P>(Comment 11) A comment objected that FDA has not provided any information on how it will select target names to include in the pre-test and subsequently decide which target names will be used in the main study. The comment expressed concerns that the pre-test will not be able to develop multiple distinct levels of efficacy or indication implication among target names that will be reliably identifiable by HCPs or consumers. The comment asserted that a proprietary name may not be reliably classified and separated into multiple levels of implication.</P>
                <P>(Response 11) Our full stimuli are under development during the PRA process. We do not make draft stimuli public during this time because of concerns that this may contaminate our participant pool and compromise our research. In our research proposals, we describe the purpose of the study, the design, the population of interest, and the estimated burden.</P>
                <P>
                    Names will be intentionally developed to have promotional implications (
                    <E T="03">e.g.,</E>
                     overstatement of efficacy). Many of the names were used in our cognitive interviews. In addition, we will conduct up to two pre-tests, at which point, if any names are not distinguishable from those composed of random syllables, they will be replaced. A similar process was used in another recent study, with reliable results. Participants did distinguish between names created from random syllables and those with promotional implications.
                </P>
                <P>(Comment 12) One comment advised that the pronunciation offered to a respondent would influence a respondent's impressions and that it would be important for FDA to control for this influence. The comment opined that the pronunciation should result in as neutral a reading as possible, not emphasizing any particular aspect of a name.</P>
                <P>(Response 12) All drug names were recorded by the same voiceover specialist in as neutral a manner as possible.</P>
                <P>(Comment 13) A comment similarly asserted that the impression formed from a visual cue (drug name written out) would influence and be influenced by an audio cue and vice versa. The comment contended that there would be less bias introduced by listening first to an audio cue. The comment also recommended that an audio cue first be provided, followed by the question about hearing the name, and that the visual image of the name would be presented followed by the question about seeing the name.</P>
                <P>(Response 13) We agree that people access both the orthographic and phonological interpretations when they read. However, since our main comparison is within subjects, it is likely that there is some consistency in the order in which any one respondent listens to the pronunciation versus reading the word, and so any variation that may exist should not confound the effects of their own interpretation of the drug names. In addition, the comment's suggestion would double the number of open-ended questions for every drug name, increasing the survey burden substantially.</P>
                <P>(Comment 14) One comment suggested altering the order of the prompts so that after gaining impressions following the audio and visual cues, the brief story or narrative prompt follows.</P>
                <P>(Response 14) The currently proposed questionnaire follows this order.</P>
                <P>(Comment 15) One comment argued that prompts should not be “double-barreled” and should not lead or prime the respondent to find benefits or other meanings where there may be none. The comment suggested that questions should ask separately about benefits and how well the drug would work and then also ask separately about risks and side effects. The comment suggested rephrasing to “Does the drug name suggest the drug may have a benefit?” or “Does the drug name make you think about how well it might work?”.</P>
                <P>
                    (Response 15) We have edited the open-ended section of the study so that these questions are no longer separate items but merely instructions preceding the first question. The phrasing the 
                    <PRTPAGE P="62429"/>
                    comment suggested is likely to lead to one-word answers “yes” or “no,” which does not provide the type of text response that is needed to conduct text analysis on the data. We did find in cognitive interviews that participants who did not perceive any meaning from a specific drug name said they would be likely to type “nothing” into the open-ended text box. Thus, we believe the study in its current form does allow for this possibility.
                </P>
                <P>(Comment 16) One comment suggested very general questions should be asked first and then those that are more specific.</P>
                <P>(Response 16) We have ordered the prompts from general to specific in line with the suggested comment.</P>
                <P>(Comment 17) One comment proposed that researchers may want to consider reducing the number of drugs queried in the survey from 12 to 6 to elicit the richest text data from respondents and that it may be helpful to give a minimum word count for text responses.</P>
                <P>(Response 17) Six drugs will not allow for enough power to make comparisons between the groups. However, if we find that we get many breakoffs (participants who begin the survey but do not complete it) in the pre-test (suggesting the survey burden is too high), we will reconsider the study design.</P>
                <P>(Comment 18) One comment recommended that an iterative plan for analysis be developed such that there are checks for both internal and external validity at specified intervals. It further proposed that researchers may want to consider a context-specific analysis plan and argued that one common analysis approach or dictionary may not measure risk, side effects, and other constructs accurately across all drugs.</P>
                <P>(Response 18) Though the topic modeling approach is designed to be exploratory for this study, we will calculate coherence metrics to assess model fit as well as perform validation exercises to assess if the generated topics can be easily interpreted.</P>
                <P>(Comment 19) One comment recommended that an iterative plan for analysis be created based on a set of preliminary data along with the other research materials, such as the questionnaire, sampling plan, etc., so that it can be reviewed before execution of the full research.</P>
                <P>(Response 19) We appreciate the comment. The pre-test will provide the valuable insight to create a specific analysis plan for the main study. The pilot data will help us assess assumptions about how respondents will respond to target names.</P>
                <P>FDA estimates the burden of this collection of information as follows:</P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12,12,12,xs72,12">
                    <TTITLE>
                        Table 1—Estimated Annual Reporting Burden 
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">Activity</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses per</LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">
                            Average burden
                            <LI>per response</LI>
                        </CHED>
                        <CHED H="1">Total hours</CHED>
                    </BOXHD>
                    <ROW EXPSTB="05" RUL="s">
                        <ENT I="21">
                            <E T="02">General Consumer Population</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Pretest 1 screener (assumes 80% eligible)</ENT>
                        <ENT>22</ENT>
                        <ENT>1</ENT>
                        <ENT>22</ENT>
                        <ENT>0.08 (5 minutes)</ENT>
                        <ENT>1.8</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pretest 1 survey</ENT>
                        <ENT>17</ENT>
                        <ENT>1</ENT>
                        <ENT>17</ENT>
                        <ENT>0.33 (20 minutes)</ENT>
                        <ENT>5.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pretest 2 screener (assumes 80% eligible)</ENT>
                        <ENT>22</ENT>
                        <ENT>1</ENT>
                        <ENT>22</ENT>
                        <ENT>0.08 (5 minutes)</ENT>
                        <ENT>1.8</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pretest 2 survey</ENT>
                        <ENT>17</ENT>
                        <ENT>1</ENT>
                        <ENT>17</ENT>
                        <ENT>0.33 (20 minutes)</ENT>
                        <ENT>5.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Main study screener (assumes 80% eligible)</ENT>
                        <ENT>413</ENT>
                        <ENT>1</ENT>
                        <ENT>413</ENT>
                        <ENT>0.08 (5 minutes)</ENT>
                        <ENT>33</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Main study survey completes</ENT>
                        <ENT>330</ENT>
                        <ENT>1</ENT>
                        <ENT>330</ENT>
                        <ENT>0.33 (20 minutes)</ENT>
                        <ENT>10 8.9</ENT>
                    </ROW>
                    <ROW EXPSTB="05" RUL="s">
                        <ENT I="21">
                            <E T="02">PCP Population</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Pretest 1 screener (assumes 30% eligible)</ENT>
                        <ENT>57</ENT>
                        <ENT>1</ENT>
                        <ENT>57</ENT>
                        <ENT>0.08 (5 minutes)</ENT>
                        <ENT>4.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pretest 1 survey</ENT>
                        <ENT>17</ENT>
                        <ENT>1</ENT>
                        <ENT>17</ENT>
                        <ENT>0.33 (20 minutes)</ENT>
                        <ENT>5.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pretest 2 screener (assumes 30% eligible)</ENT>
                        <ENT>57</ENT>
                        <ENT>1</ENT>
                        <ENT>57</ENT>
                        <ENT>0.08 (5 minutes)</ENT>
                        <ENT>4.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pretest 2 survey</ENT>
                        <ENT>17</ENT>
                        <ENT>1</ENT>
                        <ENT>17</ENT>
                        <ENT>0.33 (20 minutes)</ENT>
                        <ENT>5.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Main study screener (assumes 30% eligible)</ENT>
                        <ENT>1,100</ENT>
                        <ENT>1</ENT>
                        <ENT>1,100</ENT>
                        <ENT>0.08 (5 minutes)</ENT>
                        <ENT>88</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Main study survey completes</ENT>
                        <ENT>330</ENT>
                        <ENT>1</ENT>
                        <ENT>330</ENT>
                        <ENT>0.33 (20 minutes)</ENT>
                        <ENT>108.9</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>374</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         There are no capital costs or operating and maintenance costs associated with this collection of information.
                    </TNOTE>
                </GPOTABLE>
                <P>As with most online and mail surveys, it is always possible that some participants are in the process of completing the survey when the target number is reached and that those surveys will be completed and received before the survey is closed out. To account for this, we have estimated approximately 10 percent overage for both samples in the study.</P>
                <SIG>
                    <DATED>Dated: October 5, 2022.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22301 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2013-N-1619]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Proposed Collection; Comment Request; Current Good Manufacturing Practice in Manufacturing, Packaging, Labeling, or Holding Operations for Dietary Supplements</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Food and Drug Administration (FDA, Agency, or we) is announcing an opportunity for public comment on the proposed collection of certain information by the Agency. Under the Paperwork Reduction Act of 1995 (PRA), Federal Agencies are required to publish notice in the 
                        <E T="04">Federal Register</E>
                         concerning each proposed collection of information, including each proposed extension of an existing collection of information, and to allow 60 days for public comment in response to the notice. This notice solicits comments on the information collection provisions of FDA's regulations regarding current good 
                        <PRTPAGE P="62430"/>
                        manufacturing practice (CGMP) for dietary supplements.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Either electronic or written comments on the collection of information must be submitted by December 13, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments as follows. Please note that late, untimely filed comments will not be considered. The 
                        <E T="03">https://www.regulations.gov</E>
                         electronic filing system will accept comments until 11:59 p.m. Eastern Time at the end of December 13, 2022. Comments received by mail/hand delivery/courier (for written/paper submissions) will be considered timely if they are postmarked or the delivery service acceptance receipt is on or before that date.
                    </P>
                </ADD>
                <HD SOURCE="HD2">Electronic Submissions</HD>
                <P>Submit electronic comments in the following way:</P>
                <P>
                    • 
                    <E T="03">Federal eRulemaking Portal: https://www.regulations.gov.</E>
                     Follow the instructions for submitting comments. Comments submitted electronically, including attachments, to 
                    <E T="03">https://www.regulations.gov</E>
                     will be posted to the docket unchanged. Because your comment will be made public, you are solely responsible for ensuring that your comment does not include any confidential information that you or a third party may not wish to be posted, such as medical information, your or anyone else's Social Security number, or confidential business information, such as a manufacturing process. Please note that if you include your name, contact information, or other information that identifies you in the body of your comments, that information will be posted on 
                    <E T="03">https://www.regulations.gov.</E>
                </P>
                <P>• If you want to submit a comment with confidential information that you do not wish to be made available to the public, submit the comment as a written/paper submission and in the manner detailed (see “Written/Paper Submissions” and “Instructions”).</P>
                <HD SOURCE="HD2">Written/Paper Submissions</HD>
                <P>Submit written/paper submissions as follows:</P>
                <P>
                    • 
                    <E T="03">Mail/Hand Delivery/Courier (for written/paper submissions):</E>
                     Dockets Management Staff (HFA-305), Food and Drug Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.
                </P>
                <P>• For written/paper comments submitted to the Dockets Management Staff, FDA will post your comment, as well as any attachments, except for information submitted, marked and identified, as confidential, if submitted as detailed in “Instructions.”</P>
                <P>
                    <E T="03">Instructions:</E>
                     All submissions received must include the Docket No. FDA-2013-N-1619 for “Agency Information Collection Activities; Proposed Collection; Comment Request; Current Good Manufacturing Practice in Manufacturing, Packaging, Labeling, or Holding Operations for Dietary Supplements.” Received comments, those filed in a timely manner (see 
                    <E T="02">ADDRESSES</E>
                    ), will be placed in the docket and, except for those submitted as “Confidential Submissions,” publicly viewable at 
                    <E T="03">https://www.regulations.gov</E>
                     or at the Dockets Management Staff between 9 a.m. and 4 p.m., Monday through Friday, 240-402-7500.
                </P>
                <P>
                    • Confidential Submissions—To submit a comment with confidential information that you do not wish to be made publicly available, submit your comments only as a written/paper submission. You should submit two copies total. One copy will include the information you claim to be confidential with a heading or cover note that states “THIS DOCUMENT CONTAINS CONFIDENTIAL INFORMATION.” The Agency will review this copy, including the claimed confidential information, in its consideration of comments. The second copy, which will have the claimed confidential information redacted/blacked out, will be available for public viewing and posted on 
                    <E T="03">https://www.regulations.gov.</E>
                     Submit both copies to the Dockets Management Staff. If you do not wish your name and contact information to be made publicly available, you can provide this information on the cover sheet and not in the body of your comments and you must identify this information as “confidential.” Any information marked as “confidential” will not be disclosed except in accordance with 21 CFR 10.20 and other applicable disclosure law. For more information about FDA's posting of comments to public dockets, see 80 FR 56469, September 18, 2015, or access the information at: 
                    <E T="03">https://www.govinfo.gov/content/pkg/FR-2015-09-18/pdf/2015-23389.pdf.</E>
                </P>
                <P>
                    <E T="03">Docket:</E>
                     For access to the docket to read background documents or the electronic and written/paper comments received, go to 
                    <E T="03">https://www.regulations.gov</E>
                     and insert the docket number, found in brackets in the heading of this document, into the “Search” box and follow the prompts and/or go to the Dockets Management Staff, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852, 240-402-7500.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Amber Sanford, Office of Operations, Food and Drug Administration, Three White Flint North, 10A-12M, 11601 Landsdown St., North Bethesda, MD 20852, 301-796-8867, 
                        <E T="03">PRAStaff@fda.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Under the PRA (44 U.S.C. 3501-3521), Federal Agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. “Collection of information” is defined in 44 U.S.C. 3502(3) and 5 CFR 1320.3(c) and includes Agency requests or requirements that members of the public submit reports, keep records, or provide information to a third party. Section 3506(c)(2)(A) of the PRA (44 U.S.C. 3506(c)(2)(A)) requires Federal Agencies to provide a 60-day notice in the 
                    <E T="04">Federal Register</E>
                     concerning each proposed collection of information, including each proposed extension of an existing collection of information, before submitting the collection to OMB for approval. To comply with this requirement, FDA is publishing notice of the proposed collection of information set forth in this document.
                </P>
                <P>With respect to the following collection of information, FDA invites comments on these topics: (1) whether the proposed collection of information is necessary for the proper performance of FDA's functions, including whether the information will have practical utility; (2) the accuracy of FDA's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used; (3) ways to enhance the quality, utility, and clarity of the information to be collected; and (4) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques, when appropriate, and other forms of information technology.</P>
                <HD SOURCE="HD1">Current Good Manufacturing Practice in Manufacturing, Packaging, Labeling, or Holding Operations for Dietary Supplements—21 CFR Part 111</HD>
                <HD SOURCE="HD2">OMB Control Number 0910-0606—Extension</HD>
                <P>
                    The Dietary Supplement Health and Education Act (DSHEA) (Pub. L. 103-417) added section 402(g) of the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) (21 U.S.C. 342(g)), which provides, in part, that the Secretary of Health and Human Services may, by regulation, prescribe good manufacturing practice for dietary supplements. Section 402(g) of the FD&amp;C Act also stipulates that such regulations will be modeled after CGMP regulations for food and may not impose standards for which there are no current, and generally available, 
                    <PRTPAGE P="62431"/>
                    analytical methodology. Section 402(g)(1) of the FD&amp;C Act states that a dietary supplement is adulterated if it has been prepared, packed, or held under conditions that do not meet current good manufacturing practice regulations.
                </P>
                <P>Accordingly, we have promulgated regulations in part 111 (21 CFR part 111) establishing minimum CGMP requirements pertaining to the manufacturing, packaging, labeling, or holding of dietary supplements to ensure their quality. Included among the requirements is recordkeeping, documenting, planning, control, and improvement processes of a quality control system. Implementation of these processes in a manufacturing operation serves as the backbone to CGMP. The records must show what is being manufactured and whether the controls in place ensure the product's identity, purity, strength, and composition and that limits on contaminants and measures to prevent adulteration are effective. Further, records must show whether and what deviations from control processes occurred, facilitate evaluation and corrective action concerning these deviations (including, where necessary, whether associated batches of product should be recalled from the marketplace), and enable a manufacturer to assure that the corrective action was effective. We believe the regulations in part 111 establish the minimum manufacturing practices necessary to ensure that dietary supplements are manufactured, packaged, labeled, or held in a manner that will ensure the quality of the dietary supplements during manufacturing, packaging, labeling, or holding operations.</P>
                <P>Specifically, the recordkeeping requirements of the regulations in part 111 include establishing written procedures and maintaining records pertaining to: (1) personnel; (2) sanitation; (3) calibration of instruments and controls; (4) calibration, inspection, or checks of automated, mechanical, or electronic equipment; (5) maintaining, cleaning, and sanitizing equipment and utensils and other contact surfaces; (6) water used that may become a component of the dietary supplement; (7) production and process controls; (8) quality control; (9) components, packaging, labels and product received for packaging and labeling; (10) master manufacturing and batch production; (11) laboratory operations; (12) manufacturing operations; (13) packaging and labeling operations; (14) holding and distributing operations; (15) returned dietary supplements; and (16) product complaints.</P>
                <P>Section 111.75(a)(1) (21 CFR 111.75(a)(1)) reflects FDA's determination that manufacturers that test or examine 100 percent of the incoming dietary ingredients for identity can be assured of the identity of the ingredient. However, we recognize that it may be possible for a manufacturer to demonstrate, through various methods and processes in use over time for its particular operation, that a system of less than 100 percent identity testing would result in no material diminution of assurance of the identity of the dietary ingredient as compared to the assurance provided by 100 percent identity testing. Section 111.75(a)(1) provides an opportunity for a manufacturer to make such a showing and reduce the frequency of identity testing of components that are dietary ingredients from 100 percent to some lower frequency. Section 111.75(a)(1) also sets forth the information a manufacturer is required to submit for an exemption from the requirement of 100 percent identity testing when a manufacturer petitions the Agency for such an exemption to 100 percent identity testing under 21 CFR 10.30 and the Agency grants such exemption.</P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     Respondents to this collection of information include manufacturers, packagers and repackagers, labelers and re-labelers, holders, distributors, warehousers, exporters, importers, large businesses, and small businesses engaged in the dietary supplement industry. Respondents are from the private sector (for-profit businesses).
                </P>
                <P>We estimate the burden of this collection of information as follows:</P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12,12,12,xs70,8">
                    <TTITLE>
                        Table 1—Estimated Annual Recordkeeping Burden 
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">21 CFR section; activity</CHED>
                        <CHED H="1">
                            Number of
                            <LI>recordkeepers</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>records per</LI>
                            <LI>recordkeeper</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual
                            <LI>records</LI>
                        </CHED>
                        <CHED H="1">
                            Average burden
                            <LI>per recordkeeping</LI>
                        </CHED>
                        <CHED H="1">
                            Total
                            <LI>hours</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">111.14; records of personnel practices, including documentation of training</ENT>
                        <ENT>15,000</ENT>
                        <ENT>4</ENT>
                        <ENT>60,000</ENT>
                        <ENT>1</ENT>
                        <ENT>60,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">111.23; records of physical plant sanitation practices, including pest control and water quality</ENT>
                        <ENT>15,000</ENT>
                        <ENT>1</ENT>
                        <ENT>15,000</ENT>
                        <ENT>0.2 (12 minutes)</ENT>
                        <ENT>3,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">111.35; records regarding equipment and utensils, including calibration and sanitation practices</ENT>
                        <ENT>400</ENT>
                        <ENT>1</ENT>
                        <ENT>400</ENT>
                        <ENT>12.5</ENT>
                        <ENT>5,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">111.95; records of production and process control systems</ENT>
                        <ENT>250</ENT>
                        <ENT>1</ENT>
                        <ENT>250</ENT>
                        <ENT>45</ENT>
                        <ENT>11,250</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">111.140; records that quality control personnel must make and keep</ENT>
                        <ENT>240</ENT>
                        <ENT>1,163</ENT>
                        <ENT>279,120</ENT>
                        <ENT>1</ENT>
                        <ENT>279,120</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">111.180; records associated with components, packaging, labels, and product received for packaging and labeling as a dietary supplement</ENT>
                        <ENT>240</ENT>
                        <ENT>1,163</ENT>
                        <ENT>279,120</ENT>
                        <ENT>1</ENT>
                        <ENT>279,120</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">111.210; requirements for what the master manufacturing record must include</ENT>
                        <ENT>240</ENT>
                        <ENT>1</ENT>
                        <ENT>240</ENT>
                        <ENT>2.5</ENT>
                        <ENT>600</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">111.260; requirements for what the batch production record must include</ENT>
                        <ENT>145</ENT>
                        <ENT>1,408</ENT>
                        <ENT>204,160</ENT>
                        <ENT>1</ENT>
                        <ENT>204,160</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">111.325; records that quality control personnel must make and keep for laboratory operations</ENT>
                        <ENT>120</ENT>
                        <ENT>1</ENT>
                        <ENT>120</ENT>
                        <ENT>15</ENT>
                        <ENT>1,800</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">111.375; records of the written procedures established for manufacturing operations</ENT>
                        <ENT>260</ENT>
                        <ENT>1</ENT>
                        <ENT>260</ENT>
                        <ENT>2</ENT>
                        <ENT>520</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">111.430; records of the written procedures for packaging and labeling operations</ENT>
                        <ENT>50</ENT>
                        <ENT>1</ENT>
                        <ENT>50</ENT>
                        <ENT>12.6</ENT>
                        <ENT>630</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">111.475; records of product distribution and procedures for holding and distributing operations</ENT>
                        <ENT>15,000</ENT>
                        <ENT>1</ENT>
                        <ENT>15,000</ENT>
                        <ENT>0.4 (24 minutes)</ENT>
                        <ENT>6,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">111.535; records for returned dietary supplements</ENT>
                        <ENT>110</ENT>
                        <ENT>4</ENT>
                        <ENT>440</ENT>
                        <ENT>13.5</ENT>
                        <ENT>5,940</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">111.570; records regarding product complaints</ENT>
                        <ENT>240</ENT>
                        <ENT>600</ENT>
                        <ENT>144,000</ENT>
                        <ENT>0.5 (30 minutes)</ENT>
                        <ENT>72,000</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="62432"/>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>929,140</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         There are no capital costs or operating and maintenance costs associated with this collection of information.
                    </TNOTE>
                </GPOTABLE>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12C,12C,12C,12C,8C">
                    <TTITLE>
                        Table 2—Estimated Annual Reporting Burden 
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">21 CFR section; activity</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses per</LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>burden</LI>
                            <LI>per response</LI>
                        </CHED>
                        <CHED H="1">Total hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">111.75; petition for exemption from 100 percent identity testing</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>8</ENT>
                        <ENT>8</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         There are no capital costs or operating and maintenance costs associated with this collection of information.
                    </TNOTE>
                </GPOTABLE>
                <P>Based on a review of the information collection since our last request for OMB approval, we have made no adjustments to our burden estimate. We base our estimates for the recordkeeping and reporting burdens on our experience with the recordkeeping and petition activities.</P>
                <SIG>
                    <DATED>Dated: October 5, 2022.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22303 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <DEPDOC>[Document Identifier OS-0945-New]</DEPDOC>
                <SUBJECT>Agency Information Collection Request; 30-Day 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 the requirement of the Paperwork Reduction Act of 1995, the Office of the Secretary (OS), Department of Health and Human Services, is publishing the following summary of a proposed collection for public comment.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on the ICR must be received on or before November 14, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments and recommendations for the proposed information collection should be sent within 30 days of publication of this notice to 
                        <E T="03">www.reginfo.gov/public/do/PRAMain</E>
                        . Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Sherrette Funn, 
                        <E T="03">Sherrette.Funn@hhs.gov</E>
                         or (202) 264-0041. When submitting comments or requesting information, please include the document identifier 0945-New-30D and project title for reference.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Interested persons are invited to send comments regarding this burden estimate or any other aspect of this collection of information, including any of the following subjects: (1) The necessity and utility of the proposed information collection for the proper performance of the agency's functions; (2) the accuracy of the estimated burden; (3) ways to enhance the quality, utility, and clarity of the information to be collected; and (4) the use of automated collection techniques or other forms of information technology to minimize the information collection burden.</P>
                <P>
                    <E T="03">Title of the Collection:</E>
                     Nondiscrimination in Health Programs and Activities.
                </P>
                <P>
                    <E T="03">Type of Collection:</E>
                     New.
                </P>
                <P>
                    <E T="03">OMB No.:</E>
                     0990-XXXX or 0990-NEW—Office for Civil Rights.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This Information Collection Request is for a new collection of information as proposed in the Department of Health and Human Services (HHS) Office for Civil Rights (OCR) Notice of Proposed Rulemaking (NPRM) entitled Nondiscrimination in Health Programs and Activities (RIN: 0945-AA17). The purpose of this information collection is to ensure covered entities (any health program or activity, any part of which is receiving federal financial assistance from the Department and any health program or activity conducted by the Department or Title I entity) adhere to the statutory requirements under Section 1557. The proposed information collection helps covered entities demonstrate compliance with federal civil rights laws and their awareness of their obligations under those laws and respective HHS implementing regulations.
                </P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,12,12,12,12">
                    <TTITLE>Estimated Annualized Burden Table</TTITLE>
                    <BOXHD>
                        <CHED H="1">Type of respondent</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number
                            <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
                            <LI>burden hours</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Recipients &amp; State-based Exchanges with 15 or more employees</ENT>
                        <ENT>41,250</ENT>
                        <ENT>1</ENT>
                        <ENT>10</ENT>
                        <ENT>412,500</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Recipients &amp; State-based Exchanges</ENT>
                        <ENT>275,002</ENT>
                        <ENT>1</ENT>
                        <ENT>1.75</ENT>
                        <ENT>481,254</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT>316,252</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>893,754</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <PRTPAGE P="62433"/>
                    <NAME>Sherrette A. Funn,</NAME>
                    <TITLE>Paperwork Reduction Act Reports Clearance Officer, Office of the Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22319 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4153-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBJECT>Establishment of the Medicare Drug Rebate and Negotiations Group Within the Center for Medicare (CM)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services, HHS.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Establish the Medicare Drug Rebate and Negotiations Group within the Center for Medicare (CM) to implement the Drug Price Negotiation Program and the Inflation Rebate Program in Medicare Part B and Part D as authorized under the Inflation Reduction Act of 2022. CMS is responsible for implementing these new programs.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This reorganization was approved by the Secretary of Health and Human Services and takes effect October 8, 2022.</P>
                </DATES>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Statement of Organization, Functions, and Delegations of Authority Part F of the Statement of Organization, Functions, and Delegations of Authority for the Department of Health and Human Services, Centers for Medicare &amp; Medicaid Services (CMS) (last amended at 
                    <E T="04">Federal Register</E>
                    , Vol. 75, No. 56, pp. 14176-14178, dated March 24, 2010; Vol. 76, No. 203, pp. 65197-65199, dated October 20, 2011; Vol. 78, No. 86, p. 26051, dated May 3, 2013; Vol. 79, No. 2, pp. 397-398, dated January 3, 2014; and Vol. 84, No. 32, p. 4470, dated February 15, 2019) is amended to reflect the establishment of the Medicare Drug Rebate and Negotiations Group within the Center for Medicare (CM) to implement the Drug Price Negotiation Program and the Inflation Rebate Program in Medicare Part B and Part D as authorized under the Inflation Reduction Act of 2022. CMS is responsible for implementing these new programs.
                </P>
                <P>Title I, Subtitle B, Part 1, sections 11001-11004, of the Inflation Reduction Act of 2022 (IRA) Public Law 117-169 enacted on August 16, 2022, establishes a new Drug Price Negotiation Program under Medicare Part B and Medicare Part D to lower prices for certain high-spend single source drugs. Title I, Subtitle B, sections 11101 and 11102 of the IRA also enacts a new program to establish Inflation Rebates in Medicare Part B and Medicare Part D. CMS is responsible for implementing these new programs.</P>
                <P>The work required to implement and administer these new programs will be novel and differ significantly from the Medicare functions that CMS performs today. Given the unique nature of this new work, there is not an existing operating component, group, office or division in CMS or CM that performs these actions. Moreover, the scope and complexity of these new programs, and the deadlines for implementation, require that a new, dedicated organization be established to ensure that CMS is able to implement these programs successfully and on time. In order to implement and operate these new programs, CMS is creating a new group—the Medicare Drug Rebate and Negotiations Group—within CM.</P>
                <P>Part F, Section FC. 10 (Organization) is revised as follows:</P>
                <FP SOURCE="FP-1">Center for Medicare, Medicare Drug Rebate and Negotiations Group</FP>
                <P>Part F, Section FC. 20 (Functions) for the new organization is as follows:</P>
                <HD SOURCE="HD1">Medicare Drug Rebate and Negotiations Group</HD>
                <P>With regard to the Drug Price Negotiation Program, each year, the new group will negotiate drug prices with pharmaceutical manufacturers for certain Part B and Part D drugs. This will require identifying negotiation-eligible drugs, entering into agreements with manufacturers, collecting extensive data from manufacturers and other sources, calculating ceiling and maximum fair prices, negotiating prices with manufacturers, re-negotiating prices as necessary and publishing the results of the negotiation. Under the Inflation Rebate Program, manufacturers of certain drugs will be required to pay a penalty or “rebate” if the price of their drug increases faster than the rate of inflation. For this program, the new group will need to identify the universe of rebatable drugs under Part B and Part D; determine which drugs had price increases in excess of inflation; and compute, invoice, and collect rebates owed by manufacturers.</P>
                <P>To carry out these functions, the major tasks of the new group will include:</P>
                <P>• Developing policy, including identifying and vetting policy options and preparing policy memoranda, rulemaking and technical guidance;</P>
                <P>• Briefing policy officials in CMS, U.S. Department of Health and Human Services (HHS), and Executive Office of the President (EOP);</P>
                <P>• Establishing operational processes to collect data from manufacturers and other sources;</P>
                <P>• Conducting pharmacoeconomic analyses and assessments of selected drugs;</P>
                <P>• Establishing operational processes to negotiate and re-negotiate drug prices and conducting those negotiations with manufacturers;</P>
                <P>• Establishing operational processes to calculate and invoice rebates;</P>
                <P>• Developing contractual agreements with manufacturers necessary to effectuate both programs;</P>
                <P>• Monitoring manufacturer compliance with programmatic rules;</P>
                <P>• Procuring and managing contractors to support these functions;</P>
                <P>• Conducting stakeholder outreach and educational materials; and</P>
                <P>• Responding to inquiries from Congress, the press, and other external stakeholders.</P>
                <P>
                    <E T="03">Authority:</E>
                     44 U.S.C. 3101.
                </P>
                <SIG>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <NAME>Xavier Becerra,</NAME>
                    <TITLE>Secretary, Department of Health and Human Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22296 Filed 10-12-22; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 4120-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute on Drug Abuse; Notice of Closed Meeting</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended, notice is hereby given of the following meeting.</P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The contract proposals and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the contract proposals, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute on Drug Abuse Special Emphasis Panel; Blueprint MedTech (BPMT) Biocompatibility, Sterilization, and Animal Studies.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         November 15, 2022.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         1:00 p.m. to 2:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate contract proposals.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, National Institute on Drug Abuse, 301 North Stonestreet Avenue, Bethesda, MD 20892 (Virtual Meeting).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Ipolia R. Ramadan, Ph.D., Scientific Review Officer, Scientific Review 
                        <PRTPAGE P="62434"/>
                        Branch, Division of Extramural Research, National Institute on Drug Abuse, NIH, 301 North Stonestreet Avenue, MSC 6021, Bethesda, MD 20892, (301) 827-4471, 
                        <E T="03">ramadanir@mail.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.277, Drug Abuse Scientist Development Award for Clinicians, Scientist Development Awards, and Research Scientist Awards; 93.278, Drug Abuse National Research Service Awards for Research Training; 93.279, Drug Abuse and Addiction Research Programs, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>Melanie J. Pantoja,</NAME>
                    <TITLE>Program Analyst,  Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22361 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <DEPDOC>[Docket No. USCG-2021-0345]</DEPDOC>
                <SUBJECT>Notice of Availability of Draft Study; Extension of Comment Period</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability and extension of comment period.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is extending the comment period of the draft Pacific Coast Port Access Route Study (PAC-PARS) in order to provide stakeholders with additional time to provide the Coast Guard with valuable input. This study evaluates safe access routes for the movement of vessel traffic proceeding to or from ports or places along the western seaboard of the United States and determines whether a shipping safety fairway (“fairway”) and/or routing measures should be established, adjusted or modified.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Comments must be submitted to the online docket via 
                        <E T="03">https://www.regulations.gov</E>
                         on or before November 8, 2022.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments identified by docket number USCG-2021-0345 using the Federal Decision Making Portal at 
                        <E T="03">https://www.regulations.gov.</E>
                         See the “Public Participation and Request for Comments” portion of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for further instructions on submitting comments.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For information about this document call or email LCDR Sara Conrad, Coast Guard Pacific Area (PAC-54), U.S. Coast Guard; telephone (510) 437-3813, email 
                        <E T="03">Sara.E.Conrad@uscg.mil</E>
                         or Mr. Tyrone Conner, Eleventh Coast Guard District (dpw), U.S. Coast Guard; telephone (510) 437-2968, email 
                        <E T="03">Tyrone.L.Conner@uscg.mil</E>
                         or Mr. John Moriarty, Thirteenth Coast Guard District (dpw), U.S. Coast Guard; telephone (206) 220-7274, email 
                        <E T="03">John.F.Moriarty@uscg.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Public Participation and Comments</HD>
                <P>
                    Two webinars are being offered to present the contents of the draft study to the public and answer questions. The first webinar was held on October 4th, 2022. The presentation slides and a recording of the webinar are available on the PAC-PARS Homeport website here: 
                    <E T="03">https://cglink.uscg.mil/efedac43.</E>
                     The second webinar will be held on Tuesday, October 11th, 2022 at 11:00am PST. The link to register can also be found on the PAC-PARS Homeport website: 
                    <E T="03">https://cglink.uscg.mil/efedac43.</E>
                </P>
                <P>We encourage you to submit comments (or related material) on the draft PAC-PARS. We will consider all submissions and may adjust our final recommendations based on your comments. If you submit a comment, please include the docket number for this notice, indicate the specific section of this document to which each comment applies, and provide a reason for each suggestion or recommendation.</P>
                <P>
                    <E T="03">Submitting comments.</E>
                     We encourage you to submit comments through the Federal Decision Making Portal at 
                    <E T="03">http://www.regulations.gov.</E>
                     To do so, go to 
                    <E T="03">https://www.regulations.gov,</E>
                     type USCG-2021-0345 in the search box and click “Search.” Next, look for this document in the Search Results column, and click on it. Then click on the Comment option. If your material cannot be submitted using 
                    <E T="03">http://www.regulations.gov,</E>
                     contact the person in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this document for alternate instructions.
                </P>
                <P>
                    <E T="03">Viewing material in docket.</E>
                     To view documents mentioned in this notice as being available in the docket, find the docket as described in the previous paragraph, and then select “Supporting &amp; Related Material” in the Document Type column. Public comments will also be placed in our online docket and can be viewed by following instructions on the 
                    <E T="03">https://www.regulations.gov</E>
                     Frequently Asked Questions web page. We review all comments received, but we may choose not to post off-topic, inappropriate, or duplicate comments that we receive.
                </P>
                <P>
                    <E T="03">Personal information.</E>
                     We accept anonymous comments. Comments we post to 
                    <E T="03">https://www.regulations.gov</E>
                     will include any personal information you have provided. For more about privacy and submissions in response to this document, see DHS's eRulemaking System of Records notice (85 FR 14226, March 11, 2020).
                </P>
                <HD SOURCE="HD1">Discussion</HD>
                <P>The draft PAC-PARS was published on August 26, 2022 (87 FR 52587). The original comment period closes on October 25, 2022. However, the Coast Guard has been notified that several stakeholders would like more time to prepare their comments on the draft study. The Coast Guard has decided that an extension of the public comment period would be appropriate to allow interested parties additional time to submit comments for Coast Guard's consideration. Thus, the comment period is extended by 14 days until November 8, 2022. This notice is issued under authority of 46 U.S.C. 70003(c)(1).</P>
                <SIG>
                    <DATED>Dated: October 6, 2022.</DATED>
                    <NAME>L. Hannah,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Chief, Pacific Area Preparedness Division.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22339 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <DEPDOC>[Docket ID FEMA-2022-0002; Internal Agency Docket No. FEMA-B-2279]</DEPDOC>
                <SUBJECT>Proposed Flood Hazard Determinations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Comments are requested on proposed flood hazard determinations, which may include additions or modifications of any Base Flood Elevation (BFE), base flood depth, Special Flood Hazard Area (SFHA) boundary or zone designation, or regulatory floodway on the Flood Insurance Rate Maps (FIRMs), and where applicable, in the supporting Flood Insurance Study (FIS) reports for the communities listed in the table below. The purpose of this notice is to seek general information and comment regarding the preliminary FIRM, and where applicable, the FIS report that the Federal Emergency Management Agency (FEMA) has provided to the affected communities. The FIRM and FIS report are the basis of the floodplain management measures that the 
                        <PRTPAGE P="62435"/>
                        community is required either to adopt or to show evidence of having 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>Comments are to be submitted on or before January 12, 2023.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The Preliminary FIRM, and where applicable, the FIS report for each community are available for inspection at both the online location 
                        <E T="03">https://hazards.fema.gov/femaportal/prelimdownload</E>
                         and the respective Community Map Repository address listed in the tables below. Additionally, the current effective FIRM and FIS report for each community are accessible online through the FEMA Map Service Center at 
                        <E T="03">https://msc.fema.gov</E>
                         for comparison.
                    </P>
                    <P>
                        You may submit comments, identified by Docket No. FEMA-B-2279, to Rick Sacbibit, Chief, Engineering Services Branch, Federal Insurance and Mitigation Administration, FEMA, 400 C Street SW, Washington, DC 20472, (202) 646-7659, or (email) 
                        <E T="03">patrick.sacbibit@fema.dhs.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Rick Sacbibit, Chief, Engineering Services Branch, Federal Insurance and Mitigation Administration, FEMA, 400 C Street SW, Washington, DC 20472, (202) 646-7659, or (email) 
                        <E T="03">patrick.sacbibit@fema.dhs.gov;</E>
                         or visit the FEMA Mapping and Insurance eXchange (FMIX) online at 
                        <E T="03">https://www.floodmaps.fema.gov/fhm/fmx_main.html.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>FEMA proposes to make flood hazard determinations for each community listed below, in accordance with section 110 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4104, and 44 CFR 67.4(a).</P>
                <P>These proposed flood hazard determinations, together with the floodplain management criteria required by 44 CFR 60.3, are the minimum that are required. They should not be construed to mean that the community must change any existing ordinances that are more stringent in their floodplain management requirements. The community may at any time enact stricter requirements of its own or pursuant to policies established by other Federal, State, or regional entities. These flood hazard determinations are used to meet the floodplain management requirements of the NFIP.</P>
                <P>The communities affected by the flood hazard determinations are provided in the tables below. Any request for reconsideration of the revised flood hazard information shown on the Preliminary FIRM and FIS report that satisfies the data requirements outlined in 44 CFR 67.6(b) is considered an appeal. Comments unrelated to the flood hazard determinations also will be considered before the FIRM and FIS report become effective.</P>
                <P>
                    Use of a Scientific Resolution Panel (SRP) is available to communities in support of the appeal resolution process. SRPs are independent panels of experts in hydrology, hydraulics, and other pertinent sciences established to review conflicting scientific and technical data and provide recommendations for resolution. Use of the SRP only may be exercised after FEMA and local communities have been engaged in a collaborative consultation process for at least 60 days without a mutually acceptable resolution of an appeal. Additional information regarding the SRP process can be found online at 
                    <E T="03">https://www.floodsrp.org/pdfs/srp_overview.pdf.</E>
                </P>
                <P>
                    The watersheds and/or communities affected are listed in the tables below. The Preliminary FIRM, and where applicable, FIS report for each community are available for inspection at both the online location 
                    <E T="03">https://hazards.fema.gov/femaportal/prelimdownload</E>
                     and the respective Community Map Repository address listed in the tables. For communities with multiple ongoing Preliminary studies, the studies can be identified by the unique project number and Preliminary FIRM date listed in the tables. Additionally, the current effective FIRM and FIS report for each community are accessible online through the FEMA Map Service Center at 
                    <E T="03">https://msc.fema.gov</E>
                     for comparison.
                </P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance No. 97.022, “Flood Insurance.”)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Nicholas A. Shufro,</NAME>
                    <TITLE>Assistant Administrator for Risk Management (Acting), Federal Emergency Management Agency, Department of Homeland Security.</TITLE>
                </SIG>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s100,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Community</CHED>
                        <CHED H="1">Community map repository address</CHED>
                    </BOXHD>
                    <ROW EXPSTB="01">
                        <ENT I="21">
                            <E T="02">Johnson County, Iowa and Incorporated Areas</E>
                        </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="21">
                            <E T="02">Project: 17-07-0294S Preliminary Date: April 20, 2022</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">City of Coralville</ENT>
                        <ENT>City Hall, 1512 7th Street, Coralville, IA 52241.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">City of Iowa City</ENT>
                        <ENT>Civic Center, 410 East Washington Street, Iowa City, IA 52240.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">City of Shueyville</ENT>
                        <ENT>Shueyville City Hall, 2863 120th Street Northeast, Swisher, IA 52338.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">City of Solon</ENT>
                        <ENT>City Hall, 101 North Iowa Street, Solon, IA 52333.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">City of Swisher</ENT>
                        <ENT>City Hall, 66 2nd Street Southwest, Swisher, IA 52338.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Unincorporated Areas Johnson County</ENT>
                        <ENT>Johnson County Planning Development and Sustainability Department, 913 South Dubuque Street, Iowa City, IA 52240.</ENT>
                    </ROW>
                    <ROW EXPSTB="01">
                        <ENT I="21">
                            <E T="02">Linn County, Iowa and Incorporated Areas</E>
                        </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="21">
                            <E T="02">Project: 19-07-0020S Preliminary Date: March 21, 2022</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">City of Cedar Rapids</ENT>
                        <ENT>City Hall, 101 1st Street Southeast, Cedar Rapids, IA 52401.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">City of Center Point</ENT>
                        <ENT>City Hall, 200 Franklin Street, Center Point, IA 52213.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">City of Marion</ENT>
                        <ENT>City Hall, 1225 6th Avenue, Suite 200, Marion, IA 52302.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">City of Palo</ENT>
                        <ENT>City Hall, 2800 Hollenbeck Road, Palo, IA 52324.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Unincorporated Areas of Linn County</ENT>
                        <ENT>Linn County Planning and Development Department, 935 2nd Street Southwest, Cedar Rapids, IA 52404.</ENT>
                    </ROW>
                </GPOTABLE>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22316 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="62436"/>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <DEPDOC>[Docket ID FEMA-2022-0002]</DEPDOC>
                <SUBJECT>Changes in Flood Hazard Determinations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>New or modified Base (1-percent annual chance) Flood Elevations (BFEs), base flood depths, Special Flood Hazard Area (SFHA) boundaries or zone designations, and/or regulatory floodways (hereinafter referred to as flood hazard determinations) as shown on the indicated Letter of Map Revision (LOMR) for each of the communities listed in the table below are finalized. Each LOMR revises the Flood Insurance Rate Maps (FIRMs), and in some cases the Flood Insurance Study (FIS) reports, currently in effect for the listed communities.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Each LOMR was finalized as in the table below.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Each LOMR is available for inspection at both the respective Community Map Repository address listed in the table below and online through the FEMA Map Service Center at 
                        <E T="03">https://msc.fema.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Rick Sacbibit, Chief, Engineering Services Branch, Federal Insurance and Mitigation Administration, FEMA, 400 C Street SW, Washington, DC 20472, (202) 646-7659, or (email) 
                        <E T="03">patrick.sacbibit@fema.dhs.gov;</E>
                         or visit the FEMA Mapping and Insurance eXchange (FMIX) online at 
                        <E T="03">https://www.floodmaps.fema.gov/fhm/fmx_main.html.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Federal Emergency Management Agency (FEMA) makes the final flood hazard determinations as shown in the LOMRs for each community listed in the table below. Notice of these modified flood hazard determinations has been published in newspapers of local circulation and 90 days have elapsed since that publication. The Deputy Associate Administrator for Insurance and Mitigation has resolved any appeals resulting from this notification.</P>
                <P>
                    The modified flood hazard determinations are made pursuant to section 206 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4105, and are in accordance with the National Flood Insurance Act of 1968, 42 U.S.C. 4001 
                    <E T="03">et seq.,</E>
                     and with 44 CFR part 65. The currently effective community number is shown and must be used for all new policies and renewals.
                </P>
                <P>The new or modified flood hazard information is the basis for the floodplain management measures that the community is required either to adopt or to show evidence of being already in effect in order to remain qualified for participation in the National Flood Insurance Program (NFIP).</P>
                <P>This new or modified flood hazard information, together with the floodplain management criteria required by 44 CFR 60.3, are the minimum that are required. They should not be construed to mean that the community must change any existing ordinances that are more stringent in their floodplain management requirements. The community may at any time enact stricter requirements of its own or pursuant to policies established by other Federal, State, or regional entities.</P>
                <P>This new or modified flood hazard determinations are used to meet the floodplain management requirements of the NFIP. The changes in flood hazard determinations are in accordance with 44 CFR 65.4.</P>
                <P>
                    Interested lessees and owners of real property are encouraged to review the final flood hazard information available at the address cited below for each community or online through the FEMA Map Service Center at 
                    <E T="03">https://msc.fema.gov.</E>
                </P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance No. 97.022, “Flood Insurance.”)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Nicholas A. Shufro,</NAME>
                    <TITLE>Assistant Administrator for Risk Management (Acting), Federal Emergency Management Agency, Department of Homeland Security.</TITLE>
                </SIG>
                <GPOTABLE COLS="6" OPTS="L2,tp0,i1" CDEF="xl50,xl50,xl75,xl100,xs80,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">State and county</CHED>
                        <CHED H="1">Location and case No.</CHED>
                        <CHED H="1">Chief executive officer of community</CHED>
                        <CHED H="1">Community map repository</CHED>
                        <CHED H="1">Date of modification</CHED>
                        <CHED H="1">Community No.</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">Colorado:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Arapahoe (FEMA Docket No.: B-2251).</ENT>
                        <ENT>City of Aurora, (21-08-1133P).</ENT>
                        <ENT>The Honorable Mike Coffman, Mayor, City of Aurora, 15151 East Alameda Parkway, Aurora, CO 80012.</ENT>
                        <ENT>Public Works Department, 15151 East Alameda Parkway, Aurora, CO 80012.</ENT>
                        <ENT>Sep. 9, 2022</ENT>
                        <ENT>080002</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Arapahoe (FEMA Docket No.: B-2244).</ENT>
                        <ENT>City of Centennial, (21-08-1000P).</ENT>
                        <ENT>The Honorable Stephanie Piko, Mayor, City of Centennial, 13133 East Arapahoe Road, Centennial, CO 80112.</ENT>
                        <ENT>Southeast Metro Stormwater Authority, 7437 South Fairplay Street, Centennial, CO 80112.</ENT>
                        <ENT>Sep. 9, 2022</ENT>
                        <ENT>080315</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Connecticut:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fairfield (FEMA Docket No.: B-2251).</ENT>
                        <ENT>Town of Greenwich (21-01-1171P).</ENT>
                        <ENT>The Honorable Fred Camillo, First Selectman, Town of Greenwich Board of Selectmen, 101 Field Point Road, 1st Floor, Greenwich, CT 06830.</ENT>
                        <ENT>Town Hall, 101 Field Point Road, Greenwich, CT 06830.</ENT>
                        <ENT>Sep. 14, 2022</ENT>
                        <ENT>090008</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Florida:  </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Broward (FEMA Docket No.: B-2244).</ENT>
                        <ENT>City of Lauderdale Lakes (21-04-5598P).</ENT>
                        <ENT>The Honorable Hazelle P. Rogers, Mayor, City of Lauderdale Lakes, 4300 Northwest 36th Street, Lauderdale Lakes, FL 33319.</ENT>
                        <ENT>Development Services Planning and Zoning Section, 3521 Northwest 43rd Avenue, Lauderdale Lakes, FL 33319.</ENT>
                        <ENT>Sep. 14, 2022</ENT>
                        <ENT>120043</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="62437"/>
                        <ENT I="03">Pinellas (FEMA Docket No.: B-2251).</ENT>
                        <ENT>Unincorporated areas of Pinellas County (22-04-1973P).</ENT>
                        <ENT>The Honorable Charlie Justice, Chairman, Pinellas County Board of Commissioners, 315 Court Street, Clearwater, FL 33756.</ENT>
                        <ENT>Pinellas County Building Services Department, 440 Court Street, Clearwater, FL 33756.</ENT>
                        <ENT>Sep. 15, 2022</ENT>
                        <ENT>125139</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Georgia:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Douglas (FEMA Docket No.: B-2251).</ENT>
                        <ENT>Unincorporated areas of Douglas County (21-04-2703P).</ENT>
                        <ENT>The Honorable Romona Jackson Jones, Chair, Douglas County Commission, 8700 Hospital Drive, 3rd Floor, Douglasville, GA 30134.</ENT>
                        <ENT>Douglas County Courthouse, 8700 Hospital Drive, 3rd Floor, Douglasville, GA 30134.</ENT>
                        <ENT>Sep. 16, 2022</ENT>
                        <ENT>130306</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Kentucky: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Scott (FEMA Docket No.: B-2253).</ENT>
                        <ENT>City of Georgetown (22-04-2347P).</ENT>
                        <ENT>The Honorable Tom Prather, Mayor, City of Georgetown, 100 North Court Street, Georgetown, KY 40324.</ENT>
                        <ENT>Planning and Zoning Department, 230 East Main Street, Georgetown, KY 40324.</ENT>
                        <ENT>Sep. 12, 2022</ENT>
                        <ENT>210208</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Maryland:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Prince George's (FEMA Docket No.: B-2244).</ENT>
                        <ENT>City of Laurel (22-03-0012P).</ENT>
                        <ENT>The Honorable Craig A. Moe, Mayor, City of Laurel, 8103 Sandy Spring Road, Laurel, MD 20707.</ENT>
                        <ENT>City Hall, 8103 Sandy Spring Road, Laurel, MD 20707.</ENT>
                        <ENT>Sep. 9, 2022</ENT>
                        <ENT>240053</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Oklahoma:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tulsa (FEMA Docket No.: B-2251).</ENT>
                        <ENT>City of Bixby (21-06-3360P).</ENT>
                        <ENT>Mr. Jared Cottle, Manager, City of Bixby, P.O. Box 70, Bixby, OK 74008.</ENT>
                        <ENT>Development, Services Department, 113 West Dawes Street, Bixby, OK 74008.</ENT>
                        <ENT>Sep. 19, 2022</ENT>
                        <ENT>400207</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Pennsylvania:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Montgomery (FEMA Docket No.: B-2244).</ENT>
                        <ENT>Township of Lower Frederick (22-03-0084P).</ENT>
                        <ENT>The Honorable Marla Hexter, Chair, Township of Lower Frederick, Board of Supervisors, 53 Spring Mount Road, Schwenksville, PA 19473.</ENT>
                        <ENT>Township Hall, 53 Spring Mount Road, Schwenksville, PA 19473.</ENT>
                        <ENT>Sep. 8, 2022</ENT>
                        <ENT>420952</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">South Dakota:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Deuel (FEMA Docket No.: B-2251).</ENT>
                        <ENT>Town of Altamont (22-08-0536P).</ENT>
                        <ENT>The Honorable Jennifer Jensen, Mayor, Town of Altamont, 307 Carmen Street, Altamont, SD 57226.</ENT>
                        <ENT>Town Hall, 307 Carmen Street, Altamont, SD 57226.</ENT>
                        <ENT>Sep. 2, 2022</ENT>
                        <ENT>460320</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Deuel (FEMA Docket No.: B-2251).</ENT>
                        <ENT>Town of Brandt (22-08-0536P).</ENT>
                        <ENT>The Honorable Greg Anderson, Mayor-President, Town of Brandt, P.O. Box 218, Brandt, SD 57218.</ENT>
                        <ENT>Town Hall, 112 Main Street, Brandt, SD 57218.</ENT>
                        <ENT>Sep. 2, 2022</ENT>
                        <ENT>460319</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Texas:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Dallas (FEMA Docket No.: B-2251).</ENT>
                        <ENT>City of DeSoto (21-06-3174P).</ENT>
                        <ENT>The Honorable Rachel L. Proctor, Mayor, City of DeSoto, 211 East Pleasant Run Road, DeSoto, TX 75115.</ENT>
                        <ENT>Development Services Department, 211 East Pleasant Run Road, DeSoto, TX 75115.</ENT>
                        <ENT>Sep. 7, 2022</ENT>
                        <ENT>480172</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Denton (FEMA Docket No.: B-2244).</ENT>
                        <ENT>City of Fort Worth (22-06-0542P).</ENT>
                        <ENT>The Honorable Mattie Parker, Mayor, City of Fort Worth, 200 Texas Street, Fort Worth, TX 76102.</ENT>
                        <ENT>Transportation and Public Works Department, Engineering Vault, 200 Texas Street, Fort Worth, TX 76102.</ENT>
                        <ENT>Sep. 15, 2022</ENT>
                        <ENT>480596</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Denton (FEMA Docket No.: B-2251).</ENT>
                        <ENT>Town of Prosper (21-06-3249P).</ENT>
                        <ENT>The Honorable Ray Smith, Mayor, Town of Prosper, P.O. Box 307, Prosper, TX 75078.</ENT>
                        <ENT>Engineering Services Department, 250 West 1st Street, Prosper, TX 75078.</ENT>
                        <ENT>Sep. 12, 2022</ENT>
                        <ENT>480141</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Denton (FEMA Docket No.: B-2251).</ENT>
                        <ENT>Unincorporated areas of Denton County (21-06-3249P).</ENT>
                        <ENT>The Honorable Andy Eads, Denton County Judge, 1 Courthouse Drive, Suite 100, Denton, TX 76201.</ENT>
                        <ENT>Denton County Development Services Department, 3900 Morse Street, Denton, TX 76208.</ENT>
                        <ENT>Sep. 12, 2022</ENT>
                        <ENT>480774</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="62438"/>
                        <ENT I="03">Harris (FEMA Docket No.: B-2253).</ENT>
                        <ENT>City of Houston (21-06-2034P).</ENT>
                        <ENT>The Honorable Sylvester Turner, Mayor, City of Houston, P.O. Box 1562, Houston, TX 77251.</ENT>
                        <ENT>Floodplain Management department, 1002 Washington Avenue, Houston, TX 77002.</ENT>
                        <ENT>Sep. 12, 2022</ENT>
                        <ENT>480296</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Johnson (FEMA Docket No.: B-2244).</ENT>
                        <ENT>City of Burleson (21-06-2082P).</ENT>
                        <ENT>The Honorable Chris Fletcher, Mayor, City of Burleson, 141 West Renfro Street, Burleson, TX 76028.</ENT>
                        <ENT>City Hall, 141 West Renfro Street, Burleson, TX 76028.</ENT>
                        <ENT>Sep. 8, 2022</ENT>
                        <ENT>485459</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Montgomery (FEMA Docket No.: B-2251).</ENT>
                        <ENT>City of Conroe (21-06-2197P).</ENT>
                        <ENT>The Honorable Jody Czajkoski, Mayor, City of Conroe, P.O. Box 3066, Conroe, TX 77305.</ENT>
                        <ENT>City Hall, 300 West Davis Street, Conroe, TX 77305.</ENT>
                        <ENT>Sep. 9, 2022</ENT>
                        <ENT>480484</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tarrant (FEMA Docket No.: B-2244).</ENT>
                        <ENT>City of Fort Worth (22-06-0310P).</ENT>
                        <ENT>The Honorable Mattie Parker, Mayor, City of Fort Worth, 200 Texas Street, Fort Worth, TX 76102.</ENT>
                        <ENT>Transportation and Public Works Department, Engineering Vault, 200 Texas Street, Fort Worth, TX 76102.</ENT>
                        <ENT>Sep. 15, 2022</ENT>
                        <ENT>480596</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Williamson (FEMA Docket No.: B-2244).</ENT>
                        <ENT>City of Georgetown (21-06-2319P).</ENT>
                        <ENT>Mr. David Morgan, Manager, City of Georgetown, P.O. Box 409, Georgetown, TX 78626.</ENT>
                        <ENT>Mapping and GIS Department, 300-1 Industrial Avenue, Georgetown, TX 78626.</ENT>
                        <ENT>Sep. 8, 2022</ENT>
                        <ENT>481048</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Williamson (FEMA Docket No.: B-2244).</ENT>
                        <ENT>City of Round Rock (22-06-0132P).</ENT>
                        <ENT>The Honorable Craig Morgan, Mayor, City of Round Rock, 221 East Main Street, Round Rock, TX 78664.</ENT>
                        <ENT>City Hall, 221 East Main Street, Round Rock, TX 78664.</ENT>
                        <ENT>Sep. 8, 2022</ENT>
                        <ENT>481079</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Williamson (FEMA Docket No.: B-2244).</ENT>
                        <ENT>Unincorporated areas of Williamson County (21-06-2319P).</ENT>
                        <ENT>The Honorable Bill Gravell, Jr., Williamson County Judge, 710 South Main Street, Suite 101, Georgetown, TX 78626.</ENT>
                        <ENT>Williamson County, Engineering Department, 3151 Southeast Inner Loop, Georgetown, TX 78626.</ENT>
                        <ENT>Sep. 1, 2022</ENT>
                        <ENT>481079</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Williamson (FEMA Docket No.: B-2244).</ENT>
                        <ENT>Unincorporated areas of Williamson County (22-06-0132P).</ENT>
                        <ENT>The Honorable Bill Gravell, Jr., Williamson County Judge, 710 South Main Street, Suite 101, Georgetown, TX 78626.</ENT>
                        <ENT>Williamson County, Engineering Department, 3151 Southeast Inner Loop, Georgetown, TX 78626.</ENT>
                        <ENT>Sep. 8, 2022</ENT>
                        <ENT>481079</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Utah:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Washington (FEMA Docket No.: B-2251).</ENT>
                        <ENT>City of St. George (22-08-0191P).</ENT>
                        <ENT>The Honorable Michele Randall, Mayor, City of St. George, 175 East 200 North, St. George, UT 84770.</ENT>
                        <ENT>City Hall, 175 East 200 North, St. George, UT 84770.</ENT>
                        <ENT>Sep. 12, 2022</ENT>
                        <ENT>490177</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Virginia:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Charles City (FEMA Docket No.: B-2253).</ENT>
                        <ENT>Unincorporated areas of Charles City County (22-03-0523P).</ENT>
                        <ENT>Michelle Johnson, Administrator, Charles City County, P.O. Box 128, Charles City, VA 23030.</ENT>
                        <ENT>Charles City County, Government Administration Building, 10900 Courthouse Road, Charles City, VA 23030.</ENT>
                        <ENT>Sep. 9, 2022</ENT>
                        <ENT>510198</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">West Virginia:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wood (FEMA Docket No.: B-2244).</ENT>
                        <ENT>Unincorporated areas of Wood County (22-03-0440P).</ENT>
                        <ENT>The Honorable David Blair Couch, President, Wood County Commission, 1 Court Square, Suite 205, Parkersburg, WV 26101.</ENT>
                        <ENT>Wood County Commission Office, 1 Court Square, Suite 205, Parkersburg, WV 26101.</ENT>
                        <ENT>Sep. 9, 2022</ENT>
                        <ENT>540213</ENT>
                    </ROW>
                </GPOTABLE>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22317 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="62439"/>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>U.S. Citizenship and Immigration Services</SUBAGY>
                <DEPDOC>[OMB Control Number 1615-0124]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Extension, Without Change, of a Currently Approved Collection: Consideration of Deferred Action for Childhood Arrivals</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Citizenship and Immigration Services, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>60-Day notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Department of Homeland Security (DHS), U.S. Citizenship and Immigration Services (USCIS) invites the general public and other Federal agencies to comment upon this proposed extension of a currently approved collection of information. In accordance with the Paperwork Reduction Act (PRA) of 1995, the information collection notice is published in the 
                        <E T="04">Federal Register</E>
                         to obtain comments regarding the nature of the information collection, the categories of respondents, the estimated burden (
                        <E T="03">i.e.</E>
                         the time, effort, and resources used by the respondents to respond), the estimated cost to the respondent, and the actual information collection instruments.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments are encouraged and will be accepted for 60 days until December 13, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        All submissions received must include the OMB Control Number 1615-0124 in the body of the letter, the agency name and Docket ID USCIS-2012-0012. Submit comments via the Federal eRulemaking Portal website at 
                        <E T="03">https://www.regulations.gov</E>
                         under e-Docket ID number USCIS-2012-0012.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        USCIS, Office of Policy and Strategy, Regulatory Coordination Division, Samantha Deshommes, Chief, telephone number (240) 721-3000 (This is not a toll-free number. Comments are not accepted via telephone message). Please note contact information provided here is solely for questions regarding this notice. It is not for individual case status inquiries. Applicants seeking information about the status of their individual cases can check Case Status Online, available at the USCIS website at 
                        <E T="03">https://www.uscis.gov,</E>
                         or call the USCIS Contact Center at 800-375-5283 (TTY 800-767-1833).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments</HD>
                <P>
                    You may access the information collection instrument with instructions or additional information by visiting the Federal eRulemaking Portal site at: 
                    <E T="03">https://www.regulations.gov</E>
                     and entering USCIS-2012-0012 in the search box. All submissions will be posted, without change, to the Federal eRulemaking Portal at 
                    <E T="03">https://www.regulations.gov,</E>
                     and will include any personal information you provide. Therefore, submitting this information makes it public. You may wish to consider limiting the amount of personal information that you provide in any voluntary submission you make to DHS. DHS may withhold information provided in comments from public viewing that it determines may impact the privacy of an individual or is offensive. For additional information, please read the Privacy Act notice that is available via the link in the footer of 
                    <E T="03">https://www.regulations.gov.</E>
                </P>
                <P>Written comments and suggestions from the public and affected agencies should address one or more of the following four points:</P>
                <P>(1) Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>(2) Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
                <P>(3) Enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    (4) Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses.
                </P>
                <HD SOURCE="HD1">Overview of This Information Collection</HD>
                <P>
                    (1) 
                    <E T="03">Type of Information Collection:</E>
                     Extension, Without Change, of a Currently Approved Collection.
                </P>
                <P>
                    (2) 
                    <E T="03">Title of the Form/Collection:</E>
                     Consideration of Deferred Action for Childhood Arrivals.
                </P>
                <P>
                    (3) 
                    <E T="03">Agency form number, if any, and the applicable component of the DHS sponsoring the collection:</E>
                     Form I-821D; USCIS.
                </P>
                <P>
                    (4) 
                    <E T="03">Affected public who will be asked or required to respond, as well as a brief abstract: Primary:</E>
                     Individuals or households. The information collected on this form is used by USCIS to determine eligibility of certain illegal aliens who entered the United States as minors and meet the following guidelines to be considered for Deferred Action for Childhood Arrivals:
                </P>
                <P>1. Was under the age of 31 as of June 15, 2012;</P>
                <P>2. Came to the United States before reaching his or her 16th birthday;</P>
                <P>3. Has continuously resided in the United States since June 15, 2007, up to the present time;</P>
                <P>4. Was present in the United States on June 15, 2012 and at the time of making his or her request for consideration of deferred action with USCIS;</P>
                <P>5. Had no lawful status on June 15, 2012; NOTE: No lawful status on June 15, 2012 means that:</P>
                <P>(a) You never had a lawful immigration status on or before June 15, 2012; or</P>
                <P>(b) Any lawful immigration status or parole that you obtained prior to June 15, 2012 had expired as of June 15, 2012.</P>
                <P>6. Is currently in school, has graduated or obtained a certificate of completion from high school, has obtained a general education development (GED) certificate, or is an honorably discharged veteran of the U.S. Armed Forces or U.S. Coast Guard; and</P>
                <P>7. Has not been convicted of a felony, a significant misdemeanor, or three or more misdemeanors, and does not otherwise pose a threat to national security or public safety.</P>
                <P>
                    (5) 
                    <E T="03">An estimate of the total number of respondents and the amount of time estimated for an average respondent to respond:</E>
                     The estimated total number of respondents for the I-821D initial requests (paper) information collection is 32,655 annually, and the estimated hour burden per response is 3 hours; the estimated total number of respondents for the I-821D renewal requests (paper) information collection is 335,020, and the estimated hour burden per response is 3 hours; the estimated total number of respondents for the I-821D renewal requests (electronic) information collection is 91,919, and the estimated hour burden per response is 2.5 hours.
                </P>
                <P>
                    (6) 
                    <E T="03">An estimate of the total public burden (in hours) associated with the collection:</E>
                     The total estimated annual hour burden associated with this collection is 1,332,823 hours.
                </P>
                <P>
                    (7) 
                    <E T="03">An estimate of the total public burden (in cost) associated with the collection:</E>
                     The estimated total annual cost burden associated with this collection of information is $50,555,340.
                </P>
                <SIG>
                    <PRTPAGE P="62440"/>
                    <DATED>Dated: October 07, 2022.</DATED>
                    <NAME>Samantha L. Deshommes,</NAME>
                    <TITLE>Chief, Regulatory Coordination Division, Office of Policy and Strategy, U.S. Citizenship and Immigration Services, Department of Homeland Security.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22359 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9111-97-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Land Management</SUBAGY>
                <DEPDOC>[MTM-79374-01]</DEPDOC>
                <SUBJECT>Notice of Application for Withdrawal Extension and Public Meeting, Crystal Park Recreation Area; Beaverhead County, MT</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of application.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>On behalf of the United States Department of Agriculture, the United States Forest Service (USFS) filed an application with the Bureau of Land Management (BLM) requesting the Secretary of the Interior extend Public Land Order (PLO) No. 6958 for an additional 30-year term. PLO No. 6958 withdrew 220 acres of National Forest System lands in Beaverhead County, Montana, from location and entry under the United States mining laws, subject to valid existing rights, to protect the USFS-managed recreation area. The lands remain open to leasing under the mineral leasing laws, and to such uses as may be made on National Forest System lands. The withdrawal created by PLO No. 6958 will expire on March 1, 2023, unless extended. This notice announces to the public an opportunity to comment on the proposal and announces the date, time, and how to access the virtual public meeting to be held in conjunction with this withdrawal extension application.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Comments must be received by January 12, 2023. Notice is hereby given that the USFS will hold a virtual public meeting in connection with the withdrawal extension application on November 7, 2022, at 6:30 p.m. The USFS will publish instructions on how to access the online public meeting in the 
                        <E T="03">Montana Standard</E>
                         newspaper a minimum of 30 days prior to the meeting.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>All written comments should be sent to the Office of the Regional Forester, Region One, 26 Fort Missoula Road, Missoula, Montana 59804.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Will Pedde, Land Status Program Manager, USFS Region One, (406) 329-3204 or via email at 
                        <E T="03">will.pedde@usda.gov</E>
                         or you may contact the USFS office at the earlier address.
                    </P>
                    <P>Individuals in the United States who are deaf, deafblind, hard of hearing, or have a speech disability may dial 711 (TTY, TDD, or Tele Braille) to access telecommunications relay services. Individuals outside the United States should use the relay services offered within their country to make international calls to the point-of-contact in the United States.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The USFS filed an application requesting extension of the withdrawal established by PLO No. 6958 (58 FR 11968). PLO No. 6958 withdrew 220 acres of National Forest System lands in Beaverhead County, Montana, from location and entry under the United States mining laws (30 U.S.C. Ch.2), but not from leasing under the mineral leasing laws, or entry under the general land laws, subject to valid existing rights, for a 30-year term. PLO No. 6958 is incorporated herein by reference.</P>
                <P>The purpose of the proposed extension is to preserve and protect the existing recreational opportunities, facilities, and capital improvements from locatable mineral development of the Crystal Park Recreation Area through the year 2053.</P>
                <P>The use of a rights-of-way, interagency agreement, or cooperative agreement would not provide adequate protection for this site.</P>
                <P>There are no suitable alternative sites available which would facilitate public opportunity for this type of recreation experience.</P>
                <P>No water rights will be needed to fulfill the purpose of the requested withdrawal.</P>
                <P>
                    All interested persons who wish to submit comments, suggestions, or objections in connection with the withdrawal extension application may submit a written request to the Regional Forester by January 12, 2023, at the address in the 
                    <E T="02">ADDRESSES</E>
                     section earlier.
                </P>
                <P>Comments, including names and street addresses of respondents, will be available for public review at Region One, 26 Fort Missoula Road, Missoula, Montana 59804, during regular business hours.</P>
                <P>Before including your address, phone number, email address, or other personal identifying information in your comment, be advised that your entire comment—including your personal identifying information—may be made publicly available at any time. While you may ask the BLM in your comment to withhold from your personal identifying information from the public review, we cannot guarantee that we will be able to do so.</P>
                <P>This application will be processed in accordance with the regulations set-forth in 43 CFR 2310.4.</P>
                <SIG>
                    <NAME>Sonya Germann,</NAME>
                    <TITLE>State Director.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22398 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3411-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Land Management</SUBAGY>
                <DEPDOC>[L19900000.PO0000.LLHQ320.22X; OMB Control No. 1004-0073]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Coal Management</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of information collection; request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, the Bureau of Land Management (BLM) proposes to renew an information collection.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Interested persons are invited to submit comments on or before December 13, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Send your written comments on this information collection request (ICR) by mail to Darrin King, Information Collection Clearance Officer, U.S. Department of the Interior, Bureau of Land Management, Attention PRA Office, 440 W 200 S #500, Salt Lake City, UT 84101; or by email to 
                        <E T="03">BLM_HQ_PRA_Comments@blm.gov.</E>
                         Please reference Office of Management and Budget (OMB) Control Number 1004-0073 in the subject line of your comments. The electronic submission of comments is recommended.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        To request additional information about this Information Collection Request (ICR), contact Tom Huebner by email at 
                        <E T="03">thuebner@blm.gov,</E>
                         or by telephone at (307) 775-6195. Individuals in the United States who are deaf, deafblind, hard of hearing, or have a speech disability may dial 711 (TTY, TDD, or TeleBraille) to access telecommunications relay services. Individuals outside the United States should use the relay services offered within their country to make international calls to the point-of-contact in the United States. You may also view the ICR at 
                        <E T="03">http://www.reginfo.gov/public/do/PRAMain.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <PRTPAGE P="62441"/>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    In accordance with the Paperwork Reduction Act of 1995 (PRA, 44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ) and 5 CFR 1320.8(d)(1), all information collections require approval under the PRA. We may not conduct or sponsor, and you are not required to respond to a collection of information unless it displays a currently valid OMB control number.
                </P>
                <P>As part of our continuing effort to reduce paperwork and respondent burdens, we invite the public and other Federal agencies to comment on new, proposed, revised, and continuing collections of information. This helps us assess the impact of our information collection requirements and minimize the public's reporting burden. It also helps the public understand our information collection requirements and provide the requested data in the desired format.</P>
                <P>We are especially interested in public comment addressing the following:</P>
                <P>(1) Whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>(2) The accuracy of our estimate of the burden for this collection of information, including the validity of the methodology and assumptions used;</P>
                <P>(3) Ways to enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    (4) How the agency might minimize the burden of the collection of information on those who are to respond, including the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of response.
                </P>
                <P>Comments that you submit in response to this notice are a matter of public record. We will include or summarize each comment in our request to OMB to approve this ICR. Before including your address, phone number, email address, or other personal identifying information in your comment, you should be aware that your entire comment—including your personal identifying information—may be made publicly available at any time. While you can ask us in your comment to withhold your personal identifying information from public review, we cannot guarantee that we will be able to do so.</P>
                <P>
                    <E T="03">Abstract:</E>
                     This collection enables the BLM to learn the extent and qualities of Federal coal resources; evaluate the environmental impacts of coal leasing and development; determine the qualifications of prospective lessees to acquire and hold Federal coal leases; and ensure lessee compliance with applicable statutes, regulations, and lease terms and conditions. This OMB Control Number is currently scheduled to expire on April 30, 2023. The BLM plans to request that OMB renew this OMB Control Number for an additional three years.
                </P>
                <P>
                    <E T="03">Title of Collection:</E>
                     Coal Management (43 CFR parts 3400-3480).
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1004-0073.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     3440-001—Application and License to Mine Coal (Free Use) and Form 3400-012—Coal Lease.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Respondents/Affected Public:</E>
                     Applicants for, and holders of, coal exploration licenses; applicants/bidders for, and holders of, coal leases; applicants for, and holders of, licenses to mine coal; and surface owners and State and tribal governments whose lands overlie coal deposits.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Respondents:</E>
                     1,017.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Responses:</E>
                     1,017.
                </P>
                <P>
                    <E T="03">Estimated Completion Time per Response:</E>
                     Varies from 1 to 800 hours.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Burden Hours:</E>
                     19,897.
                </P>
                <P>
                    <E T="03">Respondent's Obligation:</E>
                     Required to obtain or retain a benefit.
                </P>
                <P>
                    <E T="03">Frequency of Collection:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Total Estimated Annual Nonhour Burden Cost:</E>
                     $943,463.
                </P>
                <P>An agency may not conduct or sponsor and, notwithstanding any other provision of law, a person is not required to respond to a collection of information unless it displays a currently valid OMB control number.</P>
                <P>
                    The authority for this action is the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <SIG>
                    <NAME>Darrin A. King,</NAME>
                    <TITLE>Information Collection Clearance Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22404 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-84-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Land Management</SUBAGY>
                <DEPDOC>[LLAK940000.L14100000.BX0000.223.LXSS001L0100]</DEPDOC>
                <SUBJECT>Filing of Plats of Survey: Alaska</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of official filing.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The plats of survey of lands described in this notice are scheduled to be officially filed in the Bureau of Land Management (BLM), Alaska State Office, Anchorage, Alaska. The surveys, which were executed at the request of the Bureau of Indian Affairs (BIA) and BLM, are necessary for the management of these lands.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The BLM must receive protests by November 14, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may buy a copy of the plats from the BLM Alaska Public Information Center, 222 W 7th Avenue, Mailstop 13, Anchorage, AK 99513. Please use this address when filing written protests. You may also view the plats at the BLM Alaska Public Information Center, Fitzgerald Federal Building, 222 W 7th Avenue, Anchorage, Alaska, at no cost.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Thomas O'Toole, Chief, Branch of Cadastral Survey, Alaska State Office, Bureau of Land Management, 222 W 7th Avenue, Anchorage, AK 99513; 907-271-4231; 
                        <E T="03">totoole@blm.gov.</E>
                         People who use a telecommunications device for the deaf may call the Federal Relay Service (FRS) at 1-800-877-8339 to contact the BLM during normal business hours. The FRS is available 24 hours a day, 7 days a week, to leave a message or question with the above individual. You will receive a reply during normal business hours.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The lands surveyed are:</P>
                <EXTRACT>
                    <HD SOURCE="HD1">Copper River Meridian, Alaska</HD>
                    <FP SOURCE="FP-2">U.S. Survey No. 1871, accepted August 5, 2022, situated in T. 56 S., R. 72 E.</FP>
                    <FP SOURCE="FP-2">U.S. Survey No. 3851, accepted August 5, 2022, situated in T. 56 S., R. 72 E.</FP>
                    <FP SOURCE="FP-2">U.S. Survey No. 3852, accepted August 5, 2022, situated in T. 56 S., R. 72 E.</FP>
                    <FP SOURCE="FP-2">U.S. Survey No. 14549, accepted September 27, 2022, situated in T. 18 S., R. 18 E.</FP>
                    <FP SOURCE="FP-2">U.S. Survey No. 14553, accepted September 27, 2022, situated in T. 19 S., R. 17 E.</FP>
                    <FP SOURCE="FP-2">U.S. Survey No. 14554, accepted September 27, 2022, situated in T. 19 S., R. 17 E.</FP>
                    <FP SOURCE="FP-2">T. 27 N., R. 18 E., accepted September 21, 2022.</FP>
                    <FP SOURCE="FP-2">T. 28 N., R. 18 E., accepted September 21, 2022.</FP>
                    <HD SOURCE="HD1">Fairbanks Meridian, Alaska</HD>
                    <FP SOURCE="FP-2">T. 7 S., R. 27 E., accepted September 21, 2022.</FP>
                    <HD SOURCE="HD1">Seward Meridian, Alaska</HD>
                    <FP SOURCE="FP-2">U.S. Survey No. 4545, accepted August 23, 2022, situated in T. 12 N., R. 10 W.</FP>
                    <FP SOURCE="FP-2">U.S. Survey No. 14463, accepted August 5, 2022, situated in T. 31 S., R. 50 W.</FP>
                    <FP SOURCE="FP-2">U.S. Survey No. 14481, accepted August 5, 2022, situated in T. 8 S., R. 47 W.</FP>
                    <FP SOURCE="FP-2">T. 12 N., R. 10 W., accepted August 5, 2022.</FP>
                    <FP SOURCE="FP-2">T. 12 N., R. 11 W., accepted August 5, 2022.</FP>
                    <FP SOURCE="FP-2">T. 26 N., R. 64 W., accepted September 13, 2022.</FP>
                    <FP SOURCE="FP-2">
                        T. 25 N., R. 65 W., accepted September 13, 2022.
                        <PRTPAGE P="62442"/>
                    </FP>
                    <FP SOURCE="FP-2">T. 26 N., R. 65 W., accepted September 13, 2022.</FP>
                    <FP SOURCE="FP-2">T. 27 N., R. 65 W., accepted September 13, 2022.</FP>
                    <FP SOURCE="FP-2">T. 25 N., R. 66 W., accepted September 13, 2022.</FP>
                    <FP SOURCE="FP-2">T. 26 N., R. 66 W., accepted September 13, 2022.</FP>
                    <FP SOURCE="FP-2">T. 20 N., R. 67 W., accepted September 13, 2022.</FP>
                    <FP SOURCE="FP-2">T. 21 N., R. 67 W., accepted September 13, 2022.</FP>
                    <FP SOURCE="FP-2">T. 20 N., R. 69 W., accepted September 13, 2022.</FP>
                </EXTRACT>
                <P>A person or party who wishes to protest one or more plats of survey identified above must file a written notice of protest with the State Director for the BLM in Alaska. The protest may be filed by mailing to BLM State Director, Alaska State Office, Bureau of Land Management, 222 W 7th Avenue, Anchorage, AK 99513 or by delivering it in person to BLM Alaska Public Information Center, Fitzgerald Federal Building, 222 W 7th Avenue, Anchorage, Alaska. The notice of protest must identify the plat(s) of survey that the person or party wishes to protest. You must file the notice of protest before the scheduled date of official filing for the plat(s) of survey being protested. The BLM will not consider any notice of protest filed after the scheduled date of official filing. A notice of protest is considered filed on the date it is received by the State Director for the BLM in Alaska during regular business hours; if received after regular business hours, a notice of protest will be considered filed the next business day. A written statement of reasons in support of a protest, if not filed with the notice of protest, must be filed with the State Director for the BLM in Alaska within 30 calendar days after the notice of protest is filed.</P>
                <P>If a notice of protest against a plat of survey is received prior to the scheduled date of official filing, the official filing of the plat of survey identified in the notice of protest will be stayed pending consideration of the protest. A plat of survey will not be officially filed until the dismissal or resolution of all protests of the plat.</P>
                <P>Before including your address, phone number, email address, or other personally identifiable information in a notice of protest or statement of reasons, you should be aware that the documents you submit, including your personally identifiable information, may be made publicly available in their entirety at any time. While you can ask the BLM to withhold your personally identifiable information from public review, we cannot guarantee that we will be able to do so.</P>
                <P>
                    <E T="03">Authority:</E>
                     43 U.S.C. Chap. 3.
                </P>
                <SIG>
                    <NAME>Thomas O'Toole,</NAME>
                    <TITLE>Chief Cadastral Surveyor, Alaska.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22318 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-JA-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>National Park Service</SUBAGY>
                <DEPDOC>[NPS-WASO-NRSS- NPS0034116 PPWONRADC0; PPMRSNR1Y.NM0000; 222P103601; OMB Control Number 1024-NEW]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Visitor Perceptions of Climate Change Study</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Park Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of information collection; request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995 we, the National Park Service (NPS) are proposing a new information collection.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Interested persons are invited to submit comments on or before December 13, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Send your comments on this information collection request (ICR) by mail to Phadrea Ponds, NPS Information Collection Clearance Officer, 12201 Sunrise Valley Drive (MS-242), Reston, Virginia 20192; or by email to 
                        <E T="03">phadrea_ponds@nps.gov.</E>
                         Please reference Office of Management and Budget (OMB) Control Number 1024-NEW (PVIA) in the subject line of your comments.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        To request additional information about this ICR, contact Larry Perez, Communications Coordinator, NPS Climate Change Response Program by email at 
                        <E T="03">larry_perez@nps.gov</E>
                         or by telephone at 970-267-2136. Please reference OMB Control Number 1024-NEW (PVIA) in the subject line of your comments. Individuals in the United States who are deaf, deafblind, hard of hearing, or have a speech disability may dial 711 (TTY, TDD, or TeleBraille) to access telecommunications relay services. Individuals outside the United States should use the relay services offered within their country to make international calls to the point-of-contact in the United States. You may also view the ICR at 
                        <E T="03">http://www.reginfo.gov/public/do/PRAMain.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In accordance with the PRA and 5 CFR 1320.8(d)(1), all information collections require approval under the PRA.</P>
                <P>As part of our continuing effort to reduce paperwork and respondent burdens, we invite the public and other Federal agencies to comment on new, proposed, revised, and continuing collections of information. This helps us assess the impact of our information collection requirements and minimize the public's reporting burden. It also helps the public understand our information collection requirements and provide the requested data in the desired format.</P>
                <P>We are especially interested in public comment addressing the following:</P>
                <P>(1) Whether or not the collection of information is necessary for the proper performance of the functions of the agency, including whether or not the information will have practical utility;</P>
                <P>(2) The accuracy of our estimate of the burden for this collection of information, including the validity of the methodology and assumptions used;</P>
                <P>(3) Ways to enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    (4) How the agency might minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of response.
                </P>
                <P>Comments that you submit in response to this notice are a matter of public record. We will include or summarize each comment in our request to OMB to approve this ICR. Before including your address, phone number, email address, or other personal identifying information in your comment, you should be aware that your entire comment—including your personal identifying information—may be made publicly available at any time. While you can ask us in your comment to withhold your personal identifying information from public review, we cannot guarantee that we will be able to do so.</P>
                <P>
                    <E T="03">Abstract:</E>
                     The NPS is authorized by the National Park Service Protection, Interpretation, and Research in System (54 U.S.C. 100701) statutes to collect information used to enhance the management and planning of parks and their resources. The Climate Change Response Program (administered through the Natural Resource Stewardship and Science directorate) and the U.S. Fish and Wildlife Service (FWS) Human Dimensions Branch (administered through the Natural Resource Program Center within the National Wildlife Refuge System) are partnering to conduct a voluntary, on-site survey to understand park and 
                    <PRTPAGE P="62443"/>
                    refuge visitors' attitudes, perceptions, and beliefs about climate-related topics.
                </P>
                <P>Both the National Park System and the National Wildlife Refuge System protect places, resources, and experiences of importance to the American public. But climate change has serious implications for the protection of landscapes, ecosystems, recreational opportunities, and visitor experiences in parks and refuges. Thus, the NPS and FWS seek to better understand visitors' understanding and concerns about climate change.</P>
                <P>Both the NPS and FWS administer high-quality programs of interpretation and education, and communication about pressing, climate-related topics is increasingly necessary. Audience analysis is important for guiding such efforts. Results of this survey will provide insight into topics, methods, and/or communications media of most interest to park and refuge visitors.</P>
                <P>
                    <E T="03">Title of Collection:</E>
                     Visitor Perceptions of Climate Change Study.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1024-NEW.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     None.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     New.
                </P>
                <P>
                    <E T="03">Respondents/Affected Public:</E>
                     General Public.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Respondents:</E>
                     6,720.
                </P>
                <P>
                    <E T="03">Estimated Completion Time per Response:</E>
                     7 minutes.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Burden Hours:</E>
                     784.
                </P>
                <P>
                    <E T="03">Respondent's Obligation:</E>
                     Voluntary.
                </P>
                <P>
                    <E T="03">Frequency of Collection:</E>
                     Once.
                </P>
                <P>
                    <E T="03">Total Estimated Annual Nonhour Burden Cost:</E>
                     None.
                </P>
                <P>An agency may not conduct or sponsor nor is a person required to respond to a collection of information unless it displays a currently valid OMB control number.</P>
                <P>
                    The authority for this action is the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <SIG>
                    <NAME>Phadrea Ponds,</NAME>
                    <TITLE>Information Collection Clearance Officer, National Park Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22369 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4312-52-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>National Park Service</SUBAGY>
                <DEPDOC>[NPS-WASO-PCE-COR-NTS-NPS0034418; PPWOPCADT0, PPMPSPD1T.Y00000 (211); OMB Control Number 1024-0283]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Application for Designation as National Recreation Trail or National Water Trail</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Park Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of information collection; request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, we, the National Park Service (NPS) are proposing to renew an information collection with revisions.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Interested persons are invited to submit comments on or before November 14, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments and suggestions on the information collection requirements should be submitted by the date specified above in 
                        <E T="02">DATES</E>
                         to 
                        <E T="03">http://www.reginfo.gov/public/do/PRAMain.</E>
                         Find this particular information collection by selecting “Currently under Review—Open for Public Comments” or by using the search function. Please provide a copy of your comments to the NPS Information Collection Clearance Officer (ADIR-ICCO), 12201 Sunrise Valley Drive, (MS-242) Reston, VA 20191 (mail); or 
                        <E T="03">phadrea_ponds@nps.gov</E>
                         (email). Please include “1024-0283” in the subject line of your comments.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        To request additional information about this ICR, contact Peter Bonsall, National Trails System Program Specialist, National Recreation Trails Coordinator for the Department of the Interior, 12795 W Alameda Parkway, Lakewood, CO 80228; at 
                        <E T="03">peter_bonsall@nps.gov</E>
                         (email), or (303) 969-2620 (telephone). Please reference OMB Control Number 1024-0283 in the subject line of your comments. Individuals in the United States who are deaf, deafblind, hard of hearing, or have a speech disability may dial 711 (TTY, TDD, or TeleBraille) to access telecommunications relay services. Individuals outside the United States should use the relay services offered within their country to make international calls to the point of contact in the United States. You may also view the ICR at 
                        <E T="03">http://www.reginfo.gov/public/do/PRAMain.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In accordance with the Paperwork Reduction Act of 1995, we provide the general public and other Federal agencies with an opportunity to comment on new, proposed, revised, and continuing collections of information. This helps us assess the impact of our information collection requirements and minimize the public's reporting burden. It also helps the public understand our information collection requirements and provide the requested data in the desired format.</P>
                <P>
                    On January 12, 2022, we published a 
                    <E T="04">Federal Register</E>
                     notice soliciting comments on this collection of information for 60 days, (87 FR 1779) ending on March 14, 2022. No comments were received.
                </P>
                <P>We are again soliciting comments on the proposed ICR described below. We are especially interested in public comment addressing the following issues: (1) is the collection necessary to the proper functions of the NPS; (2) will this information be processed and used in a timely manner; (3) is the estimate of burden accurate; (4) how might the NPS enhance the quality, utility, and clarity of the information to be collected; and (5) how might the NPS minimize the burden of this collection on the respondents, including through the use of information technology.</P>
                <P>Comments that you submit in response to this notice are a matter of public record. We will include or summarize each comment in our request to OMB to approve this ICR. Before including your address, phone number, email address, or other personal identifying information in your comment, you should be aware that your entire comment—including your personal identifying information—may be made publicly available at any time. While you can ask us in your comment to withhold your personal identifying information from public review, we cannot guarantee that we will be able to do so.</P>
                <P>
                    <E T="03">Abstract:</E>
                     The NPS administers the NRT program as authorized by section 4 of the National Trails System Act (16 U.S.C. 1243) and Secretarial Order No. 3319, which establishes National Water Trails as a class of National Recreation Trails and directs that such trails collectively be considered in a National Water Trails System.
                </P>
                <P>
                    The NPS uses forms 10-1002: 
                    <E T="03">Application for Designation as National Water Trail</E>
                     and 10-1003: 
                    <E T="03">Application for Designation as National Recreation Trail,</E>
                     to evaluate the applications for adherence to NRT requirements and criteria. NPS Approval of an application is based on (1) the sufficiency of information provided on the application form and in supporting documentation, such as photographs, maps, and written landowner consents that accompany the form, and (2) successfully meeting the NRT requirements and criteria. Successful applications are forwarded to the Secretary of the Interior for approval. Revisions to Forms 10-1002: 
                    <E T="03">Application for Designation—National Water Trails System</E>
                     and 10-1003: 
                    <E T="03">Application for Designation—National Recreation Trail</E>
                     are intended to better clarify trail attributes, provide more detailed public information, and align questions asked to establish a more unified application process.
                    <PRTPAGE P="62444"/>
                </P>
                <P>
                    <E T="03">Title of Collection:</E>
                     Application for Designation as National Recreation Trail or National Water Trail.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1024-0283.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     NPS 10-1002: 
                    <E T="03">Application for Designation as National Water Trail</E>
                     and NPS 10-1003: 
                    <E T="03">Application for Designation as National Recreation Trail.</E>
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision of a currently approved collection.
                </P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     Private individuals; businesses; educational institutions; nonprofit organizations; state, tribal, and local governments; and Federal agency land units.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Respondents:</E>
                     30.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Responses:</E>
                     30.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Burden Hours:</E>
                     130 hours.
                </P>
                <P>
                    <E T="03">Respondent's Obligation:</E>
                     Required to obtain or retain a benefit.
                </P>
                <P>
                    <E T="03">Frequency of Collection:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Total Estimated Annual Nonhour Burden Cost:</E>
                     None.
                </P>
                <FP>
                    *
                    <E T="03">rounded to nearest hour</E>
                </FP>
                <P>An agency may not conduct or sponsor and a person is not required to respond to a collection of information unless it displays a currently valid OMB control number.</P>
                <P>
                    The authority for this action is the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <SIG>
                    <NAME>Phadrea Ponds,</NAME>
                    <TITLE>Information Collection Clearance Officer, National Park Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22363 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4312-52-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>National Park Service</SUBAGY>
                <DEPDOC>[NPS-WASO-NAGPRA-NPS0034710; PPWOCRADN0-PCU00RP14.R50000]</DEPDOC>
                <SUBJECT>Notice of Inventory Completion Amendment: University of California, Berkeley, Berkeley, CA</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Park Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; amendment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with the Native American Graves Protection and Repatriation Act (NAGPRA), the University of California, Berkeley, has amended a Notice of Inventory Completion published in the 
                        <E T="04">Federal Register</E>
                         on February 2, 2005. This notice amends both the number of associated funerary objects and the cultural affiliation of the human remains and associated funerary objects removed from Sonoma County, CA.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Repatriation of the human remains and associated funerary objects in this notice may occur on or after November 14, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Alex Lucas; University of California, Berkeley; Office of Government and Community Relations, 120 California Hall, Berkeley, CA 94720, telephone (925) 791-7231, email 
                        <E T="03">nagpra-ucb@berkeley.edu.</E>
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice is published as part of the National Park Service's administrative responsibilities under NAGPRA. The determinations in this notice are the sole responsibility of the University of California, Berkeley. The National Park Service is not responsible for the determinations in this notice. Additional information on the amendments and determinations in this notice, including the results of consultation, can be found in the inventory or related records held by the University of California, Berkeley.</P>
                <HD SOURCE="HD1">Amendment</HD>
                <P>
                    This notice amends the determinations published in a Notice of Inventory Completion in the 
                    <E T="04">Federal Register</E>
                     (70 FR 5466-5467, February 2, 2005). Repatriation of the items in the original Notice of Inventory Completion has not occurred.
                </P>
                <P>Following additional consultation, this notice amends both the number of associated funerary objects and the cultural affiliation of the human remains and associated funerary objects removed from site CA-Son-5 in Sonoma County, CA.</P>
                <P>The four associated funerary objects (previously identified as three associated funerary objects) are one stone pestle, one clam shell bead, one lot of shells, and one lot of stone blades and flakes.</P>
                <P>
                    Site CA-Son-5 is located in a region that has been occupied by Pomo speakers since approximately 5,000 B.C. Based on geographical location, age of the burial, and information provided during consultation, the human remains are culturally affiliated with descendants of the Pomo. The modern-day representatives of the Pomo in Sonoma County are the Cloverdale Rancheria of Pomo Indians of California; Dry Creek Rancheria of Pomo Indians, California (
                    <E T="03">previously</E>
                     listed as Dry Creek Rancheria of Pomo Indians of California); Federated Indians of Graton Rancheria, California; Guidiville Rancheria of California; Kashia Band of Pomo Indians of the Stewarts Point Rancheria, California; Lytton Rancheria of California; Middletown Rancheria of Pomo Indians of California; Pinoleville Pomo Nation, California (
                    <E T="03">previously</E>
                     listed as Pinoleville Rancheria of Pomo Indians of California); and the Robinson Rancheria (
                    <E T="03">previously</E>
                     listed as Robinson Rancheria Band of Pomo Indians, California).
                </P>
                <HD SOURCE="HD1">Determinations (as Amended)</HD>
                <P>Pursuant to NAGPRA and its implementing regulations, and after consultation with the appropriate Indian Tribes and Native Hawaiian organizations, the University of California, Berkeley has determined that:</P>
                <P>• The human remains represent the physical remains of one individual of Native American ancestry.</P>
                <P>• The four objects are reasonably believed to have been placed with or near individual human remains at the time of death or later as part of the death rite or ceremony.</P>
                <P>
                    • There is a relationship of shared group identity that can be reasonably traced between the human remains and associated funerary objects and the Cloverdale Rancheria of Pomo Indians of California; Dry Creek Rancheria of Pomo Indians, California (
                    <E T="03">previously</E>
                     listed as Dry Creek Rancheria of Pomo Indians of California); Federated Indians of Graton Rancheria, California; Guidiville Rancheria of California; Kashia Band of Pomo Indians of the Stewarts Point Rancheria, California; Lytton Rancheria of California; Middletown Rancheria of Pomo Indians of California; Pinoleville Pomo Nation, California (
                    <E T="03">previously</E>
                     listed as Pinoleville Rancheria of Pomo Indians of California); and the Robinson Rancheria (
                    <E T="03">previously</E>
                     listed as Robinson Rancheria Band of Pomo Indians, California).
                </P>
                <HD SOURCE="HD1">Requests for Repatriation</HD>
                <P>
                    Written requests for repatriation of the human remains and associated funerary objects in this notice must be sent to the Responsible Official identified in 
                    <E T="02">ADDRESSES</E>
                    . Requests for repatriation may be submitted by:
                </P>
                <P>1. Any one or more of the Indian Tribes or Native Hawaiian organizations identified in this notice.</P>
                <P>2. Any lineal descendant, Indian Tribe, or Native Hawaiian organization not identified in this notice who shows, by a preponderance of the evidence, that the requestor is a lineal descendant or a culturally affiliated Indian Tribe or Native Hawaiian organization.</P>
                <P>
                    Repatriation of the human remains and associated funerary objects in this notice to a requestor may occur on or after November 14, 2022. If competing requests for repatriation are received, the University of California, Berkeley 
                    <PRTPAGE P="62445"/>
                    must determine the most appropriate requestor prior to repatriation. Requests for joint repatriation of the human remains and associated funerary objects are considered a single request and not competing requests. The University of California, Berkeley is responsible for sending a copy of this notice to the Indian Tribes and Native Hawaiian organizations identified in this notice.
                </P>
                <P>
                    <E T="03">Authority:</E>
                     Native American Graves Protection and Repatriation Act, 25 U.S.C. 3003, and the implementing regulations, 43 CFR 10.9, 10.10, 10.13, and 10.14.
                </P>
                <SIG>
                    <DATED>Dated: October 5, 2022.</DATED>
                    <NAME>Melanie O'Brien,</NAME>
                    <TITLE>Manager, National NAGPRA Program.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22337 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4312-52-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>National Park Service</SUBAGY>
                <DEPDOC>[NPS-NERO-CHHO-34434; PPNCCHOHS0-PPMPSPD1Z.YM0000]</DEPDOC>
                <SUBJECT>Chesapeake and Ohio Canal National Historical Park Commission Request for Nominations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Park Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for nominations.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The National Park Service, U.S. Department of the Interior, is requesting nominations for qualified persons to serve as members of the Chesapeake and Ohio Canal National Historical Park Commission (Commission).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written nominations must be received by December 13, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Send nominations to: Mackensie Henn, Assistant to the Superintendent, Chesapeake and Ohio Canal National Historical Park, 142 W Potomac Street, Williamsport, Maryland 21795, or by email 
                        <E T="03">choh_information@nps.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mackensie Henn, by email 
                        <E T="03">choh_information@nps.gov</E>
                         or telephone at (240) 520-3135.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Commission was established by section 6 of the Chesapeake and Ohio Canal Development Act (16 U.S.C. 410y-4) and terminated January 8, 2011. The Commission has been extended by Public Law 113-178 and the new termination date is September 26, 2024. The purpose of the Commission is to meet and consult with the Secretary of the Interior (Secretary), or the Secretary's designee, on general policies and specific matters related to the administration and development of the Chesapeake and Ohio Canal National Historical Park.</P>
                <P>The Commission shall be composed of 19 members appointed by the Secretary for 5-year terms as follows: (1) Eight members to be appointed from recommendations submitted by the boards of commissioners or the county councils, as the case may be, of Montgomery, Frederick, Washington, and Allegany Counties, Maryland, of which two members shall be appointed from recommendations submitted by each such board or council, as the case may be; (2) Eight members to be appointed from recommendations submitted by the Governor of the State of Maryland, the Governor of the State of West Virginia, the Governor of the Commonwealth of Virginia, and the Mayor of the District of Columbia, of which two members shall be appointed from recommendations submitted by each such Governor or Mayor, as the case may be; and (3) Three members to be appointed by the Secretary, one of whom shall be designated Chair of the Commission and two of who shall be members of regularly constituted conservation organizations.</P>
                <P>
                    We are currently seeking members to represent all categories. The Chair will be appointed as a special Government employee (SGE). Please be aware that the individual selected to serve as the Chair will be required, prior to appointment, to file a Confidential Financial Disclosure Report in order to avoid involvement in real or apparent conflicts of interest. You may find a copy of the Confidential Financial Disclosure Report at the following website: 
                    <E T="03">https://www.doi.gov/ethics/special-government-employees/financial-disclosure.</E>
                     Additionally, after appointment, the Chair will be required to meet applicable financial disclosure and ethics training requirements. Please contact the Departmental Ethics Office at (202) 208-7960 or 
                    <E T="03">DOI_Ethics@sol.doi.gov</E>
                     with any questions about the SGE ethics requirements.
                </P>
                <P>Nominations should be typed and should include a resume providing an adequate description of the nominee's qualifications, including information that would enable the Department of the Interior to make an informed decision regarding meeting the membership requirements of the Commission and permit the Department to contact a potential member. All documentation, including letters of recommendation, must be compiled and submitted in one complete package. All those interested in membership, including current members whose terms are expiring, must follow the same nomination process. Members may not appoint deputies or alternates.</P>
                <P>Members of the Commission serve without compensation. However, while away from their homes or regular places of business in the performance of services for the Commission as approved by the NPS, members may be allowed travel expenses, including per diem in lieu of subsistence, in the same manner as persons employed intermittently in Government service are allowed such expenses under section 5703 of title 5 of the United States Code.</P>
                <EXTRACT>
                    <FP>(Authority: 16 U.S.C. 410y-4, as amended.)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Alma Ripps,</NAME>
                    <TITLE>Chief, Office of Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22293 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4312-52-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>National Park Service</SUBAGY>
                <DEPDOC>[NPS-WASO-NAGPRA-NPS0034711; PPWOCRADN0-PCU00RP14.R50000]</DEPDOC>
                <SUBJECT>Notice of Inventory Completion: University of Michigan, Ann Arbor, MI</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Park Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The University of Michigan has completed an inventory of human remains and associated funerary objects in consultation with the appropriate Indian Tribes or Native Hawaiian organizations and has determined that there is a cultural affiliation between the human remains and associated funerary objects and present-day Indian Tribes or Native Hawaiian organizations. Lineal descendants or representatives of any Indian Tribe or Native Hawaiian organization not identified in this notice that wish to request transfer of control of these human remains and associated funerary objects should submit a written request to the University of Michigan. If no additional requestors come forward, transfer of control of the human remains and associated funerary objects to the lineal descendants, Indian Tribes, or Native Hawaiian organizations stated in this notice may proceed.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Lineal descendants or representatives of any Indian Tribe or Native Hawaiian organization not identified in this notice that wish to request transfer of control of these human remains and associated funerary objects should submit a written request with information in support of the request to the University of Michigan at 
                        <PRTPAGE P="62446"/>
                        the address in this notice by November 14, 2022.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Dr. Ben Secunda, NAGPRA Project Manager, University of Michigan, Office of Research, 3003 South State Street, First Floor, Wolverine Tower, Ann Arbor, MI 48109-1274, telephone (734) 764-1185, email 
                        <E T="03">bsecunda@umich.edu.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Notice is here given in accordance with the Native American Graves Protection and Repatriation Act (NAGPRA), 25 U.S.C. 3003, of the completion of an inventory of human remains and associated funerary objects under the control of the University of Michigan, Ann Arbor, MI. The human remains and associated funerary objects were removed from the Moccasin Bluff site (20BE08) in Berrien County, MI.</P>
                <P>This notice is published as part of the National Park Service's administrative responsibilities under NAGPRA, 25 U.S.C. 3003(d)(3). The determinations in this notice are the sole responsibility of the museum, institution, or Federal agency that has control of the Native American human remains and associated funerary objects. The National Park Service is not responsible for the determinations in this notice.</P>
                <HD SOURCE="HD1">Consultation</HD>
                <P>
                    A detailed assessment of the human remains was made by the University of Michigan Museum of Anthropological Archaeology (UMMAA) professional staff in consultation with representatives of the Citizen Potawatomi Nation, Oklahoma; Forest County Potawatomi Community, Wisconsin; Hannahville Indian Community, Michigan; Match-e-be-nash-she-wish Band of Pottawatomi Indians of Michigan; Miami Tribe of Oklahoma; Nottawaseppi Huron Band of the Potawatomi, Michigan (
                    <E T="03">previously</E>
                     listed as Huron Potawatomi, Inc.); Pokagon Band of Potawatomi Indians, Michigan and Indiana; and the Prairie Band Potawatomi Nation (
                    <E T="03">previously</E>
                     listed as Prairie Band of Potawatomi Nation, Kansas) (hereafter referred to as “The Tribes”).
                </P>
                <HD SOURCE="HD1">History and Description of the Remains</HD>
                <P>In 1948, human remains representing, at minimum, one individual were removed from the Moccasin Bluff site (20BE08) in Berrien County, MI, by UMMAA archeologist Hale Smith. Smith uncovered three burials while excavating a trench at the multi-component site. All the individuals were found buried in an extended position and oriented in the same direction. According to a publication, Smith identified three burials at the site, but he presumably only excavated one of the burials, which he then brought to the Museum. The date range for this burial is A.D. 1400-1820, based on the extended burial treatment, with individuals facing the same direction, and the associated funerary objects. All the human remains listed in this notice were excavated by Smith in 1948. The associated funerary objects came from excavations by Smith in 1948; Joseph Birdsell, who excavated the site in 1938, and donated some of the funerary objects he recovered to the UMMAA in 1947; and Arthur Jelinek, who excavated the site in 1961. The human remains are of one child ≤13 years old, of indeterminate sex. No known individual was identified. The nine associated funerary objects are one lot of earthenware vessel sections; four lots of earthenware body sherds; one lot of lithic flakes; one lot of earthenware body sherds and small sherd crumb; one lot of lithics, ceramic sherds, and unworked faunal bone fragments; and one lot of reconstructed sections of an earthenware vessel including rim and body sherds.</P>
                <P>The human remains have been determined to be Native American based on mortuary treatment, diagnostic artifacts, and archeological context. A relationship of shared group identity can be reasonably traced between the Native American human remains from this site and the Potawatomi and Miami, based on archeological and historical records that indicate both Tribes had a predominant presence in the St. Joseph River Valley from the time of first contact with the French through the early-1800s. Both Tribes were known to have had close and friendly relations in this area. In the early-1800s, the Potawatomi leader Moccasin presided over a village in the immediate vicinity of the site (in present-day Buchanan, MI) on a bluff that now bears his name.</P>
                <HD SOURCE="HD1">Determinations Made by the University of Michigan</HD>
                <P>Officials of the University of Michigan have determined that:</P>
                <P>• Pursuant to 25 U.S.C. 3001(9), the human remains described in this notice represent the physical remains of one individual of Native American ancestry.</P>
                <P>• Pursuant to 25 U.S.C. 3001(3)(A), the nine objects described in this notice are reasonably believed to have been placed with or near individual human remains at the time of death or later as part of the death rite or ceremony.</P>
                <P>• Pursuant to 25 U.S.C. 3001(2), there is a relationship of shared group identity that can be reasonably traced between the Native American human remains and associated funerary objects and The Tribes.</P>
                <HD SOURCE="HD1">Additional Requestors and Disposition</HD>
                <P>
                    Lineal descendants or representatives of any Indian Tribe or Native Hawaiian organization not identified in this notice that wish to request transfer of control of these human remains and associated funerary objects should submit a written request with information in support of the request to Dr. Ben Secunda, NAGPRA Project Manager, University of Michigan, Office of Research, 3003 South State Street, First Floor, Wolverine Tower, Ann Arbor, MI 48109-1274, telephone (734) 764-1185, email 
                    <E T="03">bsecunda@umich.edu,</E>
                     by November 14, 2022. After that date, if no additional requestors have come forward, transfer of control of the human remains and associated funerary objects to The Tribes may proceed.
                </P>
                <P>The University of Michigan is responsible for notifying The Tribes that this notice has been published.</P>
                <SIG>
                    <DATED>Dated: October 5, 2022.</DATED>
                    <NAME>Melanie O'Brien,</NAME>
                    <TITLE>Manager, National NAGPRA Program.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22336 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4312-52-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Ocean Energy Management</SUBAGY>
                <DEPDOC>[OMB Control Number 1010-0006; Docket ID: BOEM-2017-0016]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Leasing of Sulfur or Oil and Gas in the Outer Continental Shelf</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Ocean Energy Management, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of information collection; request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, the Bureau of Ocean Energy Management (BOEM) is proposing this information collection request (ICR) to renew Control Number 1010-0006 with revisions.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by the Office of Management and Budget (OMB) no later than November 14, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit your written comments on this ICR to the OMB's desk officer for the Department of the Interior at 
                        <E T="03">www.reginfo.gov/public/do/PRAMain</E>
                         within 30 days of publication of this notice. From the 
                        <E T="03">www.reginfo.gov/public/do/PRAMain</E>
                         landing page, find this information collection by selecting “Currently under Review—Open for Public Comments” or 
                        <PRTPAGE P="62447"/>
                        by using the search function. Please provide a copy of your comments by parcel delivery to the BOEM Information Collection Clearance Officer, Anna Atkinson, Bureau of Ocean Energy Management, 45600 Woodland Road, Sterling, Virginia 20166; or by email to 
                        <E T="03">anna.atkinson@boem.gov.</E>
                         Please reference OMB Control Number 1010-0006 in the subject line of your comments. You may also comment by searching the docket number BOEM-2017-0016 at 
                        <E T="03">http://www.reginfo.gov/public/do/PRAMain.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Anna Atkinson by email at 
                        <E T="03">anna.atkinson@boem.gov</E>
                         or by telephone at 703-787-1025. Individuals in the United States who are deaf, deafblind, hard of hearing, or have a speech disability may dial 711 (TTY, TDD, or TeleBraille) to access telecommunications relay services. Individuals outside the United States should use the relay services offered within their country to make international calls to the point-of-contact in the United States.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In accordance with the Paperwork Reduction Act of 1995, BOEM provides the general public and other Federal agencies with an opportunity to comment on new, proposed, revised, and continuing collections of information. This helps BOEM assess the impact of its information collection requirements and minimize the public's reporting burden. It also helps the public understand BOEM's information collection requirements and provide the requested data in the desired format.</P>
                <P>
                    <E T="03">Title of Collection:</E>
                     “Leasing of Sulfur or Oil and Gas in the Outer Continental Shelf.”
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This ICR concerns the paperwork requirements in 30 CFR parts 550, 556, and 560. This ICR also concerns the use of forms to process bonds, transfer interest in leases, and file relinquishments.
                </P>
                <P>
                    The Outer Continental Shelf Lands Act, as amended (43 U.S.C. 1331 
                    <E T="03">et seq.</E>
                    ), authorizes the Secretary of the Interior to prescribe rules and regulations to administer leasing of the Outer Continental Shelf (OCS) and all operations conducted under a lease. Operations on the OCS must develop oil and natural gas resources in a manner that is consistent with the need to make such resources available to meet the Nation's energy needs; balance orderly energy resource development with protection of human, marine, and coastal environments; ensure the public a fair return on the resources of the OCS; and preserve and maintain free enterprise competition. Also, the Energy Policy and Conservation Act of 1975 prohibits certain lease bidding arrangements (42 U.S.C. 6213(a)).
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1010-0006.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                </P>
                <P>• BOEM-0150, “Assignment of Record Title Interest in Federal OCS Oil and Gas Lease”;</P>
                <P>• BOEM-0151, “Assignment of Operating Rights Interest in Federal OCS Oil and Gas Lease”;</P>
                <P>• BOEM-0152, “Relinquishment of Federal OCS Oil and Gas Lease”;</P>
                <P>• BOEM-2028, “Outer Continental Shelf (OCS) Mineral Lessee's or Operator's Bond”;</P>
                <P>• BOEM-2028A, “Outer Continental Shelf (OCS) Mineral Lessee's or Operator's Supplemental Bond”; and</P>
                <P>• BOEM-2030, “Outer Continental Shelf (OCS) Pipeline Right-of-Way Grant Bond”.</P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision of a currently approved information collection.
                </P>
                <P>
                    <E T="03">Respondents/Affected Public:</E>
                     Federal oil, gas, or sulfur lessees and operators; right-of-way grant holders.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Responses:</E>
                     21,826 responses.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Burden Hours:</E>
                     21,935 hours.
                </P>
                <P>
                    <E T="03">Respondent's Obligation:</E>
                     Mandatory or required to obtain or retain a benefit.
                </P>
                <P>
                    <E T="03">Frequency of Collection:</E>
                     On occasion or annual.
                </P>
                <P>
                    <E T="03">Total Estimated Annual Non-Hour Burden Cost:</E>
                     $766,053.
                </P>
                <P>
                    <E T="03">Estimated Reporting and Recordkeeping Hour Burden:</E>
                     We expect the burden estimate for the renewal will be 21,935 hours with 21,826 responses, which reflects an increase of 2,881 hours and 11,628 responses. One hour of the increase accounts for Alaska's surety bond submission (30 CFR 550.1011), which was not previously included in the annual burden hours. The remaining increase of 2,880 annual burden hours accounts for submissions of documents under 30 CFR 556.715 and 556.808. Under the current 1010-0006, BOEM accounted for the burden hours to file the requisite fees under 30 CFR 556.715 and 556.808 but did not account for the burden hours to submit the requisite documents.
                </P>
                <P>The following table details the individual components and respective burden hour estimates of this ICR.</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,r100,r50,12,12">
                    <TTITLE>Burden Breakdown</TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            30 CFR 
                            <LI>Part 550 Subpart J</LI>
                        </CHED>
                        <CHED H="1">Reporting requirement *</CHED>
                        <CHED H="1">Hour burden</CHED>
                        <CHED H="2">Non-hour cost burdens</CHED>
                        <CHED H="1">
                            Average 
                            <LI>number of </LI>
                            <LI>annual </LI>
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">Annual burden hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">550.1011(a)</ENT>
                        <ENT>Provide surety bond (Form BOEM-2030) and required information</ENT>
                        <ENT>Gulf of Mexico 0.25</ENT>
                        <ENT>52</ENT>
                        <ENT>13</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>Pacific 3.5</ENT>
                        <ENT>3</ENT>
                        <ENT>11</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>Alaska 1</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">30 CFR 550, Subpart J, Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>56 Responses</ENT>
                        <ENT>25 hours</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="62448"/>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,r100,r50,12,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            30 CFR 
                            <LI>Part 556 and NTLs</LI>
                        </CHED>
                        <CHED H="1">Reporting requirement *</CHED>
                        <CHED H="1">Hour burden</CHED>
                        <CHED H="2">Non-hour cost burdens</CHED>
                        <CHED H="1">
                            Average 
                            <LI>number of </LI>
                            <LI>annual </LI>
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">Annual burden hours</CHED>
                    </BOXHD>
                    <ROW EXPSTB="04" RUL="s">
                        <ENT I="21">
                            <E T="02">Subpart A</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00" RUL="n,n,s,s,n">
                        <ENT I="01">104(b)</ENT>
                        <ENT>Submit confidentiality agreement</ENT>
                        <ENT>0.25</ENT>
                        <ENT>500</ENT>
                        <ENT>125</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">106</ENT>
                        <ENT>Cost recovery and service fees; confirmation receipt</ENT>
                        <ENT A="01">Cost recovery and service fees and associated documentation are covered under individual requirements throughout part. **</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW RUL="n,n,s,s,n">
                        <ENT I="01">107</ENT>
                        <ENT>
                            Submit required documentation electronically through BOEM-approved system; comply with filing specifications, as directed by notice in the 
                            <E T="02">Federal Register</E>
                             in accordance with 30 CFR 560.500
                        </ENT>
                        <ENT A="01">Burden covered in 30 CFR 560.500</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">107</ENT>
                        <ENT>File seals, documents, statements, signatures, etc., to establish legal status of all future submissions (paper or electronic)</ENT>
                        <ENT>10 min</ENT>
                        <ENT>400</ENT>
                        <ENT>67</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">Subtotal</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>900</ENT>
                        <ENT>192</ENT>
                    </ROW>
                    <ROW EXPSTB="04" RUL="s">
                        <ENT I="21">
                            <E T="02">Subpart B</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00" RUL="n,n,s,s,n">
                        <ENT I="01">201-204</ENT>
                        <ENT>Submit nominations, suggestions, comments, and information in response to requests for information or comments, draft or proposed 5-year leasing program, etc., including information from States and local governments, Federal agencies, industry, and others</ENT>
                        <ENT A="01">
                            Not considered an information
                            <LI>collection (IC) as defined in 5 CFR 1320.3(h)(4).</LI>
                        </ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">202-204</ENT>
                        <ENT>Submit nominations &amp; specific information requested in draft proposed 5-year leasing program, from States and local governments</ENT>
                        <ENT>4</ENT>
                        <ENT>69</ENT>
                        <ENT>276</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">Subtotal</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>69</ENT>
                        <ENT>276</ENT>
                    </ROW>
                    <ROW EXPSTB="04" RUL="s">
                        <ENT I="21">
                            <E T="02">Subpart C</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00" RUL="n,n,s,s,n">
                        <ENT I="01">301; 302</ENT>
                        <ENT>Submit response &amp; specific information requested in requests for industry interest and calls for information and nominations, etc., on areas proposed for leasing; including information from States and local governments</ENT>
                        <ENT A="01">Not considered IC as defined in 5 CFR 1320.3(h)(4).</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">302(d)</ENT>
                        <ENT>Request summary of interest (nonproprietary information) for calls for information and requests for interest, etc</ENT>
                        <ENT>1</ENT>
                        <ENT>5</ENT>
                        <ENT>5</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">305; 306</ENT>
                        <ENT>States or local governments submit comments, recommendations, other responses on size, timing, or location of proposed lease sale. Request extension; enter agreement</ENT>
                        <ENT>4</ENT>
                        <ENT>25</ENT>
                        <ENT>100</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">Subtotal</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>30</ENT>
                        <ENT>105</ENT>
                    </ROW>
                    <ROW EXPSTB="04" RUL="s">
                        <ENT I="21">
                            <E T="02">Subpart D</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00" RUL="n,n,s,s,n">
                        <ENT I="01">400-402; 405</ENT>
                        <ENT>Establish file for qualification; submit evidence and certification for lessee and bidder qualification. Provide updates; obtain BOEM approval &amp; qualification number</ENT>
                        <ENT>2</ENT>
                        <ENT>107</ENT>
                        <ENT>214</ENT>
                    </ROW>
                    <ROW RUL="n,n,s,s,n">
                        <ENT I="01">403(c)</ENT>
                        <ENT>Request hearing on disqualification</ENT>
                        <ENT A="01">Requirement not considered IC under 5 CFR 1320.3(h)(9).</ENT>
                        <ENT> 0</ENT>
                    </ROW>
                    <ROW RUL="n,n,s,s,n">
                        <ENT I="01">403; 404</ENT>
                        <ENT>Notify BOEM if you or your principals are excluded, disqualified, or convicted of a crime—Federal non- procurement debarment and suspension requirements; request exception; enter transaction</ENT>
                        <ENT>1.5</ENT>
                        <ENT>50</ENT>
                        <ENT>75</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <PRTPAGE P="62449"/>
                        <ENT I="01">405</ENT>
                        <ENT>Notify BOEM of all mergers, name changes, or change of business</ENT>
                        <ENT A="01">Requirement not considered IC under 5 CFR 1320.3(h)(1).</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">Subtotal</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>157</ENT>
                        <ENT>289</ENT>
                    </ROW>
                    <ROW EXPSTB="04" RUL="s">
                        <ENT I="21">
                            <E T="02">Subpart E</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00" RUL="n,n,s,s,n">
                        <ENT I="01">500; 501</ENT>
                        <ENT>Submit bids, deposits, and required information, including GDIS &amp; maps; in manner specified. Make data available to BOEM</ENT>
                        <ENT>5</ENT>
                        <ENT>2,000</ENT>
                        <ENT>10,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">500(e); 517</ENT>
                        <ENT>Request reconsideration of bid decision</ENT>
                        <ENT A="01">Requirement not considered IC under 5 CFR 1320.3(h)(9).</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">501(e)</ENT>
                        <ENT>Apply for reimbursement</ENT>
                        <ENT A="01">Burden covered in OMB Control Number 1010-0048, 30 CFR 551.</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW RUL="n,n,s,s,n">
                        <ENT I="01">511(b); 517</ENT>
                        <ENT>Submit appeal of listing on restricted joint bidders list; appeal bid decision</ENT>
                        <ENT A="01">Requirement not considered IC under 5 CFR 1320.3(h)(9).</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW RUL="n,n,s,s,n">
                        <ENT I="01">513; 514</ENT>
                        <ENT>File statement and detailed report of production. Make documents available to BOEM</ENT>
                        <ENT>2</ENT>
                        <ENT>100</ENT>
                        <ENT>200</ENT>
                    </ROW>
                    <ROW RUL="n,n,s,s,n">
                        <ENT I="01">515</ENT>
                        <ENT>Request exemption from bidding restrictions; submit appropriate information</ENT>
                        <ENT A="01">Requirement not considered IC under 5 CFR 1320.3(h)(9).</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">516</ENT>
                        <ENT>File agreement on determination of lessee following BOEM's notice of tie bid</ENT>
                        <ENT>3.5</ENT>
                        <ENT>2</ENT>
                        <ENT>7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">520; 521; 600(c)</ENT>
                        <ENT>Execute lease (includes submission of evidence of authorized agent, completion of steps leading to lease execution, and request adjusted effective date of lease); submit required data and rental</ENT>
                        <ENT>1</ENT>
                        <ENT>852</ENT>
                        <ENT>852</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">520(b)</ENT>
                        <ENT>Provide acceptable bond for payment of a deferred bonus</ENT>
                        <ENT>0.25</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">Subtotal</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>2,955</ENT>
                        <ENT>11,060</ENT>
                    </ROW>
                    <ROW EXPSTB="04" RUL="s">
                        <ENT I="21">
                            <E T="02">Subparts F, G, H</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00" RUL="n,n,s">
                        <ENT I="01">700-716</ENT>
                        <ENT>File application and required information for assignment or transfer of record title or any other lease interest (Form BOEM-0150) (includes sale, sublease, segregation exchange, transfer); request effective date and confidentiality; provide notifications. **</ENT>
                        <ENT>1</ENT>
                        <ENT>1,414</ENT>
                        <ENT>1,414</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT A="02">$198 fee × 1,414 forms = $279,972</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">715(a); 808(a)</ENT>
                        <ENT>File required instruments creating or transferring working interests, etc., for record purposes. **</ENT>
                        <ENT>1</ENT>
                        <ENT>2,369</ENT>
                        <ENT>2,369</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT A="02">$29 fee × 2,369 filings = $68,701</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">715(b); 808(b)</ENT>
                        <ENT>
                            Submit “non-required” documents, for record purposes that respondents want BOEM to file with the lease document. 
                            <E T="03">(Accepted on behalf of lessees as a service; BOEM does not require nor need them.)</E>
                        </ENT>
                        <ENT>.25</ENT>
                        <ENT>11,518</ENT>
                        <ENT>2,880</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT A="02">$29 fee × 11,518 filings = $334,022</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">800-810</ENT>
                        <ENT>File application and required information for assignment or transfer of operating interest (Form BOEM-0151) (includes sale, sublease, segregation exchange, severance, transfer); request effective date; provide notifications. **</ENT>
                        <ENT>1</ENT>
                        <ENT>421</ENT>
                        <ENT>421</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT A="02">$198 fee × 421 forms = $83,358</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">Subtotal</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>15,722</ENT>
                        <ENT>7,084</ENT>
                    </ROW>
                    <ROW EXPSTB="03" RUL="s">
                        <PRTPAGE P="62450"/>
                        <ENT I="22"> </ENT>
                        <ENT>$766,053</ENT>
                    </ROW>
                    <ROW EXPSTB="04" RUL="s">
                        <ENT I="21">
                            <E T="02">Subpart I</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">900(a)-(e); 901; 902; 903(a)</ENT>
                        <ENT>Submit form for OCS mineral lessee's and operator's bond (Form BOEM-2028); execute bond</ENT>
                        <ENT>0.33</ENT>
                        <ENT>135</ENT>
                        <ENT>45</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">900(c), (d), (f), (g); 901(c), (d), (f); 902(e)</ENT>
                        <ENT>Demonstrate financial worth and ability to carry out present and future financial obligations, request approval of another form of security, or request reduction in amount of supplemental bond required on BOEM-approved forms. Monitor and submit required information</ENT>
                        <ENT>3.5</ENT>
                        <ENT>166</ENT>
                        <ENT>581</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">900(e); 901; 902; 903(a)</ENT>
                        <ENT>Submit form for OCS mineral lessee's and operator's supplemental plugging &amp; abandonment bond (Form BOEM-2028A); execute bond</ENT>
                        <ENT>0.25</ENT>
                        <ENT>141</ENT>
                        <ENT>35</ENT>
                    </ROW>
                    <ROW RUL="n,n,s,s,n">
                        <ENT I="01">900(f), (g)</ENT>
                        <ENT>Submit authority for Regional Director to sell Treasury or alternate type of securities</ENT>
                        <ENT>2</ENT>
                        <ENT>12</ENT>
                        <ENT>24</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">901</ENT>
                        <ENT>Submit exploration plan, development and production plan, development operations coordination document</ENT>
                        <ENT A="01">IC burden covered in separate approved collection for 1010-0151, 30 CFR part 550, subpart B.</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW RUL="n,n,s,s,n">
                        <ENT I="01">901(f)</ENT>
                        <ENT>Submit oral/written comment on adjusted bond amount and information</ENT>
                        <ENT A="01">Requirement not considered IC under 5 CFR 1320.3(h)(9).</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">903(b)</ENT>
                        <ENT>Notify BOEM of any lapse in bond coverage and action filed alleging lessee, surety, or guarantor is insolvent or bankrupt</ENT>
                        <ENT>1</ENT>
                        <ENT>4</ENT>
                        <ENT>4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">904</ENT>
                        <ENT>Provide plan and instructions to fund lease-specific abandonment account and related information; request approval to withdraw funds</ENT>
                        <ENT>12</ENT>
                        <ENT>2</ENT>
                        <ENT>24</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">905</ENT>
                        <ENT>Provide third-party guarantee, indemnity agreement, financial and required information, related notices, reports, and annual update; notify BOEM if guarantor becomes unqualified</ENT>
                        <ENT>19</ENT>
                        <ENT>46</ENT>
                        <ENT>874</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">905(d)(3); 906</ENT>
                        <ENT>Provide notice of and request approval to terminate period of liability, cancel bond, or other security; provide required information</ENT>
                        <ENT>0.5</ENT>
                        <ENT>378</ENT>
                        <ENT>189</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">907(c)(2)</ENT>
                        <ENT>Provide information to demonstrate lease will be brought into compliance</ENT>
                        <ENT>16</ENT>
                        <ENT>5</ENT>
                        <ENT>80</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">Subtotal</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>889</ENT>
                        <ENT>1,856</ENT>
                    </ROW>
                    <ROW EXPSTB="04" RUL="s">
                        <ENT I="21">
                            <E T="02">Subpart K</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">1101</ENT>
                        <ENT>Request relinquishment (Form BOEM-0152) of lease; submit required information</ENT>
                        <ENT>1</ENT>
                        <ENT>247</ENT>
                        <ENT>247</ENT>
                    </ROW>
                    <ROW RUL="n,n,s,s,n">
                        <ENT I="01">1102</ENT>
                        <ENT>Request additional time to bring lease into compliance</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">1102(c)</ENT>
                        <ENT>Comment on cancellation.</ENT>
                        <ENT A="01">Requirement not considered IC under 5 CFR 1320.3(h)(9).</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="03">Subtotal</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>248</ENT>
                        <ENT>248</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="05">30 CFR 556 Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>20,970</ENT>
                        <ENT>21,110</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT> </ENT>
                        <ENT A="02">$766,053 Non-Hour Cost Burdens</ENT>
                    </ROW>
                </GPOTABLE>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,r100,r50,12,12">
                    <BOXHD>
                        <CHED H="1">30 CFR Part 560</CHED>
                        <CHED H="1">Reporting requirement *</CHED>
                        <CHED H="1">Hour burden</CHED>
                        <CHED H="1">
                            Average 
                            <LI>number of </LI>
                            <LI>annual </LI>
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">Annual burden hours</CHED>
                    </BOXHD>
                    <ROW RUL="n,n,s,s,n">
                        <ENT I="01">560.224(a)</ENT>
                        <ENT>Request BOEM to reconsider field assignment of a lease</ENT>
                        <ENT A="01">Requirement not considered IC under 5 CFR 1320.3(h)(9)</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">560.500</ENT>
                        <ENT>
                            Submit required documentation electronically through BOEM-approved system; comply with filing specifications, as directed by notice in the 
                            <E T="02">Federal Register</E>
                             (
                            <E T="03">e.g.,</E>
                             bonding info.)
                        </ENT>
                        <ENT>1</ENT>
                        <ENT>800</ENT>
                        <ENT>800</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="62451"/>
                        <ENT I="03">30 CFR 560 Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>800 </ENT>
                        <ENT>800</ENT>
                    </ROW>
                    <ROW RUL="n,n,n,s">
                        <ENT I="05">Total Reporting for Collection</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>21,826</ENT>
                        <ENT>21,935</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT/>
                        <ENT/>
                        <ENT A="01">$766,053 Non-Hour Cost Burdens</ENT>
                    </ROW>
                    <TNOTE>* In the future, BOEM may require electronic filing of certain submissions.</TNOTE>
                    <TNOTE>** Cost recovery/service fees.</TNOTE>
                    <TNOTE>—For requests of approval for various operations or submission of plans or applications, the burdens are included with other OMB-approved collections: for BOEM, 30 CFR part 550 (subpart A, Control Number 1010-0114; subpart B, Control Number 1010-0151); and for BSEE, 30 CFR part 250 (subpart A, Control Number 1014-0022; subpart D, Control Number 1014-0018).</TNOTE>
                    <TNOTE>—All submission for designation of operator (Form BOEM-1123) under 30 CFR parts 550, 556, and 560 are captured in OMB Control Number 1010-0114.</TNOTE>
                </GPOTABLE>
                <P>
                    A 
                    <E T="04">Federal Register</E>
                     notice with a 60-day public comment period on this proposed ICR was published on May 24, 2022 (87 
                    <E T="03">FR</E>
                     31576). BOEM did not receive any comments during the 60-day comment period.
                </P>
                <P>BOEM is again soliciting comments on the proposed ICR. BOEM is especially interested in public comments addressing the following issues: (1) is the collection necessary to the proper functions of BOEM; (2) what can BOEM do to ensure that this information is processed and used in a timely manner; (3) is the burden estimate accurate; (4) how might BOEM enhance the quality, utility, and clarity of the information to be collected; and (5) how might BOEM minimize the burden of this collection on the respondents, including minimizing the burden through the use of information technology?</P>
                <P>
                    Comments submitted in response to this notice are a matter of public record and will be available for public review on 
                    <E T="03">www.reginfo.gov.</E>
                     You should be aware that your entire comment—including your address, phone number, email address, or other personally identifiable information included in your comment—may be made publicly available. Even if BOEM withholds your information in the context of this ICR, your comment is subject to the Freedom of Information Act (FOIA). If your comment is requested under the FOIA, your information will only be withheld if BOEM determines that a FOIA exemption to disclosure applies. BOEM will make such a determination in accordance with the Department of the Interior's (DOI) FOIA regulations and applicable law.
                </P>
                <P>In order for BOEM to consider withholding from disclosure your personally identifiable information, you must identify, in a cover letter, any information contained in your comments that, if released, would constitute a clearly unwarranted invasion of your personal privacy. You must also briefly describe any possible harmful consequence of the disclosure of information, such as embarrassment, injury, or other harm.</P>
                <P>
                    Note that BOEM will make available for public inspection all comments on 
                    <E T="03">www.reginfo.gov,</E>
                     in their entirety, submitted by organizations and businesses or by individuals identifying themselves as representatives of organizations or businesses.
                </P>
                <P>BOEM protects proprietary information in accordance with FOIA (5 U.S.C. 552), DOI's implementing regulations (43 CFR part 2), and 30 CFR parts 550 and 552 promulgated pursuant to the Outer Continental Shelf Lands Act (43 U.S.C. 1352(c)).</P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a valid OMB control number.</P>
                <P>
                    The authority for this action is the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <SIG>
                    <NAME>Karen Thundiyil,</NAME>
                    <TITLE>Chief, Office of Regulations, Bureau of Ocean Energy Management.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22344 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-MR-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[Investigation No. 337-TA-1252]</DEPDOC>
                <SUBJECT>Certain Robotic Floor Cleaning Devices and Components Thereof; Notice of Request for Submissions on the Public Interest</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. International Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given that on October 7, 2022, the presiding administrative law judge (“ALJ”) issued an Initial Determination on Violation of Section 337. The ALJ also issued a Recommended Determination on remedy and bonding should a violation be found in the above-captioned investigation. The Commission is soliciting submissions on public interest issues raised by the recommended relief should the Commission find a violation. This notice is soliciting comments from the public only.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Clint Gerdine, Esq., Office of the General Counsel, U.S. International Trade Commission, 500 E Street SW, Washington, DC 20436, telephone (202)708-2310. Copies of non-confidential documents filed in connection with this investigation may be viewed on the Commission's electronic docket (EDIS) at 
                        <E T="03">https://edis.usitc.gov.</E>
                         For help accessing EDIS, please email 
                        <E T="03">EDIS3Help@usitc.gov.</E>
                         General information concerning the Commission may also be obtained by accessing its internet server at 
                        <E T="03">https://www.usitc.gov.</E>
                         Hearing-impaired persons are advised that information on this matter can be obtained by contacting the Commission's TDD terminal on (202) 205-1810.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Section 337 of the Tariff Act of 1930 provides that, if the Commission finds a violation, it shall exclude the articles concerned from the United States:</P>
                <EXTRACT>
                    <FP>unless, after considering the effect of such exclusion upon the public health and welfare, competitive conditions in the United States economy, the production of like or directly competitive articles in the United States, and United States consumers, it finds that such articles should not be excluded from entry.</FP>
                </EXTRACT>
                <FP>19 U.S.C. 1337(d)(1). A similar provision applies to cease and desist orders. 19 U.S.C. 1337(f)(1).</FP>
                <P>
                    The Commission is soliciting submissions on public interest issues raised by the recommended relief 
                    <PRTPAGE P="62452"/>
                    should the Commission find a violation, specifically: (1) limited exclusion orders directed to certain robotic floor cleaning devices and components thereof imported, sold for importation, and/or sold after importation by respondents SharkNinja Operating LLC, SharkNinja Management LLC, SharkNinja Management Co., SharkNinja Sales Co., and EP Midco LLC, all of Needham, Massachusetts; and SharkNinja Hong Kong Co. Ltd. of Hong Kong Island, Hong Kong (collectively, the “Respondents”) that infringe one or more of asserted claims 9 and 12 of U.S. Patent No. 9,884,423 and claims 1 and 9 of U.S. Patent No. 10,813,517; and (2) cease and desist orders directed to Respondents with respect to these asserted claims. Parties are to file public interest submissions pursuant to 19 CFR 210.50(a)(4).
                </P>
                <P>The Commission is interested in further development of the record on the public interest in this investigation. Accordingly, members of the public are invited to file submissions of no more than five (5) pages, inclusive of attachments, concerning the public interest in light of the ALJ's Recommended Determination on Remedy and Bonding issued in this investigation on October 7, 2022. Comments should address whether issuance of the recommended remedial orders in this investigation, should the Commission find a violation, would affect the public health and welfare in the United States, competitive conditions in the United States economy, the production of like or directly competitive articles in the United States, or United States consumers.</P>
                <P>In particular, the Commission is interested in comments that:</P>
                <P>(i) explain how the articles potentially subject to the recommended remedial orders are used in the United States;</P>
                <P>(ii) identify any public health, safety, or welfare concerns in the United States relating to the recommended orders;</P>
                <P>(iii) identify like or directly competitive articles that complainant, its licensees, or third parties make in the United States which could replace the subject articles if they were to be excluded;</P>
                <P>(iv) indicate whether complainant, complainant's licensees, and/or third-party suppliers have the capacity to replace the volume of articles potentially subject to the recommended orders within a commercially reasonable time; and</P>
                <P>(v) explain how the recommended orders would impact consumers in the United States.</P>
                <P>Written submissions must be filed no later than by the close of business on November 7, 2022.</P>
                <P>
                    Persons filing written submissions must file the original document electronically on or before the deadlines stated above. The Commission's paper filing requirements in 19 CFR 210.4(f) are currently waived. 85 FR 15798 (Mar. 19, 2020). Submissions should refer to the investigation number (“Inv. No. 337-TA-1252”) in a prominent place on the cover page and/or the first page. (
                    <E T="03">See Handbook for Electronic Filing Procedures, https://www.usitc.gov/documents/handbook_on_filing_procedures.pdf.</E>
                    ). Persons with questions regarding filing should contact the Secretary (202-205-2000).
                </P>
                <P>Any person desiring to submit a document to the Commission in confidence must request confidential treatment by marking each document with a header indicating that the document contains confidential information. This marking will be deemed to satisfy the request procedure set forth in Rules 201.6(b) and 210.5(e)(2) (19 CFR 201.6(b) &amp; 210.5(e)(2)). Documents for which confidential treatment by the Commission is properly sought will be treated accordingly. Any non-party wishing to submit comments containing confidential information must serve those comments on the parties to the investigation pursuant to the applicable Administrative Protective Order. A redacted non-confidential version of the document must also be filed simultaneously with any confidential filing and must be served in accordance with Commission Rule 210.4(f)(7)(ii)(A) (19 CFR 210.4(f)(7)(ii)(A)). All information, including confidential business information and documents for which confidential treatment is properly sought, submitted to the Commission for purposes of this investigation may be disclosed to and used: (i) by the Commission, its employees and Offices, and contract personnel (a) for developing or maintaining the records of this or a related proceeding, or (b) in internal investigations, audits, reviews, and evaluations relating to the programs, personnel, and operations of the Commission including under 5 U.S.C. Appendix 3; or (ii) by U.S. government employees and contract personnel, solely for cybersecurity purposes. All contract personnel will sign appropriate nondisclosure agreements. All nonconfidential written submissions will be available for public inspection on EDIS.</P>
                <P>This action is taken under the authority of section 337 of the Tariff Act of 1930, as amended (19 U.S.C. 1337), and in part 210 of the Commission's Rules of Practice and Procedure (19 CFR part 210).</P>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: October 11, 2022.</DATED>
                    <NAME>Katherine Hiner,</NAME>
                    <TITLE>Acting Secretary to the Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22381 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[Investigation No. 337-TA-1318]</DEPDOC>
                <SUBJECT>Certain Graphics Systems, Components Thereof, and Digital Televisions Containing the Same; Notice of Commission Decision Not To Review Initial Determinations Terminating the Investigation as to Certain Patent Claims and Granting Complainants' Motion To Amend the Complaint and Notice of Investigation</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. International Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given that the U.S. International Trade Commission (“the Commission”) has determined not to review two initial determinations (“IDs”) of the presiding administrative law judge (“ALJ”): (1) Order No. 23 terminating the investigation as to claims 17-21 of U.S. Patent No. 8,468,547 (“the '547 patent”) (collectively, the “Withdrawn Claims”); and (2) Order No. 24 granting complainants' motion to amend the complaint and notice of investigation (“NOI”) in the above-captioned investigation to correct the names of two respondents.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Clint Gerdine, Esq., Office of the General Counsel, U.S. International Trade Commission, 500 E Street SW, Washington, DC 20436, telephone (202) 708-2310. Copies of non-confidential documents filed in connection with this investigation may be viewed on the Commission's electronic docket (EDIS) at 
                        <E T="03">https://edis.usitc.gov.</E>
                         For help accessing EDIS, please email 
                        <E T="03">EDIS3Help@usitc.gov.</E>
                         General information concerning the Commission may also be obtained by accessing its internet server at 
                        <E T="03">https://www.usitc.gov.</E>
                         Hearing-impaired persons are advised that information on this matter can be obtained by contacting the Commission's TDD terminal, telephone (202) 205-1810.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Commission instituted this investigation on June 7, 2022, based on a complaint 
                    <PRTPAGE P="62453"/>
                    filed on behalf of Advanced Micro Devices, Inc. of Santa Clara, California and ATI Technologies ULC of Ontario, Canada (collectively, “Complainants”). 87 FR 34718-19 (Jun. 7, 2022). The complaint, as supplemented, alleges violations of section 337 of the Tariff Act of 1930, as amended, 19 U.S.C. 1337, based upon the importation into the United States, the sale for importation, and the sale within the United States after importation of certain graphics systems, components thereof, and digital televisions containing the same by reason of infringement of certain claims of the '547 patent and U.S. Patent Nos. 7,742,053; 8,760,454; 11,184,628; and 8,854,381. The complaint further alleges that a domestic industry exists and is in the process of being established. The Commission's NOI named fourteen (14) respondents, including: TCL Industries Holdings Co., Ltd., TCL Technology Group Corporation, TCL King Electrical Appliances (Huizhou) Co. Ltd., and Shenzhen TCL New Technologies Co., Ltd., all of Guangdong, China; TCL Industries Holdings (H.K.) Limited, TCL Electronics Holdings Limited f/k/a TCL Multimedia Technology Holdings, Ltd., TTE Corporation, TCL Holdings (BVI) Limited, TCL MOKA International Limited, and TCL Overseas Marketing Ltd., all of New Territories, Hong Kong; TCL Smart Device (Vietnam) Co., Ltd. of Binh Duong Province, Vietnam; Manufacturas Avanzadas SA de CV of Chihuahua, Mexico; TCL Electronics Mexico, S de RL de CV of Distrito Federal, Mexico City, Mexico; and Realtek Semiconductor Corp. of Hsinchu, Taiwan. The Office of Unfair Import Investigations is not participating in the investigation.
                </P>
                <P>On September 16, 2022, Complainants filed an unopposed motion to terminate the investigation as to the Withdrawn Claims based on the withdrawal of the allegations in the complaint as to those claims.</P>
                <P>Also on September 16, 2022, Complainants filed an unopposed motion for leave to amend the complaint and NOI to change the name of respondent “TCL Industries Holdings (H.K.) Limited” to “TCL Industries Holdings (H.K.) Co. Limited,” and the name of respondent “Shenzhen TCL New Technologies Co., Ltd.” to “Shenzhen TCL New Technology Co., Ltd.”</P>
                <P>
                    On September 20, 2022, the ALJ issued the subject IDs (Order Nos. 23, 24) granting both Complainants' motion for partial termination of the investigation as to the Withdrawn Claims and Complainants' motion for leave to amend the complaint and NOI. Order No. 23 finds that the motion for termination satisfies Commission Rule 210.21(a)(1), 19 CFR 210.21(a)(1), and that no extraordinary circumstances exist that would prevent the requested partial termination. Order No. 24 finds that Complainants have shown good cause to amend the NOI and that “[c]orrection of a Respondent's name is in the interests of the parties and the public.” 
                    <E T="03">See</E>
                     Order No. 24 at 2 (quoting Complainants' Motion at 3). No petitions for review were filed.
                </P>
                <P>The Commission has determined not to review the subject IDs. Claims 17-21 of the '547 patent are terminated from this investigation, and the NOI is amended to correct the names of the indicated respondents.</P>
                <P>The Commission vote for this determination took place on October 7, 2022.</P>
                <P>The authority for the Commission's determination is contained in section 337 of the Tariff Act of 1930, as amended, 19 U.S.C. 1337, and in Part 210 of the Commission's Rules of Practice and Procedure, 19 CFR part 210.</P>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: October 11, 2022.</DATED>
                    <NAME>Katherine Hiner,</NAME>
                    <TITLE>Acting Secretary to the Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22356 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <SUBJECT>Notice of Receipt of Complaint; Solicitation of Comments Relating to the Public Interest</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. International Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Notice is hereby given that the U.S. International Trade Commission has received a complaint entitled 
                        <E T="03">Certain Electronic Devices, Semiconductor Devices, and Components Thereof, DN 3647;</E>
                         the Commission is soliciting comments on any public interest issues raised by the complaint or complainant's filing pursuant to the Commission's Rules of Practice and Procedure.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Katherine M. Hiner, Acting Secretary to the Commission, U.S. International Trade Commission, 500 E Street SW, Washington, DC 20436, telephone (202) 205-2000. The public version of the complaint can be accessed on the Commission's Electronic Document Information System (EDIS) at 
                        <E T="03">https://edis.usitc.gov.</E>
                         For help accessing EDIS, please email 
                        <E T="03">EDIS3Help@usitc.gov.</E>
                         General information concerning the Commission may also be obtained by accessing its internet server at United States International Trade Commission (USITC) at 
                        <E T="03">https://www.usitc.gov</E>
                         . The public record for this investigation may be viewed on the Commission's Electronic Document Information System (EDIS) at 
                        <E T="03">https://edis.usitc.gov.</E>
                         Hearing-impaired persons are advised that information on this matter can be obtained by contacting the Commission's TDD terminal on (202) 205-1810.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Commission has received a complaint and a submission pursuant to § 210.8(b) of the Commission's Rules of Practice and Procedure filed on behalf Bell Semiconductor, LLC on October 6, 2022. The complaint alleges violations of section 337 of the Tariff Act of 1930 (19 U.S.C. 1337) in the importation into the United States, the sale for importation, and the sale within the United States after importation of regarding certain electronic devices, semiconductor devices, and components thereof. The complainant names as respondents: NXP Semiconductors, N.V. of Netherlands; NXP B.V., of Netherlands; NXP USA, Inc. of Austin, TX; SMC Networks, Inc. d/b/a/IgniteNet, of Irvine, CA; Micron Technology, Inc. of Boise, ID; NVIDIA Corporation of Santa Clara, CA; Advanced Micro Devices, Inc. of Santa Clara, CA; Acer, Inc. of Taiwan; Acer America Corporation of San Jose, CA; Infineon Technologies AG of Germany; Infineon Technologies America Corp. of Milpitas, CA; Qualcomm Technologies, Inc. of San Diego, CA; Motorola Mobility LLC of Chicago, IL and Western Digital Technologies, Inc. of San Jose, CA. The complainant requests that the Commission issue a limited exclusion order and cease and desist orders and impose a bond upon respondent's alleged infringing articles during the 60-day Presidential review period pursuant to 19 U.S.C. 1337(j).</P>
                <P>
                    Proposed respondents, other interested parties, and members of the public are invited to file comments on any public interest issues raised by the complaint or § 210.8(b) filing. Comments should address whether issuance of the relief specifically requested by the complainant in this investigation would affect the public health and welfare in the United States, competitive conditions in the United States economy, the production of like or directly competitive articles in the United States, or United States consumers.
                    <PRTPAGE P="62454"/>
                </P>
                <P>In particular, the Commission is interested in comments that:</P>
                <P>(i) explain how the articles potentially subject to the requested remedial orders are used in the United States;</P>
                <P>(ii) identify any public health, safety, or welfare concerns in the United States relating to the requested remedial orders;</P>
                <P>(iii) identify like or directly competitive articles that complainant, its licensees, or third parties make in the United States which could replace the subject articles if they were to be excluded;</P>
                <P>(iv) indicate whether complainant, complainant's licensees, and/or third party suppliers have the capacity to replace the volume of articles potentially subject to the requested exclusion order and/or a cease and desist order within a commercially reasonable time; and</P>
                <P>(v) explain how the requested remedial orders would impact United States consumers.</P>
                <P>
                    Written submissions on the public interest must be filed no later than by close of business, eight calendar days after the date of publication of this notice in the 
                    <E T="04">Federal Register</E>
                    . There will be further opportunities for comment on the public interest after the issuance of any final initial determination in this investigation. Any written submissions on other issues must also be filed by no later than the close of business, eight calendar days after publication of this notice in the 
                    <E T="04">Federal Register</E>
                    . Complainant may file replies to any written submissions no later than three calendar days after the date on which any initial submissions were due. No other submissions will be accepted, unless requested by the Commission. Any submissions and replies filed in response to this Notice are limited to five (5) pages in length, inclusive of attachments.
                </P>
                <P>
                    Persons filing written submissions must file the original document electronically on or before the deadlines stated above. Submissions should refer to the docket number (“Docket No. 3647”) in a prominent place on the cover page and/or the first page. (
                    <E T="03">See</E>
                     Handbook for Electronic Filing Procedures, Electronic Filing Procedures.) 
                    <SU>1</SU>
                    <FTREF/>
                     Please note the Secretary's Office will accept only electronic filings during this time. Filings must be made through the Commission's Electronic Document Information System (EDIS, 
                    <E T="03">https://edis.usitc.gov.</E>
                    ) No in-person paper-based filings or paper copies of any electronic filings will be accepted until further notice. Persons with questions regarding filing should contact the Secretary at 
                    <E T="03">EDIS3Help@usitc.gov.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Handbook for Electronic Filing Procedures: 
                        <E T="03">https://www.usitc.gov/documents/handbook_on_filing_procedures.pdf.</E>
                    </P>
                </FTNT>
                <P>
                    Any person desiring to submit a document to the Commission in confidence must request confidential treatment. All such requests should be directed to the Secretary to the Commission and must include a full statement of the reasons why the Commission should grant such treatment. 
                    <E T="03">See</E>
                     19 CFR 201.6. Documents for which confidential treatment by the Commission is properly sought will be treated accordingly. All information, including confidential business information and documents for which confidential treatment is properly sought, submitted to the Commission for purposes of this Investigation may be disclosed to and used: (i) by the Commission, its employees and Offices, and contract personnel (a) for developing or maintaining the records of this or a related proceeding, or (b) in internal investigations, audits, reviews, and evaluations relating to the programs, personnel, and operations of the Commission including under 5 U.S.C. appendix 3; or (ii) by U.S. government employees and contract personnel,
                    <SU>2</SU>
                    <FTREF/>
                     solely for cybersecurity purposes. All nonconfidential written submissions will be available for public inspection at the Office of the Secretary and on EDIS.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         All contract personnel will sign appropriate nondisclosure agreements.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Electronic Document Information System (EDIS): 
                        <E T="03">https://edis.usitc.gov.</E>
                    </P>
                </FTNT>
                <P>This action is taken under the authority of section 337 of the Tariff Act of 1930, as amended (19 U.S.C. 1337), and of §§ 201.10 and 210.8(c) of the Commission's Rules of Practice and Procedure (19 CFR 201.10, 210.8(c)).</P>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: October 7, 2022.</DATED>
                    <NAME>Katherine Hiner,</NAME>
                    <TITLE>Acting Secretary to the Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22353 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[Inv. No. 337-TA-1332]</DEPDOC>
                <SUBJECT>Certain Semiconductors and Devices and Products Containing the Same, Including Printed Circuit Boards, Automotive Parts, and Automobiles; Institution of Investigation</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. International Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given that a complaint was filed with the U.S. International Trade Commission on August 23, 2022, under section 337 of the Tariff Act of 1930, as amended, on behalf of Daedalus Prime LLC of Bronxville, New York. A supplement to the complaint was filed on September 12, 2022. The complaint alleges violations of section 337 based upon the importation into the United States, the sale for importation, and the sale within the United States after importation of certain semiconductors and devices and products containing the same, including printed circuit boards, automotive parts, and automobiles by reason of the infringement of certain claims of U.S. Patent No. 8,775,833 (“the '833 patent”); U.S. Patent No. 8,898,494 (“the '494 patent”); U.S. Patent No. 9,575,895 (“the '895 patent”); U.S. Patent No. 10,049,080 (“the '080 patent”); U.S. Patent No. 10,394,300 (“the '300 patent”); and U.S. Patent No. 10,705,588 (“the '588 patent”). The complaint further alleges that an industry in the United States exists as required by the applicable Federal Statute.</P>
                    <P>The complainant requests that the Commission institute an investigation and, after the investigation, issue a limited exclusion order and cease and desist orders.</P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The complaint, except for any confidential information contained therein, may be viewed on the Commission's electronic docket (EDIS) at 
                        <E T="03">https://edis.usitc.gov.</E>
                         For help accessing EDIS, please email 
                        <E T="03">EDIS3Help@usitc.gov.</E>
                         Hearing impaired individuals are advised that information on this matter can be obtained by contacting the Commission's TDD terminal on (202) 205-1810. Persons with mobility impairments who will need special assistance in gaining access to the Commission should contact the Office of the Secretary at (202) 205-2000. General information concerning the Commission may also be obtained by accessing its internet server at 
                        <E T="03">https://www.usitc.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Pathenia M. Proctor, The Office of Unfair Import Investigations, U.S. International Trade Commission, telephone (202) 205-2560.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Authority:</E>
                     The authority for institution of this investigation is contained in section 337 of the Tariff Act of 1930, as amended, 19 U.S.C. 1337, and in section 210.10 of the Commission's Rules of Practice and Procedure, 19 CFR 210.10 (2022).
                    <PRTPAGE P="62455"/>
                </P>
                <P>
                    <E T="03">Scope of Investigation:</E>
                     Having considered the complaint, the U.S. International Trade Commission, on October 6, 2022, 
                    <E T="03">ordered that</E>
                    —
                </P>
                <P>(1) Pursuant to subsection (b) of section 337 of the Tariff Act of 1930, as amended, an investigation be instituted to determine whether there is a violation of subsection (a)(1)(B) of section 337 in the importation into the United States, the sale for importation, or the sale within the United States after importation of certain products identified in paragraph (2) by reason of infringement of one or more of claims 1-18 of the '833 patent; claims 1-18 of the '494 patent; claims 1-17 of the '895 patent; claims 1-24 of the '080 patent; claims 1-19 of the '300 patent; and claims 1-20 of the '588 patent, and whether an industry in the United States exists or is in the process of being established as required by subsection (a)(2) of section 337;</P>
                <P>(2) Pursuant to section 210.10(b)(1) of the Commission's Rules of Practice and Procedure, 19 CFR 210.10(b)(1), the plain language description of the accused products or category of accused products, which defines the scope of the investigation, is “semiconductor chips and printed circuit boards for use in automobile infotainment systems and instrument clusters, and automobile infotainment systems, instrument clusters, and automobiles containing the same, and components thereof”;</P>
                <P>(3) Pursuant to Commission Rule 210.50(b)(l), 19 CFR 210.50(b)(1), the presiding administrative law judge shall take evidence or other information and hear arguments from the parties or other interested persons with respect to the public interest in this investigation, as appropriate, and provide the Commission with findings of fact and a recommended determination on this issue, which shall be limited to the statutory public interest factors set forth in 19 U.S.C. l337(d)(l), (f)(1), (g)(1)</P>
                <P>(4) For the purpose of the investigation so instituted, the following are hereby named as parties upon which this notice of investigation shall be served:</P>
                <P>(a) The complainant is:</P>
                <FP SOURCE="FP-1">Daedalus Prime LLC, 51 Pondfield Road, Suite 3, Bronxville, NY 10708</FP>
                <P>(b) The respondents are the following entities alleged to be in violation of section 337, and are the parties upon which the complaint is to be served:</P>
                <FP SOURCE="FP-1">Avnet, Inc., 2211 South 47th Street, Phoenix, AZ 85034</FP>
                <FP SOURCE="FP-1">Digi-Key Electronics, 701 Brooks Avenue South, Thief River Falls, MN 56701</FP>
                <FP SOURCE="FP-1">Mercedes-Benz Group AG, 70546 Stuttgart, Germany</FP>
                <FP SOURCE="FP-1">Mercedes-Benz AG, Epplestraβe 225, 70567 Stuttgart-Möhringen, Germany</FP>
                <FP SOURCE="FP-1">Mercedes-Benz USA, LLC, 1 Mercedes-Benz Drive, Sandy Springs, GA 30328</FP>
                <FP SOURCE="FP-1">Mouser Electronics, Inc., 1000 North Main Street, Mansfield, TX 76063</FP>
                <FP SOURCE="FP-1">Newark, 300 S Riverside Plaza, Suite 2200, Chicago, IL 60606</FP>
                <FP SOURCE="FP-1">NXP Semiconductors N.V., High Tech Campus 60, 5656 AG Eindhoven, Netherlands</FP>
                <FP SOURCE="FP-1">NXP USA, Inc., 6501 W William Cannon Dr., Austin, TX 78735</FP>
                <P>(c) The Office of Unfair Import Investigations, U.S. International Trade Commission, 500 E Street SW, Suite 401, Washington, DC 20436; and</P>
                <P>(5) For the investigation so instituted, the Chief Administrative Law Judge, U.S. International Trade Commission, shall designate the presiding Administrative Law Judge.</P>
                <P>Responses to the complaint and the notice of investigation must be submitted by the named respondents in accordance with section 210.13 of the Commission's Rules of Practice and Procedure, 19 CFR 210.13. Pursuant to 19 CFR 201.16(e) and 210.13(a), as amended in 85 FR 15798 (March 19, 2020), such responses will be considered by the Commission if received not later than 20 days after the date of service by the complainant of the complaint and the notice of investigation. Extensions of time for submitting responses to the complaint and the notice of investigation will not be granted unless good cause therefor is shown.</P>
                <P>Failure of a respondent to file a timely response to each allegation in the complaint and in this notice may be deemed to constitute a waiver of the right to appear and contest the allegations of the complaint and this notice, and to authorize the administrative law judge and the Commission, without further notice to the respondent, to find the facts to be as alleged in the complaint and this notice and to enter an initial determination and a final determination containing such findings, and may result in the issuance of an exclusion order or a cease and desist order or both directed against the respondent.</P>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: October 7, 2022.</DATED>
                    <NAME>Katherine Hiner,</NAME>
                    <TITLE>Acting Secretary to the Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22288 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[Investigation No. 337-TA-1226]</DEPDOC>
                <SUBJECT>Certain Artificial Eyelash Extension Systems, Products, and Components Thereof; Notice of the Commission's Final Determination Finding No Violation of Section 337; Termination of the Investigation</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. International Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given that the U.S. International Trade Commission (“Commission”) has found no violation of section 337 of the Tariff Act of 1930, as amended, in the above-captioned investigation. The investigation is terminated.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Lynde Herzbach, Office of the General Counsel, U.S. International Trade Commission, 500 E Street SW, Washington, DC 20436, telephone (202) 205-3228. Copies of non-confidential documents filed in connection with this investigation may be viewed on the Commission's electronic docket (EDIS) at 
                        <E T="03">https://edis.usitc.gov.</E>
                         For help accessing EDIS, please email 
                        <E T="03">EDIS3Help@usitc.gov.</E>
                         General information concerning the Commission may also be obtained by accessing its internet server at 
                        <E T="03">https://www.usitc.gov.</E>
                         Hearing-impaired persons are advised that information on this matter can be obtained by contacting the Commission's TDD terminal on (202) 205-1810.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On October 28, 2020, the Commission instituted this investigation under section 337 of the Tariff Act of 1930, as amended, 19 U.S.C. 1337 (“section 337”), based on a complaint filed by Lashify, Inc. of Glendale, California (“Lashify”). 
                    <E T="03">See</E>
                     85 FR 68366-67 (Oct. 28, 2020). The complaint, as supplemented, alleges a violation of section 337 based upon the importation into the United States, sale for importation, or sale after importation into the United States of certain artificial eyelash extension systems, products, and components thereof by reason of infringement of certain claims of U.S. Patent Nos. 10,660,388 (“the '388 patent”) and 10,721,984 (“the '984 patent”), and the sole claims of U.S. Design Patent Nos. D877,416 (“the D'416 patent”) and D867,664 (“the D'664 patent”), respectively (collectively, the “Asserted Patents”). The complaint also alleges the existence of a domestic industry. The notice of 
                    <PRTPAGE P="62456"/>
                    investigation (“NOI”) names nine respondents, including: KISS Nail Products, Inc. of Port Washington, New York (“KISS”); Ulta Beauty, Inc. of Bolingbrook, Illinois; CVS Health Corporation of Woonsocket, Rhode Island; Walmart, Inc. of Bentonville, Arkansas (“Walmart”); Qingdao Hollyren Cosmetics Co., Ltd. d/b/a Hollyren of Shandong Province, China (“Hollyren”); Qingdao Xizi International Trading Co., Ltd. d/b/a Xizi Lashes of Shandong Province, China (“Xizi Lashes”); Qingdao LashBeauty Cosmetic Co., Ltd. d/b/a Worldbeauty of Qingdao, China (“Worldbeauty”); Alicia Zeng d/b/a Lilac St. and Artemis Family Beginnings, Inc. of San Francisco, California (collectively, “Lilac”); and Rachael Gleason d/b/a Avant Garde Beauty Co. of Dallas, Texas. 
                    <E T="03">Id.</E>
                     The Office of Unfair Import Investigations (“OUII”) is also a party to the investigation. 
                    <E T="03">Id.</E>
                </P>
                <P>
                    The Commission later amended the complaint and NOI to substitute CVS Pharmacy, Inc. of Woonsocket, Rhode Island (“CVS”) in place of named respondent CVS Health Corporation and Ulta Salon, Cosmetics &amp; Fragrance, Inc. of Bolingbrook, Illinois (“Ulta”) in place of named respondent Ulta Beauty, Inc. 
                    <E T="03">See</E>
                     Order No. 10, 
                    <E T="03">unreviewed by</E>
                     Comm'n Notice (Feb. 10, 2021); 
                    <E T="03">see also</E>
                     86 FR 9535 (Feb. 16, 2021).
                </P>
                <P>
                    The Commission previously terminated the investigation as to claims 2-4 and 7 of the '388 patent and claims 6-8, 12, 18-19, 25-26, and 29 of the '984 patent based on Lashify's partial withdrawal of the complaint. 
                    <E T="03">See</E>
                     Order No. 24 (Apr. 23, 2021), 
                    <E T="03">unreviewed by</E>
                     Comm'n Notice (May 11, 2021). The Commission also previously terminated claims 2-5, 10-11, 14, 17, 21-22, and 24 of the '984 patent from the investigation. 
                    <E T="03">See</E>
                     Order No. 38 (June 22, 2021), 
                    <E T="03">unreviewed by</E>
                     Comm'n Notice (July 6, 2021).  
                </P>
                <P>
                    The Commission previously terminated Rachael Gleason d/b/a Avant Garde Beauty Company from the investigation based on a Consent Order. 
                    <E T="03">See</E>
                     Order No. 28, 
                    <E T="03">unreviewed by</E>
                     Comm'n Notice (May 20, 2021).
                </P>
                <P>
                    The Commission previously determined that Lashify failed to satisfy the technical prong of the domestic industry requirement for the '388 patent, thus terminating that patent from the investigation. 
                    <E T="03">See</E>
                     Order No. 35, 
                    <E T="03">unreviewed by</E>
                     Comm'n Notice (July 9, 2021).
                </P>
                <P>Prior to the issuance of the final initial determination, the remaining respondents included: KISS, Ulta, CVS, Walmart, Hollyren, Xizi Lashes, Worldbeauty, and Lilac (collectively, “Respondents”).</P>
                <P>On October 28, 2021, the presiding administrative law judge issued a final initial determination (“FID”), finding that no violation of section 337 has occurred in the importation into the United States, the sale for importation, or the sale within the United States after importation, of certain artificial eyelash extension systems, products, and components thereof. FID at 141-142. The FID finds that two accused products infringe the '984 patent and the'984 patent is not invalid, but also finds that Lashify has failed to satisfy the technical prong of the domestic industry requirement with respect to the '984 patent. The FID further finds that the D'416 patent and D'664 patent are infringed and not invalid, and that Lashify satisfied the technical prong with respect to both design patents. The FID further finds that Lashify has failed to satisfy the economic prong of the domestic industry requirement with respect to all of the Asserted Patents remaining in the investigation.</P>
                <P>On November 29, 2021, respondents KISS, Ulta, Walmart, and CVS filed a joint submission on the public interest pursuant to Commission Rule 210.50(a)(4) (19 CFR 210.50 (a)(4)). Lashify and OUII did not file a statement on the public interest. No submissions were received in response to the Commission notice seeking public interest submissions. 86 FR 62844-45 (Nov. 12, 2021).</P>
                <P>
                    On January 20, 2022, the Commission determined to review the FID in part. 87 FR 4044-46 (Jan. 26, 2022). Specifically for the '984 patent, the Commission reviewed the FID's findings regarding the technical prong of the domestic industry requirement and the FID's findings that the asserted claims of the '984 patent are not invalid as obvious. 
                    <E T="03">Id.</E>
                     at 4045. The Commission also reviewed the FID's findings regarding the economic prong of the domestic industry requirement. 
                    <E T="03">Id.</E>
                     The Commission asked the parties to address two questions related to the issues under review with respect to the economic prong of the domestic industry requirement. 
                    <E T="03">Id.</E>
                </P>
                <P>On February 3, 2022, Lashify, Respondents, and OUII each filed an initial written response to the Commission's request for briefing. On February 10, 2022, Lashify, Respondents, and OUII each filed a reply submission.</P>
                <P>Having reviewed the record of the investigation, including the FID and the parties' submissions, the Commission has determined to find no violation of section 337 as to any Asserted Patent. Specifically, with respect to the '984 patent, the Commission has determined to: (1) affirm, with supplemental analysis, the FID's finding that Lashify has failed to satisfy the technical prong of the domestic industry requirement; and (2) take no position regarding whether claims 1, 9, 23, and 27 of the '984 patent are invalid for obviousness under 35 U.S.C. 103. The Commission has further determined to affirm, with supplemental reasoning, the FID's finding that Lashify failed to satisfy the economic prong of the domestic industry requirement for any of the Asserted Patents. Commissioners Karpel and Schmidtlein concur in the determination of no violation as to the '984 patent. However, they find a violation of section 337 as to the D'416 and D'664 patents. Specifically, they find that Lashify has satisfied the economic prong of the domestic industry requirement under subsection 337(a)(3)(B), but not under subsection 337(a)(3)(A), with respect to the D'416 and D'664 patents. They take no position on subsection 337(a)(3)(C) with respect to the D'416 and D'664 patents, or on whether Lashify satisfies the economic prong for the '984 patent.</P>
                <P>The investigation is terminated with a finding of no violation of section 337. The Commission's reasoning in support of its determinations is set forth more fully in its opinion. The reasoning in support of the separate views of Commissioners Karpel and Schmidtlein is set forth in the Separate Views of Commissioners Karpel and Schmidtlein in Dissent on the Economic Prong of the Domestic Industry Requirement as to U.S. Design Patent Nos. D877,416 and D867,664, issued concurrently therewith.</P>
                <P>The Commission vote for this determination took place on October 6, 2022.</P>
                <P>The authority for the Commission's determination is contained in section 337 of the Tariff Act of 1930, as amended (19 U.S.C. 1337), and in part 210 of the Commission's Rules of Practice and Procedure (19 CFR part 210).</P>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: October 6, 2022.</DATED>
                    <NAME>Katherine Hiner,</NAME>
                    <TITLE>Acting Secretary to the Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22287 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="62457"/>
                <AGENCY TYPE="S">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[USITC SE-22-043]</DEPDOC>
                <SUBJECT>Sunshine Act Meetings</SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">Agency Holding the Meeting:</HD>
                    <P> United States International Trade Commission.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">TIME AND DATE: </HD>
                    <P>October 21, 2022 at 11 a.m.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PLACE: </HD>
                    <P>Room 101, 500 E Street SW, Washington, DC 20436, Telephone: (202) 205-2000.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">STATUS: </HD>
                    <P>Open to the public.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">MATTERS TO BE CONSIDERED:</HD>
                    <P> </P>
                    <P>1. Agendas for future meetings: none.</P>
                    <P>2. Minutes.</P>
                    <P>3. Ratification List.</P>
                    <P>4. Commission vote on Inv. Nos. 701-TA-545-546 and 731-TA-1291-1297 (Review) and 731-TA-808 (Fourth Review) (Hot-Rolled Steel Flat Products from Australia, Brazil, Japan, Netherlands, Russia, South Korea, Turkey, and the United Kingdom). The Commission is currently scheduled to complete and file its determinations and views of the Commission on November 9, 2022.</P>
                    <P>5. Outstanding action jackets: none.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION: </HD>
                    <P>William Bishop, Supervisory Hearings and Information Officer, 202-205-2595.</P>
                    <P>The Commission is holding the meeting under the Government in the Sunshine Act, 5 U.S.C. 552(b). In accordance with Commission policy, subject matter listed above, not disposed of at the scheduled meeting, may be carried over to the agenda of the following meeting.</P>
                </PREAMHD>
                <SIG>
                    <P>By order of the Commission:</P>
                    <DATED>Issued: October 11, 2022.</DATED>
                    <NAME>William Bishop,</NAME>
                    <TITLE>Supervisory Hearings and Information Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22436 Filed 10-12-22; 11:15 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBJECT>Notice of Lodging of Proposed Consent Decree Under the Clean Air Act</SUBJECT>
                <P>
                    On October 6, 2022, the Department of Justice lodged a proposed Consent Decree (“Consent Decree”) with the United States District Court for the District of New Jersey in the lawsuit entitled 
                    <E T="03">United States and the State of New Jersey, Department of Environmental Protection</E>
                     v. 
                    <E T="03">Stony Brook Regional Sewerage Authority,</E>
                     Civil Action No. 3:22-cv-05922.
                </P>
                <P>In a Complaint, the United States, on behalf of the U.S. Environmental Protection Agency (“EPA”), and the State of New Jersey, on behalf of the Department of Environmental Protection, alleges that the Stony Brook Regional Sewerage Authority (“SBRSA”) violated the Clean Air Act (the “Act”), 42 U.S.C. 7413, by violating: (1) the Solid Waste Combustion provisions in Section 129 of the Clean Air Act, 42 U.S.C. 7429, and (2) the Federal Plan Requirements for Sewage Sludge Incineration Units Constructed on or Before October 14, 2010, 40 CFR part 62, subpart LLL (“Subpart LLL”). The proposed Consent Decree in this case requires SBRSA to pay a civil penalty of $335,750; to complete and submit a control plan and site-specific monitoring plan that include procedures to measure the mercury concentration in its sewage sludge; to conduct a Subpart LLL-compliant performance test; to develop and undertake standard operating procedures and recordkeeping and reporting obligations to minimize the use of the bypass stack; to undertake root cause analyses and corrective actions whenever there is an exceedance of the limit for the mercury concentration of the sewage sludge or the bypass stack is used; and, to pay stipulated penalties for violations of Consent Decree requirements. In addition, the Consent Decree requires a New Jersey-sponsored environmental project, to be overseen by the state, involving a contribution to the New Jersey Department of Environmental Protection's Environmental Mitigation Project Fund.</P>
                <P>
                    The publication of this notice opens a period for public comment on the proposed Consent Decree. Comments should be addressed to the Assistant Attorney General, Environment and Natural Resources Division, and should refer to 
                    <E T="03">United States and the State of New Jersey, Department of Environmental Protection</E>
                     v. 
                    <E T="03">Stony Brook Regional Sewerage Authority,</E>
                     D.J. Ref. No. 90-5-2-1-12080. All comments must be submitted no later than thirty (30) days after the publication date of this notice. Comments may be submitted either by email or by mail:
                </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="xs50,r50">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1" O="L">
                            <E T="03">To submit comments:</E>
                        </CHED>
                        <CHED H="1" O="L">
                            <E T="03">Send them to:</E>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">By email</ENT>
                        <ENT>
                            <E T="03">pubcomment-ees.enrd@usdoj.gov.</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">By mail</ENT>
                        <ENT>Assistant Attorney General, U.S. DOJ-ENRD, P.O. Box 7611, Washington, DC 20044-7611.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    During the public comment period, the proposed Consent Decree may be examined and downloaded at this Justice Department website: 
                    <E T="03">https://www.justice.gov/enrd/consent-decrees.</E>
                     We will provide a paper copy of the proposed Consent Decree upon written request and payment of reproduction costs. Please mail your request and payment to: Consent Decree Library, U.S. DOJ-ENRD, P.O. Box 7611, Washington, DC 20044-7611.
                </P>
                <P>Please enclose a check or money order for $13.50 (25 cents per page reproduction cost), payable to the United States Treasury.</P>
                <SIG>
                    <NAME>Henry Friedman,</NAME>
                    <TITLE>Assistant Chief, Environmental Enforcement Section, Environment &amp; Natural Resources Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22289 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Employment and Training Administration</SUBAGY>
                <SUBJECT>Workforce Innovation and Opportunity Act; Native American Employment and Training Council</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Employment and Training Administration, Department of Labor.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to the Federal Advisory Committee Act (FACA), as amended, and the Workforce Innovation and Opportunity Act (WIOA), notice is hereby given of the next meeting of the Native American Employment and Training Council (Council), as constituted under WIOA.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will begin at 9:00 a.m., (Pacific Daylight Time) on Sunday, October 30, 2022, and continue until 4:30 p.m. The meeting will reconvene at 9:00 a.m., on Monday, October 31, 2022, and adjourn at 4:30 p.m. The period from 3:00 p.m., to 4:00 p.m., on October 31, 2022, is reserved for participation and comment by members of the public.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meeting will be held in person at the Citizen Hotel, 926 J Street, Sacramento, California, 95814. The meeting will also be accessible virtually on the Zoom.gov platform. To join the meeting use the following:</P>
                    <FP SOURCE="FP-1">https://www.zoomgov.com/j/1612156612</FP>
                    <FP SOURCE="FP-1">Meeting ID: 161 215 6612</FP>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Council members and members of the public are encouraged to log on to Zoom.gov early to allow for connection issues and troubleshooting.</P>
                <P>
                    Members of the public not present may submit a written statement by 
                    <PRTPAGE P="62458"/>
                    Tuesday, October 25, 2022, to be included in the record of the meeting. Statements are to be submitted to Athena R. Brown, Designated Federal Officer (DFO), and U.S. Department of Labor at 
                    <E T="03">brown.athena@dol.gov.</E>
                     Persons who need special accommodations should contact Suzie Casal at (202) 309-8589 or 
                    <E T="03">casal.suzie@dol.gov,</E>
                     at least two business days before the meeting. The formal agenda will focus on the following topics: (1) NAETC issues/discussion, (2) Introduction to National Congress of American Indians Training and Key Priorities, (3) NAETC Two-Year Strategic Plan Update; (4) 477 Update from Federal Partners Meeting; (5) Upcoming Regional/National TAT conferences; (6) DINAP Report Out and Updates; and (7) public comment.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Athena R. Brown, DFO, Division of Indian and Native American Programs, Employment and Training Administration, U.S. Department of Labor, Room C-4311, 200 Constitution Avenue NW, Washington, DC, 20210. Telephone number (202) 693-3737 (VOICE) (this is not a toll-free number).</P>
                    <SIG>
                        <NAME>Brent Parton,</NAME>
                        <TITLE>Acting Assistant Secretary for Employment and Training, Labor.</TITLE>
                    </SIG>
                </FURINF>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22402 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-FR-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Bureau of Labor Statistics</SUBAGY>
                <SUBJECT>Data Users Advisory Committee; Notice of Meeting and Agenda</SUBJECT>
                <P>The Bureau of Labor Statistics Data Users Advisory Committee will meet on Thursday, November 10, 2022. This meeting will be held virtually.</P>
                <P>The Committee provides advice to the Bureau of Labor Statistics from the points of view of data users from various sectors of the U.S. economy, including the labor, business, research, academic, and government communities. The Committee advises on technical matters related to the collection, analysis, dissemination, and use of the Bureau's statistics, on its published reports, and on the broader aspects of its overall mission and function.</P>
                <P>The agenda for the meeting is as follows:</P>
                <FP SOURCE="FP-2">12:00 p.m. Commissioner's Welcome and Review of Agency Developments</FP>
                <FP SOURCE="FP-2">12:30 p.m. Update on NextGen News Releases</FP>
                <FP SOURCE="FP-2">1:15 p.m. Student MLR</FP>
                <FP SOURCE="FP-2">1:45 p.m. Break</FP>
                <FP SOURCE="FP-2">2:00 p.m. Reaching new audiences: New ways of presenting data for novice users: Scrollytelling and BLS educational material</FP>
                <FP SOURCE="FP-2">2:45 p.m. Reaching those with Limited English Proficiency</FP>
                <FP SOURCE="FP-2">3:15 p.m. BLS Apps: CareerInfo and Local Data</FP>
                <FP SOURCE="FP-2">3:45 p.m. Discussion of Future Topics and Concluding Remarks</FP>
                <FP SOURCE="FP-2">4:00 p.m. Conclusion</FP>
                <P>
                    The meeting is open to the public. Anyone planning to attend the meeting should contact Ebony Davis, Data Users Advisory Committee, at 
                    <E T="03">Davis.Ebony@bls.gov.</E>
                     Any questions about the meeting should be addressed to Mrs. Davis. Individuals who require special accommodations should contact Mrs. Davis at least two days prior to the meeting date.
                </P>
                <SIG>
                    <DATED>Signed at Washington, DC, this 7th day of October 2022.</DATED>
                    <NAME>Leslie Bennett,</NAME>
                    <TITLE>Chief, Division of Management Systems.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22322 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-24-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">LEGAL SERVICES CORPORATION</AGENCY>
                <SUBJECT>Sunshine Act Meeting</SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">TIME AND DATE: </HD>
                    <P>The Legal Services Corporation's (LSC) Board of Directors and its seven committees will meet October 20-21, 2022. On Thursday, October 20, the first meeting will begin at 9 a.m. Central Daylight Time (CDT), with the next meeting commencing promptly upon adjournment of the immediately preceding meeting. On Friday, October 21, the first meeting will again begin at 8 a.m., CDT, with the next meeting commencing promptly upon adjournment of the immediately preceding meeting.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PLACE:</HD>
                    <P> </P>
                    <P>
                        <E T="03">Public Notice of Virtual Meeting:</E>
                         LSC will conduct the October 20-21, 2022 meetings in-person and via Zoom.
                    </P>
                    <P>
                        <E T="03">Public Observation:</E>
                         Unless otherwise noted herein, the Board and all committee meetings will be open to public observation via Zoom. Members of the public who wish to participate remotely in the public proceedings may do so by following the directions provided below.
                    </P>
                </PREAMHD>
                <HD SOURCE="HD1">Directions for Open Sessions</HD>
                <HD SOURCE="HD2">Thursday, October 20, 2022</HD>
                <P>• To join the Zoom meeting by computer, please use this link.</P>
                <P>
                    • 
                    <E T="03">https://lsc-gov.zoom.us/j/84817635983?pwd=Wmx4Nit3NkZ3SUpZaTNLYlRMUE5PQT09&amp;from=addon</E>
                </P>
                <FP SOURCE="FP-1">
                    ○ 
                    <E T="03">Meeting ID:</E>
                     848 1763 5983
                </FP>
                <FP SOURCE="FP-1">
                    ○ 
                    <E T="03">Passcode:</E>
                     102022
                </FP>
                <P>• To join the Zoom meeting with one tap from your mobile phone, please click dial:</P>
                <FP SOURCE="FP-1">○ +13017158592,,84817635983# US (Washington, DC)</FP>
                <FP SOURCE="FP-1">○ +13126266799,,84817635983# US (Chicago)</FP>
                <P>• To join the Zoom meeting by telephone, please dial one of the following numbers:</P>
                <FP SOURCE="FP-1">○ +1 301 715 8592 US (Washington, DC)</FP>
                <FP SOURCE="FP-1">○ +1 312 626 6799 US (Chicago)</FP>
                <FP SOURCE="FP-1">○ +1 646 876 9923 US (New York)</FP>
                <FP SOURCE="FP-1">○ +1 346 248 7799 US (Houston)</FP>
                <FP SOURCE="FP-1">○ +1 408 638 0968 US (San Jose)</FP>
                <FP SOURCE="FP-1">○ +1 253 215 8782 US (Tacoma)</FP>
                <FP SOURCE="FP-1">
                    ○ 
                    <E T="03">Meeting ID:</E>
                     848 1763 5983
                </FP>
                <FP SOURCE="FP-1">
                    ○ 
                    <E T="03">Passcode:</E>
                     102022
                </FP>
                <FP SOURCE="FP-1">
                    ○ If calling from outside the U.S., find your local number here: 
                    <E T="03">https://lsc-gov.zoom.us/u/acCVpRj1FD</E>
                </FP>
                <HD SOURCE="HD2">Friday, October 21, 2022</HD>
                <P>• To join the Zoom meeting by computer, please use this link.</P>
                <FP SOURCE="FP-1">
                    ○ 
                    <E T="03">https://lsc-gov.zoom.us/j/89663269110?pwd=N2poRVFTMUN2dVRrTUdNYzZlV1FNdz09&amp;from=addon</E>
                </FP>
                <FP SOURCE="FP-1">
                    ○ 
                    <E T="03">Meeting ID:</E>
                     896 6326 9110
                </FP>
                <FP SOURCE="FP-1">
                    ○ 
                    <E T="03">Passcode:</E>
                     102122
                </FP>
                <P>• To join the Zoom meeting with one tap from your mobile phone, please click dial:</P>
                <FP SOURCE="FP-1">○ +13017158592,,89663269110# US (Washington, DC)</FP>
                <FP SOURCE="FP-1">○ +16468769923,,89663269110# US (New York)</FP>
                <P>• To join the Zoom meeting by telephone, please dial one of the following numbers:</P>
                <FP SOURCE="FP-1">○ +1 301 715 8592 US (Washington, DC)</FP>
                <FP SOURCE="FP-1">○ +1 646 876 9923 US (New York)</FP>
                <FP SOURCE="FP-1">○ +1 312 626 6799 US (Chicago)</FP>
                <FP SOURCE="FP-1">○ +1 408 638 0968 US (San Jose)</FP>
                <FP SOURCE="FP-1">○ +1 253 215 8782 US (Tacoma)</FP>
                <FP SOURCE="FP-1">○ +1 346 248 7799 US (Houston)</FP>
                <FP SOURCE="FP-1">
                    ○ 
                    <E T="03">Meeting ID:</E>
                     896 6326 9110
                </FP>
                <FP SOURCE="FP-1">
                    ○ 
                    <E T="03">Passcode:</E>
                     102122
                </FP>
                <FP SOURCE="FP-1">
                    ○ If calling from outside the U.S., find your local number here: 
                    <E T="03">https://lsc-gov.zoom.us/u/acCVpRj1FD</E>
                </FP>
                <P>Once connected to Zoom, please immediately mute your computer or telephone. Members of the public are asked to keep their computers or telephones muted to eliminate background noise. To avoid disrupting the meetings, please refrain from placing the call on hold if doing so will trigger recorded music or other sound.</P>
                <P>
                    From time to time, the Board or Committee Chair may solicit comments 
                    <PRTPAGE P="62459"/>
                    from the public. To participate in the meeting during public comment, use the `raise your hand' or `chat' functions in Zoom and wait to be recognized by the Chair before stating your questions and/or comments.
                </P>
                <PREAMHD>
                    <HD SOURCE="HED">STATUS: </HD>
                    <P>Open, except as noted below.</P>
                    <P>
                        <E T="03">Audit Committee</E>
                        —Open, except that, upon a vote of the Board of Directors, the meeting may be closed to the public to meeting to discuss follow-up work by the Office of Compliance and Enforcement relating to open Office of Inspector General investigations.
                    </P>
                    <P>
                        <E T="03">Institutional Advancement Committee</E>
                        —Open, except that, upon a vote of the Board of Directors, the meeting may be closed to the public for a briefing on development activities, an update on LSC's 50th anniversary fundraising activities, and to discuss prospective members of the Leaders Council and Emerging Leaders Council.
                    </P>
                    <P>
                        <E T="03">Board of Directors</E>
                        —Open, except that, upon a vote of the Board of Directors, a portion of the meeting may be closed to the public for briefings by management and LSC's Inspector General and for the Board to consider and act on the General Counsel's report on potential and pending litigation involving LSC as well as a list of prospective Leaders Council and Emerging Leaders Council members.
                    </P>
                    <P>
                        Any portion of the closed session consisting solely of briefings does not fall within the Sunshine Act's definition of the term “meeting” and, therefore, the requirements of the Sunshine Act do not apply to such portion of the closed session.
                        <SU>1</SU>
                        <FTREF/>
                    </P>
                </PREAMHD>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         5 U.S.C. 552b (a) (2) and (b). See also 45 CFR 1622.2 &amp; 1622.3.
                    </P>
                </FTNT>
                <P>A verbatim written transcript will be made of the closed session of the Audit, Board, and Institutional Advancement Committee meetings. The transcript of any portions of the closed sessions falling within the relevant provisions of the Government in the Sunshine Act, 5 U.S.C. 552b(c)(6), (7), (9) and (10), will not be available for public inspection. A copy of the General Counsel's Certification that, in his opinion, the closing is authorized by law will be available upon request.</P>
                <PREAMHD>
                    <HD SOURCE="HED">MATTERS TO BE CONSIDERED:</HD>
                    <P> </P>
                </PREAMHD>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s150,xs60">
                    <TTITLE>Meeting Schedule</TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">
                            Start time
                            <LI>(all CDT)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">
                            <E T="03">Thursday, October 20, 2022:</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">1. Meeting of the Communications Subcommittee of the Institutional Committee</ENT>
                        <ENT>9 a.m. CDT.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">2. Finance Committee Meeting</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">3. Audit Committee Meeting</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">4. Delivery of Legal Services Committee Meeting</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">
                            <E T="03">Friday, October 21, 2022:</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">1. Institutional Advancement Committee</ENT>
                        <ENT>8 a.m. CDT.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">2. Open Board Meeting</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">3. Closed Board Meeting</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Thursday, October 20, 2022</HD>
                <HD SOURCE="HD2">Meeting of Communications Subcommittee of the Institutional Advancement Committee</HD>
                <HD SOURCE="HD3">Open Session</HD>
                <FP SOURCE="FP-2">1. Approval of Agenda</FP>
                <FP SOURCE="FP-2">2. Approval of Minutes of the Subcommittee's Open Session Meeting on July 14, 2022</FP>
                <FP SOURCE="FP-2">3. Communications and Social Media Update</FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Carl Rauscher, Director of Communications and Media Relations, Legal Services Corporation</E>
                </FP>
                <FP SOURCE="FP-2">4. Public Comment</FP>
                <FP SOURCE="FP-2">5. Consider and Act on Other Business</FP>
                <FP SOURCE="FP-2">6. Consider and Act on Motion to Adjourn the Meeting</FP>
                <HD SOURCE="HD2">Finance Committee Meeting</HD>
                <HD SOURCE="HD3">Open Session</HD>
                <FP SOURCE="FP-2">1. Approval of Meeting Agenda</FP>
                <FP SOURCE="FP-2">2. Approval of Minutes of the Committee's Open Session Meetings on June 13, June 30, July 5, and July 14, 2022</FP>
                <FP SOURCE="FP-2">3. Approval of Minutes of the Committee's Closed Session Meeting on July 14, 2022</FP>
                <FP SOURCE="FP-2">4. Presentation of LSC's Financial Report for Fiscal Year 2022, Ending September 30, 2022</FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Debbie Moore, Chief Financial Officer and Treasurer</E>
                </FP>
                <FP SOURCE="FP-2">5. Report on Fiscal Year 2023 Appropriation and Supplemental Requests</FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Carol Bergman, Vice President for Government Relations and Public Affairs</E>
                </FP>
                <FP SOURCE="FP-2">6. Report on Fiscal Year 2023 Management and Grants Oversight Budget</FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Ron Flagg, President</E>
                </FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Debbie Moore, Chief Financial Officer and Treasurer</E>
                </FP>
                <FP SOURCE="FP-2">7. Report on Fiscal Year 2024 Budget Request</FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Carol Bergman, Vice President for Government Relations and Public Affairs</E>
                </FP>
                <FP SOURCE="FP-2">8. Briefing on Capitol Hill Visits During the Executive Directors Conference</FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Carol Bergman, Vice President for Government Relations and Public Affairs</E>
                </FP>
                <FP SOURCE="FP-2">9. Public Comment</FP>
                <FP SOURCE="FP-2">10. Consider and Act on Other Business</FP>
                <FP SOURCE="FP-2">11. Consider and Act on Motion to Adjourn the Meeting</FP>
                <HD SOURCE="HD2">Audit Committee Meeting</HD>
                <HD SOURCE="HD3">Open Session</HD>
                <FP SOURCE="FP-2">1. Approval of Agenda</FP>
                <FP SOURCE="FP-2">2. Approval of Minutes of the Committee's Open Session Meeting on July 13, 2022</FP>
                <FP SOURCE="FP-2">3. Briefing by the Office of Inspector General</FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Roxanne Caruso, Acting Inspector General &amp; Assistant Inspector General for Audit</E>
                </FP>
                <FP SOURCE="FP-2">4. Review LSC's Efforts, Including Training and Education, to Help Ensure that LSC Employees and Grantees Act Ethically and Safeguard LSC Funds</FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Will Gunn, Vice President for Legal Affairs</E>
                </FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Lynn Jennings, Vice President for Grants Management</E>
                </FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Debbie Moore, Treasurer &amp; Chief Financial Officer</E>
                </FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Stefanie Davis, Senior Associate General Counsel for Regulations and Ethics Officer</E>
                </FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Roxanne Caruso, Acting Inspector General &amp; Assistant Inspector General for Audit</E>
                </FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Daniel O'Rourke, Assistant Inspector General for Investigations</E>
                    <PRTPAGE P="62460"/>
                </FP>
                <FP SOURCE="FP-2">5. Management Update Regarding Risk Management</FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Will Gunn, Vice President for Legal Affairs</E>
                </FP>
                <FP SOURCE="FP-2">6. Briefing About Follow-Up by the Office of Compliance and Enforcement on Referrals by the Office of Inspector General Regarding Audit Reports and Annual Financial Statement Audits of Grantees</FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Lora Rath, Director, Office of Compliance and Enforcement</E>
                </FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Roxanne Caruso, Acting Inspector General &amp; Assistant Inspector General for Audit</E>
                </FP>
                <FP SOURCE="FP-2">7. Public Comment</FP>
                <FP SOURCE="FP-2">8. Consider and Act on Other Business</FP>
                <FP SOURCE="FP-2">9. Consider and Act on Motion to Adjourn the Open Session Meeting and Proceed to a Closed Session</FP>
                <HD SOURCE="HD3">Closed Session</HD>
                <FP SOURCE="FP-2">1. Approval of Minutes of the Committee's Closed Session Meeting on July 13, 2022</FP>
                <FP SOURCE="FP-2">2. Briefing by Office Compliance and Enforcement on Active Enforcement Matter(s) and Follow-Up on Open Investigation Referrals from the Office of Inspector General</FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Lora Rath, Director, Office of Compliance and Enforcement</E>
                </FP>
                <FP SOURCE="FP-2">3. Consider and Act on Motion to Adjourn the Meeting</FP>
                <HD SOURCE="HD2">Delivery of Legal Services Committee Meeting</HD>
                <HD SOURCE="HD3">Open Session</HD>
                <FP SOURCE="FP-2">1. Approval of Agenda</FP>
                <FP SOURCE="FP-2">2. Approval of Minutes of the Committee's Open Session Meeting on July 13, 2022</FP>
                <FP SOURCE="FP-2">3. LSC Performance Criteria Revisions Update</FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Lynn Jennings, Vice President for Grants Management</E>
                </FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Joyce McGee, Director, Office of Program Performance</E>
                </FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Evora Thomas, Consultant</E>
                </FP>
                <FP SOURCE="FP-2">4. Panel Discussion: Disaster Legal Aid</FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Leslie Powell-Beaudreaux, Executive Director, Legal Services of North Florida</E>
                </FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Maria Thomas Jones, Executive Director, Legal Aid of Northwest Texas</E>
                </FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Laura Tuggle, Executive Director, Southeast Louisiana Legal Services</E>
                </FP>
                <FP SOURCE="FP1-2">
                    <E T="03">Moderator: Joyce McGee, Director, Office of Program Performance</E>
                </FP>
                <FP SOURCE="FP-2">5. Public Comment</FP>
                <FP SOURCE="FP-2">6. Consider and Act on Other Business</FP>
                <FP SOURCE="FP-2">7. Consider and Act on a Motion to Adjourn the Meeting</FP>
                <HD SOURCE="HD1">Friday, October 21, 2022</HD>
                <HD SOURCE="HD2">Institutional Advancement Committee Meeting</HD>
                <HD SOURCE="HD3">Open Session</HD>
                <FP SOURCE="FP-2">1. Approval of Agenda</FP>
                <FP SOURCE="FP-2">2. Approval of Minutes of the Institutional Advancement Committee's Open Session Meeting on July 13, 2022</FP>
                <FP SOURCE="FP-2">3. Update on Leaders Council and Emerging Leaders Council</FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">John G. Levi, Chairman of the Board</E>
                </FP>
                <FP SOURCE="FP-2">4. Development Report</FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Nadia Elguindy, Director of Institutional Advancement</E>
                </FP>
                <FP SOURCE="FP-2">5. Update on Privately Funded Initiatives</FP>
                <FP SOURCE="FP1-2">• Veterans Task Force Implementation</FP>
                <FP SOURCE="FP1-2">
                    ○ 
                    <E T="03">Stefanie Davis, Senior Assistant General Counsel and Ethics Officer</E>
                </FP>
                <FP SOURCE="FP1-2">• Executive Director Conference and Midwest Capstone Disaster Conference</FP>
                <FP SOURCE="FP1-2">
                    ○ 
                    <E T="03">Lynn Jennings, Vice President for Grants Management</E>
                </FP>
                <FP SOURCE="FP1-2">• Rural Justice Task Force</FP>
                <FP SOURCE="FP1-2">
                    ○ 
                    <E T="03">Jessica Wechter, Special Assistant to the President</E>
                </FP>
                <FP SOURCE="FP-2">6. Public Comment</FP>
                <FP SOURCE="FP-2">7. Consider and Act on Other Business</FP>
                <FP SOURCE="FP-2">8. Consider and Act on Motion to Adjourn the Open Session Meeting and Proceed to a Closed Session</FP>
                <HD SOURCE="HD3">Closed Session</HD>
                <FP SOURCE="FP-2">1. Approval of Minutes of the Institutional Advancement Committee's Closed Session Meeting on July 13, 2022</FP>
                <FP SOURCE="FP-2">2. Development Activities Report</FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Nadia Elguindy, Director of Institutional Advancement</E>
                </FP>
                <FP SOURCE="FP-2">3. Update on LSC's 50th Anniversary Fundraising Campaign</FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Nadia Elguindy, Director of Institutional Advancement</E>
                </FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">Leo Latz, Latz &amp; Company</E>
                </FP>
                <FP SOURCE="FP-2">4. Consider and Act on Motion to Approve Leaders Council and Emerging Leaders Council Invitees</FP>
                <FP SOURCE="FP-2">5. Consider and Act on Other Business</FP>
                <FP SOURCE="FP-2">6. Consider and Act on Motion to Adjourn the Meeting</FP>
                <HD SOURCE="HD2">Board of Directors</HD>
                <HD SOURCE="HD3">Open Session</HD>
                <FP SOURCE="FP-2">1. Pledge of Allegiance</FP>
                <FP SOURCE="FP-2">2. Approval of Agenda</FP>
                <FP SOURCE="FP-2">3. Approval of Minutes of the Board's Open Session Meeting on July 14, 2022</FP>
                <FP SOURCE="FP-2">4. Chairman's Report</FP>
                <FP SOURCE="FP-2">5. Members' Reports</FP>
                <FP SOURCE="FP-2">6. President's Report</FP>
                <FP SOURCE="FP-2">7. Inspector General's Report</FP>
                <FP SOURCE="FP-2">8. Consider and Act on the Report of the Governance and Performance Review Committee, following its September 23, 2022, Videoconference Meeting</FP>
                <FP SOURCE="FP-2">9. Consider and Act on the Report of the Operations and Regulations Committee, following its October 4, 2022, Videoconference Meeting</FP>
                <FP SOURCE="FP-2">10. Consider and Act on the Report of the Finance Committee</FP>
                <FP SOURCE="FP-2">11. Consider and Act on the Report of the Audit Committee</FP>
                <FP SOURCE="FP-2">12. Consider and Act on the Report of the Delivery of Legal Services Committee</FP>
                <FP SOURCE="FP-2">13. Consider and Act on the Report of the Institutional Advancement Committee</FP>
                <FP SOURCE="FP-2">14. Public Comment</FP>
                <FP SOURCE="FP-2">15. Consider and Act on Other Business</FP>
                <FP SOURCE="FP-2">16. Consider and Act on Motion to Adjourn the Open Session Meeting and Proceed to a Closed Session</FP>
                <HD SOURCE="HD3">Closed Session</HD>
                <FP SOURCE="FP-2">1. Approval of Minutes of the Board's Closed Session Meeting on July 14, 2022</FP>
                <FP SOURCE="FP-2">2. Management Briefing</FP>
                <FP SOURCE="FP-2">3. Inspector General Briefing</FP>
                <FP SOURCE="FP-2">4. Consider and Act on General Counsel's Report on Potential and Pending Litigation Involving Legal Services Corporation</FP>
                <FP SOURCE="FP-2">5. Consider and Act on List of Prospective Leaders Council and Emerging Council Invitees</FP>
                <FP SOURCE="FP-2">6. Consider and Act on Motion to Adjourn the Meeting</FP>
                <PREAMHD>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION: </HD>
                    <P>
                        Kaitlin Brown, Executive and Board Project Coordinator, at (202) 295-1555. Questions may also be sent by electronic mail to 
                        <E T="03">brownk@lsc.gov.</E>
                    </P>
                    <P>
                        <E T="03">Non-Confidential Meeting Materials:</E>
                         Non-confidential meeting materials will be made available in electronic format at least 24 hours in advance of the meeting on the LSC website, at 
                        <E T="03">https://www.lsc.gov/about-lsc/board-meeting-materials.</E>
                    </P>
                </PREAMHD>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>Kaitlin D. Brown,</NAME>
                    <TITLE>Executive and Board Project Coordinator, Legal Services Corporation.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22452 Filed 10-12-22; 11:15 am]</FRDOC>
            <BILCOD>BILLING CODE 7050-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL ARCHIVES AND RECORDS ADMINISTRATION</AGENCY>
                <DEPDOC>[NARA-2023-001]</DEPDOC>
                <SUBJECT>National Industrial Security Program Policy Advisory Committee (NISPPAC); Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Information Security Oversight Office (ISOO), National Archives and Records Administration (NARA).</P>
                </AGY>
                <ACT>
                    <PRTPAGE P="62461"/>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Federal Advisory Committee meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We are announcing an upcoming National Industrial Security Program Policy Advisory Committee (NISPPAC) meeting in accordance with the Federal Advisory Committee Act and implementing regulations.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be on November 2, 2022, from 10 a.m-1 p.m EST.</P>
                    <P>
                        <E T="03">Location:</E>
                         This meeting will be a virtual meeting. See supplementary procedures below.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Heather Harris Pagán, ISOO Program Analyst, by telephone at 202.357.5351 or by email at 
                        <E T="03">ISOO@nara.gov.</E>
                         Contact ISOO at 
                        <E T="03">ISOO@nara.gov</E>
                         and the NISPPAC at 
                        <E T="03">NISPPAC@nara.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This virtual meeting is open to the public in accordance with the Federal Advisory Committee Act (5 U.S.C. app 2) and implementing regulations at 41 CFR 102-3. The Committee will discuss National Industrial Security Program policy matters.</P>
                <P>
                    <E T="03">Procedures:</E>
                     Members of the public must register in advance through the Event Services link 
                    <E T="03">https://ems8.intellor.com?do=register&amp;t=1&amp;p=844912</E>
                     if you wish to attend. NISPPAC members, ISOO employees, and speakers should send an email to 
                    <E T="03">NISPPAC@nara.gov</E>
                     for the appropriate registration information instead of registering with the above link.
                </P>
                <SIG>
                    <NAME>Tasha Ford,</NAME>
                    <TITLE>Committee Management Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22392 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7515-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NUCLEAR REGULATORY COMMISSION </AGENCY>
                <SUBJECT>700th Meeting of the Advisory Committee on Reactor Safeguards (ACRS)</SUBJECT>
                <P>
                    In accordance with the purposes of sections 29 and 182b of the Atomic Energy Act (42 U.S.C. 2039, 2232(b)), the Advisory Committee on Reactor Safeguards (ACRS) will hold meetings on November 1-4, 2022. The Committee will be conducting meetings that will include some Members being physically present at the NRC while other Members participate remotely. Interested members of the public are encouraged to participate remotely in any open sessions via MS Teams or via phone at 301-576-2978, passcode 365074284#. A more detailed agenda including the MSTeams link may be found at the ACRS public website at 
                    <E T="03">https://www.nrc.gov/reading-rm/doc-collections/acrs/agenda/index.html.</E>
                     If you would like the MSTeams link forwarded to you, please contact the Designated Federal Officer as follows: 
                    <E T="03">Quynh.Nguyen@nrc.gov,Derek.Widmayer@nrc.gov</E>
                     or 
                    <E T="03">Lawrence.Burkhart@nrc.gov.</E>
                </P>
                <HD SOURCE="HD1">Tuesday, November 1, 2022</HD>
                <P>
                    <E T="03">1 p.m.-1:05 p.m.: Opening Remarks by the ACRS Chairman</E>
                     (Open)—The ACRS Chairman will make opening remarks regarding the conduct of the meeting.
                </P>
                <P>
                    <E T="03">1:05 p.m.-2:45 p.m.: SECY on Potential Expansion of Current NRC policy on Common Cause Failures</E>
                     (Open)—The Committee will have presentations and discussion with representatives from the NRC staff regarding the subject topic.
                </P>
                <P>
                    <E T="03">2:45 p.m.-3:45 p.m.: Committee Deliberation on SECY on Potential Expansion of Current NRC policy on Common Cause Failures</E>
                     (Open)—The Committee will deliberate regarding the subject topic.
                </P>
                <P>
                    <E T="03">3:45 p.m.-5:15 p.m.: Regulatory Guide (RG) 1.82, Revision 5, “Water Sources for Long-term Recirculation Cooling following a Loss-of-Coolant Accident”</E>
                     (Open)—The Committee will have presentations and discussion with representatives from the NRC staff regarding the subject topic.
                </P>
                <P>
                    <E T="03">5:15 p.m.-6 p.m.: Committee Deliberation on RG 1.82, Revision 5, “Water Sources for Long-term Recirculation Cooling following a Loss-of-Coolant Accident”</E>
                     (Open)—The Committee will deliberate regarding the subject topic.
                </P>
                <HD SOURCE="HD1">Wednesday, November 2, 2022</HD>
                <P>
                    <E T="03">8:30 a.m.-10:30 a.m.: 10 CFR part 53, “Risk-Informed, Technology-Inclusive Regulatory Framework for Commercial Nuclear Plants,” Proposed Rulemaking Language</E>
                     (Open)—The Committee will have presentations and discussion with representatives from the NRC staff regarding the subject topic.
                </P>
                <P>
                    <E T="03">10:30 a.m.-11:30 a.m.: Committee Deliberation on 10 CFR part 53, “Risk-Informed, Technology-Inclusive Regulatory Framework for Commercial Nuclear Plants,” Proposed Rulemaking Language</E>
                     (Open)—The Committee will deliberate regarding the subject topic.
                </P>
                <P>
                    <E T="03">1 p.m.-6 p.m.: Preparation of Reports</E>
                     (Open)—The Committee will continue its discussion of proposed ACRS reports.
                </P>
                <HD SOURCE="HD1">Thursday, November 3, 2022</HD>
                <P>
                    <E T="03">8:30 a.m.-6:00 p.m.: Preparation of Reports</E>
                     (Open)—The Committee will continue its discussion of proposed ACRS reports.
                </P>
                <HD SOURCE="HD1">Friday, November 4, 2022</HD>
                <P>
                    <E T="03">8:30 a.m.-11:30 a.m.: Future ACRS Activities/Report of the Planning and Procedures Subcommittee and Reconciliation of ACRS Comments and Recommendations/Preparation of Reports/SHINE Memoranda Review and Deliberation</E>
                     (Open/Closed)—The Committee will hear discussion of the recommendations of the Planning and Procedures Subcommittee regarding items proposed for consideration by the Full Committee during future ACRS meetings, and/or proceed to preparation of reports as determined by the Chairman. [NOTE: Pursuant to 5 U.S.C. 552b(c)(4), a portion of this session may be closed in order to discuss and protect information designated as proprietary.]. [NOTE: Pursuant to 5 U.S.C. 552b(c)(2), a portion of this meeting may be closed to discuss organizational and personnel matters that relate solely to internal personnel rules and practices of the ACRS.]
                </P>
                <P>
                    <E T="03">1:30 p.m.-6 p.m.: Preparation of Reports</E>
                     (Open)—The Committee will continue its discussion of proposed ACRS reports.
                </P>
                <P>
                    Procedures for the conduct of and participation in ACRS meetings were published in the 
                    <E T="04">Federal Register</E>
                     on June 13, 2019 (84 FR 27662). In accordance with those procedures, oral or written views may be presented by members of the public, including representatives of the nuclear industry. Persons desiring to make oral statements should notify Quynh Nguyen or Derek Widmayer, Cognizant ACRS Staff and the Designated Federal Officer (Telephone: 301-415-5844, Email: 
                    <E T="03">Derek.Widmayer@nrc.gov</E>
                     or 
                    <E T="03">Quynh.Nguyen@nrc.gov</E>
                    ), 5 days before the meeting, if possible, so that appropriate arrangements can be made to allow necessary time during the meeting for such statements. In view of the possibility that the schedule for ACRS meetings may be adjusted by the Chairman as necessary to facilitate the conduct of the meeting, persons planning to attend should check with the cognizant ACRS staff if such rescheduling would result in major inconvenience.
                </P>
                <P>An electronic copy of each presentation should be emailed to the cognizant ACRS staff at least one day before the meeting.</P>
                <P>
                    In accordance with subsection 10(d) of Public Law 92-463 and 5 U.S.C. 552b(c), certain portions of this meeting may be closed, as specifically noted above. Use of still, motion picture, and television cameras during the meeting 
                    <PRTPAGE P="62462"/>
                    may be limited to selected portions of the meeting as determined by the Chairman. Electronic recordings will be permitted only during the open portions of the meeting.
                </P>
                <P>
                    ACRS meeting agendas, meeting transcripts, and letter reports are available through the NRC Public Document Room (PDR) at 
                    <E T="03">pdr.resource@nrc.gov,</E>
                     or by calling the PDR at 1-800-397-4209, or from the Publicly Available Records System component of NRC's Agencywide Documents Access and Management System, which is accessible from the NRC website at 
                    <E T="03">https://www.nrc.gov/reading-rm/adams.html</E>
                     or 
                    <E T="03">https://www.nrc.gov/reading-rm/doc-collections/#ACRS/.</E>
                </P>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>Russell E. Chazell,</NAME>
                    <TITLE>Federal Advisory Committee Management Officer, Office of the Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22352 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[NRC-2021-0231]</DEPDOC>
                <SUBJECT>Guide for Assessing, Monitoring, and Mitigating Aging Effects on Electrical Equipment Used in Production and Utilization Facilities</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Nuclear Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Regulatory guide; issuance.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Nuclear Regulatory Commission (NRC) is issuing a new Regulatory Guide (RG) 1.248, “Guide for Assessing, Monitoring, and Mitigating Aging Effects on Electrical Equipment Used in Production and Utilization Facilities.” This RG describes an approach that is acceptable to the staff of the NRC to meet regulatory requirements for managing, monitoring, and mitigating the aging effects on electrical equipment. It endorses Institute of Electrical and Electronics Engineers (IEEE) Standard (Std.) 1205 2014, “IEEE Guide for Assessing, Monitoring, and Mitigating Aging Effects on Electrical Equipment Used in Nuclear Power Generating Stations and Other Nuclear Facilities.”</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Revision 0 to RG 1.248 is available on October 14, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Please refer to Docket ID NRC-2021-0231 when contacting the NRC about the availability of information regarding this document. You may obtain publicly available information related to this document using any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal Rulemaking Website:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov</E>
                         and search for Docket ID NRC-2021-0231. Address questions about Docket IDs in 
                        <E T="03">Regulations.gov</E>
                         to Stacy Schumann; telephone: 301-415-0624; email: 
                        <E T="03">Stacy.Schumann@nrc.gov.</E>
                         For technical questions, contact the individuals listed in the 
                        <E T="02">For Further Information Contact</E>
                         section of this document.
                    </P>
                    <P>
                        • 
                        <E T="03">NRC's Agencywide Documents Access and Management System (ADAMS):</E>
                         You may obtain publicly available documents online in the ADAMS Public Documents collection at 
                        <E T="03">https://www.nrc.gov/reading-rm/adams.html.</E>
                         To begin the search, select “Begin Web-based ADAMS Search.” For problems with ADAMS, please contact the NRC's Public Document Room (PDR) reference staff at 1-800-397-4209, 301-415-4737, or by email to 
                        <E T="03">PDR.Resource@nrc.gov.</E>
                         The ADAMS accession number for each document referenced (if it is available in ADAMS) is provided the first time that it is mentioned in this document.
                    </P>
                    <P>
                        • 
                        <E T="03">NRC's PDR:</E>
                         You may examine and purchase copies of public documents, by appointment, at the NRC's Public Document Room (PDR), Room P1 B35, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852. To make an appointment to visit the PDR, please send an email to 
                        <E T="03">PDR.Resource@nrc.gov</E>
                         or call 1-800-397-4209 or 301-415-4737, between 8:00 a.m. and 4:00 p.m. Eastern Time (ET), Monday through Friday, except Federal holidays.
                    </P>
                    <P>RG 1.248 and the regulatory analysis may be found in ADAMS under Accession Nos. ML22221A220 and ML21288A112, respectively.</P>
                    <P>Regulatory guides are not copyrighted, and NRC approval is not required to reproduce them.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Michael Eudy, telephone: 301-415-3104, email: 
                        <E T="03">Michael.Eudy@nrc.gov</E>
                         and Mohammad Sadollah, telephone: 301-415-6804, email: 
                        <E T="03">Mohammad.Sadollah@nrc.gov.</E>
                         Both are staff of the Office of Nuclear Regulatory Research at the U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Discussion</HD>
                <P>The NRC is issuing a new guide in the NRC's “Regulatory Guide” series. This series was developed to describe methods that are acceptable to the NRC staff for implementing specific parts of the agency's regulations, to explain techniques that the staff uses in evaluating specific issues or postulated events, and to describe information that the staff needs in its review of applications for permits and licenses. RG 1.248 was issued with a temporary identification of Draft Regulatory Guide, DG-1393.</P>
                <HD SOURCE="HD1">II. Additional Information</HD>
                <P>
                    The NRC published a notice of the availability of DG-1393 in the 
                    <E T="04">Federal Register</E>
                     on February 3, 2022 (87 FR 6204) for a 30-day public comment period. The public comment period closed on March 7, 2022. Public comments on DG-1393 and the staff responses to the public comments are available under ADAMS under Accession No. ML22221A222.
                </P>
                <HD SOURCE="HD1">III. Congressional Review Act</HD>
                <P>This RG is a rule as defined in the Congressional Review Act (5 U.S.C. 801-808). However, the Office of Management and Budget has not found it to be a major rule as defined in the Congressional Review Act.</P>
                <HD SOURCE="HD1">IV. Backfitting, Forward Fitting, and Issue Finality</HD>
                <P>
                    The NRC staff may use this RG as a reference in its regulatory processes, such as licensing, inspection, or enforcement, as appropriate. However, the NRC staff does not intend to use the guidance in this RG to support NRC staff actions in a manner that would constitute backfitting as that term is defined in section 50.109 of title 10 of the 
                    <E T="03">Code of Federal Regulations</E>
                     (10 CFR), “Backfitting,” and as described in NRC Management Directive 8.4, “Management of Backfitting, Forward Fitting, Issue Finality, and Information Requests,” nor does the NRC staff intend to use the guidance to affect the issue finality of an approval under 10 CFR part 52, “Licenses, Certifications, and Approvals for Nuclear Power Plants. The staff also does not intend to use the guidance to support NRC staff actions in a manner that constitutes forward fitting as that term is defined and described in MD 8.4. If a licensee believes that the NRC is using this RG in a manner inconsistent with the discussion in this Implementation section, then the licensee may file a backfitting or forward fitting appeal with the NRC in accordance with the process in MD 8.4.
                </P>
                <HD SOURCE="HD1">V. Submitting Suggestions for Improvement of Regulatory Guides</HD>
                <P>
                    A member of the public may, at any time, submit suggestions to the NRC for improvement of existing RGs or for the development of new RGs. Suggestions can be submitted on the NRC's public website at 
                    <E T="03">
                        https://www.nrc.gov/reading-rm/doc-collections/reg-guides/
                        <PRTPAGE P="62463"/>
                        contactus.html.
                    </E>
                     Suggestions will be considered in future updates and enhancements to the “Regulatory Guide” series.
                </P>
                <SIG>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <P>For the Nuclear Regulatory Commission.</P>
                    <NAME>Meraj Rahimi,</NAME>
                    <TITLE>Chief, Regulatory Guide and Programs Management Branch, Division of Engineering, Office of Nuclear Regulatory Research.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22300 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[Docket No. 99902088; NRC-2022-0167]</DEPDOC>
                <SUBJECT>Abilene Christian University</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Nuclear Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Construction permit application; receipt.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Nuclear Regulatory Commission (NRC) is providing public notice of receipt and availability of an application for a construction permit from Abilene Christian University (ACU). The construction permit application is dated August 12, 2022.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>October 14, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Please refer to Docket ID NRC-2022-0167 when contacting the NRC about the availability of information regarding this document. You may obtain publicly available information related to this document using any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal Rulemaking Website:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov</E>
                         and search for Docket ID NRC-2022-0167. Address questions about Docket IDs in 
                        <E T="03">Regulations.gov</E>
                         to Stacy Schumann; telephone: 301-415-0624; email: 
                        <E T="03">Stacy.Schumann@nrc.gov.</E>
                         For technical questions, contact the individual listed in the 
                        <E T="02">For Further Information Contact</E>
                         section of this document.
                    </P>
                    <P>
                        • 
                        <E T="03">NRC's Agencywide Documents Access and Management System (ADAMS):</E>
                         You may obtain publicly available documents online in the ADAMS Public Documents collection at 
                        <E T="03">https://www.nrc.gov/reading-rm/adams.html.</E>
                         To begin the search, select “Begin Web-based ADAMS Search.” For problems with ADAMS, please contact the NRC's Public Document Room (PDR) reference staff at 1-800-397-4209, 301-415-4737, or by email to 
                        <E T="03">PDR.Resource@nrc.gov.</E>
                         The ADAMS accession number for each document referenced (if it is available in ADAMS) is provided the first time that it is mentioned in this document.
                    </P>
                    <P>
                        • 
                        <E T="03">NRC's PDR:</E>
                         You may examine and purchase copies of public documents, by appointment, at the NRC's PDR, Room P1 B35, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852. To make an appointment to visit the PDR, please send an email to 
                        <E T="03">PDR.Resource@nrc.gov</E>
                         or call 1-800-397-4209 or 301-415-4737, between 8 a.m. and 4 p.m. eastern tme (ET), Monday through Friday, except Federal holidays.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Richard F. Rivera, Office of Nuclear Reactor Regulation, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001; telephone: 301-415-7190; email: 
                        <E T="03">Richard.Rivera@nrc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Discussion</HD>
                <P>
                    ACU filed with the NRC pursuant to Section 104c of the Atomic Energy Act and part 50 of title 10 of the 
                    <E T="03">Code of Federal Regulations</E>
                     (10 CFR), “Domestic Licensing of Production and Utilization Facilities,” an application dated August 12, 2022, for a construction permit for one research reactor proposed to be located in Abilene, Texas. The reactor is to be identified as the Molten Salt Research Reactor.
                </P>
                <P>The application is available in ADAMS Package Accession No. ML22227A201, which includes the transmittal letter and the preliminary safety analysis report. The information submitted by the applicant includes certain administrative information, such as financial qualifications submitted pursuant to 10 CFR 50.33, “Contents of applications; general information,” as well as technical information submitted pursuant to 10 CFR 50.34, “Contents of applications; technical information.” The environmental report was also submitted as part of the preliminary safety analysis report.</P>
                <P>
                    The NRC staff is currently undertaking its acceptance review of the application. If the application is accepted for docketing, subsequent 
                    <E T="04">Federal Register</E>
                     notices will be issued that address the acceptability of the tendered construction permit application for docketing and provisions for participation of the public in the permitting process.
                </P>
                <SIG>
                    <DATED>Dated: October 7, 2022.</DATED>
                    <P>For the Nuclear Regulatory Commission.</P>
                    <NAME>Richard F. Rivera,</NAME>
                    <TITLE>Project Manager, Advanced Reactor Licensing Branch, Division of Advanced Reactors and Non-Power Production and Utilization Facilities, Office of Nuclear Reactor Regulation.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22294 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">PEACE CORPS</AGENCY>
                <SUBJECT>Information Collection Request; Submission for OMB Review</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Peace Corps.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>60-Day notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Peace Corps will be submitting the following information collection request to the Office of Management and Budget (OMB) for review and approval. In accordance with the Paperwork Reduction Act of 1995 and implementing OMB guidance, we are requesting comments on this collection from all interested individuals and organizations. The purpose of this notice is to allow 60 days for public comment in the 
                        <E T="04">Federal Register</E>
                         preceding submission to OMB.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments on or before December 13, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Address written comments and recommendations for the proposed information collection to Virginia Burke, FOIA/Privacy Act Officer, by email at 
                        <E T="03">pcfr@peacecorps.gov.</E>
                         Email comments must be made in text and not in attachments.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Virginia Burke, FOIA/Privacy Act Officer, at (202) 692-1887, or 
                        <E T="03">PCFR@peacecorps.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <P>
                    <E T="03">Title:</E>
                     Peace Corps Awareness and Affinity: National Survey of U.S. Adults.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0420-****.
                </P>
                <P>
                    <E T="03">Form number:</E>
                     PC-2210.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     New collection.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals.
                </P>
                <P>
                    <E T="03">Respondents Obligation to Reply:</E>
                     Voluntary.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Members of the public and prospective Peace Corps Volumteer applicants.
                </P>
                <P>
                    <E T="03">Burden to the Public:</E>
                </P>
                <P>
                    (a) 
                    <E T="03">Estimated number of respondents:</E>
                     6,200.
                </P>
                <P>
                    (b) 
                    <E T="03">Frequency of response:</E>
                     Twice.
                </P>
                <P>
                    (c) 
                    <E T="03">Estimated average burden per response:</E>
                     .188 hours.
                </P>
                <P>
                    (d) 
                    <E T="03">Estimated total reporting burden:</E>
                     2333.32 hours.
                </P>
                <P>
                    (e) 
                    <E T="03">Estimated annual cost to respondents:</E>
                     0.00.
                    <PRTPAGE P="62464"/>
                </P>
                <P>
                    <E T="03">General Description of Collection:</E>
                     The Peace Corps experienced unprecedented challenges during the COVID-19 pandemic, including recalling its entire Volunteer workforce in March 2020. The Peace Corps will launch a new national awareness and recruitment campaign as it returns to full service to promote the organization, its mission, goals, and values, and to attract and recruit qualified and diverse Volunteer applicants. The Peace Corps' Office of Communications will use the information collected by the Peace Corps Awareness and Affinity: National Survey of U.S. Adults to help assess the effectiveness of the new campaign. The survey will also collect information to help broaden the pool of potential Volunteers and engage more diverse audiences. This information collection will also be used to gather information and insights to identify key audience segments and help ensure the efficiency and success of future marketing efforts by:
                </P>
                <P>• Identifying levels of awareness, knowledge, attitudes and opinions about the Peace Corps among the general U.S. public and targeted audience segments;</P>
                <P>• Collecting insights to inform communications, education, and outreach strategies by understanding which themes resonate most with different audience segments; and,</P>
                <P>• Determining the best channels for communication</P>
                <P>The Office of Communications will conduct this survey twice: once to serve as a baseline prior to the launch of its national awareness and recruitment campaign, and once after the campaign has launched to assess campaign impact.</P>
                <P>
                    <E T="03">Request for Comment:</E>
                     Peace Corps invites comments on whether the proposed collections of information are necessary for proper performance of the functions of the Peace Corps, including whether the information will have practical use; the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the information to be collected; and, ways to minimize the burden of the collection of information on those who are to respond, including through the use of automated collection techniques, when appropriate, and other forms of information technology.
                </P>
                <SIG>
                    <DATED>This notice is issued in Washington, DC, on October 11, 2022.</DATED>
                    <NAME>Virginia Burke,</NAME>
                    <TITLE>FOIA/Privacy Act Officer, Management.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22372 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6051-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">POSTAL SERVICE</AGENCY>
                <SUBJECT>Product Change—Priority Mail Express, Priority Mail, First-Class Package Service, and Parcel Select Service Negotiated Service Agreement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>
                        Postal Service
                        <E T="51">TM</E>
                        .
                    </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Postal Service gives notice of filing a request with the Postal Regulatory Commission to add a domestic shipping services contract to the list of Negotiated Service Agreements in the Mail Classification Schedule's Competitive Products List.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Date of required notice:</E>
                         October 14, 2022.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sean Robinson, 202-268-8405.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The United States Postal Service® hereby gives notice that, pursuant to 39 U.S.C. 3642 and 3632(b)(3), on October 3, 2022, it filed with the Postal Regulatory Commission a 
                    <E T="03">USPS Request to Add Priority Mail Express, Priority Mail, First-Class Package Service, and Parcel Select Service Contract 59 to Competitive Product List.</E>
                     Documents are available at 
                    <E T="03">www.prc.gov,</E>
                     Docket Nos. MC2023-5, CP2023-5.
                </P>
                <SIG>
                    <NAME>Sarah Sullivan,</NAME>
                    <TITLE>Attorney, Ethics &amp; Legal Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22312 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">POSTAL SERVICE</AGENCY>
                <SUBJECT>International Product Change—Priority Mail Express International, Priority Mail International &amp; First-Class Package International Service Agreement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>
                        Postal Service
                        <E T="51">TM</E>
                        .
                    </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Postal Service gives notice of filing a request with the Postal Regulatory Commission to add a Priority Mail Express International, Priority Mail International &amp; First-Class Package International Service contract to the list of Negotiated Service Agreements in the Competitive Product List in the Mail Classification Schedule.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Date of notice:</E>
                         October 14, 2022.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Christopher C. Meyerson, (202) 268-7820.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The United States Postal Service® hereby gives notice that, pursuant to 39 U.S.C. 3642 and 3632(b)(3), on October 7, 2022, it filed with the Postal Regulatory Commission a 
                    <E T="03">USPS Request to Add Priority Mail Express International, Priority Mail International &amp; First-Class Package International Service Contract 7 to Competitive Product List.</E>
                     Documents are available at 
                    <E T="03">www.prc.gov,</E>
                     Docket Nos. MC2023-11 and CP2023-11.
                </P>
                <SIG>
                    <NAME>Sarah Sullivan,</NAME>
                    <TITLE>Attorney, Ethics &amp; Legal Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22387 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">POSTAL SERVICE</AGENCY>
                <SUBJECT>Product Change—Parcel Select Negotiated Service Agreement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>
                        Postal Service
                        <E T="51">TM</E>
                        .
                    </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Postal Service gives notice of filing a request with the Postal Regulatory Commission to add a domestic shipping services contract to the list of Negotiated Service Agreements in the Mail Classification Schedule's Competitive Products List.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Date of required notice:</E>
                         October 14, 2022.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sean Robinson, 202-268-8405.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The United States Postal Service® hereby gives notice that, pursuant to 39 U.S.C. 3642 and 3632(b)(3), on October 3, 2022, it filed with the Postal Regulatory Commission a 
                    <E T="03">USPS Request to Add Parcel Select Contract 53 to Competitive Product List.</E>
                     Documents are available at 
                    <E T="03">www.prc.gov,</E>
                     Docket Nos. MC2023-3, CP2023-3.
                </P>
                <SIG>
                    <NAME>Sarah Sullivan,</NAME>
                    <TITLE>Attorney, Ethics &amp; Legal Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22306 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">POSTAL SERVICE</AGENCY>
                <SUBJECT>Product Change—Priority Mail Express, Priority Mail, First-Class Package Service, and Parcel Select Service Negotiated Service Agreement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>
                        Postal Service
                        <E T="51">TM</E>
                        .
                    </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Postal Service gives notice of filing a request with the Postal Regulatory Commission to add a domestic shipping services contract to the list of Negotiated Service Agreements in the Mail Classification Schedule's Competitive Products List.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Date of required notice:</E>
                         October 14, 2022.
                    </P>
                </DATES>
                <FURINF>
                    <PRTPAGE P="62465"/>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sean Robinson, 202-268-8405.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The United States Postal Service® hereby gives notice that, pursuant to 39 U.S.C. 3642 and 3632(b)(3), on October 5, 2022, it filed with the Postal Regulatory Commission a 
                    <E T="03">USPS Request to Add Priority Mail Express, Priority Mail, First-Class Package Service, and Parcel Select Service Contract 60 to Competitive Product List.</E>
                     Documents are available at 
                    <E T="03">www.prc.gov,</E>
                     Docket Nos. MC2023-6, CP2023-6.
                </P>
                <SIG>
                    <NAME>Sarah Sullivan,</NAME>
                    <TITLE>Attorney, Ethics &amp; Legal Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22310 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">POSTAL SERVICE</AGENCY>
                <SUBJECT>Product Change—Priority Mail Express, Priority Mail, First-Class Package Service, and Parcel Select Service Negotiated Service Agreement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>
                        Postal Service
                        <E T="51">TM</E>
                        .
                    </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Postal Service gives notice of filing a request with the Postal Regulatory Commission to add a domestic shipping services contract to the list of Negotiated Service Agreements in the Mail Classification Schedule's Competitive Products List.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Date of required notice:</E>
                         October 14, 2022.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sean Robinson, 202-268-8405.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The United States Postal Service® hereby gives notice that, pursuant to 39 U.S.C. 3642 and 3632(b)(3), on October 7, 2022, it filed with the Postal Regulatory Commission a 
                    <E T="03">USPS Request to Add Priority Mail Express, Priority Mail, First-Class Package Service, and Parcel Select Service Contract 62 to Competitive Product List.</E>
                     Documents are available at 
                    <E T="03">www.prc.gov,</E>
                     Docket Nos. MC2023-8, CP2023-8.
                </P>
                <SIG>
                    <NAME>Sarah Sullivan,</NAME>
                    <TITLE>Attorney, Ethics &amp; Legal Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22308 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">POSTAL SERVICE</AGENCY>
                <SUBJECT>Product Change—Priority Mail Express, Priority Mail, First-Class Package Service, and Parcel Select Service Negotiated Service Agreement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>
                        Postal Service
                        <E T="51">TM</E>
                        .
                    </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Postal Service gives notice of filing a request with the Postal Regulatory Commission to add a domestic shipping services contract to the list of Negotiated Service Agreements in the Mail Classification Schedule's Competitive Products List.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Date of required notice:</E>
                         October 14, 2022.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sean Robinson, 202-268-8405.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The United States Postal Service® hereby gives notice that, pursuant to 39 U.S.C. 3642 and 3632(b)(3), on October 7, 2022, it filed with the Postal Regulatory Commission a 
                    <E T="03">USPS Request to Add Priority Mail Express, Priority Mail, First-Class Package Service, and Parcel Select Service Contract 64 to Competitive Product List.</E>
                     Documents are available at 
                    <E T="03">www.prc.gov,</E>
                     Docket Nos. MC2023-10, CP2023-10.
                </P>
                <SIG>
                    <NAME>Sarah Sullivan,</NAME>
                    <TITLE>Attorney, Ethics &amp; Legal Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22309 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">POSTAL SERVICE</AGENCY>
                <SUBJECT>Product Change—Priority Mail Express, Priority Mail, First-Class Package Service, and Parcel Select Service Negotiated Service Agreement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>
                        Postal Service
                        <E T="51">TM</E>
                        .
                    </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Postal Service gives notice of filing a request with the Postal Regulatory Commission to add a domestic shipping services contract to the list of Negotiated Service Agreements in the Mail Classification Schedule's Competitive Products List.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Date of required notice:</E>
                         October 14, 2022.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sean Robinson, 202-268-8405.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The United States Postal Service® hereby gives notice that, pursuant to 39 U.S.C. 3642 and 3632(b)(3), on October 7, 2022, it filed with the Postal Regulatory Commission a 
                    <E T="03">USPS Request to Add Priority Mail Express, Priority Mail, First-Class Package Service, and Parcel Select Service Contract 63 to Competitive Product List.</E>
                     Documents are available at 
                    <E T="03">www.prc.gov,</E>
                     Docket Nos. MC2023-9, CP2023-9.
                </P>
                <SIG>
                    <NAME>Sarah Sullivan,</NAME>
                    <TITLE>Attorney, Ethics &amp; Legal Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22314 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">POSTAL SERVICE</AGENCY>
                <SUBJECT>Product Change—Priority Mail Express, Priority Mail, First-Class Package Service, and Parcel Select Service Negotiated Service Agreement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>
                        Postal Service
                        <E T="51">TM</E>
                        .
                    </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Postal Service gives notice of filing a request with the Postal Regulatory Commission to add a domestic shipping services contract to the list of Negotiated Service Agreements in the Mail Classification Schedule's Competitive Products List.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Date of required notice:</E>
                         October 14, 2022.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sean Robinson, 202-268-8405.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The United States Postal Service® hereby gives notice that, pursuant to 39 U.S.C. 3642 and 3632(b)(3), on October 3, 2022, it filed with the Postal Regulatory Commission a 
                    <E T="03">USPS Request to Add Priority Mail Express, Priority Mail, First-Class Package Service, and Parcel Select Service Contract 57 to Competitive Product List.</E>
                     Documents are available at 
                    <E T="03">www.prc.gov,</E>
                     Docket Nos. MC2023-2, CP2023-2.
                </P>
                <SIG>
                    <NAME>Sarah Sullivan,</NAME>
                    <TITLE>Attorney, Ethics &amp; Legal Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22311 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">POSTAL SERVICE</AGENCY>
                <SUBJECT>Product Change—Priority Mail Express, Priority Mail, First-Class Package Service, and Parcel Select Service Negotiated Service Agreement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>
                        Postal Service
                        <E T="51">TM</E>
                        .
                    </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Postal Service gives notice of filing a request with the Postal Regulatory Commission to add a domestic shipping services contract to the list of Negotiated Service Agreements in the Mail Classification Schedule's Competitive Products List.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Date of required notice:</E>
                         October 14, 2022.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sean Robinson, 202-268-8405.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The United States Postal Service® hereby gives notice that, pursuant to 39 U.S.C. 3642 and 3632(b)(3), on October 5, 2022, it filed with the Postal Regulatory Commission a 
                    <E T="03">
                        USPS Request to Add Priority Mail Express, Priority Mail, First-Class Package Service, and Parcel 
                        <PRTPAGE P="62466"/>
                        Select Service Contract 61 to Competitive Product List.
                    </E>
                     Documents are available at 
                    <E T="03">www.prc.gov,</E>
                     Docket Nos. MC2023-7, CP2023-7.
                </P>
                <SIG>
                    <NAME>Sarah Sullivan,</NAME>
                    <TITLE>Attorney, Ethics &amp; Legal Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22313 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">POSTAL SERVICE</AGENCY>
                <SUBJECT>Product Change—Priority Mail Express, Priority Mail, First-Class Package Service, and Parcel Select Service Negotiated Service Agreement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>
                        Postal Service
                        <E T="51">TM</E>
                        .
                    </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Postal Service gives notice of filing a request with the Postal Regulatory Commission to add a domestic shipping services contract to the list of Negotiated Service Agreements in the Mail Classification Schedule's Competitive Products List.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Date of required notice:</E>
                         October 14, 2022.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sean Robinson, 202-268-8405.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The United States Postal Service® hereby gives notice that, pursuant to 39 U.S.C. 3642 and 3632(b)(3), on October 3, 2022, it filed with the Postal Regulatory Commission a 
                    <E T="03">USPS Request to Add Priority Mail Express, Priority Mail, First-Class Package Service, and Parcel Select Service Contract 58 to Competitive Product List.</E>
                     Documents are available at 
                    <E T="03">www.prc.gov,</E>
                     Docket Nos. MC2023-4, CP2023-4.
                </P>
                <SIG>
                    <NAME>Sarah Sullivan,</NAME>
                    <TITLE>Attorney, Ethics &amp; Legal Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22307 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION </AGENCY>
                <DEPDOC>[Release No. 34-96011; File No. SR-CboeBZX-2022-006]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Cboe BZX Exchange, Inc.; Order Disapproving a Proposed Rule Change To List and Trade Shares of the WisdomTree Bitcoin Trust Under BZX Rule 14.11(e)(4), Commodity-Based Trust Shares</SUBJECT>
                <DATE>October 11, 2022.</DATE>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    On January 25, 2022, Cboe BZX Exchange, Inc. (“BZX” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”), pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Exchange Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change to list and trade shares (“Shares”) of the WisdomTree Bitcoin Trust (“Trust”) under BZX Rule 14.11(e)(4), Commodity-Based Trust Shares. The proposed rule change was published for comment in the 
                    <E T="04">Federal Register</E>
                     on February 14, 2022.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 94184 (Feb. 8, 2022), 87 FR 8318 (“Notice”). Comments received on the proposed rule change are available at: 
                        <E T="03">https://www.sec.gov/comments/sr-cboebzx-2022-006/srcboebzx2022006.htm.</E>
                         BZX previously filed, and the Commission disapproved, a substantially similar proposal to list and trade the Shares of the Trust. 
                        <E T="03">See</E>
                         Notice of Filing of a Proposed Rule Change to List and Trade Shares of the WisdomTree Bitcoin Trust Under BZX Rule 14.11(e)(4), Commodity-Based Trust Shares, Securities Exchange Act Release No. 91521 (Apr. 9, 2021), 86 FR 19917 (Apr. 15, 2021); Order Disapproving a Proposed Rule Change To List and Trade Shares of the WisdomTree Bitcoin Trust Under BZX Rule 14.11(e)(4), Commodity-Based Trust Shares, Securities Exchange Act Release No. 93700 (Dec. 1, 2021), 86 FR 69322 (Dec. 7, 2021) (SR-CboeBZX-2021-024) (“WisdomTree Order”).
                    </P>
                </FTNT>
                <P>
                    On March 18, 2022, pursuant to Section 19(b)(2) of the Exchange Act,
                    <SU>4</SU>
                    <FTREF/>
                     the Commission designated a longer period within which to approve the proposed rule change, disapprove the proposed rule change, or institute proceedings to determine whether to disapprove the proposed rule change.
                    <SU>5</SU>
                    <FTREF/>
                     On May 13, 2022, the Commission instituted proceedings under Section 19(b)(2)(B) of the Exchange Act 
                    <SU>6</SU>
                    <FTREF/>
                     to determine whether to approve or disapprove the proposed rule change,
                    <SU>7</SU>
                    <FTREF/>
                     and on August 4, 2022, the Commission designated a longer period for Commission action on the proposed rule change.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 94476, 87 FR 16800 (Mar. 24, 2022).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         15 U.S.C. 78s(b)(2)(B).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 94907, 87 FR 30546 (May 19, 2022).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 95422, 87 FR 48738 (Aug. 10, 2022).
                    </P>
                </FTNT>
                <P>
                    This order disapproves the proposed rule change. The Commission concludes that BZX has not met its burden under the Exchange Act and the Commission's Rules of Practice to demonstrate that its proposal is consistent with the requirements of Exchange Act Section 6(b)(5), which requires, in relevant part, that the rules of a national securities exchange be “designed to prevent fraudulent and manipulative acts and practices” and “to protect investors and the public interest.” 
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>
                    When considering whether BZX's proposal to list and trade the Shares is designed to prevent fraudulent and manipulative acts and practices, the Commission applies the same analytical framework used in its orders considering previous proposals to list bitcoin 
                    <SU>10</SU>
                    <FTREF/>
                    -based commodity trusts and bitcoin-based trust issued receipts to assess whether a listing exchange of an exchange-traded product (“ETP”) can meet its obligations under Exchange Act Section 6(b)(5).
                    <SU>11</SU>
                    <FTREF/>
                     As the Commission 
                    <PRTPAGE P="62467"/>
                    has explained, an exchange that lists bitcoin-based ETPs 
                    <SU>12</SU>
                    <FTREF/>
                     can meet its obligations under Exchange Act Section 6(b)(5) by demonstrating that the exchange has a comprehensive surveillance-sharing agreement with a regulated market of significant size related to the underlying or reference bitcoin assets.
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Bitcoins are digital assets that are issued and transferred via a decentralized, open-source protocol used by a peer-to-peer computer network through which transactions are recorded on a public transaction ledger known as the “bitcoin blockchain.” The bitcoin protocol governs the creation of new bitcoins and the cryptographic system that secures and verifies bitcoin transactions. 
                        <E T="03">See, e.g.,</E>
                         Notice, 87 FR at 8320.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         Order Setting Aside Action by Delegated Authority and Disapproving a Proposed Rule Change, as Modified by Amendments No. 1 and 2, To List and Trade Shares of the Winklevoss Bitcoin Trust, Securities Exchange Act Release No. 83723 (July 26, 2018), 83 FR 37579 (Aug. 1, 2018) (SR-BatsBZX-2016-30) (“Winklevoss Order”); Order Disapproving a Proposed Rule Change, as Modified by Amendment No. 1, To Amend NYSE Arca Rule 8.201-E (Commodity-Based Trust Shares) and To List and Trade Shares of the United States Bitcoin and Treasury Investment Trust Under NYSE Arca Rule 8.201-E, Securities Exchange Act Release No. 88284 (Feb. 26, 2020), 85 FR 12595 (Mar. 3, 2020) (SR-NYSEArca-2019-39) (“USBT Order”); WisdomTree Order; Order Disapproving a Proposed Rule Change To List and Trade Shares of the Valkyrie Bitcoin Fund Under NYSE Arca Rule 8.201-E (Commodity-Based Trust Shares), Securities Exchange Act Release No. 93859 (Dec. 22, 2021), 86 FR 74156 (Dec. 29, 2021) (SR-NYSEArca-2021-31) (“Valkyrie Order”); Order Disapproving a Proposed Rule Change To List and Trade Shares of the Kryptoin Bitcoin ETF Trust Under BZX Rule 14.11(e)(4), Commodity-Based Trust Shares, Securities Exchange Act Release No. 93860 (Dec. 22, 2021), 86 FR 74166 (Dec. 29, 2021) (SR-CboeBZX-2021-029) (“Kryptoin Order”); Order Disapproving a Proposed Rule Change To List and Trade Shares of the First Trust SkyBridge Bitcoin ETF Trust Under NYSE Arca Rule 8.201-E, Securities Exchange Act Release No. 94006 (Jan. 20, 2022), 87 FR 3869 (Jan. 25, 2022) (SR-NYSEArca-2021-37) (“SkyBridge Order”); Order Disapproving a Proposed Rule Change To List and Trade Shares of the Wise Origin Bitcoin Trust Under BZX Rule 14.11(e)(4), Commodity-Based Trust Shares, Securities Exchange Act Release No. 94080 (Jan. 27, 2022), 87 FR 5527 (Feb. 1, 2022) (SR-CboeBZX-2021-039) (“Wise Origin Order”); Order Disapproving a Proposed Rule Change To List and Trade Shares of the NYDIG Bitcoin ETF Under NYSE Arca Rule 8.201-E (Commodity-Based Trust Shares), Securities Exchange Act Release No. 94395 (Mar. 10, 2022), 87 FR 14932 (Mar. 16, 2022) (SR-NYSEArca-2021-57) (“NYDIG Order”); Order Disapproving a Proposed Rule Change To List and Trade Shares of the Global X Bitcoin Trust Under BZX Rule 14.11(e)(4), Commodity-Based Trust Shares, Securities Exchange Act Release No. 94396 (Mar. 10, 2022), 87 FR 14912 (Mar. 16, 2022) (SR-CboeBZX-2021-052) (“Global X Order”); Order Disapproving a Proposed Rule Change, as Modified by Amendment No. 1, To List and Trade Shares of the ARK 21Shares Bitcoin ETF Under BZX Rule 14.11(e)(4), Commodity-Based Trust Shares, Securities Exchange Act Release No. 94571 (Mar. 31, 2022), 87 FR 20014 (Apr. 6, 2022) (SR-CboeBZX-2021-051) (“ARK 21Shares Order”); 
                        <PRTPAGE/>
                        Order Disapproving a Proposed Rule Change To List and Trade Shares of the One River Carbon Neutral Bitcoin Trust Under NYSE Arca Rule 8.201-E (Commodity-Based Trust Shares), Securities Exchange Act Release No. 94999 (May 27, 2022), 87 FR 33548 (June 2, 2022) (SR-NYSEArca-2021-67) (“One River Order”); Order Disapproving a Proposed Rule Change To List and Trade Shares of the Bitwise Bitcoin ETP Trust Under NYSE Arca Rule 8.201-E (Commodity-Based Trust Shares), Securities Exchange Act Release No. 95179 (June 29, 2022), 87 FR 40282 (July 6, 2022) (SR-NYSEArca-2021-89) (“Bitwise Order”); Order Disapproving a Proposed Rule Change, as Modified by Amendment No. 1, To List and Trade Shares of Grayscale Bitcoin Trust under NYSE Arca Rule 8.201-E (Commodity-Based Trust Shares), Securities Exchange Act Release No. 95180 (June 29, 2022), 87 FR 40299 (July 6, 2022) (SR-NYSEArca-2021-90) (“Grayscale Order”). In addition, orders were issued by delegated authority on the following matters: Order Disapproving a Proposed Rule Change, as Modified by Amendment No. 1, Relating to the Listing and Trading of Shares of the SolidX Bitcoin Trust Under NYSE Arca Equities Rule 8.201, Securities Exchange Act Release No. 80319 (Mar. 28, 2017), 82 FR 16247 (Apr. 3, 2017) (SR-NYSEArca-2016-101) (“SolidX Order”); Order Disapproving a Proposed Rule Change To List and Trade the Shares of the ProShares Bitcoin ETF and the ProShares Short Bitcoin ETF, Securities Exchange Act Release No. 83904 (Aug. 22, 2018), 83 FR 43934 (Aug. 28, 2018) (SR-NYSEArca-2017-139) (“ProShares Order”); Order Disapproving a Proposed Rule Change To List and Trade the Shares of the GraniteShares Bitcoin ETF and the GraniteShares Short Bitcoin ETF, Securities Exchange Act Release No. 83913 (Aug. 22, 2018), 83 FR 43923 (Aug. 28, 2018) (SR-CboeBZX-2018-001) (“GraniteShares Order”); Order Disapproving a Proposed Rule Change To List and Trade Shares of the VanEck Bitcoin Trust Under BZX Rule 14.11(e)(4), Commodity-Based Trust Shares, Securities Exchange Act Release No. 93559 (Nov. 12, 2021), 86 FR 64539 (Nov. 18, 2021) (SR-CboeBZX-2021-019) (“VanEck Order”); Order Granting Approval of a Proposed Rule Change, as Modified by Amendment No. 2, To List and Trade Shares of the Teucrium Bitcoin Futures Fund Under NYSE Arca Rule 8.200-E, Commentary .02 (Trust Issued Receipts), Securities Exchange Act Release No. 94620 (Apr. 6, 2022), 87 FR 21676 (Apr. 12, 2022) (SR-NYSEArca-2021-53) (“Teucrium Order”); Order Granting Approval of a Proposed Rule Change, as Modified by Amendment Nos. 1 and 2, To List and Trade Shares of the Valkyrie XBTO Bitcoin Futures Fund Under Nasdaq Rule 5711(g), Securities Exchange Act Release No. 94853 (May 5, 2022), 87 FR 28848 (May 11, 2022) (SR-NASDAQ-2021-066) (“Valkyrie XBTO Order”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         As used in this order, the term “ETFs” refers to open-end exchange-traded funds that register the offer and sale of their shares under the Securities Act of 1933 (“Securities Act”) and are regulated as investment companies under the Investment Company Act of 1940 (“1940 Act”). The term “ETPs” refers to exchange-traded products that register the offer and sale of their shares under the Securities Act but are not regulated under the 1940 Act, such as commodity trusts and trust issued receipts.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See</E>
                         USBT Order, 85 FR at 12596. 
                        <E T="03">See also</E>
                         Winklevoss Order, 83 FR at 37592 n.202 and accompanying text (discussing previous Commission approvals of commodity-trust ETPs); GraniteShares Order, 83 FR at 43925-27 nn.35-39 and accompanying text (discussing previous Commission approvals of commodity-futures ETPs).
                    </P>
                </FTNT>
                <P>
                    In this context, the terms “significant market” and “market of significant size” include a market (or group of markets) as to which (a) there is a reasonable likelihood that a person attempting to manipulate the ETP would also have to trade on that market to successfully manipulate the ETP, so that a surveillance-sharing agreement would assist in detecting and deterring misconduct, and (b) it is unlikely that trading in the ETP would be the predominant influence on prices in that market.
                    <SU>14</SU>
                    <FTREF/>
                     A surveillance-sharing agreement must be entered into with a “significant market” to assist in detecting and deterring manipulation of the ETP, because a person attempting to manipulate the ETP is reasonably likely to also engage in trading activity on that “significant market.” 
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See</E>
                         Winklevoss Order, 83 FR at 37594. 
                        <E T="03">See also</E>
                         USBT Order, 85 FR at 12596-97; WisdomTree Order, 86 FR at 69322.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         USBT Order, 85 FR at 12597.
                    </P>
                </FTNT>
                <P>
                    Although surveillance-sharing agreements are not the exclusive means by which a listing exchange of a commodity-trust ETP can meet its obligations under Exchange Act Section 6(b)(5), such agreements have previously provided the basis for the exchanges that list commodity-trust ETPs to meet those obligations, and the Commission has historically recognized their importance. And where, as here, a listing exchange fails to establish that other means to prevent fraudulent and manipulative acts and practices will be sufficient, the listing exchange must enter into a surveillance-sharing agreement with a regulated market of significant size because such agreements detect and deter fraudulent and manipulative activity.
                    <SU>16</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See</E>
                         Amendment to Rule Filing Requirements for Self-Regulatory Organizations Regarding New Derivative Securities Products, Securities Exchange Act Release No. 40761 (Dec. 8, 1998), 63 FR 70952, 70954, 70959 (Dec. 22, 1998) (File No. S7-13-98) (“NDSP Adopting Release”). 
                        <E T="03">See also</E>
                         Winklevoss Order, 83 FR at 37593-94; ProShares Order, 83 FR at 43936; GraniteShares Order, 83 FR at 43924; USBT Order, 85 FR at 12596.
                    </P>
                </FTNT>
                <P>
                    The Commission has long recognized that surveillance-sharing agreements “provide a necessary deterrent to manipulation because they facilitate the availability of information needed to fully investigate a manipulation if it were to occur” and thus “enable the Commission to continue to effectively protect investors and promote the public interest.” 
                    <SU>17</SU>
                    <FTREF/>
                     As the Commission has emphasized, it is essential for an exchange listing a derivative securities product to have the ability that surveillance-sharing agreements provide to obtain information necessary to detect, investigate, and deter fraud and market manipulation, as well as violations of exchange rules and applicable federal securities laws and rules.
                    <SU>18</SU>
                    <FTREF/>
                     The hallmarks of a surveillance-sharing agreement are that the agreement provides for the sharing of information about market trading activity, clearing activity, and customer identity; that the parties to the agreement have reasonable ability to obtain access to and produce requested information; and that no existing rules, laws, or practices would impede one party to the agreement from obtaining this information from, or producing it to, the other party.
                    <SU>19</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         NDSP Adopting Release, 63 FR at 70954, 70959. 
                        <E T="03">See also id.</E>
                         at 70959 (“It is essential that the SRO [self-regulatory organization] have the ability to obtain the information necessary to detect and deter market manipulation, illegal trading and other abuses involving the new derivative securities product. Specifically, there should be a comprehensive ISA [information-sharing agreement] that covers trading in the new derivative securities product and its underlying securities in place between the SRO listing or trading a derivative product and the markets trading the securities underlying the new derivative securities product.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">See</E>
                         NDSP Adopting Release, 63 FR at 70959.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See</E>
                         Winklevoss Order, 83 FR at 37592-93 (discussing Letter from Brandon Becker, Director, Division of Market Regulation, Commission, to Gerard D. O'Connell, Chairman, Intermarket Surveillance Group (June 3, 1994), 
                        <E T="03">available at https://www.sec.gov/divisions/marketreg/mr-noaction/isg060394.htm</E>
                        ).
                    </P>
                </FTNT>
                <P>
                    The Commission has explained that the ability of a national securities exchange to enter into surveillance-sharing agreements “furthers the protection of investors and the public interest because it will enable the [e]xchange to conduct prompt investigations into possible trading violations and other regulatory improprieties.” 
                    <SU>20</SU>
                    <FTREF/>
                     The Commission has also long taken the position that surveillance-sharing agreements are important in the context of exchange listing of derivative security products, such as equity options, because a surveillance-sharing agreement “permits the sharing of information” that is “necessary to detect” manipulation and “provide[s] an important deterrent to manipulation because [it] facilitate[s] the availability of information needed to fully investigate a potential 
                    <PRTPAGE P="62468"/>
                    manipulation if it were to occur.” 
                    <SU>21</SU>
                    <FTREF/>
                     With respect to ETPs, when approving the listing and trading of one of the first commodity-linked ETPs—a commodity-linked exchange-traded note—on a national securities exchange, the Commission continued to emphasize the importance of surveillance-sharing agreements, stating that the listing exchange had entered into surveillance-sharing agreements with each of the futures markets on which pricing of the ETP would be based and stating that “[t]hese agreements should help to ensure the availability of information necessary to detect and deter potential manipulations and other trading abuses, thereby making [the commodity-linked notes] less readily susceptible to manipulation.” 
                    <SU>22</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         Securities Exchange Act Release No. 27877 (Apr. 4, 1990), 55 FR 13344 (Apr. 10, 1990) 
                        <E T="03">(N</E>
                        otice of Filing and Order Granting Accelerated Approval to Proposed Rule Change Regarding Cooperative Agreements With Domestic and Foreign Self-Regulatory Organizations) (SR-NYSE-90-14).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         Securities Exchange Act Release No. 33555 (Jan. 31, 1994), 59 FR 5619, 5621 (Feb. 7, 1994) (SR-Amex-93-28) (order approving listing of options on American Depositary Receipts (“ADR”)) (“ADR Option Order”). The Commission further stated that it “generally believes that having a comprehensive surveillance sharing agreement in place, between the exchange where the ADR option trades and the exchange where the foreign security underlying the ADR primarily trades, will ensure the integrity of the marketplace. The Commission further believes that the ability to obtain relevant surveillance information, including, among other things, the identity of the ultimate purchasers and sellers of securities, is an essential and necessary component of a comprehensive surveillance sharing agreement.” 
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         Securities Exchange Act Release No. 35518 (Mar. 21, 1995), 60 FR 15804, 15807 (Mar. 27, 1995) (SR-Amex-94-30). 
                        <E T="03">See also</E>
                         Winklevoss Order, 83 FR at 37593 n.206.
                    </P>
                </FTNT>
                <P>
                    Consistent with these statements, for the commodity-trust ETPs approved to date for listing and trading, there has been in 
                    <E T="03">every</E>
                     case at least one significant, regulated market for trading futures on the underlying commodity and the ETP listing exchange has entered into surveillance-sharing agreements with, or held Intermarket Surveillance Group (“ISG”) membership in common with, that market.
                    <SU>23</SU>
                    <FTREF/>
                     Moreover, the surveillance-sharing agreements have been consistently present whenever the Commission has approved the listing and trading of derivative securities, even where the underlying securities were also listed on national securities exchanges—such as options based on an index of stocks traded on a national securities exchange—and were thus subject to the Commission's direct regulatory authority.
                    <SU>24</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">See</E>
                         Winklevoss Order, 83 FR at 37594. See also SolidX Order, 82 FR at 16254-55 n.125 for a discussion of the representations the Commission has received from listing exchanges in connection with proposals to list commodity-trust ETPs about the existence of a significant, regulated market for trading futures on the underlying commodity and the listing exchanges' ability to obtain trading information with respect to such market. Furthermore, the Commission notes that each of those cases dealt with a futures market that had been trading for a long period of time before an exchange proposed a commodity-trust ETP based on the asset underlying those futures. For example, silver futures and gold futures began trading in 1933 and 1974, respectively, 
                        <E T="03">see https://www.cmegroup.com/media-room/historical-first-trade-dates.html,</E>
                         and the first ETPs based on spot silver and gold were approved for listing and trading in 2006 and 2004. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 53521 (Mar. 20, 2006), 71 FR 14967 (Mar. 24, 2006) (SR-Amex-2005-072) (order approving iShares Silver Trust); Securities Exchange Act Release No. 50603 (Oct. 28, 2004), 69 FR 64614 (Nov. 5, 2004) (SR-NYSE-2004-22) (order approving streetTRACKS Gold Shares). Platinum futures and palladium futures began trading in 1956 and 1968, respectively, 
                        <E T="03">see https://www.cmegroup.com/media-room/historical-first-trade-dates.html,</E>
                         and the first ETPs based on spot platinum and palladium were approved for listing and trading in 2009. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 61220 (Dec. 22, 2009), 74 FR 68895 (Dec. 29, 2009) (SR-NYSEArca-2009-94) (order approving ETFS Palladium Trust); Securities Exchange Act Release No. 61219 (Dec. 22, 2009), 74 FR 68886 (Dec. 29, 2009) (SR-NYSEArca-2009-95) (order approving ETFS Platinum Trust). Copper futures began trading in 1988, 
                        <E T="03">see https://www.cmegroup.com/media-room/historical-first-trade-dates.html#metals,</E>
                         and the first ETPs based on spot copper were approved for listing and trading in 2012. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 68440 (Dec. 14, 2012), 77 FR 75468 (Dec. 20, 2012) (SR-NYSEArca-2012-28) (order approving JPM XF Physical Copper Trust).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">See</E>
                         USBT Order, 85 FR at 12597; ADR Option Order, 59 FR at 5621. The Commission has also recognized that surveillance-sharing agreements provide a necessary deterrent to fraud and manipulation in the context of index options even when (i) all of the underlying index component stocks were either registered with the Commission or exempt from registration under the Exchange Act; (ii) all of the underlying index component stocks were traded in the U.S. either directly or as ADRs on a national securities exchange; and (iii) effective international ADR arbitrage alleviated concerns over the relatively smaller ADR trading volume, helped to ensure that ADR prices reflected the pricing on the home market, and helped to ensure more reliable price determinations for settlement purposes, due to the unique composition of the index and reliance on ADR prices. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 26653 (Mar. 21, 1989), 54 FR 12705, 12708 (Mar. 28, 1989) (SR-Amex-87-25) (stating that “surveillance-sharing agreements between the exchange on which the index option trades and the markets that trade the underlying securities are necessary” and that “[t]he exchange of surveillance data by the exchange trading a stock index option and the markets for the securities comprising the index is important to the detection and deterrence of intermarket manipulation”). And the Commission has explained that surveillance-sharing agreements “ensure the availability of information necessary to detect and deter potential manipulations and other trading abuses” even when approving options based on an index of stocks traded on a national securities exchange. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 30830 (June 18, 1992), 57 FR 28221, 28224 (June 24, 1992) (SR-Amex-91-22).
                    </P>
                </FTNT>
                <P>
                    Listing exchanges have also attempted to demonstrate that other means besides surveillance-sharing agreements will be sufficient to prevent fraudulent and manipulative acts and practices, including that the bitcoin market as a whole or the relevant underlying bitcoin market is “uniquely” and “inherently” resistant to fraud and manipulation.
                    <SU>25</SU>
                    <FTREF/>
                     In response, the Commission has stated that, if a listing exchange could establish that the underlying market inherently possesses a unique resistance to manipulation beyond the protections that are utilized by traditional commodity or securities markets, the listing market would not necessarily need to enter into a surveillance-sharing agreement with a regulated significant market.
                    <SU>26</SU>
                    <FTREF/>
                     Such resistance to fraud and manipulation, however, must be novel and beyond those protections that exist in traditional commodity markets or securities markets for which surveillance-sharing agreements in the context of listing derivative securities products have been consistently present.
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See</E>
                         USBT Order, 85 FR at 12597.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">See</E>
                         Winklevoss Order, 83 FR at 37580, 37582-91 (addressing assertions that “bitcoin and [spot] bitcoin markets,” generally, as well as one bitcoin trading platform, specifically, have unique resistance to fraud and manipulation). 
                        <E T="03">See also</E>
                         USBT Order, 85 FR at 12597.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">See</E>
                         USBT Order, 85 FR at 12597, 12599.
                    </P>
                </FTNT>
                <P>
                    Here, BZX contends that approval of the proposal is consistent with Section 6(b)(5) of the Exchange Act, and, in particular, Section 6(b)(5)'s requirement that the rules of a national securities exchange be designed to prevent fraudulent and manipulative acts and practices and to protect investors and the public interest.
                    <SU>28</SU>
                    <FTREF/>
                     As discussed in more detail below, BZX asserts that the proposal is consistent with Section 6(b)(5) of the Exchange Act because the Exchange has a comprehensive surveillance-sharing agreement with a regulated market of significant size,
                    <SU>29</SU>
                    <FTREF/>
                     and there exist other means to prevent fraudulent and manipulative acts and practices that are sufficient to justify dispensing with the detection and deterrence of fraud and manipulation provided by a comprehensive surveillance-sharing agreement with a regulated market of significant size related to spot bitcoin.
                    <SU>30</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">See</E>
                         Notice, 87 FR at 8327-29, 8331-34.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See id.</E>
                         at 8327-28, 8332-33.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         
                        <E T="03">See id.</E>
                         at 8328-29, 8333.
                    </P>
                </FTNT>
                <P>
                    In the analysis that follows, the Commission examines whether the proposed rule change is consistent with Section 6(b)(5) of the Exchange Act by addressing: in Section III.B.1 assertions that other means besides surveillance-sharing agreements will be sufficient to prevent fraudulent and manipulative acts and practices; in Section III.B.2 assertions that BZX has entered into a comprehensive surveillance-sharing agreement with a regulated market of significant size related to spot bitcoin; in Section III.B.3 assertions that the 
                    <PRTPAGE P="62469"/>
                    Commission must approve the proposal because the Commission has approved the listing and trading of ETFs and ETPs that hold CME bitcoin futures; and in Section III.C assertions that the proposal is consistent with the protection of investors and the public interest.
                </P>
                <P>Based on its analysis, the Commission concludes that BZX has not established that other means to prevent fraudulent and manipulative acts and practices are sufficient to justify dispensing with the detection and deterrence of fraud and manipulation provided by a comprehensive surveillance-sharing agreement with a regulated market of significant size related to spot bitcoin. The Commission further concludes that BZX has not established that it has a comprehensive surveillance-sharing agreement with a regulated market of significant size related to spot bitcoin, the underlying bitcoin assets that would be held by the Trust. As discussed further below, BZX repeats various assertions made in prior bitcoin-based ETP proposals that the Commission has previously addressed and rejected, including in the prior WisdomTree Order—and more importantly, BZX does not respond to the Commission's reasons for rejecting those assertions. As a result, the Commission is unable to find that the proposed rule change is consistent with the statutory requirements of Exchange Act Section 6(b)(5).</P>
                <P>The Commission emphasizes that its disapproval of this proposed rule change does not rest on an evaluation of the relative investment quality of a product holding spot bitcoin versus a product holding CME bitcoin futures, or an assessment of whether bitcoin, or blockchain technology more generally, has utility or value as an innovation or an investment. Rather, the Commission is disapproving this proposed rule change because, as discussed below, BZX has not met its burden to demonstrate that its proposal is consistent with the requirements of Exchange Act Section 6(b)(5).</P>
                <HD SOURCE="HD1">II. Description of the Proposed Rule Change</HD>
                <P>
                    As described in more detail in the Notice,
                    <SU>31</SU>
                    <FTREF/>
                     the Exchange proposes to list and trade the Shares of the Trust under BZX Rule 14.11(e)(4), which governs the listing and trading of Commodity-Based Trust Shares on the Exchange.
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         
                        <E T="03">See supra</E>
                         note 3. According to the Exchange, the Trust has filed an amended registration statement on Form S-1 under the Securities Act dated December 8, 2021 (File No. 333-254134) (“Registration Statement”).
                    </P>
                </FTNT>
                <P>
                    The investment objective of the Trust would be to gain exposure to the price of bitcoin, less expenses and liabilities of the Trust's operation.
                    <SU>32</SU>
                    <FTREF/>
                     The Trust would hold bitcoin and would calculate the Trust's net asset value (“NAV”) daily based on the value of bitcoin as reflected by the CF Bitcoin US Settlement Price (“Reference Rate”). The Reference Rate was created, and is administered, by CF Benchmarks Ltd. (“Benchmark Administrator”), an independent entity.
                    <SU>33</SU>
                    <FTREF/>
                     The Reference Rate is a once-a-day benchmark rate of the U.S. dollar price of bitcoin (USD/BTC), calculated as of 4:00 p.m. E.T., and is based on materially the same methodology (except calculation time) 
                    <SU>34</SU>
                    <FTREF/>
                     as the Benchmark Administrator's CME CF Bitcoin Reference Rate (“BRR”), which is the rate on which CME bitcoin futures contracts are cash-settled in U.S. dollars.
                    <SU>35</SU>
                    <FTREF/>
                     The Reference Rate aggregates the trade flow of several bitcoin platforms (current platform composition of the Reference Rate is Bitstamp, Coinbase, Gemini, itBit, and Kraken, collectively, “Constituent Bitcoin Platforms”). In calculating the Reference Rate, the methodology creates a joint list of the trade prices and sizes from the Constituent Bitcoin Platforms between 3:00 p.m. E.T. and 4:00 p.m. E.T. and then divides this list into 12 equally-sized time intervals of five minutes and calculates the volume-weighted median trade price for each of those time intervals. The Reference Rate is the arithmetic mean of these 12 volume-weighted median trade prices.
                    <SU>36</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         
                        <E T="03">See</E>
                         Notice, 87 FR at 8329. WisdomTree Digital Commodity Services, LLC (“Sponsor”) is the sponsor of the Trust, and Delaware Trust Company is the trustee. U.S. Bank, N.A. would serve as the custodian of the Trust (“Custodian”). U.S. Bancorp Fund Services, LLC dba U.S. Bank Global Fund Services would be the administrator and transfer agent (“Administrator”) of the Trust. Foreside Fund Services LLC would be the marketing agent in connection with the creation and redemption of Shares. 
                        <E T="03">See id.</E>
                         at 8318-19, 8329.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         
                        <E T="03">See id.</E>
                         at 8329. The Commission notes that the Benchmark Administrator's website states that the Reference Rate was 
                        <E T="03">discontinued</E>
                         as of April 2022. 
                        <E T="03">See https://www.cfbenchmarks.com/blog/cessation-of-the-cf-bitcoin-us-settlement-price-and-cf-ether-dollar-us-settlement-price.</E>
                         The Exchange has not amended its filing to indicate how the Trust would value bitcoin following discontinuation of the Reference Rate.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         The Reference Rate is calculated as of 4:00 p.m. E.T., whereas the BRR is calculated as of 4:00 p.m. London Time. 
                        <E T="03">See id.</E>
                         at 8329 n.77.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         
                        <E T="03">See id.</E>
                         at 8329.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         
                        <E T="03">See id.</E>
                         at 8329-30.
                    </P>
                </FTNT>
                <P>
                    Each Share would represent a fractional undivided beneficial interest in and ownership of the Trust. The Trust's assets would consist of bitcoin held by the Custodian on behalf of the Trust. The Trust generally does not intend to hold cash or cash equivalents. However, there may be situations where the Trust would unexpectedly hold cash on a temporary basis.
                    <SU>37</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         
                        <E T="03">See id.</E>
                         at 8329.
                    </P>
                </FTNT>
                <P>
                    The Administrator would determine the NAV and NAV per Share of the Trust on each day that the Exchange is open for regular trading after 4:00 p.m. E.T. (often by 5:30 p.m. E.T. and almost always by 8:00 p.m. E.T.). The NAV of the Trust would be the aggregate value of the Trust's assets, less total liabilities of the Trust, each determined on the basis of generally accepted accounting principles. In determining the Trust's NAV, the Administrator would value the bitcoin held by the Trust based on the price set by the Reference Rate as of 4:00 p.m. E.T.
                    <SU>38</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         
                        <E T="03">See id.</E>
                         at 8330.
                    </P>
                </FTNT>
                <P>
                    The Trust would provide information regarding the Trust's bitcoin holdings, as well as an Intraday Indicative Value (“IIV”) per Share updated every 15 seconds, as calculated by the Exchange or a third-party financial data provider during the Exchange's Regular Trading Hours (9:30 a.m. to 4:00 p.m. E.T.). The IIV would be calculated by using the prior day's closing NAV per Share as a base and updating that value during Regular Trading Hours to reflect changes in the value of the Trust's bitcoin holdings during the trading day.
                    <SU>39</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         
                        <E T="03">See id.</E>
                         at 8334.
                    </P>
                </FTNT>
                <P>
                    When the Trust sells or redeems its Shares, it would do so in “in-kind” transactions in blocks of 50,000 Shares at the Trust's NAV. Authorized participants would deliver, or facilitate the delivery of, bitcoin to the Trust's account with the Custodian in exchange for Shares when they purchase Shares, and the Trust, through the Custodian, would deliver bitcoin to such authorized participants when they redeem Shares with the Trust.
                    <SU>40</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         
                        <E T="03">See id.</E>
                         at 8329.
                    </P>
                </FTNT>
                <P>
                    Further, BZX represents that, although the Trust would not be an investment company registered under the 1940 Act, in seeking to protect investors and the public, the Sponsor has taken 1940 Act considerations into account in the structure of the Trust's operation.
                    <SU>41</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         
                        <E T="03">See id.</E>
                         at 8323-24. For a more detailed description of those considerations, 
                        <E T="03">see infra</E>
                         note 221 and accompanying text.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Discussion</HD>
                <HD SOURCE="HD2">A. The Applicable Standard for Review</HD>
                <P>
                    The Commission must consider whether BZX's proposal is consistent with the Exchange Act. Section 6(b)(5) of the Exchange Act requires, in relevant part, that the rules of a national securities exchange be designed “to 
                    <PRTPAGE P="62470"/>
                    prevent fraudulent and manipulative acts and practices” and “to protect investors and the public interest.” 
                    <SU>42</SU>
                    <FTREF/>
                     Under the Commission's Rules of Practice, the “burden to demonstrate that a proposed rule change is consistent with the Exchange Act and the rules and regulations issued thereunder . . . is on the self-regulatory organization [`SRO'] that proposed the rule change.” 
                    <SU>43</SU>
                    <FTREF/>
                     
                </P>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         15 U.S.C. 78f(b)(5). Pursuant to Section 19(b)(2) of the Exchange Act, 15 U.S.C. 78s(b)(2), the Commission must disapprove a proposed rule change filed by a national securities exchange if it does not find that the proposed rule change is consistent with the applicable requirements of the Exchange Act. Exchange Act Section 6(b)(5) states that an exchange shall not be registered as a national securities exchange unless the Commission determines that “[t]he rules of the exchange are designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to foster cooperation and coordination with persons engaged in regulating, clearing, settling, processing information with respect to, and facilitating transactions in securities, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and, in general, to protect investors and the public interest; and are not designed to permit unfair discrimination between customers, issuers, brokers, or dealers, or to regulate by virtue of any authority conferred by this title matters not related to the purposes of this title or the administration of the exchange.” 15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         Rule 700(b)(3), Commission Rules of Practice, 17 CFR 201.700(b)(3).
                    </P>
                </FTNT>
                <P>
                    The description of a proposed rule change, its purpose and operation, its effect, and a legal analysis of its consistency with applicable requirements must all be sufficiently detailed and specific to support an affirmative Commission finding,
                    <SU>44</SU>
                    <FTREF/>
                     and any failure of an SRO to provide this information may result in the Commission not having a sufficient basis to make an affirmative finding that a proposed rule change is consistent with the Exchange Act and the applicable rules and regulations.
                    <SU>45</SU>
                    <FTREF/>
                     Moreover, “unquestioning reliance” on an SRO's representations in a proposed rule change is not sufficient to justify Commission approval of a proposed rule change.
                    <SU>46</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         
                        <E T="03">Susquehanna Int'l Group, LLP</E>
                         v. 
                        <E T="03">Securities and Exchange Commission,</E>
                         866 F.3d 442, 447 (DC Cir. 2017) (“Susquehanna”).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Whether BZX Has Met Its Burden To Demonstrate That the Proposal Is Designed To Prevent Fraudulent and Manipulative Acts and Practices</HD>
                <HD SOURCE="HD3">(1) Assertions That Other Means Besides Surveillance-Sharing Agreements Will Be Sufficient to Prevent Fraudulent and Manipulative Acts and Practices</HD>
                <HD SOURCE="HD3">(i) Assertions Regarding the Bitcoin Market</HD>
                <P>
                    As stated above, the Commission has recognized that a listing exchange could demonstrate that other means to prevent fraudulent and manipulative acts and practices are sufficient to justify dispensing with the detection and deterrence of fraud and manipulation provided by a comprehensive surveillance-sharing agreement with a regulated market of significant size related to the underlying bitcoin assets, including by demonstrating that the bitcoin market as a whole or the relevant underlying bitcoin market is uniquely and inherently resistant to fraud and manipulation.
                    <SU>47</SU>
                    <FTREF/>
                     Such resistance to fraud and manipulation, however, must be novel and beyond those protections that exist in traditional commodities or securities markets.
                    <SU>48</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         
                        <E T="03">See</E>
                         USBT Order, 85 FR at 12597 n.23. The Commission is not applying a “cannot be manipulated” standard. Instead, the Commission is examining whether the proposal meets the requirements of the Exchange Act and, pursuant to its Rules of Practice, places the burden on the listing exchange to demonstrate the validity of its contentions and to establish that the requirements of the Exchange Act have been met. 
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         
                        <E T="03">See id.</E>
                         at 12597.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(a) BZX's Assertions</HD>
                <P>
                    BZX asserts that bitcoin is resistant to price manipulation. According to BZX, the geographically diverse and continuous nature of bitcoin trading render it difficult and prohibitively costly to manipulate the price of bitcoin.
                    <SU>49</SU>
                    <FTREF/>
                     BZX asserts that fragmentation across bitcoin platforms, the relatively slow speed of transactions, and the capital necessary to maintain a significant presence on each trading platform make manipulation of bitcoin prices through continuous trading activity challenging.
                    <SU>50</SU>
                    <FTREF/>
                     In addition, BZX states that, to the extent that there are bitcoin platforms engaged in or allowing wash trading or other activity intended to manipulate the price of bitcoin on other markets, such pricing does not normally impact prices on other platforms because participants will generally ignore markets with quotes that they deem non-executable.
                    <SU>51</SU>
                    <FTREF/>
                     BZX further argues that the linkage between the bitcoin markets and the presence of arbitrageurs in those markets means that the manipulation of the price of bitcoin on any single venue would require manipulation of the global bitcoin price in order to be effective.
                    <SU>52</SU>
                    <FTREF/>
                     According to BZX, arbitrageurs must have funds distributed across multiple trading platforms in order to take advantage of temporary price dislocations, thereby making it unlikely that there will be strong concentration of funds on any particular bitcoin trading venue.
                    <SU>53</SU>
                    <FTREF/>
                     As a result, BZX concludes that the potential for manipulation on a bitcoin trading platform would require overcoming the liquidity supply of such arbitrageurs who are effectively eliminating any cross-market pricing differences.
                    <SU>54</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         
                        <E T="03">See</E>
                         Notice, 87 FR at 8327 n.65.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>54</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <P>
                    BZX also argues that the significant liquidity in the spot bitcoin market and the impact of market orders on the overall price of bitcoin mean that attempting to move the price of bitcoin is costly and has grown more expensive over the past year.
                    <SU>55</SU>
                    <FTREF/>
                     According to BZX, in January 2020, for example, the cost to buy or sell $5 million worth of bitcoin averaged roughly 30 basis points (compared to 10 basis points in February 2021) with a market impact of 50 basis points (compared to 30 basis points in February 2021). For a $10 million market order, the cost to buy or sell was roughly 50 basis points (compared to 20 basis points in February 2021) with a market impact of 80 basis points (compared to 50 basis points in February 2021). BZX contends that, as the liquidity in the spot bitcoin market increases, it follows that the impact of $5 million and $10 million orders will continue to decrease.
                    <SU>56</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>55</SU>
                         
                        <E T="03">See id.</E>
                         at 8328-29.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>56</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(b) Analysis</HD>
                <P>
                    As with the previous proposals, the Commission here concludes that the record does not support a finding that the bitcoin market is inherently and uniquely resistant to fraud and manipulation. BZX does not sufficiently contest the presence of possible sources of fraud and manipulation in the spot bitcoin market that the Commission has identified in previous orders, including: (1) “wash” trading; 
                    <SU>57</SU>
                    <FTREF/>
                     (2) persons with a 
                    <PRTPAGE P="62471"/>
                    dominant position in bitcoin manipulating bitcoin pricing; (3) hacking of the bitcoin network and trading platforms; (4) malicious control of the bitcoin network; (5) trading based on material, non-public information (for example, plans of market participants to significantly increase or decrease their holdings in bitcoin, new sources of demand for bitcoin, or the decision of a bitcoin-based investment vehicle on how to respond to a “fork” in the bitcoin blockchain, which would create two different, non-interchangeable types of bitcoin) or based on the dissemination of false and misleading information; (6) manipulative activity involving purported “stablecoins,” including Tether (USDT); and (7) fraud and manipulation at bitcoin trading platforms.
                    <SU>58</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>57</SU>
                         
                        <E T="03">See also CFTC</E>
                         v. 
                        <E T="03">Gemini Trust Co., LLC,</E>
                         No. 22-cv-4563 (S.D.N.Y. filed June 2, 2022) (alleging, among other things, failure by Gemini personnel to disclose to the Commodity Futures Trading 
                        <PRTPAGE/>
                        Commission (“CFTC”) that Gemini customers could and did engage in collusive or wash trading).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>58</SU>
                         
                        <E T="03">See</E>
                         USBT Order, 85 FR at 12600-01 &amp; nn.66-67 (discussing J. Griffin &amp; A. Shams, 
                        <E T="03">Is Bitcoin Really Untethered?</E>
                         (Oct. 28, 2019), 
                        <E T="03">available at https://ssrn.com/abstract=3195066</E>
                         and published in 75 J. Finance 1913 (2020)); Winklevoss Order, 83 FR at 37585-86; WisdomTree Order, 86 FR at 69326; Global X Order, 87 FR at 14916; ARK 21Shares Order, 87 FR at 20019; One River Order, 87 FR at 33554; Bitwise Order, 87 FR at 40283-84; Grayscale Order, 87 FR at 40305.
                    </P>
                </FTNT>
                <P>
                    BZX asserts that, because of how bitcoin trades occur, including through continuous means and through fragmented platforms, arbitrage across the bitcoin platforms essentially helps to keep global bitcoin prices aligned with one another, thus hindering manipulation. The Exchange, however, does not provide any data or analysis to support its assertions, either in terms of how closely bitcoin prices are aligned across different bitcoin trading venues or how quickly price disparities may be arbitraged away.
                    <SU>59</SU>
                    <FTREF/>
                     Here, the Exchange provides no evidence to support its assertion of efficient price arbitrage across bitcoin platforms, let alone any evidence that price arbitrage in the bitcoin market is novel or unique so as to warrant the Commission dispensing with the detection and deterrence of fraud and manipulation provided by a comprehensive surveillance-sharing agreement with a regulated market of significant size related to spot bitcoin. As stated above, “unquestioning reliance” on an SRO's representations in a proposed rule change is not sufficient to justify Commission approval of a proposed rule change.
                    <SU>60</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>59</SU>
                         For example, the Registration Statement states that “[i]f increases in throughput on the Bitcoin network lag behind growth in usage of bitcoin, average fees and settlement times may increase considerably . . . which could adversely impact the value of the Shares.” 
                        <E T="03">See</E>
                         Registration Statement at 20. BZX does not provide data or analysis to address, among other things, whether such risks of increased fees and bitcoin transaction settlement times may affect the arbitrage effectiveness that BZX asserts. 
                        <E T="03">See also infra</E>
                         note 73 and accompanying text (referencing statements made in the Registration Statement that contradict assertions made by BZX).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>60</SU>
                         
                        <E T="03">See supra</E>
                         note 46.
                    </P>
                </FTNT>
                <P>
                    In any event, the Commission has explained that efficient price arbitrage is not sufficient to support the finding that a market is uniquely or inherently resistant to manipulation such that the Commission can dispense with surveillance-sharing agreements.
                    <SU>61</SU>
                    <FTREF/>
                     The Commission has stated, for example, that even for equity options based on securities listed on national securities exchanges, the Commission relies on surveillance-sharing agreements to detect and deter fraud and manipulation.
                    <SU>62</SU>
                    <FTREF/>
                     Equities that underlie such options trade on U.S. equity markets that are deep, liquid, and highly interconnected.
                    <SU>63</SU>
                    <FTREF/>
                     Moreover, BZX does not take into account that a market participant with a dominant ownership position would not find it prohibitively expensive to overcome the liquidity supplied by arbitrageurs and could use dominant market share to engage in manipulation.
                    <SU>64</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>61</SU>
                         
                        <E T="03">See</E>
                         Winklevoss Order, 83 FR at 37586; SolidX Order, 82 FR at 16256-57; USBT Order, 85 FR at 12601; WisdomTree Order, 86 FR at 69325; Valkyrie Order, 86 FR at 74159-60; Kryptoin Order, 86 FR at 74170; Wise Origin Order, 87 FR at 5531; ARK 21Shares Order, 87 FR at 20019; Grayscale Order, 87 FR at 40306.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>62</SU>
                         
                        <E T="03">See, e.g.,</E>
                         USBT Order, 85 FR at 12601; WisdomTree Order, 86 FR at 69329; Valkyrie Order, 86 FR at 74160; Kryptoin Order, 86 FR at 74170; Wise Origin Order, 87 FR at 5531; ARK 21Shares Order, 87 FR at 20019; Grayscale Order, 87 FR at 40306-07.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>63</SU>
                         
                        <E T="03">See</E>
                         Market Data Infrastructure Adopting Release, Securities Exchange Act Release No. 90610 (Dec. 9, 2020); 86 FR 18596, 18606-07 (Apr. 9, 2021); Market Data Infrastructure Proposing Release, Securities Exchange Act Release No. 88216 (Feb. 14, 2020), 85 FR 16726, 16728 (Mar. 24, 2020); Concept Release on Equity Market Structure, Securities Exchange Act Release No. 61358 (Jan. 14, 2010), 75 FR 3594 (Jan. 21, 2010). 
                        <E T="03">See also</E>
                         ARK 21Shares Order, 87 FR at 20019 n.70.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>64</SU>
                         
                        <E T="03">See, e.g.,</E>
                         Winklevoss Order, 83 FR at 37584; USBT Order, 85 FR at 12600-01; WisdomTree Order, 86 FR at 69325.
                    </P>
                </FTNT>
                <P>
                    In addition, the Exchange makes the unsupported claim that, to the extent that there are bitcoin platforms engaged in or allowing wash trading or other activity intended to manipulate the price of bitcoin on other markets, market participants will generally ignore those platforms. However, the record does not demonstrate that wash trading and other possible sources of fraud and manipulation in the broader bitcoin spot market will be ignored by market participants.
                    <SU>65</SU>
                    <FTREF/>
                     Without the necessary data or other evidence, the Commission has no basis on which to conclude that bitcoin platforms are insulated from prices of others that engage in or permit fraud or manipulation.
                    <SU>66</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>65</SU>
                         
                        <E T="03">See infra</E>
                         note 89 and accompanying text.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>66</SU>
                         
                        <E T="03">See</E>
                         USBT Order, 85 FR at 12601; WisdomTree Order, 86 FR at 69325.
                    </P>
                </FTNT>
                <P>
                    Further, the continuous nature of bitcoin trading does not support the finding that the bitcoin market is uniquely or inherently resistant to manipulation, and neither do linkages among markets, as BZX asserts.
                    <SU>67</SU>
                    <FTREF/>
                     Even in the presence of continuous trading or linkages among markets, formal (such as those with consolidated quotations or routing requirements) or otherwise (such as in the context of the fragmented, global bitcoin markets), manipulation of asset prices, as a general matter, can occur simply through trading activity that creates a false impression of supply or demand.
                    <SU>68</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>67</SU>
                         
                        <E T="03">See</E>
                         Winklevoss Order, 83 FR at 37585 n.92 and accompanying text.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>68</SU>
                         
                        <E T="03">See id.</E>
                         at 37585. 
                        <E T="03">See also, e.g.,</E>
                         WisdomTree Order, 86 FR at 69325-26.
                    </P>
                </FTNT>
                <P>
                    Moreover, the data furnished by BZX regarding the cost to move the price of bitcoin, and the market impact of such attempts, are incomplete.
                    <SU>69</SU>
                    <FTREF/>
                     BZX does not provide meaningful analysis pertaining to how these figures compare to other markets or why one must conclude, based on the numbers provided, that the bitcoin market is costly to manipulate. In addition, BZX's analysis of the market impact of a mere two sample transactions is not sufficient evidence to conclude that the bitcoin market is resistant to manipulation.
                    <SU>70</SU>
                    <FTREF/>
                     The Commission thus concludes that the record does not demonstrate that the nature of bitcoin trading renders the bitcoin market inherently and uniquely resistant to fraud and manipulation. Even assuming that the Commission agreed with BZX's premise that it is costly to manipulate the bitcoin market and it is becoming increasingly so, any such evidence speaks only to establish that there is potentially some resistance to manipulation, not that it establishes 
                    <E T="03">unique</E>
                     resistance to manipulation that would justify dispensing with the detection and deterrence of fraud and manipulation provided by a comprehensive surveillance-sharing agreement with a regulated market of significant size related to spot bitcoin.
                    <SU>71</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>69</SU>
                         
                        <E T="03">See</E>
                         WisdomTree Order, 86 FR at 69326.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>70</SU>
                         Aside from stating that the “statistics are based on samples of bitcoin liquidity in USD (excluding stablecoins or Euro liquidity) based on executable quotes on Coinbase Pro, Gemini, Bitstamp, Kraken, LMAX Exchange, BinanceUS, and OKCoin during February 2021,” the Exchange provides no other information pertaining to the methodology used to enable the Commission to evaluate these findings or their significance. 
                        <E T="03">See</E>
                         Notice, 87 FR at 8328-29 nn.74-75.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>71</SU>
                         
                        <E T="03">See</E>
                         USBT Order, 85 FR at 12601; WisdomTree Order, 86 FR at 69326; Kryptoin Order, 86 FR at 
                        <PRTPAGE/>
                        74171; Global X Order, 87 FR at 14916; Wise Origin Order, 87 FR at 5531; Grayscale Order, 87 FR at 40306.
                    </P>
                </FTNT>
                <PRTPAGE P="62472"/>
                <P>
                    Finally, BZX does not address risk factors specific to the bitcoin blockchain and bitcoin platforms, described in the Trust's Registration Statement, that undermine the argument that the bitcoin market is inherently resistant to fraud and manipulation.
                    <SU>72</SU>
                    <FTREF/>
                     For example, the Registration Statement acknowledges that “bitcoin [platforms] on which bitcoin trades are relatively new and, in some cases, unregulated, and, therefore, may be more exposed to fraud and security breaches than established, regulated exchanges for other financial assets or instruments”; that “as an intangible asset without centralized issuers or governing bodies, bitcoin has been, and may in the future be, subject to security breaches, cyberattacks or other malicious activities”; that “[t]he trading for bitcoin occurs on multiple trading venues that have various levels and types of regulation, but are not regulated in the same manner as traditional stock and bond exchanges” and if these spot markets “do not operate smoothly or face technical, security or regulatory issues, that could impact the ability of Authorized Participants to make markets in the Shares” which could lead to “trading in the Shares [to] occur at a material premium or discount to the NAV”; that the bitcoin blockchain could be vulnerable to a “51% attack,” in which a bad actor that controls a majority of the processing power dedicated to mining on the bitcoin network may be able to alter the bitcoin blockchain on which the bitcoin network and bitcoin transactions rely; that “some bitcoin [platforms] have been closed due to fraud and manipulative activity” and that larger bitcoin platforms are more likely to be “appealing targets for hackers”; and that “[b]itcoin [platforms] may be more exposed to the risk of market manipulation than exchanges for more traditional assets.” 
                    <SU>73</SU>
                    <FTREF/>
                     The Exchange also acknowledges in the proposed rule change that “largely unregulated currency and spot commodity markets do not provide the same protections as the markets that are subject to the Commission's oversight.” 
                    <SU>74</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>72</SU>
                         
                        <E T="03">See</E>
                         WisdomTree Order, 86 FR at 69326.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>73</SU>
                         Registration Statement at 11, 18-19, 25, 37-38. 
                        <E T="03">See also</E>
                         Winklevoss Order, 83 FR at 37585.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>74</SU>
                         Notice, 87 FR at 8320.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(ii) Assertions Regarding the Reference Rate and the Create/Redeem Process</HD>
                <HD SOURCE="HD3">(a) BZX's Assertions</HD>
                <P>
                    The Exchange also asserts that the Reference Rate, which it uses to value the Trust's bitcoin, is itself resistant to manipulation based on the Reference Rate's methodology.
                    <SU>75</SU>
                    <FTREF/>
                     The Exchange states that the Reference Rate is calculated based on the “Relevant Transactions” 
                    <SU>76</SU>
                    <FTREF/>
                     of all of its Constituent Bitcoin Platforms. All Relevant Transactions are added to a joint list, recording the time of execution, trade price, and size for each transaction, and the list is partitioned by timestamp into 12 equally-sized time intervals of five-minute length.
                    <SU>77</SU>
                    <FTREF/>
                     For each partition separately, the volume-weighted median trade price is calculated from the trade prices and sizes of all Relevant Transactions.
                    <SU>78</SU>
                    <FTREF/>
                     The Reference Rate is then determined by the arithmetic mean of the volume-weighted medians of all partitions.
                    <SU>79</SU>
                    <FTREF/>
                     According to BZX, “[b]y employing the foregoing steps, the Reference Rate thereby seeks to ensure that transactions in bitcoin conducted at outlying prices do not have an undue effect on the value of a specific partition, large trades or clusters of trades transacted over a short period of time will not have an undue influence on the index level, and the effect of large trades at prices that deviate from the prevailing price are mitigated from having an undue influence on the benchmark level.” 
                    <SU>80</SU>
                    <FTREF/>
                     BZX concludes its analysis of the Reference Rate by noting that “an oversight function is implemented by the Benchmark Administrator in seeking to ensure that the Reference Rate is administered through codified policies for Reference Rate integrity.” 
                    <SU>81</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>75</SU>
                         
                        <E T="03">See</E>
                         Notice, 87 FR at 8333.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>76</SU>
                         According to the Exchange, a “Relevant Transaction” is any cryptocurrency versus U.S. dollar spot trade that occurs during the observation window between 3:00 p.m. and 4:00 p.m. E.T. on a Constituent Bitcon Platform in the BTC/USD pair that is reported and disseminated by a Constituent Bitcoin Platform and observed by the Benchmark Adminstrator. 
                        <E T="03">See id.</E>
                         at 8329 n.78.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>77</SU>
                         
                        <E T="03">See id.</E>
                         at 8329.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>78</SU>
                         
                        <E T="03">See id.</E>
                         According to the Exchange, a volume-weighted median differs from a standard median in that a weighting factor, in this case trade size, is factored into the calculation. 
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>79</SU>
                         
                        <E T="03">See id.</E>
                         at 8330.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>80</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>81</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    In addition, the Exchange states that to qualify as part of the bitcoin pricing input for the Trust, a Constituent Bitcoin Platform must: (a) have policies to ensure fair and transparent market conditions at all times and have processes in place to identify and impede illegal, unfair or manipulative trading practices; and (b) comply with applicable law and regulation, including, but not limited to, capital markets regulations, money transmission regulations, client money custody regulations, know-your-client (“KYC”) regulations and anti-money laundering (“AML”) regulations.
                    <SU>82</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>82</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <P>
                    Simultaneously with its assertions regarding the Reference Rate, BZX also states that, because the Trust will engage in in-kind creations and redemptions only, the “manipulability of the Reference Rate [is] significantly less important.” 
                    <SU>83</SU>
                    <FTREF/>
                     The Exchange elaborates that, “because the Trust will not accept cash to buy bitcoin in order to create new shares or . . . be forced to sell bitcoin to pay cash for redeemed shares, the price that the Sponsor uses to value the Trust's bitcoin is not particularly important.” 
                    <SU>84</SU>
                    <FTREF/>
                     According to BZX, when authorized participants create Shares with the Trust, they would need to deliver a certain number of bitcoin per Share (regardless of the valuation used), and when they redeem with the Trust, they would similarly expect to receive a certain number of bitcoin per Share.
                    <SU>85</SU>
                    <FTREF/>
                     As such, BZX argues that, even if the price used to value the Trust's bitcoin is manipulated, the ratio of bitcoin per Share does not change, and the Trust will either accept (for creations) or distribute (for redemptions) the same number of bitcoin regardless of the value.
                    <SU>86</SU>
                    <FTREF/>
                     This, according to BZX, not only mitigates the risk associated with potential manipulation, but also discourages and disincentivizes manipulation of the Reference Rate because there is little financial incentive to do so.
                    <SU>87</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>83</SU>
                         
                        <E T="03">See id.</E>
                         at 8333.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>84</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>85</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>86</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>87</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(b) Analysis</HD>
                <P>Based on the assertions made and the information provided with respect to the Reference Rate and the create/redeem process, the record is inadequate to conclude that BZX has articulated other means to prevent fraud and manipulation that are sufficient to justify dispensing with the detection and deterrence of fraud and manipulation provided by a comprehensive surveillance-sharing agreement with a regulated market of significant size related to spot bitcoin.</P>
                <P>
                    The record does not demonstrate that the proposed methodology for calculating the Reference Rate would make the proposed ETP resistant to 
                    <PRTPAGE P="62473"/>
                    fraud or manipulation such that the ability to detect and deter fraud and manipulation that is provided by a comprehensive surveillance-sharing agreement with a regulated market of significant size related to spot bitcoin is unnecessary. Specifically, BZX has not assessed the possible influence that spot platforms not included among the Constituent Bitcoin Platforms would have on bitcoin prices used to calculate the Reference Rate.
                    <SU>88</SU>
                    <FTREF/>
                     As discussed above, BZX does not sufficiently contest the presence of possible sources of fraud and manipulation in the spot bitcoin market generally.
                    <SU>89</SU>
                    <FTREF/>
                     Instead, BZX focuses its analysis on the eligibility and attributes of the Constituent Bitcoin Platforms, as well as the Reference Rate's methodology that calibrates the pricing input generated by the Constituent Bitcoin Platforms (such as partitioning the Relevant Transactions into equally-sized time intervals and using volume-weighted median trade prices). What the Exchange does not address, however, is that, to the extent that trading on spot bitcoin platforms not directly used to calculate the Reference Rate affects prices on the Constituent Bitcoin Platforms, the activities on those other platforms—where various kinds of fraud and manipulation from a variety of sources may be present and persist—may affect whether the Reference Rate is resistant to manipulation. Importantly, the record does not demonstrate that these possible sources of fraud and manipulation in the broader spot bitcoin market do not affect the Constituent Bitcoin Platforms that represent a portion of the spot bitcoin market. To the extent that fraudulent and manipulative trading on the broader bitcoin market could influence prices or trading activity on the Constituent Bitcoin Platforms, the Constituent Bitcoin Platforms (and thus the Reference Rate) would not be inherently resistant to manipulation.
                    <SU>90</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>88</SU>
                         As discussed above, while the Exchange asserts that bitcoin prices on platforms with wash trades or other activity intended to manipulate the price of bitcoin would generally be ignored, the Commission has no basis on which to conclude that bitcoin platforms are insulated from prices of others that engage in or permit fraud or manipulation. 
                        <E T="03">See supra</E>
                         note 66 and accompanying text.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>89</SU>
                         
                        <E T="03">See supra</E>
                         notes 65-66 and accompanying text.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>90</SU>
                         
                        <E T="03">See</E>
                         USBT Order, 85 FR at 12601; WisdomTree Order, 86 FR at 69327; Kryptoin Order, 86 FR at 74172; Valkyrie Order, 86 FR at 74161; SkyBridge Order, 87 FR at 3873; Grayscale Order, 87 FR at 40309.
                    </P>
                </FTNT>
                <P>
                    In addition, while BZX asserts that aspects of the Reference Rate methodology mitigate the impact of fraud and manipulation on the Shares, the Commission can find no basis to conclude that the Reference Rate methodology constitutes a novel means beyond the protections utilized by traditional commodity or securities markets to prevent fraud and manipulation that is sufficient to justify dispensing with the detection and deterrence of fraud and manipulation provided by a comprehensive surveillance-sharing agreement with a regulated market of significant size related to spot bitcoin. BZX has not shown that its proposed use of 12 equally-sized time intervals of five minute length over the observation window between 3:00 p.m. and 4:00 p.m. E.T. to calculate the Reference Rate would effectively be able to eliminate fraudulent or manipulative activity that is not transient. As the Commission has previously stated, fraud and manipulation in the spot bitcoin market could persist for a “significant duration.” 
                    <SU>91</SU>
                    <FTREF/>
                     The Exchange does not explain how the use of such partitions would protect against the effects of the wash and fictitious trading that may persist in the spot bitcoin market for a significant duration.
                    <SU>92</SU>
                    <FTREF/>
                     While the Reference Rate methodology records the time of execution, trade price, and size for each Relevant Transaction, partitions the list of Relevant Transactions by timestamp into equally-sized time intervals, and calculates the weighted median trade price from the trade prices and sizes of such Relevant Transactions, this methodology could at most attenuate, but not eliminate, the effect of manipulative activity on the Constituent Bitcoin Platforms—just as it could at most attenuate, but would not eliminate, the effect of bona fide liquidity demand on those platforms.
                    <SU>93</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>91</SU>
                         
                        <E T="03">See</E>
                         USBT Order, 85 FR at 12601 n.66; 
                        <E T="03">see also id.</E>
                         at 12607.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>92</SU>
                         
                        <E T="03">See</E>
                         WisdomTree Order, 86 FR at 69327.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>93</SU>
                         
                        <E T="03">See</E>
                         SolidX Order, 82 FR at 16257.
                    </P>
                </FTNT>
                <P>
                    Moreover, the Exchange's assertions that the Reference Rate's methodology helps make the Reference Rate resistant to manipulation conflict with the Registration Statement. Specifically, the Registration Statement represents, among other things, that “[b]itcoin [platforms] on which bitcoin trades . . . may be more exposed to fraud and security breaches than established, regulated exchanges for other financial assets or instruments, which could have a negative impact on the performance of the Trust.” 
                    <SU>94</SU>
                    <FTREF/>
                     Constituent Bitcoin Platforms are a subset of the bitcoin platforms currently in existence. Although the Sponsor raises concerns regarding fraud and security of bitcoin platforms in the Registration Statement, the Exchange does not explain how or why such concerns are consistent with its assertion that the Reference Rate is resistant to fraud and manipulation.
                </P>
                <FTNT>
                    <P>
                        <SU>94</SU>
                         Registration Statement at 19.
                    </P>
                </FTNT>
                <P>
                    The Commission thus concludes that the Exchange has not demonstrated that its Reference Rate methodology makes the proposed ETP resistant to manipulation. While the proposed procedures for calculating the Reference Rate using only prices from the Constituent Bitcoin Platforms are intended to provide some degree of protection against attempts to manipulate the Reference Rate, these procedures are not sufficient for the Commission to dispense with the detection and deterrence of fraud and manipulation provided by a comprehensive surveillance-sharing agreement with a regulated market of significant size related to spot bitcoin.
                    <SU>95</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>95</SU>
                         
                        <E T="03">See</E>
                         WisdomTree Order, 86 FR at 69327-28.
                    </P>
                </FTNT>
                <P>
                    In addition, while BZX represents that a Constituent Bitcoin Platform must have policies to ensure fair and transparent market conditions at all times and have processes in place to identify and impede illegal, unfair, or manipulative trading practices, and comply with applicable law and regulation, including, but not limited to, capital markets regulations, money transmission regulations, client money custody regulations, KYC regulations and AML regulations, any oversight relating to such policies, processes, and regulations, including KYC and AML regulations, is not a substitute for a surveillance-sharing agreement between the Exchange and a 
                    <E T="03">regulated</E>
                     market of significant size related to the underlying bitcoin assets. KYC and AML regulation, for example, do not substitute for the sharing of information about market trading activity or clearing activity that a surveillance-sharing agreement would afford. As the Commission has explained, there are substantial differences between such regulations and the Commission's regulation of national securities exchanges.
                    <SU>96</SU>
                    <FTREF/>
                     For example, the Commission's market oversight of national securities exchanges includes substantial requirements, including the requirement to have rules that are “designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to foster cooperation and coordination with 
                    <PRTPAGE P="62474"/>
                    persons engaged in regulating, clearing, settling, processing information with respect to, and facilitating transactions in securities, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and, in general, to protect investors and the public interest.” 
                    <SU>97</SU>
                    <FTREF/>
                     Moreover, national securities exchanges must file proposed rules with the Commission regarding certain material aspects of their operations,
                    <SU>98</SU>
                    <FTREF/>
                     and the Commission has the authority to disapprove any such rule that is not consistent with the requirements of the Exchange Act.
                    <SU>99</SU>
                    <FTREF/>
                     Thus, national securities exchanges are subject to Commission oversight of, among other things, their governance, membership qualifications, trading rules, disciplinary procedures, recordkeeping, and fees.
                    <SU>100</SU>
                    <FTREF/>
                     The Constituent Bitcoin Platforms have none of these requirements—none are registered as a national securities exchange and none are comparable to a national securities exchange or futures exchange.
                    <SU>101</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>96</SU>
                         KYC and AML regulation have been referenced in other bitcoin-based ETP proposals as a purportedly alternative means by which such ETPs would be uniquely resistant to manipulation. 
                        <E T="03">See</E>
                         USBT Order, 85 FR at 12603 n.101 and accompanying text. 
                        <E T="03">See also, e.g.,</E>
                         WisdomTree Order, 86 FR at 69328 n.95; Kryptoin Order, 86 FR at 74173 n.98; ARK 21Shares Order, 87 FR at 20022 n.107; Grayscale Order, 87 FR at 40308 n.111.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>97</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>98</SU>
                         17 CFR 240.19b-4(a)(6)(i).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>99</SU>
                         Section 6 of the Exchange Act, 15 U.S.C. 78f, requires national securities exchanges to register with the Commission and requires an exchange's registration to be approved by the Commission, and Section 19(b) of the Exchange Act, 15 U.S.C. 78s(b), requires national securities exchanges to file proposed rule changes with the Commission and provides the Commission with the authority to disapprove proposed rule changes that are not consistent with the Exchange Act. Designated contract markets (“DCMs”) (commonly called “futures markets”) registered with and regulated by the CFTC must comply with, among other things, a similarly comprehensive range of regulatory principles and must file rule changes with the CFTC. 
                        <E T="03">See, e.g.,</E>
                         Designated Contract Markets (DCMs), CFTC, 
                        <E T="03">available at http://www.cftc.gov/IndustryOversight/TradingOrganizations/DCMs/index.htm.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>100</SU>
                         
                        <E T="03">See</E>
                         Winklevoss Order, 83 FR at 37597.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>101</SU>
                         
                        <E T="03">See</E>
                         USBT Order, 85 FR at 12603-05 and n.101; VanEck Order, 86 FR at 64545 and n.89; WisdomTree Order, 86 FR at 69328 and n.95; Kryptoin Order, 86 FR at 74173 and n.98; ARK 21Shares Order, 87 FR at 20021-22 and n.107; Grayscale Order, 87 FR at 40308 and n.110.
                    </P>
                </FTNT>
                <P>
                    In addition, the Exchange states that the Benchmark Administrator would implement an oversight function to ensure that the Reference Rate is administered through codified policies for Reference Rate integrity.
                    <SU>102</SU>
                    <FTREF/>
                     However, the record does not suggest that the purported oversight represents a unique measure to resist or prevent fraud or manipulation beyond protections that exist in traditional securities or commodities markets.
                    <SU>103</SU>
                    <FTREF/>
                     Rather, the oversight performed by the Benchmark Administrator appears to be for the purpose of ensuring the accuracy and integrity of the Reference Rate. Such Reference Rate accuracy and integrity oversight serves a fundamentally different purpose as compared to the regulation of national securities exchanges and the requirements of the Exchange Act. While the Commission recognizes that this may be an important function in ensuring the integrity of the Reference Rate, such requirements do not imbue the Benchmark Administrator with regulatory authority similar to that which the Exchange Act confers upon self-regulatory organizations such as national securities exchanges.
                    <SU>104</SU>
                    <FTREF/>
                     Furthermore, other commodity-based ETPs approved by the Commission for listing and trading utilize reference rates or indices administered by similar benchmark administrators,
                    <SU>105</SU>
                    <FTREF/>
                     and the Commission has not, in those instances, dispensed with the need for a surveillance-sharing agreement with a significant regulated market.
                </P>
                <FTNT>
                    <P>
                        <SU>102</SU>
                         
                        <E T="03">See supra</E>
                         note 81 and accompanying text.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>103</SU>
                         
                        <E T="03">See, e.g.,</E>
                         WisdomTree Order, 86 FR at 69328; Valkyrie Order, 86 FR at 74162.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>104</SU>
                         
                        <E T="03">See</E>
                         WisdomTree Order, 86 FR at 69329; One River Order, 87 FR at 33556; Grayscale Order, 87 FR at 40310. The Benchmark Administrator does not itself exercise governmental regulatory authority. Rather, the Benchmark Administrator is a registered, privately-held company in England. 
                        <E T="03">See https://blog.cfbenchmarks.com/legal/</E>
                         (stating that the Benchmark Administrator is authorized and regulated by the UK Financial Conduct Authority (“FCA”) as a registered Benchmark Administrator (FRN 847100) under the EU benchmark regulation, and further noting that the Benchmark Administrator is a member of the Crypto Research group of companies which is in turn a member of the Payward, Inc. group of companies, and Payward, Inc. is the owner and operator of the Kraken Exchange, a venue that facilitates the trading of cryptocurrencies). The Benchmark Administrator's relationship with the Constituent Bitcoin Platforms is based on such platforms' participation in the determination of reference rates, such as the Reference Rate. While the Benchmark Administrator is regulated by the FCA as a benchmark administrator, the FCA's regulations do not extend to the Constituent Bitcoin Platforms by virtue of their trade prices serving as input data underlying the Reference Rate. 
                        <E T="03">See</E>
                         USBT Order, 85 FR at 12604. 
                        <E T="03">See also</E>
                         WisdomTree Order, 86 FR at 69328-29.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>105</SU>
                         
                        <E T="03">See, e.g.,</E>
                         Securities Exchange Act Release Nos. 80840 (June 1, 2017) 82 FR 26534 (June 7, 2017) (SR-NYSEArca-2017-33) (approving the listing and trading of shares of certain trusts seeking to track the Solactive GLD EUR Gold Index, Solactive GLD GBP Gold Index, and the Solactive GLD JPY Gold Index).
                    </P>
                </FTNT>
                <P>
                    Further, BZX does not explain the significance of the Reference Rate's purported resistance to manipulation to the overall analysis of whether the proposal to list and trade the Shares is designed to prevent fraud and manipulation.
                    <SU>106</SU>
                    <FTREF/>
                     To the extent that BZX's argument is that the price of the Trust's Shares would be resistant to manipulation if the Reference Rate is resistant to manipulation, BZX has not established in the record a basis for this conclusion because BZX has not established a link between the price of the Shares and the Reference Rate, either in the primary or secondary market. The Trust uses the Reference Rate to calculate the value of the bitcoin it holds according to the methodology discussed above.
                    <SU>107</SU>
                    <FTREF/>
                     However, the Trust will create or redeem baskets in the primary market only upon the receipt or distribution of bitcoins from/to authorized participants, and only for the amount of bitcoin represented by the Shares in such baskets, 
                    <E T="03">without</E>
                     reference to the value of such bitcoin as determined by the Reference Rate or otherwise.
                    <SU>108</SU>
                    <FTREF/>
                     In the secondary market, the Shares would trade at market-based prices, and market partcipants may or may not take into account the value of bitcoin as measured by the Reference Rate in determining such prices. The Exchange provides no information on the relationship between the Reference Rate and secondary market prices generally, or how the use of the Reference Rate would mitigate fraud and manipulation of the Shares in the secondary market.
                    <SU>109</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>106</SU>
                         The Commission has previously considered and rejected similar arguments about the valuation of bitcoin according to a benchmark or reference price. 
                        <E T="03">See, e.g.,</E>
                         SolidX Order, 82 FR at 16258; Winklevoss Order, 83 FR at 37587-90; USBT Order, 85 FR at 12599-601; WisdomTree Order, 86 FR at 69327-29;Valkyrie Order, 86 FR at 74162; ARK 21Shares Order, 87 FR at 20022; Grayscale Order, 87 FR at 40310.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>107</SU>
                         
                        <E T="03">See supra</E>
                         notes 32-36 and accompanying text.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>108</SU>
                         
                        <E T="03">See</E>
                         Notice, 87 FR at 8330. According to the Exchange, to create, “the total deposit of bitcoin required is an amount of bitcoin that is in the same proportion to the total assets of the Trust, net of accrued expenses and other liabilities, on the date the order to purchase is properly received, as the number of Shares to be created under the purchase order is in proportion to the total number of Shares outstanding on the date the order is received.” The required deposit is determined “for a given day by dividing the number of bitcoin held by the Trust as of the opening of business on that business day, adjusted for the amount of bitcoin constituting estimated accrued but unpaid fees and expenses of the Trust as of the opening of business on that business day, by the quotient of the number of Shares outstanding at the opening of business divided by the aggregation of shares (
                        <E T="03">i.e.,</E>
                         50,000) associated with a creation unit.”
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>109</SU>
                         
                        <E T="03">See</E>
                         WisdomTree Order, 86 FR at 69329 and n.108; Valkyrie Order, 86 FR at 74162; ARK 21Shares Order, 87 FR at 20022; Grayscale Order, 87 FR at 40310.
                    </P>
                </FTNT>
                <P>
                    Moreover, the Exchange's arguments are contradictory. While arguing that the Reference Rate is resistant to manipulation, the Exchange simultaneously downplays the importance of the Reference Rate in light of the Trust's in-kind creation and redemption mechanism.
                    <SU>110</SU>
                    <FTREF/>
                     The Exchange points out that the Trust will create and redeem Shares in-kind, not in cash, which renders the NAV calculation, and thereby the ability to manipulate NAV, “significantly less 
                    <PRTPAGE P="62475"/>
                    important.” 
                    <SU>111</SU>
                    <FTREF/>
                     In BZX's own words, the Trust will not accept cash to buy bitcoin in order to create shares or sell bitcoin to pay cash for redeemed shares, so the price that the Sponsor uses to value the Trust's bitcoin “is not particularly important.” 
                    <SU>112</SU>
                    <FTREF/>
                     If the Reference Rate that the Trust uses to value the Trust's bitcoin “is not particularly important,” it follows that the Reference Rate's resistance to manipulation is not material to the Shares' susceptibility to fraud and manipulation. As the Exchange does not address or provide any analysis with respect to these issues, the Commission cannot conclude that the Reference Rate aids in the determination that the proposal to list and trade the Shares is designed to prevent fraudulent and manipulative acts and practices.
                    <SU>113</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>110</SU>
                         
                        <E T="03">See supra</E>
                         notes 83-84 and accompanying text.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>111</SU>
                         Notice, 87 FR at 8333 (“While the Sponsor believes that the Reference Rate which it uses to value the Trust's bitcoin is itself resistant to manipulation based on the methodology further described below, the fact that creations and redemptions are only available in-kind makes the manipulability of the Reference Rate significantly less important.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>112</SU>
                         
                        <E T="03">Id.</E>
                         (concluding that “because the Trust will not accept cash to buy bitcoin in order to create new shares or, barring a forced redemption of the Trust or under other extraordinary circumstances, be forced to sell bitcoin to pay cash for redeemed shares, the price that the Sponsor uses to value the Trust's bitcoin is not particularly important.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>113</SU>
                         
                        <E T="03">See</E>
                         WisdomTree Order, 86 FR at 69329.
                    </P>
                </FTNT>
                <P>
                    Finally, the Commission finds that BZX has not demonstrated that in-kind creations and redemptions provide the Shares with a unique resistance to manipulation. The Commission has previously addressed similar assertions.
                    <SU>114</SU>
                    <FTREF/>
                     As the Commission stated before, in-kind creations and redemptions are a common feature of ETPs, and the Commission has not previously relied on the in-kind creation and redemption mechanism as a basis for excusing exchanges that list ETPs from entering into surveillance-sharing agreements with significant, regulated markets related to the portfolio's assets.
                    <SU>115</SU>
                    <FTREF/>
                     Accordingly, the Commission is not persuaded here that the Trust's in-kind creations and redemptions afford it a unique resistance to manipulation.
                    <SU>116</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>114</SU>
                         
                        <E T="03">See</E>
                         Winklevoss Order, 83 FR at 37589-90; USBT Order, 85 FR at 12607-08; WisdomTree Order, 86 FR at 69329.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>115</SU>
                         
                        <E T="03">See, e.g.,</E>
                         iShares COMEX Gold Trust, Securities Exchange Act Release No. 51058 (Jan. 19, 2005), 70 FR 3749, 3751-55 (Jan. 26, 2005) (SR-Amex-2004-38); iShares Silver Trust, Securities Exchange Act Release No. 53521 (Mar. 20, 2006), 71 FR 14969, 14974 (Mar. 24, 2006) (SR-Amex-2005-072).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>116</SU>
                         Putting aside the Exchange's various assertions about the nature of bitcoin and the bitcoin market, the Reference Rate, and the Shares, the Exchange also does not address concerns the Commission has previously identified, including the susceptibility of bitcoin markets to potential trading on material, non-public information (such as plans of market participants to significantly increase or decrease their holdings in bitcoin; new sources of demand for bitcoin; the decision of a bitcoin-based investment vehicle on how to respond to a “fork” in the bitcoin blockchain, which would create two different, non-interchangeable types of bitcoin), or to the dissemination of false or misleading information. 
                        <E T="03">See</E>
                         Winklevoss Order, 83 FR at 37585. 
                        <E T="03">See also</E>
                         USBT Order, 85 FR at 12600-01.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(2) Assertions That BZX Has Entered Into a Comprehensive Surveillance-Sharing Agreement With a Regulated Market of Significant Size Related to the Underlying Bitcoin Assets</HD>
                <P>
                    As BZX has not demonstrated that other means besides surveillance-sharing agreements will be sufficient to prevent fraudulent and manipulative acts and practices, the Commission next examines whether the record supports the conclusion that BZX has entered into a comprehensive surveillance-sharing agreement with a regulated market of significant size related to the underlying bitcoin assets. In this context, the term “market of significant size” includes a market (or group of markets) as to which (i) there is a reasonable likelihood that a person attempting to manipulate the ETP would also have to trade on that market to successfully manipulate the ETP, so that a surveillance-sharing agreement would assist in detecting and deterring misconduct, and (ii) it is unlikely that trading in the ETP would be the predominant influence on prices in that market.
                    <SU>117</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>117</SU>
                         
                        <E T="03">See</E>
                         Winklevoss Order, 83 FR at 37594.
                    </P>
                </FTNT>
                <P>
                    As the Commission has explained, it considers two markets that are members of the ISG to have a comprehensive surveillance-sharing agreement with one another, even if they do not have a separate bilateral surveillance-sharing agreement.
                    <SU>118</SU>
                    <FTREF/>
                     Accordingly, based on the common membership of BZX and the CME in the ISG,
                    <SU>119</SU>
                    <FTREF/>
                     BZX has the equivalent of a comprehensive surveillance-sharing agreement with the CME. However, while the Commission recognizes that the CFTC regulates the CME futures market,
                    <SU>120</SU>
                    <FTREF/>
                     including the CME bitcoin futures market, and thus such market is “regulated,” in the context of the proposed ETP, the record does not, as explained further below, establish that the CME bitcoin futures market is a “market of significant size” related to spot bitcoin, the underlying bitcoin assets that would be held by the Trust.
                </P>
                <FTNT>
                    <P>
                        <SU>118</SU>
                         
                        <E T="03">See id.</E>
                         at 37580 n.19.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>119</SU>
                         
                        <E T="03">See</E>
                         Notice, 87 FR at 8328, 8333.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>120</SU>
                         While the Commission recognizes that the CFTC regulates the CME, the CFTC is not responsible for direct, comprehensive regulation of the underlying spot bitcoin market. 
                        <E T="03">See</E>
                         Winklevoss Order, 83 FR at 37587, 37599. 
                        <E T="03">See also</E>
                         WisdomTree Order, 86 FR at 69330 n.118; Kryptoin Order, 86 FR at 74174 n.119; SkyBridge Order, 87 FR at 3874 n.80; Wise Origin Order, 87 FR at 5534 n.93; ARK 21Shares Order, 87 FR at 20023 n.121; Bitwise Order, 87 FR at 40286 n.54; Grayscale Order, 87 FR at 40311 n.138.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(i) Whether There is a Reasonable Likelihood That a Person Attempting To Manipulate the ETP Would Also Have To Trade on the CME Bitcoin Futures Market to Successfully Manipulate the ETP</HD>
                <P>
                    The first prong in establishing whether the CME bitcoin futures market constitutes a “market of significant size” related to spot bitcoin is the determination that there is a reasonable likelihood that a person attempting to manipulate the ETP would have to trade on the CME bitcoin futures market to successfully manipulate the ETP. In previous Commission orders, the Commission explained that the lead-lag relationship between the bitcoin futures market and the spot market is “central” to understanding this first prong.
                    <SU>121</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>121</SU>
                         
                        <E T="03">See, e.g.,</E>
                         USBT Order, 85 FR at 12612 (“[E]stablishing a lead-lag relationship between the bitcoin futures market and the spot market is central to understanding whether it is reasonably likely that a would-be manipulator of the ETP would need to trade on the bitcoin futures market to successfully manipulate prices on those spot platforms that feed into the proposed ETP's pricing mechanism. In particular, if the spot market leads the futures market, this would indicate that it would not be necessary to trade on the futures market to manipulate the proposed ETP, even if arbitrage worked efficiently, because the futures price would move to meet the spot price.”). When considering past proposals for spot bitcoin ETPs, the Commission has discussed whether there is a lead-lag relationship between the regulated market (
                        <E T="03">e.g.,</E>
                         the CME) and the market on which the assets held by the ETP would have traded (
                        <E T="03">i.e.,</E>
                         spot bitcoin platforms), as part of an analysis of whether a would-be manipulator of the spot bitcoin ETP would need to trade on the regulated market to effect such manipulation. 
                        <E T="03">See, e.g.,</E>
                         USBT Order, 85 FR at 12612. 
                        <E T="03">See also</E>
                         VanEck Order, 86 FR at 64547; WisdomTree Order, 86 FR at 69330-31; Kryptoin Order, 86 FR at 74175-76; SkyBridge Order, 87 FR at 3875-76; Wise Origin Order, 87 FR at 5535-36, 5539-40; ARK 21Shares Order, 87 FR at 20023-24; Bitwise Order, 87 FR at 40287-89; Grayscale Order, 87 FR at 40311-13.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(a) BZX's Assertions</HD>
                <P>
                    The Exchange asserts in its proposal that the significant growth in CME bitcoin futures across each of trading volumes, open interest, large open interest holders, and total market participants over the last two years are reflective of that market's growing influence on the spot price.
                    <SU>122</SU>
                    <FTREF/>
                     The Exchange represents that, from October 25, 2021, through November 19, 2021, CFTC-regulated bitcoin futures represented approximately $2.9 billion in notional trading volume on CME on a daily basis, and notional volume was 
                    <PRTPAGE P="62476"/>
                    never below $1.2 billion per day.
                    <SU>123</SU>
                    <FTREF/>
                     The Exchange also represents that “[o]pen interest was over $4 billion for the entirety of the period and at one point reached $5.5 billion.” 
                    <SU>124</SU>
                    <FTREF/>
                     BZX further asserts that “[n]early every measurable metric related to CME Bitcoin Futures has trended consistently up since launch and/or accelerated upward in the past year.” 
                    <SU>125</SU>
                    <FTREF/>
                     As an example, the Exchange states that “there was approximately $12 billion in trading in Bitcoin Futures in August 2021 compared to $3.9 billion, $4.5[] billion, and $9[ ] billion in total trading in August 2017, August 2018, and August 2019, respectively.” 
                    <SU>126</SU>
                    <FTREF/>
                     The Exchange states that “Bitcoin Futures traded over $500m and represented $1.5 billion in open interest compared to $115 million in December 2019.” 
                    <SU>127</SU>
                    <FTREF/>
                     BZX also asserts that the number of large open interest holders 
                    <SU>128</SU>
                    <FTREF/>
                     “has continued to increase even as the price of bitcoin has risen, as have the number of unique accounts trading Bitcoin Futures.” 
                    <SU>129</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>122</SU>
                         
                        <E T="03">See</E>
                         Notice, 87 FR at 8328, 8333.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>123</SU>
                         
                        <E T="03">See id.</E>
                         at 8321.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>124</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>125</SU>
                         
                        <E T="03">Id.</E>
                         at 8325.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>126</SU>
                         
                        <E T="03">Id.</E>
                         The Exchange does not define the term “Bitcoin Futures” in its filing.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>127</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>128</SU>
                         The Exchange states that a “large open interest holder in Bitcoin Futures is an entity that holds at least 25 contracts, which is the equivalent of 125 bitcoin. At a price of approximately $46,996 per bitcoin on 8/31/21, more than 80 firms had outstanding positions of greater than $5.8 million in Bitcoin Futures.” 
                        <E T="03">Id.</E>
                         at 8326 n.61.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>129</SU>
                         
                        <E T="03">Id.</E>
                         at 8326.
                    </P>
                </FTNT>
                <P>
                    Moreover, acording to the Exchange, the Sponsor believes that “academic research corroborates this overall trend and supports the thesis that bitcoin futures, and more particularly CME [b]itcoin [f]utures[,] given the recent significant growth in that market, is a predominant influence in bitcoin price formation.” 
                    <SU>130</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>130</SU>
                         
                        <E T="03">Id.</E>
                         at 8327 (citing to (a) representations made and comments submitted with respect to the proposed rule changes in connection with the ARK 21Shares Order and the Wise Origin Order, and (b) Hu, Y., Hou, Y. and Oxley, L. (2019), “What role do futures markets play in Bitcoin pricing? Causality, cointegration and price discovery from a time-varying perspective” (
                        <E T="03">available at: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7481826/</E>
                        ) (“Hu, Hou &amp; Oxley”)). The Exchange references the following conclusion from the “time-varying price discovery” section of Hu, Hou &amp; Oxley: “There exist no episodes where the Bitcoin spot markets dominates the price discovery processes with regard to Bitcoin futures. This points to a conclusion that the price formation originates solely in the Bitcoin futures market. We can, therefore, conclude that the Bitcoin futures markets dominate the dynamic price discovery process based upon time-varying information share measures. Overall, price discovery seems to occur in the Bitcoin futures markets rather than the underlying spot market based upon a time-varying perspective.” 
                        <E T="03">Id.</E>
                         at n.62
                    </P>
                </FTNT>
                <P>
                    BZX also contends that “[w]here CME [b]itcoin [f]utures act as a predominant influence on the price in the spot market, such that a potential manipulator of the bitcoin spot market (beyond just the constituents of the Reference Rate) would have to participate in the CME [b]itcoin [f]utures market, it follows that a potential manipulator of the Shares would similarly have to transact in the CME [b]itcoin [f]utures market because the Reference Rate is based on spot prices.” 
                    <SU>131</SU>
                    <FTREF/>
                     Further, BZX asserts that “the Trust only allows for in-kind creation and redemption, which . . . reduces the potential for manipulation of the Shares through manipulation of the Reference Rate or any of its individual constituents, again emphasizing that a potential manipulator of the Shares would have to manipulate the entirety of the bitcoin spot market, of which the CME [b]itcoin [f]utures market appears to be a predominant influence.” 
                    <SU>132</SU>
                    <FTREF/>
                     As such, the Exchange believes that the first prong of the significant market test is satisfied and that common membership in ISG between the Exchange and CME would assist the listing exchange in detecting and deterring misconduct in the Shares.
                    <SU>133</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>131</SU>
                         
                        <E T="03">Id.</E>
                         at 8328, 8333.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>132</SU>
                         
                        <E T="03">Id.</E>
                         at 8328.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>133</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(b) Analysis</HD>
                <P>
                    The record does not demonstrate that there is a reasonable likelihood that a person attempting to manipulate the proposed ETP would have to trade on the CME bitcoin futures market to successfully manipulate the proposed ETP. Specifically, BZX's assertions about the general upward trends in trading volume and open interest of, and in the number of large open interest holders and number of unique accounts trading in, CME bitcoin futures do not establish that the CME bitcoin futures market is of significant size.
                    <SU>134</SU>
                    <FTREF/>
                     While BZX provides data showing 
                    <E T="03">absolute</E>
                     growth in the size of the CME bitcoin futures market, it provides no data 
                    <E T="03">relative</E>
                     to the concomitant growth in either the spot bitcoin markets or other bitcoin futures markets (including unregulated futures markets). Moreover, even if the CME has grown in relative size, as the Commission has previously articulated, including in the WisdomTree Order, the interpretation of the term “market of significant size” or “significant market” depends on the interrelationship between the market with which the listing exchange has a surveillance-sharing agreement and the proposed ETP.
                    <SU>135</SU>
                    <FTREF/>
                     BZX's recitation of data reflecting the size of the CME bitcoin futures market, alone, either currently or in relation to previous years, is not sufficient to establish an interrelationship between the CME bitcoin futures market and the proposed ETP.
                    <SU>136</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>134</SU>
                         
                        <E T="03">See</E>
                         WisdomTree Order, 86 FR at 69330.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>135</SU>
                         
                        <E T="03">See</E>
                         USBT Order, 85 FR at 12611. 
                        <E T="03">See also</E>
                         WisdomTree Order, 86 FR at 69330; Kryptoin Order, 86 FR at 74175; SkyBridge Order, 87 FR at 3875; Wise Origin Order, 87 FR at 5534.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>136</SU>
                         
                        <E T="03">See</E>
                         USBT Order, 85 FR at 12612. The Commission has previously considered and rejected similar arguments. 
                        <E T="03">See, e.g.,</E>
                         VanEck Order, 86 FR at 64547; WisdomTree Order, 86 FR at 69330; Kryptoin Order, 86 FR at 74175-76; SkyBridge Order, 87 FR at 3875-76; Wise Origin Order, 87 FR at 5534-35; Global X Order, 87 FR at 14919; Grayscale Order, 87 FR at 40312.
                    </P>
                </FTNT>
                <P>
                    In addition, the econometric evidence in the record for the proposal does not support the conclusion that an interrelationship exists between the CME bitcoin futures market and the spot bitcoin market such that it is reasonably likely that a person attempting to manipulate the proposed ETP would also have to trade on the CME bitcoin futures market.
                    <SU>137</SU>
                    <FTREF/>
                     The Exchange and the Sponsor, as they have done previously, rely on the findings of one section of the Hu, Hou &amp; Oxley paper; 
                    <SU>138</SU>
                    <FTREF/>
                     however, they do not address issues that the Commission has previously raised, including in the WisdomTree Order, with respect to this paper.
                    <SU>139</SU>
                    <FTREF/>
                     As the Commission explained in the WisdomTree Order, the findings of this paper's Granger causality analysis, which is widely used to formally test for lead-lag relationships, are concededly mixed.
                    <SU>140</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>137</SU>
                         
                        <E T="03">See also</E>
                         USBT Order, 85 FR at 12611; WisdomTree Order, 86 FR at 69330-31; Wise Origin Order, 87 FR at 5535; NYDIG Order, 87 FR at 14938; Global X Order, 87 FR at 14920; ARK 21Shares, 87 FR at 20024; Bitwise Order, 87 FR at 40288-89; Grayscale Order, 87 FR at 40312-13.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>138</SU>
                         
                        <E T="03">See supra</E>
                         note 130.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>139</SU>
                         
                        <E T="03">See, e.g.,</E>
                         WisdomTree Order, 86 FR at 69331 (discussing that the paper's use of daily price data, as opposed to intraday prices may not be able to distinguish which market incorporates new information faster; and discussing that the paper found inconclusive evidence that futures prices lead spot bitcoin prices—in particular, that the months at the end of the paper's sample period showed, using Granger causality methodology, that the spot market was the leading market—and that the record did not include evidence to explain why this would not indicate a shift towards prices in the spot market leading the futures market that would be expected to persist into the future). 
                        <E T="03">See also</E>
                         USBT Order, 85 FR at 12613 n.244.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>140</SU>
                         The paper finds that the CME bitcoin futures market dominates the spot markets in terms of Granger causality, but that the causal relationship is bi-directional, and a Granger causality episode from March 2019 to June/July 2019 runs from bitcoin spot prices to CME bitcoin futures prices. The paper concludes: “[T]he Granger causality episodes are not constant throughout the whole sample period. Via our causality detection methods, market participants can identify when markets are being led by futures prices and when they might not 
                        <PRTPAGE/>
                        be.” 
                        <E T="03">See</E>
                         Hu, Hou &amp; Oxley, 
                        <E T="03">supra</E>
                         note 130. 
                        <E T="03">See also</E>
                         WisdomTree Order, 86 FR at 69331.
                    </P>
                </FTNT>
                <PRTPAGE P="62477"/>
                <P>
                    Moreover, while the Exchange highlights data and analyses submitted to the Commission in connection with the Wise Origin Order and the ARK 21Shares Order to support the premise that the CME bitcoin futures market leads the spot bitcoin market,
                    <SU>141</SU>
                    <FTREF/>
                     the Commission disapproved the proposals related to these submissions, and the Commission raised issues with respect to these submissions—including with the data and analyses therein—that the Exchange does not address.
                    <SU>142</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>141</SU>
                         
                        <E T="03">See supra</E>
                         note
                        <E T="03"> 130 and accompanying text.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>142</SU>
                         
                        <E T="03">See, e.g.,</E>
                         Wise Origin Order, 87 FR at 5534-36, 5539-40; ARK 21Shares Order, 87 FR at 20023-24.
                    </P>
                </FTNT>
                <P>
                    The Exchange does not provide results of its own lead-lag analysis or provide any additional evidence of an interrelationship between the CME bitcoin futures market, which is the regulated market, and spot bitcoin platforms, which are the markets on which the assets held by the proposed ETP would trade. As discussed in previous disapprovals, including the WisdomTree Order, analyses regarding whether the CME bitcoin futures market leads the spot market remain inconclusive.
                    <SU>143</SU>
                    <FTREF/>
                     Thus, as in previous disapprovals, because the lead-lag analysis regarding whether the CME bitcoin futures market leads the spot market is “central” to understanding the first prong, the Commission determines that the evidence in the record is inadequate to conclude that an interrelationship exists between the CME bitcoin futures market and the spot bitcoin market such that it is reasonably likely that a person attempting to manipulate the proposed ETP would have to trade on the CME bitcoin futures market to successfully manipulate the proposed ETP.
                </P>
                <FTNT>
                    <P>
                        <SU>143</SU>
                         As the academic literature and listing exchanges' analyses pertaining to the pricing relationship between the CME bitcoin futures market and spot bitcoin market have developed, the Commission has critically reviewed those materials. 
                        <E T="03">See</E>
                         Grayscale Order, 87 FR at 40311-13; Bitwise Order, 87 FR at 40286-89; ARK 21Shares Order, 87 FR at 20024; Global X Order, 87 FR at 14920; Wise Origin Order, 87 FR at 5535-36, 5539-40; Kryptoin Order, 86 FR at 74176; WisdomTree Order, 86 FR at 69330-32; VanEck Order, 86 FR at 64547-48; USBT Order, 85 FR at 12613.
                    </P>
                </FTNT>
                <P>
                    The Exchange also makes additional assertions 
                    <SU>144</SU>
                    <FTREF/>
                     that are conclusory and presuppose that the CME bitcoin futures market is a “predominant influence” on the spot bitcoin market. For example, the Exchange's assertion that “a potential manipulator of the Shares would . . . have to transact in the CME [b]itcoin [f]utures market because the Reference Rate is based on spot prices” 
                    <SU>145</SU>
                    <FTREF/>
                     presupposes that “CME [b]itcoin [f]utures act as a predominant influence on the price in the spot market” 
                    <SU>146</SU>
                    <FTREF/>
                     and assumes a link between the Reference Rate and the Shares that, as discussed above,
                    <SU>147</SU>
                    <FTREF/>
                     the Exchange has not established. Likewise, the Exchange states that the Trust's in-kind create/redeem process supports the conclusion that a would-be manipulator would have to trade on the CME bitcoin futures market to successfully manipulate the proposed ETP because the “CME [b]itcoin [f]utures market appears to be a predominant influence” on the spot bitcoin market.
                    <SU>148</SU>
                    <FTREF/>
                     However, as discussed already, the evidence in the record is inadequate to conclude that CME bitcoin futures prices lead spot bitcoin prices, let alone the premise that the CME bitcoin futures market has a “predominant influence” on the spot bitcoin market.
                </P>
                <FTNT>
                    <P>
                        <SU>144</SU>
                         
                        <E T="03">See supra</E>
                         notes 131-132.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>145</SU>
                         Notice, 87 FR at 8328, 8333.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>146</SU>
                         Notice, 87 FR at 8333.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>147</SU>
                         
                        <E T="03">See supra</E>
                         notes 106-109 and accompanying text.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>148</SU>
                         Notice, 87 FR at 8328 (“the Trust only allows for in-kind creation and redemption, which . . . reduces the potential for manipulation of the Shares through manipulation of the Reference Rate or any of its individual constituents, again emphasizing that a potential manipulator of the Shares would have to manipulate the entirety of the bitcoin spot market, of which the CME [b]itcoin [f]utures market appears to be a predominant influence”).
                    </P>
                </FTNT>
                <P>The Commission thus concludes that the information that BZX provides is not sufficient to support a determination that it is reasonably likely that a would-be manipulator of the proposed ETP would have to trade on the CME bitcoin futures market to successfully manipulate the proposed ETP. Therefore, the information in the record also does not establish that the CME bitcoin futures market is a “market of significant size” related to the assets to be held by the proposed ETP.</P>
                <HD SOURCE="HD3">(ii) Whether It is Unlikely That Trading in the Proposed ETP Would Be the Predominant Influence on Prices in the CME Bitcoin Futures Market</HD>
                <P>
                    The second prong in establishing whether the CME bitcoin futures market constitutes a “market of significant size” related to spot bitcoin is the determination that it is unlikely that trading in the proposed ETP would be the predominant influence on prices in the CME bitcoin futures market.
                    <SU>149</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>149</SU>
                         
                        <E T="03">See</E>
                         Winklevoss Order, 83 FR at 37594; USBT Order, 85 FR at 12596-97.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(a) BZX's Assertions</HD>
                <P>
                    BZX asserts that “trading in the Shares would not be the predominant force on prices in the CME [b]itcoin [f]utures market (or spot market) for a number of reasons, including the significant volume in the CME [b]itcoin [f]utures market, the size of bitcoin's market cap, and the significant liquidity available in the spot market.” 
                    <SU>150</SU>
                    <FTREF/>
                     Moreover, BZX asserts that “the Shares should trade close to NAV given that market participants would arbitrage any significant price deviations between the price of the Shares and prices in the spot market.” 
                    <SU>151</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>150</SU>
                         Notice, 87 FR at 8328, 8333.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>151</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    In addition to the CME bitcoin futures market data points cited above, BZX represents that “the spot market for bitcoin is also very liquid.” 
                    <SU>152</SU>
                    <FTREF/>
                     According to the Exchange, based on data from February 2021, the cost to buy or sell $5 million worth of bitcoin averages roughly 10 basis points with a market impact of 30 basis points.
                    <SU>153</SU>
                    <FTREF/>
                     According to the Exchange, based on the same data, the cost to buy or sell a $10 million market order of bitcoin “is roughly 20 basis points with a market impact of 50 basis points.” 
                    <SU>154</SU>
                    <FTREF/>
                     According to the Exchange “[s]tated another way, a market participant could enter a market buy or sell order for $10 million of bitcoin and only move the market 0.5%.” 
                    <SU>155</SU>
                    <FTREF/>
                     As such, BZX concludes that “the combination of CME [b]itcoin [f]utures acting as a predominant influence on price discovery, the overall size of the bitcoin market, and the ability for market participants, including authorized participants creating and redeeming in-kind with the Trust, to buy or sell large amounts of bitcoin without significant market impact will help prevent the Shares from becoming the predominant force on pricing in either the bitcoin spot or CME [b]itcoin [f]utures markets.” 
                    <SU>156</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>152</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>153</SU>
                         These statistics are sourced from CoinRoutes from February 2021 and are based on samples of bitcoin liquidity in USD (excluding stablecoins or Euro liquidity) based on executable quotes on Coinbase Pro, Gemini, Bitstamp, Kraken, LMAX Exchange, BinanceUS, and OKCoin during February 2021. 
                        <E T="03">See</E>
                         Notice, 87 FR at 8328-29 nn.74-75.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>154</SU>
                         Notice, 87 FR at 8328.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>155</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>156</SU>
                         
                        <E T="03">Id.</E>
                         In addition, the Exchange states that the largest bitcoin futures ETF represents 3,803 contracts of the total 9,625 contracts of open interest in December CME bitcoin futures as of December 2, 2021, (roughly 40% of open interest) and that this directly contradicts the previously articulated standards by the Commission in the disapproval orders issued for spot bitcoin ETPs related to whether the trading in the ETP would be the predominant influence on prices in that market. 
                        <E T="03">See id.</E>
                         at 8324. The Commission disagrees. The proposed rule change does not relate to the same underlying holdings as such ETFs, which provide exposure to bitcoin through CME bitcoin futures. The Commission considers the proposed rule change on its own merits and under the standards 
                        <PRTPAGE/>
                        applicable to it. Namely, with respect to this proposed rule change, the Commission must apply the standards as provided by Section 6(b)(5) of the Exchange Act, which it has applied in connection with its orders considering previous proposals to list bitcoin-based commodity trusts and bitcoin-based trust issued receipts. 
                        <E T="03">See supra</E>
                         note 11 and accompanying text. 
                        <E T="03">See also infra</E>
                         Section III.B.3.
                    </P>
                </FTNT>
                <PRTPAGE P="62478"/>
                <HD SOURCE="HD3">(b) Analysis</HD>
                <P>
                    The Commission does not agree with BZX's assertions, which are substantially the same assertions that BZX made, and the Commission discussed, in the WisdomTree Order. Now, as then, the record does not demonstrate that it is unlikely that trading in the proposed ETP would be the predominant influence on prices in the CME bitcoin futures market. As the Commission has already addressed and rejected one of the bases of BZX's assertion—that CME bitcoin futures lead price discovery 
                    <SU>157</SU>
                    <FTREF/>
                    —the Commission will only address below the other two bases: the overall size of, and the impact of buys and sells on, the bitcoin market.
                </P>
                <FTNT>
                    <P>
                        <SU>157</SU>
                         
                        <E T="03">See supra</E>
                         Section III.B.2.i.b.
                    </P>
                </FTNT>
                <P>
                    BZX's assertions about the potential effect of trading in the Shares on the CME bitcoin futures market and spot bitcoin market are general and conclusory, citing to the aforementioned trade volume of the CME bitcoin futures market and the size and liquidity of the spot bitcoin market, as well as the market impact of a single transaction in spot bitcoin, without any analysis or evidence to support these assertions. For example, there is no limit on the amount of mined bitcoin that the Trust may hold. Yet BZX does not provide any information on the expected growth in the size of the Trust and the resultant increase in the amount of bitcoin held by the Trust over time, or on the overall expected number, size, and frequency of creations and redemptions—or how any of the foregoing could (if at all) influence prices in the CME bitcoin futures market. Thus, the Commission cannot conclude, based on BZX's statements alone and absent any evidence or analysis in support of BZX's assertions, that it is unlikely that trading in the ETP would be the predominant influence on prices in the CME bitcoin futures market.
                    <SU>158</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>158</SU>
                         
                        <E T="03">See</E>
                         VanEck Order, 86 FR at 64548-59; WisdomTree Order, 86 FR at 69332-33; Kryptoin Order, 86 FR at 74177; SkyBridge Order, 87 FR at 3879; Wise Origin Order, 87 FR at 5537; ARK 21Shares Order, 87 FR at 20025; Global X Order, 87 FR at 14921.
                    </P>
                </FTNT>
                <P>
                    The Commission also is not persuaded by BZX's assertions about the minimal effect a market order to buy or sell bitcoin would have on the bitcoin market.
                    <SU>159</SU>
                    <FTREF/>
                     While BZX concludes by way of an example of a $10 million market order that buying or selling large amounts of bitcoin would have insignificant market impact, the conclusion does not analyze the extent of any impact on the CME bitcoin futures market or the CME bitcoin futures market's prices. Accordingly, such statistics, without more, are not relevant to the Commission's consideration of whether trading in the ETP would be the predominant influence on prices in the CME bitcoin futures market.
                </P>
                <FTNT>
                    <P>
                        <SU>159</SU>
                         
                        <E T="03">See</E>
                         Notice, 87 FR at 8328 (“For a $10 million market order, the cost to buy or sell is roughly 20 basis points with a market impact of 50 basis points. Stated another way, a market participant could enter a market buy or sell order for $10 million of bitcoin and only move the market 0.5%.”).
                    </P>
                </FTNT>
                <P>
                    To the extent that BZX is suggesting that a single $10 million order in bitcoin would have immaterial impact on the prices in the CME bitcoin futures market, the Exchange has not adequately explained why 
                    <E T="03">a single market order in spot bitcoin</E>
                     is an appropriate proxy for trading in the Shares. As stated above, the second prong in establishing whether the CME bitcoin futures market constitutes a “market of significant size” is the determination that it is unlikely that 
                    <E T="03">trading in the proposed ETP</E>
                     would be the predominant influence on prices in the CME bitcoin futures market. While authorized participants of the Trust might transact in the spot bitcoin market as part of their creation or redemption of Shares, the Shares themselves would be traded in the secondary market on BZX. Furthermore, the record does not discuss the expected number or trading volume of the Shares, or establish the potential effect of the Shares' trade prices on CME bitcoin futures prices. For example, BZX does not provide any data or analysis about the potential effect the quotations or trade prices of the Shares might have on market-maker quotations in CME bitcoin futures contracts and whether those effects would constitute a predominant influence on the prices of those futures contracts.
                    <SU>160</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>160</SU>
                         
                        <E T="03">See</E>
                         VanEck Order, 86 FR at 64549; WisdomTree Order, 86 FR at 69333; Kryptoin Order, 86 FR at 74177; SkyBridge Order, 87 FR at 3879; Wise Origin Order, 87 FR at 5537; ARK 21Shares Order, 87 FR at 20025; Global X Order, 87 FR at 14921.
                    </P>
                </FTNT>
                <P>
                    Moreover, although BZX asserts that “the Shares should trade close to NAV given that market participants would arbitrage any significant price deviations between the price of the Shares and prices in the spot market,” 
                    <SU>161</SU>
                    <FTREF/>
                     the Exchange does not provide any additional data or analysis to support such an assertion; 
                    <SU>162</SU>
                    <FTREF/>
                     nor does the Exchange show that the arbitrage that may exist between the Shares and prices in the 
                    <E T="03">spot</E>
                     bitcoin markets demonstrates that the Shares would not be the predominant force on prices in the 
                    <E T="03">CME bitcoin futures</E>
                     market.
                </P>
                <FTNT>
                    <P>
                        <SU>161</SU>
                         Notice, 87 FR at 8328.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>162</SU>
                         
                        <E T="03">See also supra</E>
                         notes 106-109 and accompanying text.
                    </P>
                </FTNT>
                <P>Thus, the Commission cannot conclude, based on the assertions in the filing and absent sufficient evidence or analysis in support of these assertions, that it is unlikely that trading in the proposed ETP would be the predominant influence on prices in the CME bitcoin futures market.</P>
                <P>Therefore, because BZX has not provided sufficient information to establish both prongs of the “market of significant size” determination, the Commission cannot conclude that the CME bitcoin futures market is a “market of significant size” related to spot bitcoin such that BZX would be able to rely on a surveillance-sharing agreement with the CME to provide sufficient protection against fraudulent and manipulative acts and practices.</P>
                <HD SOURCE="HD3">(3) Assertions That the Proposed Spot Bitcoin ETP Is Comparable to Bitcoin Futures-Based ETFs</HD>
                <HD SOURCE="HD3">(i) BZX's Assertions</HD>
                <P>
                    BZX asserts that, after allowing the listing and trading of bitcoin futures ETFs that hold primarily CME bitcoin futures, disapproving spot bitcoin ETPs “seems . . . arbitrary and capricious.” 
                    <SU>163</SU>
                    <FTREF/>
                     BZX asserts that, if the CME bitcoin futures market were not, in the opinion of the Commission, a regulated market of significant size, permitting bitcoin futures ETFs that trade on such market “would seem to be inconsistent with the requirement under the [Exchange] Act of being designed to `prevent fraudulent and manipulative acts and practices.' ” 
                    <SU>164</SU>
                    <FTREF/>
                     BZX argues that this is particularly true for the Trust, which would use the Reference Rate as its price source to calculate its daily NAV, “with inputs from 
                    <E T="03">the same</E>
                     bitcoin trading platforms. . . and materially the same methodology as is used to price CME [b]itcoin [f]utures.” 
                    <SU>165</SU>
                    <FTREF/>
                     According to BZX, the Constituent Bitcoin Platforms' pricing inputs and methodology (except for the calculation time) are the same “with respect to the Trust and CME bitcoin futures.” 
                    <SU>166</SU>
                    <FTREF/>
                     BZX asserts that any 
                    <PRTPAGE P="62479"/>
                    objective review of the proposals to list spot bitcoin ETPs compared to the already listed and traded bitcoin futures ETFs would lead to the conclusion that spot bitcoin ETPs should be available to U.S. investors 
                    <SU>167</SU>
                    <FTREF/>
                     because “any concerns related to preventing fraudulent and manipulative acts and practices related to [s]pot [b]itcoin ETPs would apply equally to the spot markets underlying the futures contracts held by a [CME] [b]itcoin [f]utures ETF.” 
                    <SU>168</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>163</SU>
                         Notice, 87 FR at 8325.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>164</SU>
                         
                        <E T="03">Id.</E>
                         at 8323; 15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>165</SU>
                         Notice, 87 FR at 8323 (emphasis in the original).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>166</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>167</SU>
                         
                        <E T="03">See</E>
                         Notice, 87 FR at 8324.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>168</SU>
                         
                        <E T="03">Id.</E>
                         at 8325.
                    </P>
                </FTNT>
                <P>
                    Further, as discussed in more detail below,
                    <SU>169</SU>
                    <FTREF/>
                     while the Trust is not an investment company registered under the 1940 Act,
                    <SU>170</SU>
                    <FTREF/>
                     according to BZX, “the Sponsor has taken 1940 Act considerations into account in structuring the Trust's operations in seeking `to protect investors and the public interest.' ” 
                    <SU>171</SU>
                    <FTREF/>
                     According to BZX, “the Sponsor has structured the Trust's operations to operate as if certain 1940 Act provisions apply, providing transparency and investor protections such that a distinction between [bitcoin futures] ETFs and [spot bitcoin] ETPs is unwarranted.” 
                    <SU>172</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>169</SU>
                         
                        <E T="03">See</E>
                         Section III.C, 
                        <E T="03">infra.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>170</SU>
                         
                        <E T="03">See id.</E>
                         at 8329 (according to the Registration Statement, “the Trust is neither an investment company registered under the [1940 Act], as amended, nor a commodity pool for purposes of the Commodity Exchange Act . . . , and neither the Trust nor the Sponsor is subject to regulation as a commodity pool operator or a commodity trading adviser in connection with the Shares.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>171</SU>
                         
                        <E T="03">Id.</E>
                         at 8323. 
                        <E T="03">See also supra</E>
                         note 41 and accompanying text (summarizing the 1940 Act considerations taken into account by the Sponsor in structuring the Trust's operations).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>172</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(ii) Analysis</HD>
                <P>
                    The Commission disagrees with these assertions and conclusions. The proposed rule change does not relate to the same underlying holdings as ETFs regulated under the 1940 Act that provide exposure to bitcoin through CME bitcoin futures, or CME bitcoin futures-based ETPs that have registered their offerings under the Securities Act but are not regulated under the 1940 Act. The Commission considers the proposed rule change on its own merits and under the standards applicable to it. Namely, with respect to this proposed rule change, the Commission must apply the standards as provided by Section 6(b)(5) of the Exchange Act, which it has applied in connection with its orders considering previous proposals to list bitcoin-based commodity trusts and bitcoin-based trust issued receipts.
                    <SU>173</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>173</SU>
                         
                        <E T="03">See supra</E>
                         note 11 and accompanying text.
                    </P>
                </FTNT>
                <P>
                    In focusing on whether “concerns related to preventing fraudulent and manipulative acts and practices related to [s]pot [b]itcoin ETPs would apply equally to the spot markets underlying the futures contracts held by a [CME] [b]itcoin [f]utures ETF,” 
                    <SU>174</SU>
                    <FTREF/>
                     the Exchange mischaracterizes the framework that the Commission has articulated in the Winklevoss Order. As stated in the Winklevoss Order, the Commission is not applying a “cannot be manipulated”approach—either on the CME bitcoin futures market or the spot bitcoin markets. Rather, as the Commission has repeatedly emphasized, and also summarized above, the Commission is examining whether the proposal meets the requirements of the Exchange Act and, pursuant to its Rules of Practice, is placing the burden on BZX to demonstrate the validity of its contention that other means to prevent fraudulent and manipulative acts and practices are sufficient to justify dispensing with the detection and deterrence of fraud and manipulation provided by a comprehensive surveillance-sharing agreement with a regulated market of significant size related to spot bitcoin,
                    <SU>175</SU>
                    <FTREF/>
                     or to establish that it has entered into such a surveillance-sharing agreement.
                </P>
                <FTNT>
                    <P>
                        <SU>174</SU>
                         
                        <E T="03">See</E>
                         Notice, 87 FR at 8325.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>175</SU>
                         
                        <E T="03">See supra</E>
                         notes 42-45 and accompanying text.
                    </P>
                </FTNT>
                <P>
                    Consistent with this approach, the Commission's consideration (and thus far, disapproval) of proposals to list and trade spot bitcoin ETPs does not focus on an assessment of the overall risk of fraud and manipulation in the spot bitcoin or futures markets, or on the extent to which such risks are similar.
                    <SU>176</SU>
                    <FTREF/>
                     Rather, the Commission's focus has been consistently on whether the listing exchange has a comprehensive surveillance-sharing agreement with a regulated market of significant size related to the underlying bitcoin assets of the ETP under consideration, so that it would have the necessary ability to detect and deter manipulative activity. For reasons articulated in the orders approving proposals to list and trade CME bitcoin futures-based ETPs (
                    <E T="03">i.e.,</E>
                     the Teucrium Order and the Valkyrie XBTO Order), the Commission found that in each such case the listing exchange has entered into such a surveillance-sharing agreement.
                    <SU>177</SU>
                    <FTREF/>
                     Applying the same framework to this proposed spot bitcoin ETP, however, as discussed and explained above, the Commission finds that BZX has not.
                </P>
                <FTNT>
                    <P>
                        <SU>176</SU>
                         The Commission's past general discussion on the risk of fraud and manipulation in the spot bitcoin or futures markets is only in response to arguments raised by the proposing listing exchanges (or commenters) that mitigating factors against fraud and manipulation in the spot bitcoin or futures markets should compel the Commission to dispense with the detection and deterrence of fraud and manipulation provided by a comprehensive surveillance-sharing agreement with a regulated market of significant size related to the underlying bitcoin assets. 
                        <E T="03">See, e.g.,</E>
                         Winklevoss Order, 83 FR at 37580, 37582-91 (addressing assertions that “bitcoin and [spot] bitcoin markets,” generally, as well as one bitcoin trading platform, specifically, have unique resistance to fraud and manipulation). 
                        <E T="03">See also</E>
                         USBT Order, 85 FR at 12597, 12599-12608. But even in such instance, the central issue is about the necessity of such a surveillance-sharing agreement, not the overall risk of fraud and manipulation in the spot bitcoin or futures markets, or the extent to which such risks are similar.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>177</SU>
                         
                        <E T="03">See</E>
                         Teucrium Order, 87 FR at 21678-81; Valkyrie XBTO Order, 87 FR at 28850-53.
                    </P>
                </FTNT>
                <P>
                    Moreover, for the CME bitcoin futures ETPs under consideration in the Teucrium Order and the Valkyrie XBTO Order, the proposed “significant” regulated market (
                    <E T="03">i.e.,</E>
                     the CME) with which the listing exchange has a surveillance-sharing agreement is the 
                    <E T="03">same</E>
                     market on which the underlying bitcoin assets (
                    <E T="03">i.e.,</E>
                     CME bitcoin futures contracts) trade. As explained in those Orders, the CME's surveillance can reasonably be relied upon to capture the effects on the CME bitcoin futures market caused by a person attempting to manipulate the CME bitcoin futures ETP by manipulating the price of CME bitcoin futures contracts, whether that attempt is made by directly trading on the CME bitcoin futures market or indirectly by trading outside of the CME bitcoin futures market.
                    <SU>178</SU>
                    <FTREF/>
                     Regarding the approved Teucrium Bitcoin Futures Fund in the Teucrium Order (“Fund”), for example, when the CME shares its surveillance information with the listing exchange, the information would assist in detecting and deterring fraudulent or manipulative misconduct related to the non-cash assets held by the Fund.
                    <SU>179</SU>
                    <FTREF/>
                     Accordingly, the Commission explains in the Teucrium Order and the Valkyrie XBTO Order that it is unnecessary for a listing exchange to establish a reasonable likelihood that a would-be manipulator would have to trade on the CME itself to manipulate a proposed ETP whose only non-cash holdings would be CME bitcoin futures contracts.
                    <SU>180</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>178</SU>
                         
                        <E T="03">See</E>
                         Teucrium Order, 87 FR at 21679; Valkyrie XBTO Order, 87 FR at 28851.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>179</SU>
                         
                        <E T="03">See</E>
                         Teucrium Order, 87 FR at 21679.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>180</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <P>
                    However, as the Commission also states in those Orders, this reasoning does not extend to spot bitcoin ETPs. Spot bitcoin markets are not currently “regulated.” 
                    <SU>181</SU>
                    <FTREF/>
                     If an exchange seeking 
                    <PRTPAGE P="62480"/>
                    to list a spot bitcoin ETP relies on the CME as the regulated market with which it has a comprehensive surveillance-sharing agreement, the assets held by the spot bitcoin ETP would not be traded on the CME. Because of this significant difference, with respect to a spot bitcoin ETP, there would be reason to question whether a surveillance-sharing agreement with the CME would, in fact, assist in detecting and deterring fraudulent and manipulative misconduct affecting the price of the spot bitcoin held by that ETP. If, however, an exchange proposing to list and trade a spot bitcoin ETP identifies the CME as the regulated market with which it has a comprehensive surveillance-sharing agreement, the exchange could overcome the Commission's concern by demonstrating that there is a reasonable likelihood that a person attempting to manipulate the spot bitcoin ETP would have to trade on the CME in order to manipulate the ETP, because such demonstration would help establish that the exchange's surveillance-sharing agreement with the CME would have the intended effect of aiding in the detection and deterrence of fraudulent and manipulative misconduct related to the spot bitcoin held by the ETP.
                    <SU>182</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>181</SU>
                         
                        <E T="03">See</E>
                         Teucrium Order, 87 FR at 21679 n.46 (citing USBT Order, 85 FR at 12604; NYDIG Order, 87 FR at 14936 nn.65-67). 
                        <E T="03">See also</E>
                         Valkyrie XBTO Order, 87 FR at 28851 n.42.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>182</SU>
                         
                        <E T="03">See</E>
                         Teucrium Order, 87 FR at 21679 n.46; Valkyrie XBTO Order, 87 FR at 28851 n.42.
                    </P>
                </FTNT>
                <P>
                    Because, here, BZX is seeking to list a spot bitcoin ETP that relies on the CME as the purported “significant” regulated market with which it has a comprehensive surveillance-sharing agreement, the assets held by the proposed ETP would 
                    <E T="03">not</E>
                     be traded on the CME. Thus there is reason to question whether a surveillance-sharing agreement with the CME would, in fact, assist in detecting and deterring fraudulent and manipulative misconduct affecting the price of the spot bitcoin held by the proposed ETP.
                    <SU>183</SU>
                    <FTREF/>
                     An exchange can overcome this concern by demonstrating that there is a reasonable likelihood that a person attempting to manipulate the proposed ETP would have to trade 
                    <E T="03">on the CME</E>
                     in order to manipulate the ETP because such demonstration would help establish that an exchange's surveillance-sharing agreement with the CME would have the intended effect of aiding in the detection and deterrence of fraudulent and manipulative misconduct related to the spot bitcoin held by the proposed ETP.
                    <SU>184</SU>
                    <FTREF/>
                     As discussed and explained above,
                    <SU>185</SU>
                    <FTREF/>
                     the Commission finds that BZX has not made such demonstration.
                </P>
                <FTNT>
                    <P>
                        <SU>183</SU>
                         
                        <E T="03">See</E>
                         Teucrium Order, 87 FR at 21679 n.46; Valkyrie XBTO Order, 87 FR at 28851 n.42. There is reason to question whether the CME's surveillance would capture manipulation of spot bitcoin that occurs off of the CME, if, for example, off-CME manipulation of spot bitcoin does not also similarly impact CME bitcoin futures contracts.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>184</SU>
                         
                        <E T="03">See</E>
                         Teucrium Order, 87 FR at 21679 n.46; Valkyrie XBTO Order, 87 FR at 28851 n.42.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>185</SU>
                         
                        <E T="03">See</E>
                         Section III.B.2.i, 
                        <E T="03">supra.</E>
                    </P>
                </FTNT>
                <P>
                    To the extent that the Exchange is arguing that the CME's surveillance would, in fact, assist in detecting and deterring fraudulent and manipulative misconduct that impacts spot bitcoin ETPs in the same way as it would for misconduct that impacts the CME bitcoin futures ETFs/ETPs, the information in the record for this filing does not support such a claim. First, while BZX emphasizes that the “pricing inputs and methodology (except for the calculation time)” for the Reference Rate are “the same” as for the BRR,
                    <SU>186</SU>
                    <FTREF/>
                     this does not—absent supporting data—establish any link between prices of shares of any CME bitcoin futures ETFs/ETPs and the prices of Shares of the proposed spot bitcoin ETP. There is no evidence in the record that shares of CME bitcoin futures ETFs/ETPs are priced according to the BRR. The BRR is a once-a-day reference rate of the U.S. dollar price of one bitcoin as of 4:00 p.m., London Time.
                    <SU>187</SU>
                    <FTREF/>
                     The BRR aggregates the trade flow of its constituent spot bitcoin platforms—Coinbase, Gemini, LMAX Digital, itBit, Kraken, and Bitstamp 
                    <SU>188</SU>
                    <FTREF/>
                    —during a specific one-hour calculation window.
                    <SU>189</SU>
                    <FTREF/>
                     While the BRR is used to value the final cash settlement of CME bitcoin futures contracts, it is not generally used for daily cash settlement of such contracts,
                    <SU>190</SU>
                    <FTREF/>
                     nor is it claimed to be used for any intra-day trading of such contracts. In addition, CME bitcoin futures ETFs do not hold their CME bitcoin futures contracts to final cash settlement; rather, the contracts are rolled 
                    <SU>191</SU>
                    <FTREF/>
                     prior to their settlement dates. Moreover, the shares of CME bitcoin futures ETFs trade in secondary markets, and there is no evidence in the record for this filing that such intra-day, secondary market trading prices are determined by the BRR.
                </P>
                <FTNT>
                    <P>
                        <SU>186</SU>
                         
                        <E T="03">See</E>
                         Notice, 87 FR at 8323. The Reference Rate is calculated as of 4:00 p.m. E.T., whereas the BRR is calculated as of 4:00 p.m. London Time. 
                        <E T="03">See</E>
                         Notice, 87 FR at 8329 n.77.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>187</SU>
                         
                        <E T="03">See https://docs-cfbenchmarks.s3.amazonaws.com/CME+CF+Reference+Rates+Methodology.pdf.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>188</SU>
                         
                        <E T="03">See https://docs-cfbenchmarks.s3.amazonaws.com/CME+CF+Constituent+Exchanges.pdf.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>189</SU>
                         
                        <E T="03">See https://www.cmegroup.com/trading/files/bitcoin-reference-rate-methodology.pdf.</E>
                         This one-hour window is partitioned into 12, five-minute intervals, where the BRR is calculated as the equally-weighted average of the volume-weighted medians of all 12 partitions. 
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>190</SU>
                         Under normal procedures, daily cash settlements are generally based on the volume-weighted average price of trading activity on CME Globex between 2:59 p.m. and 3:00 p.m., Central Time). 
                        <E T="03">See https://www.cmegroup.com/confluence/display/EPICSANDBOX/Bitcoin</E>
                         for a description of CME bitcoin futures daily settlement procedures.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>191</SU>
                         Rolling a futures contract refers to extending the expiration of a position by closing out the futures contract that is nearing expiration and opening a new position in a futures contract with a later expiration.
                    </P>
                </FTNT>
                <P>
                    There is also no evidence in the record that the Shares' prices would be determined by the Reference Rate.
                    <SU>192</SU>
                    <FTREF/>
                     The Reference Rate aggregates the trade flow of the Constituent Bitcoin Platforms—the current Constituent Bitcoin Platforms are Bitstamp, Coinbase, Gemini, itBit and Kraken—during an observation window between 3:00 p.m. and 4:00 p.m. E.T. into the U.S. dollar price of one bitcoin at 4:00 p.m. E.T. While the Reference Rate would be used daily to value the bitcoins held by the Trust, the Reference Rate would not be used for the creation or redemption of Shares, nor is it claimed that the Reference Rate would be used for any intra-day secondary market trading of the Shares.
                    <SU>193</SU>
                    <FTREF/>
                     Rather, the Share price would be discovered through continuous intra-day, secondary market interactions of buy and sell interests.
                    <SU>194</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>192</SU>
                         As noted above, 
                        <E T="03">see supra</E>
                         note 33, the Commission understands that the Reference Rate was discontinued as of April 2022. Because the Exchange has not amended its filing or its assertions with respect to the Reference Rate, the Commission's analysis herein responds to the Exchange's arguments as presented in its filing by assuming that the Reference Rate continues to be published.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>193</SU>
                         
                        <E T="03">See supra</E>
                         notes 106-109 and accompanying text.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>194</SU>
                         As discussed above, the use of the Reference Rate by the Trust to determine the value of its bitcoin does not support the finding that the Exchange has established other means to prevent fraud and manipulation that are sufficient to justify dispensing with the detection and deterrence of fraud and manipulation provided by a comprehensive surveillance-sharing agreement with a regulated market of significant size related to spot bitcoin. 
                        <E T="03">See</E>
                         Section III.B.1.ii, 
                        <E T="03">supra.</E>
                         Likewise, the Commission has previously rejected arguments by listing exchanges that the use of a reference rate similar to the BRR to value bitcoin held by proposed spot bitcoin ETPs provides other means to prevent fraud and manipulation that are sufficient to justify dispensing with the detection and deterrence of fraud and manipulation provided by a comprehensive surveillance-sharing agreement with a regulated market of significant size related to spot bitcoin. 
                        <E T="03">See</E>
                         Wise Origin Order, 87 FR at 5532-33; SkyBridge Order, 87 FR at 3877. Accordingly, the Reference Rate and the BRR, and the similarities between the BRR and the Reference Rate, are not informative in the Commission's determination of whether the Exchange has established other means to prevent fraud and manipulation.
                    </P>
                </FTNT>
                <P>
                    Thus, although the Exchange focuses on the similarities between the BRR and the Reference Rate,
                    <SU>195</SU>
                    <FTREF/>
                     there is no 
                    <PRTPAGE P="62481"/>
                    evidence in the record that the shares of any CME bitcoin futures ETF/ETP, or the Shares of the proposed spot bitcoin ETP, would trade in the secondary market at a price related to (or informed by) the BRR or the Reference Rate.
                    <SU>196</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>195</SU>
                         Despite the Exchange's claim that the Reference Rate uses “inputs from 
                        <E T="03">the same</E>
                         bitcoin trading platforms” as the BRR, the BRR includes trade flow from LMAX Digital, which platform does 
                        <PRTPAGE/>
                        not appear to be included as a Constituent Bitcoin Platform of the Reference Rate.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>196</SU>
                         In addition, the Commission's determination in the Teucrium Order and the Valkyrie XBTO Order to approve the listing and trading of the relevant CME bitcoin futures ETPs was not based on the ETPs' use—or lack of use—of the BRR (or any other similar pricing mechanism) for the calculation of NAV, or on the fact that the BRR is used for the final cash settlement of CME bitcoin futures contracts. Rather, as discussed above, the Commission approved the listing and trading of such CME bitcoin futures ETPs, not because of the BRR, but because the Commission found that the listing exchanges satisfy the requirement pertaining to a surveillance-sharing agreement with a regulated market of significant size related to the underlying bitcoin assets—which for such ETPs are CME bitcoin futures contracts, not spot bitcoin.
                    </P>
                </FTNT>
                <P>
                    Second, even if the Exchange had demonstrated a link between the BRR and/or the Reference Rate and the prices of bitcoin futures ETFs/ETPs and/or the proposed spot bitcoin ETP, which it has not, it does not necessarily follow that the CME's surveillance would, in fact, assist in detecting and deterring fraudulent and manipulative misconduct that impacts spot bitcoin ETPs in the same way as it would for misconduct that impacts the CME bitcoin futures ETFs/ETPs—particularly when such misconduct occurs off of the CME itself.
                    <SU>197</SU>
                    <FTREF/>
                     For example, even assuming, for the sake of argument, that the BRR and/or the Reference Rate is a potential link between prices on certain spot bitcoin platforms and CME bitcoin futures prices, it does not—absent supporting data—necessarily follow that 
                    <E T="03">any</E>
                     manipulation that impacts spot bitcoin 
                    <E T="03">also similarly</E>
                     impacts CME bitcoin futures contracts. The Exchange has not provided analysis or data that assesses the reaction (if any) of CME bitcoin futures contracts to instances of fraud and manipulation in spot bitcoin markets.
                </P>
                <FTNT>
                    <P>
                        <SU>197</SU>
                         
                        <E T="03">See also supra</E>
                         note 183.
                    </P>
                </FTNT>
                <P>
                    In addition, the disapproval of the proposal would not constitute an “arbitrary and capricious” administrative action in violation of the Administrative Procedure Act.
                    <SU>198</SU>
                    <FTREF/>
                     Importantly, the issuers are not similarly situated. The issuers of CME bitcoin futures-based ETFs/ETPs propose to hold only CME bitcoin futures contracts (which are traded on the CME itself) as their only non-cash holdings, and the Trust proposes to hold only spot bitcoin (which is not traded on the CME). As explained in detail above, and in the Teucrium Order, Valkyrie XBTO Order, and the Grayscale Order, because of this important difference, for a spot bitcoin ETP, there is reason to question whether a surveillance-sharing agreement with the CME would, in fact, assist in detecting and deterring fraudulent and manipulative misconduct affecting the price of the spot bitcoin held by that ETP.
                    <SU>199</SU>
                    <FTREF/>
                     And as discussed above, neither the Exchange nor any other evidence in the record for this filing, sufficiently demonstrates that the CME's surveillance can be reasonably relied upon to capture the effects of manipulation of the 
                    <E T="03">spot</E>
                     bitcoin assets underlying the proposed ETP when such manipulation is not attempted on the CME itself.
                </P>
                <FTNT>
                    <P>
                        <SU>198</SU>
                         The Commission is disapproving this proposed rule change because BZX has not met its burden to demonstrate that its proposal is consistent with the requirements of Exchange Act Section 6(b)(5). The Commission's disapproval of this proposed rule change does not rest on an evaluation of the relative investment quality of a product holding spot bitcoin versus a product holding CME bitcoin futures, or an assessment of whether bitcoin, or blockchain technology more generally, has utility or value as an innovation or an investment. See, 
                        <E T="03">e.g.,</E>
                         Winklevoss Order, 83 FR at 37580; USBT Order, 85 FR at 12597; One River Order, 87 FR at 33550; Grayscale Order, 87 FR at 40318 n.227.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>199</SU>
                         
                        <E T="03">See supra</E>
                         note 183 and accompanying text.
                    </P>
                </FTNT>
                <P>
                    Moreover, the analytical framework for assessing compliance with the requirements of Exchange Act Section 6(b)(5) that the Commission applies here (
                    <E T="03">i.e.,</E>
                     comprehensive surveillance-sharing agreement with a regulated market of significant size related to the underlying bitcoin assets) is the same one that the Commission has applied in each of its orders considering previous proposals to list bitcoin-based commodity trusts and trust issued receipts.
                    <SU>200</SU>
                    <FTREF/>
                     The Commission has applied this framework to each proposal by analyzing the evidence presented by the listing exchange and statements made by commenters.
                    <SU>201</SU>
                    <FTREF/>
                     Exchange Act Section 6(b)(5) can be satisfied by a proper showing; the Commission has in fact recently approved proposals by the Exchange and the Nasdaq Stock Market to list and trade shares of ETPs holding CME bitcoin futures as their only non-cash holdings.
                    <SU>202</SU>
                    <FTREF/>
                     And in the orders approving the CME bitcoin futures-based ETPs, the Commission explicitly discussed how an exchange seeking to list and trade a spot bitcoin ETP could overcome the lack of a one-to-one relationship between the regulated market with which it has a surveillance-sharing agreement and the market(s) on which the assets held by a spot bitcoin ETP could be traded: by demonstrating that there is a reasonable likelihood that a person attempting to manipulate the spot bitcoin ETP would have to trade on the regulated market (
                    <E T="03">i.e.,</E>
                     on the CME) to manipulate the spot bitcoin ETP.
                    <SU>203</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>200</SU>
                         
                        <E T="03">See supra</E>
                         notes 11-24 and accompanying text.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>201</SU>
                         
                        <E T="03">See supra</E>
                         note 11.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>202</SU>
                         
                        <E T="03">See</E>
                         Teucrium Order and Valkyrie XBTO Order, 
                        <E T="03">supra</E>
                         note 11.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>203</SU>
                         
                        <E T="03">See supra</E>
                         note 182 and accompanying text.
                    </P>
                </FTNT>
                <P>
                    When considering past proposals for spot bitcoin ETPs, the Commission has, in particular, reviewed the econometric and/or statistical evidence in the record to determine whether the listing exchange's proposal has met the applicable standard.
                    <SU>204</SU>
                    <FTREF/>
                     The Commission's assessment fundamentally presents quantitative, empirical questions, but, as discussed above, the Exchange has not provided evidence sufficient to support its arguments. Instead, the Exchange makes various assertions that are not supported by the limited data in the record regarding, among other things, CME bitcoin futures trading size, volume, and open interest, and spot bitcoin market capitalization, or the relationship between spot bitcoin prices and CME bitcoin futures prices (including the lead-lag relationship between the spot market and the CME bitcoin futures market), and the record contains insufficient empirical analysis or quantitative evidence of any such data to support the Exchange's conclusions.
                    <SU>205</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>204</SU>
                         
                        <E T="03">See, e.g.,</E>
                         USBT Order, 85 FR at 12612-13; VanEck Order, 86 FR at 64547-48; WisdomTree Order, 86 FR at 69330-32; Kryptoin Order, 86 FR at 74175-76; NYDIG Order, 87 FR at 14938-39; Wise Origin Order, 87 FR at 5534-36; Global X Order, 87 FR at 14919-20; ARK 21Shares Order, 87 FR at 20023-24; Bitwise Order, 87 FR at 40286-92; Grayscale Order, 87 FR at 40311-14.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>205</SU>
                         
                        <E T="03">See</E>
                         Sections III.B.1 &amp; III.B.2, 
                        <E T="03">supra.</E>
                    </P>
                </FTNT>
                <P>
                    The Exchange also argues that “a distinction between [bitcoin futures] ETFs and [spot bitcoin] ETPs is unwarranted” because the Trust has agreed to voluntarily comply with some requirements of the 1940 Act.
                    <SU>206</SU>
                    <FTREF/>
                     While, as stated by the Exchange, an undertaking by the Trust to comply voluntarily with certain requirements of the 1940 Act may provide some level of transparency and promote certain types of investor protection, it does not alter the Commission's analysis under the Exchange Act relating to a spot bitcoin ETP.
                    <SU>207</SU>
                    <FTREF/>
                     As discussed above, the 
                    <PRTPAGE P="62482"/>
                    proposed rule change does not relate to the same underlying holdings as either ETFs regulated under the 1940 Act that provide exposure to bitcoin through CME bitcoin futures, or CME bitcoin futures-based ETPs that have registered their offerings under the Securities Act but are not regulated under the 1940 Act.
                    <SU>208</SU>
                    <FTREF/>
                     And as discussed above, neither the Exchange nor any other evidence in the record for this filing, sufficiently demonstrates that the CME's surveillance can be reasonably relied upon to capture the effects of manipulation of the spot bitcoin assets underlying the proposed ETP when such manipulation is not attempted on the CME itself. The requirements of Section 6(b)(5) of the Exchange Act apply to the rules of national securities exchanges. Accordingly, the relevant obligation to have a comprehensive surveillance-sharing agreement with a regulated market of significant size related to spot bitcoin, or other means to prevent fraudulent and manipulative acts and practices that are sufficient to justify dispensing with such a surveillance-sharing agreement, resides with the listing exchange. Because there is insufficient evidence in the record demonstrating that BZX has satisfied this obligation, the Commission cannot approve the proposed ETP for listing and trading on BZX.
                </P>
                <FTNT>
                    <P>
                        <SU>206</SU>
                         
                        <E T="03">See supra</E>
                         note 172 and accompanying text.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>207</SU>
                         The 1940 Act provides for the regulation of investment companies. 
                        <E T="03">See</E>
                         15 U.S.C. 80a. In general, the 1940 Act is designed to minimize conflicts of interest and is focused on disclosure to the investing public of information about the fund and its investment objectives, as well as on investment company structure and operations. 
                        <E T="03">See https://www.sec.gov/investment/laws-and-rules.</E>
                         The requirements of Section 6(b)(5) of the Exchange Act, on the other hand, apply to the rules of national securities exchanges and require, among other things, that such rules be designed to prevent 
                        <PRTPAGE/>
                        fraudulent and manipulative acts and practices. 15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>208</SU>
                         Although counsel for the sponsor of the Teucrium Bitcoin Futures Fund submitted a letter to the Commission stating that the trust, which was not regulated under the 1940 Act, intended to comply with certain requirements of the 1940 Act, the Commission did not rely on this representation as a basis for its approval of the proposed rule change. 
                        <E T="03">See</E>
                         Teucrium Order, 87 FR at 21682. 
                        <E T="03">See also</E>
                         letter from W. Thomas Conner, Shareholder, VedderPrice, dated September 1, 2021, at 9.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Whether BZX Has Met Its Burden To Demonstrate That the Proposal Is Designed To Protect Investors and the Public Interest</HD>
                <P>
                    BZX contends that, if approved, the proposed ETP would protect investors and the public interest. However, the Commission must consider these potential benefits in the broader context of whether the proposal meets each of the applicable requirements of the Exchange Act.
                    <SU>209</SU>
                    <FTREF/>
                     Because BZX has not demonstrated that its proposed rule change is designed to prevent fraudulent and manipulative acts and practices, the Commission must disapprove the proposal.
                </P>
                <FTNT>
                    <P>
                        <SU>209</SU>
                         
                        <E T="03">See</E>
                         Winklevoss Order, 83 FR at 37602. 
                        <E T="03">See also</E>
                         GraniteShares Order, 83 FR at 43931; ProShares Order, 83 FR at 43941; USBT Order, 85 FR at 12615; WisdomTree Order, 86 FR at 69333; Valkyrie Order, 86 FR at 74163; Kryptoin Order, 86 FR at 74178; SkyBridge Order, 87 FR at 3880; Wise Origin Order, 87 FR at 5537; ARK 21Shares Order, 87 FR at 20026; Global X Order, 87 FR at 14921; Bitwise Order, 87 FR at 40292; Grayscale Order, 87 FR at 40319.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(1) BZX's Assertions</HD>
                <P>
                    The Exchange states that the proposal is designed to protect investors and the public interest. BZX asserts that access for U.S. retail investors to gain exposure to bitcoin via a transparent and U.S. regulated, exchange-traded vehicle remains limited.
                    <SU>210</SU>
                    <FTREF/>
                     According to the Exchange, current options include: (i) paying a potentially high premium (and high management fees) to buy over-the-counter (“OTC”) bitcoin funds, to the advantage of more sophisticated investors that are able to create shares at NAV directly with the issuing trust; (ii) facing the technical risk, complexity, and generally high fees associated with buying spot bitcoin; (iii) purchasing shares of operating companies that they believe will provide proxy exposure to bitcoin with limited disclosure about the associated risks; or (iv) through the purchase of bitcoin futures ETFs that represents a sub-optimal investment for long-term investors.
                    <SU>211</SU>
                    <FTREF/>
                     Meanwhile, the Exchange represents that investors in many other countries, including Canada 
                    <SU>212</SU>
                    <FTREF/>
                     and Brazil, are able to use more traditional exchange-listed and traded products (including exchange-traded funds holding physical bitcoin) to gain exposure to bitcoin, disadvantaging U.S. investors and leaving them with more risky means of getting bitcoin exposure.
                    <SU>213</SU>
                    <FTREF/>
                     Additionally, investors in other countries and regions, specifically Canada and Europe, generally pay lower fees than U.S. retail investors that invest in OTC bitcoin funds due to the fee pressure that results from increased competition among available bitcoin investment options.
                    <SU>214</SU>
                    <FTREF/>
                     Without an approved and regulated spot bitcoin ETP in the U.S. as a viable alternative, BZX argues that U.S. investors could seek to purchase shares of non-U.S. bitcoin vehicles in order to get access to bitcoin exposure, and given the separate regulatory regime and the potential difficulties associated with any international litigation, such an arrangement would create more risk exposure for U.S. investors than they would otherwise have with an U.S. exchange listed ETP.
                    <SU>215</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>210</SU>
                         
                        <E T="03">See</E>
                         Notice, 87 FR at 8322.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>211</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>212</SU>
                         The Exchange notes that the Purpose Bitcoin ETF, a retail physical bitcoin ETP launched in Canada, reportedly reached $1.2 billion in assets under management as of October 15, 2021, demonstrating the demand for a North American market listed bitcoin ETP. 
                        <E T="03">See id.</E>
                         at 8322 n.46.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>213</SU>
                         The Exchange notes that securities regulators in a number of other countries have either approved or otherwise allowed the listing and trading of bitcoin ETPs. Specifically, these funds include the Purpose Bitcoin ETF, Bitcoin ETF, VanEck Vectors Bitcoin ETN, WisdomTree Bitcoin ETP, Bitcoin Tracker One, BTCetc bitcoin ETP, Amun Bitcoin ETP, Amun Bitcoin Suisse ETP, 21Shares Short Bitcoin ETP, CoinShares Physical Bitcoin ETP. 
                        <E T="03">See id.</E>
                         at 8322 n.47.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>214</SU>
                         
                        <E T="03">See id.</E>
                         at 8322.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>215</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <P>
                    BZX argues that over the past 1.5 years, U.S. investor exposure to bitcoin through OTC bitcoin funds has grown into the tens of billions of dollars and more than a billion dollars of exposure through bitcoin futures ETFs.
                    <SU>216</SU>
                    <FTREF/>
                     With that growth, BZX asserts, so too has grown the quantifiable investor protection issues to U.S. investors through roll costs for bitcoin futures ETFs and premium/discount volatility and management fees for OTC bitcoin funds.
                    <SU>217</SU>
                    <FTREF/>
                     The Exchange understands the Commission's previous focus on potential manipulation of a spot bitcoin ETP in prior disapproval orders, but now believes that such concerns have been sufficiently mitigated, and that the growing and quantifiable investor protection concerns should be a central consideration as the Commission reviews this proposal.
                    <SU>218</SU>
                    <FTREF/>
                     The Exchange believes that approving this proposal (and comparable proposals) provides the Commission with the opportunity to allow U.S. investors with access to bitcoin in a regulated and transparent exchange-traded vehicle that would act to limit risk to U.S. investors by: (i) reducing premium and discount volatility; (ii) reducing management fees through meaningful competition; (iii) reducing risks and costs associated with investing in bitcoin futures ETFs and operating companies that are imperfect proxies for bitcoin exposure; and (iv) providing an alternative for investors to self-custodying spot bitcoin.
                    <SU>219</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>216</SU>
                         
                        <E T="03">See id.</E>
                         at 8329.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>217</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>218</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>219</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <P>
                    In addition, BZX represents that the Sponsor has taken 1940 Act considerations into account in structuring the Trust's operations in seeking “to protect investors and the public interest.” 
                    <SU>220</SU>
                    <FTREF/>
                     Although the Trust would not be an investment company registered under the 1940 Act, the Exchange represents that: (a) the Trust would qualify as an investment company under Accounting Standards Update 2013-08 and, as such, the Sponsor would ensure that the Trust's financial statements would be audited at least annually by an independent registered public accounting firm and, 
                    <PRTPAGE P="62483"/>
                    as part of such audit, the auditor would be expected to perform procedures similar to those used for ETFs registered under the 1940 Act; (b) the Sponsor would facilitate the Trust's compliance with the financial record keeping and reporting requirements under the Sarbanes-Oxley Act of 2002; (c) the Trust's Custodian would qualify as a “custodian” under the 1940 Act, and the Custodian would agree to exercise reasonable care, prudence, and diligence such as a person having responsibility for the safekeeping of property of the Trust would exercise; (d) the Trust would be subject to the transparency requirements of Rule 6c-11 under the 1940 Act; (e) the Sponsor would adopt procedures to ensure there are no transactions with affiliated persons that would be prohibited by Section 17 of the 1940 Act and the applicable rules and regulations thereunder; (f) the Trust would maintain a fidelity bond for the benefit of the Trust in the maximum amount required by Rule 17g-1 under the 1940 Act; and (g) the Sponsor or applicable service provider of the Trust would maintain the books and records of the Trust in satisfaction of the requirements of Section 31 of the 1940 Act.
                    <SU>221</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>220</SU>
                         
                        <E T="03">See id.</E>
                         at 8323.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>221</SU>
                         
                        <E T="03">See id.</E>
                         at 8323-24.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(2) Analysis</HD>
                <P>
                    The Commission disagrees that the proposal should be approved because it is designed to protect investors and the public interest. Here, even if it were true that, compared to trading in unregulated spot bitcoin markets or OTC bitcoin funds, trading a spot bitcoin-based ETP on a national securities exchange could provide some additional protection to investors, or that the Shares would provide more efficient exposure to bitcoin than other products on the market such as bitcoin futures ETPs, or that approval of a spot bitcoin ETP could enhance competition, the Commission must consider this potential benefit in the broader context of whether the proposal meets each of the applicable requirements of the Exchange Act.
                    <SU>222</SU>
                    <FTREF/>
                     Moreover, the same consideration applies despite the Exchange's representation that the Sponsor would voluntarily apply certain provisions of the 1940 Act, as described above, to the Trust. Pursuant to Section 19(b)(2) of the Exchange Act, the Commission must approve a proposed rule change filed by a national securities exchange if it finds that the proposed rule change is consistent with the applicable requirements of the Exchange Act—including the requirement under Section 6(b)(5) that the rules of a national securities exchange be designed to prevent fraudulent and manipulative acts and practices—and it must disapprove the filing if it does not make such a finding.
                    <SU>223</SU>
                    <FTREF/>
                     Thus, even if a proposed rule change purports to protect investors from a particular type of investment risk—such as experiencing a potentially high premium/discount by investing in an OTC bitcoin fund or roll costs by investing in bitcoin futures ETPs—or purports to provide benefits to investors and the public interest—such as enhancing competition—the proposed rule change may still fail to meet the requirements under the Exchange Act.
                    <SU>224</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>222</SU>
                         
                        <E T="03">See supra</E>
                         note 209.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>223</SU>
                         
                        <E T="03">See</E>
                         Exchange Act Section 19(b)(2)(C), 15 U.S.C. 78s(b)(2)(C). 
                        <E T="03">See also Affiliated Ute Citizens of Utah</E>
                         v. 
                        <E T="03">United States,</E>
                         406 U.S. 128, 151 (1972) (Congress enacted the Exchange Act largely “for the purpose of avoiding frauds”); 
                        <E T="03">Gabelli</E>
                         v. 
                        <E T="03">SEC,</E>
                         568 U.S. 442, 451 (2013) (The “SEC's very purpose” is to detect and mitigate fraud.).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>224</SU>
                         
                        <E T="03">See</E>
                         SolidX Order, 82 FR at 16259; VanEck Order, 86 FR at 54550-51; WisdomTree Order, 86 FR at 69344; Kryptoin Order, 86 FR at 74179; Valkyrie Order, 86 FR at 74163; SkyBridge Order, 87 FR at 3881; Wise Origin Order, 87 FR at 5538; ARK 21Shares Order, 87 FR at 20026-27.
                    </P>
                </FTNT>
                <P>
                    For the reasons discussed above, BZX has not met its burden of demonstrating an adequate basis in the record for the Commission to find that the proposal is consistent with Exchange Act Section 6(b)(5),
                    <SU>225</SU>
                    <FTREF/>
                     and, accordingly, the Commission must disapprove the proposal.
                    <SU>226</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>225</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>226</SU>
                         In disapproving the proposed rule change, the Commission has considered its impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Conclusion</HD>
                <P>For the reasons set forth above, the Commission does not find, pursuant to Section 19(b)(2) of the Exchange Act, that the proposed rule change is consistent with the requirements of the Exchange Act and the rules and regulations thereunder applicable to a national securities exchange, and in particular, with Section 6(b)(5) of the Exchange Act.</P>
                <P>
                    <E T="03">It is therefore ordered</E>
                    , pursuant to Section 19(b)(2) of the Exchange Act, that proposed rule change SR-CboeBZX-2022-006 be, and it hereby is, disapproved.
                </P>
                <SIG>
                    <P>By the Commission.</P>
                    <NAME>J. Matthew DeLesDernier,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22345 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SOCIAL SECURITY ADMINISTRATION</AGENCY>
                <DEPDOC>[Docket No: SSA-2022-0053]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Proposed Request</SUBJECT>
                <P>The Social Security Administration (SSA) publishes a list of information collection packages requiring clearance by the Office of Management and Budget (OMB) in compliance with Public Law 104-13, the Paperwork Reduction Act of 1995, effective October 1, 1995. This notice includes one revision of an OMB-approved information collection.</P>
                <P>SSA is soliciting comments on the accuracy of the agency's burden estimate; the need for the information; its practical utility; ways to enhance its quality, utility, and clarity; and ways to minimize burden on respondents, including the use of automated collection techniques or other forms of information technology. Mail, email, or fax your comments and recommendations on the information collection(s) to the OMB Desk Officer and SSA Reports Clearance Officer at the following addresses or fax numbers.</P>
                <P>
                    Office of Management and Budget (OMB), 
                    <E T="03">Attn:</E>
                     Desk Officer for SSA, 
                    <E T="03">Comments: https://www.reginfo.gov/public/do/PRAMain.</E>
                     Submit your comments online referencing Docket ID Number [SSA-2022-0053].
                </P>
                <P>
                    Social Security Administration (SSA), OLCA, 
                    <E T="03">Attn:</E>
                     Reports Clearance Director, 3100 West High Rise, 6401 Security Blvd., Baltimore, MD 21235, 
                    <E T="03">Fax:</E>
                     410-966-2830, 
                    <E T="03">Email address: OR.Reports.Clearance@ssa.gov</E>
                    .
                </P>
                <P>
                    Or you may submit your comments online through 
                    <E T="03">https://www.reginfo.gov/public/do/PRAMain,</E>
                     referencing Docket ID Number [SSA-2022-0053].
                </P>
                <P>The information collection below is pending at SSA. SSA will submit it to OMB within 60 days from the date of this notice. To be sure we consider your comments, we must receive them no later than December 13, 2022. Individuals can obtain copies of the collection instrument by writing to the above email address.</P>
                <HD SOURCE="HD1">Certificate of Coverage Request—20 CFR 404.1913—0960-0554</HD>
                <P>
                    The United States (U.S.) has agreements with 30 foreign countries to eliminate double Social Security coverage and taxation where, except for the provisions of the agreement, a worker would be subject to coverage and taxes in both countries. These agreements contain rules for determining the country under whose laws the worker's period of employment is covered, and to which country the 
                    <PRTPAGE P="62484"/>
                    worker will pay taxes. The agreements further dictate that, upon the request of the worker or employer, the country under whose system the period of work is covered will issue a certificate of coverage. The certificate serves as proof of exemption from coverage and taxation under the system of the other country. The information we collect assists us in determining a worker's coverage and in issuing a U.S. certificate of coverage as appropriate. Per our agreements, we ask a set number of questions to the workers and employers prior to issuing a certificate of coverage; however, our agreements with Denmark, Netherlands, Norway, and Sweden require us to ask more questions in those countries. Respondents are workers and employers wishing to establish exemption from foreign Social Security taxes.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Revision of an OMB-approved information collection.
                </P>
                <GPOTABLE COLS="7" OPTS="L2,tp0,i1" CDEF="s100,12,12,12,12,12,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Modality of completion</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">Frequency of response</CHED>
                        <CHED H="1">
                            Average
                            <LI>burden per</LI>
                            <LI>response</LI>
                            <LI>(minutes)</LI>
                        </CHED>
                        <CHED H="1">Estimated total annual burden (hours)</CHED>
                        <CHED H="1">
                            Average
                            <LI>theoretical</LI>
                            <LI>hourly cost amount (dollars)*</LI>
                        </CHED>
                        <CHED H="1">Total annual opportunity cost (dollars) **</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Requests via Letter—Individuals (minus Denmark, Netherlands, Norway, Poland &amp; Sweden)</ENT>
                        <ENT>5,833</ENT>
                        <ENT>1</ENT>
                        <ENT>40</ENT>
                        <ENT>3,889</ENT>
                        <ENT>$28.01 *</ENT>
                        <ENT>$108,931 **</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Requests via Internet—Individuals (minus Denmark, Netherlands, Norway, Poland &amp; Sweden)</ENT>
                        <ENT>9,761</ENT>
                        <ENT>1</ENT>
                        <ENT>40</ENT>
                        <ENT>6,507</ENT>
                        <ENT>28.01 *</ENT>
                        <ENT>182,261 **</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Requests via Letter—Individuals in Denmark, Netherlands, Norway, &amp; Sweden</ENT>
                        <ENT>284</ENT>
                        <ENT>1</ENT>
                        <ENT>44</ENT>
                        <ENT>208</ENT>
                        <ENT>28.01 *</ENT>
                        <ENT>5,826 **</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Requests via Letter—Individuals in Poland</ENT>
                        <ENT>16</ENT>
                        <ENT>1</ENT>
                        <ENT>41</ENT>
                        <ENT>11</ENT>
                        <ENT>28.01 *</ENT>
                        <ENT>308 **</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Requests via Internet—Individuals in Denmark, Netherlands, Norway, &amp; Sweden</ENT>
                        <ENT>427</ENT>
                        <ENT>1</ENT>
                        <ENT>44</ENT>
                        <ENT>313</ENT>
                        <ENT>28.01 *</ENT>
                        <ENT>8,767 **</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Requests via Internet—Individuals in Poland</ENT>
                        <ENT>25</ENT>
                        <ENT>1</ENT>
                        <ENT>41</ENT>
                        <ENT>17</ENT>
                        <ENT>28.01 *</ENT>
                        <ENT>476 *</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Requests via Letter—Employers (minus Denmark, Netherlands, Norway, Poland &amp; Sweden)</ENT>
                        <ENT>26,047</ENT>
                        <ENT>1</ENT>
                        <ENT>40</ENT>
                        <ENT>17,365</ENT>
                        <ENT>28.01 *</ENT>
                        <ENT>486,394 **</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Requests via Internet—Employers (minus Denmark, Netherlands, Norway, Poland, &amp; Sweden)</ENT>
                        <ENT>39,096</ENT>
                        <ENT>1</ENT>
                        <ENT>40</ENT>
                        <ENT>26,064</ENT>
                        <ENT>28.01*</ENT>
                        <ENT>730,053**</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Requests via Letter—Employers in Denmark, Netherlands, Norway, &amp; Sweden</ENT>
                        <ENT>1,137</ENT>
                        <ENT>1</ENT>
                        <ENT>44</ENT>
                        <ENT>834</ENT>
                        <ENT>28.01 *</ENT>
                        <ENT>23,360 **</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Requests via Letter—Employers in Poland</ENT>
                        <ENT>57</ENT>
                        <ENT>1</ENT>
                        <ENT>41</ENT>
                        <ENT>39</ENT>
                        <ENT>28.01 *</ENT>
                        <ENT>1,092 **</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Requests via Internet—Employers in Denmark, Netherlands, Norway, &amp; Sweden</ENT>
                        <ENT>1,704</ENT>
                        <ENT>1</ENT>
                        <ENT>44</ENT>
                        <ENT>1,250</ENT>
                        <ENT>28.01 *</ENT>
                        <ENT>35,013 **</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Requests via Internet—Employers in Poland</ENT>
                        <ENT>86</ENT>
                        <ENT>1</ENT>
                        <ENT>41</ENT>
                        <ENT>59</ENT>
                        <ENT>28.01 *</ENT>
                        <ENT>1,653 **</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Totals</ENT>
                        <ENT>84,473</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>56,556</ENT>
                        <ENT/>
                        <ENT>1,584,134 **</ENT>
                    </ROW>
                    <TNOTE>
                        * We based this figure on average U.S. citizen's hourly salary, as reported by Bureau of Labor Statistics data (
                        <E T="03">https://www.bls.gov/oes/current/oes_nat.htm).</E>
                    </TNOTE>
                    <TNOTE>
                        ** This figure does not represent actual costs that SSA is imposing on recipients of Social Security payments to complete this application; rather, these are theoretical opportunity costs for the additional time respondents will spend to complete the application. 
                        <E T="03">There is no actual charge to respondents to complete the application.</E>
                    </TNOTE>
                </GPOTABLE>
                <SIG>
                    <DATED> Dated: October 7, 2022.</DATED>
                    <NAME>Naomi Sipple,</NAME>
                    <TITLE>Reports Clearance Officer, Social Security Administration.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22302 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4191-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF STATE</AGENCY>
                <DEPDOC>[Public Notice: 11887]</DEPDOC>
                <SUBJECT>Imposition of Nonproliferation Measures Against Foreign Persons, Including a Ban on United States Government Procurement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of International Security and Nonproliferation, State Department.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>A determination has been made that a number of foreign persons have engaged in activities that warrant the imposition of measures pursuant to section 3 of the Iran, North Korea, and Syria Nonproliferation Act. The Act provides for sanctions on foreign entities and individuals for the transfer to or acquisition from Iran since January 1, 1999; the transfer to or acquisition from Syria since January 1, 2005; or the transfer to or acquisition from North Korea since January 1, 2006, of goods, services, or technology controlled under multilateral control lists (Missile Technology Control Regime, Australia Group, Chemical Weapons Convention, Nuclear Suppliers Group, Wassenaar Arrangement) or otherwise having the potential to make a material contribution to the development of weapons of mass destruction (WMD) or cruise or ballistic missile systems. The latter category includes (a) items of the same kind as those on multilateral lists but falling below the control list parameters when it is determined that such items have the potential of making a material contribution to WMD or cruise or ballistic missile systems, (b) items on U.S. national control lists for WMD/missile reasons that are not on multilateral lists, and (c) other items with the potential of making such a material contribution when added through case-by-case decisions.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable October 3, 2022.</P>
                </DATES>
                <FURINF>
                    <PRTPAGE P="62485"/>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>On general issues: Pam Durham, Office of Missile, Biological, and Chemical Nonproliferation, Bureau of International Security and Nonproliferation, Department of State, Telephone (202) 647-4930. For U.S. Government procurement ban issues: Eric Moore, Office of the Procurement Executive, Department of State, Telephone: (703) 875-4079.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>On October 3, 2022, the U.S. Government applied the measures authorized in section 3 of the Iran, North Korea, and Syria Nonproliferation Act (Pub. L. 109-353) against the following foreign persons identified in the report submitted pursuant to section 2(a) of the Act:</P>
                <P>Beijing J&amp;A Industry &amp; Trade Co. Ltd. (People's Republic of China); and any successor, sub-unit, or subsidiary thereof;</P>
                <P>Linda Zhai (PRC individual);</P>
                <P>Synnat Pharma Pvt Ltd (India) and any successor, sub-unit, or subsidiary thereof;</P>
                <P>OTOBOT Project Group (Turkey) and any successor, sub-unit, or subsidiary thereof.</P>
                <P>Accordingly, pursuant to Section 3 of the Act, the following measures are imposed on these persons:</P>
                <P>1. No department or agency of the U.S. government may procure or enter into any contract for the procurement of any goods, technology, or services from these foreign persons, except to the extent that the Secretary of State otherwise may determine;</P>
                <P>2. No department or agency of the U.S. government may provide any assistance to these foreign persons, and these persons shall not be eligible to participate in any assistance program of the U.S. government, except to the extent that the Secretary of State otherwise may determine;</P>
                <P>3. No U.S. government sales to these foreign persons of any item on the United States Munitions List are permitted, and all sales to these persons of any defense articles, defense services, or design and construction services under the Arms Export Control Act are terminated; and</P>
                <P>4. No new individual licenses shall be granted for the transfer to these foreign persons of items the export of which is controlled under the Export Control Reform Act of 2018 or the Export Administration Regulations, and any existing such licenses are suspended.</P>
                <P>These measures shall be implemented by the responsible departments and agencies of the U.S. government and will remain in place for two years from the effective date, except to the extent that the Secretary of State may subsequently determine otherwise. These measures are independent of and in addition to any other sanctions imposed on such entities and/or individuals by other federal agencies under separate legal authorities.</P>
                <SIG>
                    <NAME>Choo S. Kang,</NAME>
                    <TITLE>Assistant Secretary for International Security and Nonproliferation, Department of State.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22347 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4710-25-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SURFACE TRANSPORTATION BOARD</AGENCY>
                <SUBJECT>Release of Waybill Data</SUBJECT>
                <P>The Surface Transportation Board has received a request from the Hagerstown/Eastern Panhandle Metropolitan Planning Organization (WB22-54—10/4/22) for permission to use data from the Board's 2019 masked Carload Waybill Sample. A copy of this request may be obtained from the Board's website under docket no. WB22-54.</P>
                <P>The waybill sample contains confidential railroad and shipper data; therefore, if any parties object to these requests, they should file their objections with the Director of the Board's Office of Economics within 14 calendar days of the date of this notice. The rules for release of waybill data are codified at 49 CFR 1244.9.</P>
                <P>
                    <E T="03">Contact:</E>
                     Alexander Dusenberry, (202) 245-0319.
                </P>
                <SIG>
                    <NAME>Regena Smith-Bernard,</NAME>
                    <TITLE>Clearance Clerk.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22315 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4915-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">OFFICE OF THE UNITED STATES TRADE REPRESENTATIVE</AGENCY>
                <SUBJECT>Notice of Conforming Amendments: China's Acts, Policies, and Practices Related to Technology Transfer, Intellectual Property, and Innovation</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the United States Trade Representative (USTR).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. International Trade Commission (USITC) has implemented certain changes to the Harmonized Tariff Schedule of the United States (HTSUS) to reflect Harmonized System modifications adopted by the World Customs Organization and changes to statistical categories. This notice announces conforming amendments to legal note provisions in the HTSUS associated with the actions in the section 301 investigation of China's Acts, Policies, and Practices Related to Technology Transfer, Intellectual Property, and Innovation.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The conforming amendments announced in Annex I to this notice are applicable as of October 14, 2022. The conforming amendments announced in Annex II to this notice apply as of July 1, 2022.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For general questions about this notice, contact Associate General Counsel Philip Butler, Assistant General Counsel Rachel Hasandras, or Assistant General Counsel David Salkeld at (202) 395-5725. For specific questions on customs classification or implementation of the product exclusions identified in the Annex to this notice, contact 
                        <E T="03">traderemedy@cbp.dhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">A. Background</HD>
                <P>
                    The U.S. Trade Representative has taken actions under section 301 of the Trade Act of 1974, as amended, in the form of additional duties on products of China in the investigation of China's Acts, Policies, and Practices Related to Technology Transfer, Intellectual Property, and Innovation. The China 301 actions are set out in notes to the HTSUS. 
                    <E T="03">See, e.g.,</E>
                     87 FR 26797 (section A—summarizing the trade actions and modifications).
                </P>
                <P>In Presidential Proclamation 10326 of December 23, 2021, the President directed the USITC to implement certain changes in tariff subheadings of the HTSUS, consistent with Harmonized System amendments adopted by the World Customs Organization. The changes were effective January 27, 2022. Additionally, the USITC implemented changes to certain ten-digit statistical categories approved by the Committee for Statistical Annotation of Tariff Schedules (formulated pursuant to section 484(f) of the Tariff Act of 1930, as amended (19 U.S.C. 1484(f)), effective July 1, 2022.</P>
                <HD SOURCE="HD1">B. Conforming Amendments</HD>
                <P>To maintain the pre-existing product coverage of the China 301 actions, conforming amendments to the corresponding note provisions in the HTSUS are required.</P>
                <P>
                    Annex I to this notice makes conforming amendments to a U.S. note in ch. 99 of the HTSUS in light of the changes in tariff subheadings made by the USITC in accordance with Presidential Proclamation 10326. In particular, this notice makes conforming amendments to U.S. note 20 
                    <PRTPAGE P="62486"/>
                    subdivisions (b), (f), and (s)(i) to subchapter III of chapter 99 of the HTSUS, as set out in the Annexes to the notices published at 85 FR 85831 (December 29, 2020), 86 FR 13785 (March 10, 2021), and 86 FR 63438 (November 16, 2021) in the above-titled investigation under section 301. The conforming amendments are applicable as of October 14, 2022.
                </P>
                <P>Annex II to this notice makes conforming amendments to accommodate recent changes to the HTSUS made pursuant to 19 U.S.C. 1484(f). In particular, the conforming amendments affect U.S. note 20 subdivisions (sss)(iii)(6) and (8); and U.S. note 20 subdivisions (ttt)(iii)(9), (11), (179), and (180), as set out in the Annexes to the notices published at 86 FR 63438 (November 16, 2021), 87 FR 33871 (June 3, 2022), and 87 FR 17380 (March 28, 2022). Like all exclusions under the Section 301 investigation, these conforming amendments apply to entries of goods that are not liquidated or to entries that are liquidated, but not final.</P>
                <HD SOURCE="HD1">C. Confirmation of CBP Instructions</HD>
                <P>
                    Cargo Systems Messaging Service (CSMS) No. 51166038 (sent Feb. 28, 2022) (
                    <E T="03">https://content.govdelivery.com/accounts/USDHSCBP/bulletins/30cbb56</E>
                    ), addressed duty treatment for HTSUS subheading 2202.99.91 as provided for under HTSUS 9903.88.03, effective January 27, 2022, in light of changes to the HTSUS made by the USITC in accordance with Presidential Proclamation 10326. This notice confirms the U.S. Customs and Border Protection instructions as maintaining the pre-existing product coverage of the 301 actions.
                </P>
                <HD SOURCE="HD1">Annex I</HD>
                <EXTRACT>
                    <P>1. Effective with respect to goods entered for consumption, or withdrawn from warehouse for consumption, on or after 12:01 a.m. eastern daylight time on October 14, 2022, note 20(b) to subchapter III of chapter 99 of the Harmonized Tariff Schedule of the United States (HTSUS) is amended by deleting “8541.40.95”.</P>
                    <P>2. Effective on October 14, 2022, note 20(f) to subchapter III of chapter 99 of the HTSUS is amended:</P>
                    <P>a. by inserting “2202.99.91” in numerical sequence; and</P>
                    <P>b. by deleting the following subheading numbers:</P>
                    <FP SOURCE="FP-2">“3402.11.40</FP>
                    <FP SOURCE="FP-2">5703.20.10</FP>
                    <FP SOURCE="FP-2">7019.39.50</FP>
                    <FP SOURCE="FP-2">7019.59.30</FP>
                    <FP SOURCE="FP-2">7019.59.40</FP>
                    <FP SOURCE="FP-2">7019.59.70</FP>
                    <FP SOURCE="FP-2">7019.59.90</FP>
                    <FP SOURCE="FP-2">7419.99.50</FP>
                    <FP SOURCE="FP-2">9013.90.50”.</FP>
                    <P>3. Effective on October 14, 2022, note 20(s)(i) to subchapter III of chapter 99 of the HTSUS is amended:</P>
                    <P>a. by inserting “1704.90.78” in numerical sequence; and</P>
                    <P>b. by deleting “6201.11.00”.</P>
                </EXTRACT>
                <HD SOURCE="HD1">Annex II</HD>
                <EXTRACT>
                    <P>Effective with respect to goods entered for consumption, or withdrawn from warehouse for consumption, on or after 12:01 a.m. eastern daylight time on July 1, 2022:</P>
                    <P>1. Note 20(sss)(iii)(6) to subchapter III of chapter 99 of the HTSUS is modified by deleting “5603.12.0090” and by inserting “5603.12.0090 prior to July 1, 2022; 5603.12.0070 or 5603.12.0095 effective July 1, 2022” in lieu thereof.</P>
                    <P>2. Note 20(sss)(iii)(8) to subchapter III of chapter 99 of the HTSUS is modified by deleting “5603.92.0090” and by inserting “5603.92.0090 prior to July 1, 2022; 5603.92.0070 or 5603.92.0095 effective July 1, 2022” in lieu thereof.</P>
                    <P>3. Note 20(ttt)(iii)(9) to subchapter III of chapter 99 of the HTSUS is modified by deleting “5603.12.0090” and by inserting “5603.12.0090 prior to July 1, 2022; 5603.12.0070 or 5603.12.0095 effective July 1, 2022” in lieu thereof.</P>
                    <P>4. Note 20(ttt)(iii)(11) to subchapter III of chapter 99 of the HTSUS is modified by deleting “5603.92.0090” and by inserting “5603.92.0090 prior to July 1, 2022; 5603.92.0070 or 5603.92.0095 effective July 1, 2022” in lieu thereof.</P>
                    <P>5. Note 20(ttt)(iii)(179) to subchapter III of chapter 99 of the HTSUS is modified by deleting “9403.20.0081” and by inserting “9403.20.0081 prior to July 1, 2022; described in statistical reporting number 9403.20.0082 effective July 1, 2022” in lieu thereof.</P>
                    <P>6. Note 20(ttt)(iii)(180) to subchapter III of chapter 99 of the HTSUS is modified by deleting “9403.20.0081 effective July 1, 2019” and by inserting “9403.20.0081 effective July 1, 2019 through June 30, 2022; described in statistical reporting number 9403.20.0082 effective July 1, 2022” in lieu thereof.”</P>
                </EXTRACT>
                <SIG>
                    <NAME>Greta Peisch,</NAME>
                    <TITLE>General Counsel, Office of the United States Trade Representative.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22354 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3390-F3-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">OFFICE OF THE UNITED STATES TRADE REPRESENTATIVE</AGENCY>
                <SUBJECT>Notice of Technical Amendments to Two Exclusions: China's Acts, Policies, and Practices Related to Technology Transfer, Intellectual Property, and Innovation</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the United States Trade Representative (USTR).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces the U.S. Trade Representative's determination to make two technical amendments to certain previously reinstated exclusions associated with the section 301 investigation of China Acts, Policies, and Practices Related to Technology Transfer, Intellectual Property, and Innovation.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The technical amendments announced in the Annex to this notice apply as of October 12, 2021, and extend through December 31, 2022.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For general questions about this notice, contact Associate General Counsel Philip Butler, Assistant General Counsel Rachel Hasandras, or Assistant General Counsel David Salkeld at (202) 395-5725. For specific questions on customs classification or implementation of the product exclusions identified in the Annex to this notice, contact 
                        <E T="03">traderemedy@cbp.dhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Annex to this notice makes technical amendments to U.S. note subdivisions 20(ttt)(iii)(50) and (ttt)(iii)(51) to subchapter III of chapter 99 of the Harmonized Tariff Schedule of the United States (HTSUS), as set out in the Annex of the notice published at 87 FR 17380 (March 28, 2022), to correct the descriptions of the articles covered by the exclusions.</P>
                <P>Like all exclusions under this Section 301 investigation, these technical amendments apply to entries of goods that are not liquidated or to entries that are liquidated, but not final.</P>
                <HD SOURCE="HD1">Annex</HD>
                <EXTRACT>
                    <P>1. Effective with respect to goods entered for consumption, or withdrawn from warehouse for consumption, on or after 12:01 a.m. eastern standard time on October 12, 2021, and through December 31, 2022, note 20(ttt)(iii)(50) to subchapter III of chapter 99 of the HTSUS is modified by deleting “each measuring not more than 98 cm by 52 cm by 17 cm,”.</P>
                    <P>2. Effective with respect to goods entered for consumption, or withdrawn from warehouse for consumption, on or after 12:01 a.m. eastern standard time on October 12, 2021, and through December 31, 2022, note 20(ttt)(iii)(51) to subchapter III of chapter 99 of the HTSUS is modified by deleting “each measuring not more than 81 cm by 39 cm by 11 cm,”.</P>
                </EXTRACT>
                <SIG>
                    <NAME>Greta Peisch,</NAME>
                    <TITLE>General Counsel, Office of the United States Trade Representative.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22355 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3390-F3-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="62487"/>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Motor Carrier Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. FMCSA-2013-0122; FMCSA-2013-0123; FMCSA-2013-0125; FMCSA-2014-0102; FMCSA-2014-0107; FMCSA-2015-0327; FMCSA-2015-0328; FMCSA-2015-0329; FMCSA-2017-0057; FMCSA-2017-0059; FMCSA-2017-0060; FMCSA-2018-0139; FMCSA-2019-0109; FMCSA-2019-0111; FMCSA-2020-0024; FMCSA-2020-0025]</DEPDOC>
                <SUBJECT>Qualification of Drivers; Exemption Applications; Hearing</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Motor Carrier Safety Administration (FMCSA), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of final disposition.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>FMCSA announces its decision to renew exemptions for 40 individuals from the hearing requirement in the Federal Motor Carrier Safety Regulations (FMCSRs) for interstate commercial motor vehicle (CMV) drivers. The exemptions enable these hard of hearing and deaf individuals to continue to operate CMVs in interstate commerce.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Each group of renewed exemptions were applicable on the dates stated in the discussions below and will expire on the dates provided below.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ms. Christine A. Hydock, Chief, Medical Programs Division, (202) 366-4001, 
                        <E T="03">fmcsamedical@dot.gov,</E>
                         FMCSA, DOT, 1200 New Jersey Avenue SE, Room W64-224, Washington, DC 20590-0001. Office hours are from 8:30 a.m. to 5 p.m., ET, Monday through Friday, except Federal holidays. If you have questions regarding viewing or submitting material to the docket, contact Dockets Operations, (202) 366-9826.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Public Participation</HD>
                <HD SOURCE="HD2">A. Viewing Comments</HD>
                <P>
                    To view comments go to 
                    <E T="03">www.regulations.gov.</E>
                     Insert the docket number, FMCSA-2013-0122, FMCSA-2013-0123, FMCSA-2013-0125, FMCSA-2014-0102, FMCSA-2014-0107, FMCSA-2015-0327, FMCSA-2015-0328, FMCSA-2015-0329, FMCSA-2017-0057, FMCSA-2017-0059, FMCSA-2017-0060, FMCSA-2018-0139, FMCSA-2019-0109, FMCSA-2019-0111, FMCSA-2020-0024, or FMCSA-2020-0025 in the keyword box, and click “Search.” Next, sort the results by “Posted (Newer-Older),” choose the first notice listed, and click “Browse Comments.” If you do not have access to the internet, you may view the docket online by visiting Dockets Operations in Room W12-140 on the ground floor of the DOT West Building, 1200 New Jersey Avenue SE, Washington, DC 20590-0001, between 9 a.m. and 5 p.m., ET, Monday through Friday, except Federal holidays. To be sure someone is there to help you, please call (202) 366-9317 or (202) 366-9826 before visiting Dockets Operations.
                </P>
                <HD SOURCE="HD2">B. Privacy Act</HD>
                <P>
                    In accordance with 49 U.S.C. 31315(b)(6), DOT solicits comments from the public on the exemption request. DOT posts these comments, without edit, including any personal information the commenter provides, to 
                    <E T="03">www.regulations.gov.</E>
                     As described in the system of records notice (DOT/ALL-14 FDMS), which can be reviewed at 
                    <E T="03">www.dot.gov/privacy,</E>
                     the comments are searchable by the name of the submitter.
                </P>
                <HD SOURCE="HD1">II. Background</HD>
                <P>On August 10, 2022, FMCSA published a notice announcing its decision to renew exemptions for 40 individuals from the hearing standard in 49 CFR 391.41(b)(11) to operate a CMV in interstate commerce and requested comments from the public (87 FR 48749). The public comment period ended on September 9, 2022, and no comments were received.</P>
                <P>FMCSA has evaluated the eligibility of these applicants and determined that renewing these exemptions would achieve a level of safety equivalent to, or greater than, the level that would be achieved by complying with § 391.41(b)(11).</P>
                <P>The physical qualification standard for drivers regarding hearing found in § 391.41(b)(11) states that a person is physically qualified to drive a CMV if that person first perceives a forced whispered voice in the better ear at not less than 5 feet with or without the use of a hearing aid or, if tested by use of an audiometric device, does not have an average hearing loss in the better ear greater than 40 decibels at 500 Hz, 1,000 Hz, and 2,000 Hz with or without a hearing aid when the audiometric device is calibrated to American National Standard (formerly ASA Standard) Z24.5-1951.</P>
                <P>This standard was adopted in 1970 and was revised in 1971 to allow drivers to be qualified under this standard while wearing a hearing aid, 35 FR 6458, 6463 (Apr. 22, 1970) and 36 FR 12857 (July 3, 1971).</P>
                <HD SOURCE="HD1">III. Discussion of Comments</HD>
                <P>FMCSA received no comments in this proceeding.</P>
                <HD SOURCE="HD1">IV. Conclusion</HD>
                <P>Based upon its evaluation of the 40 renewal exemption applications, FMCSA announces its decision to exempt the following drivers from the hearing requirement in § 391.41 (b)(11).</P>
                <P>As of June 17, 2022, and in accordance with 49 U.S.C. 31136(e) and 31315(b), the following 23 individuals have satisfied the renewal conditions for obtaining an exemption from the hearing requirement in the FMCSRs for interstate CMV drivers (87 FR 48749):</P>
                <FP SOURCE="FP-1">Paul Aseka (TX)</FP>
                <FP SOURCE="FP-1">James Bogart (KS)</FP>
                <FP SOURCE="FP-1">Thomas Buretz (FL)</FP>
                <FP SOURCE="FP-1">Forrest Carroll (OH)</FP>
                <FP SOURCE="FP-1">Glenn Ferguson (TX)</FP>
                <FP SOURCE="FP-1">Ariel Gonzalez (RI)</FP>
                <FP SOURCE="FP-1">Nicholas Green (FL)</FP>
                <FP SOURCE="FP-1">Richard Hadlock (IL)</FP>
                <FP SOURCE="FP-1">Sean Hunt (SC)</FP>
                <FP SOURCE="FP-1">Jesus Javier (NJ)</FP>
                <FP SOURCE="FP-1">Larry Lang (TX)</FP>
                <FP SOURCE="FP-1">Yoel Lopez-Perez (FL)</FP>
                <FP SOURCE="FP-1">Bryan MacFarlane (OH)</FP>
                <FP SOURCE="FP-1">Darren Nordquist (WI)</FP>
                <FP SOURCE="FP-1">Anthony Panto (NJ)</FP>
                <FP SOURCE="FP-1">Ernst Pratt (PA)</FP>
                <FP SOURCE="FP-1">Brian Shoup (SC)</FP>
                <FP SOURCE="FP-1">William Symonds (IL)</FP>
                <FP SOURCE="FP-1">Steven Tipton (IA)</FP>
                <FP SOURCE="FP-1">Daniel Tricolici (MA)</FP>
                <FP SOURCE="FP-1">Wayne Turner (IL)</FP>
                <FP SOURCE="FP-1">Fernando Velasquez (TX)</FP>
                <FP SOURCE="FP-1">Scott Weeaks (OK)</FP>
                <P>The drivers were included in docket number FMCSA-2013-0122, FMCSA-2013-0123, FMCSA-2013-0125, FMCSA-2014-0107, FMCSA-2015-0327, FMCSA-2015-0328, FMCSA-2015-0329, FMCSA-2017-0057, FMCSA-2017-0059, FMCSA-2018-0139, FMCSA-2019-0109, FMCSA-2019-0111, or FMCSA-2020-0024. Their exemptions were applicable as of June 17, 2022 and will expire on June 17, 2024.</P>
                <P>As of June 18, 2022, and in accordance with 49 U.S.C. 31136(e) and 31315(b), the following seven individuals have satisfied the renewal conditions for obtaining an exemption from the hearing requirement in the FMCSRs for interstate CMV drivers (87 FR 48749):</P>
                <FP SOURCE="FP-1">Joshua Affholter (MI)</FP>
                <FP SOURCE="FP-1">Gantulga Badarach (IL)</FP>
                <FP SOURCE="FP-1">Awash Demoz (MD)</FP>
                <FP SOURCE="FP-1">Muhammad Javed (IN)</FP>
                <FP SOURCE="FP-1">Charles O'Bryan (NY)</FP>
                <FP SOURCE="FP-1">Anna Ruiz (AZ)</FP>
                <FP SOURCE="FP-1">Kyle Taylor (GA)</FP>
                <P>
                    The drivers were included in docket number FMCSA-2020-0025. Their 
                    <PRTPAGE P="62488"/>
                    exemptions were applicable as of June 18, 2022 and will expire on June 18, 2024.
                </P>
                <P>As of June 25, 2022, and in accordance with 49 U.S.C. 31136(e) and 31315(b), the following three individuals have satisfied the renewal conditions for obtaining an exemption from the hearing requirement in the FMCSRs for interstate CMV drivers (87 FR 48749):</P>
                <P>Alfredo Ramirez (TX); Julie Ramirez (TX); and Hayden Teesdale (TX).</P>
                <P>The drivers were included in docket number FMCSA-2014-0102. Their exemptions were applicable as of June 25, 2022 and will expire on June 25, 2024.</P>
                <P>As of June 29, 2022, and in accordance with 49 U.S.C. 31136(e) and 31315(b), the following seven individuals have satisfied the renewal conditions for obtaining an exemption from the hearing requirement in the FMCSRs for interstate CMV drivers (87 FR 48749):</P>
                <FP SOURCE="FP-1">Leroy Carter (OH)</FP>
                <FP SOURCE="FP-1">Robert Cates (NM)</FP>
                <FP SOURCE="FP-1">Brodey DiPasquale (MD)</FP>
                <FP SOURCE="FP-1">Richard Fisher (PA)</FP>
                <FP SOURCE="FP-1">Kimberly Foss (OR)</FP>
                <FP SOURCE="FP-1">Marcel Paul (WA)</FP>
                <FP SOURCE="FP-1">Jason Winemiller (IL)</FP>
                <P>The drivers were included in docket number FMCSA-2017-0060. Their exemptions were applicable as of June 29, 2022 and will expire on June 29, 2024.</P>
                <P>In accordance with 49 U.S.C. 31315(b), each exemption will be valid for 2 years from the effective date unless revoked earlier by FMCSA. The exemption will be revoked if the following occurs: (1) the person fails to comply with the terms and conditions of the exemption; (2) the exemption has resulted in a lower level of safety than was maintained prior to being granted; or (3) continuation of the exemption would not be consistent with the goals and objectives of 49 U.S.C. 31136(e) and 31315(b).</P>
                <SIG>
                    <NAME>Larry W. Minor,</NAME>
                    <TITLE>Associate Administrator for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22342 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-EX-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Motor Carrier Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. FMCSA-2022-0036]</DEPDOC>
                <SUBJECT>Qualification of Drivers; Exemption Applications; Hearing</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Motor Carrier Safety Administration (FMCSA), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of applications for exemption; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>FMCSA announces receipt of applications from 13 individuals for an exemption from the hearing requirement in the Federal Motor Carrier Safety Regulations (FMCSRs) to operate a commercial motor vehicle (CMV) in interstate commerce. If granted, the exemptions would enable these hard of hearing and deaf individuals to operate CMVs in interstate commerce.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before November 14, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by the Federal Docket Management System Docket No. FMCSA-2022-0036 using any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">www.regulations.gov/,</E>
                         insert the docket number, FMCSA-2022-0036, in the keyword box, and click “Search.” Next, sort the results by “Posted (Newer-Older),” choose the first notice listed, and click on the “Comment” button. Follow the online instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Dockets Operations; U.S. Department of Transportation, 1200 New Jersey Avenue SE, West Building Ground Floor, Room W12-140, Washington, DC 20590-0001.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE, Washington, DC 20590-0001, between 9 a.m. and 5 p.m., ET, Monday through Friday, except Federal Holidays.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (202) 493-2251.
                    </P>
                    <P>
                        To avoid duplication, please use only one of these four methods. See the “Public Participation” portion of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for instructions on submitting comments.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ms. Christine A. Hydock, Chief, Medical Programs Division, (202) 366-4001, 
                        <E T="03">fmcsamedical@dot.gov,</E>
                         FMCSA, DOT, 1200 New Jersey Avenue SE, Room W64-224, Washington, DC 20590-0001. Office hours are 8:30 a.m. to 5 p.m., ET, Monday through Friday, except Federal holidays. If you have questions regarding viewing or submitting material to the docket, contact Dockets Operations, (202) 366-9826.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Public Participation</HD>
                <HD SOURCE="HD2">A. Submitting Comments</HD>
                <P>If you submit a comment, please include the docket number for this notice (Docket No. FMCSA-2022-0036), indicate the specific section of this document to which each comment applies, and provide a reason for each suggestion or recommendation. You may submit your comments and material online or by fax, mail, or hand delivery, but please use only one of these means. FMCSA recommends that you include your name and a mailing address, an email address, or a phone number in the body of your document so that FMCSA can contact you if there are questions regarding your submission.</P>
                <P>
                    To submit your comment online, go to 
                    <E T="03">www.regulations.gov/docket?D=FMCSA-2022-0036</E>
                    . Next, sort the results by “Posted (Newer-Older),” choose the first notice listed, click the “Comment” button, and type your comment into the text box on the following screen. Choose whether you are submitting your comment as an individual or on behalf of a third party and then submit.
                </P>
                <P>
                    If you submit your comments by mail or hand delivery, submit them in an unbound format, no larger than 8
                    <FR>1/2</FR>
                     by 11 inches, suitable for copying and electronic filing. If you submit comments by mail and would like to know that they reached the facility, please enclose a stamped, self-addressed postcard or envelope.
                </P>
                <P>FMCSA will consider all comments and material received during the comment period.</P>
                <HD SOURCE="HD2">B. Viewing Comments</HD>
                <P>
                    To view comments go to 
                    <E T="03">www.regulations.gov.</E>
                     Insert the docket number, FMCSA-2022-0036, in the keyword box, and click “Search.” Next, sort the results by “Posted (Newer-Older),” choose the first notice listed, and click “Browse Comments.” If you do not have access to the internet, you may view the docket online by visiting Dockets Operations in Room W12-140 on the ground floor of the DOT West Building, 1200 New Jersey Avenue SE, Washington, DC 20590-0001, between 9 a.m. and 5 p.m., ET, Monday through Friday, except Federal holidays. To be sure someone is there to help you, please call (202) 366-9317 or (202) 366-9826 before visiting Dockets Operations.
                    <PRTPAGE P="62489"/>
                </P>
                <HD SOURCE="HD2">C. Privacy Act</HD>
                <P>
                    In accordance with 49 U.S.C. 31315(b)(6), DOT solicits comments from the public on the exemption request. DOT posts these comments, without edit, including any personal information the commenter provides, to 
                    <E T="03">www.regulations.gov.</E>
                     As described in the system of records notice (DOT/ALL-14 FDMS), which can be reviewed at 
                    <E T="03">www.dot.gov/privacy,</E>
                     the comments are searchable by the name of the submitter.
                </P>
                <HD SOURCE="HD1">II. Background</HD>
                <P>Under 49 U.S.C. 31136(e) and 31315(b), FMCSA may grant an exemption from the FMCSRs for no longer than a 5-year period if it finds such exemption would likely achieve a level of safety that is equivalent to, or greater than, the level that would be achieved absent such exemption. The statute also allows the Agency to renew exemptions at the end of the 5-year period. FMCSA grants medical exemptions from the FMCSRs for a 2-year period to align with the maximum duration of a driver's medical certification.</P>
                <P>The 13 individuals listed in this notice have requested an exemption from the hearing requirement in 49 CFR 391.41(b)(11). Accordingly, the Agency will evaluate the qualifications of each applicant to determine whether granting the exemption will achieve the required level of safety mandated by statute.</P>
                <P>The physical qualification standard for drivers regarding hearing found in § 391.41(b)(11) states that a person is physically qualified to drive a CMV if that person first perceives a forced whispered voice in the better ear at not less than 5 feet with or without the use of a hearing aid or, if tested by use of an audiometric device, does not have an average hearing loss in the better ear greater than 40 decibels at 500 Hz, 1,000 Hz, and 2,000 Hz with or without a hearing aid when the audiometric device is calibrated to American National Standard (formerly ASA Standard) Z24.5-1951.</P>
                <P>This standard was adopted in 1970 and was revised in 1971 to allow drivers to be qualified under this standard while wearing a hearing aid, 35 FR 6458, 6463 (Apr. 22, 1970) and 36 FR 12857 (July 3, 1971).</P>
                <P>On February 1, 2013, FMCSA announced in a Notice of Final Disposition titled, “Qualification of Drivers; Application for Exemptions; National Association of the Deaf,” (78 FR 7479), its decision to grant requests from 40 individuals for exemptions from the Agency's physical qualification standard concerning hearing for interstate CMV drivers. Since that time the Agency has published additional notices granting requests from hard of hearing and deaf individuals for exemptions from the Agency's physical qualification standard concerning hearing for interstate CMV drivers.</P>
                <HD SOURCE="HD1">III. Qualifications of Applicants</HD>
                <HD SOURCE="HD2">Frank Darracott</HD>
                <P>Mr. Darracott, 54, holds a class A commercial learner's permit in Florida.</P>
                <HD SOURCE="HD2">Tonnette Garza</HD>
                <P>Ms. Garza, 44, holds a class E driver's license in Florida.</P>
                <HD SOURCE="HD2">Andrew Gibson</HD>
                <P>Mr. Gibson, 35, holds a class C driver's license in Texas.</P>
                <HD SOURCE="HD2">Tyler Harmount</HD>
                <P>Mr. Harmount, 22, holds a class C driver's license in California.</P>
                <HD SOURCE="HD2">Maxwell Latin</HD>
                <P>Mr. Latin, 31, holds a class C driver's license in Maryland.</P>
                <HD SOURCE="HD2">Paradise Larizza</HD>
                <P>Ms. Larizza, 28, holds a class C driver's license in Oregon.</P>
                <HD SOURCE="HD2">Hank Moore</HD>
                <P>Mr. Moore, 56, holds a class C driver's license in Kansas.</P>
                <HD SOURCE="HD2">Mayur Motiwale</HD>
                <P>Mr. Motiwale, 41, holds a class D driver's license in New Jersey.</P>
                <HD SOURCE="HD2">Michael Reed</HD>
                <P>Mr. Reed, 61, holds a class A commercial driver's license in Arkansas.</P>
                <HD SOURCE="HD2">Chad Smith</HD>
                <P>Mr. Smith, 43, holds a class D driver's license in Ohio.</P>
                <HD SOURCE="HD2">Justin Turner</HD>
                <P>Mr. Turner, 23, holds a class C driver's license in Texas.</P>
                <HD SOURCE="HD2">Cody Upchurch</HD>
                <P>Mr. Upchurch, 44, holds a class C driver's license in Texas.</P>
                <HD SOURCE="HD2">Thomas Williamson</HD>
                <P>Mr. Williamson, 22, holds a class D driver's license in Illinois.</P>
                <HD SOURCE="HD1">IV. Request for Comments</HD>
                <P>
                    In accordance with 49 U.S.C. 31136(e) and 31315(b), FMCSA requests public comment from all interested persons on the exemption petitions described in this notice. We will consider all comments received before the close of business on the closing date indicated under the 
                    <E T="02">DATES</E>
                     section of the notice.
                </P>
                <SIG>
                    <NAME>Larry W. Minor,</NAME>
                    <TITLE>Associate Administrator for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22341 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-EX-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. NHTSA-2021-0032]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Submission to the Office of Management and Budget for Review and Approval; Consolidated Vehicles' Owner's Manual Requirements for Motor Vehicles and Motor Vehicle Equipment</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Highway Traffic Safety Administration (NHTSA), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments on a reinstatement with modification of a previously approved information collection.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In compliance with the Paperwork Reduction Act of 1995 (PRA), this notice announces that the Information Collection Request (ICR) summarized below will be submitted to the Office of Management and Budget (OMB) for review and approval. The ICR describes the nature of the information collection and its expected burden. This document describes a collection of information for which NHTSA intends to seek OMB approval on Vehicle Owner's Manual Requirements for Motor Vehicles and Motor Vehicle Equipment.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before November 14, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments and recommendations for the proposed information collection, including suggestions for reducing burden, should be submitted to the Office of Management and Budget at 
                        <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                         To find this particular information collection, select “Currently under Review—Open for Public Comment” or use the search function.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For additional information or access to background documents, contact James Myers, NHTSA, 1200 New Jersey Avenue SE, West Building, Room W43-320, NRM-100, Washington, DC 20590. Mr. Myers' telephone number is 202-493-0031. Please identify the relevant collection of information by referring to its OMB Control Number.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <PRTPAGE P="62490"/>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Under the PRA (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), a Federal agency must receive approval from the Office of Management and Budget (OMB) before it collects certain information from the public and a person is not required to respond to a collection of information by a Federal agency unless the collection displays a valid OMB control number. In compliance with these requirements, this notice announces that the following information collection request will be submitted OMB.
                </P>
                <P>
                    A 
                    <E T="04">Federal Register</E>
                     notice with a 60-day comment period soliciting public comments on the following information collection was published on February 22, 2022.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Consolidated Vehicle Owner's Manual Requirements for Motor Vehicles and Motor Vehicle Equipment.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     2127-0541.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     N/A.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Request for reinstatement with modification of a previously approved collection of information.
                </P>
                <P>
                    <E T="03">Type of Review Requested:</E>
                     Regular.
                </P>
                <P>
                    <E T="03">Length of Approval Requested:</E>
                     Three years from date of approval.
                </P>
                <P>
                    <E T="03">Summary of the Collection of Information:</E>
                     The National Traffic and Motor Vehicle Act, authorizes the Secretary of Transportation (NHTSA by delegation), at 49 U.S.C. 30111, to issue Federal Motor Vehicle Safety Standards (FMVSS) that set performance standards for motor vehicles and items of motor vehicle equipment. Further, the Secretary (NHTSA by delegation) is authorized, at 49 U.S.C. 30117, to require manufacturers to provide information to first purchasers of motor vehicles or items of motor vehicle equipment related to performance and safety in printed materials that are attached to or accompany the motor vehicle or item of motor vehicle equipment. NHTSA has exercised this authority to require manufacturers to provide certain specified safety information to be readily available to consumers and purchasers of motor vehicles and items of motor vehicle equipment. This information is most often provided in vehicle owners' manuals and the requirements are found in 49 CFR parts 563, 571, and 575. This information collection request only covers requirements or requests to provide information that is not provided verbatim in the regulation or standard. The information requirements or requests are included in: Part 563, “Event data recorders;” FMVSS No. 108, “Lamps, reflective devices, and associated equipment;” FMVSS No. 110, “Tire selection and rims;” FMVSS No. 138, “Tire Pressure Monitoring Systems;” FMVSS No. 202a, “Head restraints;” FMVSS No. 205, “Glazing materials;” FMVSS No. 208, “Occupant crash protection;” FMVSS No. 210, “Seat belt assembly anchorages;” FMVSS No. 213, “Child restraint systems;” FMVSS No. 225, “Child restraint anchorage systems;” FMVSS No. 226, “Ejection mitigation;” FMVSS No. 303, “Fuel System Integrity of Compressed Natural Gas Vehicles;” section 575.103, “Truck-camper loading;” section 575.104, “Uniform tire quality grading standards;” and section 575.105, “Vehicle rollover.”
                </P>
                <P>
                    <E T="03">Part 563—Event data recorders.</E>
                     Section 563.11 requires manufacturers of vehicles equipped with event data recorders (EDRs) to provide a prescribed statement (provided verbatim) in the owner's manual,
                    <SU>1</SU>
                    <FTREF/>
                     which is not an information collection. Section 563.11 also states that the owner's manual may include additional information about the form, function, and capabilities of the EDR, in supplement to the required statement. This voluntary disclosure of information is an information collection for which NHTSA is seeking approval. There is a slight burden for respondents to include the voluntary additional information in their owner's manuals. The vehicle manufacturers which provide this additional information in the owner's manual incur minimal burden. We conservatively estimate that half of the 406 vehicle models for light duty vehicles will have owner's manuals that contain this supplemental information and that the burden for updating and reviewing this information will be 1 hour per model line. This would result in 203 annual burden hours (203 vehicle model lines × 1 hour of time × 1 manual per model).
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         49 CFR 563.11(a).
                    </P>
                </FTNT>
                <P>It is estimated that the word content in the owner's manual required by Part 563 would be 100 text words. Hence, the cost burden to vehicle manufacturers is estimated to be $30,566.25 (17,100,939 total vehicles × 50% of vehicles including added language in the owner's manuals × 100 text words × 1.1 production factor × 0.25 printing factor × $0.00013 per word). Cost burdens for this regulation were not included in the previous information collection request.</P>
                <P>
                    <E T="03">FMVSS No. 108, “Lamps, reflective devices, and associated equipment.”</E>
                     This standard requires that certain lamps and reflective devices with certain performance levels be installed on motor vehicles to assure that the roadway is properly illuminated, that vehicles can be readily seen, and the signals can be transmitted to other drivers sharing the road during day, night, and inclement weather. In addition to establishing performance requirements for those lamps and reflective devices, FMVSS No. 108 also contains provisions requiring manufacturers to provide instructions or information on the lighting device. FMVSS No. 108, S10.18.8.2 requires manufacturers to provide instructions for proper aiming of a vehicle's Vehicle Headlamp Aiming Device (VHAD) headlamps. FMVSS No. 108, S9.4.1.1 requires manufacturers to provide information regarding how to operate semiautomatic beam switching devices.
                </P>
                <P>NHTSA estimates 50% of vehicle models will offer adaptive driving beam headlighting systems on at least one trim level that will include a VHAD. Further, NHTSA estimates manufacturers will require 4 hours per each new vehicle model and 1 hour for carry-over vehicle models to gather the necessary VHAD aiming instructions for the owner's manual. FMVSS No. 108 permits each manufacturer a choice in placing headlamp aiming instruction in the owner's manual or on a label affixed to the vehicle. We estimate about half of the VHAD aiming applications would be on labels attached to the VHAD, with the remainder (50%) using information in the owner's manual to convey the necessary information. The annual burden hours required by FMVSS No. 108`s VHAD section in the owner's manual is 383 hours ((438 models × 0.5 use VHAD × 0.25 new models × 4 hours/model) + (438 models × 0.5 use VHAD × 0.75 non-new models × 1 hour/model)).</P>
                <P>We estimate that approximately 80% of new vehicle models include a semiautomatic beam switching device (SAB) on at least one trim level for the U.S. market. For new model vehicles the time to collect, prepare, and review the required information is estimated to be 4 hours per manual. For carry-over vehicles, we estimate 1 hour to review the required information for continued accuracy. The annual burden hours required by FMVSS No. 108's semiautomatic beam switching device section in the owner's manual is 613 hours ((438 models × 0.8 offer SABs × 0.25 new models × 4 hours/model) + (438 models × 0.8 offer SABs × 0.75 non-new models × 1 hour/model)).</P>
                <P>
                    The annual printing annual cost burden to the respondents to include the information required by FMVSS No. 108's VHAD section in the owner's manual is $38,208 (17,100,000 vehicles × 0.5 use VHAD × 0.5 provide info in manual × 250 words of text × 1.1 production factor × 0.25 printing factor 
                    <PRTPAGE P="62491"/>
                    × $0.00013 per word). The annual printing cost burden to the respondents to include the information required by FMVSS No. 108's semiautomatic beam switching device section in the owner's manual is $244,530 (17,100,000 vehicles × 0.8 use SABs × 500 words of text × 1.1 production factor × 0.25 printing factor × $0.00013 per word).
                </P>
                <P>
                    <E T="03">FMVSS No. 110, “Tire selection and rims.”</E>
                     This standard specifies requirements for tire selection to prevent tire overloading. The vehicle's normal load and maximum load on the tire shall not be greater than applicable specified limits. The standard requires a permanently affixed vehicle placard specifying vehicle capacity weight, designated seating capacity, manufacturer-recommended cold tire inflation pressure, and manufacturer's recommended tire size. The standard further specifies rim construction requirements, load limits of non-pneumatic spare tires, and labeling requirements for non-pneumatic spare tires, including a required placard. Owner's manual information is required for non-pneumatic spare tires.
                </P>
                <P>Currently, manufacturers do not equip current passenger vehicles, trucks, buses, trailers, or motorcycles with non-pneumatic spare tires. If vehicles were equipped with non-pneumatic spare tires, the number of annual burden hours imposed on manufacturers who choose to equip their vehicles with this equipment would be determined from the number of model lines produced annually (of which an estimated 25% are new and 75% are on-new, a repeat of previous years' model lines) multiplied by the portion of vehicle models equipped with non-pneumatic spare tires multiplied by the estimated number of hours required to assemble the required information (estimated to be 4 hours of review for new vehicles and 1 hour to review the information for non-new vehicles). The product of these factors would provide the number of hours required by manufacturers to produce necessary information to place into an owner's manual “master” for printing. The printing cost burden for these owner's manuals would be the number of vehicles produced annually multiplied by the portion of vehicles equipped with non-pneumatic spare tires, multiplied by certain printing factors (an estimated 500 text words required per owner's manual, a 1.1 multiplier to account for aftermarket manuals, a 0.25 printing factor, and a $0.00013 cost per word). Because manufacturers do not equip current passenger vehicles, trucks, buses, trailers, or motorcycles with non-pneumatic spare tires, NHTSA estimates the hour burden as 0 hours, and the printing cost at $0.</P>
                <P>
                    <E T="03">FMVSS No. 138, “Tire pressure monitoring systems.”</E>
                     This standard specifies requirements for a tire pressure monitoring system to warn the driver of an under-inflated tire condition. Its purpose is to reduce the likelihood of a vehicle crash resulting from tire failure due to operation in an under-inflated condition. The standard requires the owner's manual to include specific information on the low-pressure warning telltale and the malfunction indicator telltale.
                </P>
                <P>The information required by FMVSS No. 138 to be included in the owner's manual is provided verbatim and may be taken from the Federal regulation in its entirety. FMVSS No. 138, also states that the owner's manual may include additional information about the low-pressure telltale and the malfunction indicator telltale. NHTSA estimates the burden to be 1 hour for the respondents to format their owner's manuals to include the text and additional information. There is an average of 438 model lines each year that include tire pressure monitoring information in the owner's manual. Therefore, NHTSA estimates the total annual burden hours for § 571.138 to be 438 hours (438 model lines × 1 manual per model × 1 hour).</P>
                <P>It is estimated that the information required by FMVSS No. 138 in the owner's manual is equivalent to 400 words of text. This would result in $244,530 in cost burden to the respondents (17,100,000 vehicles × 400 words of text × 1.1 production factor × 0.25 printing factor × $0.00013 per word).</P>
                <P>
                    <E T="03">FMVSS No. 202a, “Head restraints.”</E>
                     This standard specifies requirements for head restraints. The standard, which seeks to reduce whiplash injuries in rear collisions, currently requires head restraints for front outboard designated seating positions in passenger cars and in light multipurpose passenger vehicles, trucks and buses with a gross vehicle weight rating of 4,536 kg or less and specifies requirements for optionally provided rear outboard seat head restraints in the same vehicles. The standard requires that vehicle manufacturers include information in owner's manuals for vehicles manufactured on or after September 1, 2008. The owner's manual must clearly identify which seats are equipped with head restraints. If the head restraints are removable, the owner's manual must provide instructions on how to remove the head restraint by a deliberate action distinct from any act necessary for adjustment, and how to reinstall the head restraints. The owner's manual must warn that all head restraints must be reinstalled to properly protect vehicle occupants. Finally, the owner's manual must describe, in an easily understandable format, the adjustment of the head restraints and/or seat back to achieve appropriate head restraint position relative to the occupant's head.
                </P>
                <P>It is estimated that 438 model lines need to be reviewed annually, but only a fraction (25 percent) need major revision each year. It is further estimated that it would take 5 hours to complete the major revisions. The remaining fraction of model lines (75 percent) only require reverification of existing information. The total annual burden hours are estimated to be 876 hours (438 model lines × 0.25 needing revision × 5 hours plus 438 model lines × 0.75 needing revision × 1 hour).</P>
                <P>The word count required to disclose the required head restraint information in the owner's manual is estimated to be 1,200 words. The annual cost burden to the respondents to include the information required by FMVSS No. 202a in the owner's manual is $733,590 (17,100,000 vehicles × 1,200 words of text × 1.1 production factor × 0.25 printing factor × $0.00013 per word).</P>
                <P>
                    <E T="03">FMVSS No. 205, “Glazing materials.”</E>
                     This standard specifies requirements for all glazing material used in windshields, windows, and interior partitions of motor vehicles. Its purpose is to reduce injuries resulting from impact to glazing surfaces, to ensure a necessary degree of transparency in motor vehicle windows for driver visibility, and to minimize the possibility of occupants being thrown through the vehicle windows in collisions. More detailed information regarding the care and maintenance of plastic glazing items, such as a glass-plastic windshield, is required to be placed in the vehicle owner's manual.
                </P>
                <P>It is estimated that the burden to provide information in the owner's manual for detailed care and maintenance is minimal because manufacturers already provide this type of information in the vehicle cleaning and maintenance section of the owner's manual. NHTSA estimates a burden for each manual of 1 hour because manufacturers would need to verify that detailed care and maintenance information has been included in their cleaning and maintenance section of the owner's manual. The annual estimated burden from § 571.205 is 176.0 hours (176 model lines × 1 manual per model × 1 hour).</P>
                <P>
                    The word count required in the owner's manual is estimated to be 210 words. Only buses and low speed vehicles currently use plastic type glazing, so NHTSA estimates there are 
                    <PRTPAGE P="62492"/>
                    17,400 new vehicles each year that include glazing information in the owner's manual. The annual cost burden to the respondents to include the information required by FMVSS No. 205 is $130.15 (17,400 vehicles × 210 words of text × 1.1 production factor × 0.25 printing factor × $0.00013 per word).
                </P>
                <P>
                    <E T="03">FMVSS No. 208, “Occupant crash protection.”</E>
                     This standard specifies requirements for both active and passive occupant crash protection systems for passenger cars, multipurpose passenger vehicles, trucks, and small buses. Certain safety features, such as air bags, or the care and maintenance of air bag systems, are required to be explained to the owner by means of the owner's manual. For example, the owner's manual must describe the vehicle's air bag system and provide precautionary information about the proper positioning of the occupants, including children. The owner's manual must also warn that no objects should be placed over or near the air bag covers. There is also required information about the operation of seat belt assemblies and other information that could total up to about 20 pages in the owner's manual. This material would also need to be kept current with the latest technical information on an annual basis.
                </P>
                <P>A conservative estimated burden to produce the required text and information is 16 hours (or 2 days). It is also estimated that a fraction (25 percent) of the model lines would require updates annually. The remaining fraction of model lines (75 percent) only require reverification (1-hour burden) of existing information. This would result in 2,750 annual burden hours (579 vehicle model lines × 0.25 percent that need updating × 16 hours of time plus 579 model lines × 0.75 needing revision × 1 hour).</P>
                <P>It is estimated that the word content in the owner's manual required by FMVSS No. 208 would be 5,400 text words. Hence, the cost burden to vehicle manufacturers is estimated to be $3,397,680 (17,600,000 total vehicles × 5,400 text words × 1.1 production factor × 0.25 printing factor × $0.00013 per word).</P>
                <P>
                    <E T="03">FMVSS No. 210, “Seat belt assembly anchorages.”</E>
                     This standard specifies requirements for seat belt assembly anchorages to ensure effective occupant restraint and to reduce the likelihood of failure in a crash. FMVSS No. 210 requires that manufacturers place the following information in the vehicle owner's manual: (a) an explanation that child restraints are designed to be secured by means of the vehicle's seat belts, and (b) a statement alerting vehicle owners that children are always safer in the rear seat.
                </P>
                <P>It is estimated that it would take a vehicle manufacturer no more than 1 hour per vehicle model line to assemble all of the FMVSS No. 210 information for inclusion in the owner's manual. This would result in 438 annual burden hours (438 vehicle model lines × 1 manual per model × 1 hour).</P>
                <P>It is estimated that the word content in the owner's manual required by FMVSS No. 210 would be 400 text words. Hence, the cost burden to vehicle manufacturers is estimated to be $244,530 (17,100,000 total vehicles × 400 text words × 1.1 production factor × 0.25 printing factor × $0.00013 per word).</P>
                <P>
                    <E T="03">FMVSS No. 213, “Child restraint systems.”</E>
                     This standard specifies requirements for child restraint systems and requires that manufacturers provide consumers with detailed information relating to child safety in air bag-equipped vehicles. The vehicle owner's manual must include information about the operation and do's and don'ts of built-in child seats. NHTSA estimates that there are no more than 20 vehicle models that are equipped with built-in child restraints. However, as stated in FMVSS No. 213, the information must be made available on strategically placed labels within the vehicles, in addition to the vehicle's owner's manual. Thus, it is assumed that the burden hours would be minimal since the information is already available from the information required to produce the labels. This would result in 20 annual burden hours (20 vehicle model lines × 1 manual per model × 1 hour).
                </P>
                <P>It is estimated that the recurring information required for child safety in the owner's manual would be 500 text words. NHTSA estimates that 5% of vehicles may be in lines that offer built in child restraints. Hence, the cost burden to vehicle manufacturers is estimated to be $15,730 (17,600,000 total vehicles × 5% × 500 text words × 1.1 production factor × 0.25 printing factor × $0.00013 per word).</P>
                <P>
                    <E T="03">FMVSS No. 225; “Child restraint anchorage systems.”</E>
                     This standard establishes requirements for child restraint anchorage systems to ensure their proper location and strength for the effective securing of child restraints, to reduce the likelihood of the anchorage systems' failure, and to increase the likelihood that child restraints are properly secured and thus more fully achieve their potential effectiveness in motor vehicles. The vehicle owner's manual must provide written instructions, in English, for using the tether anchorages and the child restraint anchorage system in the vehicle. Instructions must at a minimum indicate which seating positions in the vehicle are equipped with tether anchorages and child restraint anchorage systems, explain the meaning of markings provided to locate the lower anchorages, and include instructions that provide a step-by-step procedure (including diagrams) for properly attaching a child restraint system's tether strap to the tether anchorages.
                </P>
                <P>NHTSA estimates that it takes a vehicle manufacturer no more than 5 hours to compile the required material and that only a fraction (25 percent) would need major revisions each year. The remaining fraction of model lines (75 percent) only require reverification (1-hour burden) of existing information. This would result in 876 annual burden hours ((438 vehicle model lines × 1 manual per model × 0.25 (percent requiring major revisions) × 5 hours of time) + (438 model lines × 1 manual per model × 0.75 (percent requiring reverification) × 1 hour)).</P>
                <P>NHTSA estimates that the word content in the owner's manual required by FMVSS No. 225 would be 1,500 text words. Hence, the cost burden to vehicle manufacturers is estimated to be $943,800 (17,600,000 total vehicles × 1,500 text words × 1.1 production factor × 0.25 printing factor × $0.00013 per word).</P>
                <P>
                    <E T="03">FMVSS No. 226, “Ejection mitigation.”</E>
                     This standard establishes vehicle requirements intended to reduce the partial and complete ejection of vehicle occupants through side windows in crashes, particularly rollover crashes. The standard applies to passenger cars, and to multipurpose passenger vehicles, trucks, and buses with a gross vehicle weight rating of 4,536 kg (10,000 pounds) or less. Written information must be provided that describes any ejection mitigation countermeasure that deploys in the event of a rollover and a discussion of the readiness indicator with a list of the elements of the system being monitored by the indicator, a discussion of the purpose and location of the telltale, and instructions to the consumer on the steps to take if the telltale is illuminated.
                </P>
                <P>
                    It is estimated that it would take a vehicle manufacturer no more than 8 hours to compile the required material and it is estimated that a fraction (25 percent) would need major revisions each year. The remaining fraction of model lines (75 percent) only require reverification (1-hour burden) of existing information. This would result in 1,204.5 annual burden hours (438 
                    <PRTPAGE P="62493"/>
                    vehicle model lines × 1 manual per model × 0.25 (percent that need updating) × 8 hours of time plus 438 model lines × 1 manual per model × 0.75 (percent needing revision) × 1 hour).
                </P>
                <P>It is estimated that the word content in the owner's manual required by FMVSS No. 226 would be 3,000 text words. Hence, the cost burden to vehicle manufacturers is estimated to be $1,833,975 (17,100,000 total vehicles × 3,000 text words × 1.1 production factor × 0.25 printing factor × $0.00013 per word).</P>
                <P>
                    <E T="03">FMVSS No. 303, “Fuel System Integrity of Compressed Natural Gas Vehicles.”</E>
                     This standard specifies requirements for the integrity of motor vehicle fuel systems using compressed natural gas (CNG), including the CNG fuel systems of bi-fuel, dedicated, and dual fuel CNG vehicles. This regulation requires manufacturers to permanently label CNG vehicles, near the vehicle refueling connection, with service pressure information and the statement “See instructions on fuel container for inspection and service life.” Manufacturers of CNG vehicles shall also provide a first purchaser this information in either an owner's manual or a one-page document. The service pressure information required for the owner's manuals under FMVSS No. 303 is developed by manufacturers as part of their routine engineering development for their vehicles. Therefore, there is a slight burden of 1 hour for respondents to include this information in their owner's manuals. This would result in 18 annual burden hours (18 vehicle model lines × 1 manual per model × 1 hour of time).
                </P>
                <P>It is estimated that no more than 50 words are required in the owner's manual to comply with the requirements in FMVSS No. 303. There are conservatively 20,000 CNG vehicles produced annually. Hence, the cost burden to CNG vehicle manufacturers is estimated to be $35.75 (20,000 total units × 50 text words × 1.1 production factor × 0.25 printing factor × $0.00013 per word). Cost burdens for this regulation were not included in the previous information collection request.</P>
                <P>
                    <E T="03">Section 575.103, “Truck-camper loading.”</E>
                     This regulation requires manufacturers of slide-in campers to affix to each camper a label that contains information relating to identification and proper loading of the camper and to provide more detailed loading information in the owner's manual. This regulation also requires manufacturers of trucks that would accommodate slide-in campers to specify the cargo weight ratings and the longitudinal limits within which the center of gravity for the cargo weight rating should be located. The information required for the owner's manuals under section 575.103 is developed by manufacturers as part of their routine engineering development for their vehicles. The figures to include in truck and slide-in camper owner's manuals are provided in the regulation. Therefore, there is a slight 1-hour burden for respondents to include this information in their owner's manuals. This would result in 35 annual burden hours (35 vehicle model lines × 1 manual per model × 1 hour of time).
                </P>
                <P>It is estimated that 480 words are minimally required in the owner's manual to comply with § 575.103. There are approximately 2,300,000 pickup trucks and 11,000 truck camper units produced annually. These total to an annual production of 2,311,000 units. Hence, the cost burden to vehicle manufacturers is estimated to be $39,656.76 (2,311,000 total units × 480 text words × 1.1 production factor × 0.25 printing factor × $0.00013 per word).</P>
                <P>
                    <E T="03">Section 575.104, “Uniform tire quality grading standards.”</E>
                     This regulation requires manufacturers of motor vehicles to inform the drivers of the type and quality of the tires with which their vehicles are equipped. A statement, which manufacturers shall include in the owner's manual, is provided in the regulation in its entirety or equivalent form. Hence there is a slight 1-hour burden on the respondents for inclusion of this information into their owner's manuals. This would result in 579 annual burden hours (579 vehicle model lines × 1 manual per model × 1 hour of time).
                </P>
                <P>It is estimated that 390 words are minimally required in the owner's manual to comply with § 575.104. There are approximately 13,857,300 vehicles covered by this regulation. Hence, the cost burden to vehicle manufacturers is estimated to be $193,205.41 (13,857,300 total vehicles × 390 text words × 1.1 production factor × 0.25 printing factor × $0.00013 per word). Cost burdens for this regulation were not included in the previous information collection request.</P>
                <P>
                    <E T="03">Section 575.105, “Vehicle rollover.”</E>
                     This regulation requires manufacturers of utility vehicles 
                    <SU>2</SU>
                    <FTREF/>
                     to alert the drivers of those vehicles that they have a higher possibility of rollover than other vehicle types and to advise them of steps that can be taken to reduce the possibility of rollover and/or to reduce the likelihood of injury in a rollover. A statement, which manufacturers shall include in the owner's manual, is provided in the regulation in its entirety or equivalent form. Hence there is a slight 1-hour burden on the respondents for inclusion of this information into their owner's manuals. This would result in 18 annual burden hours (18 vehicle model lines × 1 manual per model × 1 hour of time).
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         49 CFR 575.105 states 
                        <E T="03">Utility vehicles</E>
                         means multipurpose passenger vehicles (other than those which are passenger car derivatives) which have a wheelbase of 110 inches or less and special features for occasional off-road operation.
                    </P>
                </FTNT>
                <P>It is estimated that 117 words are minimally required in the owner's manual to comply with § 575.105. There are approximately 2,700,000 utility vehicles with 4-wheel drive and a wheelbase of 110 inches or less. Therefore, the cost burden to vehicle manufacturers is estimated to be $11,293.43 (2,700,000 total vehicles × 117 text words × 1.1 production factor × 0.25 printing factor × $0.00013 per word). Cost burdens for this regulation were not included in the previous information collection request.</P>
                <P>
                    <E T="03">Description of the Need for the Information and Proposed Use of the Information:</E>
                </P>
                <P>The purpose of requiring certain information to be provided in manuals is to ensure owners and operators are provided with readily accessible important information about critical components of their vehicles, such as the performance of their vehicle or instructions for proper operation. The Federal program for reducing highway fatalities, injuries and crashes is likely to be adversely affected if the information is not collected, since consumers would not be made readily aware of certain important safety provisions that apply to critical components of their vehicles and would not have a readily accessible source of information when circumstances require such information.</P>
                <P>
                    <E T="03">Earlier 60-Day Notice:</E>
                </P>
                <P>
                    A 
                    <E T="04">Federal Register</E>
                     Notice, 87 FR 9787, with a 60-day comment period soliciting comments on the following information collection was published on February 22, 2022. No comments were received for that notice.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Vehicle manufacturers.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     52.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On Occasion.
                </P>
                <P>
                    <E T="03">Number of Responses:</E>
                     52.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     8,628.
                </P>
                <P>
                    <E T="03">Estimated Total Combined Annual Burden Costs:</E>
                     $8,406,632.
                </P>
                <P>
                    The table below summarizes the total hour burden, associated labor costs, and printing cost estimates.
                    <PRTPAGE P="62494"/>
                </P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,r50,12,12">
                    <TTITLE>Table 1—Estimated Hour Burden and Associated Labor Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Part/section</CHED>
                        <CHED H="1">Brief title</CHED>
                        <CHED H="1">Estimated total annual burden hours</CHED>
                        <CHED H="1">Estimated total annual labor costs at $50.44/hour</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">563</ENT>
                        <ENT>Event Data Recorders</ENT>
                        <ENT>203</ENT>
                        <ENT>$10,239</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.108</ENT>
                        <ENT>Lighting-VHAD</ENT>
                        <ENT>383</ENT>
                        <ENT>19,319</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.108</ENT>
                        <ENT>Lighting-SABs</ENT>
                        <ENT>613</ENT>
                        <ENT>30,920</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.110</ENT>
                        <ENT>Tire Selection and Rims</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.138</ENT>
                        <ENT>Tire Pressure Monitoring</ENT>
                        <ENT>438</ENT>
                        <ENT>22,093</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.202a</ENT>
                        <ENT>Head Restraints</ENT>
                        <ENT>876</ENT>
                        <ENT>44,185</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.205</ENT>
                        <ENT>Glazing</ENT>
                        <ENT>176</ENT>
                        <ENT>8,877</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.208</ENT>
                        <ENT>Crash Protection</ENT>
                        <ENT>2,750</ENT>
                        <ENT>138,710</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.210</ENT>
                        <ENT>Seat Belt Anchors</ENT>
                        <ENT>438</ENT>
                        <ENT>22,093</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.213</ENT>
                        <ENT>Child Restraints</ENT>
                        <ENT>20</ENT>
                        <ENT>1,009</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.225</ENT>
                        <ENT>Child Restraint Anchorages</ENT>
                        <ENT>876</ENT>
                        <ENT>44,185</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.226</ENT>
                        <ENT>Ejection Mitigation</ENT>
                        <ENT>1,205</ENT>
                        <ENT>60,755</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.303</ENT>
                        <ENT>CNG Fuel Systems</ENT>
                        <ENT>18</ENT>
                        <ENT>908</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">575.103</ENT>
                        <ENT>Truck-Camper Loading</ENT>
                        <ENT>35</ENT>
                        <ENT>1,765</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">575.104</ENT>
                        <ENT>Tire Quality</ENT>
                        <ENT>579</ENT>
                        <ENT>29,205</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">575.105</ENT>
                        <ENT>Utility Vehicles</ENT>
                        <ENT>18</ENT>
                        <ENT>908</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Totals</ENT>
                        <ENT/>
                        <ENT>8,628</ENT>
                        <ENT>435,171</ENT>
                    </ROW>
                </GPOTABLE>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s25,r100,12">
                    <TTITLE>Table 2—Estimated Printing Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Part/section</CHED>
                        <CHED H="1">Brief title</CHED>
                        <CHED H="1">
                            Estimated total costs to
                            <LI>respondents</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">563</ENT>
                        <ENT>Event Data Recorders</ENT>
                        <ENT>$30,566</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.108</ENT>
                        <ENT>Lighting-VHAD</ENT>
                        <ENT>38,208</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.108</ENT>
                        <ENT>Lighting-SABs</ENT>
                        <ENT>244,530</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.110</ENT>
                        <ENT>Tire Selection and Rims</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.138</ENT>
                        <ENT>Tire Pressure Monitoring Systems</ENT>
                        <ENT>244,530</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.202a</ENT>
                        <ENT>Head Restraints</ENT>
                        <ENT>733,590</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.205</ENT>
                        <ENT>Glazing</ENT>
                        <ENT>131</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.208</ENT>
                        <ENT>Occupant Crash Protection</ENT>
                        <ENT>3,397,680</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.210</ENT>
                        <ENT>Seat Belt Assembly Anchors</ENT>
                        <ENT>244,530</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.213</ENT>
                        <ENT>Child Restraints Systems</ENT>
                        <ENT>15,730</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.225</ENT>
                        <ENT>Child Restraint Anchorage Systems</ENT>
                        <ENT>943,800</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.226</ENT>
                        <ENT>Ejection Mitigation</ENT>
                        <ENT>1,833,975</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">571.303</ENT>
                        <ENT>Fuel System Integrity of Compressed Natural Gas Vehicles</ENT>
                        <ENT>36</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">575.103</ENT>
                        <ENT>Truck-Camper Loading</ENT>
                        <ENT>39,657</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">575.104</ENT>
                        <ENT>Uniform Tire Quality Grading Standards</ENT>
                        <ENT>193,205</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">575.105</ENT>
                        <ENT>Vehicle Rollover</ENT>
                        <ENT>11,293</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total Printing Costs</ENT>
                        <ENT/>
                        <ENT>7,971,461</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Public Comments Invited:</E>
                </P>
                <P>
                    You are asked to comment on any aspects of this information collection, including (a) whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; (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 the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses.
                </P>
                <P>
                    <E T="03">Authority:</E>
                     The Paperwork Reduction Act of 1995; 44 U.S.C. Chapter 35, as amended; 49 CFR 1.49; and DOT Order 1351.29.
                </P>
                <SIG>
                    <NAME>Raymond R. Posten,</NAME>
                    <TITLE>Associate Administrator for Rulemaking.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22298 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-59-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. NHTSA-2020-0071]</DEPDOC>
                <SUBJECT>Denial of Motor Vehicle Defect Petition, DP20-002</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Highway Traffic Safety Administration, (NHTSA), Department of Transportation.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Denial of a petition for a defect investigation.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This notice sets forth the reasons for the denial of a defect petition, DP20-002, submitted by Mr. V.T. Wakefield (the Petitioner) to NHTSA (the Agency) by a letter dated December 12, 2019. The petition 
                        <PRTPAGE P="62495"/>
                        requested that the Agency initiate a safety defect investigation of passenger compartment fires attributed to HVAC blower motor connectors overheating in Model Year (MY) 2006-2010 Pontiac Solstice and Saturn Sky vehicles (the “subject vehicles”). After conducting a technical review of: (1) consumer complaints identified by the petitioner; (2) consumer complaint information in NHTSA's databases; and (3) information provided by General Motors (GM) in response to the Agency's information request regarding vehicle fires and complaints received by GM, NHTSA's Office of Defect Investigations (ODI) has concluded that the issues raised by the petition do not warrant a defect investigation. Accordingly, the Agency has denied the petition.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Alexander Argant, Vehicle Defect Division A, Office of Defects Investigation, NHTSA 1200 New Jersey Avenue SE, Washington, DC 20590. Telephone: 202-366-8787. Email: 
                        <E T="03">alexander.argant@dot.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Introduction</HD>
                <P>
                    Interested persons may petition NHTSA requesting that the Agency initiate an investigation to determine whether a motor vehicle or an item of replacement equipment does not comply with an applicable motor vehicle safety standard or contains a defect that relates to motor vehicle safety. 49 U.S.C. 30162(a)(2); 49 CFR 552.1. Upon receipt of a properly filed petition, the Agency conducts a technical review of the petition, material submitted with the petition and any additional information. 49 U.S.C. 30162(a)(2); 49 CFR 552.6. The technical review may consist solely of a review of information already in the possession of the Agency or it may include the collection of information from the motor vehicle manufacturer and/or other sources. After conducting the technical review and considering appropriate factors, which may include, but are not limited to, the nature of the complaint, allocation of Agency resources, Agency priorities, the likelihood of uncovering sufficient evidence to establish the existence of a defect and the likelihood of success in any necessary enforcement litigation, the Agency will grant or deny the petition. 
                    <E T="03">See</E>
                     49 U.S.C. 30162(a)(2); 49 CFR 552.8.
                </P>
                <HD SOURCE="HD1">Background Information</HD>
                <P>In a letter dated December 12, 2019, the petitioner, Mr. V.T. Wakefield, requested that NHTSA initiate an investigation into passenger compartment fires in Model Years (MY) 2006-2010 Saturn Sky and Pontiac Solstice vehicles. The petitioner alleged the fires were caused by the overheating of the HVAC blower motor connector. The petitioner further alleged that Saturn Sky and Pontiac Solstice vehicles experience the same electrical problem (overheating HVAC blower resistor) addressed by NHTSA Safety Recall 15V-421, which involved MY2006-2010 Hummer H3 and 2009-2010 Hummer H3T vehicles. The petitioner's complaint reported that the affected parts in the Sky and Solstice vehicles are identical to those covered by Recall 15V-421.</P>
                <P>NHTSA has based its decision on a review of the material cited by the petitioner in his complaint and petition, information submitted by GM in response to the Agency's information request letter, and other pertinent information in NHTSA's databases.</P>
                <HD SOURCE="HD1">Summary of the Petition</HD>
                <P>The petitioner alleges that MY2006-2010 Saturn Sky and Pontiac Solstice vehicles can pose a fire risk due to the overheating of the HVAC blower motor connectors. The petitioner cites the fact the Sky and Solstice vehicles use the same blower motor parts as the Hummer H3 and H3T vehicles that were recalled under Safety Recall 15V-421 for a potential fire risk.</P>
                <P>GM filed Safety Recall 15V-421 on June 15, 2015 to remedy the connector module that controls the blower motor speed in the HVAC system of MY2006-2010 Hummer H3 and 2009-2010 Hummer H3T vehicles. The module may overheat under extended operational periods at high and medium-high blower speeds in those vehicles. The recall followed eleven (11) related fires affecting a fleet of 165,000 vehicles with five to ten years of time in service.</P>
                <HD SOURCE="HD1">Office of Defects Investigation Analysis</HD>
                <P>An analysis of General Motors (GM) complaint data and information in NHTSA's databases identified thirteen unique vehicle identification numbers (VINs) with reported incidents that could pertain to blower motor overheating, smoking, or melting in the 90,938 MY2006-2010 Saturn Sky and Pontiac Solstice vehicles produced. Two of the thirteen cited incidents reported smoke and thermal damage that may be attributed to the HVAC blower motor although neither incident was confirmed through vehicle inspection. One incident was with a MY2008 Saturn Sky that had substantial field exposure including a frontal crash that occurred one month prior to the August 2017 thermal incident. The Saturn Sky thermal incident was reported as plastic dripping from the dash and a fire in the carpet. A root cause could not be identified for this thermal event.</P>
                <P>The other incident was with a MY2007 Pontiac Solstice. The owner did not inform the manufacturer nor take their vehicle to a dealer for evaluation after reporting an electrical smell and observing smoke in the glove box in December 2016. No inspection of the vehicle was conducted.</P>
                <P>Most of the 13 incidents reported an overheated or discolored connector with attendant loss of HVAC blower fan function. GM reported 354 warranty claims with the subject components for the Sky and Solstice, none of which included a report of fire and only one report of smoke. Over a period of ten to fourteen years in service, there are two reports of smoke or thermal damage.</P>
                <P>While the subject Sky and Solstice vehicles and the recalled Hummer H3 and H3T vehicles do share common components, the Sky and Solstice vehicles have demonstrated very different behavior and the HVAC system has a lower power draw than the recalled Hummer H3 and H3T vehicles. The recalled H3 and H3T vehicles generate over triple the failure rate of the Sky and Solstice vehicles. GM suggested in its response to the Agency's information request that this difference was due to the larger interior volume of a recalled Hummer vehicle imposing a heavier electrical load and duty cycle on its HVAC blower. The duty cycle is defined as how long it takes for the vehicle to cool down enough before the HVAC blower motor fan speed is lowered or turned off completely.</P>
                <P>Additionally, due to the size differential between the Sky and Solstice vehicles and the recalled Hummer H3 and H3T vehicles, the parts have a different power draw. The Sky and Solstice vehicles, due to their smaller size, draw less wattage, which reduces the likelihood of a thermal event. This condition in the Sky and Solstice vehicles typically leads to an inoperable HVAC blower motor as opposed to a thermal event.</P>
                <P>
                    Despite the commonality of parts in the Sky and Solstice vehicles with those that were the basis of a safety recall, the subject vehicles have not demonstrated a safety defect trend that would likely lead to a safety recall or merit further investigation by the Agency. The subject vehicles have a low rate of reported thermal events over the ten to fourteen years they have been in service with the most recent occurring in 2017. The HVAC blower motor was not confirmed 
                    <PRTPAGE P="62496"/>
                    to be the root cause for either thermal event cited above.
                </P>
                <P>After thoroughly assessing the material submitted by the petitioner, information already in NHTSA's possession, information submitted by GM in response to an information request, and the potential risks to safety implicated by the petitioner's allegation, NHTSA does not believe that the petition warrants a formal investigation at this time. Consequently, the petition is denied. As with all potential motor vehicle safety risks, NHTSA will continue to review any new information or incidents as they are submitted to the Agency. The denial of this petition does not foreclose the Agency from taking further action if warranted or making a future finding that a safety-related defect exists based on additional information the Agency may receive.</P>
                <P>
                    <E T="03">Authority:</E>
                     49 U.S.C. 30162(d); delegations of authority at CFR1.95 and 501.8.
                </P>
                <SIG>
                    <NAME>Anne L. Collins,</NAME>
                    <TITLE>Associate Administrator for Enforcement.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22394 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-59-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. NHTSA-2022-0034]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Submission to the Office of Management and Budget for Review and Approval; Compliance Labeling Warning Devices</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Highway Traffic Safety Administration (NHTSA), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for public comment on the reinstatement of a previously approved collection of information.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In compliance with the Paperwork Reduction Act of 1995, this notice announces that the Information Collection Request (ICR) summarized below, regarding the reinstatement of a previously approved collection of information on Federal Motor vehicle Safety Standard (FMVSS) No. 125, will be submitted to the Office of Management and Budget for review and approval. The ICR describes the labeling requirement for warning devices and its expected burden. A 
                        <E T="04">Federal Register</E>
                         Notice with a 60-day comment period soliciting comments on the following information collection was published on May 3, 2022. No comments were received.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before November 14, 2022.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments and recommendations for the proposed information collection, including suggestions for reducing burden, should be submitted to the Office of Management and Budget at 
                        <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                         To find this particular information collection, select “Currently under Review—Open for Public Comment” or use the search function.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For additional information or access to background documents, contact Toyoaki Nogami, Office of Crash Avoidance Standards, National Highway Traffic Safety Administration, West Building—4th Floor—Room W43-462, 1200 New Jersey Avenue SE, Washington, DC 20590. He can be reached at (202) 366-1810. Please identify the relevant collection of information by referring to its OMB Control Number.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Under the PRA (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), a Federal agency must receive approval from the Office of Management and Budget (OMB) before it collects certain information from the public and a person is not required to respond to a collection of information by a Federal agency unless the collection displays a valid OMB control number. In compliance with these requirements, this notice announces that the following information collection request will be submitted OMB.
                </P>
                <P>
                    A 
                    <E T="04">Federal Register</E>
                     notice with a 60-day comment period soliciting public comments on the following information collection was published on May 3, 2022 (87 FR 26253).
                </P>
                <P>
                    <E T="03">Title:</E>
                     49 CFR 571.125. Standard No. 125; Warning devices, Compliance Labeling of Warning Devices.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     2127-0506.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Reinstatement of a previously approved information.
                </P>
                <P>
                    <E T="03">Type of Review Requested:</E>
                     Regular.
                </P>
                <P>
                    <E T="03">Length of Approval Requested:</E>
                     Three years from date of approval.
                </P>
                <P>
                    <E T="03">Summary of the Collection of Information:</E>
                     The National Traffic and Motor Vehicle Safety Act of 1966, authorizes the Secretary of Transportation (NHTSA by delegation), at 49 U.S.C. 30111 to issue Federal Motor Vehicle Safety Standards (FMVSS) that set performance standards for motor vehicles and items of motor vehicle equipment. 49 U.S.C. 30115 (
                    <E T="03">https://www.govinfo.gov/link/uscode/49/30115</E>
                    ) requires manufacturers of motor vehicles or motor vehicle equipment to certify that the vehicle or equipment complies with applicable motor vehicle safety standards prescribed under this chapter. Section 30115 further specifies that certification of equipment may be shown by a label or tag on the equipment or on the outside of the container in which the equipment is delivered to certify that items of motor vehicle equipment subject to FMVSS comply with all applicable standards. Further, the Secretary (NHTSA by delegation) is authorized, at 49 U.S.C. 30117 (
                    <E T="03">https://www.govinfo.gov/link/uscode/49/30117</E>
                    ), to require manufacturers to provide information to first purchasers of motor vehicles or motor vehicle equipment when the vehicle or equipment is purchased, in the form of printed matter placed in the vehicle or attached to the vehicle or motor vehicle equipment.
                </P>
                <P>Federal Motor Vehicle Safety Standard (FMVSS) No. 125, “Warning devices” specifies requirements for devices, without self-containing energy sources, that are designed to be carried in buses and trucks with a Gross Vehicle Weight Rating (GVWR) greater than 10,000 pounds, although they can be carried in other vehicles. These devices are used to warn approaching traffic of the presence of a stopped vehicle. This requirement does not apply to devices designed to be permanently affixed to the vehicle. The purpose of the standard is to reduce deaths and injuries due to rear end collisions between moving traffic and disabled vehicles. To ensure that the warning devices provide effective warnings to approaching traffic of the presence of a stopped vehicle, the standard sets forth specific requirements for the chromaticity of the reflex reflective material and fluorescent material affixed to both faces of the device.</P>
                <P>In addition to performance requirements, the FMVSS No. 125 requires manufacturers to permanently and legibly mark their warning devices with (a) the manufacturer's name, (b) the month and year of manufacture, and (c) the symbol DOT, or the statement that the warning device complies with all applicable FMVSS. Manufacturers must also provide, with each warning device they manufacture, instructions printed or attached to the device in a manner that cannot easily be removed, for the operator to understand its erection and placement and a recommendation that the driver activate the vehicle hazard warning signal lamps before leaving the vehicle.</P>
                <P>
                    Since the last notice, the total burden hours were revised from one hour to three hours based on the number of respondents and required reporting tasks. The total annual cost burden was 
                    <PRTPAGE P="62497"/>
                    revised from $26 to $4,075, and the number of responses increased from 2.85 million to 4.31 million based on the number of trucks registered in the United States. In addition, maintenance and materials costs were updated.
                </P>
                <P>
                    <E T="03">Description of the Need for the Information and Proposed Use of the Information:</E>
                     Manufacturers of warning devices are required to certify that their products meet the requirements of FMVSS No. 125. Without the identification information provided by the certification, NHTSA would be unable to identify the manufacturer of equipment that fails to meet the minimum performance for reflectivity and ability to withstand environmental conditions consistent with roadsides on which they are to be used. The instruction labeling also serves the safety purpose of FMVSS No. 125 by providing important information to operators, thereby increasing the likelihood of correct usage. Without labeling and instructions, a driver may not properly erect or place the warning devices in a manner that reduces the risk of rear end crashes with disabled vehicles. Federal Motor Carriers Safety Administration (FMCSA) also requires the placement of warning devices around buses and trucks that have a Gross Vehicle Weight Rating (GVWR) greater than 10,000 pounds, for warning to approaching traffic when they are disabled on a highway or shoulder. The labeling requirement assists FMCSA enforcement with the ability to verify that warning devices being used in commercial motor vehicles meet the minimum performance levels for safety.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Manufacturers of warning devices.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     3.
                </P>
                <P>The respondents are likely to be manufacturers of warning devices. The agency estimates that currently there are three manufacturers producing warning devices for use in motor vehicles.</P>
                <P>
                    <E T="03">Frequency:</E>
                     As needed.
                </P>
                <P>
                    <E T="03">Number of Responses:</E>
                     4,3200,000.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     3 hours.
                </P>
                <P>NHTSA was able to identify three manufacturers of warning devices. NHTSA estimates there are approximately 4.32 million labels affixed to warning devices each year.</P>
                <P>
                    This is based on the total number of truck tractors and other medium- and heavy-duty trucks registrations, which was 14,369,339 in 2019.
                    <SU>1</SU>
                    <FTREF/>
                     NHTSA estimates that 1 out of 10 trucks requires a new set of warning devices each year or, approximately 1.44 million (1,436,934 or rounded to 1.44 million), and each warning device requires three labels. Accordingly, NHTSA estimates that the three respondents produce 4.32 million labels each year, for an annual average of 1.44 million labels per respondent. Because the labels are molded onto the warning devices and cases, NHTSA estimates that the only time burden associated with this collection is time required to log the production of the molding presses in a highly-automated production process, which NHTSA estimates will take each manufacturer 1 hour per year. Accordingly, NHTSA estimates the total burden for this collection to be 3 hours (3 respondents × 1 hour). Using the estimate from the Bureau of Labor Statistics (BLS) for the average hourly compensation for Molders and Molding Machine Setters, Operators, and Tenders, Metal and Plastic (BLS Occupation code 51-4070) in the Motor Vehicle Manufacturing Industry, NHTSA estimate the loaded labor cost is $34.67 per hour.
                    <SU>2</SU>
                    <FTREF/>
                     Thus, the total labor cost associated with the burden hours is $104.01 for all responses generated by all 3 respondents together. Table 1 provides a summary of the estimated burden hours and labor costs associated with those submissions.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Bureau of Transportation Statistics, Table titled “Number of U.S. Truck Registrations by Type | Bureau of Transportation Statistics,” 
                        <E T="03">https://www.bts.gov/browse-statistical-products-and-data/national-transportation-statistics/number-us-truck.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The hourly wage is estimated to be $24.48 per hour. National Industry-Specific Occupational Employment and Wage Estimates NAICS 336100—Motor Vehicle Manufacturing, May 2020, 
                        <E T="03">https://www.bls.gov/oes/current/naics4_336100.htm#51-0000,</E>
                         last accessed November 5, 2021. The Bureau of Labor Statistics estimates that wages represent 70.6 percent of total compensation to private workers, on average. Bureau of Labor Statistics. Employer Costs for Employee Compensation—June 2021. 
                        <E T="03">https://www.bls.gov/news.release/ecec.t04.htm,</E>
                         last accessed November 5, 2021. Therefore, NHTSA estimates the total hourly compensation cost to be $34.67.
                    </P>
                </FTNT>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s25,12C,12C,12C,12C,12C">
                    <TTITLE>Table 1—Summary of Burden Hours and Associated Labor Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Estimated 
                            <LI>annual hour </LI>
                            <LI>burden per </LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>hourly </LI>
                            <LI>labor cost</LI>
                        </CHED>
                        <CHED H="1">
                            Annual labor 
                            <LI>cost per </LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual 
                            <LI>burden hours</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual 
                            <LI>labor costs</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">3</ENT>
                        <ENT>1 hour</ENT>
                        <ENT>
                            $34.67 
                            <SU>2</SU>
                        </ENT>
                        <ENT>$34.67</ENT>
                        <ENT>3</ENT>
                        <ENT>$104.01</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Estimated Total Annual Burden Cost:</E>
                     $4,075 per year.
                </P>
                <P>NHTSA estimates that the total annual cost to respondents is $4,075.00, or $.00094 per response ($4,075 ÷ 4.32 million labels). This cost is comprised of the annualized cost of depreciation of purchase and modification of the equipment required for molding the labels onto the warning devices and cases and the annual cost of materials required for the labeling.</P>
                <P>The initial cost to the respondents was based on estimated costs for modifying the die-mold such that it creates the label during normal production. The cost to manufacturers of the label requirement is the amortization of the die mold modification and the additional material consumed. The labels are to be placed on every warning device manufactured. The labels are produced during the normal course of steady flow manufacturing operation without a direct time penalty. The sole method used for producing the label is a process by which the required information is molded into the parts and/or cases directly. The cost of modifying a die mold to include the required information is estimated to be $10,000 per mold. The typical life of a die-mold of this type is 30 years, for a straight-line depreciation of the molds ($10,000 divided by 30) equal to $333.33 per mold. Part of the required information is included on the molds that create the warning devices, while the remaining information (instructions) is included within the molds that create the cases that are supplied with the warning devices. Each of the three manufacturers is estimated to have 2 warning device molds and 2 case molds for a total of 12 molds. Accordingly, NHTSA estimates the total cost for equipment to be $4,000 per year (($333.33 × 4 molds) × 3 respondents = $4,000).</P>
                <P>
                    The additional material required to produce the instructions is expected to be very small because the engraving depth is approximately 0.1 mm with a text width of 0.5 mm and a length of 300 
                    <PRTPAGE P="62498"/>
                    mm, resulting in a volume of material of 1.5 mm
                    <SU>3</SU>
                     per warning device, or 6,480,000 mm
                    <SU>3</SU>
                     per year (1.5 × 4.32 million devices). The price of polypropylene is estimated at $1,100 per ton with a density of 0.95 g/cm
                    <SU>3</SU>
                     (1.0472 × 10−8 tons/mm
                    <SU>3</SU>
                    ). The total material price is thus estimated to be $74.64 ((1.0472 × 10−8 tons/mm
                    <SU>3</SU>
                    ) × $1,100 × 6,480,000 mm
                    <SU>3</SU>
                    ) per year, rounded to $75 per year.
                </P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12,12,12,12,12">
                    <TTITLE>Table 2—Summary of Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">
                            Estimated 
                            <LI>annual </LI>
                            <LI>depreciation cost per mold</LI>
                        </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>molds per </LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Annual 
                            <LI>cost per </LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual cost 
                            <LI>burden all </LI>
                            <LI>respondents</LI>
                        </CHED>
                    </BOXHD>
                    <ROW RUL="s">
                        <ENT I="01">Die Mold Cost</ENT>
                        <ENT>$333.33</ENT>
                        <ENT>4</ENT>
                        <ENT>$1,333.33</ENT>
                        <ENT>3</ENT>
                        <ENT>$4,000.00</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="22"> </ENT>
                        <ENT>Annual number of labels (m)</ENT>
                        <ENT>Annual number of labels per respondent (m)</ENT>
                        <ENT>Annual cost per respondent</ENT>
                        <ENT>Number of respondents</ENT>
                        <ENT>Total annual cost burden all respondents</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Material Cost</ENT>
                        <ENT>4.32</ENT>
                        <ENT>1.44</ENT>
                        <ENT>25.00</ENT>
                        <ENT>3</ENT>
                        <ENT>75.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total Costs</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>1,358.33</ENT>
                        <ENT/>
                        <ENT>4,075.00</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Public Comments Invited:</E>
                </P>
                <P>
                    You are asked to comment on any aspects of this information collection, including (a) whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; (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 the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses.
                </P>
                <P>
                    <E T="03">Authority:</E>
                     The Paperwork Reduction Act of 1995; 44 U.S.C. Chapter 35, as amended; 49 CFR 1.49; and DOT Order 1351.29.
                </P>
                <SIG>
                    <NAME>Raymond R. Posten,</NAME>
                    <TITLE>Associate Administrator for Rulemaking.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2022-22297 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-59-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBJECT>Departmental Offices; Debt Management Advisory Committee Meeting</SUBJECT>
                <P>Notice is hereby given, pursuant to 5 U.S.C. app. 2, 10(a)(2), that a meeting will be held at the United States Treasury Department, 15th Street and Pennsylvania Avenue NW, Washington, DC on November 1, 2022 at 9:00 a.m. of the following debt management advisory committee: Treasury Borrowing Advisory Committee.</P>
                <P>At this meeting, the Treasury is seeking advice from the Committee on topics related to the economy, financial markets, Treasury financing, and debt management. Following the working session, the Committee will present a written report of its recommendations. The meeting will be closed to the public, pursuant to 5 U.S.C. app. 2, 10(d) and Public Law 103-202, 202(c)(1)(B)(31 U.S.C. 3121 note).</P>
                <P>This notice shall constitute my determination, pursuant to the authority placed in heads of agencies by 5 U.S.C. app. 2, 10(d) and vested in me by Treasury Department Order No. 101-05, that the meeting will consist of discussions and debates of the issues presented to the Committee by the Secretary of the Treasury and the making of recommendations of the Committee to the Secretary, pursuant to Public Law 103-202, 202(c)(1)(B).</P>
                <P>Thus, this information is exempt from disclosure under that provision and 5 U.S.C. 552b(c)(3)(B). In addition, the meeting is concerned with information that is exempt from disclosure under 5 U.S.C. 552b(c)(9)(A). The public interest requires that such meetings be closed to the public because the Treasury Department requires frank and full advice from representatives of the financial community prior to making its final decisions on major financing operations. Historically, this advice has been offered by debt management advisory committees established by the several major segments of the financial community. When so utilized, such a committee is recognized to be an advisory committee under 5 U.S.C. app. 2, 3.</P>
                <P>Although the Treasury's final announcement of financing plans may not reflect the recommendations provided in reports of the Committee, premature disclosure of the Committee's deliberations and reports would be likely to lead to significant financial speculation in the securities market. Thus, this meeting falls within the exemption covered by 5 U.S.C. 552b(c)(9)(A).</P>
                <P>The Office of Debt Management is responsible for maintaining records of debt management advisory committee meetings and for providing annual reports setting forth a summary of Committee activities and such other matters as may be informative to the public consistent with the policy of 5 U.S.C. 552(b). The Designated Federal Officer or other responsible agency official who may be contacted for additional information is Fred Pietrangeli, Director for Office of Debt Management (202) 622-1876.</P>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>Frederick E. Pietrangeli,</NAME>
                    <TITLE>Director, Office of Debt Management.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22321 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-25-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
                <SUBJECT>Advisory Committee on Prosthetics and Special-Disabilities Programs, Amended Notice of Meeting</SUBJECT>
                <P>
                    The Department of Veterans Affairs (VA) gives notice under the Federal Advisory Committee Act (5 U.S.C. app. 2), that a meeting of the Federal 
                    <PRTPAGE P="62499"/>
                    Advisory Committee on Prosthetics and Special-Disabilities Programs will be held on Tuesday, October 25-Wednesday, October 26, 2022. The meeting will be a hybrid meeting, held in-person at VA Central Office, 810 Vermont Avenue NW, Washington, DC, Room 630, and virtually via WebEx. The meeting sessions will begin and end as follows:
                </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,p7,7/8,i1" CDEF="s25,r25">
                    <BOXHD>
                        <CHED H="1">Date</CHED>
                        <CHED H="1">
                            Time 
                            <LI>(Eastern standard time)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">October 25, 2022</ENT>
                        <ENT>9:00 a.m-3:00 p.m.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">October 26, 2022</ENT>
                        <ENT>9:00 a.m-1:00 p.m.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The meeting sessions are open to the public virtually.</P>
                <P>The purpose of the Committee is to advise the Secretary of Veterans Affairs on VA's prosthetics programs designed to provide state-of-the-art prosthetics and the associated rehabilitation research, development, and evaluation of such technology. The Committee also provides advice to the Secretary on special-disabilities programs, which are defined as any program administered by the Secretary to serve Veterans with spinal cord injuries, blindness or visual impairments, loss of extremities or loss of function, deafness or hearing impairment, and other serious incapacities in terms of daily life functions.</P>
                <P>On October 25, 2022, the Committee will convene open (hybrid) sessions on Recreation Therapy and Creative Arts Therapy Service, National Veterans Sports Programs and Special Events, Prosthetic and Sensory Aids Service, Rehabilitation Research and Development Service, and the Office of Integrated Veterans Care.</P>
                <P>On October 26, 2022, the Committee members will convene open (hybrid) sessions on Audiology and Speech Pathology Service and Blind Rehabilitation Service.</P>
                <P>
                    No time will be allocated at this meeting for receiving oral presentations from the public. However, the public may submit written statements for the Committee's review. Public comments may be received no later than October 17, 2022, for inclusion in the official meeting record. Please send these comments to Dr. Lauren Racoosin, Designated Federal Officer, Rehabilitation and Prosthetic Services, Veterans Health Administration at 
                    <E T="03">Lauren.Racoosin@va.gov.</E>
                </P>
                <P>
                    Members of the public should contact Dr. Lauren Racoosin, at 
                    <E T="03">Lauren.Racoosin@va.gov</E>
                     and provide your name, professional affiliation, email address, and phone number, who wish to obtain a copy of the agenda. Any member of the public wishing to attend or seeking additional information should contact Dr. Racoosin. Members of the public may attend the meeting only virtually due to room capacity limitations. To join, please use the WebEx link below: 
                    <E T="03">https://veteransaffairs.webex.com/veteransaffairs/j.php?MTID=m326ad3b10acfa27572452e9d1c6e1401.</E>
                </P>
                <FP SOURCE="FP-1">Audio Only 404.397.1596/Access Code 2761 980 5183.</FP>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>LaTonya L. Small,</NAME>
                    <TITLE>Federal Advisory Committee Management Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22378 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
                <SUBJECT>Veterans' Advisory Committee on Education, Notice of Meeting</SUBJECT>
                <P>The Department of Veterans Affairs gives notice under the Federal Advisory Committee Act, 5 U.S.C. app. 2., that the Veterans' Advisory Committee on Education (“Committee”) will meet on November 29, 2022-November 30, 2022, from 10 a.m. to 5 p.m., eastern standard time in Washington, DC. All sessions are open to the public.</P>
                <P>The purpose of the Committee is to advise the Secretary of Veterans Affairs on the administration of education and training programs for Veterans, Servicepersons, Reservists, and Dependents of Veterans including programs under chapters 30, 32, 33, 35, and 36 of title 38, and chapter 1606 of title 10, United States Code.</P>
                <P>During the meeting sessions, the Committee will hear reports from three subcommittees (Modernization, Veteran Vocational Education and Training Programs and Distance Learning) and will receive other updates and briefings.</P>
                <P>
                    Interested persons may attend virtually via Microsoft Teams. Please email 
                    <E T="03">EDUSTAENG.VBAVACO@va.gov</E>
                     prior to November 25, 2022 if you wish to attend or you can dial-in by phone (for audio only) at 1-872-701-0185 (Toll-Free) using the Conference ID: 503 072 155#.
                </P>
                <P>
                    Although no time will be allotted for receiving oral presentations from the public, individuals wishing to share information with the Committee may submit written statements for the Committee's review to Mr. Joseph Maltby, Designated Federal Official, Department of Veterans Affairs, by email at 
                    <E T="03">EDUSTAENG.VBAVACO@va.gov</E>
                    . Comments will be accepted until close of business on Monday, November 28, 2022. In the communication, the writers must identify themselves and state the organization or association they represent for inclusion in the official record.
                </P>
                <SIG>
                    <DATED>Dated: October 11, 2022.</DATED>
                    <NAME>Jelessa M. Burney,</NAME>
                    <TITLE>Federal Advisory Committee Management Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2022-22358 Filed 10-13-22; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8320-01-P</BILCOD>
        </NOTICE>
    </NOTICES>
    <VOL>87</VOL>
    <NO>198</NO>
    <DATE>Friday, October 14, 2022</DATE>
    <UNITNAME>Presidential Documents</UNITNAME>
    <PRESDOCS>
        <PRESDOCU>
            <EXECORD>
                <TITLE3>Title 3—</TITLE3>
                <PRES>
                    The President
                    <PRTPAGE P="62283"/>
                </PRES>
                <EXECORDR>Executive Order 14086 of October 7, 2022</EXECORDR>
                <HD SOURCE="HED">Enhancing Safeguards for United States Signals Intelligence Activities</HD>
                <FP>By the authority vested in me as President by the Constitution and the laws of the United States of America, it is hereby ordered as follows:</FP>
                <FP>
                    <E T="04">Section 1</E>
                    . 
                    <E T="03">Purpose.</E>
                     The United States collects signals intelligence so that its national security decisionmakers have access to the timely, accurate, and insightful information necessary to advance the national security interests of the United States and to protect its citizens and the citizens of its allies and partners from harm. Signals intelligence capabilities are a major reason we have been able to adapt to a dynamic and challenging security environment, and the United States must preserve and continue to develop robust and technologically advanced signals intelligence capabilities to protect our security and that of our allies and partners. At the same time, the United States recognizes that signals intelligence activities must take into account that all persons should be treated with dignity and respect, regardless of their nationality or wherever they might reside, and that all persons have legitimate privacy interests in the handling of their personal information. Therefore, this order establishes safeguards for such signals intelligence activities.
                </FP>
                <FP>
                    <E T="04">Sec. 2</E>
                    . 
                    <E T="03">Signals Intelligence Activities.</E>
                </FP>
                <P>
                    (a) 
                    <E T="03">Principles.</E>
                     Signals intelligence activities shall be authorized and conducted consistent with the following principles:
                </P>
                <FP SOURCE="FP1">(i) Signals intelligence activities shall be authorized by statute or by Executive Order, proclamation, or other Presidential directive and undertaken in accordance with the Constitution and with applicable statutes and Executive Orders, proclamations, and other Presidential directives.</FP>
                <FP SOURCE="FP1">(ii) Signals intelligence activities shall be subject to appropriate safeguards, which shall ensure that privacy and civil liberties are integral considerations in the planning and implementation of such activities so that:</FP>
                <P SOURCE="P1">(A) signals intelligence activities shall be conducted only following a determination, based on a reasonable assessment of all relevant factors, that the activities are necessary to advance a validated intelligence priority, although signals intelligence does not have to be the sole means available or used for advancing aspects of the validated intelligence priority; and</P>
                <P SOURCE="P1">(B) signals intelligence activities shall be conducted only to the extent and in a manner that is proportionate to the validated intelligence priority for which they have been authorized, with the aim of achieving a proper balance between the importance of the validated intelligence priority being advanced and the impact on the privacy and civil liberties of all persons, regardless of their nationality or wherever they might reside.</P>
                <FP SOURCE="FP1">(iii) Signals intelligence activities shall be subjected to rigorous oversight in order to ensure that they comport with the principles identified above.</FP>
                <P>
                    (b) 
                    <E T="03">Objectives.</E>
                     Signals intelligence collection activities shall be conducted in pursuit of legitimate objectives.
                </P>
                <FP SOURCE="FP1">
                    (i) 
                    <E T="03">Legitimate objectives.</E>
                </FP>
                <P SOURCE="P1">
                    (A) Signals intelligence collection activities shall be conducted only in pursuit of one or more of the following objectives:
                    <PRTPAGE P="62284"/>
                </P>
                <FP SOURCE="FP2">(1) understanding or assessing the capabilities, intentions, or activities of a foreign government, a foreign military, a faction of a foreign nation, a foreign-based political organization, or an entity acting on behalf of or controlled by any such foreign government, military, faction, or political organization, in order to protect the national security of the United States and of its allies and partners;</FP>
                <FP SOURCE="FP2">(2) understanding or assessing the capabilities, intentions, or activities of foreign organizations, including international terrorist organizations, that pose a current or potential threat to the national security of the United States or of its allies or partners;</FP>
                <FP SOURCE="FP2">(3) understanding or assessing transnational threats that impact global security, including climate and other ecological change, public health risks, humanitarian threats, political instability, and geographic rivalry;</FP>
                <FP SOURCE="FP2">(4) protecting against foreign military capabilities and activities;</FP>
                <FP SOURCE="FP2">(5) protecting against terrorism, the taking of hostages, and the holding of individuals captive (including the identification, location, and rescue of hostages and captives) conducted by or on behalf of a foreign government, foreign organization, or foreign person;</FP>
                <FP SOURCE="FP2">(6) protecting against espionage, sabotage, assassination, or other intelligence activities conducted by, on behalf of, or with the assistance of a foreign government, foreign organization, or foreign person;</FP>
                <FP SOURCE="FP2">(7) protecting against threats from the development, possession, or proliferation of weapons of mass destruction or related technologies and threats conducted by, on behalf of, or with the assistance of a foreign government, foreign organization, or foreign person;</FP>
                <FP SOURCE="FP2">(8) protecting against cybersecurity threats created or exploited by, or malicious cyber activities conducted by or on behalf of, a foreign government, foreign organization, or foreign person;</FP>
                <FP SOURCE="FP2">(9) protecting against threats to the personnel of the United States or of its allies or partners;</FP>
                <FP SOURCE="FP2">(10) protecting against transnational criminal threats, including illicit finance and sanctions evasion related to one or more of the other objectives identified in subsection (b)(i) of this section;</FP>
                <FP SOURCE="FP2">(11) protecting the integrity of elections and political processes, government property, and United States infrastructure (both physical and electronic) from activities conducted by, on behalf of, or with the assistance of a foreign government, foreign organization, or foreign person; and</FP>
                <FP SOURCE="FP2">(12) advancing collection or operational capabilities or activities in order to further a legitimate objective identified in subsection (b)(i) of this section.</FP>
                <P SOURCE="P1">(B) The President may authorize updates to the list of objectives in light of new national security imperatives, such as new or heightened threats to the national security of the United States, for which the President determines that signals intelligence collection activities may be used. The Director of National Intelligence (Director) shall publicly release any updates to the list of objectives authorized by the President, unless the President determines that doing so would pose a risk to the national security of the United States.</P>
                <FP SOURCE="FP1">
                    (ii) 
                    <E T="03">Prohibited objectives.</E>
                </FP>
                <P SOURCE="P1">(A) Signals intelligence collection activities shall not be conducted for the purpose of:</P>
                <FP SOURCE="FP2">(1) suppressing or burdening criticism, dissent, or the free expression of ideas or political opinions by individuals or the press;</FP>
                <FP SOURCE="FP2">(2) suppressing or restricting legitimate privacy interests;</FP>
                <FP SOURCE="FP2">(3) suppressing or restricting a right to legal counsel; or</FP>
                <FP SOURCE="FP2">(4) disadvantaging persons based on their ethnicity, race, gender, gender identity, sexual orientation, or religion.</FP>
                <P SOURCE="P1">
                    (B) It is not a legitimate objective to collect foreign private commercial information or trade secrets to afford a competitive advantage to United States companies and United States business sectors commercially. The 
                    <PRTPAGE P="62285"/>
                    collection of such information is authorized only to protect the national security of the United States or of its allies or partners.
                </P>
                <FP SOURCE="FP1">
                    (iii) 
                    <E T="03">Validation of signals intelligence collection priorities.</E>
                </FP>
                <P SOURCE="P1">(A) Under section 102A of the National Security Act of 1947, as amended (50 U.S.C. 3024), the Director must establish priorities for the Intelligence Community to ensure the timely and effective collection of national intelligence, including national intelligence collected through signals intelligence. The Director does this through the National Intelligence Priorities Framework (NIPF), which the Director maintains and presents to the President, through the Assistant to the President for National Security Affairs, on a regular basis. In order to ensure that signals intelligence collection activities are undertaken to advance legitimate objectives, before presenting the NIPF or any successor framework that identifies intelligence priorities to the President, the Director shall obtain from the Civil Liberties Protection Officer of the Office of the Director of National Intelligence (CLPO) an assessment as to whether, with regard to anticipated signals intelligence collection activities, each of the intelligence priorities identified in the NIPF or successor framework:</P>
                <FP SOURCE="FP2">(1) advances one or more of the legitimate objectives set forth in subsection (b)(i) of this section;</FP>
                <FP SOURCE="FP2">(2) neither was designed nor is anticipated to result in signals intelligence collection in contravention of the prohibited objectives set forth in subsection (b)(ii) of this section; and</FP>
                <FP SOURCE="FP2">(3) was established after appropriate consideration for the privacy and civil liberties of all persons, regardless of their nationality or wherever they might reside.</FP>
                <P SOURCE="P1">(B) If the Director disagrees with any aspect of the CLPO's assessment with respect to any of the intelligence priorities identified in the NIPF or successor framework, the Director shall include the CLPO's assessment and the Director's views when presenting the NIPF to the President.</P>
                <P>
                    (c) 
                    <E T="03">Privacy and civil liberties safeguards.</E>
                     The following safeguards shall fulfill the principles contained in subsections (a)(ii) and (a)(iii) of this section.
                </P>
                <FP SOURCE="FP1">
                    (i) 
                    <E T="03">Collection of signals intelligence.</E>
                </FP>
                <P SOURCE="P1">(A) The United States shall conduct signals intelligence collection activities only following a determination that a specific signals intelligence collection activity, based on a reasonable assessment of all relevant factors, is necessary to advance a validated intelligence priority, although signals intelligence does not have to be the sole means available or used for advancing aspects of the validated intelligence priority; it could be used, for example, to ensure alternative pathways for validation or for maintaining reliable access to the same information. In determining whether to collect signals intelligence consistent with this principle, the United States—through an element of the Intelligence Community or through an interagency committee consisting in whole or in part of the heads of elements of the Intelligence Community, the heads of departments containing such elements, or their designees—shall consider the availability, feasibility, and appropriateness of other less intrusive sources and methods for collecting the information necessary to advance a validated intelligence priority, including from diplomatic and public sources, and shall prioritize such available, feasible, and appropriate alternatives to signals intelligence.</P>
                <P SOURCE="P1">
                    (B) Signals intelligence collection activities shall be as tailored as feasible to advance a validated intelligence priority and, taking due account of relevant factors, not disproportionately impact privacy and civil liberties. Such factors may include, depending on the circumstances, the nature of the pursued objective; the feasible steps taken to limit the scope of the collection to the authorized purpose; the intrusiveness of the collection activity, including its duration; the probable contribution of the collection to the objective pursued; the reasonably foreseeable consequences to individuals, including unintended third parties; the nature and sensitivity 
                    <PRTPAGE P="62286"/>
                    of the data to be collected; and the safeguards afforded to the information collected.
                </P>
                <P SOURCE="P1">(C) For purposes of subsection (c)(i) of this section, the scope of a specific signals intelligence collection activity may include, for example, a specific line of effort or target, as appropriate.</P>
                <FP SOURCE="FP1">
                    (ii) 
                    <E T="03">Bulk collection of signals intelligence.</E>
                </FP>
                <P SOURCE="P1">(A) Targeted collection shall be prioritized. The bulk collection of signals intelligence shall be authorized only based on a determination—by an element of the Intelligence Community or through an interagency committee consisting in whole or in part of the heads of elements of the Intelligence Community, the heads of departments containing such elements, or their designees—that the information necessary to advance a validated intelligence priority cannot reasonably be obtained by targeted collection. When it is determined to be necessary to engage in bulk collection in order to advance a validated intelligence priority, the element of the Intelligence Community shall apply reasonable methods and technical measures in order to limit the data collected to only what is necessary to advance a validated intelligence priority, while minimizing the collection of non-pertinent information.</P>
                <P SOURCE="P1">(B) Each element of the Intelligence Community that collects signals intelligence through bulk collection shall use such information only in pursuit of one or more of the following objectives:</P>
                <FP SOURCE="FP2">(1) protecting against terrorism, the taking of hostages, and the holding of individuals captive (including the identification, location, and rescue of hostages and captives) conducted by or on behalf of a foreign government, foreign organization, or foreign person;</FP>
                <FP SOURCE="FP2">(2) protecting against espionage, sabotage, assassination, or other intelligence activities conducted by, on behalf of, or with the assistance of a foreign government, foreign organization, or foreign person;</FP>
                <FP SOURCE="FP2">(3) protecting against threats from the development, possession, or proliferation of weapons of mass destruction or related technologies and threats conducted by, on behalf of, or with the assistance of a foreign government, foreign organization, or foreign person;</FP>
                <FP SOURCE="FP2">(4) protecting against cybersecurity threats created or exploited by, or malicious cyber activities conducted by or on behalf of, a foreign government, foreign organization, or foreign person;</FP>
                <FP SOURCE="FP2">(5) protecting against threats to the personnel of the United States or of its allies or partners; and</FP>
                <FP SOURCE="FP2">(6) protecting against transnational criminal threats, including illicit finance and sanctions evasion related to one or more of the other objectives identified in subsection (c)(ii) of this section.</FP>
                <P SOURCE="P1">(C) The President may authorize updates to the list of objectives in light of new national security imperatives, such as new or heightened threats to the national security of the United States, for which the President determines that bulk collection may be used. The Director shall publicly release any updates to the list of objectives authorized by the President, unless the President determines that doing so would pose a risk to the national security of the United States.</P>
                <P SOURCE="P1">(D) In order to minimize any impact on privacy and civil liberties, a targeted signals intelligence collection activity that temporarily uses data acquired without discriminants (for example, without specific identifiers or selection terms) shall be subject to the safeguards described in this subsection, unless such data is:</P>
                <FP SOURCE="FP2">(1) used only to support the initial technical phase of the targeted signals intelligence collection activity;</FP>
                <FP SOURCE="FP2">(2) retained for only the short period of time required to complete this phase; and</FP>
                <FP SOURCE="FP2">(3) thereafter deleted.</FP>
                <FP SOURCE="FP1">
                    (iii) 
                    <E T="03">Handling of personal information collected through signals intelligence.</E>
                    <PRTPAGE P="62287"/>
                </FP>
                <P SOURCE="P1">
                    (A) 
                    <E T="03">Minimization.</E>
                     Each element of the Intelligence Community that handles personal information collected through signals intelligence shall establish and apply policies and procedures designed to minimize the dissemination and retention of personal information collected through signals intelligence.
                </P>
                <FP SOURCE="FP2">
                    (1) 
                    <E T="03">Dissemination.</E>
                     Each element of the Intelligence Community that handles personal information collected through signals intelligence:
                </FP>
                <P SOURCE="P2">(a) shall disseminate non-United States persons' personal information collected through signals intelligence only if it involves one or more of the comparable types of information that section 2.3 of Executive Order 12333 of December 4, 1981 (United States Intelligence Activities), as amended, states may be disseminated in the case of information concerning United States persons;</P>
                <P SOURCE="P2">(b) shall not disseminate personal information collected through signals intelligence solely because of a person's nationality or country of residence;</P>
                <P SOURCE="P2">(c) shall disseminate within the United States Government personal information collected through signals intelligence only if an authorized and appropriately trained individual has a reasonable belief that the personal information will be appropriately protected and that the recipient has a need to know the information;</P>
                <P SOURCE="P2">(d) shall take due account of the purpose of the dissemination, the nature and extent of the personal information being disseminated, and the potential for harmful impact on the person or persons concerned before disseminating personal information collected through signals intelligence to recipients outside the United States Government, including to a foreign government or international organization; and</P>
                <P SOURCE="P2">(e) shall not disseminate personal information collected through signals intelligence for the purpose of circumventing the provisions of this order.</P>
                <FP SOURCE="FP2">
                    (2) 
                    <E T="03">Retention.</E>
                     Each element of the Intelligence Community that handles personal information collected through signals intelligence:
                </FP>
                <P SOURCE="P2">(a) shall retain non-United States persons' personal information collected through signals intelligence only if the retention of comparable information concerning United States persons would be permitted under applicable law and shall subject such information to the same retention periods that would apply to comparable information concerning United States persons;</P>
                <P SOURCE="P2">(b) shall subject non-United States persons' personal information collected through signals intelligence for which no final retention determination has been made to the same temporary retention periods that would apply to comparable information concerning United States persons; and</P>
                <P SOURCE="P2">(c) shall delete non-United States persons' personal information collected through signals intelligence that may no longer be retained in the same manner that comparable information concerning United States persons would be deleted.</P>
                <P SOURCE="P1">
                    (B) 
                    <E T="03">Data security and access.</E>
                     Each element of the Intelligence Community that handles personal information collected through signals intelligence:
                </P>
                <FP SOURCE="FP2">(1) shall process and store personal information collected through signals intelligence under conditions that provide appropriate protection and prevent access by unauthorized persons, consistent with the applicable safeguards for sensitive information contained in relevant Executive Orders, proclamations, other Presidential directives, Intelligence Community directives, and associated policies;</FP>
                <FP SOURCE="FP2">
                    (2) shall limit access to such personal information to authorized personnel who have a need to know the information to perform their mission and have received appropriate training on the requirements of applicable United States law, as described in policies and procedures issued under subsection (c)(iv) of this section; and
                    <PRTPAGE P="62288"/>
                </FP>
                <FP SOURCE="FP2">(3) shall ensure that personal information collected through signals intelligence for which no final retention determination has been made is accessed only in order to make or support such a determination or to conduct authorized administrative, testing, development, security, or oversight functions.</FP>
                <P SOURCE="P1">
                    (C) 
                    <E T="03">Data quality.</E>
                     Each element of the Intelligence Community that handles personal information collected through signals intelligence shall include such personal information in intelligence products only as consistent with applicable Intelligence Community standards for accuracy and objectivity, with a focus on applying standards relating to the quality and reliability of the information, consideration of alternative sources of information and interpretations of data, and objectivity in performing analysis.
                </P>
                <P SOURCE="P1">
                    (D) 
                    <E T="03">Queries of bulk collection.</E>
                     Each element of the Intelligence Community that conducts queries of unminimized signals intelligence obtained by bulk collection shall do so consistent with the permissible uses of signals intelligence obtained by bulk collection identified in subsection (c)(ii)(B) of this section and according to policies and procedures issued under subsection (c)(iv) of this section, which shall appropriately take into account the impact on the privacy and civil liberties of all persons, regardless of their nationality or wherever they might reside.
                </P>
                <P SOURCE="P1">
                    (E) 
                    <E T="03">Documentation.</E>
                     In order to facilitate the oversight processes set forth in subsection (d) of this section and the redress mechanism set forth in section 3 of this order, each element of the Intelligence Community that engages in signals intelligence collection activities shall maintain documentation to the extent reasonable in light of the nature and type of collection at issue and the context in which it is collected. The content of any such documentation may vary based on the circumstances but shall, to the extent reasonable, provide the factual basis pursuant to which the element of the Intelligence Community, based on a reasonable assessment of all relevant factors, assesses that the signals intelligence collection activity is necessary to advance a validated intelligence priority.
                </P>
                <FP SOURCE="FP1">
                    (iv) 
                    <E T="03">Update and publication of policies and procedures.</E>
                     The head of each element of the Intelligence Community:
                </FP>
                <P SOURCE="P1">(A) shall continue to use the policies and procedures issued pursuant to Presidential Policy Directive 28 of January 17, 2014 (Signals Intelligence Activities) (PPD-28), until they are updated pursuant to subsection (c)(iv)(B) of this section;</P>
                <P SOURCE="P1">(B) shall, within 1 year of the date of this order, in consultation with the Attorney General, the CLPO, and the Privacy and Civil Liberties Oversight Board (PCLOB), update those policies and procedures as necessary to implement the privacy and civil liberties safeguards in this order; and</P>
                <P SOURCE="P1">(C) shall, within 1 year of the date of this order, release these policies and procedures publicly to the maximum extent possible, consistent with the protection of intelligence sources and methods, in order to enhance the public's understanding of, and to promote public trust in, the safeguards pursuant to which the United States conducts signals intelligence activities.</P>
                <FP SOURCE="FP1">
                    (v) 
                    <E T="03">Review by the PCLOB.</E>
                </FP>
                <P SOURCE="P1">
                    (A) 
                    <E T="03">Nature of review.</E>
                     Consistent with applicable law, the PCLOB is encouraged to conduct a review of the updated policies and procedures described in subsection (c)(iv)(B) of this section once they have been issued to ensure that they are consistent with the enhanced safeguards contained in this order.
                </P>
                <P SOURCE="P1">
                    (B) 
                    <E T="03">Consideration of review.</E>
                     Within 180 days of completion of any review by the PCLOB described in subsection (c)(v)(A) of this section, the head of each element of the Intelligence Community shall carefully consider and shall implement or otherwise address all recommendations contained in such review, consistent with applicable law.
                    <PRTPAGE P="62289"/>
                </P>
                <P>
                    (d) 
                    <E T="03">Subjecting signals intelligence activities to rigorous oversight.</E>
                     The actions directed in this subsection are designed to build on the oversight mechanisms that elements of the Intelligence Community already have in place, in order to further ensure that signals intelligence activities are subjected to rigorous oversight.
                </P>
                <FP SOURCE="FP1">
                    (i) 
                    <E T="03">Legal, oversight, and compliance officials.</E>
                     Each element of the Intelligence Community that collects signals intelligence:
                </FP>
                <P SOURCE="P1">(A) shall have in place senior-level legal, oversight, and compliance officials who conduct periodic oversight of signals intelligence activities, including an Inspector General, a Privacy and Civil Liberties Officer, and an officer or officers in a designated compliance role with the authority to conduct oversight of and ensure compliance with applicable United States law;</P>
                <P SOURCE="P1">(B) shall provide such legal, oversight, and compliance officials access to all information pertinent to carrying out their oversight responsibilities under this subsection, consistent with the protection of intelligence sources or methods, including their oversight responsibilities to ensure that any appropriate actions are taken to remediate an incident of non-compliance with applicable United States law; and</P>
                <P SOURCE="P1">(C) shall not take any actions designed to impede or improperly influence such legal, oversight, and compliance officials in carrying out their oversight responsibilities under this subsection.</P>
                <FP SOURCE="FP1">
                    (ii) 
                    <E T="03">Training.</E>
                     Each element of the Intelligence Community shall maintain appropriate training requirements to ensure that all employees with access to signals intelligence know and understand the requirements of this order and the policies and procedures for reporting and remediating incidents of non-compliance with applicable United States law.
                </FP>
                <FP SOURCE="FP1">
                    (iii) 
                    <E T="03">Significant incidents of non-compliance.</E>
                </FP>
                <P SOURCE="P1">(A) Each element of the Intelligence Community shall ensure that, if a legal, oversight, or compliance official, as described in subsection (d)(i) of this section, or any other employee, identifies a significant incident of non-compliance with applicable United States law, the incident is reported promptly to the head of the element of the Intelligence Community, the head of the executive department or agency (agency) containing the element of the Intelligence Community (to the extent relevant), and the Director.</P>
                <P SOURCE="P1">(B) Upon receipt of such report, the head of the element of the Intelligence Community, the head of the agency containing the element of the Intelligence Community (to the extent relevant), and the Director shall ensure that any necessary actions are taken to remediate and prevent the recurrence of the significant incident of non-compliance.</P>
                <P>
                    (e) 
                    <E T="03">Savings clause.</E>
                     Provided the signals intelligence collection is conducted consistent with and in the manner prescribed by this section of this order, this order does not limit any signals intelligence collection technique authorized under the National Security Act of 1947, as amended (50 U.S.C. 3001 
                    <E T="03">et seq.</E>
                    ), the Foreign Intelligence Surveillance Act of 1978, as amended (50 U.S.C. 1801 
                    <E T="03">et seq.</E>
                    ) (FISA), Executive Order 12333, or other applicable law or Presidential directive.
                </P>
                <FP>
                    <E T="04">Sec. 3</E>
                    . 
                    <E T="03">Signals Intelligence Redress Mechanism.</E>
                </FP>
                <P>
                    (a) 
                    <E T="03">Purpose.</E>
                     This section establishes a redress mechanism to review qualifying complaints transmitted by the appropriate public authority in a qualifying state concerning United States signals intelligence activities for any covered violation of United States law and, if necessary, appropriate remediation.
                </P>
                <P>
                    (b) 
                    <E T="03">Process for submission of qualifying complaints.</E>
                     Within 60 days of the date of this order, the Director, in consultation with the Attorney General and the heads of elements of the Intelligence Community that collect or 
                    <PRTPAGE P="62290"/>
                    handle personal information collected through signals intelligence, shall establish a process for the submission of qualifying complaints transmitted by the appropriate public authority in a qualifying state.
                </P>
                <P>
                    (c) 
                    <E T="03">Initial investigation of qualifying complaints by the CLPO.</E>
                </P>
                <FP SOURCE="FP1">
                    (i) 
                    <E T="03">Establishment.</E>
                     The Director, in consultation with the Attorney General, shall establish a process that authorizes the CLPO to investigate, review, and, as necessary, order appropriate remediation for qualifying complaints. This process shall govern how the CLPO will review qualifying complaints in a manner that protects classified or otherwise privileged or protected information and shall ensure, at a minimum, that for each qualifying complaint the CLPO shall:
                </FP>
                <P SOURCE="P1">(A) review information necessary to investigate the qualifying complaint;</P>
                <P SOURCE="P1">(B) exercise its statutory and delegated authority to determine whether there was a covered violation by:</P>
                <FP SOURCE="FP2">(i) taking into account both relevant national security interests and applicable privacy protections;</FP>
                <FP SOURCE="FP2">(ii) giving appropriate deference to any relevant determinations made by national security officials; and</FP>
                <FP SOURCE="FP2">(iii) applying the law impartially;</FP>
                <P SOURCE="P1">(C) determine the appropriate remediation for any covered violation;</P>
                <P SOURCE="P1">(D) provide a classified report on information indicating a violation of any authority subject to the oversight of the Foreign Intelligence Surveillance Court (FISC) to the Assistant Attorney General for National Security, who shall report violations to the FISC in accordance with its rules of procedure;</P>
                <P SOURCE="P1">(E) after the review is completed, inform the complainant, through the appropriate public authority in a qualifying state and without confirming or denying that the complainant was subject to United States signals intelligence activities, that:</P>
                <FP SOURCE="FP2">(1) “the review either did not identify any covered violations or the Civil Liberties Protection Officer of the Office of the Director of National Intelligence issued a determination requiring appropriate remediation”;</FP>
                <FP SOURCE="FP2">(2) the complainant or an element of the Intelligence Community may, as prescribed in the regulations issued by the Attorney General pursuant to section 3(d)(i) of this order, apply for review of the CLPO's determinations by the Data Protection Review Court described in subsection (d) of this section; and</FP>
                <FP SOURCE="FP2">(3) if either the complainant or an element of the Intelligence Community applies for review by the Data Protection Review Court, a special advocate will be selected by the Data Protection Review Court to advocate regarding the complainant's interest in the matter;</FP>
                <P SOURCE="P1">(F) maintain appropriate documentation of its review of the qualifying complaint and produce a classified decision explaining the basis for its factual findings, determination with respect to whether a covered violation occurred, and determination of the appropriate remediation in the event there was such a violation, consistent with its statutory and delegated authority;</P>
                <P SOURCE="P1">(G) prepare a classified ex parte record of review, which shall consist of the appropriate documentation of its review of the qualifying complaint and the classified decision described in subsection (c)(i)(F) of this section; and</P>
                <P SOURCE="P1">(H) provide any necessary support to the Data Protection Review Court.</P>
                <FP SOURCE="FP1">
                    (ii) 
                    <E T="03">Binding effect.</E>
                     Each element of the Intelligence Community, and each agency containing an element of the Intelligence Community, shall comply with any determination by the CLPO to undertake appropriate remediation 
                    <PRTPAGE P="62291"/>
                    pursuant to subsection (c)(i)(C) of this section, subject to any contrary determination by the Data Protection Review Court.
                </FP>
                <FP SOURCE="FP1">
                    (iii) 
                    <E T="03">Assistance.</E>
                     Each element of the Intelligence Community shall provide the CLPO with access to information necessary to conduct the reviews described in subsection (c)(i) of this section, consistent with the protection of intelligence sources and methods, and shall not take any actions designed to impede or improperly influence the CLPO's reviews. Privacy and civil liberties officials within elements of the Intelligence Community shall also support the CLPO as it performs the reviews described in subsection (c)(i) of this section.
                </FP>
                <FP SOURCE="FP1">
                    (iv) 
                    <E T="03">Independence.</E>
                     The Director shall not interfere with a review by the CLPO of a qualifying complaint under subsection (c)(i) of this section; nor shall the Director remove the CLPO for any actions taken pursuant to this order, except for instances of misconduct, malfeasance, breach of security, neglect of duty, or incapacity.
                </FP>
                <P>
                    (d) 
                    <E T="03">Data Protection Review Court.</E>
                </P>
                <FP SOURCE="FP1">
                    (i) 
                    <E T="03">Establishment.</E>
                     The Attorney General is authorized to and shall establish a process to review determinations made by the CLPO under subsection (c)(i) of this section. In exercising that authority, the Attorney General shall, within 60 days of the date of this order, promulgate regulations establishing a Data Protection Review Court to exercise the Attorney General's authority to review such determinations. These regulations shall, at a minimum, provide that:
                </FP>
                <P SOURCE="P1">(A) The Attorney General, in consultation with the Secretary of Commerce, the Director, and the PCLOB, shall appoint individuals to serve as judges on the Data Protection Review Court, who shall be legal practitioners with appropriate experience in the fields of data privacy and national security law, giving weight to individuals with prior judicial experience, and who shall not be, at the time of their initial appointment, employees of the United States Government. During their term of appointment on the Data Protection Review Court, such judges shall not have any official duties or employment within the United States Government other than their official duties and employment as judges on the Data Protection Review Court.</P>
                <P SOURCE="P1">(B) Upon receipt of an application for review filed by the complainant or an element of the Intelligence Community of a determination made by the CLPO under subsection (c) of this section, a three-judge panel of the Data Protection Review Court shall be convened to review the application. Service on the Data Protection Review Court panel shall require that the judge hold the requisite security clearances to access classified national security information.</P>
                <P SOURCE="P1">(C) Upon being convened, the Data Protection Review Court panel shall select a special advocate through procedures prescribed in the Attorney General's regulations. The special advocate shall assist the panel in its consideration of the application for review, including by advocating regarding the complainant's interest in the matter and ensuring that the Data Protection Review Court panel is well informed of the issues and the law with respect to the matter. Service as a special advocate shall require that the special advocate hold the requisite security clearances to access classified national security information and to adhere to restrictions prescribed in the Attorney General's regulations on communications with the complainant to ensure the protection of classified or otherwise privileged or protected information.</P>
                <P SOURCE="P1">
                    (D) The Data Protection Review Court panel shall impartially review the determinations made by the CLPO with respect to whether a covered violation occurred and the appropriate remediation in the event there was such a violation. The review shall be based at a minimum on the classified ex parte record of review described in subsection (c)(i)(F) of this section and information or submissions provided by the complainant, 
                    <PRTPAGE P="62292"/>
                    the special advocate, or an element of the Intelligence Community. In reviewing determinations made by the CLPO, the Data Protection Review Court panel shall be guided by relevant decisions of the United States Supreme Court in the same way as are courts established under Article III of the United States Constitution, including those decisions regarding appropriate deference to relevant determinations of national security officials.
                </P>
                <P SOURCE="P1">(E) In the event that the Data Protection Review Court panel disagrees with any of the CLPO's determinations with respect to whether a covered violation occurred or the appropriate remediation in the event there was such a violation, the panel shall issue its own determinations.</P>
                <P SOURCE="P1">(F) The Data Protection Review Court panel shall provide a classified report on information indicating a violation of any authority subject to the oversight of the FISC to the Assistant Attorney General for National Security, who shall report violations to the FISC in accordance with its rules of procedure.</P>
                <P SOURCE="P1">(G) After the review is completed, the CLPO shall be informed of the Data Protection Review Court panel's determinations through procedures prescribed by the Attorney General's regulations.</P>
                <P SOURCE="P1">(H) After a review is completed in response to a complainant's application for review, the Data Protection Review Court, through procedures prescribed by the Attorney General's regulations, shall inform the complainant, through the appropriate public authority in a qualifying state and without confirming or denying that the complainant was subject to United States signals intelligence activities, that “the review either did not identify any covered violations or the Data Protection Review Court issued a determination requiring appropriate remediation.”</P>
                <FP SOURCE="FP1">
                    (ii) 
                    <E T="03">Binding effect.</E>
                     Each element of the Intelligence Community, and each agency containing an element of the Intelligence Community, shall comply with any determination by a Data Protection Review Court panel to undertake appropriate remediation.
                </FP>
                <FP SOURCE="FP1">
                    (iii) 
                    <E T="03">Assistance.</E>
                     Each element of the Intelligence Community shall provide the CLPO with access to information necessary to conduct the review described in subsection (d)(i) of this section, consistent with the protection of intelligence sources and methods, that a Data Protection Review Court panel requests from the CLPO and shall not take any actions for the purpose of impeding or improperly influencing a panel's review.
                </FP>
                <FP SOURCE="FP1">
                    (iv) 
                    <E T="03">Independence.</E>
                     The Attorney General shall not interfere with a review by a Data Protection Review Court panel of a determination the CLPO made regarding a qualifying complaint under subsection (c)(i) of this section; nor shall the Attorney General remove any judges appointed as provided in subsection (d)(i)(A) of this section, or remove any judge from service on a Data Protection Review Court panel, except for instances of misconduct, malfeasance, breach of security, neglect of duty, or incapacity, after taking due account of the standards in the Rules for Judicial-Conduct and Judicial-Disability Proceedings promulgated by the Judicial Conference of the United States pursuant to the Judicial Conduct and Disability Act (28 U.S.C. 351 
                    <E T="03">et seq.</E>
                    ).
                </FP>
                <FP SOURCE="FP1">
                    (v) 
                    <E T="03">Record of determinations.</E>
                     For each qualifying complaint transmitted by the appropriate public authority in a qualifying state, the Secretary of Commerce shall:
                </FP>
                <P SOURCE="P1">(A) maintain a record of the complainant who submitted such complaint;</P>
                <P SOURCE="P1">
                    (B) not later than 5 years after the date of this order and no less than every 5 years thereafter, contact the relevant element or elements of the Intelligence Community regarding whether information pertaining to the review of such complaint by the CLPO has been declassified and whether information pertaining to the review of any application for review submitted to the Data Protection Review Court has been declassified, 
                    <PRTPAGE P="62293"/>
                    including whether an element of the Intelligence Community filed an application for review with the Data Protection Review Court; and
                </P>
                <P SOURCE="P1">(C) if informed that such information has been declassified, notify the complainant, through the appropriate public authority in a qualifying state, that information pertaining to the review of their complaint by the CLPO or to the review of any application for review submitted to the Data Protection Review Court may be available under applicable law.</P>
                <P>
                    (e) 
                    <E T="03">Annual review by PCLOB of redress process.</E>
                </P>
                <FP SOURCE="FP1">
                    (i) 
                    <E T="03">Nature of review.</E>
                     Consistent with applicable law, the PCLOB is encouraged to conduct an annual review of the processing of qualifying complaints by the redress mechanism established by section 3 of this order, including whether the CLPO and the Data Protection Review Court processed qualifying complaints in a timely manner; whether the CLPO and the Data Protection Review Court are obtaining full access to necessary information; whether the CLPO and the Data Protection Review Court are operating consistent with this order; whether the safeguards established by section 2 of this order are properly considered in the processes of the CLPO and the Data Protection Review Court; and whether the elements of the Intelligence Community have fully complied with determinations made by the CLPO and the Data Protection Review Court.
                </FP>
                <FP SOURCE="FP1">
                    (ii) 
                    <E T="03">Assistance.</E>
                     The Attorney General, the CLPO, and the elements of the Intelligence Community shall provide the PCLOB with access to information necessary to conduct the review described in subsection (e)(i) of this section, consistent with the protection of intelligence sources and methods.
                </FP>
                <FP SOURCE="FP1">
                    (iii) 
                    <E T="03">Report and certification.</E>
                     Within 30 days of completing any review described in subsection (e)(i) of this section, the PCLOB is encouraged to:
                </FP>
                <P SOURCE="P1">(A) provide the President, the Attorney General, the Director, the heads of elements of the Intelligence Community, the CLPO, and the congressional intelligence committees with a classified report detailing the results of its review;</P>
                <P SOURCE="P1">(B) release to the public an unclassified version of the report; and</P>
                <P SOURCE="P1">(C) make an annual public certification as to whether the redress mechanism established pursuant to section 3 of this order is processing complaints consistent with this order.</P>
                <P SOURCE="P1">
                    (iv) 
                    <E T="03">Consideration of review.</E>
                     Within 180 days of receipt of any report by the PCLOB described in subsection (e)(iii)(A) of this section, the Attorney General, the Director, the heads of elements of the Intelligence Community, and the CLPO shall carefully consider and shall implement or otherwise address all recommendations contained in such report, consistent with applicable law.
                </P>
                <P>
                    (f) 
                    <E T="03">Designation of qualifying state.</E>
                </P>
                <FP SOURCE="FP1">(i) To implement the redress mechanism established by section 3 of this order, the Attorney General is authorized to designate a country or regional economic integration organization as a qualifying state for purposes of the redress mechanism established pursuant to section 3 of this order, effective immediately or on a date specified by the Attorney General, if the Attorney General determines, in consultation with the Secretary of State, the Secretary of Commerce, and the Director, that:</FP>
                <P SOURCE="P1">
                    (A) the laws of the country, the regional economic integration organization, or the regional economic integration organization's member countries require appropriate safeguards in the conduct of signals intelligence activities for United States persons' personal information that is transferred from the United States to the territory of the country or a member country of the regional economic integration organization;
                    <PRTPAGE P="62294"/>
                </P>
                <P SOURCE="P1">(B) the country, the regional economic integration organization, or the regional economic integration organization's member countries of the regional economic integration organization permit, or are anticipated to permit, the transfer of personal information for commercial purposes between the territory of that country or those member countries and the territory of the United States; and</P>
                <P SOURCE="P1">(C) such designation would advance the national interests of the United States.</P>
                <FP SOURCE="FP1">(ii) The Attorney General may revoke or amend such a designation, effective immediately or on a date specified by the Attorney General, if the Attorney General determines, in consultation with the Secretary of State, the Secretary of Commerce, and the Director, that:</FP>
                <P SOURCE="P1">(A) the country, the regional economic integration organization, or the regional economic integration organization's member countries do not provide appropriate safeguards in the conduct of signals intelligence activities for United States persons' personal information that is transferred from the United States to the territory of the country or to a member country of the regional economic integration organization;</P>
                <P SOURCE="P1">(B) the country, the regional economic integration organization, or the regional economic integration organization's member countries do not permit the transfer of personal information for commercial purposes between the territory of that country or those member countries and the territory of the United States; or</P>
                <P SOURCE="P1">(C) such designation is not in the national interests of the United States.</P>
                <P>
                    <E T="04">Sec. 4</E>
                    . 
                    <E T="03">Definitions.</E>
                     For purposes of this order:
                </P>
                <FP>(a) “Appropriate remediation” means lawful measures designed to fully redress an identified covered violation regarding a specific complainant and limited to measures designed to address that specific complainant's complaint, taking into account the ways that a violation of the kind identified have customarily been addressed. Such measures may include, depending on the specific covered violation at issue, curing through administrative measures violations found to have been procedural or technical errors relating to otherwise lawful access to or handling of data, terminating acquisition of data where collection is not lawfully authorized, deleting data that had been acquired without lawful authorization, deleting the results of inappropriately conducted queries of otherwise lawfully collected data, restricting access to lawfully collected data to those appropriately trained, or recalling intelligence reports containing data acquired without lawful authorization or that were otherwise disseminated in a manner inconsistent with United States law. Appropriate remediation shall be narrowly tailored to redress the covered violation and to minimize adverse impacts on the operations of the Intelligence Community and the national security of the United States.</FP>
                <P>(b) “Bulk collection” means the authorized collection of large quantities of signals intelligence data that, due to technical or operational considerations, is acquired without the use of discriminants (for example, without the use of specific identifiers or selection terms).</P>
                <P>(c) “Counterintelligence” shall have the same meaning as it has in Executive Order 12333.</P>
                <P>(d) “Covered violation” means a violation that:</P>
                <FP SOURCE="FP1">(i) arises from signals intelligence activities conducted after the date of this order regarding data transferred to the United States from a qualifying state after the effective date of the Attorney General's designation for such state, as provided in section 3(f)(i) of this order;</FP>
                <FP SOURCE="FP1">(ii) adversely affects the complainant's individual privacy and civil liberties interests; and</FP>
                <FP SOURCE="FP1">(iii) violates one or more of the following:</FP>
                <P SOURCE="P1">
                    (A) the United States Constitution;
                    <PRTPAGE P="62295"/>
                </P>
                <P SOURCE="P1">(B) the applicable sections of FISA or any applicable FISC-approved procedures;</P>
                <P SOURCE="P1">(C) Executive Order 12333 or any applicable agency procedures pursuant to Executive Order 12333;</P>
                <P SOURCE="P1">(D) this order or any applicable agency policies and procedures issued or updated pursuant to this order (or the policies and procedures identified in section 2(c)(iv)(A) of this order before they are updated pursuant to section 2(c)(iv)(B) of this order);</P>
                <P SOURCE="P1">(E) any successor statute, order, policies, or procedures to those identified in section 4(d)(iii)(B)-(D) of this order; or</P>
                <P SOURCE="P1">(F) any other statute, order, policies, or procedures adopted after the date of this order that provides privacy and civil liberties safeguards with respect to United States signals intelligence activities within the scope of this order, as identified in a list published and updated by the Attorney General, in consultation with the Director of National Intelligence.</P>
                <P>(e) “Foreign intelligence” shall have the same meaning as it has in Executive Order 12333.</P>
                <P>(f) “Intelligence” shall have the same meaning as it has in Executive Order 12333.</P>
                <P>(g) “Intelligence Community” and “elements of the Intelligence Community” shall have the same meaning as they have in Executive Order 12333.</P>
                <P>(h) “National security” shall have the same meaning as it has in Executive Order 13526 of December 29, 2009 (Classified National Security Information).</P>
                <P>(i) “Non-United States person” means a person who is not a United States person.</P>
                <P>(j) “Personnel of the United States or of its allies or partners” means any current or former member of the Armed Forces of the United States, any current or former official of the United States Government, and any other person currently or formerly employed by or working on behalf of the United States Government, as well as any current or former member of the military, current or former official, or other person currently or formerly employed by or working on behalf of an ally or partner.</P>
                <P>(k) “Qualifying complaint” means a complaint, submitted in writing, that:</P>
                <FP SOURCE="FP1">(i) alleges a covered violation has occurred that pertains to personal information of or about the complainant, a natural person, reasonably believed to have been transferred to the United States from a qualifying state after the effective date of the Attorney General's designation for such state, as provided in section 3(f)(i) of this order;</FP>
                <FP SOURCE="FP1">(ii) includes the following basic information to enable a review: information that forms the basis for alleging that a covered violation has occurred, which need not demonstrate that the complainant's data has in fact been subject to United States signals intelligence activities; the nature of the relief sought; the specific means by which personal information of or about the complainant was believed to have been transmitted to the United States; the identities of the United States Government entities believed to be involved in the alleged violation (if known); and any other measures the complainant pursued to obtain the relief requested and the response received through those other measures;</FP>
                <FP SOURCE="FP1">(iii) is not frivolous, vexatious, or made in bad faith;</FP>
                <FP SOURCE="FP1">(iv) is brought on behalf of the complainant, acting on that person's own behalf, and not as a representative of a governmental, nongovernmental, or intergovernmental organization; and</FP>
                <FP SOURCE="FP1">
                    (v) is transmitted by the appropriate public authority in a qualifying state, after it has verified the identity of the complainant and that the complaint satisfies the conditions of section 5(k)(i)-(iv) of this order.
                    <PRTPAGE P="62296"/>
                </FP>
                <P>(l) “Significant incident of non-compliance” shall mean a systemic or intentional failure to comply with a principle, policy, or procedure of applicable United States law that could impugn the reputation or integrity of an element of the Intelligence Community or otherwise call into question the propriety of an Intelligence Community activity, including in light of any significant impact on the privacy and civil liberties interests of the person or persons concerned.</P>
                <P>(m) “United States person” shall have the same meaning as it has in Executive Order 12333.</P>
                <P>(n) “Validated intelligence priority” shall mean, for most United States signals intelligence collection activities, a priority validated under the process described in section 2(b)(iii) of this order; or, in narrow circumstances (for example, when such process cannot be carried out because of a need to address a new or evolving intelligence requirement), shall mean a priority set by the President or the head of an element of the Intelligence Community in accordance with the criteria described in section 2(b)(iii)(A)(1)-(3) of this order to the extent feasible.</P>
                <P>(o) “Weapons of mass destruction” shall have the same meaning as it has in Executive Order 13526.</P>
                <FP>
                    <E T="04">Sec. 5</E>
                    . 
                    <E T="03">General Provisions.</E>
                     (a) Nothing in this order shall be construed to impair or otherwise affect:
                </FP>
                <FP SOURCE="FP1">(i) the authority granted by law to an executive department, agency, or the head thereof; or</FP>
                <FP SOURCE="FP1">(ii) the functions of the Director of the Office of Management and Budget relating to budgetary, administrative, or legislative proposals.</FP>
                <P>(b) This order shall be implemented consistent with applicable law, including orders of and procedures approved by the FISC, and subject to the availability of appropriations.</P>
                <P>(c) Nothing in this order precludes the application of more privacy-protective safeguards for United States signals intelligence activities that would apply in the absence of this order. In the case of any conflict between this order and other applicable law, the more privacy-protective safeguards shall govern the conduct of signals intelligence activities, to the maximum extent allowed by law.</P>
                <P>(d) Nothing in this order prohibits elements of the Intelligence Community from disseminating information relating to a crime for law enforcement purposes; disseminating warnings of threats of killing, serious bodily injury, or kidnapping; disseminating cyber threat, incident, or intrusion response information; notifying victims or warning potential victims of crime; or complying with dissemination obligations required by statute, treaty, or court order, including orders of and procedures approved by the FISC or other court orders.</P>
                <P>(e) The collection, retention, and dissemination of information concerning United States persons is governed by multiple legal and policy requirements, such as those required by FISA and Executive Order 12333. This order is not intended to alter the rules applicable to United States persons adopted pursuant to FISA, Executive Order 12333, or other applicable law.</P>
                <P>
                    (f) This order shall apply to signals intelligence activities consistent with the scope of PPD-28's application to such activities prior to PPD-28's partial revocation by the national security memorandum issued concurrently with this order. To implement this subsection, the head of each agency containing an element of the Intelligence Community, in consultation with the Attorney General and the Director, is hereby delegated the authority to issue guidance, which may be classified, as appropriate, as to the scope of application of this order with respect to the element or elements of the Intelligence Community within their agency. The CLPO and the Data Protection Review Court, in carrying out the functions assigned to it under this order, shall treat such guidance as authoritative and binding.
                    <PRTPAGE P="62297"/>
                </P>
                <P>(g) Nothing in this order confers authority to declassify or disclose classified national security information except as authorized pursuant to Executive Order 13526 or any successor order. Consistent with the requirements of Executive Order 13526, the CLPO, the Data Protection Review Court, and the special advocates shall not have authority to declassify classified national security information, nor shall they disclose any classified or otherwise privileged or protected information except to authorized and appropriately cleared individuals who have a need to know the information.</P>
                <P>(h) This order creates an entitlement to submit qualifying complaints to the CLPO and to obtain review of the CLPO's decisions by the Data Protection Review Court in accordance with the redress mechanism established in section 3 of this order. This order is not intended to, and does not, create any other entitlement, right, or benefit, substantive or procedural, enforceable at law or in equity by any party against the United States, its departments, agencies, or entities, its officers, employees, or agents, or any other person. This order is not intended to, and does not, modify the availability or scope of any judicial review of the decisions rendered through the redress mechanism, which is governed by existing law.</P>
                <GPH SPAN="1" DEEP="80" HTYPE="RIGHT">
                    <GID>BIDEN.EPS</GID>
                </GPH>
                <PSIG> </PSIG>
                <PLACE>THE WHITE HOUSE,</PLACE>
                <DATE>October 7, 2022.</DATE>
                <FRDOC>[FR Doc. 2022-22531 </FRDOC>
                <FILED>Filed 10-13-22; 8:45 am]</FILED>
                <BILCOD>Billing code 3395-F3-P</BILCOD>
            </EXECORD>
        </PRESDOCU>
    </PRESDOCS>
    <VOL>87</VOL>
    <NO>198</NO>
    <DATE>Friday, October 14, 2022</DATE>
    <UNITNAME>Presidential Documents</UNITNAME>
    <PRESDOC>
        <PRESDOCU>
            <PROCLA>
                <PRTPAGE P="62299"/>
                <PROC>Proclamation 10474 of October 11, 2022</PROC>
                <HD SOURCE="HED">General Pulaski Memorial Day, 2022</HD>
                <PRES>By the President of the United States of America</PRES>
                <PROC>A Proclamation</PROC>
                <FP>On September 11, 1777, Casimir Pulaski rode into battle with the Continental Army, led a skillful counterattack to slow the British advance, and helped save George Washington's life. Known as the “Father of the American Cavalry,” he would rise to the rank of Brigadier General, continue fighting for American independence in battles across the colonies, and eventually make the ultimate sacrifice in pursuit of revolutionary ideas: freedom, equality, and democracy. Today, we commemorate General Pulaski's heroism and service, honor generations of immigrants who followed in his path, and celebrate our Nation's rich Polish-American heritage.</FP>
                <FP>Every day, the contributions of 9 million Polish-Americans help make this country a beacon of hope and opportunity. As small business owners and elected representatives of the people, as educators and doctors, as champions of civil rights and patriots serving in uniform at home and abroad, Polish-Americans make communities across our Nation more prosperous, vibrant, and humane.</FP>
                <FP>As we continue to champion liberty and justice around the world, America draws great strength from the support of vital international allies like Poland. While Russia continues its unprovoked war in Ukraine, Poland and the United States stand shoulder-to-shoulder in defense of democracy and our collective security. As we pay tribute to General Pulaski and his legacy, may we always remember that the darkness of autocracy is no match for the flame of liberty that lights the souls of free people everywhere.</FP>
                <FP>NOW, THEREFORE, I, JOSEPH R. BIDEN JR., President of the United States of America, by virtue of the authority vested in me by the Constitution and laws of the United States, do hereby proclaim October 11, 2022, as General Pulaski Memorial Day. I encourage all Americans to commemorate this occasion with appropriate programs and activities paying tribute to General Casimir Pulaski and honoring all those who defend the freedom of our great Nation.</FP>
                <PRTPAGE P="62300"/>
                <FP>IN WITNESS WHEREOF, I have hereunto set my hand this eleventh day of October, in the year of our Lord two thousand twenty-two, and of the Independence of the United States of America the two hundred and forty-seventh.</FP>
                <GPH SPAN="1" DEEP="80" HTYPE="RIGHT">
                    <GID>BIDEN.EPS</GID>
                </GPH>
                <PSIG> </PSIG>
                <FRDOC>[FR Doc. 2022-22533 </FRDOC>
                <FILED>Filed 10-13-22; 8:45 am]</FILED>
                <BILCOD>Billing code 3395-F3-P</BILCOD>
            </PROCLA>
        </PRESDOCU>
    </PRESDOC>
    <VOL>87</VOL>
    <NO>198</NO>
    <DATE>Friday, October 14, 2022</DATE>
    <UNITNAME>Presidential Documents</UNITNAME>
    <PRESDOC>
        <PRESDOCU>
            <PROCLA>
                <PRTPAGE P="62301"/>
                <PROC>Proclamation 10475 of October 11, 2022</PROC>
                <HD SOURCE="HED">International Day of the Girl, 2022</HD>
                <PRES>By the President of the United States of America</PRES>
                <PROC>A Proclamation</PROC>
                <FP>Ten years ago, on the first International Day of the Girl, the United States joined nations around the world to recognize the challenges that girls face and commit to expanding opportunity and equality for them in every part of the globe. Today, on this 10th anniversary, we know that when girls are empowered to dream big and reach their full potential, the possibilities for our world are limitless. From combating the climate crisis and standing up for human rights to fighting for equitable access to education, health care, and opportunity, girls are strengthening democracies, powering economies, and enriching communities everywhere.</FP>
                <FP>Despite their dynamic potential, we must also recognize on this day that girls continue to face significant challenges in the United States and around the world. Hunger, homelessness, and lack of access to adequate health care and educational opportunities threaten their health and wellbeing and create barriers to their full and equal participation in society.</FP>
                <FP>Both at home and abroad, gender-based violence compromises their safety—from child sexual abuse and exploitation to female genital cutting and child marriage. The direct and indirect impacts of gender-based violence and the effect they have on girls' potential and opportunity reinforce our commitment to building a world where all people can live free from violence or intimidation.</FP>
                <FP>That is why my Administration has prioritized unlocking doors of opportunity and delivering the full measure of equity and dignity due to all girls. At home, we are championing equitable access to education, equal pay, and access to jobs and job training so that when girls grow up, they can choose their own path and lead the workforce of the future. We are taking action to expand girls' access to health care, which is critical to supporting their success. I am committed to addressing gender-based violence wherever it occurs—online, in school, at work, or at home—which is why I am proud to have reauthorized and strengthened the Violence Against Women Act. And by supporting LGBTQI+ rights across this Nation, I affirm that everyone deserves respect, protection, and belonging.</FP>
                <FP>My Administration's commitment to empowering girls extends beyond our borders. The United States is supporting equitable access to health care by providing lifesaving HIV treatment to over 19 million people worldwide. We reached over two million adolescent girls and young women just last year. We have committed to improving access to education and learning for 15 million girls and young women by 2025. And we are committed to ending the scourge of gender-based violence globally—particularly in conflict zones, in humanitarian and refugee contexts, and in the aftermath of natural disasters where women and girls face distinct vulnerabilities.</FP>
                <FP>
                    My Administration is also investing in education and programs to advance economic security for women and girls globally, including by pledging $50 million to the World Bank's Global Childcare Incentive Fund and calling on the Congress to provide $200 million for the Gender Equity and Equality Action Fund to support women's economic participation. I will continue to speak out for women and girls around the globe, including in Iran, 
                    <PRTPAGE P="62302"/>
                    where brave young women are demonstrating to secure their basic rights, and I have called on the Congress to double funding for programs that promote gender equality worldwide.
                </FP>
                <FP>When girls break barriers, they blaze trails for the generations that follow. Investing in their health, safety, education, and economic security moves us closer to building more just, equitable societies and flourishing democracies. It helps us develop leaders across sectors and enables us to create a strong workforce that is ready to meet the challenges and opportunities ahead. Together, we can prepare the next dreamers and doers to shape a new and better future for us all.</FP>
                <FP>NOW, THEREFORE, I, JOSEPH R. BIDEN JR., President of the United States of America, by virtue of the authority vested in me by the Constitution and the laws of the United States, do hereby proclaim October 11, 2022, as International Day of the Girl. I call upon the people of the United States to observe this day with programs, ceremonies, and activities that advance equality and opportunity for girls everywhere.</FP>
                <FP>IN WITNESS WHEREOF, I have hereunto set my hand this eleventh day of October, in the year of our Lord two thousand twenty-two, and of the Independence of the United States of America the two hundred and forty-seventh.</FP>
                <GPH SPAN="1" DEEP="80" HTYPE="RIGHT">
                    <GID>BIDEN.EPS</GID>
                </GPH>
                <PSIG> </PSIG>
                <FRDOC>[FR Doc. 2022-22534 </FRDOC>
                <FILED>Filed 10-13-22; 8:45 am]</FILED>
                <BILCOD>Billing code 3395-F3-P</BILCOD>
            </PROCLA>
        </PRESDOCU>
    </PRESDOC>
    <VOL>87</VOL>
    <NO>198</NO>
    <DATE>Friday, October 14, 2022</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="62501"/>
            <PARTNO>Part II</PARTNO>
            <AGENCY TYPE="P">Department of the Interior</AGENCY>
            <SUBAGY>Fish and Wildlife Service</SUBAGY>
            <HRULE/>
            <CFR>50 CFR Part 17</CFR>
            <TITLE>Endangered and Threatened Wildlife and Plants; Designation of Critical Habitat for Chamaecrista lineata var. keyensis (Big Pine Partridge Pea), Chamaesyce deltoidea ssp. serpyllum (Wedge Spurge), Linum arenicola (Sand Flax), and Argythamnia blodgettii (Blodgett's Silverbush); Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="62502"/>
                    <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                    <SUBAGY>Fish and Wildlife Service</SUBAGY>
                    <CFR>50 CFR Part 17</CFR>
                    <DEPDOC>[Docket No. FWS-R4-ES-2022-0116; FF09E21000 FXES1111090FEDR 223]</DEPDOC>
                    <RIN>RIN 1018-BE51</RIN>
                    <SUBJECT>
                        Endangered and Threatened Wildlife and Plants; Designation of Critical Habitat for 
                        <E T="0714">Chamaecrista lineata</E>
                         var. 
                        <E T="0714">keyensis</E>
                         (Big Pine Partridge Pea), 
                        <E T="0714">Chamaesyce deltoidea</E>
                         ssp. 
                        <E T="0714">serpyllum</E>
                         (Wedge Spurge), 
                        <E T="0714">Linum arenicola</E>
                         (Sand Flax), and 
                        <E T="0714">Argythamnia blodgettii</E>
                         (Blodgett's Silverbush)
                    </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Fish and Wildlife Service, Interior.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Proposed rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>
                            We, the U.S. Fish and Wildlife Service (Service), propose to designate critical habitat for 
                            <E T="03">Chamaecrista lineata</E>
                             var. 
                            <E T="03">keyensis</E>
                             (Big Pine partridge pea), 
                            <E T="03">Chamaesyce deltoidea</E>
                             ssp. 
                            <E T="03">serpyllum</E>
                             (wedge spurge), 
                            <E T="03">Linum arenicola</E>
                             (sand flax), and 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's silverbush) under the Endangered Species Act (Act). In total, approximately 1,462 acres (592 hectares) for Big Pine partridge pea and approximately 1,379 acres (558 hectares) for wedge spurge, in Monroe County, Florida, and approximately 5,090 acres (2,060 hectares) for sand flax and 16,635 acres (6,732 hectares) for Blodgett's silverbush in Miami-Dade and Monroe Counties, Florida, fall within the boundaries of the proposed critical habitat designations. If we finalize this rule as proposed, it would extend the Act's protections to the species' critical habitat. We also announce the availability of a draft economic analysis of the proposed designation of critical habitat for these four plant species.
                        </P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>
                            We will accept comments received or postmarked on or before December 13, 2022. Comments submitted electronically using the Federal eRulemaking Portal (see 
                            <E T="02">ADDRESSES</E>
                             below) must be received by 11:59 p.m. eastern time on the closing date. We must receive requests for public hearings, in writing, at the address shown in 
                            <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                             by November 28, 2022.
                        </P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>You may submit comments by one of the following methods:</P>
                        <P>
                            (1) 
                            <E T="03">Electronically:</E>
                             Go to the Federal eRulemaking Portal: 
                            <E T="03">https://www.regulations.gov.</E>
                             In the Search box, enter FWS-R4-ES-2022-0116, which is the docket number for this rulemaking action. Then, click on the Search button. On the resulting page, in the panel on the left side of the screen, under the Document Type heading, check the Proposed Rule box to locate this document. You may submit a comment by clicking on “Comment.”
                        </P>
                        <P>
                            (2) 
                            <E T="03">By hard copy:</E>
                             Submit by U.S. mail to: Public Comments Processing, Attn: FWS-R4-ES-2022-0116, U.S. Fish and Wildlife Service, MS: PRB/3W, 5275 Leesburg Pike, Falls Church, VA 22041-3803.
                        </P>
                        <P>
                            We request that you send comments only by the methods described above. We will post all comments on 
                            <E T="03">https://www.regulations.gov.</E>
                             This generally means that we will post any personal information you provide us (see Information Requested, below, for more information).
                        </P>
                        <P>
                            <E T="03">Availability of supporting materials:</E>
                             For the proposed critical habitat designation, the coordinates or plot points or both from which the maps are generated are included in the decision file and are available at 
                            <E T="03">https://www.fws.gov/office/florida-ecological-services/library</E>
                             and at 
                            <E T="03">https://www.regulations.gov</E>
                             under Docket No. FWS-R4-ES-2022-0116. Any supporting information that we developed for this critical habitat designation will be available on the Service's website or at 
                            <E T="03">https://www.regulations.gov.</E>
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Lourdes Mena, Classification and Recovery Division Manager, U.S. Fish and Wildlife Service, Florida Ecological Services Field Office, 7915 Baymeadows Way, Suite 200, Jacksonville, FL 32256; by telephone 904-731-3134; or by facsimile 904-731-3045. Individuals in the United States who are deaf, deafblind, hard of hearing, or have a speech disability may dial 711 (TTY, TDD, or TeleBraille) to access telecommunications relay services. Individuals outside the United States should use the relay services offered within their country to make international calls to the point-of-contact in the United States.</P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P/>
                    <HD SOURCE="HD1">Executive Summary</HD>
                    <P>
                        <E T="03">Why we need to publish a proposed rule.</E>
                         Under the Act, when we determine that any species is a threatened or endangered species, we must designate critical habitat, to the maximum extent prudent and determinable. Designations and revisions of critical habitat can only be completed by issuing a rule through the Administrative Procedure Act rulemaking process (5 U.S.C. 1531 
                        <E T="03">et seq.</E>
                        ).
                    </P>
                    <P>
                        <E T="03">What this document does.</E>
                         This document proposes to designate critical habitat for three plant species, Big Pine partridge pea, wedge spurge, and sand flax, listed as endangered species under the Act, and one plant species, Blodgett's silverbush, listed as a threatened species under the Act (September 29, 2016 (81 FR 66842)).
                    </P>
                    <P>
                        <E T="03">The basis for our action.</E>
                         Section 3(5)(A) of the Act defines critical habitat as (i) the specific areas within the geographical area occupied by the species, at the time it is listed, on which are found those physical or biological features (I) essential to the conservation of the species and (II) which may require special management considerations or protections; and (ii) specific areas outside the geographical area occupied by the species at the time it is listed, upon a determination by the Secretary that such areas are essential for the conservation of the species. Section 4(b)(2) of the Act states that the Secretary must make the designation on the basis of the best scientific data available and after taking into consideration the economic impact, the impact on national security, and any other relevant impacts of specifying any particular area as critical habitat.
                    </P>
                    <P>
                        <E T="03">Draft economic analysis of the proposed designation of critical habitat.</E>
                         We have prepared an analysis of the probable economic impacts of the proposed critical habitat designation and related factors. In this document, we announce the availability of the draft economic analysis and seek additional public review and comment.
                    </P>
                    <P>
                        <E T="03">Public comment.</E>
                         We are seeking comments and soliciting information from the public on our proposed designation to make sure we consider the best scientific and commercial information available in developing our final designation. Because we will consider all comments and information we receive during the comment period, our final determination may differ from this proposal. We will respond to substantive comments we receive during the comment period in our final rule.
                    </P>
                    <P>
                        <E T="03">Peer review.</E>
                         In accordance with our joint policy on peer review published in the 
                        <E T="04">Federal Register</E>
                         on July 1, 1994 (59 FR 34270), and our August 22, 2016, memorandum updating and clarifying the role of peer review of determinations under section 4 of the Act, including listing determinations and critical habitat designations, we are seeking comments from independent specialists. The purpose of peer review is to ensure that our critical habitat 
                        <PRTPAGE P="62503"/>
                        designation is based on scientifically sound data, assumptions, and analyses. The peer reviewers have expertise in the biology, habitat, and threats to the species addressed herein. We have invited these peer reviewers to comment on our specific assumptions and conclusions in this critical habitat proposal during the public comment period for this proposed rule (see 
                        <E T="02">DATES</E>
                        , above).
                    </P>
                    <HD SOURCE="HD1">Information Requested</HD>
                    <P>We intend that any final action resulting from this proposed rule will be based on the best scientific and commercial data available and be as accurate and as effective as possible. Therefore, we request comments or information from other governmental agencies, Native American tribes, the scientific community, industry, or any other interested parties concerning this proposed rule. We particularly seek comments concerning:</P>
                    <P>
                        (1) The reasons why we should or should not designate habitat as “critical habitat” under section 4 of the Act (16 U.S.C. 1531 
                        <E T="03">et seq.</E>
                        ), including information regarding the following factors that the regulations identify as reasons why designation of critical habitat may be not prudent:
                    </P>
                    <P>(a) The species is threatened by taking or other human activity and identification of critical habitat can be expected to increase the degree of such threat to the species; or</P>
                    <P>(b) Such designation of critical habitat would not be beneficial to the species. In determining whether a designation would not be beneficial, the factors the Services may consider include but are not limited to: whether the present or threatened destruction, modification, or curtailment of a species' habitat or range is not a threat to the species, or whether any areas meet the definition of “critical habitat.”</P>
                    <P>(2) Specific information on:</P>
                    <P>(a) The amount and distribution of Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush habitat.</P>
                    <P>
                        (b) Any additional areas occurring within the range of the species, 
                        <E T="03">i.e.,</E>
                         south and central Florida peninsula and the Florida Keys, that should be included in the designation because they (i) were occupied at the time of listing in 2016 and contain the physical or biological features that are essential to the conservation of the species and that may require special management considerations, or (ii) were unoccupied at the time of listing, and are essential for the conservation of the species, because they have potential to successfully support introduced or reintroduced populations of these species.
                    </P>
                    <P>(c) While we seek comments on any additional areas under (b)(i) and (ii) above, we particularly seek comments on the following unoccupied areas, including information on whether these areas have the potential to support introduced or reintroduced populations: No Name Key, Upper and Lower Sugarloaf Keys, Cudjoe Key, and Little Pine Key in Monroe County, Florida; and Trinity Pinelands, Nixon Smiley, Quail Roost Pineland, and Navy Wells in Miami-Dade County, Florida.</P>
                    <P>(d) Special management considerations or protection that may be needed in critical habitat areas we are proposing, including managing for the potential effects of climate change.</P>
                    <P>(e) Whether we have appropriately identified the physical or biological features that are essential to the conservation for each species.</P>
                    <P>(3) Land use designations and current or planned activities in the subject areas and their possible impacts on proposed critical habitat.</P>
                    <P>(4) Information on the projected and reasonably likely impacts of climate change on Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush and proposed critical habitat.</P>
                    <P>(5) Information on the extent to which the description of probable economic impacts in the draft economic analysis is a reasonable estimate of the likely economic impacts and any additional information regarding probable economic impacts that we should consider.</P>
                    <P>(6) Whether any specific areas we are proposing for critical habitat designation should be considered for exclusion under section 4(b)(2) of the Act, and whether the benefits of potentially excluding any specific area outweigh the benefits of including that area under section 4(b)(2) of the Act. If you think we should exclude any additional areas, please provide information regarding the existence of a meaningful economic or other relevant impact supporting a benefit of exclusion.</P>
                    <P>(7) Whether we could improve or modify our approach to designating critical habitat in any way to provide for greater public participation and understanding, or to better accommodate public concerns and comments.</P>
                    <P>Please include sufficient information with your submission (such as scientific journal articles or other publications) to allow us to verify any scientific or commercial information you include. Please note that submissions merely stating support for, or opposition to, the action under consideration without providing supporting information, although noted, will not be considered in making a final critical habitat determination. Section 4(b)(2) of the Act directs that the Secretary shall designate critical habitat on the basis of the best scientific information data available.</P>
                    <P>
                        You may submit your comments and materials concerning this proposed rule by one of the methods listed in 
                        <E T="02">ADDRESSES</E>
                        . We request that you send comments only by the methods described in 
                        <E T="02">ADDRESSES</E>
                        .
                    </P>
                    <P>
                        If you submit information via 
                        <E T="03">https://www.regulations.gov,</E>
                         your entire submission—including any personal identifying information—will be posted on the website. If your submission is made via a hardcopy that includes personal identifying information, you may request at the top of your document that we withhold this information from public review. However, we cannot guarantee that we will be able to do so. We will post all hardcopy submissions on 
                        <E T="03">https://www.regulations.gov.</E>
                    </P>
                    <P>
                        Comments and materials we receive, as well as supporting documentation we used in preparing this proposed rule, will be available for public inspection on 
                        <E T="03">https://www.regulations.gov.</E>
                    </P>
                    <P>Because we will consider all comments and information we receive during the comment period, our final designation may differ from this proposal. Based on the new information we receive (and any comments on that new information), our final designation may not include all areas proposed, may include some additional areas that meet the definition of critical habitat, or may exclude some areas if we find the benefits of exclusion outweigh the benefits of inclusion. Such final decisions would be a logical outgrowth of this proposal, as long as we: (1) base the decisions on the best scientific and commercial data available after considering all of the relevant factors; (2) do not rely on factors Congress has not intended us to consider; and (3) articulate a rational connection between the facts found and the conclusions made, including why we changed our conclusion.</P>
                    <HD SOURCE="HD2">Public Hearing</HD>
                    <P>
                        Section 4(b)(5) of the Act provides for a public hearing on this proposal, if requested. Requests must be received by the date specified in 
                        <E T="02">DATES</E>
                        . Such requests must be sent to the address shown in 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        . We will schedule a public hearing on this proposal, if requested, and announce the date, time, and place of the hearing, as well as how to obtain reasonable accommodations, in the 
                        <PRTPAGE P="62504"/>
                        <E T="04">Federal Register</E>
                         and local newspapers at least 15 days before the hearing. We may hold the public hearing in person or virtually via webinar. We will announce any public hearing on our website, in addition to the 
                        <E T="04">Federal Register</E>
                        . The use of virtual public hearings is consistent with our regulation at 50 CFR 424.16(c)(3).
                    </P>
                    <HD SOURCE="HD1">Acronyms Used in This Document</HD>
                    <P>For the convenience of the reader, we provide this list of some of the acronyms used in this proposed rule:</P>
                    <EXTRACT>
                        <FP SOURCE="FP-2">CCAA = candidate conservation agreements with assurances</FP>
                        <FP SOURCE="FP-2">CCP = comprehensive conservation plan</FP>
                        <FP SOURCE="FP-2">DoD = Department of Defense</FP>
                        <FP SOURCE="FP-2">ENP = Everglades National Park</FP>
                        <FP SOURCE="FP-2">FKWEA = Florida Keys Wildlife and Environmental Area</FP>
                        <FP SOURCE="FP-2">FNAI = Florida Natural Areas Inventory</FP>
                        <FP SOURCE="FP-2">HARB = Homestead Air Reserve Base</FP>
                        <FP SOURCE="FP-2">HCP = habitat conservation plan</FP>
                        <FP SOURCE="FP-2">INRMP = integrated natural resources management plan</FP>
                        <FP SOURCE="FP-2">KWNAS = Key West Naval Air Station</FP>
                        <FP SOURCE="FP-2">NKDR = National Key Deer Refuge</FP>
                        <FP SOURCE="FP-2">NWRs = National Wildlife Refuges</FP>
                        <FP SOURCE="FP-2">SHA = safe harbor agreements</FP>
                        <FP SOURCE="FP-2">SOCSO = Special Operations Command South</FP>
                        <FP SOURCE="FP-2">USDA = U.S. Department of Agriculture</FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">Previous Federal Actions</HD>
                    <P>On September 29, 2015, we proposed to list Big Pine partridge pea, wedge spurge, and sand flax as endangered species and Blodgett's silverbush as a threatened species under the Act (80 FR 58536). On September 29, 2016, we finalized the listing (81 FR 66842). At the time of our proposal, we determined that critical habitat was prudent, but not determinable because we lacked specific information on the impacts of our designation. In our final listing rule, we stated we were in the process of obtaining information on the impacts of the designation (81 FR 66842). All previous Federal actions for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush are described in detail in our final rule listing the four plant species as endangered and threatened species under the Act (81 FR 66842).</P>
                    <P>It is our intent to discuss in this proposed rule only those topics directly relevant to the designation of critical habitat for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush. For more information on the taxonomy, life history, habitat, population descriptions, and factors affecting the species, please refer to the September 29, 2015, proposed listing rule for these species (80 FR 58536) and the September 29, 2016, final listing rule (81 FR 66842).</P>
                    <HD SOURCE="HD1">Critical Habitat</HD>
                    <HD SOURCE="HD2">Background</HD>
                    <P>Section 4 of the Act (16 U.S.C. 1533) and the implementing regulations in title 50 of the Code of Federal Regulations set forth the procedures for determining whether a species is an endangered species or a threatened species, issuing protective regulations for threatened species, and designating critical habitat for threatened and endangered species. In 2019, jointly with the National Marine Fisheries Service, the Service issued final rules that revised the regulations in 50 CFR parts 17 and 424 regarding how we add, remove, and reclassify threatened and endangered species and the criteria for designating listed species' critical habitat (84 FR 45020 and 84 FR 44752; August 27, 2019). At the same time the Service also issued final regulations that, for species listed as threatened species after September 26, 2019, eliminated the Service's general protective regulations automatically applying to threatened species the prohibitions that section 9 of the Act applies to endangered species (collectively, the 2019 regulations).</P>
                    <P>
                        However, on July 5, 2022, the U.S. District Court for the Northern District of California vacated the 2019 regulations (
                        <E T="03">Center for Biological Diversity</E>
                         v. 
                        <E T="03">Haaland,</E>
                         No. 4:19-cv-05206-JST, Doc. 168 (N.D. Cal. July 5, 2022) (
                        <E T="03">CBD</E>
                         v. 
                        <E T="03">Haaland</E>
                        )), reinstating the regulations that were in effect before the effective date of the 2019 regulations as the law governing species classification and critical-habitat decisions. Accordingly, in developing the analysis contained in this proposal, we applied the pre-2019 regulations, which may be reviewed in the 2018 edition of the Code of Federal Regulations at 50 CFR 424.02 and 424.12(a)(1) and (b)(2). Because of the ongoing litigation regarding the court's vacatur of the 2019 regulations, and the resulting uncertainty surrounding the legal status of the regulations, we also undertook an analysis of whether the proposal would be different if we were to apply the 2019 regulations. That analysis, which we described in a separate memo in the decisional file and posted on 
                        <E T="03">https://www.regulations.gov,</E>
                         concluded that we would have reached the same proposal if we had applied the 2019 regulations. For the four plants, we find that critical habitat is prudent under either regulatory scheme because we determined that the present or threatened destruction, modification, or curtailment of habitat or range is a threat to all four species. In addition, in the final listing rule (81 FR 66842; September 29, 2016), illegal collection of any of the four Florida Keys plants was not identified as a threat under Factor B, and identification and mapping of critical habitat is not expected to initiate any such threat. We also determined the occupied areas may be adequate to ensure the conservation of these species. For Blodgett's silverbush, the amount and distribution of critical habitat we are proposing for designation in occupied areas would allow existing and future established populations to maintain their existing distributions; expand their distributions into suitable nearby areas (needed to offset habitat loss and fragmentation); increase the size of each population to a level where the threats of genetic, demographic, and normal environmental uncertainties are diminished; and maintain their ability to withstand local or unit-level environmental fluctuations or catastrophic events. Accordingly, we have not identified unoccupied areas that are essential for the conservation of this species at this time. For Big Pine partridge pea, wedge spurge, and sand flax, we identified areas of remaining pine rockland habitat that we are considering whether these areas meet the definition of unoccupied critical habitat for these three species.
                    </P>
                    <P>
                        On September 21, 2022, the U.S. Circuit Court of Appeals for the Ninth Circuit stayed the district court's July 5, 2022, order vacating the 2019 regulations until a pending motion for reconsideration before the district court is resolved (
                        <E T="03">In re: Cattlemen's Ass'n,</E>
                         No. 22-70194). The effect of the stay is that the 2019 regulations are currently the governing law. Because a court order requires us to submit this proposal to the 
                        <E T="04">Federal Register</E>
                         by September 30, 2022, it is not feasible for us to revise the proposal in response to the Ninth Circuit's decision. Instead, we hereby adopt the analysis in the separate memo that applied the 2019 regulations as our primary justification for the proposal. However, due to the continued uncertainty resulting from the ongoing litigation, we also retain the analysis in this preamble that applies the pre-2019 regulations and we conclude that, for the reasons stated in our separate memo analyzing the 2019 regulations, this proposal would have been the same if we had applied the 2019 regulations.
                    </P>
                    <P>Critical habitat is defined in section 3 of the Act as:</P>
                    <P>
                        (1) The specific areas within the geographical area occupied by the species, at the time it is listed in accordance with the Act, on which are found those physical or biological features
                        <PRTPAGE P="62505"/>
                    </P>
                    <P>(a) Essential to the conservation of the species, and</P>
                    <P>(b) Which may require special management considerations or protection; and</P>
                    <P>(2) Specific areas outside the geographical area occupied by the species at the time it is listed, upon a determination that such areas are essential for the conservation of the species.</P>
                    <P>
                        Our regulations at 50 CFR 424.02 define the geographical area occupied by the species as an area that may generally be delineated around species' occurrences, as determined by the Secretary (
                        <E T="03">i.e.,</E>
                         range). Such areas may include those areas used throughout all or part of the species' life cycle, even if not used on a regular basis (
                        <E T="03">e.g.,</E>
                         migratory corridors, seasonal habitats, and habitats used periodically, but not solely by vagrant individuals).
                    </P>
                    <P>Conservation, as defined under section 3 of the Act, means to use and the use of all methods and procedures that are necessary to bring an endangered or threatened species to the point at which the measures provided pursuant to the Act are no longer necessary. Such methods and procedures include, but are not limited to, all activities associated with scientific resources management such as research, census, law enforcement, habitat acquisition and maintenance, propagation, live trapping, and transplantation, and, in the extraordinary case where population pressures within a given ecosystem cannot be otherwise relieved, may include regulated taking.</P>
                    <P>Critical habitat receives protection under section 7 of the Act through the requirement that Federal agencies ensure, in consultation with the Service, that any action they authorize, fund, or carry out is not likely to result in the destruction or adverse modification of critical habitat. The designation of critical habitat does not affect land ownership or establish a refuge, wilderness, reserve, preserve, or other conservation area. Designation also does not allow the government or public to access private lands, nor does designation require implementation of restoration, recovery, or enhancement measures by non-Federal landowners. Where a landowner requests Federal agency funding or authorization for an action that may affect a listed species or critical habitat, the Federal agency would be required to consult with the Service under section 7(a)(2) of the Act. However, even if the Service were to conclude that the proposed activity would result in destruction or adverse modification of the critical habitat, the Federal action agency and the landowner are not required to abandon the proposed activity, or to restore or recover the species; instead, they must implement “reasonable and prudent alternatives” to avoid destruction or adverse modification of critical habitat.</P>
                    <P>Under the first prong of the Act's definition of critical habitat, areas within the geographical area occupied by the species at the time it was listed are included in a critical habitat designation if they contain physical or biological features (1) which are essential to the conservation of the species and (2) which may require special management considerations or protection. For these areas, critical habitat designations identify, to the extent known using the best scientific and commercial data available, those physical or biological features that are essential to the conservation of the species (such as space, food, cover, and protected habitat). In identifying those physical or biological features that occur in specific occupied areas, we focus on those features that are essential to support the life-history needs of the species, including, but not limited to, water characteristics, soil type, geological features, prey, vegetation, symbiotic species, or other features. A feature may be a single habitat characteristic or a more complex combination of habitat characteristics. Features may include habitat characteristics that support ephemeral or dynamic habitat conditions. Features may also be expressed in terms relating to principles of conservation biology, such as patch size, distribution distances, and connectivity.</P>
                    <P>Under the second prong of the Act's definition of critical habitat, we can designate critical habitat in areas outside the geographical area occupied by the species at the time it is listed, upon a determination that such areas are essential for the conservation of the species.</P>
                    <P>
                        Section 4 of the Act requires that we designate critical habitat on the basis of the best scientific data available. Further, our Policy on Information Standards Under the Endangered Species Act (published in the 
                        <E T="04">Federal Register</E>
                         on July 1, 1994 (59 FR 34271)), the Information Quality Act (section 515 of the Treasury and General Government Appropriations Act for Fiscal Year 2001 (Pub. L. 106-554; H.R. 5658)), and our associated Information Quality Guidelines provide criteria, establish procedures, and provide guidance to ensure that our decisions are based on the best scientific data available. They require our biologists, to the extent consistent with the Act and with the use of the best scientific data available, to use primary and original sources of information as the basis for recommendations to designate critical habitat.
                    </P>
                    <P>When we are determining which areas should be designated as critical habitat, our primary source of information is generally the information from the listing process for the species. Additional information sources may include any generalized conservation strategy, criteria, or outline that may have been developed for the species; the recovery plan for the species; articles in peer-reviewed journals; conservation plans developed by States and counties; scientific status surveys and studies; biological assessments; other unpublished materials; or experts' opinions or personal knowledge.</P>
                    <P>Habitat is dynamic, and species may move from one area to another over time. We recognize that critical habitat designated at a particular point in time may not include all of the habitat that we may later determine are necessary for the recovery of the species. For these reasons, a critical habitat designation does not signal that habitat outside the designated area is unimportant or may not be needed for recovery of the species. Areas that are important to the conservation of the species, both inside and outside the critical habitat designation, will continue to be subject to: (1) Conservation actions implemented under section 7(a)(1) of the Act; (2) regulatory protections afforded by the requirement in section 7(a)(2) of the Act for Federal agencies to ensure their actions are not likely to jeopardize the continued existence of any endangered or threatened species; and (3) section 9 of the Act's prohibitions on taking any individual of the species, including taking caused by actions that affect habitat. Federally funded or permitted projects affecting listed species outside their designated critical habitat areas may still result in jeopardy findings in some cases. These protections and conservation tools will continue to contribute to recovery of the species. Similarly, critical habitat designations made on the basis of the best available information at the time of designation will not control the direction and substance of future recovery plans, habitat conservation plans (HCPs), or other species conservation planning efforts if new information available at the time of those planning efforts calls for a different outcome.</P>
                    <HD SOURCE="HD1">Prudency Determination</HD>
                    <P>
                        Section 4(a)(3) of the Act, as amended, and implementing regulations 
                        <PRTPAGE P="62506"/>
                        (50 CFR 424.12) require that, to the maximum extent prudent and determinable, the Secretary shall designate critical habitat at the time the species is determined to be an endangered or threatened species. Our regulations (50 CFR 424.12(a)(1)) state that a designation of critical habitat is not prudent when any of the following situations exist:
                    </P>
                    <P>(i) The species is threatened by taking or other human activity, and identification of critical habitat can be expected to increase the degree of such threat to the species; or</P>
                    <P>(ii) Such designation of critical habitat would not be beneficial to the species. In determining whether a designation would not be beneficial, the factors the Services may consider include but are not limited to: Whether the present or threatened destruction, modification, or curtailment of a species' habitat or range is not a threat to the species, or whether any areas meet the definition of “critical habitat.”</P>
                    <P>As discussed in the final listing rule (81 FR 66842), there is currently no imminent threat of take attributed to collection or vandalism identified under Factor B for these species, and identification and mapping of critical habitat is not expected to initiate or increase the degree of any such threat. In our listing determination for these species, we determined that the present or threatened destruction, modification, or curtailment of habitat or range is a threat to these species. Accordingly, the designation of critical habitat is likely to be beneficial. Therefore, because none of the circumstances enumerated in our regulations at 50 CFR 424.12(a)(1) have been met, we have determined that the designation of critical habitat is prudent for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush.</P>
                    <HD SOURCE="HD1">Critical Habitat Determinability</HD>
                    <P>Having determined that designation of critical habitat is prudent for each species, under section 4(a)(3) of the Act, we must find whether critical habitat for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush is determinable. Our regulations at 50 CFR 424.12(a)(2) state that critical habitat is not determinable when one or both of the following situations exist:</P>
                    <P>(i) Data sufficient to perform required analyses are lacking, or</P>
                    <P>(ii) The biological needs of the species are not sufficiently well known to identify any area that meets the definition of “critical habitat.”</P>
                    <P>When critical habitat is not determinable, the Act allows the Service an additional year to publish a critical habitat designation (16 U.S.C. 1533(b)(6)(C)(ii)).</P>
                    <P>At the time of our proposal, we determined that critical habitat was prudent, but not determinable because we lacked specific information on the impacts of our designation (80 FR 58536). In our final listing rule, we stated we were in the process of obtaining information on the impacts of the designation (81 FR 66842). We reviewed the available information pertaining to the biological needs of the species and habitat characteristics where these species are located. This and other information represent the best scientific data available and led us to conclude that the designation of critical habitat is determinable for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush.</P>
                    <HD SOURCE="HD1">Physical or Biological Features</HD>
                    <P>In accordance with section 3(5)(A)(i) of the Act and regulations at 50 CFR 424.12(b), in determining which areas we will designate as critical habitat from within the geographical area occupied by the species at the time of listing, we consider the physical or biological features that are essential to the conservation of the species and that may require special management considerations or protection. The regulations at 50 CFR 424.02 define “physical or biological features” as the features that support the life-history needs of the species, including, but not limited to, water characteristics, soil type, geological features, sites, prey, vegetation, symbiotic species, or other features. A feature may be a single habitat characteristic or a more complex combination of habitat characteristics. Features may include habitat characteristics that support ephemeral or dynamic habitat conditions. Features may also be expressed in terms relating to principles of conservation biology, such as patch size, distribution distances, and connectivity. For example, physical features essential to the conservation of the species might include gravel of a particular size required for spawning, alkali soil for seed germination, protective cover for migration, or susceptibility to flooding or fire that maintains necessary early-successional habitat characteristics. Biological features might include prey species, forage grasses, specific kinds or ages of trees for roosting or nesting, symbiotic fungi, or absence of a particular level of nonnative species consistent with conservation needs of the listed species. The features may also be combinations of habitat characteristics and may encompass the relationship between characteristics or the necessary amount of a characteristic essential to support the life history of the species.</P>
                    <P>In considering whether features are essential to the conservation of the species, the Service may consider an appropriate quality, quantity, and spatial and temporal arrangement of habitat characteristics in the context of the life-history needs, condition, and status of the species. These characteristics include, but are not limited to, space for individual and population growth and for normal behavior; food, water, air, light, minerals, or other nutritional or physiological requirements; cover or shelter; sites for breeding, reproduction, or rearing (or development) of offspring; and habitats that are protected from disturbance.</P>
                    <P>We derive the specific physical or biological features essential to Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush from studies of the species' habitat, ecology, and life history as described below. Additional information can be found in the September 29, 2015, proposed listing rule (80 FR 58536) and the September 29, 2016, final listing rule (81 FR 66842) for these species. We have determined that the following physical or biological features are essential to the conservation of Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush.</P>
                    <HD SOURCE="HD1">Big Pine Partridge Pea, Wedge Spurge, and Sand Flax</HD>
                    <HD SOURCE="HD2">Space for Individual and Population Growth and for Normal Behavior</HD>
                    <HD SOURCE="HD3">Plant Community and Competitive Ability</HD>
                    <P>
                        Big Pine partridge pea, wedge spurge, and sand flax occur in the lower Florida Keys in Monroe County in communities classified as pine rockland and on disturbed sites adjacent to pine rocklands, such as roadside and mowed areas still dominated by native species (see more detailed description of disturbed sites below). In addition, sand flax occurs on the Miami Rock Ridge in Miami-Dade County in pine rockland, on disturbed sites adjacent to pine rockland, and on two canal banks that likely incorporated pine rockland substrate as fill (Bradley and Gann 1999, p. 61; Hodges and Bradley 2006, p. 37). These communities and their associated native plant species are described in the Background section of the September 29, 2015, proposed listing rule (80 FR 58536) and in the September 29, 2016, final listing rule (81 FR 66842) for Big Pine partridge pea, wedge spurge, and sand flax. These habitats and their associated plant communities provide 
                        <PRTPAGE P="62507"/>
                        vegetation structure that allows for adequate growing space, moisture, sunlight, pollinators, and a competitive regime that is required for Big Pine partridge pea, wedge spurge, and sand flax to persist and spread.
                    </P>
                    <P>
                        Pine rocklands are a fire-maintained ecosystem characterized by an open canopy, understory, and a limestone substrate (often exposed). Open canopy conditions are required to allow sufficient sunlight to reach the herbaceous layer and permit growth and flowering of Big Pine partridge pea, wedge spurge, and sand flax (Ross and Ruiz 1996, pp. 5-6; Bradley and Saha 2009, p. 4). These species also require a calcareous limestone substrate that varies from nearly bare to thin layers or small pockets of shallow soil to provide suitable growing conditions (
                        <E T="03">e.g.,</E>
                         pH, nutrients, anchoring, and proper drainage). As a result of these marginal soil conditions, plants such as Big Pine partridge pea, wedge spurge, and sand flax rely on sparse competition and periodic disturbance to thrive and persist. This combination of ecosystem characteristics (
                        <E T="03">i.e.,</E>
                         open canopy with a partially exposed limestone substrate and periodic disturbance) occurs only in pine rockland habitats (as opposed to rockland hammock, which occurs in conjunction with pine rockland and has a limestone substrate but a closed canopy).
                    </P>
                    <P>Disturbed areas that support Big Pine partridge pea, wedge spurge, and sand flax consist of sites that formerly were pine rocklands, but in most cases have no remaining pine canopy because of previous disturbance from clearing or scraping. In addition, some disturbed areas that support sand flax are sites where pine rockland substrate was used as fill. These include roadsides, firebreaks, and other areas that are infrequently mowed, or have no pine canopy but retain native pine rockland herbs, grass species, and substrate (Bradley and van der Heiden 2013, pp. 7-12; Bradley 2006, p. 37: Bradley and Gann 1999, p. 61).</P>
                    <P>Sand flax occurrences reported from marl prairie are at sites that have been artificially drained (Bradley and Van Der Heiden 2013, p. 11) or are scraped pine rocklands that function more like marl prairie (Kernan and Bradley 1996, p. 11). As with disturbed roadside habitats, it is possible that dry marl prairies have become refugia for the sand flax as fire regimes and natural areas were altered and destroyed over the last century. However, the Service does not consider marl prairie to be a primary habitat for sand flax.</P>
                    <P>The total remaining area of pine rockland in the lower Florida Keys (Monroe County) is now approximately 1,899 acres (ac) (769 hectares (ha)), most of which is on Big Pine Key (1,480 ac (599 ha)) (U.S. Geological Survey (USGS) 2019). In mainland south Florida (Miami-Dade County), development and agriculture have reduced pine rockland habitat by 90 percent. Recent vegetation mapping in Everglades National Park (ENP) indicates there are a total of 14,211 ac (5,751 ha) of pine rocklands remaining in ENP, which includes the largest remaining area of pine rockland (approximately 10,895 ac (4,409 ha)) in Florida (Long Pine Key) (Ruiz 2022). Outside of ENP, pine rockland habitat decreased from approximately 185,329 ac (75,000 ha) in the early 1900s to only 3,707 ac (1,500 ha) in 2014 (Possley et al. 2014, p. 154) and 2,275 ac (921 ha) in 2019 (USGS 2019), leaving only about 1.2 percent of the pine rocklands on the Miami Rock Ridge remaining, and much of what is left are small remnants scattered throughout the Miami metropolitan area, isolated from other natural areas (Herndon 1998, p. 1). Based on the data presented above, outside of ENP the total remaining area of pine rockland in Miami-Dade and Monroe Counties is now 4,174 ac (1,689 ha) (approximately 2,275 ac (921 ha) in Miami-Dade County and 1,899 ac (769 ha) in the Florida Keys (Monroe County)). The extreme rarity of high-quality pine rockland habitat supporting Big Pine partridge pea, wedge spurge, and sand flax elevates the importance of disturbed remnant sites that still retain some pine rockland species.</P>
                    <P>We consider pine rockland to be the primary habitat for Big Pine partridge pea, wedge spurge, and sand flax. However, adjacent disturbed areas currently supporting the species are considered essential when adjacent pine rocklands do not support an existing population or are of insufficient size or connectivity to support a population of Big Pine partridge pea, wedge spurge, and sand flax. Therefore, based on the information above, we identify upland habitats consisting of pine rocklands and adjacent disturbed areas to be a physical or biological feature essential to the conservation of these species.</P>
                    <HD SOURCE="HD2">Food, Water, Air, Light, Minerals, or Other Nutritional or Physiological Requirements</HD>
                    <HD SOURCE="HD3">Climate (Temperature and Precipitation)</HD>
                    <P>Big Pine partridge pea, wedge spurge, and sand flax require adequate rainfall and do not tolerate prolonged freezing temperatures. The climate of south Florida where these species occur is characterized by distinct wet and dry seasons, a monthly mean temperature above 64.4°F (F) (18° Celsius (C)) in every month of the year, and annual rainfall averaging 30 to 60 inches (in) (75 to 150 centimeters (cm)) (Gabler et al. 1994, p. 211). Rainfall within the range of sand flax varies from an annual average of 60-65 in (153-165 cm) in the northern portion of the Miami Rock Ridge to an average of 35-40 in (89-102 cm) in the lower Florida Keys (Snyder et al. 1990, p. 238). Areas of pine rockland that are adjacent to wetlands may experience prolonged flooded periods lasting up to 60 days, while those at higher elevation have shorter or no annual flooding period (Florida Natural Areas Inventory (FNAI) 2010a, p. 2). Freezes can occur in the winter months but are very infrequent at this latitude in Florida. Therefore, based on the information above, we determined a subtropical humid (Miami-Dade County) or tropical humid (Monroe County) climate to be an essential physical feature for Big Pine partridge pea, wedge spurge, and sand flax.</P>
                    <HD SOURCE="HD3">Soils</HD>
                    <P>Substrates supporting Big Pine partridge pea, wedge spurge, and sand flax are composed of oolitic limestone that is at or very near the surface. Solution holes occasionally form where the surface limestone is dissolved by organic acids. There is typically very little soil development, consisting primarily of accumulations of low-nutrient sand, marl, clayey loam, and organic debris found in solution holes, depressions, and crevices on the limestone surface (FNAI 2010a, p. 62). However, extensive sandy pockets can be found at the northern end of the Miami Rock Ridge, beginning from approximately North Miami Beach and extending south to approximately SW 216 Street (which runs east-west approximately one-half mile south of Quail Roost Pineland) (Service 1999, p. 3-162).</P>
                    <P>
                        These substrates provide anchoring, nutrients, moisture regime, and suitable soil chemistry for Big Pine partridge pea, wedge spurge, and sand flax; they facilitate a community of associated plant species that creates competition which allows Big Pine partridge pea, wedge spurge, and sand flax to persist and spread. Therefore, based on the information above, we identify substrates derived from calcareous limestone (often exposed with little soil development) that provide nutritional requirements and suitable growing conditions (
                        <E T="03">e.g.,</E>
                         pH, nutrients, anchoring and drainage) to be an essential physical feature for Big Pine 
                        <PRTPAGE P="62508"/>
                        partridge pea, wedge spurge, and sand flax.
                    </P>
                    <HD SOURCE="HD2">Cover or Shelter</HD>
                    <P>
                        As mentioned previously, Big Pine partridge pea, wedge spurge, and sand flax occur in pine rocklands and adjacent disturbed areas in the lower Florida Keys (Bradley and Gann 1999, pp. 17-18; Bradley 2006, p. 21). In addition, sand flax occurs in pine rocklands on the Miami Rock Ridge in Miami-Dade County. These pine rocklands are characterized by an open canopy of 
                        <E T="03">Pinus elliottii</E>
                         var. 
                        <E T="03">densa</E>
                         (South Florida slash pine). The shrub/understory layer is also characteristically open, although the height and density of the shrub layer varies based on fire frequency, with understory plants growing taller and denser as time since fire increases. The open canopy and understory of pine rocklands are required to allow sufficient sunlight to reach the herbaceous layer and permit growth and flowering of Big Pine partridge pea, wedge spurge, and sand flax (Bradley and Gann 1999, pp. 17-18; Bradley 2006, p. 37).
                    </P>
                    <P>Disturbed areas that are adjacent to pine rocklands that support Big Pine partridge pea, wedge spurge, and sand flax may have little to no pine canopy, but an herbaceous layer dominated by native herbs and grasses. Usually, these are former (remnant) pine rocklands that have a history of disturbance (clearing or scraping). These sites tend to be infrequently (every 2-3 months) mowed areas adjacent to existing pine rocklands, such as roadsides and fields. These areas can provide the open conditions required by Big Pine partridge pea, wedge surge, and sand flax (Bradley 2006, p. 37).</P>
                    <P>Therefore, based on the information above, we identify vegetation composition and structure characterized by an open canopy of South Florida slash pine and understory that allows for sufficient sunlight and space for individual growth and population expansion to be an essential feature for Big Pine partridge pea, wedge spurge, and sand flax.</P>
                    <HD SOURCE="HD2">Sites for Breeding, Reproduction, or Rearing (or Development) of Offspring</HD>
                    <P>Big Pine partridge pea reproduction is sexual, and flowers require insect visitation for pollination. Though many types of insects visit Big Pine partridge pea flowers, effective pollination can be performed only by buzz-pollinating bees (Liu and Koptur 2003, pp. 1184-1186). Seed production is higher when cross-pollination occurs. In addition, seed germination rates are higher from cross-pollinated flowers, suggesting that inbreeding depression occurs in seeds produced through self-pollination (Liu and Koptur 2003, pp. 1184-1186). Taken together, these findings indicate that insect pollination is crucial to the plant's reproduction and progeny fitness. Declines in pollinator visitation may cause decreased seed production, which could lead to lower seedling establishment and numbers of mature plants.</P>
                    <P>
                        The biology and demography of wedge spurge have received considerable study. Small groups of the plant are scattered widely across the pine rocklands of Big Pine Key (Herndon 1993, in Bradley and Gann 1999, p. 31), with a population estimated at 368,557 in 2014 (Bradley et al. 2015, p. 21). The population was confirmed to still be present in 2019 (Lange et al. 2019, p. 16). Wedge spurge reproduction is sexual and likely requires insect visitation for pollination. Other species of 
                        <E T="03">Chamaesyce</E>
                         are completely reliant on insects for pollination and seed production while others are capable of self-pollination. Pollinators may include bees, flies, ants, and wasps (Ehrenfeld 1976, pp. 95-97, 406).
                    </P>
                    <P>Little is known about the life history of sand flax, including pollination biology, seed production, or dispersal. Sand flax reproduction is sexual, with new plants generated from seeds. A recent study found that pollinators are important in fruit production of sand flax (Harris and Koptur 2022, pp. 7-8). Effective pollination has been found from small bees and flies that visit the flowers of sand flax (Harris and Koptur 2022, pp. 4-6). This recent information suggests that insect pollination is important to the species' reproduction. Therefore, like Big Pine partridge pea and wedge spurge, declines in pollinator visitation may cause decreased seed or fruit production of sand flax, which could lead to lower seedling establishment and numbers of mature plants.</P>
                    <P>The pine rocklands and adjacent disturbed habitats identified above as essential physical or biological features provide a plant community with associated plant species that foster a competitive regime suitable to Big Pine partridge pea, wedge spurge, and sand flax and contain adequate open space for the recruitment of new plants. Associated plant species in these habitats attract and provide cover for insect pollinators required for Big Pine partridge pea pollination, wedge spurge, and sand flax.</P>
                    <P>Therefore, based on the information above, we identify pine rockland habitat and adjacent disturbed areas containing the presence of native pollinators for natural pollination and reproduction to be an essential feature for Big Pine partridge pea, wedge spurge, and sand flax.</P>
                    <HD SOURCE="HD2">Habitats Representative of the Historical, Geographical, and Ecological Distributions of the Species</HD>
                    <P>Big Pine partridge pea, wedge spurge, and sand flax continue to occur in habitats that are representative of the species' historical, geographical, and ecological distribution, although their current ranges have been reduced. These species are currently found in pine rocklands, and they also occur in adjacent disturbed areas, such as roadsides. As described above, these habitats provide a community of associated plant and animal species that are compatible with Big Pine partridge pea, wedge spurge, and sand flax. In addition, these habitats provide the vegetation structure that provides adequate sunlight levels and open space for plant growth and regeneration, and substrates with adequate moisture availability and suitable soil chemistry needed for these species. Representative communities are located on Federal, State, local, and private conservation lands that implement conservation measures benefitting these species.</P>
                    <HD SOURCE="HD3">Disturbance Regime</HD>
                    <P>
                        Pine rockland habitat that could support or currently supports Big Pine partridge pea, wedge spurge, and sand flax depend on a disturbance regime of wild or prescribed fire to open the canopy in order to provide light levels sufficient to support these species. Fire return intervals of 5 to 7 years generate the lowest extinction and population decline probabilities for Big Pine partridge pea (Liu et al. 2005, p. 210). The historical frequency and magnitude of fire allowed for the persistence of Big Pine partridge pea, wedge spurge, and sand flax by maintaining an open canopy and understory and preventing succession (transition) of pine rocklands to hardwood-dominated community (rockland hammock). In the absence of fire, some areas of pine rockland may have closed canopies, resulting in areas lacking enough available sunlight to support Big Pine partridge pea, wedge spurge, and sand flax. Most of these areas can be enhanced if habitats are managed with a combination of mechanical hardwood removal and prescribed fire. Disturbed sites that support Big Pine partridge pea, wedge spurge, and sand flax are typically maintained by infrequent mowing. Mowing is similar in effect to fire in that 
                        <PRTPAGE P="62509"/>
                        it limits encroachment of hardwood species and maintains open canopy conditions suitable for these species. We consider wildfire to be the natural disturbance factor for pine rocklands and Big Pine partridge pea, wedge spurge, and sand flax. In adjacent disturbed areas currently supporting the species, mowing serves some of the ecological function of fire and maintains suitable habitat conditions (open canopy) for these species.
                    </P>
                    <P>
                        Therefore, based on the information above, we identify periodic natural (
                        <E T="03">e.g.,</E>
                         fire) or nonnatural (
                        <E T="03">e.g.,</E>
                         prescribed fire, mowing) disturbance regimes to maintain open canopy conditions in South Florida pine rocklands, to be an important process to maintain essential features for Big Pine partridge pea, wedge spurge, and sand flax.
                    </P>
                    <HD SOURCE="HD2">Summary of Physical or Biological Features Essential to the Conservation of Big Pine Partridge Pea, Wedge Spurge, and Sand Flax</HD>
                    <P>Based on the best available science related to the life history and ecology of these species, as outlined in the discussion above, we have determined that the following physical or biological features are essential to the conservation of Big Pine partridge pea, wedge spurge, and sand flax:</P>
                    <P>South Florida pine rockland habitat and adjacent disturbed areas:</P>
                    <P>
                        (1) Consisting of calcareous limestone substrate (often exposed with little soil development) that provides nutritional requirements and suitable growing conditions (
                        <E T="03">e.g.,</E>
                         pH, nutrients, anchoring and drainage);
                    </P>
                    <P>
                        (2) Characterized by an open canopy of 
                        <E T="03">Pinus elliottii</E>
                         var. 
                        <E T="03">densa</E>
                         (South Florida slash pine) and understory with a high proportion of native pine rockland plant species to provide for sufficient sunlight to permit growth and flowering;
                    </P>
                    <P>(3) Subjected to a monthly mean temperature characteristic of the subtropical humid classification in Miami-Dade County and tropical humid classification in Monroe County in every month of the year and short hydroperiods ranging of up to 60 days each year;</P>
                    <P>
                        (4) Subjected to periodic natural (
                        <E T="03">e.g.,</E>
                         fire) or nonnatural (
                        <E T="03">e.g.,</E>
                         prescribed fire, mowing) disturbance regimes to maintain open canopy conditions; and
                    </P>
                    <P>(5) Containing the presence of native pollinators for natural pollination and reproduction.</P>
                    <HD SOURCE="HD1">Blodgett's Silverbush</HD>
                    <HD SOURCE="HD2">Space for Individual and Population Growth and for Normal Behavior</HD>
                    <HD SOURCE="HD3">Plant Community and Competitive Ability</HD>
                    <P>
                        Blodgett's silverbush occurs in the Florida Keys in Monroe County and on the Miami Rock Ridge in Miami-Dade County in communities classified as pine rockland, rockland hammock, and coastal berm, as well as disturbed sites adjacent to these habitats, such as roadsides and mowed areas still dominated by native species (Bradley and Gann 1999, p. 3). These communities and their associated native plant species are described in the final listing rule for Blodgett's silverbush published in the 
                        <E T="04">Federal Register</E>
                         on September 29, 2016 (81 FR 66842). These habitats and their associated plant communities provide vegetation structure that allows for adequate growing space, moisture, sunlight, pollinators, and a competitive regime that is required for Blodgett's silverbush to persist and spread. As discussed above for Big Pine partridge pea, wedge spurge, and sand flax, pine rocklands are a fire-maintained ecosystem characterized by an open canopy and understory and a limestone substrate (often exposed). Rockland hammock is a species-rich tropical hardwood forest on upland sites in areas where limestone is very near the surface and often exposed. Coastal berms are landscape features found along low-energy coastlines in south Florida and the Florida Keys. Coastal berm is a short forest or shrub thicket found on long, narrow, storm-deposited ridges (sand dunes) of loose sediment formed by a mixture of coarse shell fragments, pieces of coralline algae, and other coastal debris.
                    </P>
                    <P>
                        Similar to the other species, open canopy conditions are required to allow sufficient sunlight to reach the herbaceous layer and permit growth and flowering of Blodgett's silverbush. These conditions are maintained by fire in pine rocklands. In rockland hammocks, only the edges and canopy disruption in the interior provide enough sunlight for Blodgett's silverbush. Canopy disruption on rockland hammocks can occur due to natural events such as hurricanes and storm surge. Human disturbance, especially mowing, also maintains suitable conditions in disturbed areas, as discussed above for Big Pine partridge pea, wedge spurge, and sand flax. The plant also requires a calcareous limestone substrate that varies from nearly bare to thin layers or small pockets of shallow soil in pine rocklands, to shallow organic soils over calcareous limestone in rockland hammocks, and deep, calcareous sandy soils typical of coastal berm to provide suitable growing conditions (
                        <E T="03">e.g.,</E>
                         pH, nutrients, anchoring, and proper drainage). As a result of these marginal soil conditions, plants such as Blodgett's silverbush rely on sparse competition and periodic disturbance to thrive and persist. This combination of ecosystem characteristics (
                        <E T="03">i.e.,</E>
                         open canopy and limestone substrate) occurs in pine rocklands, along edges and gaps in rockland hammocks, and in coastal berm.
                    </P>
                    <P>Disturbed areas that support Blodgett's silverbush consist of sites that formerly were pine rocklands or rockland hammocks, but in most cases have no remaining pine or hardwood canopy because of previous disturbance (clearing or scraping). These include roadsides, firebreaks, and other areas that are infrequently mowed or have no tree canopy but retain native herbs, grass species, and substrate (Bradley 2006, p. 37: Bradley and Gann 1999, p. 61).</P>
                    <P>Loss of pine rockland habitat in Miami-Dade and Monroe County is discussed above for Big Pine partridge pea, wedge spurge, and sand flax. In addition, modification and destruction from residential and commercial development have severely impacted rockland hammocks and coastal berm that support Blodgett's silverbush. Rockland hammocks were once abundant in Miami-Dade and Monroe Counties but are now considered imperiled locally and globally (FNAI 2010b, pp. 24-26). The tremendous development and agricultural pressures in south Florida have resulted in significant reductions of rockland hammock (Phillips 1940, p. 167; Snyder et al. 1990, pp. 271-272; FNAI 2010b, pp. 24-26).</P>
                    <P>The extreme rarity of high-quality pine rockland, rockland hammock, and coastal berm habitat supporting Blodgett's silverbush in Miami-Dade and Monroe Counties elevates the importance of disturbed remnant sites that still retain some habitat values.</P>
                    <P>
                        We consider pine rocklands, edges or gaps in rockland hammocks, and coastal berm to be the primary habitats for Blodgett's silverbush. However, adjacent disturbed areas currently supporting the species are considered more important when adjacent pine rocklands, rockland hammocks, or coastal berm do not support an existing population, or are of insufficient size or connectivity to support a population of Blodgett's silverbush. Therefore, based on the information above, we identify upland 
                        <PRTPAGE P="62510"/>
                        habitats consisting of pine rocklands, rockland hammocks, coastal berms, and adjacent disturbed areas to be physical or biological features essential to the conservation of Blodgett's silverbush.
                    </P>
                    <HD SOURCE="HD2">Food, Water, Air, Light, Minerals, or Other Nutritional or Physiological Requirements</HD>
                    <HD SOURCE="HD3">Climate (Temperature and Precipitation)</HD>
                    <P>Blodgett's silverbush requires adequate rainfall and does not tolerate prolonged freezing temperatures. The climate of south Florida where Blodgett's silverbush occurs is classified as subtropical humid (Miami-Dade County) and tropical humid (Monroe County), as described above for Big Pine partridge pea, wedge spurge, and sand flax. Rainfall within the range of Blodgett's silverbush varies from an annual average of 60-65 in (153-165 cm) in the northern portion of the Miami Rock Ridge to an average of 35-40 in (89-102 cm) in the lower Florida Keys (Snyder et al. 1990, p. 238). Areas of pine rockland that are adjacent to wetlands may experience prolonged flooded periods lasting up to 60 days, while those at higher elevation have shorter or no annual flooding period (FNAI 2010a, p. 2). Freezes can occur in the winter months but are very infrequent at this latitude in Florida. Therefore, based on the information above, we determined this type of climate to be an essential physical feature for Blodgett's silverbush.</P>
                    <HD SOURCE="HD3">Soils</HD>
                    <P>Substrates supporting Blodgett's silverbush are composed of oolitic limestone that is at or very near the surface. Solution holes occasionally form where the surface limestone is dissolved by organic acids. In pine rocklands, there is typically very little soil development, consisting primarily of accumulations of low-nutrient sand, marl, clayey loam, and organic debris found in solution holes, depressions, and crevices on the limestone surface (FNAI 2010a, p. 62). However, extensive sandy pockets can be found at the northern end of the Miami Rock Ridge, beginning from approximately North Miami Beach and extending south to approximately SW 216 Street (which runs east-west approximately one-half mile south of Quail Roost Pineland) (Service 1999, p. 3-162). Rockland hammock occurs on a thin layer of highly organic soil covering limestone on high ground that does not regularly flood (FNAI 2010b p. 1). In coastal berms, deep, calcareous sandy soils are the typical substrate of this habitat.</P>
                    <P>
                        These substrates provide anchoring, nutrients, moisture regime, and suitable soil chemistry for Blodgett's silverbush; and facilitate a community of associated plant species that create a competitive regime that allows Blodgett's silverbush to persist and spread. Therefore, based on the information above, we identify substrates derived from calcareous limestone (often exposed with little soil development in pine rocklands; with a thin to thick organic soil layer in the case of rockland hammocks; deep, calcareous soils in coastal berm) that provide nutritional requirements and suitable growing conditions (
                        <E T="03">e.g.,</E>
                         pH, nutrients, anchoring and drainage) to be an essential physical feature for Blodgett's silverbush.
                    </P>
                    <HD SOURCE="HD2">Cover or Shelter</HD>
                    <P>As previously mentioned, Blodgett's silverbush occurs in pine rockland, rockland hammock, and coastal berm habitats in the lower Florida Keys in Monroe County and the Miami Rock Ridge in Miami-Dade County; and adjacent disturbed areas (Bradley and Gann, 1999, p. 3). Pine rocklands of the Florida Keys are characterized by an open canopy of South Florida slash pine. The shrub/understory layer is also characteristically open, although the height and density of the shrub layer varies based on fire frequency, with understory plants growing taller and denser as time since fire increases. The open canopy and understory of pine rocklands are required to allow sufficient sunlight to reach the herbaceous layer and permit growth and flowering of Blodgett's silverbush (Ross and Ruiz 1996, pp. 5-6; Bradley and Saha 2009, p.4).</P>
                    <P>Rockland hammock forest floor is largely covered by leaf litter and may have an organic soil layer of variable depth. Rockland hammocks typically have larger, more mature trees and deep organic soil layer in the interior, while the margins can be almost impenetrable in places with dense growth of smaller shrubs, trees, and vines and shallow organic soil layer. Mature hammocks may be open beneath a tall, well-defined canopy and subcanopy. More commonly, in less mature or disturbed hammocks, dense woody vegetation of varying heights from canopy to short shrubs is often present. Herbaceous species are occasionally present and generally sparse in coverage (FNAI 2010b p. 1).</P>
                    <P>Coastal berm is a short forest or shrub thicket found on long, narrow, storm-deposited ridges (sand dunes). Structure and composition of the vegetation is variable depending on height and time since the last storm event. The most stable berms may share some tree species with rockland hammocks, but generally have a greater proportion of shrubs and herbs. This is a structurally variable community that may appear in various stages of succession following storm disturbance, from scattered herbaceous beach colonizers to a dense stand of tall shrubs (FNAI 2010c, p. 2).</P>
                    <P>Disturbed areas that are adjacent to pine rocklands, rockland hammocks, and coastal berms that support Blodgett's silverbush may have little to no pine or hardwood canopy, but an herbaceous layer dominated by native herbs and grasses. Usually these are former (remnant) pine rocklands or rockland hammocks that have a history of disturbance (clearing or scraping). These sites tend to be infrequently (every 2-3 months) mowed areas adjacent to existing pine rocklands or rockland hammocks, such as roadsides and fields. These areas provide the open conditions required by Blodgett's silverbush (Bradley 2006, p. 37).</P>
                    <P>Therefore, based on the information above, we identify vegetation composition and structure characterized by an open canopy and understory that allows for sufficient sunlight, and space for individual growth and population expansion, to be an essential feature for Blodgett's silverbush.</P>
                    <HD SOURCE="HD2">Sites for Breeding, Reproduction, or Rearing (or Development) of Offspring</HD>
                    <P>Little is known about the life history of Blodgett's silverbush, including pollination biology, seed production, or dispersal. Blodgett's silverbush reproduction is sexual, with new plants generated from seeds. This species likely requires insect visitation for pollination, although there is limited information on this.</P>
                    <P>The pine rocklands, rockland hammocks, coastal berms, and adjacent disturbed habitats identified above as physical or biological features provide a plant community with associated plant species that foster a competitive regime suitable to Blodgett's silverbush and contain adequate open space for the recruitment of new plants. Associated plant species in these habitats attract and provide cover for insect pollinators required for Blodgett's silverbush pollination.</P>
                    <P>
                        Therefore, based on the information above, we identify pine rockland, rockland hammock, and coastal berm habitat and adjacent disturbed areas containing the presence of native pollinators for natural pollination and reproduction to be an essential feature for Blodgett's silverbush.
                        <PRTPAGE P="62511"/>
                    </P>
                    <HD SOURCE="HD2">Habitats Representative of the Historical, Geographic, and Ecological Distributions of the Species</HD>
                    <P>Blodgett's silverbush continues to occur in habitats that are representative of the species' historical, geographical, and ecological distribution although its range has been reduced. The species is currently found in pine rocklands, rockland hammocks, and coastal berms, and it also occurs in adjacent disturbed areas. As described above, these habitats provide a community of associated plant and animal species that are compatible with Blodgett's silverbush, vegetation structure that provides adequate sunlight levels and open space for plant growth and regeneration, and substrates with adequate moisture availability and suitable soil chemistry. Representative communities are located on Federal, State, local, and private conservation lands that implement conservation measures benefitting the species.</P>
                    <HD SOURCE="HD2">Disturbance Regime</HD>
                    <P>Pine rockland habitat that could or currently support Blodgett's silverbush depend on a disturbance regime of wild or prescribed fire to open the canopy and provide light levels sufficient to support Blodgett's silverbush. The historical frequency and magnitude of fire allowed for the persistence of Blodgett's silverbush, maintaining an open canopy and understory, and preventing succession (transition) of pine rocklands to hardwood-dominated community (rockland hammock). In the absence of fire, some areas of pine rockland may have closed canopies, resulting in areas lacking enough available sunlight to support Blodgett's silverbush. Most of these areas can be restored if habitats are managed with a combination of mechanical hardwood removal and prescribed fire.</P>
                    <P>Rockland hammock is susceptible to fire, frost, canopy disruption, and ground water reduction. Rockland hammock can be the advanced successional stage of pine rockland, especially in cases where rockland hammock is adjacent to pine rockland. In such cases, when fire is excluded from pine rockland for 15 to 25 years, it can succeed to rockland hammock vegetation. Historically, rockland hammocks in south Florida evolved with fire in the landscape, fire most often extinguished near the edges when it encountered the hammock's moist microclimate and litter layer. However, rockland hammocks are susceptible to damage from fire during extreme drought or when the water table is lowered. In these cases, fire can cause tree mortality and consume the organic soil layer. Rockland hammocks are also sensitive to the strong winds and storm surge associated with hurricanes (FNAI 2010b p. 2).</P>
                    <P>Coastal berms are deposited by storm waves along low-energy coasts. Their distance inland depends on the height of the storm surge. Coastal berms that are deposited far enough inland and remain undisturbed may in time succeed to hammock. This is a structurally variable community that may appear in various stages of succession following storm disturbance, from scattered herbaceous beach colonizers to a dense stand of tall shrubs (FNAI 2010c, p. 2).</P>
                    <P>The sparsely vegetated edges or interior portions laid open by canopy disruption are the areas of rockland hammock and coastal berm that have light levels sufficient to support Blodgett's silverbush. However, the dynamic nature of the habitat means that areas not currently open may become open in the future as a result of canopy disruption from hurricanes, while areas currently open may develop denser canopy over time, eventually rendering that portion of the hammock unsuitable for Blodgett's silverbush.</P>
                    <P>Disturbed sites that support Blodgett's silverbush are typically maintained by infrequent mowing. Mowing is similar in effect to fire in that it limits encroachment of hardwood species and maintains open canopy conditions suitable for Blodgett's silverbush. We consider wildfire to be the natural disturbance factor for pine rocklands. Periodic hurricanes and storm surge are the natural disturbance factors for rockland hammock and coastal berm. In adjacent disturbed areas currently supporting the species, mowing serves some of the ecological function of fire and maintains suitable habitat conditions (open canopy) for the species.</P>
                    <P>
                        Therefore, based on the information above, we identify periodic natural (
                        <E T="03">e.g.,</E>
                         fire, hurricanes) or nonnatural (
                        <E T="03">e.g.,</E>
                         prescribed fire, mowing) disturbance regimes that maintain open canopy conditions to be essential features for Blodgett's silverbush.
                    </P>
                    <HD SOURCE="HD2">Summary of Physical or Biological Features Essential to the Conservation of Blodgett's Silverbush</HD>
                    <P>Based on the best available science related to the life history and ecology of the species, as outlined in the discussion above, we have determined that the following physical or biological features are essential to the conservation of Blodgett's silverbush:</P>
                    <P>South Florida pine rockland, rockland hammock, or coastal berm habitats and adjacent disturbed areas:</P>
                    <P>
                        (1) Consisting of limestone substrate that provides nutritional requirements and suitable growing conditions (
                        <E T="03">e.g.,</E>
                         pH, nutrients, anchoring and drainage);
                    </P>
                    <P>(2) Characterized by an open canopy and understory with a high proportion of native plant species to provide for sufficient sunlight to permit growth and flowering;</P>
                    <P>(3) Subjected to a monthly mean temperature characteristic of the subtropical humid classification in Miami-Dade County and tropical humid classification in Monroe County in every month of the year, with short hydroperiods ranging of up to 60 days each year;</P>
                    <P>
                        (4) Subjected to periodic natural (
                        <E T="03">e.g.,</E>
                         fire, hurricanes, storm surge) or nonnatural (
                        <E T="03">e.g.,</E>
                         prescribed fire, mowing) disturbance regimes to maintain open canopy conditions; and
                    </P>
                    <P>(5) Containing the presence of native pollinators for natural pollination and reproduction.</P>
                    <HD SOURCE="HD1">Special Management Considerations or Protection</HD>
                    <P>When designating critical habitat, we assess whether the specific areas within the geographical area occupied by the species at the time of listing contain features which are essential to the conservation of the species and which may require special management considerations or protection. The features essential to the conservation of Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush may require special management considerations or protection to reduce threats related to habitat loss, fragmentation, and modification primarily due to development; inadequate fire management; nonnative plants; hurricanes and storm surge; changes in disturbance regime; and sea level rise. For an in-depth discussion of threats, see Summary of Factors Affecting the Species in our September 29, 2015, proposed listing rule (80 FR 58536) and September 29, 2016, final listing rule (81 FR 66842).</P>
                    <P>
                        Some of these threats (
                        <E T="03">e.g.,</E>
                         habitat loss, inadequate fire management) can be addressed by special management considerations or protection while others (
                        <E T="03">e.g.,</E>
                         sea level rise, hurricanes, storm surge) may be beyond the control of landowners and managers. However, even when landowners or land managers may not be able to control all the threats, they may be able to address or ameliorate the effects of the threats. Habitat loss is a primary threat to Big Pine partridge pea, wedge spurge, sand 
                        <PRTPAGE P="62512"/>
                        flax, and Blodgett's silverbush. Loss of pine rocklands, rockland hammock, and coastal berm to development has reduced these habitats in Monroe and Miami-Dade Counties.
                    </P>
                    <P>Habitat fragmentation can have negative effects on populations, especially rare plants, and can affect survival and recovery (Aguilar et al. 2006, pp. 968-980; Aguilar et al. 2008, pp. 5177-5188; Potts et al. 2010, pp. 345-352). In general, habitat fragmentation causes habitat loss, habitat degradation, habitat isolation, changes in species composition, changes in species interactions, increased edge effects, and reduced habitat connectivity (Fahrig 2003, pp. 487-515; Fischer and Lindenmayer 2007, pp. 265-280). Habitat fragments are often functionally smaller than they appear because edge effects (such as increased nonnative, invasive species or wind speeds) impact the available habitat within the fragment (Lienert and Fischer 2003, p. 597). For example, decreases in Big Pine partridge pea seed production near urban areas due to increased seed predation, compared with areas away from development have been reported (Liu and Koptur 2003, p. 1184).</P>
                    <P>
                        Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush occur on a mix of private and publicly owned lands, most of which are managed for conservation. Populations that occur on private land or non-conservation public land are vulnerable to habitat loss, while populations on conservation lands are vulnerable to the effects of habitat degradation if disturbance regimes are disrupted (
                        <E T="03">e.g.,</E>
                         through inadequate fire management or change in management practices on disturbed sites that support the species). Prolonged lack of fire in pine rockland typically results in succession to rockland hammock, and displacement of native species by invasive, nonnative plants often occurs. Changes in management practices at disturbed sites may include changes in mowing frequency or height, herbicide use, deposition of fill material, and sodding. Further development and degradation of pine rockland, rockland hammock, and coastal berm increase fragmentation and decrease the conservation value of the remaining functioning habitats. In addition, pine rocklands are expected to be further degraded and fragmented due to anticipated sea level rise, which would fully or partially inundate most pine rocklands and increase salinity of the water table and soils. These impacts are likely to cause vegetation shifts in additional pine rocklands, particularly in the lower Florida Keys. Some existing pine rockland, rockland hammock, and coastal berm areas are also projected to be developed for housing as the human population grows and adjusts to rising sea levels.
                    </P>
                    <P>In summary, the features essential to the conservation of Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush may require special management considerations or protection to reduce threats and conserve these features. Actions that could ameliorate threats include, but are not limited to:</P>
                    <P>(1) Increase habitat restoration and management efforts, including fire management and nonnative plant control;</P>
                    <P>(2) Protect, restore, or enhance inland or higher elevation habitats where these species occur and are predicted to be unaffected or less affected by sea level rise;</P>
                    <P>(3) Augment existing small populations; and</P>
                    <P>(4) Conduct annual or seasonal monitoring efforts, or monitoring conducted prior to, but coordinated with habitat and fire management planning to refine management efforts over time.</P>
                    <HD SOURCE="HD1">Criteria Used To Identify Critical Habitat</HD>
                    <P>As required by section 4(b)(2) of the Act, we use the best scientific data available to designate critical habitat. In accordance with the Act and our implementing regulations at 50 CFR 424.12(b), we review available information pertaining to the habitat requirements of the species and identify specific areas within the geographical area occupied by the species at the time of listing and any specific areas outside the geographical area occupied by the species to be considered for designation as critical habitat.</P>
                    <P>We are proposing to designate critical habitat in areas within the geographical area occupied by these species at the time of listing in 2016. At this time, we have not identified specific areas outside the geographical range occupied by the species that are essential for the species' conservation. However, as discussed below, we are considering whether areas outside the geographical range of the Big Pine Partridge Pea, wedge spurge, and sand flax at the time of listing meet the definition of critical habitat. If we determine some or all of those areas are critical habitat for these species, we will include them in our final designation.</P>
                    <P>
                        We anticipate that full recovery for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush will require continued protection of the remaining extant populations and habitat and augmenting existing small populations. Recovery of Big Pine partridge pea, wedge spurge, and sand flax may also require reestablishing populations in additional areas (
                        <E T="03">i.e.,</E>
                         unoccupied areas) to approximate more closely the species' historical distribution to ensure adequate numbers of plants exist in stable populations and these populations occur over their entire geographic range. This scenario could help to reduce the chance that catastrophic events, such as storms, will simultaneously affect all known populations. However, some of the historical locations no longer contain suitable habitat, and thus are not proposed.
                    </P>
                    <P>Small plant populations or those with limited distributions, such as Big Pine partridge pea, wedge spurge, and sand flax, are vulnerable to relatively minor environmental disturbances (Frankham 2005, pp. 135-136) that could result in the loss of genetic diversity from genetic drift, the random loss of genes, and inbreeding (Ellstrand and Elam 1993, pp. 217-237; Leimu et al. 2006, pp. 942-952). Plant populations with lowered genetic diversity are more prone to local extinction (Barrett and Kohn 1991, pp. 4, 28). Smaller plant populations generally have lower genetic diversity, and lower genetic diversity may in turn lead to even smaller populations by decreasing the species' ability to adapt, thereby increasing the probability of population extinction (Newman and Pilson 1997, p. 360; Palstra and Ruzzante 2008, pp. 3428-3447). Because of the dangers associated with small populations or limited distributions, the recovery of many rare plant species, such as Big Pine partridge pea, wedge spurge, and sand flax, may include the creation of new sites or reintroductions to ameliorate these effects.</P>
                    <P>In considering our proposal of critical habitat, we identified the following conservation strategy and goals for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush:</P>
                    <P>(1) Conserve existing viable populations with sufficient native habitat;</P>
                    <P>(2) Work with partners to conserve existing populations, and implement efforts that will benefit the species and its habitat; and</P>
                    <P>(3) Augment existing populations and facilitate establishment/reestablishment of populations into suitable protected habitat.</P>
                    <P>
                        To facilitate the application of our conservation strategy and goals for these species, we utilized the Shaffer and Stein (2000, entire) methodology for 
                        <PRTPAGE P="62513"/>
                        conserving the resiliency, representation, and redundancy of imperiled species. Resiliency is the ability to sustain populations through the natural range of favorable and unfavorable conditions. Representation ensures adaptive capacity within a species and allows it to respond to environmental changes. This can be facilitated by conserving not just genetic diversity, but also the species' associated habitat type and plant communities. Redundancy ensures an adequate number of sites with resilient populations such that the species has the ability to withstand catastrophic events. Implementation of this methodology has been widely accepted as a reasonable conservation strategy (Tear et al. 2005, p. 841).
                    </P>
                    <HD SOURCE="HD1">Big Pine Partridge Pea</HD>
                    <P>Big Pine partridge pea is endemic to the lower Florida Keys in Monroe County, Florida. Historical records exist for occurrences in pine rocklands on five islands: Big Pine Key, Ramrod Key, Cudjoe Key, No Name Key, and Lower Sugarloaf Key (Hodges and Bradley 2006, pp. 20-21). At the time of listing and currently, native populations of the plant occur only on Big Pine Key and Cudjoe Key since the species has been extirpated from Ramrod Key and Lower Sugarloaf Key (Bradley and Gann 1999, p. 18; Hodges and Bradley 2006, p. 21; Lange et al. 2019). In 2019, a population was successfully introduced in NKDR on No Name Key. Except for Ramrod Key, all these Keys still contain pine rockland habitat. While the Big Pine Key population is relatively large, estimated at 313,914 plants in 2013 (Bradley et al. 2015, p. 21), the Cudjoe Key population was relatively small, consisting of approximately 150 individuals ((Hodges and Bradley 2006, p. 21), and recent surveys did not find the species there (Lange et al. 2019, p. 16). Therefore, if the species is not found at Cudjoe Key during future surveys, reintroductions may be needed at Cudjoe Key.</P>
                    <P>Given the species occurs only within the lower Florida Keys, it has inherently low redundancy; with only two extant populations at the time of listing, the current redundancy of native populations has been even further reduced from historical levels. In addition, because there currently are three populations (two native and one reintroduced) across the naturally limited historical range of the species, Big Pine partridge pea is vulnerable to stochastic extinction events from natural or other disturbances (such as hurricanes or storm surge) that could affect the entire geographic range of the species. Both natural populations occur on small islands where the amount of suitable remaining habitat is limited (low resiliency), and much of the remaining habitat may be lost to sea level rise over the next century. Therefore, we are proposing critical habitat units that contain the physical or biological features essential to the conservation of the species and that support both extant populations at the time of listing.</P>
                    <P>Additionally, we acknowledge that areas unoccupied at the time of listing may be essential for the conservation of the Big Pine partridge pea. We are considering whether areas of remaining pine rockland habitat on Little Pine Key, No Name Key, and Sugarloaf Keys meet the definition of critical habitat. The area on Little Pine Key consists of approximately 97 ac (39 ha) of pine rockland habitat in Monroe County and is comprised entirely of lands in Federal ownership, 100 percent of which are located within NKDR. Pine rocklands cover about two-thirds of the interior portion of the island. We note that this area wholly overlaps with designated critical habitat for silver rice rat and Bartram's scrub-hairstreak butterfly. The area on No Name Key includes approximately 123 ac (50 ha) of pine rockland habitat in Monroe County comprised of a combination of Federal lands within NKDR, State lands, County lands, and property in private or other ownership). State lands are interspersed within NKDR lands and managed as part of the Refuge. We note that this area wholly overlaps with designated critical habitat for Bartram's scrub-hairstreak butterfly. Finally, on Sugarloaf Keys, we are considering approximately 73 ac (30 ha) of pine rockland habitat north of U.S. 1, comprised of a combination of Federal lands within NKDR, County lands, and property in private or other ownership. We note that these areas on Sugarloaf Keys wholly overlap with the areas being proposed as critical habitat for the sand flax and the endangered key deer occurs throughout this area. We will determine whether these areas are essential to protect habitat needed to recover the species and establish new populations within the range of the species such that they meet the definition of critical habitat. If we decide some or all of these areas are essential to the conservation of the Big Pine partridge pea, we will include them in our final critical habitat determination (see also Information Requested, above).</P>
                    <HD SOURCE="HD1">Wedge Spurge</HD>
                    <P>Wedge spurge is endemic to the lower Florida Keys in Monroe County, Florida. Its historical range encompassed pine rocklands on Big Pine Key. At the time of listing and currently, the only native population of the plant currently occurs on Big Pine Key, with small groups of plants scattered widely across the island. The Big Pine population is relatively large, estimated at 368,557 individuals in 2014 (Bradley et al. 2015, pp. 24-25); the presence of this population was verified in 2019 (Lange et al. 2019, p. 16). However, since the time the species was listed, a population was successfully introduced in NKDR on No Name Key. While the Big Pine Key population is relatively large, estimated at 368,557 individuals in 2014 (Bradley et al. 2015, pp. 24-25), it is the only extant native population.</P>
                    <P>Given the species occurs within the lower Florida Keys, it has inherently low redundancy; with only one extant populations at the time of listing, the current redundancy of native population has been reduced from historical levels. Because there currently are only two populations (one native and one introduced) across the naturally limited historical range, wedge spurge is vulnerable to stochastic extinction events from natural or other disturbances (such as hurricanes or storm surge) that could affect the entire geographic range of wedge spurge. The sole natural population occurs on a small island where the amount of suitable habitat is limited (low resiliency) and much of that habitat may be lost to sea level rise over the next century. Therefore, the resiliency of the population and redundancy of the wedge spurge will continue to be limited by the amount of pine rockland habitat remaining in the lower Florida Keys. We are proposing a critical habitat unit that contains the physical or biological features essential to the conservation of the species and supports the single native population on Big Pine Key extant at the time of listing.</P>
                    <P>
                        Additionally, we acknowledge that areas unoccupied at the time of listing may be essential for the conservation of the wedge spurge. We are considering whether areas of remaining pine rockland habitat on Little Pine Key, No Name Key, Cudjoe Key, and Sugarloaf Keys of the wedge spurge meet the definition of critical habitat. The area on Little Pine Key consists of approximately 97 ac (39 ha) of pine rockland habitat in Monroe County and is comprised entirely of lands in Federal ownership, 100 percent of which are located within NKDR. Pine rocklands cover about two-thirds of the interior portion of the island. We note that this area wholly overlaps with designated critical habitat for silver rice rat and 
                        <PRTPAGE P="62514"/>
                        Bartram's scrub-hairstreak butterfly. The area on No Name Key includes approximately 123 ac (50 ha) of pine rockland habitat in Monroe County comprised of a combination of Federal lands within NKDR, State lands, County lands, and property in private or other ownership. State lands are interspersed within NKDR lands and managed as part of the Refuge. We note that this area wholly overlaps with designated critical habitat for Bartram's scrub-hairstreak butterfly. The area on Cudjoe Key consists of approximately 88 ac (33 ha) of pine rockland habitat in Monroe County and is comprised of a combination of Federal lands within NKDR, State lands, County lands, and property in private or other ownership. State lands are interspersed within NKDR lands and managed as part of the Refuge. We note that this area wholly overlaps with designated critical habitat for silver rice rat. Finally, on Sugarloaf Keys, we are considering approximately 73 ac (30 ha) of pine rockland habitat north of U.S. 1, comprised of a combination of Federal lands within NKDR, County lands, and property in private or other ownership. We note that these areas on Sugarloaf Keys wholly overlap with the areas being proposed as critical habitat for the sand flax and the endangered key deer occurs throughout this area. We will determine whether these areas are essential to protect habitat needed to recover the species and establish new populations within the range of the species such that they meet the definition of critical habitat. If we decide some or all of these areas are essential for the conservation of the wedge spurge, we will include them in our final critical habitat determination (see also Information Requested, above).
                    </P>
                    <HD SOURCE="HD1">Sand Flax</HD>
                    <P>Sand flax has a historical range consisting of central and southern Miami-Dade County and Monroe County in the lower Florida Keys (Bradley and Gann 1999, p. 61). At the time of listing and currently, there were twelve extant populations of sand flax, with eight extant populations in Miami-Dade County and four extant populations in the Florida Keys. In Miami-Dade County, historical records for the species were widespread from the Coconut Grove area to the southern part of the county, close to what is now the main entrance to ENP and Turkey Point (Bradley and Gann 1999, p. 61). In 2013, sand flax populations were found at six sites, containing an estimated total of 107,060 plants (Bradley and van der Heiden 2013, p. 4). In Miami-Dade County, recent observations include confirmation of the species' continued presence at the Richmond Pinelands, Martinez Pineland Preserve, Department of Defense (DoD) Special Operations Command South (SOCSO) and Homestead Air Reserve Base (HARB), and the C-102 and L-31E canal levee populations. Additionally, a new population was established at Rockdale Pineland in 2019 (Possley, pers. comm. 2019). The four largest populations of sand flax include Homestead, Florida (located on the HARB and SOCSO DoD sites), estimated at 96,037 individuals; the C-102 canal levee and L-31E canal levee sites, estimated at 1,000 to 10,000 plants, respectively; and Big Pine Key, estimated at 2,676 individuals. All other sites have fewer than 100 individuals, except Martinez pinelands (100-200 individuals) and Lower Sugarloaf Key (531 individuals). Two populations occupy levees that cannot be restored to pine rockland habitat, rendering sand flax vulnerable to stochastic extinction events from natural or other disturbances (such as hurricanes or storm surge) that could affect the entire geographic range of sand flax.</P>
                    <P>In the Florida Keys (Monroe County), there are historical records of the species from Big Pine Key, Ramrod Key, Upper and Lower Sugarloaf Keys, Park Key, Boca Chica Key, Middle Torch Key (Bradley and Gann 1999, p. 61), and Big Torch Key (Hodges 2010, p. 10). The current distribution of sand flax includes four islands: Big Pine Key, Upper and Lower Sugarloaf Keys, and Big Torch Key. Additionally, a population was successfully introduced in NKDR on No Name Key since the time of listing.</P>
                    <P>Resiliency of sand flax will continue to be limited by the reduced amount of pine rockland habitat remaining in Florida. All Miami-Dade populations are on small remnant pine rockland sites and adjacent disturbed areas, while all Monroe County populations occur on small islands. In both cases, the amount of suitable remaining habitat is limited (low resiliency) and much of the remaining habitat may be lost to sea level rise over the next century. Therefore, we are proposing critical habitat units that contain the physical or biological features essential to the conservation of the species and support the seven extant populations at the time of listing.</P>
                    <P>
                        Additionally, we acknowledge that areas unoccupied at the time of listing may be essential for the conservation of the sand flax. We are considering whether areas of remaining pine rockland habitat on Little Pine Key, No Name Key, Cudjoe Key, and Sugarloaf Keys of the wedge spurge meet the definition of critical habitat. The area on Little Pine Key consists of approximately 97 ac (39 ha) of pine rockland habitat in Monroe County and is comprised entirely of lands in Federal ownership, 100 percent of which are located within NKDR. Pine rocklands cover about two-thirds of the interior portion of the island. We note that this area wholly overlaps with designated critical habitat for silver rice rat and Bartram's scrub-hairstreak butterfly. The area on No Name Key includes approximately 123 ac (50 ha) of pine rockland habitat in Monroe County comprised of a combination of Federal lands within NKDR, State lands, County lands, and property in private or other ownership. State lands are interspersed within NKDR lands and managed as part of the Refuge. We note that this area wholly overlaps with designated critical habitat for Bartram's scrub-hairstreak butterfly. The area on Cudjoe Key consists of approximately 88 ac (33 ha) of pine rockland habitat in Monroe County and is comprised of a combination of Federal lands within NKDR, State lands, County lands, and property in private or other ownership. State lands are interspersed within NKDR lands and managed as part of the Refuge. We note that this area wholly overlaps with designated critical habitat for silver rice rat. The area of Trinity Pinelands consists of approximately 48 ac (19 ha) of pine rockland habitat in Miami-Dade County and is comprised of a combination of State lands, County lands, and property in private or other ownership. We note that this area wholly overlaps with designated critical habitat for Carter's small-flowered flax (
                        <E T="03">Linum carteri var. carteri</E>
                        ) and Florida brickell-bush. The area of Nixon Smiley consists of approximately 264 ac (107 ha) of pine rockland habitat in Miami-Dade County comprised of a combination of State lands, County lands, and property in private or other ownership. We note that this area wholly overlaps with designated critical habitat for Carter's small-flowered flax and Florida brickell-bush. The area of U.S. Department of Agriculture (USDA) Subtropical Horticulture Research Station consists of approximately 297 ac (120 ha) of pine rockland habitat in Miami-Dade County and is comprised of a combination of Federal lands, State lands, and property in private or other ownership. We note that this area wholly overlaps with designated critical habitat for Carter's small-flowered flax and Florida brickell-bush. The area of Quail's Roost consists of approximately 256 ac (104 ha) of pine rockland habitat in Miami-Dade County and is comprised 
                        <PRTPAGE P="62515"/>
                        of a combination of State lands, County lands, and property in private or other ownership. We note that this area wholly overlaps with designated critical habitat for Carter's small-flowered flax, Florida brickell-bush, and Bartram's scrub hairstreak butterfly. The area of Navy Wells consists of approximately 558 ac (226 ha) of pine rockland habitat in Miami-Dade County and is comprised of a combination of State lands, County lands, and property in private or other ownership. We note that this area wholly overlaps with designated critical habitat for Carter's small-flowered flax, Florida brickell-bush, Bartram's scrub hairstreak butterfly, and Florida leafwing butterfly. We will determine whether these areas are essential to protect habitat needed to recover the species and establish new populations within the range of the species such that they meet the definition of critical habitat. If we decide some or all of these areas are essential for the conservation of the wedge spurge, we will include them in our final critical habitat determination (see also Information Requested, above).
                    </P>
                    <HD SOURCE="HD1">Blodgett's Silverbush</HD>
                    <P>Blodgett's silverbush historically occurred from central and southern Miami-Dade County from Brickell Hammock to Long Pine Key in ENP, and in Monroe County throughout the Florida Keys (Monroe County) from Totten Key south to Key West (Bradley and Gann 1999, p. 2). At the time of listing and currently, the Blodgett's silverbush consists of 20 extant populations in Miami-Dade County and Monroe County in the Florida Keys. Blodgett's silverbush is currently known from central Miami-Dade County from Coral Gables and southern Miami-Dade County to Long Pine Key in ENP, and from nine islands in the Florida Keys, from Windley Key (Bradley and Gann 1999, p. 3) southwest to Boca Chica Key (Hodges and Bradley 2006, pp. 10, 43). At least eight of the 20 extant populations of Blodgett's silverbush consist of fewer than 100 individuals. These small populations are at risk of adverse effects from reduced genetic variation, an increased risk of inbreeding depression, and reduced reproductive output. Many of these populations are small and isolated from each other, decreasing the likelihood that they could be naturally reestablished if extinction from one location occurred.</P>
                    <P>Resiliency will continue to be limited by the reduced amount of pine rockland, rockland hammock, and coastal habitat remaining in Miami-Dade and Monroe Counties. All Miami-Dade County populations are on small remnant pine rockland, rockland hammock, and coastal berm sites and adjacent disturbed areas, while all Monroe County populations occur on small islands. In both cases, the amount of suitable remaining habitat is limited (low resiliency) and much of the remaining habitat may be lost to sea level rise over the next century. Therefore, we are proposing to designate critical habitat units within the historical range of Blodgett's silverbush and that contain the physical or biological features essential to the conservation of the species, where the species was extant at the time of listing.</P>
                    <P>The amount and distribution of critical habitat being proposed for designation would allow existing (native) populations of Blodgett's silverbush to:</P>
                    <P>(1) Maintain their existing distribution;</P>
                    <P>(2) Expand their distribution into suitable nearby areas (needed to offset habitat loss and fragmentation);</P>
                    <P>(3) Use habitat depending on habitat availability (response to changing nature of coastal habitat including sea level rise) and support genetic diversity;</P>
                    <P>(4) Increase the size of each population to a level where the threats of genetic, demographic, and normal environmental uncertainties are diminished; and</P>
                    <P>(5) Maintain their ability to withstand local or unit-level environmental fluctuations or catastrophes.</P>
                    <HD SOURCE="HD2">Sources of Data to Identify Critical Habitat Boundaries</HD>
                    <P>We have determined that all areas known to be occupied at the time of listing should be proposed for critical habitat designation because all occupied sites are necessary to conserve the species. To determine the location and boundaries of occupied critical habitat, the Service used sources of data and information for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush that include the following:</P>
                    <P>(1) Species occurrence spatial data and ArcGIS geographic information system software to spatially depict the location and extent of documented populations of the species;</P>
                    <P>(2) Reports prepared by FNAI, Fairchild Tropical Botanical Garden, Institute for Regional Conservation, National Park Service, and Florida Department of Environmental Protection;</P>
                    <P>(3) Historical records found in reports and associated voucher specimens housed at herbaria, all of which are referenced in the above-mentioned reports;</P>
                    <P>(4) Digitally produced habitat maps provided by Miami-Dade and Monroe Counties; and</P>
                    <P>(5) Aerial images of Miami-Dade and Monroe Counties. The presence of pine rocklands was determined through the use of GIS spatial data depicting the current habitat status. These habitat data for the Florida Keys were developed by Monroe County from 2006 aerial images, and ground conditions for many areas were checked in 2009. Habitat data from Monroe County identifies pine rockland habitat. Habitat data for Miami-Dade County were developed by Miami-Dade Department of Environmental Protection for the Natural Forest Community program and include pine rocklands and rockland hammocks. Pine rockland, rockland hammock, and coastal berm habitat follow predictable landscape patterns and have a recognizable signature in the aerial imagery. Aerial imagery was utilized to identify disturbed areas adjacent to pine rocklands, rockland hammock, and coastal berm.</P>
                    <P>We delineated critical habitat unit boundaries for these species using the following criteria:</P>
                    <P>
                        (1) The delineation included space to allow for the successional nature of the habitats (
                        <E T="03">i.e.,</E>
                         gain and loss of areas with sufficient light availability due to disturbance of the vegetation, driven by natural events such as inundation and hurricanes, or through natural or prescribed fire) and habitat transition or loss due to sea level rise.
                    </P>
                    <P>
                        (2) All areas (
                        <E T="03">i.e.,</E>
                         physical or biological features) will require special management to be able to support a higher density of plants within the occupied space. These areas generally are habitats where some of the habitat features have been degraded or lost through natural or human causes. These areas would help to offset the anticipated loss and degradation of habitat occurring or expected from the effects of climate change (such as sea level rise) or development.
                    </P>
                    <P>(3) The areal extent of a plant population is dynamic over time within suitable habitat, while a survey represents a snapshot in time. Unsurveyed areas near mapped populations likely support plants currently or did in the past.</P>
                    <HD SOURCE="HD2">Areas Occupied at the Time of Listing</HD>
                    <P>
                        The proposed occupied critical habitat designation for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush focuses on areas within the historical range that have retained the necessary habitat characteristics that will allow for the maintenance and expansion of existing 
                        <PRTPAGE P="62516"/>
                        populations, and the establishment or reestablishment of populations through reintroduction (
                        <E T="03">i.e.,</E>
                         Cudjoe Key for Big Pine partridge pea). The proposed occupied critical habitat units were delineated based on documented extant populations at the time of listing. These units include the mapped extent of the population and nearby areas that contain one or more of the physical or biological features essential to the conservation of the species.
                    </P>
                    <P>In summary, for areas within the geographic area occupied by Big Pine partridge pea, wedge spurge, and sand flax at the time of listing, we delineated critical habitat unit boundaries using the following criteria:</P>
                    <P>(1) Pine rockland habitat that was occupied by the species at the time of listing;</P>
                    <P>(2) Presence of suitable pine rockland habitat and sufficient essential features; and</P>
                    <P>(3) Whether the pine rockland habitat is natural versus human-made habitat that was not historically pine rockland.</P>
                    <P>For Big Pine partridge pea, two occupied units (Big Pine Key and Cudjoe Key) are proposed as critical habitat. We consider pine rockland to be the primary habitat for Big Pine partridge pea. Adjacent disturbed areas currently supporting the species are also considered essential when adjacent pine rocklands do not support an existing population or are of insufficient size or connectivity to support a population of the species. While pine rockland habitat occurs on numerous other Keys, including nearby Sugarloaf Keys and Little Pine Key, none support existing populations of Big Pine partridge pea now nor did they at the time of listing. As mentioned previously, after the time of listing, a population of Big Pine partridge pea was introduced on No Name Key, which has high-quality pine rockland habitat and currently supports the reintroduced population. Plants and seeds were introduced in 2019 by Fairchild Tropical Botanical Garden, in cooperation with NKDR and the Florida Department of Agriculture and Consumer Services. This action aligns with the recovery strategy that the Service will seek to implement for this species. We are considering whether areas on these Keys may be essential for the conservation of the Big Pine partridge pea. If we determine they are, they will be included in our final designation.</P>
                    <P>For wedge spurge, one unit (one population: Big Pine Key) is proposed as critical habitat. We consider pine rockland to be the primary habitat for wedge spurge. Adjacent disturbed areas currently supporting the species are also considered essential when adjacent pine rocklands do not support an existing population or are of insufficient size or connectivity to support a population of the species. Even though pine rockland habitat is present on numerous other Keys, including nearby Little Pine Key, Cudjoe Key, and Sugarloaf Keys, none support existing populations of the species now, nor did they at the time of listing or historically. As mentioned previously, after the time of listing, a population of wedge spurge was introduced on No Name Key. We are considering whether areas on these Keys may be essential for the conservation of the wedge spur. If we determine they are, they will be included in our final designation.</P>
                    <P>For sand flax, five units containing seven populations are proposed for critical habitat. We consider pine rockland to be the primary habitat for sand flax. While pine rockland habitat occurs on numerous other keys in Monroe County and other areas in Miami-Dade County, these do not support existing populations of sand flax now, nor did they historically or at the time of listing, and are therefore not proposed as critical habitat. Adjacent disturbed areas currently supporting the species are also considered essential when adjacent pine rocklands do not support an existing population or are of insufficient size or connectivity to support a population of sand flax. Such is the case for the area we are proposing as critical habitat on Sugarloaf Key (see below).</P>
                    <P>
                        Two well-maintained levees in Miami-Dade County support large populations of sand flax, which were established when fill used to construct the levees included pine rockland substrate and the seeds of pine rockland species, such as sand flax. While these levees support robust populations of sand flax, they are not included in proposed critical habitat because the habitat is human-made, and these populations are not natural populations or purposefully established. In addition, we do not expect these areas to support the needs of the species long-term, as the maintenance of these areas may not be compatible with the species over time. In addition, there are roadside areas on Middle Torch Key, Big Torch Key, and Lower Sugarloaf Keys that support sand flax, but are not associated with an adjacent pine rockland. These populations may also have been established at these sites through the deposition of fill. Because these areas are mowed occasionally, they provide the open conditions required by sand flax (Bradley 2006, p. 37). However, these areas are not included in proposed critical habitat, because the habitat is human-made, do not contain the physical or biological features (
                        <E T="03">i.e.,</E>
                         these disturbed areas are not adjacent to native pine rockland and are not characterized by an open canopy and understory with a high proportion of native plant species occurring in pine rockland habitat), and they are not adjacent to pine rockland that would facilitate expansion of the population into natural habitat.
                    </P>
                    <P>As mentioned previously, there is remaining pine rockland habitat on numerous other Keys, including Little Pine Key and Cudjoe Key, and areas in Miami-Dade County, including Trinity Pinelands, Nixon Smiley, Quail's Roost, Navy Wells, and USDA Horticulture Research Station, but these areas do not currently or at the time of listing support existing populations of sand flax. No Name Key currently supports a reintroduced populations of sand flax in NKDR. We are considering whether these areas may be essential for the conservation of the sand flax. If so, we will include them in our final designation.</P>
                    <P>For Blodgett's silverbush, for areas within the geographic area occupied at the time of listing, we delineated critical habitat unit boundaries using the following criteria:</P>
                    <P>(1) Pine rockland, rockland hammock, and coastal berm habitats that were occupied by Blodgett's silverbush at the time of listing;</P>
                    <P>(2) Presence of suitable pine rockland, rockland hammock, and coastal berm habitats and sufficient essential features; and</P>
                    <P>(3) Whether the pine rockland, rockland hammock, and coastal berm habitats are natural versus human-made habitat that was not historically pine rockland, rockland hammock, or coastal berm.</P>
                    <P>
                        For Blodgett's silverbush, 13 occupied units contain 18 populations are proposed as critical habitat for the species. We consider pine rockland to be one of the primary habitats for Blodgett's silverbush. In addition, we consider rockland hammock and coastal berm to be primary habitats for the species. Adjacent disturbed areas currently supporting the species are also considered essential when adjacent pine rocklands, rockland hammocks, or coastal berms do not support an existing population or are of insufficient size or connectivity to support a population of sand flax. While pine rockland habitat, rockland hammock, and coastal berm occurs on numerous other Keys and areas in Miami-Dade County, these do not support existing populations of Blodgett's silverbush now, nor did they 
                        <PRTPAGE P="62517"/>
                        historically or at the time of listing, and therefore, are not proposed as critical habitat. We have not identified any specific areas outside the geographical area occupied by the species at the time it was listed that are essential for the conservation of the species. Accordingly, we are not proposing any unoccupied areas as critical habitat.
                    </P>
                    <P>In summary, for areas within the geographical area occupied by Big Pine partridge pea, wedge spurge, and sand flax at the time of listing, we delineated critical habitat unit boundaries by evaluating habitat suitability of pine rockland habitat within the historical range of the plant and retained those areas that contain some or all of the physical or biological features essential to the conservation of the species and that may require special management. For areas within the geographical area occupied by Blodgett's silverbush at the time of listing, we delineated critical habitat unit boundaries by evaluating habitat suitability of pine rockland, rockland hammocks, and coastal berm habitats within the historical range of the plant and retained those areas that contain some or all of the physical or biological essential to the conservation of the species and that may require special management.</P>
                    <P>When determining proposed critical habitat boundaries, we made every effort to avoid including developed areas such as lands covered by buildings, pavement, and other structures because such lands lack physical or biological features essential to the conservation of these species, nor are they essential to the conservation of the species themselves. The scale of the maps we prepared under the parameters for publication within the Code of Federal Regulations may not reflect the exclusion of such developed lands. Any such lands inadvertently left inside critical habitat boundaries shown on the maps of this proposed rule have been excluded by text in the proposed rule and are not proposed for designation as critical habitat. Therefore, if the critical habitat is finalized as proposed, a Federal action involving these lands would not trigger section 7 consultation with respect to critical habitat and the requirement of no adverse modification unless the specific action would affect the physical or biological features in the adjacent critical habitat.</P>
                    <P>We are proposing for designation as critical habitat those lands that we have determined were occupied at the time of listing and which contain one or more of the physical or biological features that are essential to support life-history processes of the species. For Big Pine partridge pea, two units are proposed for designation based on one or more of the physical or biological features being present to support the specie's life-history processes. Both units contain all of the identified physical or biological features and support multiple life-history processes. For wedge spurge, one unit is proposed for designation based on one or more of the physical or biological features being present to support wedge spurge's life-history processes. The unit contains all of the identified physical or biological features and supports multiple life-history processes. For sand flax, five units are proposed for designation based on one or more of the physical or biological features being present to support sand flax's life-history processes. Some units contain all of the identified physical or biological features and support multiple life-history processes. Some units contain only some of the physical or biological features necessary to support sand flax particular use of that habitat. For Blodgett's silverbush, 13 units are proposed for designation based on one or more of the physical or biological features being present to support Blodgett's silverbush's life-history processes. Some units contain all of the identified physical or biological features and support multiple life-history processes. Some units contain only some of the physical or biological features necessary to support Blodgett's silverbush's particular use of that habitat.</P>
                    <P>
                        The proposed critical habitat designation is defined by the map or maps, as modified by any accompanying regulatory text, presented at the end of this document under Proposed Regulation Promulgation. We include more detailed information on the boundaries of the proposed critical habitat designation in the preamble of this document. We will make the coordinates or plot points or both on which each map is based available to the public on 
                        <E T="03">https://www.regulations.gov</E>
                         at Docket No. FWS-R4-ES-2022-0116, on our internet site at 
                        <E T="03">https://www.fws.gov/office/florida-ecological-services/library</E>
                         and at the field office responsible for the designation (see 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         above).
                    </P>
                    <HD SOURCE="HD1">Proposed Critical Habitat Designation for Big Pine Partridge Pea</HD>
                    <P>We are proposing to designate approximately 1,462 ac (592 ha) in two units as critical habitat for Big Pine partridge pea. The critical habitat areas we describe below constitute our current best assessment of areas that meet the definition of critical habitat for Big Pine partridge pea. The two areas we propose as critical habitat are:</P>
                    <P>(1) BPP1—Big Pine Key, Monroe County, Florida, and</P>
                    <P>(2) BPP2—Cudjoe Key in Monroe County, Florida.</P>
                    <P>Land ownership within the proposed critical habitat consists of Federal (67 percent), State (16 percent), County (10 percent), and private and other (7 percent). Other lands include areas for which ownership information is unclear or unavailable. Table 1 shows each critical habitat unit by area, land ownership, and occupancy.</P>
                    <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s75,15,15,15,15,15">
                        <TTITLE>Table 1—Proposed Critical Habitat Units for Big Pine Partridge Pea</TTITLE>
                        <TDESC>[Includes total area, area by land ownership, and occupancy. All areas rounded to the nearest whole acre (ac) and hectare (ha)]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Total ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                Federal ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                State ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                County ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                Private/other ac
                                <LI>(ha)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">BPP1—Big Pine Key</ENT>
                            <ENT>1,379 (558)</ENT>
                            <ENT>912 (369)</ENT>
                            <ENT>228 (92)</ENT>
                            <ENT>144 (58)</ENT>
                            <ENT>96 (39)</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">BPP2—Cudjoe Key</ENT>
                            <ENT>83 (33)</ENT>
                            <ENT>66 (27)</ENT>
                            <ENT>3 (1)</ENT>
                            <ENT>1 (0.5)</ENT>
                            <ENT>12 (5)</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="03">Total</ENT>
                            <ENT>1,462 (592)</ENT>
                            <ENT>978 (396)</ENT>
                            <ENT>231 (93)</ENT>
                            <ENT>145 (59)</ENT>
                            <ENT>108 (44)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Percent of Total</ENT>
                            <ENT/>
                            <ENT>67%</ENT>
                            <ENT>16%</ENT>
                            <ENT>10%</ENT>
                            <ENT>7%</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding or minor mapping discrepancies. Both units are occupied by the species.
                        </TNOTE>
                    </GPOTABLE>
                    <P>
                        Nearly all the lands (99.7 percent; all except approximately 4 ac (2 ha)) contained within units proposed as critical habitat for Big Pine partridge pea are designated critical habitat for other federally listed species.
                        <PRTPAGE P="62518"/>
                    </P>
                    <P>We present brief descriptions of each proposed critical habitat unit and the justification for why each meets the definition of critical habitat for Big Pine partridge pea, below.</P>
                    <HD SOURCE="HD3">Unit BPP1: Big Pine Key, Monroe County, Florida</HD>
                    <P>Unit BPP1 consists of 1,379 ac (558 ha) in Monroe County, Florida. This unit includes Federal lands within NKDR (912 ac (369 ha)), State lands (228 ac (92 ha)), County lands (144 ac (58 ha)), and property in private or other ownership (96 ac (39 ha)). State lands are interspersed within NKDR lands and managed as part of the Refuge.</P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by one Big Pine Partridge pea population. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Big Pine partridge pea.</P>
                    <P>The unit is part of lands contained within the Lower Florida Keys National Wildlife Refuges (NWRs), which includes NKDR, Key West NWR, and Great White Heron NWR. The Comprehensive Conservation Plan (CCP) for the Lower Florida Keys NWRs promotes the enhancement of wildlife populations by maintaining and enhancing a diversity and abundance of habitats for native plants and animals and provides specifically for maintaining and expanding populations of plant species including Big Pine partridge pea. The Service conducts nonnative species control and prescribed fire in areas that could support Big Pine partridge pea.</P>
                    <P>
                        Unit BPP1 is also designated critical habitat for the Florida leafwing (
                        <E T="03">Anaea troglodyta floridalis</E>
                        ) and Bartram's scrub-hairstreak (
                        <E T="03">Strymon acis bartrami</E>
                        ) butterflies.
                    </P>
                    <HD SOURCE="HD3">Unit BPP2: Cudjoe Key, Monroe County, Florida</HD>
                    <P>Unit BPP2 consists of 83 ac (33 ha) in Monroe County, Florida. This unit includes Federal lands within NKDR (66 ac (27 ha)), State lands (3 ac (1 ha)), County lands (1 ac (0.5 ha)), and property in private or other ownership (12 ac (5 ha)). State lands are interspersed within NKDR lands and managed as part of the Refuge.</P>
                    <P>This unit was occupied at the time the species was listed, but the population here may have since been extirpated (Possley 2020, pers. comm.). The unit does, however, still contain all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Big Pine partridge pea.</P>
                    <P>The unit is part of lands contained within the Lower Florida Keys NWRs, which includes NKDR, Key West NWR, and Great White Heron NWR. The CCP for the Lower Florida Keys NWRs promotes the enhancement of wildlife populations by maintaining and enhancing a diversity and abundance of habitats for native plants and animals and provides specifically for maintaining and expanding populations of plant species including Big Pine partridge pea. The Service conducts nonnative species control in areas that could support Big Pine partridge pea.</P>
                    <P>
                        The entirety of Unit BPP2 is also designated critical habitat for the silver rice rat (
                        <E T="03">Oryzomys palustris natator</E>
                        ).
                    </P>
                    <HD SOURCE="HD1">Proposed Critical Habitat Designation for Wedge Spurge</HD>
                    <P>We are proposing to designate approximately 1,379 ac (558 ha) in one unit as critical habitat for wedge spurge. The critical habitat area we describe below constitutes our current best assessment of lands that meet the definition of critical habitat for wedge spurge. The area we propose as critical habitat is: WS1—Big Pine Key, Monroe County, Florida.</P>
                    <P>Land ownership within the proposed critical habitat consists of Federal (66 percent), State (16 percent), County (10 percent), and private and other (7 percent). Other lands include areas for which ownership information is unclear or unavailable. Table 2 shows these units by land ownership, area, and occupancy.</P>
                    <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s75,15,15,15,15,15">
                        <TTITLE>Table 2—Proposed Critical Habitat Unit for Wedge Spurge</TTITLE>
                        <TDESC>[Includes area, area by land ownership, and occupancy. All areas rounded to the nearest whole acre (ac) and hectare (ha)]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Total ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                Federal ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                State ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                County ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                Private/other ac
                                <LI>(ha)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW RUL="n,s">
                            <ENT I="01">WS1—Big Pine Key</ENT>
                            <ENT>1,379 (558)</ENT>
                            <ENT>912 (369)</ENT>
                            <ENT>228 (92)</ENT>
                            <ENT>144 (58)</ENT>
                            <ENT>96 (39)</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="03">Total</ENT>
                            <ENT>1,379 (558)</ENT>
                            <ENT>912 (369)</ENT>
                            <ENT>228 (92)</ENT>
                            <ENT>144 (58)</ENT>
                            <ENT>96 (39)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Percent of Total</ENT>
                            <ENT/>
                            <ENT>66%</ENT>
                            <ENT>16%</ENT>
                            <ENT>10%</ENT>
                            <ENT>7%</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding or minor mapping discrepancies. The one unit is occupied by the species.
                        </TNOTE>
                    </GPOTABLE>
                    <P>Nearly all the lands (99.7 percent; all except approximately 4 ac (2 ha)) contained within units proposed as critical habitat for wedge spurge are designated critical habitat for other federally listed species. Additionally, the lands in Unit WS1—Big Pine Key are the same lands proposed for Big Pine partridge pea in BPP1, above.</P>
                    <P>We present brief descriptions of the proposed critical habitat unit and the justification for why it meets the definition of critical habitat for wedge spurge, below.</P>
                    <HD SOURCE="HD3">Unit WS1: Big Pine Key, Monroe County, Florida</HD>
                    <P>Unit WS1 consists of 1,379 ac (558 ha) in Monroe County. This unit includes Federal lands within NKDR (912 ac (369 ha)), State lands (228 ac (92 ha)), County land (144 ac (58 ha)), and property in private or other ownership (96 ac (39 ha)). State lands are interspersed within NKDR lands and managed as part of the Refuge.</P>
                    <P>
                        This unit was occupied at the time the species was listed and is currently occupied by one wedge spurge 
                        <PRTPAGE P="62519"/>
                        population. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.
                    </P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports wedge spurge.</P>
                    <P>The unit is part of lands contained within the Lower Florida Keys NWRs, which includes NKDR, Key West NWR, and Great White Heron NWR. The CCP for the Lower Florida Keys NWRs promotes the enhancement of wildlife populations by maintaining and enhancing a diversity and abundance of habitats for native plants and animals and provides specifically for maintaining and expanding populations of candidate plant species including wedge spurge. The Service conducts nonnative species control and prescribed fire in areas that support wedge spurge.</P>
                    <P>Nearly all (99.7 percent; all except 4 ac (2 ha)) of unit WS1 is also designated critical habitat for the Florida leafwing and Bartram's scrub-hairstreak butterflies.</P>
                    <HD SOURCE="HD1">Proposed Critical Habitat Designation for Sand Flax</HD>
                    <P>We are proposing to designate approximately 5,090 ac (2,060 ha) in five units as critical habitat for sand flax. The critical habitat areas we describe below constitute our current best assessment of areas that meet the definition of critical habitat for sand flax.</P>
                    <P>The five areas we propose as critical habitat are:</P>
                    <P>(1) SF1—Big Pine Key, Monroe County, Florida;</P>
                    <P>(2) SF2—Upper and Lower Sugarloaf Keys, Monroe County, Florida;</P>
                    <P>(3) SF3—Richmond Pinelands, Miami-Dade County, Florida;</P>
                    <P>(4) SF4—Camp Owaissa Bauer, Miami-Dade County, Florida; and</P>
                    <P>(5) SF5—Homestead, Miami-Dade County, Florida.</P>
                    <P>
                        We have determined that these five areas meet the definition of critical habitat. While Unit 5 meets the definition of critical habitat, a portion of the lands and features contained therein are on lands of SOCSO and covered by their INRMP, and as a result the SOCSO lands within this unit are being exempted from critical habitat (please refer to the Exemptions: 
                        <E T="03">Application of Section 4(a)(3) of the Act</E>
                         section of this proposed rule).
                    </P>
                    <P>Land ownership within the proposed critical habitat consists of Federal (49 percent), State (6 percent), County (35 percent), and private and other (10 percent). Table 3 shows these units by land ownership, area, and occupancy.</P>
                    <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s75,15,15,15,15,15">
                        <TTITLE>Table 3—Proposed Critical Habitat Units for Sand Flax</TTITLE>
                        <TDESC>[Includes area, area by land ownership, and occupancy. All areas rounded to the nearest whole acres (ac) and hectares (ha)]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Total ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                Federal ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                State ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                County ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                Private/other ac
                                <LI>(ha)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">SF1—Big Pine Key</ENT>
                            <ENT>1,379 (558)</ENT>
                            <ENT>912 (369)</ENT>
                            <ENT>228 (92)</ENT>
                            <ENT>144 (58)</ENT>
                            <ENT>96 (39)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">SF2—Upper and Lower Sugarloaf Keys</ENT>
                            <ENT>116 (47)</ENT>
                            <ENT>63 (25)</ENT>
                            <ENT>38 (15)</ENT>
                            <ENT>10 (4)</ENT>
                            <ENT>6 (2)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">SF3—Richmond Pinelands</ENT>
                            <ENT>987 (399)</ENT>
                            <ENT>191 (77)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>609 (247)</ENT>
                            <ENT>187 (76)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">SF4—Camp Owaissa Bauer</ENT>
                            <ENT>315 (128)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>49 (20)</ENT>
                            <ENT>154 (62)</ENT>
                            <ENT>113 (46)</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">SF5—Homestead</ENT>
                            <ENT>2,292 (928)</ENT>
                            <ENT>1,334 (540)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>867 (351)</ENT>
                            <ENT>91 (37)</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="03">Total</ENT>
                            <ENT>5,090 (2,060)</ENT>
                            <ENT>2,499 (1,011)</ENT>
                            <ENT>314 (127)</ENT>
                            <ENT>1,783 (722)</ENT>
                            <ENT>493 (199)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Percent of Total</ENT>
                            <ENT/>
                            <ENT>49%</ENT>
                            <ENT>6%</ENT>
                            <ENT>35%</ENT>
                            <ENT>10%</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding or minor mapping discrepancies. All 5 units are occupied by the species.
                        </TNOTE>
                    </GPOTABLE>
                    <P>
                        The Big Pine Key unit (SF1) proposed for sand flax in the Florida Keys comprises the same lands proposed for Big Pine partridge pea (BPP1) and wedge spurge (WS1) above. Of the five units, two are currently designated under the Act as critical habitat for the silver rice rat; five are designated as critical habitat for the Bartram's scrub-hairstreak butterfly; three are designated as critical habitat for the Florida leafwing butterfly; and two are designated as critical habitat for the Florida brickell-bush (
                        <E T="03">Brickellia mosieri</E>
                        ) and Carter's small-flowered flax (
                        <E T="03">Linum carteri</E>
                         ssp. 
                        <E T="03">smallii</E>
                        ).
                    </P>
                    <P>Approximately half of the lands contained within units proposed as critical habitat for sand flax (52 percent; 2,660 ac (1,076 ha)) are designated critical habitat for other federally listed species.</P>
                    <P>We present brief descriptions of each proposed critical habitat unit and the justification for why each meets the definition of critical habitat for sand flax, below.</P>
                    <HD SOURCE="HD3">Unit SF1: Big Pine Key, Monroe County, Florida</HD>
                    <P>Unit SF1 consists of 1,379 ac (558 ha) in Monroe County. This unit includes Federal lands within NKDR (912 ac (369 ha)), State lands (228 ac (92 ha)), County land (144 ac (58 ha), and property in private or other ownership (96 ac (39 ha)). State lands are interspersed within NKDR lands and managed as part of the Refuge.</P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by one sand flax population. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports sand flax.</P>
                    <P>
                        The unit is part of lands contained within the Lower Florida Keys NWRs, which includes NKDR, Key West NWR, and Great White Heron NWR. The CCP for the Lower Florida Keys NWRs promotes the enhancement of wildlife populations by maintaining and enhancing a diversity and abundance of habitats for native plants and animals and provides specifically for maintaining and expanding populations of candidate plant species including sand flax. The Service conducts nonnative species control and 
                        <PRTPAGE P="62520"/>
                        prescribed fire in areas that support sand flax.
                    </P>
                    <P>The entirety of unit SF1 is also designated critical habitat for the Florida leafwing and Bartram's scrub-hairstreak butterflies.</P>
                    <HD SOURCE="HD3">Unit SF2: Sugarloaf Keys, Monroe County, Florida</HD>
                    <P>Unit SF2 consists of 116 ac (47 ha) in Monroe County. This unit includes Federal lands within NKDR (63 ac (25 ha)), State lands (38 ac (15 ha)), County lands (10 ac (4 ha)), and property in private or other ownership (6 ac (2 ha)).</P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by one sand flax population. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address threats of lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports sand flax. The unit is part of lands contained within the Lower Florida Keys NWRs, which includes NKDR, Key West NWR, and Great White Heron NWR. The CCP for the Lower Florida Keys NWRs promotes the enhancement of wildlife populations by maintaining and enhancing a diversity and abundance of habitats for native plants and animals and provides specifically for maintaining and expanding populations of candidate plant species including sand flax. The Service conducts nonnative species control in areas that could support sand flax.</P>
                    <P>Unit SF2 is not designated critical habitat for any other species.</P>
                    <HD SOURCE="HD3">Unit SF3: Richmond Pinelands and Surrounding Areas, Miami-Dade County, Florida</HD>
                    <P>Unit SF3 consists of approximately 987 ac (399 ha) in Miami-Dade County. The unit comprises Federal lands owned by the U.S. Coast Guard (USCG), U.S. Army Corps of Engineers (USACE), Federal Bureau of Prisons (FBP), and National Oceanic and Atmospheric Administration (NOAA) (191 ac (77 ha)); County lands within and adjacent to Larry and Penny Thompson Park, Martinez Preserve, Zoo Miami, and Eachus Pineland (609 ac (247 ha)); and parcels in private or other ownership (187 ac (76 ha)), including the onsite preserve and offsite mitigation areas associated with the Coral Reef Commons HCP (110 ac (44.5) ha)).</P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by two sand flax populations. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports sand flax.</P>
                    <P>Sand flax is a covered species under the Coral Reef Commons HCP. Because sand flax is a covered species under this HCP and the preserves included within this proposed critical habitat unit are being managed for the conservation of the species and pine rockland habitat, the onsite preserve and the offsite mitigation area are being considered for exclusion from critical habitat under section 4(b)(2) of the Act (please refer to Consideration of Impacts Under Section 4(b)(2) of the Act section of this proposed rule).</P>
                    <P>The entirety of unit SF3 is also designated critical habitat for Carter's small-flowered flax and Florida brickell-bush; significant portions are designated for Bartram's scrub-hairstreak butterfly and Florida leafwing butterfly.</P>
                    <HD SOURCE="HD3">Unit SF4: Camp Owaissa Bauer and Surrounding Areas, Miami-Dade County, Florida</HD>
                    <P>Unit SF4 consists of approximately 315 ac (128 ha) of habitat in Miami-Dade County. The unit comprises State lands within Owaissa Bauer Pineland Addition, Ingram Pineland, West Biscayne Pineland, and Fuchs Hammock Addition (49 ac (20 ha)); County lands including Camp Owaissa Bauer, Pine Island Lake Park, Seminole Wayside Park, and Northrop Pineland (154 ac (62 ha)); and parcels in private and other ownership (113 ac (46 ha)), including the private conservation area, Pine Ridge Sanctuary.</P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by one sand flax population. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports sand flax.</P>
                    <P>The entirety of unit SF4 is also designated critical habitat for Carter's small-flowered flax and Florida brickell-bush; and large portions of unit SF4 are designated critical habitat for Bartram's scrub-hairstreak butterfly and Florida leafwing butterfly.</P>
                    <HD SOURCE="HD3">Unit SF5: Homestead and Surrounding Areas, Miami-Dade County, Florida</HD>
                    <P>Unit SF5 consists of approximately 2,292 ac (928 ha) in Miami-Dade County. The unit comprises Federal lands owned by DoD (1,334 ac (540 ha)), lands owned by Miami-Dade County (867 ac (351 ha)), and parcels in private or other ownership (91 ac (37 ha)).</P>
                    <P>
                        A portion (approximately 25 ac (10 ha)) of the lands and features contained within this unit are on lands of SOCSO and covered by their updated and signed INRMP, and as a result, the SOCSO lands within this unit are being exempted from critical habitat (please refer to the Exemptions: 
                        <E T="03">Application of Section 4(a)(3) of the Act</E>
                         section of this proposed rule). The HARB is working with the Service to incorporate additional conservation measures for sand flax in revisions to their INRMP, but the revised INRMP is currently being drafted and has not yet been approved and signed. Therefore, lands that are part of HARB that have been determined to be essential to the conservation of sand flax are not being exempted and are included in this proposal. If the revised INRMP is approved and signed before we finalize this designation, we would exempt this area in the final designation.
                    </P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by two sand flax populations. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports sand flax.</P>
                    <P>
                        Unit SF5 does not contain previously designated critical habitat, but the 
                        <PRTPAGE P="62521"/>
                        endangered Small's milkpea (
                        <E T="03">Galactia smallii</E>
                        ) occurs throughout the unit.
                    </P>
                    <HD SOURCE="HD1">Proposed Critical Habitat Designation for Blodgett's Silverbush</HD>
                    <P>We are proposing to designate approximately 16,667 ac (6,745 ha) in 13 units as critical habitat for Blodgett's silverbush. The critical habitat areas we describe below constitute our current best assessment of areas that meet the definition of critical habitat for Blodgett's silverbush. The 13 areas we propose as critical habitat are:</P>
                    <P>(1) BS1—Key Largo, Monroe County, Florida;</P>
                    <P>(2) BS2—Plantation Key, Monroe County, Florida;</P>
                    <P>(3) BS3—Windley Key, Monroe County, Florida;</P>
                    <P>(4) BS4—Lignumvitae Key, Monroe County, Florida;</P>
                    <P>(5) BS5—Lower Matecumbe Key, Monroe County, Florida;</P>
                    <P>(6) BS6—Marathon, Monroe County, Florida;</P>
                    <P>(7) BS7—Big Pine Key, Monroe County, Florida;</P>
                    <P>(8) BS8—Big Munson Island, Monroe County, Florida;</P>
                    <P>(9) BS9—U.S. Department of Agriculture (USDA) Subtropical Horticulture Research Station, Miami-Dade County, Florida;</P>
                    <P>(10) BS10—Richmond Pineland, Miami-Dade County, Florida;</P>
                    <P>(11) BS11—Quail Roost Pineland, Miami-Dade County, Florida;</P>
                    <P>(12) BS12—Camp Owaissa Bauer, Miami-Dade County, Florida; and</P>
                    <P>(13) BS13—Everglades National Park, Miami-Dade County, Florida.</P>
                    <P>
                        We have determined that these 13 areas meet the definition of critical habitat. While the habitat within Key West Naval Air Station (KWNAS) meets the definition of critical habitat, the lands and features contained therein are covered under the KWNAS INRMP that provides benefits to Blodgett's silverbush and its habitat and therefore will be exempted from critical habitat (see Exemptions: 
                        <E T="03">Application of Section 4(a) (3) of the Act,</E>
                         below).
                    </P>
                    <P>Land ownership within the proposed critical habitat consists of Federal (64 percent), State 17 (19 percent), County (7 percent), and private and other (9 percent). Table 4 shows these units by land ownership, area, and occupancy.</P>
                    <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s75,15,15,15,15,15">
                        <TTITLE>Table 4—Proposed Critical Habitat Units for Blodgett's Silverbush</TTITLE>
                        <TDESC>[Including area, area by land ownership, and occupancy. All areas rounded to the nearest whole acre (ac) and hectare (ha)]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Total ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                Federal ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                State ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                County ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                Private/other ac
                                <LI>(ha)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">BS1—Key Largo</ENT>
                            <ENT>3,060 (1,238)</ENT>
                            <ENT>595 (241)</ENT>
                            <ENT>2,024 (819)</ENT>
                            <ENT>214 (86)</ENT>
                            <ENT>227 (92)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BS2—Plantation Key</ENT>
                            <ENT>175 (71)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>26 (10)</ENT>
                            <ENT>33 (13)</ENT>
                            <ENT>116 (47)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BS3—Windley Key</ENT>
                            <ENT>30 (12)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>28 (11)</ENT>
                            <ENT>1 (1)</ENT>
                            <ENT>0 (0)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BS4—Lignumvitae Key</ENT>
                            <ENT>159 (64)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>157 (64)</ENT>
                            <ENT>2 (1)</ENT>
                            <ENT>0 (0)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BS5—Lower Matecumbe Key</ENT>
                            <ENT>64 (26)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>27 (11)</ENT>
                            <ENT>6 (3)</ENT>
                            <ENT>31 (13)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BS6—Marathon</ENT>
                            <ENT>103 (42)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>66 (27)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>38 (15)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BS7—Big Pine Key</ENT>
                            <ENT>1,867 (756)</ENT>
                            <ENT>1,259 (509)</ENT>
                            <ENT>328 (133)</ENT>
                            <ENT>160 (65)</ENT>
                            <ENT>122 (49)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BS8—Big Munson Island</ENT>
                            <ENT>28 (11)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>28 (11)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BS9—USDA Subtropical Horticulture Research Station</ENT>
                            <ENT>630 (255)</ENT>
                            <ENT>155 (63)</ENT>
                            <ENT>253 (103)</ENT>
                            <ENT>182 (74)</ENT>
                            <ENT>40 (16)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BS10—Richmond Pinelands</ENT>
                            <ENT>987 (399)</ENT>
                            <ENT>191 (77)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>609 (247)</ENT>
                            <ENT>187 (76)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BS11—Quail Roost Pineland</ENT>
                            <ENT>412 (167)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>174 (70)</ENT>
                            <ENT>100 (40)</ENT>
                            <ENT>139 (56)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BS12—Camp Owaissa Bauer</ENT>
                            <ENT>392 (159)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>69 (28)</ENT>
                            <ENT>184 (74)</ENT>
                            <ENT>139 (56)</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">BS13—Everglades National Park</ENT>
                            <ENT>8,728 (3,532)</ENT>
                            <ENT>8,595 (3,478)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>133 (54)</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="03">Total</ENT>
                            <ENT>16,635 (6,732)</ENT>
                            <ENT>10,794 (4,368)</ENT>
                            <ENT>3,151 (1,275)</ENT>
                            <ENT>1,490 (603)</ENT>
                            <ENT>1,199 (485)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Percent of Total</ENT>
                            <ENT/>
                            <ENT>64%</ENT>
                            <ENT>19%</ENT>
                            <ENT>7%</ENT>
                            <ENT>9%</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding or minor mapping discrepancies. All 13 units are occupied by the species.
                        </TNOTE>
                    </GPOTABLE>
                    <P>Many of the lands contained within units proposed as critical habitat for Blodgett's silverbush (15,247 ha (6,170 ha), or 91.5 percent) are designated critical habitat for other federally listed species.</P>
                    <P>We present brief descriptions of each proposed critical habitat unit and the justification for why each meets the definition of critical habitat for Blodgett's silverbush, below.</P>
                    <HD SOURCE="HD3">Unit BS1: Key Largo, Monroe County, Florida</HD>
                    <P>Unit BS1 consists of 3,060 ac (1,238 ha) in Monroe County. This unit includes Federal lands within Crocodile Lake NWR (595 ac (241 ha)), State lands within Dagny Johnson Botanical State Park, John Pennekamp Coral Reef State Park, and the Florida Keys Wildlife and Environmental Area (FKWEA) (2,024 ac (819 ha)), County lands (214 ac (86 ha)), and property in private or other ownership (227 ac (92 ha)).</P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by two Blodgett's silverbush populations. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Blodgett's silverbush.</P>
                    <P>Part of the unit is within the Crocodile Lake NWR. The CCP for Crocodile Lake NWR promotes the enhancement of wildlife populations by maintaining and enhancing a diversity and abundance of habitats for native plants and animals and provides specifically for maintaining and expanding populations of plant species including Blodgett's silverbush. The Service conducts nonnative species control in areas that could support the species.</P>
                    <P>
                        The entirety of unit BS1 is included in designated critical habitat for the American crocodile 
                        <E T="03">(Crocodylus acutus),</E>
                         Cape Sable thoroughwort (
                        <E T="03">Chromolaena frustrata</E>
                        ), and Florida semaphore cactus (
                        <E T="03">Consolea corallicola</E>
                        ).
                        <PRTPAGE P="62522"/>
                    </P>
                    <HD SOURCE="HD3">Unit BS2: Plantation Key, Monroe County, Florida</HD>
                    <P>Unit BS2 consists of 175 ac (71 ha) in Monroe County. This unit includes State lands within the FKWEA (26 ac (10 ha)), County lands (33 ac (13 ha)), and property in private or other ownership (116 ac (47 ha)).</P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by one Blodgett's silverbush population. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Blodgett's silverbush.</P>
                    <P>The entirety of Unit BS2 is designated critical habitat for the American crocodile.</P>
                    <HD SOURCE="HD3">Unit BS3: Windley Key, Monroe County, Florida</HD>
                    <P>Unit BS3 consists of 30 ac (12 ha) in Monroe County. This unit includes State lands within Windley Key Fossil Reef Geologic State Park (28 ac (11 ha)) and County property (1 ac (0.5 ha)). The unit is located on Windley Key on the north side of the Overseas Highway.</P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by one Blodgett's silverbush population. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Blodgett's silverbush.</P>
                    <P>The entirety of Unit BS3 includes designated critical habitat for the American crocodile.</P>
                    <HD SOURCE="HD3">Unit BS4: Lignumvitae Key, Monroe County, Florida</HD>
                    <P>Unit BS4 consists of 159 ac (64 ha) in Monroe County. This unit comprises State lands in Lignumvitae Key Botanical State Park (157 ac (64 ha)) and County property (1 ac (0.5 ha)). This unit includes the entire upland area of Lignumvitae Key.</P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by one Blodgett's silverbush population. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Blodgett's silverbush.</P>
                    <P>The management activities implemented by Florida State Parks promote the enhancement of wildlife populations by maintaining and enhancing a diversity and abundance of habitats for native plants and animals. Florida State Parks conducts nonnative species control in areas that could support Blodgett's silverbush.</P>
                    <P>The entirety of unit BS4 is included in designated critical habitat for the American crocodile and Cape Sable thoroughwort.</P>
                    <HD SOURCE="HD3">Unit BS5: Lower Matecumbe Key, Monroe County, Florida</HD>
                    <P>Unit BS5 consists of 64 ac (26 ha) in Monroe County. This unit includes State lands that are part of Lignumvitae Key Botanical State Park (27 ac (11 ha)), County property (6 ac (3 ha)), and property in private or other ownership (31 ac (13 ha)).</P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by one Blodgett's silverbush population. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Blodgett's silverbush.</P>
                    <P>The management activities implemented by Florida State Parks in part of this unit promote the enhancement of wildlife populations by maintaining and enhancing a diversity and abundance of habitats for native plants and animals. Florida State Parks conducts nonnative species control in areas that support Blodgett's silverbush.</P>
                    <P>The entirety of unit BS5 is included in designated critical habitat for the American crocodile and Cape Sable thoroughwort.</P>
                    <HD SOURCE="HD3">Unit BS6: Marathon, Monroe County, Florida</HD>
                    <P>Unit BS6 consists of 103 ac (42 ha) in Monroe County. This unit includes State lands within FKWEA (66 ac (27 ha)) and property in private or other ownership, including land owned by The Florida Keys Land and Sea Trust (38 ac (15 ha)).</P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by one Blodgett's silverbush population. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Blodgett's silverbush.</P>
                    <P>Unit BS6 does not include any designated critical habitat for other species.</P>
                    <HD SOURCE="HD3">Unit BS7: Big Pine Key, Monroe County, Florida</HD>
                    <P>Unit BS7 consists of 1,867 ac (756 ha) in Monroe County. This unit includes Federal lands within NKDR (1,259 ac (509 ha)), State lands (328 ac (133 ha)), County lands (160 ac (65 ha)), and property in private or other ownership (122 ac (49 ha)).</P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by two Blodgett's silverbush populations. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>
                        Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that 
                        <PRTPAGE P="62523"/>
                        help improve habitat that supports Blodgett's silverbush.
                    </P>
                    <P>The unit is part of lands contained within the Lower Florida Keys NWRs, which includes NKDR, Key West NWR, and Great White Heron NWR. The CCP for the Lower Florida Keys NWRs promotes the enhancement of wildlife populations by maintaining and enhancing a diversity and abundance of habitats for native plants and animals and provides specifically for maintaining and expanding populations of plant species including Blodgett's silverbush. The Service conducts nonnative species and prescribed fire control in areas that support Blodgett's silverbush.</P>
                    <P>The entirety of unit BS7 is designated critical habitat for the Florida leafwing and Bartram's scrub-hairstreak butterflies; Cape Sable thoroughwort; and Florida semaphore cactus. The endangered Key Deer occurs through the unit, but no critical habitat is designated for that species.</P>
                    <HD SOURCE="HD3">Unit BS8: Big Munson Island, Monroe County, Florida</HD>
                    <P>Unit BS8 consists of 28 ac (11 ha) in Monroe County. This unit is composed entirely of lands owned by the Boy Scouts of America. The unit includes all of the coastal berm and rockland hammock habitat on the island.</P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by one Blodgett's silverbush population. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Blodgett's silverbush.</P>
                    <P>The entirety of unit BS8 is designated critical habitat for the Cape Sable thoroughwort. The endangered Key deer occurs through the unit, but no critical habitat is designated for that species.</P>
                    <HD SOURCE="HD3">Unit BS9: USDA Subtropical Horticulture Research Station and Surrounding Areas, Miami-Dade County, Florida</HD>
                    <P>Unit BS9 consists of approximately 630 ac (255 ha) of habitat in Miami-Dade County. The unit comprises Federal lands within the USDA Subtropical Horticulture Research Station (155 ac (63 ha)); State lands within the R. Hardy Matheson Preserve, Ludlam Pineland, Deering Estate at Cutler, and Deering Estate South Addition (253 ac (103 ha)); County lands within Bill Sadowski Park and Matheson Hammock (182 ac (74 ha)), and parcels in private ownership (40 ac (16 ha)).</P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by two Blodgett's silverbush populations. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Blodgett's silverbush.</P>
                    <P>The entirety of unit BS9 includes designated critical habitat for the Carter's small-flowered flax and Florida brickell-bush.</P>
                    <HD SOURCE="HD3">Unit BS10: Richmond Pinelands and Surrounding Areas, Miami-Dade County, Florida</HD>
                    <P>Unit BS10 consists of approximately 987 ac (399 ha) in Miami-Dade County. The unit comprises Federal lands owned by the USCG, USACE, FBP, and NOAA (191 ac (77 ha)); County lands within and adjacent to Larry and Penny Thompson Park, Martinez Preserve, Zoo Miami, and Eachus Pineland (609 ac (247 ha)); and parcels in private or other ownership (187 ac (76 ha)), including the onsite preserve and offsite mitigation areas associated with the Coral Reef Commons HCP (110 ac (44.5) ha).</P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by one Blodgett's silverbush population. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Blodgett's silverbush.</P>
                    <P>Blodgett's silverbush is a covered species under the Coral Reef Commons HCP. Because Blodgett's silverbush is a covered species under this HCP and the preserves included within this proposed critical habitat unit are being managed for the conservation of the species and pine rockland habitat, the onsite preserve and the offsite mitigation area are being considered for exclusion from critical habitat under section 4(b)(2) of the Act (please refer to Consideration of Impacts Under Section 4(b)(2) of the Act section of this proposed rule).</P>
                    <P>The entirety of unit BS10 is designated critical habitat for Carter's small-flowered flax, Florida brickell-bush, Bartram's scrub hairstreak butterfly, and Florida leafwing butterfly.</P>
                    <HD SOURCE="HD3">Unit BS11: Quail Roost Pineland and Surrounding Areas, Miami-Dade County, Florida</HD>
                    <P>Unit BS11 consists of approximately 412 ac (167 ha) in Miami-Dade County. The unit comprises State lands within Quail Roost Pineland, Goulds Pineland and Addition, Silver Palm Groves Pineland, Castellow Hammock, Ross Hammock, Hardin Hammock, and Silver Palm Hammock (174 ac (70 ha)); County/local lands including Medsouth Park, Black Creek Forest, and Rock Pit #46 (100 ac (40 ha)); and parcels in private ownership (139 ac (56 ha)), including Porter-Russell Pineland owned by the Tropical Audubon Society.</P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by one possibly extirpated Blodgett's silverbush population and one population with uncertain status. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Blodgett's silverbush.</P>
                    <P>The entirety of unit BS11 is designated critical habitat for the Carter's small-flowered flax, Florida brickell-bush, and Bartram's scrub hairstreak butterfly.</P>
                    <HD SOURCE="HD3">Unit BS12: Camp Owaissa Bauer and Surrounding Areas, Miami-Dade County, Florida</HD>
                    <P>
                        Unit BS12 consists of approximately 392 ac (159 ha) of habitat in Miami-
                        <PRTPAGE P="62524"/>
                        Dade County. The unit comprises State lands within Owaissa Bauer Pineland Addition, West Biscayne Pineland, Ingram Pineland, Fuchs Hammock Addition, and Meissner Hammock (69 ac (28 ha)); County lands, including Camp Owaissa Bauer, Pine Island Lake Park, Seminole Wayside Park, Northrop Pineland, Hattie Bauer Hammock, and Fuchs Hammock (184 ac (74 ha)); and parcels in private ownership (139 ac (56 ha)), including the private conservation area, Pine Ridge Sanctuary.
                    </P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by three Blodgett's silverbush populations. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Blodgett's silverbush.</P>
                    <P>The entirety of Unit BS12 is designated critical habitat for Carter's small-flowered flax, Florida brickell-bush, and Bartram's scrub hairstreak butterfly.</P>
                    <HD SOURCE="HD3">Unit BS13: Everglades National Park—Pine Island and Surrounding Areas, Miami-Dade County, Florida</HD>
                    <P>Unit BS13 consists of approximately 8,728 ac (3,532 ha) in Miami-Dade County. The unit comprises Federal lands in ENP (8,595 ac (3,478 ha)) and parcels in private or other ownership (133 ac (54 ha)). The unit includes pine rocklands and numerous rockland hammocks in the vicinity of Long Pine Key in ENP.</P>
                    <P>This unit was occupied at the time the species was listed and is currently occupied by one Blodgett's silverbush population. This unit contains all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>Special management considerations or protection may be required within this unit to address lack of fire; nonnative plant and animal species; and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Blodgett's silverbush.</P>
                    <P>The entirety of unit BS13 is designated critical habitat for Bartram's scrub hairstreak butterfly and Florida leafwing butterfly.</P>
                    <HD SOURCE="HD1">Effects of Critical Habitat Designation</HD>
                    <HD SOURCE="HD2">Section 7 Consultation</HD>
                    <P>Section 7(a)(2) of the Act requires Federal agencies, including the Service, to ensure that any action they fund, authorize, or carry out is not likely to jeopardize the continued existence of any endangered species or threatened species or result in the destruction or adverse modification of designated critical habitat of such species. In addition, section 7(a)(4) of the Act requires Federal agencies to confer with the Service on any agency action which is likely to jeopardize the continued existence of any species proposed to be listed under the Act or result in the destruction or adverse modification of proposed critical habitat.</P>
                    <P>We published a final rule revising the definition of destruction or adverse modification on February 11, 2016 (81 FR 7214) (although we also published a revised definition after that (on August 27, 2019. Destruction or adverse modification means a direct or indirect alteration that appreciably diminishes the value of critical habitat for the conservation of a listed species. Such alterations may include, but are not limited to, those that alter the physical or biological features essential to the conservation of a species or that preclude or significantly delay development of such features.</P>
                    <P>
                        If a Federal action may affect a listed species or its critical habitat, the responsible Federal agency (action agency) must enter into consultation with us. Examples of actions that are subject to the section 7 consultation process are actions on State, Tribal, local, or private lands that require a Federal permit (such as a permit from the U.S. Army Corps of Engineers under section 404 of the Clean Water Act (33 U.S.C. 1251 
                        <E T="03">et seq.</E>
                        ) or a permit from the Service under section 10 of the Act) or that involve some other Federal action (such as funding from the Federal Highway Administration, Federal Aviation Administration, or the Federal Emergency Management Agency). Federal actions not affecting listed species or critical habitat—and actions on State, Tribal, local, or private lands that are not federally funded, authorized, or carried out by a Federal agency—do not require section 7 consultation.
                    </P>
                    <P>Compliance with the requirements of section 7(a)(2) is documented through our issuance of:</P>
                    <P>(1) A concurrence letter for Federal actions that may affect, but are not likely to adversely affect, listed species or critical habitat; or</P>
                    <P>(2) A biological opinion for Federal actions that may affect, and are likely to adversely affect, listed species or critical habitat.</P>
                    <P>When we issue a biological opinion concluding that a project is likely to jeopardize the continued existence of a listed species and/or destroy or adversely modify critical habitat, we provide reasonable and prudent alternatives to the project, if any are identifiable, that would avoid the likelihood of jeopardy and/or destruction or adverse modification of critical habitat. We define “reasonable and prudent alternatives” (at 50 CFR 402.02) as alternative actions identified during consultation that:</P>
                    <P>(1) Can be implemented in a manner consistent with the intended purpose of the action,</P>
                    <P>(2) Can be implemented consistent with the scope of the Federal agency's legal authority and jurisdiction,</P>
                    <P>(3) Are economically and technologically feasible, and</P>
                    <P>(4) Would, in the Service Director's opinion, avoid the likelihood of jeopardizing the continued existence of the listed species and/or avoid the likelihood of destroying or adversely modifying critical habitat.</P>
                    <P>Reasonable and prudent alternatives can vary from slight project modifications to extensive redesign or relocation of the project. Costs associated with implementing a reasonable and prudent alternative are similarly variable.</P>
                    <P>
                        Regulations at 50 CFR 402.16 set forth requirements for Federal agencies to reinitiate formal consultation on previously reviewed actions. These requirements apply when the Federal agency has retained discretionary involvement or control over the action (or the agency's discretionary involvement or control is authorized by law) and, if subsequent to the previous consultation: (a) if the amount or extent of taking specified in the incidental take statement is exceeded; (b) if new information reveals effects of the action that may affect listed species or critical habitat in a manner or to an extent not previously considered; (c) if the identified action is subsequently modified in a manner that causes an effect to the listed species or critical habitat that was not considered in the biological opinion; or (d) if a new species is listed or critical habitat designated that may be affected by the identified action. In such situations, Federal agencies sometimes may need to 
                        <PRTPAGE P="62525"/>
                        request reinitiation of consultation with us, but the regulations also specify some exceptions to the requirement to reinitiate consultation on specific land management plans after subsequently listing a new species or designating new critical habitat. See the regulations for a description of those exceptions.
                    </P>
                    <HD SOURCE="HD2">Application of the “Destruction or Adverse Modification” Standard</HD>
                    <P>The key factor related to the destruction or adverse modification determination is whether implementation of the proposed Federal action directly or indirectly alters the designated critical habitat in a way that appreciably diminishes the value of the critical habitat for the conservation of the listed species. As discussed above, the role of critical habitat is to support physical or biological features essential to the conservation of a listed species and provide for the conservation of the species.</P>
                    <P>Section 4(b)(8) of the Act requires us to briefly evaluate and describe, in any proposed or final regulation that designates critical habitat, activities involving a Federal action that may violate section 7(a)(2) of the Act by destroying or adversely modifying such habitat, or that may be affected by such designation.</P>
                    <P>Activities that we may, during a consultation under section 7(a)(2) of the Act, find are likely to destroy or adversely modify critical habitat for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush include, but are not limited to:</P>
                    <P>(1) Actions that would significantly alter the hydrology or substrate, such as ditching or filling. Such activities may include, but are not limited to, road construction or maintenance, and residential, commercial, or recreational development.</P>
                    <P>(2) Actions that would significantly alter vegetation structure or composition, such as clearing vegetation for construction of roads, residential and commercial development, recreational facilities, and trails.</P>
                    <P>(3) Actions that would introduce nonnative species that would significantly alter vegetation structure or composition. Such activities may include, but are not limited to, residential and commercial development and road construction.</P>
                    <HD SOURCE="HD1">Exemptions</HD>
                    <HD SOURCE="HD2">Application of Section 4(a)(3) of the Act</HD>
                    <P>Section 4(a)(3)(B)(i) of the Act (16 U.S.C. 1533(a)(3)(B)(i)) provides that the Secretary shall not designate as critical habitat any lands or other geographical areas owned or controlled by the DoD, or designated for its use, that are subject to an integrated natural resources management plan (INRMP) prepared under section 101 of the Sikes Act Improvement Act of 1997 (16 U.S.C. 670a) (Sikes Act), if the Secretary determines in writing that such plan provides a benefit to the species for which critical habitat is proposed for designation.</P>
                    <P>The Sikes Act required each military installation that includes land and water suitable for the conservation and management of natural resources to complete an INRMP by November 17, 2001. An INRMP integrates implementation of the military mission of the installation with stewardship of the natural resources found on the base. Each INRMP includes:</P>
                    <P>(1) An assessment of the ecological needs on the installation, including the need to provide for the conservation of listed species;</P>
                    <P>(2) A statement of goals and priorities;</P>
                    <P>(3) A detailed description of management actions to be implemented to provide for these ecological needs; and</P>
                    <P>(4) A monitoring and adaptive management plan.</P>
                    <P>Among other things, each INRMP must, to the extent appropriate and applicable, provide for fish and wildlife management; fish and wildlife habitat enhancement or modification; wetland protection, enhancement, and restoration where necessary to support fish and wildlife; and enforcement of applicable natural resource laws.</P>
                    <P>The National Defense Authorization Act for Fiscal Year 2004 (Pub. L. 108-136) amended the Act to limit areas eligible for designation as critical habitat. Specifically, section 4(a)(3)(B)(i) of the Act (16 U.S.C. 1533(a)(3)(B)(i)) provides that: “The Secretary shall not designate as critical habitat any lands or other geographical areas owned or controlled by the Department of Defense, or designated for its use, that are subject to an integrated natural resources management plan prepared under section 101 of the Sikes Act, if the Secretary determines in writing that such plan provides a benefit to the species for which critical habitat is proposed for designation.”</P>
                    <P>We consult with the military on the development and implementation of INRMPs for installations with listed species. We analyzed INRMPs developed by military installations located within the range of the proposed critical habitat designation for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush to determine if they meet the criteria for exemption from critical habitat under section 4(a)(3) of the Act. The following areas are DoD lands with completed, Service-approved INRMPs within the proposed critical habitat designation for Blodgett's silverbush: KWNAS and SOCSO.</P>
                    <HD SOURCE="HD2">Approved INRMPs</HD>
                    <P>
                        <E T="03">Key West Naval Air Station (KWNAS).</E>
                         We have determined that approximately 133 ac (54 ha) of coastal berm and pine rocklands habitat on Boca Chica Key contain the physical or biological features that are essential to the conservation of Blodgett's silverbush. These specific lands are owned and managed by DoD as part of the KWNAS. In July 2020, KWNAS, in coordination with the Service, updated their INRMP to included management and protective measures that provide a conservation benefit to Blodgett's silverbush and its habitat. The Service has approved these management and protective measures, and the INRMP has been signed. As a result, the DoD lands on KWNAS that we have determined contain the physical or biological features that are essential to the conservation of Blodgett's silverbush are being exempted from inclusion in critical habitat under section 4(a)(3)(B)(i) of the Act. Therefore, these specific lands within this installation are exempt from critical habitat designation under section 4(a)(3) of the Act. We are not including approximately 133 ac (54 ha) of habitat in this proposed critical habitat designation for Blodgett's silverbush because of this exemption.
                    </P>
                    <P>
                        <E T="03">Special Operations Command South (SOCSO).</E>
                         We have determined that approximately 25 ac (10 ha) pine rocklands habitat located within SOCSO contain physical or biological features that are essential to the conservation of Blodgett's silverbush. These specific lands are owned and managed by DoD. In July 2020, SOCSO in coordination with the Service, updated their INRMP to included management and protective measures that provide a conservation benefit to Blodgett's silverbush and its habitat. The Service has approved these management and protective measures, and the INRMP has been signed. As a result, the DoD lands on SOCSO that we have determined contain the physical or biological features that are essential to the conservation of Blodgett's silverbush are being exempted from inclusion in critical habitat under section 4(a)(3)(B)(i) of the Act. Therefore, these specific lands within this installation are exempt from critical habitat designation under section 4(a)(3) of the Act. We are not including approximately 25 ac (10 ha) of habitat in this proposed critical habitat 
                        <PRTPAGE P="62526"/>
                        designation for Blodgett's silverbush because of this exemption.
                    </P>
                    <P>
                        <E T="03">Homestead Air Reserve Base (HARB).</E>
                         We have determined that approximately 1,309 ac (530 ha) of pine rocklands and adjacent disturbed areas of habitat on HARB contain physical or biological features that are essential to the conservation of sand flax. These specific lands are owned and managed by DoD as part of the HARB. In July 2020, HARB, in coordination with the Service, began discussions about revising their INRMP to include management and protective measures that provide a conservation benefit to sand flax and its habitat. The Service will review these management and protective measures. If the revised INRMP is approved and signed before we finalize this designation, we would exempt this area in the final designation.
                    </P>
                    <HD SOURCE="HD1">Consideration of Impacts Under Section 4(b)(2) of the Act</HD>
                    <P>Section 4(b)(2) of the Act states that the Secretary shall designate and make revisions to critical habitat on the basis of the best available scientific data after taking into consideration the economic impact, national security impact, and any other relevant impact of specifying any particular area as critical habitat. The Secretary may exclude an area from designated critical habitat based on economic impacts, impacts on national security, or any other relevant impacts. Exclusion decisions are governed by the regulations at 50 CFR 424.19 and the Policy Regarding Implementation of Section 4(b)(2) of the Endangered Species Act, 81 FR 7226 (Feb. 11, 2016) (2016 Policy)—both of which were developed jointly with the National Marine Fisheries Service (NMFS). We also refer to a 2008 Department of the Interior Solicitor's opinion entitled “The Secretary's Authority to Exclude Areas from a Critical Habitat Designation under Section 4(b)(2) of the Endangered Species Act” (M-37016). We explain each decision to exclude areas, as well as decisions not to exclude, to demonstrate that the decision is reasonable.</P>
                    <P>In considering whether to exclude a particular area from the designation, we identify the benefits of including the area in the designation, identify the benefits of excluding the area from the designation, and evaluate whether the benefits of exclusion outweigh the benefits of inclusion. If the analysis indicates that the benefits of exclusion outweigh the benefits of inclusion, the Secretary may exercise discretion to exclude the area only if such exclusion would not result in the extinction of the species. In making the determination to exclude a particular area, the statute on its face, as well as the legislative history, are clear that the Secretary has broad discretion regarding which factor(s) to use and how much weight to give to any factor. We describe below the process that we undertook for taking into consideration each category of impacts and our analyses of the relevant impacts.</P>
                    <HD SOURCE="HD2">Consideration of Economic Impacts</HD>
                    <P>Section 4(b)(2) of the Act and its implementing regulations require that we consider the economic impact that may result from a designation of critical habitat. To assess the probable economic impacts of a designation, we must first evaluate specific land uses or activities and projects that may occur in the area of the critical habitat. We then must evaluate the impacts that a specific critical habitat designation may have on restricting or modifying specific land uses or activities for the benefit of the species and its habitat within the areas proposed. We then identify which conservation efforts may be the result of the species being listed under the Act versus those attributed solely to the designation of critical habitat for this particular species. The probable economic impact of a proposed critical habitat designation is analyzed by comparing scenarios both “with critical habitat” and “without critical habitat.”</P>
                    <P>
                        The “without critical habitat” scenario represents the baseline for the analysis, which includes the existing regulatory and socio-economic burden imposed on landowners, managers, or other resource users potentially affected by the designation of critical habitat (
                        <E T="03">e.g.,</E>
                         under the Federal listing as well as other Federal, State, and local regulations). The baseline, therefore, represents the costs of all efforts attributable to the listing of the species under the Act (
                        <E T="03">i.e.,</E>
                         conservation of the species and its habitat incurred regardless of whether critical habitat is designated). The “with critical habitat” scenario describes the incremental impacts associated specifically with the designation of critical habitat for the species. The incremental conservation efforts and associated impacts would not be expected without the designation of critical habitat for the species. In other words, the incremental costs are those attributable solely to the designation of critical habitat, above and beyond the baseline costs. These are the costs we use when evaluating the benefits of inclusion and exclusion of particular areas from the final designation of critical habitat should we choose to conduct a discretionary section 4(b)(2) exclusion analysis.
                    </P>
                    <P>Executive Orders (E.O.s) 12866 and 13563 direct Federal agencies to assess the costs and benefits of available regulatory alternatives in quantitative (to the extent feasible) and qualitative terms. Consistent with the E.O. regulatory analysis requirements, our effects analysis under the Act may take into consideration impacts to both directly and indirectly affected entities, where practicable and reasonable. If sufficient data are available, we assess to the extent practicable the probable impacts to both directly and indirectly affected entities. Section 3(f) of E.O. 12866 identifies four criteria when a regulation is considered a “significant” rulemaking, and requires additional analysis, review, and approval if met. The criterion relevant here is whether the designation of critical habitat may have an economic effect of greater than $100 million in any given year (section 3(f)(1)). Therefore, our consideration of economic impacts uses a screening analysis to assess whether a designation of critical habitat for these species is likely to exceed the economically significant threshold.</P>
                    <P>
                        For this particular designation, we developed an incremental effects memorandum (IEM) considering the probable incremental economic impacts that may result from this proposed designation of critical habitat. The information contained in our IEM was then used to develop a screening analysis of the probable effects of the designation of critical habitat for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush (IEc 2021, entire). We began by conducting a screening analysis of the proposed designation of critical habitat in order to focus our analysis on the key factors that are likely to result in incremental economic impacts. The purpose of the screening analysis is to filter out particular geographic areas of critical habitat that are already subject to such protections and are, therefore, unlikely to incur incremental economic impacts. In particular, the screening analysis considers baseline costs (
                        <E T="03">i.e.,</E>
                         absent critical habitat designation) and includes probable economic impacts where land and water use may be subject to conservation plans, land management plans, best management practices, or regulations that protect the habitat area as a result of the Federal listing status of the species. Ultimately, the screening analysis allows us to focus our analysis on evaluating the specific areas or sectors that may incur probable incremental economic impacts as a result of the designation.
                    </P>
                    <P>
                        The presence of the listed species in occupied areas of critical habitat means 
                        <PRTPAGE P="62527"/>
                        that any destruction or adverse modification of those areas will also likely jeopardize the continued existence of the species. Therefore, designating occupied areas as critical habitat typically causes few if any incremental impacts above and beyond the impacts of listing the species. Accordingly, the screening analysis focuses on areas of unoccupied critical habitat. The screening analysis also assesses whether units are unoccupied by the species and thus may require additional management or conservation efforts as a result of the critical habitat designation for the species; these additional efforts may incur incremental economic impacts. This screening analysis combined with the information contained in our IEM are what we consider our draft economic analysis (DEA) of the proposed critical habitat designation for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush; our DEA is summarized in the narrative below.
                    </P>
                    <P>As part of our screening analysis, we considered the types of economic activities that are likely to occur within the areas that may be affected by the critical habitat designation. In our evaluation of the probable incremental economic impacts that may result from the proposed designation of critical habitat for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush, first we identified, in the IEM dated September 15, 2021, probable incremental economic impacts associated with the following categories of activities:</P>
                    <P>(1) Land management and restoration (including, but not limited to, nonnative species control, prescribed fire, and hydrologic restoration);</P>
                    <P>(2) Roadway and bridge construction and maintenance;</P>
                    <P>(3) Right-of-way maintenance;</P>
                    <P>(4) Commercial or residential development; and</P>
                    <P>(5) Recreation (including construction and maintenance of recreation infrastructure).</P>
                    <P>
                        We considered each industry or category individually. Additionally, we considered whether their activities have any Federal involvement. Critical habitat designations generally will not affect activities that do not have any Federal involvement; designation of critical habitat only affects activities conducted, funded, permitted, or authorized by Federal agencies. In areas where Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush are present, Federal agencies already are required to consult with the Service under section 7 of the Act on activities they authorize, fund, or carry out that may affect the species. If we finalize this proposed critical habitat designation, consultations to avoid the destruction or adverse modification of critical habitat would be incorporated into the existing consultation process. In our IEM, we attempted to clarify the distinction between the effects that will result from the species being listed and those attributable to the critical habitat designation (
                        <E T="03">i.e.,</E>
                         difference between the jeopardy and adverse modification standards) for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush critical habitat. Because the designation of critical habitat for these species is being proposed several years following the listing of these species, data, such as from consultation history, is available to help us discern which conservation efforts are attributable to these species being listed and those which will result solely from the designation of critical habitat. The following specific circumstances in this case help to inform our evaluation: (1) The essential physical or biological features identified for critical habitat are the same features essential for the life requisites of the species and (2) any actions that would likely adversely affect the essential physical or biological features of occupied critical habitat are also likely to adversely affect these species. The IEM outlines our rationale concerning this limited distinction between baseline conservation efforts and incremental impacts of the designation of critical habitat for these species. This evaluation of the incremental effects has been used as the basis to evaluate the probable incremental economic impacts of this proposed designation of critical habitat.
                    </P>
                    <P>Approximately 1,462 ac (592 ha) in two units in Monroe County, Florida, are being proposed for designation as critical habitat for the Big Pine partridge pea. Both units are occupied by the Big Pine partridge pea. Approximately 1,379 ac (558 ha) in one unit in Monroe County, Florida, is being proposed for designation as critical habitat for the wedge spurge; the unit is occupied by the species. Approximately 5,090 ac (2,060 ha) in five units in Monroe and Miami-Dade Counties, Florida, are being proposed for designation as critical habitat for sand flax. All five units are occupied by sand flax. Approximately 16,635 ac (6,732 ha) in 13 units in Miami-Dade and Monroe Counties, Florida, are being proposed for designation as critical habitat for the Blodgett's silverbush. All 13 units are occupied by the Blodgett's silverbush. Land ownership across the units for all four plants includes Federal lands (64 percent), State of Florida lands (17 percent), county lands (12 percent), and private lands (7 percent). Approximately 83 percent of the total proposed designated critical habitat area for all four plants overlaps with existing designated critical habitat for other species.</P>
                    <P>Because all of the area proposed for designation is occupied, most actions that may affect these species would also affect designated critical habitat, and it is unlikely that any additional conservation efforts would be recommended to address the adverse modification standard over and above those recommended as necessary to avoid jeopardizing the continued existence of these four plants. Therefore, only administrative costs are expected in the proposed critical habitat designation. While the analysis for adverse modification of critical habitat will require time and resources by both the Federal action agency and the Service, it is believed that, in most circumstances, these costs would predominantly be administrative in nature and would not be significant.</P>
                    <P>The economic costs of critical habitat designation for these species will most likely be limited to additional administrative efforts to consider adverse modification in section 7 consultations. This finding is based on the following factors: (1) All of the proposed critical habitat units for the four plants are considered occupied by the species; (2) A number of additional baseline protections exist for the species due to the presence of other listed species and designated critical habitats, with approximately 83 percent of the proposed critical habitat overlapping with designated critical habitat for other pine rockland habitat species; and (3) A number of management plans and conservation plans also provide baseline protections to the species in proposed critical habitat areas. Additionally, if we finalize critical habitat to include areas that are unoccupied by the Big Pine partridge pea, wedge spurge, and sand flax, those areas under consideration wholly overlap with other federally listed species or designated critical habitat for other listed species. Accordingly, the costs associated with designation of unoccupied areas would also likely be limited to additional administrative efforts to consider adverse modification in section 7 consultations.</P>
                    <P>
                        In total, approximately 2 formal consultations, 39 informal consultations, and 2 technical assistance efforts that will include these species are anticipated to occur during the next 10 years in proposed critical habitat 
                        <PRTPAGE P="62528"/>
                        areas, with costs to the Service and action agencies of approximately $11,500 annually. Although the specific geographic distribution of these costs is uncertain, it appears likely that most costs would occur in the ENP unit, which comprises 46 percent of proposed critical habitat for these four plants. Any costs that would be associated with unoccupied critical habitat would not significantly increase this amount.
                    </P>
                    <P>Potential private property value effects are possible due to public perception of impacts to private lands. The designation of critical habitat may cause some developers or landowners to perceive those private lands will be subject to use restrictions or litigation from third parties, resulting in costs. However, any costs associated with public perception are speculative and not possible to quantify. Further, only seven percent of the proposed critical habitat designation is privately owned land, leading to, at most, nominal incremental costs potentially arising from changes in public perception of lands included in the designation.</P>
                    <P>The total annual incremental costs of critical habitat designation for these four plants are anticipated to be approximately $11,500 per year, and economic benefits are also anticipated to be small. Therefore, critical habitat designation for these four plants is unlikely to generate costs or benefits exceeding $100 million in a single year, and this proposed rule is unlikely to meet the threshold for an economically significant rule, with regard to costs under E.O. 12866.</P>
                    <P>We are soliciting data and comments from the public on the DEA discussed above, as well as on all aspects of this proposed rule and our required determinations. During the development of a final designation, we will consider the information presented in the DEA and any additional information on economic impacts we receive during the public comment period to determine whether any specific areas should be considered for exclusion from the final critical habitat designation under authority of section 4(b)(2) and our implementing regulations at 50 CFR 424.19. We may exclude an area from critical habitat if we determine that the benefits of excluding the area outweigh the benefits of including the area, provided the exclusion will not result in the extinction of this species.</P>
                    <HD SOURCE="HD1">Exclusions</HD>
                    <HD SOURCE="HD2">Exclusions Based on Economic Impacts</HD>
                    <P>Under section 4(b)(2) of the Act, we consider the economic impacts of specifying any particular area as critical habitat. In order to consider economic impacts, we prepared an analysis of the probable economic impacts of the proposed critical habitat designation and related factors. At this time, we are not considering any exclusions based on economic impacts.</P>
                    <P>During the development of a final designation, we will consider any additional economic impact information received through the public comment period, and as such areas may be excluded from the final critical habitat designation under section 4(b)(2) of the Act and our implementing regulations at 50 CFR 424.19.</P>
                    <HD SOURCE="HD2">Consideration of National Security Impacts</HD>
                    <P>
                        Section 4(a)(3)(B)(i) of the Act may not cover all DoD lands or areas that pose potential national-security concerns (
                        <E T="03">e.g.,</E>
                         a DoD installation that is in the process of revising its INRMP for a newly listed species or a species previously not covered). If a particular area is not covered under section 4(a)(3)(B)(i), then national-security or homeland-security concerns are not a factor in the process of determining what areas meet the definition of “critical habitat.” However, the Service must still consider impacts on national security, including homeland security, on those lands or areas not covered by section 4(a)(3)(B)(i) because section 4(b)(2) requires the Service to consider those impacts whenever it designates critical habitat. Accordingly, if DoD, Department of Homeland Security (DHS), or another Federal agency has requested exclusion based on an assertion of national-security or homeland-security concerns, or we have otherwise identified national-security or homeland-security impacts from designating particular areas as critical habitat, we generally have reason to consider excluding those areas.
                    </P>
                    <P>However, we cannot automatically exclude requested areas. When DoD, DHS, or another Federal agency requests exclusion from critical habitat on the basis of national-security or homeland-security impacts, it must provide a reasonably specific justification of an incremental impact on national security that would result from the designation of that specific area as critical habitat. That justification could include demonstration of probable impacts, such as impacts to ongoing border-security patrols and surveillance activities, or a delay in training or facility construction, as a result of compliance with section 7(a)(2) of the Act. If the agency requesting the exclusion does not provide us with a reasonably specific justification, we will contact the agency to recommend that it provide a specific justification or clarification of its concerns relative to the probable incremental impact that could result from the designation. If we conduct an exclusion analysis because the agency provides a reasonably specific justification or because we decide to exercise the discretion to conduct an exclusion analysis, we will defer to the expert judgment of DoD, DHS, or another Federal agency as to: (1) Whether activities on its lands or waters, or its activities on other lands or waters, have national-security or homeland-security implications; (2) the importance of those implications; and (3) the degree to which the cited implications would be adversely affected in the absence of an exclusion. In that circumstance, in conducting a discretionary section 4(b)(2) exclusion analysis, we will give great weight to national-security and homeland-security concerns in analyzing the benefits of exclusion.</P>
                    <P>We have evaluated whether any of the lands within the proposed designation of critical habitat are owned by DoD or DHS or could lead to national-security or homeland-security impacts if designated. In this section, we describe the areas within the proposed designation that are owned by DoD or DHS or for which designation could lead to national-security or homeland-security impacts. For each area, we describe the available information indicating whether we have reason to consider excluding the area from the designation. If, during the comment period, we identify or receive information about additional areas for which designation may result in incremental national-security or homeland-security impacts, then we may consider conducting a discretionary exclusion analysis to determine whether to exclude those additional areas under authority of section 4(b)(2) and our implementing regulations at 50 CFR 424.19.</P>
                    <HD SOURCE="HD2">DHS Land Parcel</HD>
                    <P>We have determined that some lands within the Richmond Pinelands and surrounding areas units (Units SF3 and BS10) of the proposed designation of critical habitat for sand flax and Blodgett's silverbush are owned, managed, or used by the USCG, which is part of the DHS.</P>
                    <P>
                        The USCG property is separated into two main areas: the Communication Station (COMMSTA) Miami and the Civil Engineering Unit (CEU). The COMMSTA houses transmitting and receiving antennas. The CEU plans and executes projects at regional shore 
                        <PRTPAGE P="62529"/>
                        facilities, such as construction and post-disaster assessments.
                    </P>
                    <P>The USCG parcel contains approximately 100 ac (40 ha) of standing pine rocklands. The remainder of the site, outside of the developed areas, is made up of scraped pine rocklands that are mowed three to four times per year for maintenance of a communications antenna field. While disturbed, this scraped area maintains sand substrate and many native pine rockland species, including documented occurrences of sand flax and Blodgett's silverbush. As of the drafting of this document, the USCG parcel has a draft management plan that includes management of pine rockland habitats, including vegetation control and prescribed fire and protection of lands from further development or degradation. This management plan is anticipated to be finalized in late 2022. In addition, the standing pine rockland area is partially managed through an active recovery grant to the Institute for Regional Conservation. Under this grant, up to 39 ac (16 ha) of standing pine rocklands will undergo invasive vegetation control.</P>
                    <P>Based on a review of the specific mission of the USCG facility in conjunction with the measures and efforts set forth in the draft management plan to preserve pine rockland habitat and protect sensitive and listed species, we have determined that it is unlikely that the critical habitat, if finalized as proposed, would negatively impact the facility or its operations. As a result, we do not anticipate any impact on national security. However, if through the public comment period we receive information regarding impacts on national security or homeland security from designating this area as critical habitat, then as part of developing the final designation of critical habitat, we will conduct a discretionary exclusion analysis to determine whether to exclude these areas under authority of section 4(b)(2) and our implementing regulations at 50 CFR 424.19.</P>
                    <HD SOURCE="HD2">DoD Land Parcel</HD>
                    <P>As discussed above, we have determined that the USACE, a branch of the Department of Defense, retains ownership over a 121-ac (49-ha) parcel in Units SF3 and BS10 of the proposed designation of critical habitat for sand flax and Blodgett's silverbush, respectively. More than 85 ac (34 ha) of this parcel are forested but not managed for preservation of natural resources. The USACE does not have an INRMP or any specific management plan for sand flax or Blodgett's silverbush or their habitat covering these lands. Activities conducted on this site are unknown; however, we do not anticipate any impact on national security.</P>
                    <P>Following our process for coordinating with Federal partners, we contacted the DoD and DHS about this designation and shared the IEM for their feedback. Neither agency identified any potential national-security impact, nor requested an exclusion from critical habitat based on potential national-security impacts. However, if through the public comment period we receive information regarding impacts on national security or homeland security from designating particular areas as critical habitat, then as part of developing the final designation of critical habitat, we may consider conducting a discretionary exclusion analysis to determine whether to exclude those areas under authority of section 4(b)(2) and our implementing regulations at 50 CFR 424.19.</P>
                    <HD SOURCE="HD2">Considerations of Other Relevant Impacts</HD>
                    <P>Under section 4(b)(2) of the Act, we consider any other relevant impacts, in addition to economic impacts and impacts on national security discussed above. To identify other relevant impacts that may affect the exclusion analysis, we consider a number of factors, including whether there are permitted conservation plans covering the species in the area—such as HCPs, safe harbor agreements (SHAs), or candidate conservation agreements with assurances (CCAAs)—or whether there are non-permitted conservation agreements and partnerships that may be impaired by designation of, or exclusion from, critical habitat. In addition, we look at whether Tribal conservation plans or partnerships, Tribal resources, or government-to-government relationships of the United States with Tribal entities may be affected by the designation. We also consider any State, local, social, or other impacts that might occur because of the designation. When analyzing other relevant impacts of including a particular area in a designation of critical habitat, we weigh those impacts relative to the conservation value of the particular area. To determine the conservation value of designating a particular area, we consider a number of factors, including, but not limited to, the additional regulatory benefits that the area would receive due to the protection from destruction or adverse modification as a result of actions with a Federal nexus, the educational benefits of mapping essential habitat for recovery of the listed species, and any benefits that may result from a designation due to State or Federal laws that may apply to critical habitat.</P>
                    <P>In the case of these species, the benefits of critical habitat include public awareness of the presence of these species and the importance of habitat protection, and, where a Federal nexus exists, habitat protection for these species due to protection from destruction or adverse modification of critical habitat. Continued implementation of an ongoing management plan that provides conservation equal to or more than the protections that result from a critical habitat designation would reduce those benefits of including that specific area in the critical habitat designation.</P>
                    <P>We evaluate the existence of a conservation plan when considering the benefits of inclusion. We consider a variety of factors, including, but not limited to, whether the plan is finalized; how it provides for the conservation of the essential physical or biological features; whether there is a reasonable expectation that the conservation management strategies and actions contained in a management plan will be implemented into the future; whether the conservation strategies in the plan are likely to be effective; and whether the plan contains a monitoring program or adaptive management to ensure that the conservation measures are effective and can be adapted in the future in response to new information.</P>
                    <P>After identifying the benefits of inclusion and the benefits of exclusion, we carefully weigh the two sides to evaluate whether the benefits of exclusion outweigh those of inclusion. If our analysis indicates that the benefits of exclusion outweigh the benefits of inclusion, we then determine whether exclusion would result in extinction of the species. If excluding an area from critical habitat will result in extinction, we will not exclude it from the designation.</P>
                    <HD SOURCE="HD2">Private or Other Non-Federal Conservation Plans Related to Permits Under Section 10 of the Act</HD>
                    <P>
                        HCPs for incidental take permits under section 10(a)(1)(B) of the Act provide for partnerships with non-Federal entities to minimize and mitigate impacts to listed species and their habitat. In some cases, HCP permittees agree to do more for the conservation of the species and their habitats on private lands than designation of critical habitat would provide alone. We place great value on the partnerships that are developed during the preparation and implementation of HCPs.
                        <PRTPAGE P="62530"/>
                    </P>
                    <P>CCAAs and SHAs are voluntary agreements designed to conserve candidate and listed species, respectively, on non-Federal lands. In exchange for actions that contribute to the conservation of species on non-Federal lands, participating property owners are covered by an “enhancement of survival” permit under section 10(a)(1)(A) of the Act, which authorizes incidental take of the covered species that may result from implementation of conservation actions, specific land uses, and, in the case of SHAs, the option to return to a baseline condition under the agreements. The Service also provides enrollees assurances that we will not impose further land-, water-, or resource-use restrictions, or require additional commitments of land, water, or finances, beyond those agreed to in the agreements.</P>
                    <P>
                        When we undertake a discretionary section 4(b)(2) exclusion analysis based on permitted conservation plans (
                        <E T="03">e.g.,</E>
                         CCAAs, SHAs, and HCPs), we anticipate consistently excluding such areas if incidental take caused by the activities in those areas is covered by the permit under section 10 of the Act and the CCAA/SHA/HCP meets all of the following three factors (see the 2016 Policy for additional details):
                    </P>
                    <P>a. The permittee is properly implementing the CCAA/SHA/HCP and is expected to continue to do so for the term of the agreement. A CCAA/SHA/HCP is properly implemented if the permittee is and has been fully implementing the commitments and provisions in the CCAA/SHA/HCP, implementing agreement, and permit.</P>
                    <P>b. The species for which critical habitat is being designated is a covered species in the CCAA/SHA/HCP, or very similar in its habitat requirements to a covered species. The recognition that the Services extend to such an agreement depends on the degree to which the conservation measures undertaken in the CCAA/SHA/HCP would also protect the habitat features of the similar species.</P>
                    <P>c. The CCAA/SHA/HCP specifically addresses that species' habitat and meets the conservation needs of the species in the planning area.</P>
                    <P>The proposed critical habitat designation includes areas that are covered by the following permitted plan providing for the conservation of sand flax and Blodgett's silverbush: Coral Reef Commons HCP.</P>
                    <HD SOURCE="HD2">Coral Reef Commons Habitat Conservation Plan</HD>
                    <P>In preparing this proposal, we have determined that lands associated with the Coral Reef Commons HCP within Unit SF3 for sand flax and Unit BS10 for Blodgett's silverbush (Richmond Pinelands and surrounding areas) are included within the boundaries of the proposed critical habitat.</P>
                    <P>Coral Reef Commons is a mixed-use community, which consists of 900 apartments, retail stores, restaurants, and parking. In 2017, an HCP and associated permit under section 10 of the Act was developed and issued for the Coral Reef Commons development.</P>
                    <P>As part of the HCP and permit, an approximately 53-ac (21-ha) onsite preserve (same as the area for proposed critical habitat designation) was established under a conservation encumbrance that will be managed in perpetuity for pine rockland habitat and sensitive and listed species, including sand flax and Blodgett's silverbush.</P>
                    <P>The Center for Southeastern Tropical Advanced Remote Sensing site is an offsite mitigation area for Coral Reef Commons comprising 57 ac (23 ha). Both the onsite preserve and the offsite mitigation area are being managed to maintain healthy pine rockland habitat using invasive, exotic plant management, mechanical treatment, and prescribed fire, addressing both the habitat and conservation needs of the species. Since initiating the Coral Reef Commons HCP, pine rockland restoration efforts have been conducted within all of the management units in both the onsite preserve and the offsite mitigation area. A second round of prescribed fire began in February 2021. Currently, the onsite preserve meets or exceeds the success criteria described for proper implementation of the HCP.</P>
                    <P>Critical habitat within Units SF3 and BS10 that is associated with the Coral Reef Commons HCP is limited to the onsite preserve and offsite mitigation area. Based on a cursory review of the HCP and proposed critical habitat for sand flax and Blodgett's silverbush, we do not anticipate requesting any additional conservation measures for these species beyond those that are currently in place. Therefore, at this time, we are considering excluding those specific lands associated with the Coral Reef Commons HCP that are in the preserve and off-site mitigation area from the final designation of critical habitat for sand flax and Blodgett's silverbush. However, we will more thoroughly review the HCP, its implementation of the conservation measures for sand flax and Blodgett's silverbush and their habitat therein, and public comment on this issue prior to finalizing critical habitat, and if appropriate, exclude from critical habitat for sand flax and Blodgett's silverbush those lands associated with the Coral Reef Commons HCP that are in the preserves and offsite mitigation area.</P>
                    <HD SOURCE="HD2">Monroe County HCP for Big Pine and No Name Keys</HD>
                    <P>Lands within the Monroe County HCP for Big Pine and No Name Keys are included within proposed critical habitat for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush. However, we have determined that the Monroe County HCP for Big Pine and No Name Keys does not include Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush as “covered species,” and they are not mentioned specifically anywhere in the HCP document. Because they are not covered species, the HCP will not trigger surveys or conservation measures for these species. We are requesting comments on the benefit to Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush from the Monroe County HCP for Big Pine and No Name Keys; however, at this time, we are not proposing the exclusion of any areas within the HCP from the proposed critical habitat.</P>
                    <P>We have determined that there are no additional HCPs or other management plans for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush.</P>
                    <HD SOURCE="HD2">Tribal Lands</HD>
                    <P>Several Executive orders, Secretarial orders, and policies concern working with Tribes. These guidance documents generally confirm our trust responsibilities to Tribes, recognize that Tribes have sovereign authority to control Tribal lands, emphasize the importance of developing partnerships with Tribal governments, and direct the Service to consult with Tribes on a government-to-government basis.</P>
                    <P>
                        A joint Secretarial Order that applies to both the Service and the National Marine Fisheries Service (NMFS)—Secretarial Order 3206, 
                        <E T="03">American Indian Tribal Rights, Federal-Tribal Trust Responsibilities, and the Endangered Species Act</E>
                         (June 5, 1997) (S.O. 3206)—is the most comprehensive of the various guidance documents related to Tribal relationships and Act implementation, and it provides the most detail directly relevant to the designation of critical habitat. In addition to the general direction discussed above, the Appendix to S.O. 3206 explicitly recognizes the right of Tribes to participate fully in any listing process that may affect Tribal rights or Tribal trust resources; this includes the designation of critical habitat. Section 
                        <PRTPAGE P="62531"/>
                        3(b)(4) of the Appendix requires the Service to consult with affected Tribes “when considering the designation of critical habitat in an area that may impact Tribal trust resources, Tribally-owned fee lands, or the exercise of Tribal rights.” That provision also instructs the Service to avoid including Tribal lands within a critical habitat designation unless the area is essential to conserve a listed species, and it requires the Service to “evaluate and document the extent to which the conservation needs of the listed species can be achieved by limiting the designation to other lands.”
                    </P>
                    <P>
                        Our implementing regulations at 50 CFR 424.19 and the 2016 Policy are consistent with S.O. 3206. When we undertake a discretionary exclusion analysis, in accordance with S.O. 3206 we consult with any Tribe whose Tribal trust resources, tribally owned fee lands, or Tribal rights may be affected by including any particular areas in the designation, and we evaluate the extent to which the conservation needs of the species can be achieved by limiting the designation to other areas. When we undertake a discretionary section 4(b)(2) exclusion analysis, we always consider exclusion of Tribal lands, and give great weight to Tribal concerns in analyzing the benefits of exclusion. However, S.O. 3206 does not override the Act's statutory requirement of designation of critical habitat. As stated above, we must consult with any Tribe when a designation of critical habitat may affect Tribal lands or resources. The Act requires us to identify areas that meet the definition of “critical habitat” (
                        <E T="03">i.e.,</E>
                         areas occupied at the time of listing that contain the essential physical or biological features that may require special management or protection and unoccupied areas that are essential to the conservation of a species), without regard to land ownership. While S.O. 3206 provides important direction, it expressly states that it does not modify the Secretary's statutory authority under the Act or other statutes.
                    </P>
                    <P>The proposed critical habitat designation does not include any Tribal lands.</P>
                    <HD SOURCE="HD1">Summary of Exclusions Considered Under 4(b)(2) of the Act</HD>
                    <P>Based on the information provided by entities seeking exclusion, as well as any additional public comments we receive, we will evaluate whether areas in the proposed critical habitat units are appropriate for exclusion from the final designation under section 4(b)(2) of the Act. If our analysis indicates that the benefits of excluding lands from the final designation outweigh the benefits of designating those lands as critical habitat, then the Secretary may exercise her discretion to exclude the lands from the final designation. At this time, we are considering excluding those specific lands associated with the Coral Reef Commons HCP that are in the preserve and offsite mitigation area from the final designation of critical habitat for sand flax and Blodgett's silverbush (units SF3 and BS10). In conclusion, we specifically solicit comments on the inclusion or exclusion of such areas.</P>
                    <P>During the development of a final designation, we will consider any information currently available or received during the public comment period regarding other relevant impacts of the proposed designation and will determine whether these or any other specific areas should be considered for exclusion from the final critical habitat designation under authority of section 4(b)(2), our implementing regulations at 50 CFR 424.19, and the 2016 Policy.</P>
                    <HD SOURCE="HD1">Required Determinations</HD>
                    <HD SOURCE="HD2">Clarity of the Rule</HD>
                    <P>We are required by Executive Orders 12866 and 12988 and by the Presidential Memorandum of June 1, 1998, to write all rules in plain language. This means that each rule we publish must:</P>
                    <P>(1) Be logically organized;</P>
                    <P>(2) Use the active voice to address readers directly;</P>
                    <P>(3) Use clear language rather than jargon;</P>
                    <P>(4) Be divided into short sections and sentences; and</P>
                    <P>(5) Use lists and tables wherever possible.</P>
                    <P>
                        If you feel that we have not met these requirements, send us comments by one of the methods listed in 
                        <E T="02">ADDRESSES.</E>
                         To better help us revise the rule, your comments should be as specific as possible. For example, you should tell us the numbers of the sections or paragraphs that are unclearly written, which sections or sentences are too long, the sections where you feel lists or tables would be useful, etc.
                    </P>
                    <HD SOURCE="HD2">Regulatory Planning and Review (Executive Orders 12866 and 13563)</HD>
                    <P>Executive Order 12866 provides that the Office of Information and Regulatory Affairs (OIRA) in the Office of Management and Budget will review all significant rules. OIRA has determined that this proposed rule is not significant.</P>
                    <P>Executive Order 13563 reaffirms the principles of E.O. 12866 while calling for improvements in the nation's regulatory system to promote predictability, to reduce uncertainty, and to use the best, most innovative, and least burdensome tools for achieving regulatory ends. The executive order directs agencies to consider regulatory approaches that reduce burdens and maintain flexibility and freedom of choice for the public where these approaches are relevant, feasible, and consistent with regulatory objectives. E.O. 13563 emphasizes further that regulations must be based on the best available science and that the rulemaking process must allow for public participation and an open exchange of ideas. We have developed this proposed rule in a manner consistent with these requirements.</P>
                    <HD SOURCE="HD2">
                        Regulatory Flexibility Act (5 U.S.C. 601 
                        <E T="03">et seq.</E>
                        )
                    </HD>
                    <P>
                        Under the Regulatory Flexibility Act (RFA; 5 U.S.C. 601 
                        <E T="03">et seq.</E>
                        ), as amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (SBREFA; 5 U.S.C. 801 
                        <E T="03">et seq.</E>
                        ), whenever an agency is required to publish a notice of rulemaking for any proposed or final rule, it must prepare and make available for public comment a regulatory flexibility analysis that describes the effects of the rule on small entities (
                        <E T="03">i.e.,</E>
                         small businesses, small organizations, and small government jurisdictions). However, no regulatory flexibility analysis is required if the head of the agency certifies the rule will not have a significant economic impact on a substantial number of small entities. The SBREFA amended the RFA to require Federal agencies to provide a certification statement of the factual basis for certifying that the rule will not have a significant economic impact on a substantial number of small entities.
                    </P>
                    <P>
                        According to the Small Business Administration, small entities include small organizations such as independent nonprofit organizations; small governmental jurisdictions, including school boards and city and town governments that serve fewer than 50,000 residents; and small businesses (13 CFR 121.201). Small businesses include manufacturing and mining concerns with fewer than 500 employees, wholesale trade entities with fewer than 100 employees, retail and service businesses with less than $5 million in annual sales, general and heavy construction businesses with less than $27.5 million in annual business, special trade contractors doing less than $11.5 million in annual business, and agricultural businesses with annual sales less than $750,000. To determine if potential economic impacts to these small entities are significant, we considered the types of activities that might trigger regulatory impacts under 
                        <PRTPAGE P="62532"/>
                        this designation as well as types of project modifications that may result. In general, the term “significant economic impact” is meant to apply to a typical small business firm's business operations.
                    </P>
                    <P>Under the RFA, as amended, and as understood in light of recent court decisions, Federal agencies are required to evaluate the potential incremental impacts of rulemaking on those entities directly regulated by the rulemaking itself; in other words, the RFA does not require agencies to evaluate the potential impacts to indirectly regulated entities. The regulatory mechanism through which critical habitat protections are realized is section 7 of the Act, which requires Federal agencies, in consultation with the Service, to ensure that any action authorized, funded, or carried out by the agency is not likely to destroy or adversely modify critical habitat. Therefore, under section 7, only Federal action agencies are directly subject to the specific regulatory requirement (avoiding destruction and adverse modification) imposed by critical habitat designation. Consequently, it is our position that only Federal action agencies would be directly regulated if we adopt the proposed critical habitat designation. The RFA does not require evaluation of the potential impacts to entities not directly regulated. Moreover, Federal agencies are not small entities. Therefore, because no small entities would be directly regulated by this rulemaking, the Service certifies that, if made final as proposed, the proposed critical habitat designation will not have a significant economic impact on a substantial number of small entities. In summary, we have considered whether the proposed designation would result in a significant economic impact on a substantial number of small entities. For the above reasons and based on currently available information, we certify that, if made final, the proposed critical habitat designation will not have a significant economic impact on a substantial number of small business entities. Therefore, an initial regulatory flexibility analysis is not required.</P>
                    <HD SOURCE="HD2">Energy Supply, Distribution, or Use—Executive Order 13211</HD>
                    <P>Executive Order 13211 (Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use) requires agencies to prepare statements of energy effects when undertaking certain actions. We do not foresee any energy development projects, supply distribution, or use that may affect or be affected by the proposed critical habitat for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush. Further, in our evaluation of potential economic impacts, we did not find that this proposed critical habitat designation would significantly affect energy supplies, distribution, or use. Therefore, this action is not a significant energy action, and no statement of energy effects is required.</P>
                    <HD SOURCE="HD2">Unfunded Mandates Reform Act (2 U.S.C. 1501 et seq.)</HD>
                    <P>
                        In accordance with the Unfunded Mandates Reform Act (2 U.S.C. 1501 
                        <E T="03">et seq.</E>
                        ), we make the following finding:
                    </P>
                    <P>(1) This proposed rule would not produce a Federal mandate. In general, a Federal mandate is a provision in legislation, statute, or regulation that would impose an enforceable duty upon State, local, or tribal governments, or the private sector, and includes both “Federal intergovernmental mandates” and “Federal private sector mandates.” These terms are defined in 2 U.S.C. 658(5)-(7). “Federal intergovernmental mandate” includes a regulation that “would impose an enforceable duty upon State, local, or tribal governments” with two exceptions. It excludes “a condition of Federal assistance.” It also excludes “a duty arising from participation in a voluntary Federal program,” unless the regulation “relates to a then-existing Federal program under which $500,000,000 or more is provided annually to State, local, and tribal governments under entitlement authority,” if the provision would “increase the stringency of conditions of assistance” or “place caps upon, or otherwise decrease, the Federal Government's responsibility to provide funding,” and the State, local, or tribal governments “lack authority” to adjust accordingly. At the time of enactment, these entitlement programs were: Medicaid; Aid to Families with Dependent Children work programs; Child Nutrition; Food Stamps; Social Services Block Grants; Vocational Rehabilitation State Grants; Foster Care, Adoption Assistance, and Independent Living; Family Support Welfare Services; and Child Support Enforcement. “Federal private sector mandate” includes a regulation that “would impose an enforceable duty upon the private sector, except (i) a condition of Federal assistance or (ii) a duty arising from participation in a voluntary Federal program.”</P>
                    <P>The designation of critical habitat does not impose a legally binding duty on non-Federal Government entities or private parties. Under the Act, the only regulatory effect is that Federal agencies must ensure that their actions do not destroy or adversely modify critical habitat under section 7. While non-Federal entities that receive Federal funding, assistance, or permits, or that otherwise require approval or authorization from a Federal agency for an action, may be indirectly impacted by the designation of critical habitat, the legally binding duty to avoid destruction or adverse modification of critical habitat rests squarely on the Federal agency. Furthermore, to the extent that non-Federal entities are indirectly impacted because they receive Federal assistance or participate in a voluntary Federal aid program, the Unfunded Mandates Reform Act would not apply, nor would critical habitat shift the costs of the large entitlement programs listed above onto State governments.</P>
                    <P>(2) We do not believe that this proposed rule would significantly or uniquely affect small governments. The government lands being proposed for critical habitat designation are owned by the State of Florida, DoD, National Park Service, and the Service. None of these government entities fit the definition of “small governmental jurisdiction.” Therefore, a small government agency plan is not required.</P>
                    <HD SOURCE="HD2">Takings—Executive Order 12630</HD>
                    <P>
                        In accordance with E.O. 12630 (Government Actions and Interference with Constitutionally Protected Private Property Rights), we have analyzed the potential takings implications of designating critical habitat for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush in a takings implications assessment. The Act does not authorize the Service to regulate private actions on private lands or confiscate private property as a result of critical habitat designation. Designation of critical habitat does not affect land ownership, or establish any closures, or restrictions on use of or access to the designated areas. Furthermore, the designation of critical habitat does not affect landowner actions that do not require Federal funding or permits, nor does it preclude development of habitat conservation programs or issuance of incidental take permits to permit actions that do require Federal funding or permits to go forward. However, Federal agencies are prohibited from carrying out, funding, or authorizing actions that would destroy or adversely modify critical habitat. A takings implications assessment has been completed for the proposed designation of critical habitat for Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush, and it concludes that, if 
                        <PRTPAGE P="62533"/>
                        adopted, this designation of critical habitat does not pose significant takings implications for lands within or affected by the designation.
                    </P>
                    <HD SOURCE="HD2">Federalism—Executive Order 13132</HD>
                    <P>In accordance with E.O. 13132 (Federalism), this proposed rule does not have significant federalism effects. A federalism summary impact statement is not required. In keeping with Department of the Interior and Department of Commerce policy, we requested information from, and coordinated development of this proposed critical habitat designation with, appropriate State resource agencies. From a federalism perspective, the designation of critical habitat directly affects only the responsibilities of Federal agencies. The Act imposes no other duties with respect to critical habitat, either for States and local governments, or for anyone else. As a result, the proposed rule does not have substantial direct effects either on the States, or on the relationship between the national government and the States, or on the distribution of powers and responsibilities among the various levels of government. The proposed designation may have some benefit to these governments because the areas that contain the features essential to the conservation of the species are more clearly defined, and the physical or biological features of the habitat necessary for the conservation of the species are specifically identified. This information does not alter where and what federally sponsored activities may occur. However, it may assist State and local governments in long-range planning because they no longer have to wait for case-by-case section 7 consultations to occur.</P>
                    <P>Where State and local governments require approval or authorization from a Federal agency for actions that may affect critical habitat, consultation under section 7(a)(2) of the Act would be required. While non-Federal entities that receive Federal funding, assistance, or permits, or that otherwise require approval or authorization from a Federal agency for an action, may be indirectly impacted by the designation of critical habitat, the legally binding duty to avoid destruction or adverse modification of critical habitat rests squarely on the Federal agency.</P>
                    <HD SOURCE="HD2">Civil Justice Reform—Executive Order 12988</HD>
                    <P>In accordance with Executive Order 12988 (Civil Justice Reform), the Office of the Solicitor has determined that the rule would not unduly burden the judicial system and that it meets the requirements of sections 3(a) and 3(b)(2) of the Order. We have proposed designating critical habitat in accordance with the provisions of the Act. To assist the public in understanding the habitat needs of the species, this proposed rule identifies the elements of physical or biological features essential to the conservation of the species. The proposed areas of designated critical habitat are presented on maps, and the proposed rule provides several options for the interested public to obtain more detailed location information, if desired.</P>
                    <HD SOURCE="HD2">
                        Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                        )
                    </HD>
                    <P>
                        This proposed rule does not contain information collection requirements, and a submission to the Office of Management and Budget (OMB) under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                        ) is not required. We may not conduct or sponsor and you are not required to respond to a collection of information unless it displays a currently valid OMB control number.
                    </P>
                    <HD SOURCE="HD2">National Environmental Policy Act(42 U.S.C. 4321 et seq.)</HD>
                    <P>
                        It is our position that, outside the jurisdiction of the U.S. Court of Appeals for the Tenth Circuit, we do not need to prepare environmental analyses pursuant to the National Environmental Policy Act (NEPA; 42 U.S.C. 4321 
                        <E T="03">et seq.</E>
                        ) in connection with regulations adopted pursuant to section 4(a) of the Act. We published a notice outlining our reasons for this determination in the 
                        <E T="04">Federal Register</E>
                         on October 25, 1983 (48 FR 49244). This position was upheld by the U.S. Court of Appeals for the Ninth Circuit (
                        <E T="03">Douglas County</E>
                         v. 
                        <E T="03">Babbitt,</E>
                         48 F.3d 1495 (9th Cir. 1995)).
                    </P>
                    <HD SOURCE="HD2">Government-to-Government Relationship With Tribes</HD>
                    <P>In accordance with the President's memorandum of April 29, 1994 (Government-to-Government Relations with Native American Tribal Governments; 59 FR 22951), Executive Order 13175 (Consultation and Coordination with Indian Tribal Governments), and the Department of the Interior's manual at 512 DM 2, we readily acknowledge our responsibility to communicate meaningfully with recognized Federal Tribes on a government-to-government basis. In accordance with Secretarial Order 3206 of June 5, 1997 (American Indian Tribal Rights, Federal-Tribal Trust Responsibilities, and the Endangered Species Act), we readily acknowledge our responsibilities to work directly with Tribes in developing programs for healthy ecosystems, to acknowledge that Tribal lands are not subject to the same controls as Federal public lands, to remain sensitive to Indian culture, and to make information available to Tribes.</P>
                    <P>
                        As discussed above (see 
                        <E T="03">Exclusions Based on Other Relevant Impacts</E>
                        ), we have determined that there are no Tribal lands that were occupied by Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush at the time of listing that contain the features essential for conservation of the species, and no Tribal lands unoccupied by Big Pine partridge pea, wedge spurge, sand flax, and Blodgett's silverbush that are essential for the conservation of the species. As a result, there are no Tribal lands affected by the proposed designation of critical habitat for these species.
                    </P>
                    <HD SOURCE="HD1">References Cited</HD>
                    <P>
                        A complete list of references cited in this rulemaking is available on the internet at 
                        <E T="03">https://www.regulations.gov</E>
                         and upon request from the Florida Ecological Services Field Office (see 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        ).
                    </P>
                    <HD SOURCE="HD1">Authors</HD>
                    <P>The primary authors of this proposed rule are the staff members of the Fish and Wildlife Service's Florida Ecological Services Field Office.</P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 50 CFR Part 17</HD>
                        <P>Endangered and threatened species, Exports, Imports, Plants, Reporting and recordkeeping requirements, Transportation, Wildlife.</P>
                    </LSTSUB>
                    <HD SOURCE="HD1">Proposed Regulation Promulgation</HD>
                    <P>Accordingly, we propose to amend part 17, subchapter B of chapter I, title 50 of the Code of Federal Regulations, as set forth below:</P>
                    <PART>
                        <HD SOURCE="HED">PART 17—ENDANGERED AND THREATENED WILDLIFE AND PLANTS</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 17 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 16 U.S.C. 1361-1407; 1531-1544; 4201-4245, unless otherwise noted.</P>
                    </AUTH>
                    <AMDPAR>
                        2. In § 17.12 in paragraph (h), revise the entries for “
                        <E T="03">Argythamnia blodgettii</E>
                         (Blodgett's silverbush)”, “
                        <E T="03">Chamaesyce deltoidea</E>
                         ssp. 
                        <E T="03">serpyllum</E>
                         (Wedge spurge)”, “
                        <E T="03">Chamaecrista lineata</E>
                         var. 
                        <E T="03">keyensis</E>
                         (Big Pine partridge pea)”, and “
                        <E T="03">Linum arenicola</E>
                         (Sand flax)”, under “Flowering Plants” in the List of Endangered and Threatened Plants to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 17.12</SECTNO>
                        <SUBJECT>Endangered and threatened plants.</SUBJECT>
                        <STARS/>
                        <PRTPAGE P="62534"/>
                        <P>(h) * * *</P>
                        <GPOTABLE COLS="5" OPTS="L1,tp0,i1" CDEF="s50,r50,r50,8C,r65">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1">Scientific name</CHED>
                                <CHED H="1">Common name</CHED>
                                <CHED H="1">Where listed</CHED>
                                <CHED H="1">Status</CHED>
                                <CHED H="1">Listing citations and applicable rules</CHED>
                            </BOXHD>
                            <ROW EXPSTB="04">
                                <ENT I="21">
                                    <E T="03">Flowering Plants</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Argythamnia blodgettii</E>
                                </ENT>
                                <ENT>Blodgett's silverbush</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>T</ENT>
                                <ENT>
                                    81 FR 66842, 9/29/2016; 50 CFR 17.96(a).
                                    <SU>CH</SU>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Chamaecrista lineata</E>
                                     var. 
                                    <E T="03">keyensis</E>
                                </ENT>
                                <ENT>Big Pine partridge pea</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    81 FR 66842, 9/29/2016; 50 CFR 17.96(a).
                                    <SU>CH</SU>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Chamaesyce deltoidea</E>
                                     ssp. 
                                    <E T="03">serpyllum</E>
                                </ENT>
                                <ENT>Wedge spurge</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    81 FR 66842; 9/29/2016; 50 CFR 17.96(a).
                                    <SU>CH</SU>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Linum arenicola</E>
                                </ENT>
                                <ENT>Sand flax</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    81 FR 66842, 9/29/2016;50 CFR 17.96(a).
                                    <SU>CH</SU>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                        </GPOTABLE>
                    </SECTION>
                    <AMDPAR>
                        3. Amend § 17.96 in paragraph (a) by adding entries in alphabetical order under Family Euphorbiaceae for “
                        <E T="03">Argythamnia blodgettii</E>
                         (Blodgett's silverbush)” and “
                        <E T="03">Chamaesyce deltoidea</E>
                         ssp. 
                        <E T="03">serpyllum</E>
                         (wedge spurge)”, under Family Fabaceae for “
                        <E T="03">Chamaecrista lineata</E>
                         var. 
                        <E T="03">keyensis</E>
                         (Big Pine partridge pea)”, and under Family Linaceae for “
                        <E T="03">Linum arenicola</E>
                         (sand flax)”, to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 17.96</SECTNO>
                        <SUBJECT>Critical habitat—plants.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Flowering plants.</E>
                        </P>
                        <STARS/>
                        <FP SOURCE="FP-1">
                            Family Euphorbiaceae: 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's Silverbush)
                        </FP>
                        <P>(1) Critical habitat units are depicted for Miami-Dade and Monroe Counties, Florida, on the maps below.</P>
                        <P>
                            (2) Within these areas, the physical or biological features essential to the conservation of 
                            <E T="03">Argythamnia blodgettii</E>
                             consist of south Florida pine rockland, rockland hammock, or coastal berm habitats and adjacent disturbed areas that:
                        </P>
                        <P>
                            (i) Consist of limestone substrate that provides nutritional requirements and suitable growing conditions (
                            <E T="03">e.g.,</E>
                             pH, nutrients, anchoring, and drainage);
                        </P>
                        <P>(ii) Are characterized by an open canopy and understory with a high proportion of native plant species to provide for sufficient sunlight to permit growth and flowering;</P>
                        <P>(iii) Are subjected to a monthly mean temperature characteristic of the subtropical humid classification in Miami-Dade County and tropical humid classification in Monroe County in every month of the year and short hydroperiods ranging of up to 60 days each year;</P>
                        <P>
                            (iv) Are subjected to periodic natural (
                            <E T="03">e.g.,</E>
                             fire, hurricanes) or nonnatural (
                            <E T="03">e.g.,</E>
                             prescribed fire, mowing) disturbance regimes to maintain open canopy conditions; and
                        </P>
                        <P>(v) Contain the presence of native pollinators for natural pollination and reproduction.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings, aqueducts, runways, roads, and other paved areas) and the land on which they are located existing within the legal boundaries on [EFFECTIVE DATE OF FINAL RULE].</P>
                        <P>
                            (4) Critical habitat map units. Data layers defining map units were created using ESRI ArcGIS mapping software. The projection used was Albers Conical Equal Area (Florida Geographic Data Library), NAD 1983 HARN. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. Shapefiles for the critical habitat units are available to the public at the Service's internet site, 
                            <E T="03">https://www.fws.gov/office/florida-ecological-services/library,</E>
                             and a list of coordinates outlining the units are available at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R4-ES-2022-0116, at 
                            <E T="03">https://www.fws.gov/office/florida-ecological-services/library,</E>
                             and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>
                            (5) Note: Index maps of all critical habitat units for 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's silverbush) follow:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 1 to 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's silverbush) paragraph (5)
                        </FP>
                        <BILCOD>BILLING CODE 4333-15-P</BILCOD>
                        <GPH SPAN="3" DEEP="520">
                            <PRTPAGE P="62535"/>
                            <GID>EP14OC22.005</GID>
                        </GPH>
                        <FP SOURCE="FP-1">
                            Figure 2 to 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's silverbush) paragraph (5)
                        </FP>
                        <GPH SPAN="3" DEEP="536">
                            <PRTPAGE P="62536"/>
                            <GID>EP14OC22.006</GID>
                        </GPH>
                        <P>(6) Unit 1: BS1—Key Largo, Monroe County, Florida.</P>
                        <P>(i) This unit consists of 3,060 ac (1,238 ha). This unit extends from near the northern tip of Key Largo, along the length of the island to the southern tip. It is bordered on the east by the Atlantic Ocean and on the west by Florida Bay. The unit also includes a portion of El Radabob Key.</P>
                        <P>(ii) Map of Unit 1 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 3 to 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's silverbush) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="516">
                            <PRTPAGE P="62537"/>
                            <GID>EP14OC22.007</GID>
                        </GPH>
                        <P>(7) Unit 2: BS2—Plantation Key, Monroe County, Florida.</P>
                        <P>(i) This unit consists of 175 ac (71 ha). The unit originates on the north end of Plantation Key just south of Ocean Drive and continues intermittently until the south end of the island. The unit is bordered on the east by the Atlantic Ocean and on the west by Florida Bay.</P>
                        <P>(ii) Map of Unit 2 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 4 to 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's silverbush) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="509">
                            <PRTPAGE P="62538"/>
                            <GID>EP14OC22.008</GID>
                        </GPH>
                        <P>(8) Unit 3: BS3—Windley Key, Monroe County, Florida.</P>
                        <P>(i) This unit consists of 30 ac (12 ha). The unit is located on Windley Key on the north side of the Overseas Highway.</P>
                        <P>(ii) Map of Unit 3 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 5 to 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's silverbush) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="512">
                            <PRTPAGE P="62539"/>
                            <GID>EP14OC22.009</GID>
                        </GPH>
                        <P>(9) Unit 4: BS4—Lignumvitae Key, Monroe County, Florida.</P>
                        <P>(i) This unit consists of 159 ac (64 ha). This unit includes the entire upland area of Lignumvitae Key.</P>
                        <P>(ii) Map of Unit 4 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 6 to 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's silverbush) paragraph (9)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="533">
                            <PRTPAGE P="62540"/>
                            <GID>EP14OC22.010</GID>
                        </GPH>
                        <P>(10) Unit 5: BS5—Lower Matecumbe Key, Monroe County, Florida.</P>
                        <P>(i) This unit consists of 64 ac (26 ha). This unit extends from the east side of U.S. 1 from 0.14 mi (0.2 km) from the north edge of Lower Matecumbe Key, situated across U.S. 1 from Davis Lane and Tiki Lane. The unit continues on either side of U.S. 1 approximately 0.4 mi (0.6 km) from the north edge of Lower Matecumbe Key for approximately 0.6 mi (0.9 km).</P>
                        <P>(ii) Map of Unit 5 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 7 to 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's silverbush) paragraph (10)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="514">
                            <PRTPAGE P="62541"/>
                            <GID>EP14OC22.011</GID>
                        </GPH>
                        <P>(11) Unit 6: BS6—Marathon, Monroe County, Florida.</P>
                        <P>(i) This unit consists of 103 ac (42 ha). The unit consists of several areas along the Overseas Highway. Starting at Crawl Key to the north, proceeding southward encompassing hardwood hammock areas on Long Point Key, Fat Deer Key, and Vaca Key; and coastal berm on the south shore of Boot Key.</P>
                        <P>(ii) Map of Unit 6 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 8 to 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's silverbush) paragraph (11)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="516">
                            <PRTPAGE P="62542"/>
                            <GID>EP14OC22.012</GID>
                        </GPH>
                        <P>(12) Unit 7: BS7—Big Pine Key, Monroe County, Florida.</P>
                        <P>(i) This unit consists of 1,867 ac (756 ha). This unit extends from near the northern tip of Big Pine Key to its southern shore, encompassing most of the undeveloped pine rocklands and rockland hammock habitat remaining on Big Pine Key.</P>
                        <P>(ii) Map of Unit 7 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 9 to 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's silverbush) paragraph (12)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="507">
                            <PRTPAGE P="62543"/>
                            <GID>EP14OC22.013</GID>
                        </GPH>
                        <P>(13) Unit 8: BS8—Big Munson Island, Monroe County, Florida.</P>
                        <P>(i) This unit consists of 28 ac (11 ha). The unit includes all coastal berm and rockland hammock habitat on the island.</P>
                        <P>(ii) Map of Unit 8 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 10 to 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's silverbush) paragraph (13)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="520">
                            <PRTPAGE P="62544"/>
                            <GID>EP14OC22.014</GID>
                        </GPH>
                        <P>(14) Unit 9: BS9—U.S. Department of Agriculture, Subtropical Horticulture Research Station, and surrounding areas, Miami-Dade County, Florida.</P>
                        <P>(i) This unit consists of approximately 630 ac (255 ha). This unit is bordered on the north by SW 112 Street, on the south by the intersection of Old Cutler Road and Franjo Road (County Road (CR) 977), on the east by the Atlantic Ocean, and on the west by U.S. 1 (South Dixie Highway).</P>
                        <P>(ii) Map of Unit BS9 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 11 to 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's silverbush) paragraph (14)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="505">
                            <PRTPAGE P="62545"/>
                            <GID>EP14OC22.015</GID>
                        </GPH>
                        <P>(15) Unit 10: BS10—Richmond Pinelands and surrounding areas, Miami-Dade County, Florida.</P>
                        <P>(i) This unit consists of approximately 987 ac (399 ha). This unit is bordered on the north by SW 152 Street (Coral Reef Drive), on the south by SW 200 St (Quail Drive/SR 994), on the east by U.S. 1 (South Dixie Highway), and on the west by SW 177 Avenue (Krome Avenue).</P>
                        <P>(ii) Map of Unit 10 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 12 to 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's silverbush) paragraph (15)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="516">
                            <PRTPAGE P="62546"/>
                            <GID>EP14OC22.016</GID>
                        </GPH>
                        <P>(16) Unit 11: BS11—Quail Roost Pineland and surrounding areas, Miami-Dade County, Florida.</P>
                        <P>(i) This unit consists of approximately 412 ac (167 ha). This unit is bordered on the north by SW 200 St (Quail Drive/SR 994), on the south by SW 248 Street, on the east by the Florida Turnpike, and on the west by SW 194 Avenue.</P>
                        <P>(ii) Map of Unit 11 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 13 to 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's silverbush) paragraph (16)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="513">
                            <PRTPAGE P="62547"/>
                            <GID>EP14OC22.017</GID>
                        </GPH>
                        <P>(17) Unit 12: BS12—Camp Owaissa Bauer and surrounding areas, Miami-Dade County, Florida.</P>
                        <P>(i) This unit consists of approximately 392 ac (159 ha). This unit is bordered on the north by SW 248 Street, on the south by SW 312 Street, on the east by SW 112 Avenue, and on the west by SW 217 Avenue.</P>
                        <P>(ii) Map of Unit 12 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 14 to 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's silverbush) paragraph (17)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="508">
                            <PRTPAGE P="62548"/>
                            <GID>EP14OC22.018</GID>
                        </GPH>
                        <P>(18) Unit 13: BS13—Everglades National Park, Long Pine Key and surrounding areas, Miami-Dade County, Florida.</P>
                        <P>(i) This unit consists of approximately 8,728 ac (3,532 ha). This unit is located within the boundary of Everglades National Park.</P>
                        <P>(ii) Map of Unit 13 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 15 to 
                            <E T="03">Argythamnia blodgettii</E>
                             (Blodgett's silverbush) paragraph (18)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="498">
                            <PRTPAGE P="62549"/>
                            <GID>EP14OC22.019</GID>
                        </GPH>
                        <P>
                            Family Euphorbiaceae: 
                            <E T="03">Chamaesyce deltoidea</E>
                             ssp. 
                            <E T="03">serpyllum</E>
                             (wedge spurge)
                        </P>
                        <P>(1) Critical habitat is depicted for Monroe County, Florida, on the map below.</P>
                        <P>
                            (2) Within these areas, the physical or biological features essential to the conservation of 
                            <E T="03">Chamaesyce deltoidea</E>
                             ssp. 
                            <E T="03">serpyllum</E>
                             consist of South Florida pine rockland habitat and adjacent disturbed areas that:
                        </P>
                        <P>
                            (i) Consist of calcareous limestone substrate (often exposed with little soil development) that provides nutritional requirements and suitable growing conditions (
                            <E T="03">e.g.,</E>
                             pH, nutrients, anchoring, and drainage);
                        </P>
                        <P>
                            (ii) Are characterized by an open canopy of 
                            <E T="03">Pinus elliottii</E>
                             var. 
                            <E T="03">densa</E>
                             (South Florida slash pine) and understory with a high proportion of native pine rockland plant species to provide for sufficient sunlight to permit growth and flowering;
                        </P>
                        <P>(iii) Are subjected to a monthly mean temperature characteristic of the subtropical humid classification in Miami-Dade County and tropical humid classification in Monroe County in every month of the year and short hydroperiods ranging of up to 60 days each year;</P>
                        <P>
                            (iv) Are subjected to periodic natural (
                            <E T="03">e.g.,</E>
                             fire) or nonnatural (
                            <E T="03">e.g.,</E>
                             prescribed fire, mowing) disturbance regimes to maintain open canopy conditions; and
                        </P>
                        <P>(v) Contain the presence of native pollinators for natural pollination and reproduction.</P>
                        <P>
                            (3) Critical habitat does not include manmade structures (such as buildings, aqueducts, runways, roads, and other paved areas) and the land on which they are located existing within the legal boundaries on [EFFECTIVE DATE OF FINAL RULE].
                            <PRTPAGE P="62550"/>
                        </P>
                        <P>
                            (4) Critical habitat map unit. Data layers defining the map unit were created using ESRI ArcGIS mapping software. The projection used was Albers Conical Equal Area (Florida Geographic Data Library), NAD 1983 HARN. The map in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. Shapefiles for the critical habitat unit are available to the public at the Service's internet site, 
                            <E T="03">https://www.fws.gov/office/florida-ecological-services/library,</E>
                             and a list of coordinates outlining the proposed Units are available at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R4-ES-2022-0116, at 
                            <E T="03">https://www.fws.gov/office/florida-ecological-services/library,</E>
                             and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) Unit 1: WS1—Big Pine Key, Monroe County, Florida.</P>
                        <P>(i) This unit consists of 1,379 ac (558 ha). The unit begins on northern Big Pine Key on the southern side of Gulf Boulevard, continues south on both sides of Key Deer Boulevard (CR 940) to the vicinity of Osprey Lane on the western side of CR 940 and Tea Lane to the east of CR 940; then resumes on both sides of CR 940 from Osprey Lane to south of Driftwood Lane; then resumes south of Osceola Street, between Fern Avenue to the west and Baba Lane to the east; then resumes north of Watson Boulevard in the vicinity of Avenue C; then continues south on both sides of Avenue C to South Street; then resumes on both sides of CR 940 south to U.S. 1 between Ships Way to the west and Sands Street to the east; then resumes south of U.S. 1 from Newfound Boulevard to the west and Deer Run Trail to the east; then resumes south of U.S. 1 from Palomino Horse Trail to the west and Industrial Road to the east.</P>
                        <P>(ii) Map of Unit 1 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to 
                            <E T="03">Chamaesyce deltoidea</E>
                             ssp. 
                            <E T="03">serpyllum</E>
                             (wedge spurge) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="522">
                            <PRTPAGE P="62551"/>
                            <GID>EP14OC22.020</GID>
                        </GPH>
                        <STARS/>
                        <P>
                            Family Fabaceae: 
                            <E T="03">Chamaecrista lineata</E>
                             var. 
                            <E T="03">keyensis</E>
                             (Big Pine partridge pea)
                        </P>
                        <P>(1) Critical habitat units are depicted for Monroe County, Florida, on the maps below.</P>
                        <P>
                            (2) Within these areas, the physical or biological features essential to the conservation of 
                            <E T="03">Chamaecrista lineata</E>
                             var. 
                            <E T="03">keyensis</E>
                             consist of South Florida pine rockland habitat and adjacent disturbed areas that:
                        </P>
                        <P>
                            (i) Consist of calcareous limestone substrate (often exposed with little soil development) that provides nutritional requirements and suitable growing conditions (
                            <E T="03">e.g.,</E>
                             pH, nutrients, anchoring and drainage);
                        </P>
                        <P>
                            (ii) Are characterized by an open canopy of 
                            <E T="03">Pinus elliottii</E>
                             var. 
                            <E T="03">densa</E>
                             (South Florida slash pine) and understory with a high proportion of native pine rockland plant species to provide for sufficient sunlight to permit growth and flowering;
                        </P>
                        <P>(iii) Are subjected to a monthly mean temperature characteristic of the subtropical humid classification in Miami-Dade County and tropical humid classification in Monroe County in every month of the year and short hydroperiods ranging of up to 60 days each year;</P>
                        <P>
                            (iv) Are subjected to periodic natural (
                            <E T="03">e.g.,</E>
                             fire) or nonnatural (
                            <E T="03">e.g.,</E>
                             prescribed fire, mowing) disturbance regimes to maintain open canopy conditions; and
                            <PRTPAGE P="62552"/>
                        </P>
                        <P>(v) Contain the presence of native pollinators for natural pollination and reproduction.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings, aqueducts, runways, roads, and other paved areas) and the land on which they are located existing within the legal boundaries on [EFFECTIVE DATE OF FINAL RULE].</P>
                        <P>
                            (4) Critical habitat map units. Data layers defining map units were created using ESRI ArcGIS mapping software. The projection used was Albers Conical Equal Area (Florida Geographic Data Library), NAD 1983 HARN. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. Shapefiles for the critical habitat units are available to the public at the Service's internet site, 
                            <E T="03">https://www.fws.gov/office/florida-ecological-services/library,</E>
                             and a list of coordinates outlining the units are available at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R4-ES-2022-0116, at 
                            <E T="03">https://www.fws.gov/office/florida-ecological-services/library,</E>
                             and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>
                            (5) Note: Index map of all critical habitat units for 
                            <E T="03">Chamaecrista lineata</E>
                             var. 
                            <E T="03">keyensis</E>
                             (Big Pine partridge pea) follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 1 to 
                            <E T="03">Chamaecrista lineata</E>
                             var. 
                            <E T="03">keyensis</E>
                             (Big Pine partridge pea) paragraph (5)
                        </FP>
                        <GPH SPAN="3" DEEP="516">
                            <GID>EP14OC22.021</GID>
                        </GPH>
                        <PRTPAGE P="62553"/>
                        <P>(6) Unit 1: BPP1—Big Pine Key, Monroe County, Florida.</P>
                        <P>(i) This unit consists of 1,379 ac (558 ha). The unit begins on northern Big Pine Key on the southern side of Gulf Boulevard, continues south on both sides of Key Deer Boulevard (CR 940) to the vicinity of Osprey Lane on the western side of CR 940 and Tea Lane to the east of CR 940; then resumes on both sides of CR 940 from Osprey Lane to south of Driftwood Lane; then resumes south of Osceola Street, between Fern Avenue to the west and Baba Lane to the east; then resumes north of Watson Boulevard in the vicinity of Avenue C; then continues south on both sides of Avenue C to South Street; then resumes on both sides of CR 940 south to U.S. 1 between Ships Way to the west and Sands Street to the east; then resumes south of U.S. 1 from Newfound Boulevard to the west and Deer Run Trail to the east; then resumes south of U.S. 1 from Palomino Horse Trail to the west and Industrial Road to the east.</P>
                        <P>(ii) Map of Unit 1 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 2 to 
                            <E T="03">Chamaecrista lineata</E>
                             var. 
                            <E T="03">keyensis</E>
                             (Big Pine partridge pea) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="515">
                            <GID>EP14OC22.022</GID>
                        </GPH>
                        <P>(7) Unit 2: BPP2—Cudjoe Key, Monroe County, Florida.</P>
                        <P>
                            (i) This unit consists of 83 ac (33 ha). The unit is north of U.S. 1 and extends east from Blimp Avenue to Cutthroat Drive.
                            <PRTPAGE P="62554"/>
                        </P>
                        <P>(ii) Map of Unit 2 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 3 to 
                            <E T="03">Chamaecrista lineata</E>
                             var. 
                            <E T="03">keyensis</E>
                             (Big Pine partridge pea) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="513">
                            <GID>EP14OC22.023</GID>
                        </GPH>
                        <STARS/>
                        <P>
                            Family Linaceae: 
                            <E T="03">Linum arenicola</E>
                             (sand flax)
                        </P>
                        <P>(1) Critical habitat units are depicted for Miami-Dade and Monroe Counties, Florida, on the maps below.</P>
                        <P>
                            (2) Within these areas, the physical or biological features essential to the conservation of 
                            <E T="03">Linum arenicola</E>
                             consist of South Florida pine rockland habitat and adjacent disturbed areas that:
                        </P>
                        <P>
                            (i) Consist of calcareous limestone substrate (often exposed with little soil development) that provides nutritional requirements and suitable growing conditions (
                            <E T="03">e.g.,</E>
                             pH, nutrients, anchoring, and drainage);
                        </P>
                        <P>
                            (ii) Are characterized by an open canopy of 
                            <E T="03">Pinus elliottii</E>
                             var. 
                            <E T="03">densa</E>
                             (South Florida slash pine) and understory with a high proportion of native pine rockland plant species to provide for sufficient sunlight to permit growth and flowering;
                        </P>
                        <P>
                            (iii) Are subjected to a monthly mean temperature characteristic of the subtropical humid classification in Miami-Dade County and tropical humid classification in Monroe County in 
                            <PRTPAGE P="62555"/>
                            every month of the year and short hydroperiods ranging of up to 60 days each year;
                        </P>
                        <P>
                            (iv) Are subjected to periodic natural (
                            <E T="03">e.g.,</E>
                             fire) or nonnatural (
                            <E T="03">e.g.,</E>
                             prescribed fire, mowing) disturbance regimes to maintain open canopy conditions; and
                        </P>
                        <P>(v) Contain the presence of native pollinators for natural pollination and reproduction.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings, aqueducts, runways, roads, and other paved areas) and the land on which they are located existing within the legal boundaries on [EFFECTIVE DATE OF FINAL RULE].</P>
                        <P>
                            (4) Critical habitat map units. Data layers defining map units were created using ESRI ArcGIS mapping software. The projection used was Albers Conical Equal Area (Florida Geographic Data Library), NAD 1983 HARN. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. Shapefiles for the critical habitat units are available to the public at the Service's internet site, 
                            <E T="03">https://www.fws.gov/office/florida-ecological-services/library,</E>
                             and a list of coordinates outlining the units are available at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R4-ES-2022-0116, at 
                            <E T="03">https://www.fws.gov/office/florida-ecological-services/library,</E>
                             and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>
                            (5) Note: Index maps of all critical habitat units for 
                            <E T="03">Linum arenicola</E>
                             (sand flax) follow:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 1 to 
                            <E T="03">Linum arenicola</E>
                             (sand flax) paragraph (5)
                        </FP>
                        <GPH SPAN="3" DEEP="516">
                            <PRTPAGE P="62556"/>
                            <GID>EP14OC22.024</GID>
                        </GPH>
                        <FP SOURCE="FP-1">
                            Figure 2 to 
                            <E T="03">Linum arenicola</E>
                             (sand flax) paragraph (5)
                        </FP>
                        <GPH SPAN="3" DEEP="514">
                            <PRTPAGE P="62557"/>
                            <GID>EP14OC22.025</GID>
                        </GPH>
                        <P>(6) Unit 1: SF1—Big Pine Key, Monroe County, Florida.</P>
                        <P>(i) This unit consists of 1,379 ac (558 ha). The unit begins on northern Big Pine Key on the southern side of Gulf Boulevard, continues south on both sides of Key Deer Boulevard (CR 940) to the vicinity of Osprey Lane on the western side of CR 940 and Tea Lane to the east of CR 940; then resumes on both sides of CR 940 from Osprey Lane to rest south of the vicinity of Driftwood Lane; then resumes south of Osceola Street, between Fern Avenue to the west and Baba Lane to the east; then resumes north of Watson Boulevard in the vicinity of Avenue C; then continues south on both sides of Avenue C to South Street; then resumes on both sides of CR 940 south to U.S. 1 between Ships Way to the west and Sands Street to the east; then resumes south of U.S. 1 from Newfound Boulevard to the west and Deer Run Trail to the east; then resumes south of U.S. 1 from Palomino Horse Trail to the west and Industrial Road to the east.</P>
                        <P>(ii) Map of Unit 1 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 3 to 
                            <E T="03">Linum arenicola</E>
                             (sand flax) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="499">
                            <PRTPAGE P="62558"/>
                            <GID>EP14OC22.026</GID>
                        </GPH>
                        <P>(7) Unit 2: SF2—Upper and Lower Sugarloaf Keys, Monroe County, Florida.</P>
                        <P>(i) This unit consists of 116 ac (47 ha). On Upper Sugarloaf Key, the unit is located north of U.S. 1, extending for approximately 0.5 mi (0.8 km) along both sides of Crane Boulevard, starting approximately 0.8 mi (1.3 km) from the intersection of Crane Road and Rosalind Road. A second area extends south from Pelico Road for approximately 0.2 mi (0.4 km). On Lower Sugarloaf Key, two disturbed roadside areas that support sand flax are along either side of Sugarloaf Boulevard and Square Circle, between Caymen Drive and County Road 939.</P>
                        <P>(ii) Map of Unit 2 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 4 to 
                            <E T="03">Linum arenicola</E>
                             (sand flax) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="517">
                            <PRTPAGE P="62559"/>
                            <GID>EP14OC22.027</GID>
                        </GPH>
                        <P>(8) Unit 3: SF3—Richmond Pinelands and Surrounding Areas, Miami-Dade County, Florida.</P>
                        <P>(i) This unit consists of approximately 987 ac (399 ha). This unit is bordered on the north by SW 152 Street (Coral Reef Drive), on the south by SW 200 St. (Quail Drive/SR 994), on the east by U.S. 1 (South Dixie Highway), and on the west by SW 177 Avenue (Krome Avenue).</P>
                        <P>(ii) Map of Unit 3 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 5 to 
                            <E T="03">Linum arenicola</E>
                             (sand flax) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="516">
                            <PRTPAGE P="62560"/>
                            <GID>EP14OC22.028</GID>
                        </GPH>
                        <P>(9) Unit 4: SF4—Camp Owaissa Bauer and Surrounding Areas, Miami-Dade County, Florida.</P>
                        <P>(i) This unit consists of approximately 315 ac (128 ha). This unit is bordered on the north by SW 248 Street, on the south by SW 312 Street, on the east by SW 112 Avenue, and on the west by SW 217 Avenue.</P>
                        <P>(ii) Map of Unit 4 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 6 to 
                            <E T="03">Linum arenicola</E>
                             (sand flax) paragraph (9)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="520">
                            <PRTPAGE P="62561"/>
                            <GID>EP14OC22.029</GID>
                        </GPH>
                        <P>(10) Unit 5: SF5—Homestead and Surrounding Areas, Miami-Dade County, Florida.</P>
                        <P>(i) This unit consists of approximately 2,292 ac (928 ha). The unit closely follows the Homestead Air Reserve Base property line to the east of SW 137th Avenue and extends north to SW 288th Street, roughly along the Homestead Air Reserve Base boundary. North of SW 288th Street, the unit includes the large undeveloped area extending east from SW 278th Street to 1 mi (1.6 km) west of SW 112th Avenue and bounded to the north by SW 268th Street.</P>
                        <P>(ii) Map of Unit 5 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 7 to 
                            <E T="03">Linum arenicola</E>
                             (sand flax) paragraph (10)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="510">
                            <PRTPAGE P="62562"/>
                            <GID>EP14OC22.030</GID>
                        </GPH>
                        <STARS/>
                    </SECTION>
                    <SIG>
                        <NAME>Martha Williams,</NAME>
                        <TITLE>Director, U.S. Fish and Wildlife Service.</TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 2022-21587 Filed 10-13-22; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 4333-15-C</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>87</VOL>
    <NO>198</NO>
    <DATE>Friday, October 14, 2022</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="62563"/>
            <PARTNO>Part III</PARTNO>
            <AGENCY TYPE="P">Department of the Interior</AGENCY>
            <SUBAGY>Fish and Wildlife Service</SUBAGY>
            <HRULE/>
            <CFR>50 CFR Part 17</CFR>
            <TITLE>
                Endangered and Threatened Wildlife and Plants; Designation of Critical Habitat for 
                <E T="03">Sideroxylon reclinatum</E>
                 ssp. 
                <E T="03">austrofloridense</E>
                 (Everglades bully), 
                <E T="03">Digitaria pauciflora</E>
                 (Florida pineland crabgrass), 
                <E T="03">Chamaesyce deltoidea</E>
                 ssp. 
                <E T="03">pinetorum</E>
                 (pineland sandmat), and 
                <E T="03">Dalea carthagenensis</E>
                 var. 
                <E T="03">floridana</E>
                 (Florida prairie-clover); Proposed Rule
            </TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="62564"/>
                    <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                    <SUBAGY>Fish and Wildlife Service</SUBAGY>
                    <CFR>50 CFR Part 17</CFR>
                    <DEPDOC>[Docket No. FWS-R4-ES-2022-0125; FF09E21000 FXES1111090FEDR 223]</DEPDOC>
                    <RIN>RIN 1018-BE48</RIN>
                    <SUBJECT>
                        Endangered and Threatened Wildlife and Plants; Designation of Critical Habitat for 
                        <E T="0714">Sideroxylon reclinatum</E>
                         ssp. 
                        <E T="0714">austrofloridense</E>
                         (Everglades bully), 
                        <E T="0714">Digitaria pauciflora</E>
                         (Florida pineland crabgrass), 
                        <E T="0714">Chamaesyce deltoidea</E>
                         ssp. 
                        <E T="0714">pinetorum</E>
                         (pineland sandmat), and 
                        <E T="0714">Dalea carthagenensis</E>
                         var. 
                        <E T="0714">floridana</E>
                         (Florida prairie-clover)
                    </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Fish and Wildlife Service, Interior.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Proposed rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>
                            We, the U.S. Fish and Wildlife Service (Service), propose to designate critical habitat for 
                            <E T="03">Sideroxylon reclinatum</E>
                             ssp. 
                            <E T="03">austrofloridense</E>
                             (Everglades bully), 
                            <E T="03">Digitaria pauciflora</E>
                             (Florida pineland crabgrass), 
                            <E T="03">Chamaesyce deltoidea</E>
                             ssp. 
                            <E T="03">pinetorum</E>
                             (pineland sandmat), and 
                            <E T="03">Dalea carthagenensis</E>
                             var. 
                            <E T="03">floridana</E>
                             (Florida prairie-clover) under the Endangered Species Act of 1973 (Act), as amended. In total, approximately 179,680 acres (72,714 hectares) for Everglades bully, 177,879 acres (71,985 hectares) for Florida pineland crabgrass, 8,867 acres (3,588 hectares) for pineland sandmat, and 179,300 acres (72,560 hectares) for Florida prairie-clover in Monroe, Collier, and Miami-Dade Counties, Florida, fall within the boundaries of the proposed critical habitat designations. If we finalize this rule as proposed, it would extend the Act's protections to the species' critical habitats. We also announce the availability of a draft economic analysis (DEA) of the proposed designations of critical habitat for these four plant species.
                        </P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>
                            We will accept comments received or postmarked on or before December 13, 2022. Comments submitted electronically using the Federal eRulemaking Portal (see 
                            <E T="02">ADDRESSES</E>
                            , below) must be received by 11:59 p.m. Eastern time on the closing date. We must receive requests for public hearings, in writing, at the address shown in 
                            <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                             by November 28, 2022.
                        </P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P/>
                        <P>
                            <E T="03">Written comments:</E>
                             You may submit comments by one of the following methods:
                        </P>
                        <P>
                            (1) 
                            <E T="03">Electronically:</E>
                             Go to the Federal eRulemaking Portal: 
                            <E T="03">https://www.regulations.gov.</E>
                             In the Search box, enter FWS-R4-ES-2022-0125, which is the docket number for this rulemaking. Then, click on the Search button. On the resulting page, in the panel on the left side of the screen, under the Document Type heading, check the Proposed Rule box to locate this document. You may submit a comment by clicking on “Comment.”
                        </P>
                        <P>
                            (2) 
                            <E T="03">By hard copy:</E>
                             Submit by U.S. mail or hand-delivery to: Public Comments Processing, Attn: FWS-R4-ES-2022-0125; U.S. Fish and Wildlife Service, MS: PRB/3W, 5275 Leesburg Pike, Falls Church VA 22041-3803.
                        </P>
                        <P>
                            We request that you send comments only by the methods described above. We will post all comments on 
                            <E T="03">https://www.regulations.gov.</E>
                             This generally means that we will post any personal information you provide us (see the Information Requested, below, for more information).
                        </P>
                        <P>
                            <E T="03">Availability of supporting materials:</E>
                             For the proposed critical habitat designations, the coordinates or plot points or both from which the maps are generated are included in the decision file for these critical habitat designations and are available at 
                            <E T="03">https://www.regulations.gov</E>
                             under Docket No. FWS-R4-ES-2022-0125 and on the Service's website at 
                            <E T="03">https://www.fws.gov/office/florida-ecological-services/library.</E>
                             Additional supporting information that we developed for these critical habitat designations will be available on the Service's website, at 
                            <E T="03">https://www.regulations.gov,</E>
                             or both.
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Lourdes Mena, Classification and Recovery Division Manager, U.S. Fish and Wildlife Service, Florida Ecological Services Field Office, 7915 Baymeadows Way, Suite 200, Jacksonville, FL 32256; by telephone 904-731-3134; or by facsimile 904-731-3045. Individuals in the United States who are deaf, deafblind, hard of hearing, or have a speech disability may dial 711 (TTY, TDD, or TeleBraille) to access telecommunications relay services. Individuals outside the United States should use the relay services offered within their country to make international calls to the point-of-contact in the United States.</P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P/>
                    <HD SOURCE="HD1">Executive Summary</HD>
                    <P>
                        <E T="03">Why we need to publish a rule.</E>
                         Under the Act, when we determine that any species is an endangered or threatened species, we must designate critical habitat, to the maximum extent prudent and determinable. Designations and revisions of critical habitat can only be completed by issuing a rule through the Administrative Procedure Act rulemaking process.
                    </P>
                    <P>
                        <E T="03">What this document does.</E>
                         This document proposes to designate critical habitat for one plant species, Florida prairie-clover, that is listed as an endangered species under the Act and for three plant species, Everglades bully, Florida pineland crabgrass, and pineland sandmat that are listed as threatened species under the Act (see listing rule at 82 FR 46691, October 6, 2017).
                    </P>
                    <P>
                        <E T="03">The basis for our action.</E>
                         Section 3(5)(A) of the Act defines critical habitat as (i) the specific areas within the geographical area occupied by the species, at the time it is listed, on which are found those physical or biological features (I) essential to the conservation of the species and (II) which may require special management considerations or protections; and (ii) specific areas outside the geographical area occupied by the species at the time it is listed, upon a determination by the Secretary that such areas are essential for the conservation of the species. Section 4(b)(2) of the Act states that the Secretary must make the designation on the basis of the best scientific and commercial data available and after taking into consideration the economic impact, the impact on national security, and any other relevant impacts of specifying any particular area as critical habitat.
                    </P>
                    <P>
                        <E T="03">Draft economic analysis of the proposed designations of critical habitat.</E>
                         We have prepared an analysis of the probable economic impacts of the proposed critical habitat designations and related factors. In this document, we announce the availability of the draft economic analysis and seek additional public review and comment.
                    </P>
                    <P>
                        <E T="03">Public comment.</E>
                         We are seeking comments and soliciting information from the public on our proposed designations to make sure we consider the best scientific and commercial information available in developing our final designations. Because we will consider all comments and information we receive during the comment period, our final determinations may differ from this proposal. We will respond to substantive comments we receive during the comment period in our final rule.
                    </P>
                    <P>
                        <E T="03">Peer review.</E>
                         In accordance with our joint policy on peer review published in the 
                        <E T="04">Federal Register</E>
                         on July 1, 1994 (59 FR 34270), and our August 22, 2016, memorandum updating and clarifying the role of peer review of determination 
                        <PRTPAGE P="62565"/>
                        under section 4 of the Act, including listing determinations and critical habitat designations, we are seeking comments from independent specialists. The purpose of peer review is to ensure that our critical habitat designations are based on scientifically sound data, assumptions, and analyses. The peer reviewers have expertise in the biology, habitat, and threats to the species addressed in this proposed rule. We have invited these peer reviewers to comment on our specific assumptions and conclusions in this critical habitat proposal during the public comment period for this proposed rule (see 
                        <E T="02">DATES</E>
                        , above).
                    </P>
                    <HD SOURCE="HD1">Information Requested</HD>
                    <P>We intend that any final action resulting from this proposed rule will be based on the best scientific and commercial data available and be as accurate and as effective as possible. Therefore, we request comments or information from other governmental agencies, Native American tribes, the scientific community, industry, or any other interested parties concerning this proposed rule. We particularly seek comments concerning:</P>
                    <P>
                        (1) The reasons why we should or should not designate habitat as “critical habitat” under section 4 of the Act (16 U.S.C. 1531 
                        <E T="03">et seq.</E>
                        ), including information regarding the following factors that the regulations identify as reasons why designation of critical habitat may be not prudent:
                    </P>
                    <P>(a) The species is threatened by taking or other human activity and identification of critical habitat can be expected to increase the degree of such threat to the species; or</P>
                    <P>(b) Such designation of critical habitat would not be beneficial to the species. In determining whether a designation would not be beneficial, the factors the Services may consider include but are not limited to: Whether the present or threatened destruction, modification, or curtailment of a species' habitat or range is not a threat to the species, or whether any areas meet the definition of “critical habitat.”</P>
                    <P>(2) Specific information on:</P>
                    <P>(a) The amount and distribution of Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover habitat;</P>
                    <P>
                        (b) Any additional areas occurring within the range of the species, 
                        <E T="03">i.e.,</E>
                         south and central Florida, that should be included in the designations because they (i) are occupied at the time of listing and contain the physical or biological features that are essential to the conservation of the species and that may require special management considerations, or (ii) are unoccupied at the time of listing and are essential for the conservation of the species because they have potential to successfully support introduced or reintroduced populations of these species;
                    </P>
                    <P>(c) Special management considerations or protection that may be needed in critical habitat areas we are proposing, including managing for the potential effects of climate change; and</P>
                    <P>(d) Whether we have appropriately identified the physical or biological features that are essential to the conservation for each species.</P>
                    <P>(3) Land use designations and current or planned activities in the subject areas and their possible impacts on proposed critical habitat.</P>
                    <P>(4) Information on the projected and reasonably likely impacts of climate change on Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover and proposed critical habitat.</P>
                    <P>(5) Information on the extent to which the description of probable economic impacts in the draft economic analysis is a reasonable estimate of the likely economic impacts and any additional information regarding probable economic impacts that we should consider.</P>
                    <P>(6) Any probable economic, national security, or other relevant impacts of designating any area that may be included in the final designations, and the related benefits of including or excluding specific areas.</P>
                    <P>(7) Whether any specific areas we are proposing for critical habitat designation should be considered for exclusion under section 4(b)(2) of the Act, and whether the benefits of potentially excluding any specific area outweigh the benefits of including that area under section 4(b)(2) of the Act. If you think we should exclude any additional areas, please provide information supporting a benefit of exclusion.</P>
                    <P>(8) Whether we could improve or modify our approach to designating critical habitat in any way to provide for greater public participation and understanding, or to better accommodate public concerns and comments.</P>
                    <P>Please include sufficient information with your submission (such as scientific journal articles or other publications) to allow us to verify any scientific or commercial information you include.</P>
                    <P>Please note that submissions merely stating support for, or opposition to, the action under consideration without providing supporting information, although noted, will not be considered in making a final critical habitat determination. Section 4(b)(2) of the Act directs that the Secretary shall designate critical habitat on the basis of the best scientific data available.</P>
                    <P>
                        You may submit your comments and materials concerning this proposed rule by one of the methods listed in 
                        <E T="02">ADDRESSES</E>
                        . We request that you send comments only by the methods described in 
                        <E T="02">ADDRESSES</E>
                        .
                    </P>
                    <P>
                        If you submit information via 
                        <E T="03">https://www.regulations.gov,</E>
                         your entire submission—including any personal identifying information—will be posted on the website. If your submission is made via a hardcopy that includes personal identifying information, you may request at the top of your document that we withhold this information from public review. However, we cannot guarantee that we will be able to do so. We will post all hardcopy submissions on 
                        <E T="03">https://www.regulations.gov.</E>
                    </P>
                    <P>
                        Comments and materials we receive, as well as supporting documentation we used in preparing this proposed rule, will be available for public inspection on 
                        <E T="03">https://www.regulations.gov.</E>
                    </P>
                    <P>Because we will consider all comments and information we receive during the comment period, our final designations may differ from this proposal. Based on the new information we receive (and any comments on that new information), our final designations may not include all areas proposed, may include some additional areas that meet the definition of critical habitat, or may exclude some areas if we find the benefits of exclusion outweigh the benefits of inclusion.</P>
                    <HD SOURCE="HD2">Public Hearing</HD>
                    <P>
                        Section 4(b)(5) of the Act provides for a public hearing on this proposal, if requested. Requests must be received by the date specified in 
                        <E T="02">DATES</E>
                        . Such requests must be sent to the address shown in 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        . We will schedule a public hearing on this proposal, if requested, and announce the date, time, and place of the hearing, as well as how to obtain reasonable accommodations, in the 
                        <E T="04">Federal Register</E>
                         and local newspapers at least 15 days before the hearing. We may hold the public hearing in person or virtually via webinar. We will announce any public hearing on our website, in addition to the 
                        <E T="04">Federal Register</E>
                        . The use of virtual public hearings is consistent with our regulations at 50 CFR 424.16(c)(3).
                    </P>
                    <HD SOURCE="HD1">Previous Federal Actions</HD>
                    <P>
                        On October 11, 2016, we proposed to list Florida prairie-clover as an endangered species and Everglades bully, Florida pineland crabgrass, and 
                        <PRTPAGE P="62566"/>
                        pineland sandmat as threatened species under the Act (81 FR 70282). On October 6, 2017, we published our final determination in the 
                        <E T="04">Federal Register</E>
                         (82 FR 46691) and added Florida prairie-clover as an endangered species and Everglades bully, Florida pineland crabgrass, and pineland sandmat as threatened species to the List of Endangered and Threatened Plants at 50 CFR 17.12(h). At the time of our proposal, we determined that critical habitat was prudent, but not determinable, because we lacked specific information on the impacts of our designation. In our final listing rule (82 FR 46691; October 6, 2017), we stated we were in the process of obtaining information on the impacts of the designation. All previous Federal actions for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover are outlined in our proposed listing rule for the four plant species (81 FR 70282; October 11, 2016).
                    </P>
                    <P>It is our intent to discuss in this proposed rule only those topics directly relevant to the designation of critical habitat for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover. For more information on the taxonomy, life history, habitat, population descriptions, and factors affecting the species for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover, please refer to the October 11, 2016, proposed listing rule (81 FR 70282) and the October 6, 2017, final listing rule (82 FR 46691) for these species.</P>
                    <HD SOURCE="HD1">Background</HD>
                    <P>Section 4 of the Act (16 U.S.C. 1533) and the implementing regulations in title 50 of the Code of Federal Regulations set forth the procedures for determining whether a species is an endangered species or a threatened species, issuing protective regulations for threatened species, and designating critical habitat for threatened and endangered species. In 2019, jointly with the National Marine Fisheries Service, the Service issued final rules that revised the regulations in 50 CFR parts 17 and 424 regarding how we add, remove, and reclassify threatened and endangered species and the criteria for designating listed species' critical habitat (84 FR 45020 and 84 FR 44752; August 27, 2019).</P>
                    <P>
                        However, on July 5, 2022, the U.S. District Court for the Northern District of California vacated the 2019 regulations (
                        <E T="03">Center for Biological Diversity</E>
                         v. 
                        <E T="03">Haaland,</E>
                         No. 4:19-cv-05206-JST, Doc. 168 (N.D. Cal. July 5, 2022) (
                        <E T="03">CBD</E>
                         v. 
                        <E T="03">Haaland</E>
                        )), reinstating the regulations that were in effect before the effective date of the 2019 regulations as the law governing species classification and critical habitat decisions. Accordingly, in developing the analysis contained in this proposal, we applied the pre-2019 regulations, which may be reviewed in the 2018 edition of the Code of Federal Regulations at 424.02 and 424.12(a)(1) and (b)(2)). Because of the ongoing litigation regarding the court's vacatur of the 2019 regulations, and the resulting uncertainty surrounding the legal status of the regulations, we also undertook an analysis of whether the proposal would be different if we were to apply the 2019 regulations. That analysis, which we described in a separate memo in the decisional file and posted on 
                        <E T="03">https://www.regulations.gov,</E>
                         concluded that we would have reached the same proposal if we had applied the 2019 regulations because under either regulatory scheme we find that critical habitat is prudent for the four plant species and that the occupied areas proposed for critical habitat are adequate to ensure the conservation of the species. The amount and distribution of critical habitat we are proposing for designation in occupied areas would allow existing and future established populations of Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover to maintain their existing distributions; expand their distributions into suitable nearby areas (needed to offset habitat loss and fragmentation); increase the size of each population to a level where the threats of genetic, demographic, and normal environmental uncertainties are diminished; and maintain their ability to withstand local or unit-level environmental fluctuations or catastrophic events. Accordingly, we have not identified unoccupied areas that are essential for the conservation of the species at this time.
                    </P>
                    <P>
                        On September 21, 2022, the U.S. Circuit Court of Appeals for the Ninth Circuit stayed the district court's July 5, 2022, order vacating the 2019 regulations until a pending motion for reconsideration before the district court is resolved (
                        <E T="03">In re: Cattlemen's Ass'n,</E>
                         No. 22-70194). The effect of the stay is that the 2019 regulations are currently the governing law. Because a court order requires us to submit this proposal to the 
                        <E T="04">Federal Register</E>
                         by September 30, 2022, it is not feasible for us to revise the proposal in response to the Ninth Circuit's decision. Instead, we hereby adopt the analysis in the separate memo that applied the 2019 regulations as our primary justification for the proposal. However, due to the continued uncertainty resulting from the ongoing litigation, we also retain the analysis in this preamble that applies the pre-2019 regulations and we conclude that, for the reasons stated in our separate memo analyzing the 2019 regulations, this proposal would have been the same if we had applied the 2019 regulations.
                    </P>
                    <P>Critical habitat is defined in section 3 of the Act as:</P>
                    <P>(1) The specific areas within the geographical area occupied by the species, at the time it is listed in accordance with the Act, on which are found those physical or biological features</P>
                    <P>(a) Essential to the conservation of the species, and</P>
                    <P>(b) Which may require special management considerations or protection; and</P>
                    <P>(2) Specific areas outside the geographical area occupied by the species at the time it is listed, upon a determination that such areas are essential for the conservation of the species.</P>
                    <P>
                        Our regulations at 50 CFR 424.02 define the geographical area occupied by the species as an area that may generally be delineated around species' occurrences, as determined by the Secretary (
                        <E T="03">i.e.,</E>
                         range). Such areas may include those areas used throughout all or part of the species' life cycle, even if not used on a regular basis (
                        <E T="03">e.g.,</E>
                         migratory corridors, seasonal habitats, and habitats used periodically, but not solely by vagrant individuals).
                    </P>
                    <P>Conservation, as defined under section 3 of the Act, means to use and the use of all methods and procedures that are necessary to bring an endangered or threatened species to the point at which the measures provided pursuant to the Act are no longer necessary. Such methods and procedures include, but are not limited to, all activities associated with scientific resources management such as research, census, law enforcement, habitat acquisition and maintenance, propagation, live trapping, and transplantation, and, in the extraordinary case where population pressures within a given ecosystem cannot be otherwise relieved, may include regulated taking.</P>
                    <P>
                        Critical habitat receives protection under section 7 of the Act through the requirement that Federal agencies ensure, in consultation with the Service, that any action they authorize, fund, or carry out is not likely to result in the destruction or adverse modification of critical habitat. The designation of critical habitat does not affect land 
                        <PRTPAGE P="62567"/>
                        ownership or establish a refuge, wilderness, reserve, preserve, or other conservation area. Such designation also does not allow the government or public to access private lands. Such designation does not require implementation of restoration, recovery, or enhancement measures by non-Federal landowners. Where a landowner requests Federal agency funding or authorization for an action that may affect a listed species or critical habitat, the Federal agency would be required to consult with the Service under section 7(a)(2) of the Act. However, even if the Service were to conclude that the proposed activity would likely result in destruction or adverse modification of the critical habitat, the Federal action agency and the landowner are not required to abandon the proposed activity, or to restore or recover the species; instead, they must implement “reasonable and prudent alternatives” to avoid destruction or adverse modification of critical habitat.
                    </P>
                    <P>Under the first prong of the Act's definition of critical habitat, areas within the geographical area occupied by the species at the time it was listed are included in a critical habitat designation if they contain physical or biological features (1) which are essential to the conservation of the species and (2) which may require special management considerations or protection. For these areas, critical habitat designations identify, to the extent known using the best scientific data available, those physical or biological features that are essential to the conservation of the species (such as space, food, cover, and protected habitat).</P>
                    <P>Under the second prong of the Act's definition of critical habitat, we can designate critical habitat in areas outside the geographical area occupied by the species at the time it is listed, upon a determination that such areas are essential for the conservation of the species.</P>
                    <P>
                        Section 4 of the Act requires that we designate critical habitat on the basis of the best scientific data available. Further, our Policy on Information Standards Under the Endangered Species Act (published in the 
                        <E T="04">Federal Register</E>
                         on July 1, 1994 (59 FR 34271)), the Information Quality Act (section 515 of the Treasury and General Government Appropriations Act for Fiscal Year 2001 (Pub. L. 106-554; H.R. 5658)), and our associated Information Quality Guidelines provide criteria, establish procedures, and provide guidance to ensure that our decisions are based on the best scientific data available. They require our biologists, to the extent consistent with the Act and with the use of the best scientific data available, to use primary and original sources of information as the basis for recommendations to designate critical habitat.
                    </P>
                    <P>When we are determining which areas should be designated as critical habitat, our primary source of information is generally the information from the listing rules and information developed during the listing process for the species. Additional information sources may include any generalized conservation strategy, criteria, or outline that may have been developed for the species; articles in peer-reviewed journals; conservation plans developed by States and counties; scientific status surveys and studies; biological assessments; other unpublished materials; or experts' opinions or personal knowledge.</P>
                    <P>Habitat is dynamic, and species may move from one area to another over time. We recognize that critical habitat designated at a particular point in time may not include all of the habitat areas that we may later determine are necessary for the recovery of the species. For these reasons, a critical habitat designation does not signal that habitat outside the designated area is unimportant or may not be needed for recovery of the species. Areas that are important to the conservation of the species, both inside and outside the critical habitat designation, will continue to be subject to: (1) Conservation actions implemented under section 7(a)(1) of the Act; (2) regulatory protections afforded by the requirement in section 7(a)(2) of the Act for Federal agencies to ensure their actions are not likely to jeopardize the continued existence of any endangered or threatened species; and (3) the prohibitions found in section 9 of the Act. Federally funded or permitted projects affecting listed species outside their designated critical habitat areas may still result in jeopardy findings in some cases. These protections and conservation tools will continue to contribute to recovery of the species. Similarly, critical habitat designations made on the basis of the best available information at the time of designation will not control the direction and substance of future recovery plans, habitat conservation plans (HCPs), or other species conservation planning efforts if new information available at the time of those planning efforts calls for a different outcome.</P>
                    <HD SOURCE="HD1">Prudency Determination</HD>
                    <P>Section 4(a)(3) of the Act, as amended, and implementing regulations (50 CFR 424.12) require that, to the maximum extent prudent and determinable, the Secretary shall designate critical habitat at the time the species is determined to be an endangered or threatened species. Our regulations (50 CFR 424.12(a)(1)) currently in effect state that a designation of critical habitat is not prudent when one or both of the following situations exist:</P>
                    <P>(i) The species is threatened by taking or other human activity and identification of critical habitat can be expected to increase the degree of such threat to the species; or</P>
                    <P>(ii) Such designation of critical habitat would not be beneficial to the species. In determining whether a designation would not be beneficial, the factors the Services may consider include, but are not limited to: Whether the present or threatened destruction, modification, or curtailment of a species' habitat or range is not a threat to the species, or whether any areas meet the definition of “critical habitat.”</P>
                    <P>No imminent threat of take attributed to collection or vandalism was identified under Factor B for these species in the final listing rule (82 FR 46691; October 6, 2017), nor has such a threat been identified since, and identification and mapping of critical habitat is not expected to initiate or increase the degree of any such threat. In our listing determination for these species, we determined that the present or threatened destruction, modification, or curtailment of habitat or range is a threat to these species. Therefore, because none of the circumstances enumerated in our regulations at 50 CFR 424.12(a)(1) has been met, we have determined that the designation of critical habitat is prudent for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover.</P>
                    <HD SOURCE="HD1">Critical Habitat Determinability</HD>
                    <P>Having determined that designation of critical habitat is prudent for each species, under section 4(a)(3) of the Act we must find whether critical habitat for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover is determinable. Our regulations at 50 CFR 424.12(a)(2) state that critical habitat is not determinable when one or both of the following situations exist:</P>
                    <P>(i) Data sufficient to perform required analyses are lacking, or</P>
                    <P>
                        (ii) The biological needs of the species are not sufficiently well known to identify any area that meets the definition of “critical habitat.”
                        <PRTPAGE P="62568"/>
                    </P>
                    <P>When critical habitat is not determinable, the Act allows the Service an additional year to publish a critical habitat designation (16 U.S.C. 1533(b)(6)(C)(ii)).</P>
                    <P>At the time of our proposal, we determined that critical habitat was prudent, but not determinable because we lacked specific information on the impacts of our designation (81 FR 70282; October 11, 2016). In our final listing rule, we stated we were in the process of obtaining information on the impacts of the designation (82 FR 46691; October 6, 2017). We reviewed the available information pertaining to the biological needs of the species and habitat characteristics where these species are located. At this time, we are proposing to designate critical habitat, to the maximum extent prudent, for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover.</P>
                    <HD SOURCE="HD1">Physical or Biological Features</HD>
                    <P>In accordance with section 3(5)(A)(i) of the Act and regulations at 50 CFR 424.12(b), in determining which areas we will designate as critical habitat from within the geographical area occupied by the species at the time of listing, we consider the physical or biological features that are essential to the conservation of the species and which may require special management considerations or protection. Following vacatur of the 2019 regulations, our regulations now in effect at 50 CFR 424.02 define “physical or biological features” as the features that support the life-history needs of the species, including, but not limited to, water characteristics, soil type, geological features, sites, prey, vegetation, symbiotic species, or other features. A feature may be a single habitat characteristic or a more complex combination of habitat characteristics. Features may include habitat characteristics that support ephemeral or dynamic habitat conditions. Features may also be expressed in terms relating to principles of conservation biology, such as patch size, distribution distances, and connectivity. For example, physical features essential to the conservation of the species might include gravel of a particular size required for spawning, alkaline soil for seed germination, protective cover for migration, or susceptibility to flooding or fire that maintains necessary early-successional habitat characteristics. Biological features might include prey species, forage grasses, specific kinds or ages of trees for roosting or nesting, symbiotic fungi, or absence of a particular level of nonnative species consistent with conservation needs of the listed species. The features may also be combinations of habitat characteristics and may encompass the relationship between characteristics or the necessary amount of a characteristic essential features to support the life history of the species.</P>
                    <P>In considering whether features are essential to the conservation of the species, the Service may consider an appropriate quality, quantity, and spatial and temporal arrangement of habitat characteristics in the context of the life-history needs, condition, and status of the species. These characteristics include, but are not limited to, space for individual and population growth and for normal behavior; food, water, air, light, minerals, or other nutritional or physiological requirements; cover or shelter; sites for breeding, reproduction, or rearing (or development) of offspring; and habitats that are protected from disturbance.</P>
                    <P>We derive the specific physical or biological features essential to Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover from studies of these plants' habitat, ecology, and life history as described below. Additional information can be found in the October 11, 2016, proposed listing rule (81 FR 70282) and October 6, 2017, final listing rule (82 FR 46691) for these species. We have determined that the following physical or biological features are essential to the conservation of Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie.</P>
                    <HD SOURCE="HD2">Everglades Bully, Florida Pineland Crabgrass, and Pineland Sandmat</HD>
                    <HD SOURCE="HD3">Space for Individual and Population Growth and for Normal Behavior</HD>
                    <P>
                        <E T="03">Plant Community and Competitive Ability</E>
                        —Everglades bully and Florida pineland crabgrass occur in pine rockland and marl prairies, as well as the ecotone between these habitats in Collier, Miami-Dade, and Monroe Counties (Gann et al. 2006, p. 12; Bradley et al. 2013, p. 4; Gann 2015, p. 30; Maschinski et al. 2002, p. 79), whereas pineland sandmat occurs only in communities classified as pine rockland habitat in Miami-Dade and Monroe Counties (Bradley and Gann 1999, p. 24). Detailed descriptions of these communities and their associated native plant species for Everglades bully, Florida pineland crabgrass, and pineland sandmat are provided under Background in the October 11, 2016, proposed listing rule (81 FR 70282) and under Summary of Biological Status and Threats in the October 6, 2017, final listing rule (82 FR 46691). These habitats and their associated plant communities provide vegetation structure that allows for adequate growing space, moisture, sunlight, pollinators, and a competitive regime that is required for Everglades bully, Florida pineland crabgrass, and pineland sandmat to persist and spread. Pine rocklands and marl prairies are fire-maintained ecosystems characterized by an open canopy and understory and a limestone substrate (often exposed). Open canopy conditions are required to allow sufficient sunlight to reach the herbaceous layer and permit growth and flowering of Everglades bully, Florida pineland crabgrass, and pineland sandmat (Ross and Ruiz 1996, pp. 5-6; Bradley and Saha 2009, p. 4). These species also require a calcareous limestone substrate that varies from nearly bare to thin layers or small pockets of shallow soil to provide suitable growing conditions (
                        <E T="03">e.g.,</E>
                         pH, nutrients, anchoring, and proper drainage). As a result of these marginal soil conditions, plants such as Everglades bully, Florida pineland crabgrass, and pineland sandmat rely on sparse competition and periodic disturbance to thrive and persist. This combination of ecosystem characteristics (
                        <E T="03">i.e.,</E>
                         open canopy with a partially exposed limestone substrate and periodic disturbance) occurs only in pine rockland habitats (as opposed to rockland hammock, which occurs in conjunction with pine rockland and has a limestone substrate but a closed canopy) and marl prairie habitats.
                    </P>
                    <P>
                        In Miami-Dade County, development and agriculture have reduced pine rockland habitat by 90 percent in mainland south Florida. Recent vegetation mapping in Everglades National Park (ENP) indicates there are a total of 14,211 acres (ac) (5,751 hectares (ha)) of pine rocklands remaining in ENP, which includes the largest remaining area of pine rockland (approximately 10,895 ac (4,409 ha)) in Florida (Long Pine Key) (Ruiz et al. 2022). Outside of ENP, pine rockland habitat decreased from approximately 185,329 ac (75,000 ha) in the early 1900s to only 3,707 ac (1,500 ha) in 2014 (Possley et al. 2014, p. 154) and 2,275 ac (921 ha) in 2019 (USGS 2019, p. 28), leaving only about 1.2 percent of the pine rocklands on the Miami Rock Ridge remaining. Further, much of what is left are small remnants scattered throughout the Miami metropolitan area, isolated from other natural areas 
                        <PRTPAGE P="62569"/>
                        (Herndon 1998, p. 1). The extreme rarity of high-quality pine rockland habitat supporting Everglades bully, Florida pineland crabgrass, and pineland sandmat and marl prairie habitat supporting Everglades bully and Florida pineland crabgrass elevates the importance of disturbed remnant sites that still retain some pine rockland species.
                    </P>
                    <P>We consider pine rockland and adjacent ecotonal areas to be primary habitat for Everglades bully, Florida pineland crabgrass, and pineland sandmat. Similarly, we also consider marl prairie and adjacent ecotonal areas to be primary habitat for Everglades bully and Florida pineland crabgrass. Therefore, based on the information above, we identify upland habitats consisting of pine rocklands and adjacent ecotonal areas to be a physical or biological feature essential to the conservation of Everglades bully, Florida pineland crabgrass, and pineland sandmat. Additionally, we identify upland habitats consisting of marl prairie and adjacent ecotonal areas to be a physical or biological feature essential to the conservation of Everglades bully and Florida pineland crabgrass.</P>
                    <HD SOURCE="HD3">Food, Water, Air, Light, Minerals, or Other Nutritional or Physiological Requirements</HD>
                    <P>
                        <E T="03">Climate (Temperature and Precipitation)</E>
                        —Everglades bully, Florida pineland crabgrass, and pineland sandmat require adequate rainfall and do not tolerate prolonged freezing temperatures. The climate of south Florida where Everglades bully, Florida pineland crabgrass, and pineland sandmat occur is characterized by distinct wet and dry seasons, a monthly mean temperature above 64.4 degrees (°) Fahrenheit (F) (18 °Celsius (C)) in every month of the year, and annual rainfall averaging 30 to 60 inches (in) (75 to 150 centimeters (cm)) (Gabler et al. 1994, p. 211). Areas of pine rockland that are adjacent to wetlands may experience prolonged flooded periods lasting up to 60 days, while those at higher elevation have shorter or no annual flooding period (Florida Natural Areas Inventory (FNAI) 2010, p. 2). Freezes can occur in the winter months but are very infrequent at this latitude in Florida. Therefore, based on the information above, we determined a subtropical humid climate (Miami-Dade County) or tropical humid climate (Collier and Monroe Counties) to be an essential physical feature for Everglades bully, Florida pineland crabgrass, and pineland sandmat.
                    </P>
                    <P>
                        <E T="03">Soils</E>
                        —Substrates supporting Everglades bully, Florida pineland crabgrass, and pineland sandmat are composed of oolitic limestone that is at or very near the surface (Kernan and Bradley 1996, p. 2). Solution holes occasionally form where the surface limestone is dissolved by organic acids. There is typically very little soil development, consisting primarily of accumulations of low-nutrient sand, marl, clayey loam, and organic debris found in solution holes, depressions, and crevices on the limestone surface (FNAI 2010, p. 62). However, these species can be found at the northern end of the Miami Rock Ridge, where the substrate includes extensive sandy pockets, beginning from approximately North Miami Beach and extending south to approximately SW 216 Street (which runs east-west approximately one-half mile south of Quail's Roost Pineland) (Service 1999, p. 3-162).
                    </P>
                    <P>
                        These substrates provide anchoring, nutrients, moisture regime, and suitable soil chemistry for Everglades bully, Florida pineland crabgrass, and pineland sandmat; they facilitate a community of associated plant species that creates competition, which allows these species to persist and spread. Therefore, based on the information above, we identify substrates derived from calcareous limestone (often exposed with little soil development) that provide nutritional requirements and suitable growing conditions (
                        <E T="03">e.g.,</E>
                         pH, nutrients, anchoring, and drainage) to be an essential physical feature for Everglades bully, Florida pineland crabgrass, and pineland sandmat.
                    </P>
                    <P>
                        <E T="03">Hydrology</E>
                        —Pine rocklands occur on relatively flat, moderately to well drained terrain from 6 to 21 feet (ft) (2 to 7 meters (m)) above sea level. Drainage varies according to the porosity of the limestone substrate but is generally rapid. Consequently, most sites are wet for only short periods following heavy rains. During the rainy season, however, some sites may be shallowly inundated by slow-flowing surface water for up to 60 days each year (hydroperiods) (FNAI 2010, p. 62). Marl prairies also are dependent on short hydroperiods (up to 60 days). Longer hydroperiods favor the development of peat and the dominance of sawgrass while shorter hydroperiods permit the invasion of woody species (FNAI 2010, p. 108). Therefore, based on the information above, we identify pine rockland habitat with short hydroperiods (up to 60 days) to be an essential feature for Everglades bully, Florida pineland crabgrass, and pineland sandmat. Additionally, we identify marl prairie habitat with short hydroperiods (up to 60 days) to be an essential habitat feature for Everglades bully and Florida pineland crabgrass.
                    </P>
                    <HD SOURCE="HD3">Cover or Shelter</HD>
                    <P>
                        Everglades bully, Florida pineland crabgrass, and pineland sandmat occur in open to semi-open canopy habitats. Pine rockland is characterized by an open canopy of 
                        <E T="03">Pinus elliottii</E>
                         var. 
                        <E T="03">densa</E>
                         (South Florida slash pine), with a limited subcanopy (Snyder et al. 1990, p. 253). Marl prairie is characterized by a sparsely vegetated, grass-dominated community. Although the vegetative community is diverse, most marl prairie plant species contribute little cover, and over 90 percent of the cover is contributed by only two or three dominant species in any given area (FNAI 2010, p. 108). The spatial and temporal distribution of open canopy areas varies in these habitats based on time since the last disturbance, such as fire, caused canopy openings.
                    </P>
                    <P>An open canopy and understory are required to allow sufficient sunlight to reach the herbaceous layer and permit growth and flowering of Everglades bully, Florida pineland crabgrass, and pineland sandmat. Therefore, based on the information above, we identify vegetation composition and structure characterized by an open to semi-open canopy that allows for sufficient sunlight and space for individual growth and population expansion to be an essential feature for Everglades bully, Florida pineland crabgrass, and pineland sandmat.</P>
                    <HD SOURCE="HD3">Sites for Breeding, Reproduction, or Rearing (or Development) of Offspring</HD>
                    <P>Little is known about the life history of Everglades bully, Florida pineland crabgrass, and pineland sandmat, including pollination biology, seed production, or dispersal. Reproduction is sexual, with new plants generated from seeds. Therefore, insect pollination is likely important to these species' reproduction, and declines in pollinator visitation may cause decreased seed or fruit production of Everglades bully, Florida pineland crabgrass, and pineland sandmat, which could lead to lower seedling establishment and numbers of mature plants.</P>
                    <P>
                        The pine rocklands, marl prairies, and adjacent ecotonal habitats identified above as essential features provide a plant community with associated plant species that foster a competitive regime suitable to Everglades bully, Florida pineland crabgrass, and pineland sandmat and contain adequate open space for the recruitment of new plants. Associated plant species in these habitats attract and provide cover for 
                        <PRTPAGE P="62570"/>
                        insect pollinators required for Everglades bully, Florida pineland crabgrass, and pineland sandmat pollination (for more information, see Background in the October 11, 2016, proposed listing rule (81 FR 70282) and Summary of Biological Status and Threats in the October 6, 2017, final listing rule (82 FR 46691)).
                    </P>
                    <P>Therefore, based on the information above, we identify pine rockland and adjacent ecotonal areas containing the presence of native pollinators for natural pollination and reproduction to be an essential feature for Everglades bully, Florida pineland crabgrass, and pineland sandmat. Additionally, we identify marl prairie and adjacent ecotonal areas containing the presence of native pollinators for natural pollination and reproduction to be an essential feature for Everglades bully and Florida pineland crabgrass.</P>
                    <HD SOURCE="HD3">Habitats Representative of the Historical, Geographic, and Ecological Distributions of the Species</HD>
                    <P>Everglades bully, Florida pineland crabgrass, and pineland sandmat continue to occur in habitats that are protected from incompatible human disturbance, which are habitats representative of the species' historical, geographical, and ecological distributions, although their ranges have been reduced. These species are still found in pine rocklands, and, in addition, Everglades bully and Florida pineland crabgrass are still found in marl prairies, along with the ecotonal regions between these two habitat types. As described above, these habitats provide a community of associated plant and animal species that are compatible with Everglades bully, Florida pineland crabgrass, and pineland sandmat. In addition, these habitats provide the vegetation structure that provides adequate sunlight levels and open space for plant growth and regeneration, and substrates with adequate moisture availability and suitable soil chemistry needed for these species. Representative communities are located on Federal, State, local, and private conservation lands that implement conservation measures benefitting the species.</P>
                    <P>
                        <E T="03">Disturbance Regime</E>
                        —Pine rockland and marl prairie habitats that could or currently support Everglades bully, Florida pineland crabgrass, and pineland sandmat depend on natural disturbance regimes from hurricanes or fires to open the canopy in order to provide light levels sufficient to support the species. The historical frequency and magnitude of hurricanes and fire have allowed for the persistence of Everglades bully, Florida pineland crabgrass, and pineland sandmat by occasionally creating areas of open canopy. In the absence of disturbance, these habitats may have closed canopies, resulting in areas lacking enough available sunlight to support Everglades bully, Florida pineland crabgrass, and pineland sandmat. Most of these areas can be restored if habitats are managed with a combination of mechanical hardwood removal and prescribed fire. We consider wildfire to be the natural disturbance factor for pine rocklands, marl prairies, and adjacent ecotonal areas. Therefore, we identify habitats that are subjected to periodic natural (
                        <E T="03">e.g.,</E>
                         hurricanes, fire) or unnatural (
                        <E T="03">e.g.,</E>
                         prescribed fire) disturbance regimes to maintain open canopy conditions in pine rocklands, marl prairies, and adjacent ecotonal areas as essential habitat features for Everglades bully, Florida pineland crabgrass, and pineland sandmat.
                    </P>
                    <HD SOURCE="HD3">Summary of Physical or Biological Features Essential to the Conservation of Everglades Bully, Florida Pineland Crabgrass, and Pineland Sandmat</HD>
                    <P>Based on the best available science related to the life history and ecology of these species, as outlined in the discussion above, we have determined that the following physical or biological features are essential to the conservation of Everglades bully and Florida pineland crabgrass:</P>
                    <P>South Florida pine rockland, marl prairie, and adjacent ecotonal areas:</P>
                    <P>
                        (1) Consisting of calcareous limestone substrate (often exposed with little soil development) that provides nutritional requirements and suitable growing conditions (
                        <E T="03">e.g.,</E>
                         pH, nutrients, anchoring, and drainage);
                    </P>
                    <P>(2) Characterized by an open to semi-open canopy and understory with a high proportion of native plant species to provide for sufficient sunlight to permit growth and flowering;</P>
                    <P>(3) Subjected to a monthly mean temperature characteristic of the subtropical humid classification in Miami-Dade County or the tropical humid classification in Collier and Monroe Counties and short hydroperiods ranging up to 60 days each year;</P>
                    <P>
                        (4) Subjected to periodic natural (
                        <E T="03">e.g.,</E>
                         hurricanes, fire) or unnatural (
                        <E T="03">e.g.,</E>
                         prescribed fire) disturbance regimes to maintain open canopy conditions; and
                    </P>
                    <P>(5) Containing the presence of native pollinators for natural pollination and reproduction.</P>
                    <P>Based on the best available science related to the life history and ecology of the species, as outlined in the discussion above, we have determined that the following physical or biological features are essential to the conservation of pineland sandmat:</P>
                    <P>South Florida pine rockland and adjacent ecotonal areas:</P>
                    <P>
                        (1) Consisting of calcareous limestone substrate (often exposed with little soil development) that provides nutritional requirements and suitable growing conditions (
                        <E T="03">e.g.,</E>
                         pH, nutrients, anchoring, and drainage);
                    </P>
                    <P>(2) Characterized by an open canopy and understory with a high proportion of native pine rockland plant species to provide for sufficient sunlight to permit growth and flowering;</P>
                    <P>(3) Subjected to a monthly mean temperature characteristic of the subtropical humid classification in Miami-Dade County and short hydroperiods ranging up to 60 days each year;</P>
                    <P>
                        (4) Subjected to periodic natural (
                        <E T="03">e.g.,</E>
                         hurricanes, fire) or unnatural (
                        <E T="03">e.g.,</E>
                         prescribed fire) disturbance regimes to maintain open canopy conditions; and
                    </P>
                    <P>(5) Containing the presence of native pollinators for natural pollination and reproduction.</P>
                    <HD SOURCE="HD2">Florida Prairie-Clover</HD>
                    <HD SOURCE="HD3">Space for Individual and Population Growth and for Normal Behavior</HD>
                    <P>
                        <E T="03">Plant Community and Competitive Ability</E>
                        —Florida prairie-clover occurs in Collier, Miami-Dade, and Monroe Counties in communities classified as pine rockland, marl prairie, rockland hammock, and coastal berm, in addition to disturbed sites adjacent to these habitats, such as roadsides and mowed areas still dominated by native species (Bradley and Gann 1999, p. 3; Gann 2015, p. 26). These communities and their associated native plant species are described in the October 11, 2016, proposed listing rule (81 FR 70282) and the October 6, 2017, final listing rule (82 FR 46691). These habitats and their associated plant communities provide vegetation structure that allows for adequate growing space, moisture, sunlight, pollinators, and a competitive regime that is required for Florida prairie-clover to persist and spread. The plant also requires a calcareous limestone substrate that varies from nearly bare to thin layers or small pockets of shallow soil to provide suitable growing conditions (
                        <E T="03">e.g.,</E>
                         pH, nutrients, anchoring, and proper drainage). As a result of these marginal soil conditions, plants such as Florida prairie-clover rely on sparse competition and periodic disturbance to thrive and persist.
                    </P>
                    <P>
                        As discussed above for Everglades bully, Florida pineland crabgrass, and 
                        <PRTPAGE P="62571"/>
                        pineland sandmat, pine rocklands and marl prairies are fire-maintained ecosystems characterized by an open canopy and understory and a limestone substrate (often exposed). Rockland hammock is a species-rich tropical hardwood forest on upland sites in areas where limestone is very near the surface and often exposed. Coastal berms are landscape features found along low-energy coastlines in south Florida and the Florida Keys. Coastal berm is a short forest or shrub thicket found on long, narrow, storm-deposited ridges (sand dunes) of loose sediment formed by a mixture of coarse shell fragments, pieces of coralline algae, and other coastal debris.
                    </P>
                    <P>
                        Like Everglades bully, Florida pineland crabgrass, and pineland sandmat, open canopy conditions are required to allow sufficient sunlight to reach the herbaceous layer and permit growth and flowering of Florida prairie-clover. These conditions are maintained by fire in pine rocklands and marl prairies. In rockland hammocks, only the edges and canopy disruption in the interior provide enough sunlight for Florida prairie-clover. Canopy disruption on rockland hammocks can occur due to natural events such as hurricanes and storm surge. Human disturbance, especially mowing, also maintains suitable conditions in disturbed areas. The plant also requires a limestone substrate to provide suitable growing conditions (
                        <E T="03">e.g.,</E>
                         pH, nutrients, anchoring, and proper drainage). This combination of ecosystem characteristics (
                        <E T="03">i.e.,</E>
                         open canopy and limestone substrate) occurs in pine rocklands, along edges and gaps in rockland hammocks, and in coastal berm.
                    </P>
                    <P>Disturbed areas that support Florida prairie-clover consist of sites that formerly were pine rocklands or rockland hammocks, but in most cases have no remaining pine or hardwood canopy because of previous disturbance (clearing or scraping). These include roadsides, firebreaks, levees, and other areas that are infrequently mowed, or have no tree canopy but retain native herbs and grass species (Bradley 2006, p. 37: Bradley and Gann 1999, p. 61).</P>
                    <P>Loss of pine rockland habitat in Miami-Dade and Monroe Counties is discussed above for the other three species. Habitat modification and destruction from residential and commercial development have severely impacted rockland hammocks and coastal berm that support Florida prairie-clover. Rockland hammocks were once abundant in Miami-Dade and Monroe Counties but are now considered imperiled locally and globally (FNAI 2010, pp. 24-26). Development and agricultural pressures in south Florida have resulted in significant reductions of rockland hammock (Phillips 1940, p. 167; Snyder et al. 1990, pp. 271-272; FNAI 2010, pp. 24-26).</P>
                    <P>The extreme rarity of high-quality pine rockland, rockland hammock, and coastal berm habitat supporting Florida prairie-clover in Miami-Dade and Monroe Counties elevates the importance of disturbed remnant sites that still retain some habitat values. We consider pine rocklands; marl prairies; edges or gaps in rockland hammocks; and coastal berm to be the primary habitats for Florida prairie-clover. However, adjacent disturbed areas currently supporting the species are considered more important when adjacent pine rocklands, marl prairie, rockland hammocks, or coastal berm do not support an existing population, or are of insufficient size or connectivity to support a population of Florida prairie-clover. Therefore, based on the information above, we identify upland habitats consisting of pine rocklands, marl prairie, rockland hammocks, coastal berm, and adjacent disturbed areas to be an essential habitat feature for Florida prairie-clover.</P>
                    <HD SOURCE="HD3">Food, Water, Air, Light, Minerals, or Other Nutritional or Physiological Requirements</HD>
                    <P>
                        <E T="03">Climate (Temperature and Precipitation)</E>
                        —Florida prairie-clover requires adequate rainfall and does not tolerate prolonged freezing temperatures. The climate of south Florida where Florida prairie-clover occurs is classified as tropical humid and subtropical humid, as described above for Everglades bully, Florida pineland crabgrass, and pineland sandmat. Rainfall within the range of Florida prairie-clover varies from an annual average of 60-65 in (153-165 cm) in the northern portion of the Miami Rock Ridge to an average of 35-40 in (89-102 cm) in the lower Florida Keys (Snyder et al. 1990, p. 238). Freezes can occur in the winter months but are very infrequent at this latitude in Florida. Therefore, based on the information above, we determined this type of climate to be an essential habitat feature for Florida prairie-clover.
                    </P>
                    <P>
                        <E T="03">Soils</E>
                        —Substrates supporting Florida prairie-clover are composed of oolitic limestone that is at or very near the surface. Solution holes occasionally form where the surface limestone is dissolved by organic acids. There is typically very little soil development, consisting primarily of accumulations of low-nutrient sand, marl, clayey loam, and organic debris found in solution holes, depressions, and crevices on the limestone surface (FNAI 2010, p. 62). However, Florida prairie-clover can be found at the northern end of the Miami Rock Ridge, where the substrate includes extensive sandy pockets, beginning from approximately North Miami Beach and extending south to approximately SW 216 Street (which runs east-west approximately one-half mile south of Quail Roost Pineland) (Service 1999, p. 3-162). Rockland hammock occurs on a thin layer of highly organic soil covering limestone on high ground that does not regularly flood (FNAI 2010, pp. 24-26). In coastal berms, deep, calcareous sandy soils are the typical substrate of this habitat.
                    </P>
                    <P>
                        These substrates provide anchoring, nutrients, moisture regime, and suitable soil chemistry for Florida prairie-clover, and they facilitate a community of associated plant species that create a competitive regime that allows Florida prairie-clover to persist and spread. Therefore, based on the information above, we identify substrates derived from calcareous limestone (often exposed with little soil development in pine rocklands; with a thin to thick organic soil layer in the case of rockland hammocks; deep, calcareous soils in coastal berm) that provide nutritional requirements and suitable growing conditions (
                        <E T="03">e.g.,</E>
                         pH, nutrients, anchoring, and drainage) that provide anchoring and nutritional requirements to be an essential feature for Florida prairie-clover.
                    </P>
                    <P>
                        <E T="03">Hydrology</E>
                        —Pine rocklands occur on relatively flat, moderately to well drained terrain from 2 to 7 meters above sea level. Drainage varies according to the porosity of the limestone substrate but is generally rapid. Consequently, most sites are wet for only short periods following heavy rains. During the rainy season, however, some sites may be shallowly inundated by slow-flowing surface water for up to 60 days each year (FNAI 2010, p. 62). Marl prairies also are dependent on short hydroperiods up to 60 days. Longer hydroperiods favor the development of peat and the dominance of sawgrass; shorter hydroperiods permit the invasion of woody species (FNAI 2010, p. 108). Therefore, based on the information above, we identify pine rockland, rockland hammock, marl prairie, and coastal berm habitats with short hydroperiods (up to 60 days) to be an essential habitat feature for Florida prairie-clover.
                    </P>
                    <HD SOURCE="HD3">Cover or Shelter</HD>
                    <P>
                        As previously mentioned, Florida prairie-clover occurs in pine rocklands, 
                        <PRTPAGE P="62572"/>
                        marl prairies, rockland hammocks, and coastal berms, and in adjacent disturbed areas, in Monroe and Miami-Dade Counties (Bradley and Gann 1999, p. 3). Pine rockland is characterized by an open canopy of South Florida slash pine, with a limited subcanopy (Snyder et al. 1990, p. 253). Marl prairie is a sparsely vegetated, grass-dominated community. Although the vegetative community is diverse, most marl prairie plant species contribute little cover and over 90 percent of the cover is contributed by only two or three dominant species in any given area (FNAI 2010, p. 107). The open canopy and understory of pine rocklands and marl prairies allow sufficient sunlight to reach the herbaceous layer and permit growth and flowering of Florida prairie-clover (Ross and Ruiz 1996, pp. 5-6; Bradley and Saha 2009, p. 4).
                    </P>
                    <P>Rockland hammock forest floor is largely covered by leaf litter and may have an organic soil layer of variable depth. Rockland hammocks typically have larger, more mature trees in the interior and deep organic soil layer in the interior, while the margins can be almost impenetrable in places with dense growth of smaller shrubs, trees, and vines and shallow organic soil layer. Mature hammocks may be open beneath a tall, well-defined canopy and subcanopy. More commonly, in less mature or disturbed hammocks, dense woody vegetation of varying heights from canopy to short shrubs is often present. Herbaceous species are occasionally present and generally sparse in coverage (FNAI 2010, pp. 24-26).</P>
                    <P>Coastal berm is a short forest or shrub thicket found on long, narrow, storm-deposited ridges (sand dunes). Structure and composition of the vegetation is variable depending on height and time since the last storm event. The most stable berms may share some tree species with rockland hammocks, but generally have a greater proportion of shrubs and herbs. This is a structurally variable community that may appear in various stages of succession following storm disturbance, from scattered herbaceous beach colonizers to a dense stand of tall shrubs (FNAI 2010, pp. 73-74).</P>
                    <P>Disturbed areas that are adjacent to pine rocklands, marl prairies, rockland hammocks, and coastal berms that support Florida prairie-clover may have little to no pine or hardwood canopy, but may have an herbaceous layer dominated by native herbs and grasses. Usually these are former (remnant) pine rocklands or rockland hammocks that have a history of disturbance (clearing or scraping). These sites tend to be infrequently (every 2 to 3 months) mowed areas adjacent to existing pine rocklands or rockland hammocks, such as roadsides and fields. These areas provide the open conditions required by Florida prairie-clover (Bradley 2006, p. 37).</P>
                    <P>Therefore, based on the information above, we identify vegetation composition and structure characterized by an open canopy and understory that allows for adequate sunlight and space for individual growth and population expansion, to be an essential habitat feature for Florida prairie-clover.</P>
                    <HD SOURCE="HD3">Sites for Breeding, Reproduction, or Rearing (or Development) of Offspring</HD>
                    <P>Little is known about the life history of Florida prairie-clover, including pollination biology, seed production, or dispersal. Reproduction is sexual, with new plants generated from seeds. This species likely requires insect visitation for pollination, although there is limited information on this.</P>
                    <P>The pine rocklands, marl prairies, rockland hammocks, coastal berms, and adjacent disturbed habitats identified above as physical or biological features provide a plant community with associated plant species that foster a competitive regime suitable to Florida prairie-clover and contain adequate open space for the recruitment of new plants. Associated plant species in these habitats attract and provide cover for insect pollinators required for Florida prairie-clover pollination (for more information, see Background in the October 11, 2016, proposed listing rule (81 FR 70282) and Summary of Biological Status and Threats in the October 6, 2017, final listing rule (82 FR 46691)).</P>
                    <P>Therefore, based on the information above, we identify pine rockland, marl prairie, rockland hammock, and coastal berm habitats, and adjacent disturbed areas, containing the presence of native pollinators for natural pollination and reproduction to be essential habitat features for Florida prairie-clover.</P>
                    <HD SOURCE="HD3">Habitats Representative of the Historical, Geographic, and Ecological Distributions of the Species</HD>
                    <P>Florida prairie-clover continues to occur in habitats that are representative of the species' historical, geographical, and ecological distribution, although its range has been reduced. The species is currently found in pine rocklands, marl prairies, rockland hammocks, and coastal berms, and it also occurs in adjacent disturbed areas. As described above, these habitats provide a community of associated plant and animal species that are compatible with Florida prairie-clover, vegetation structure that provides adequate sunlight levels and open space for plant growth and regeneration, and substrates with adequate moisture availability and suitable soil chemistry. Representative communities are located on Federal, State, local, and private conservation lands that implement conservation measures benefitting the species.</P>
                    <P>
                        <E T="03">Disturbance Regime</E>
                        —Pine rockland habitat that could or that currently supports Florida prairie-clover depends on a disturbance regime of wild or prescribed fire to open the canopy in order to provide light levels sufficient to support Florida prairie-clover. The historical frequency and magnitude of fire allowed for the persistence of Florida prairie-clover by maintaining an open canopy and understory and preventing succession (transition) of pine rocklands to hardwood-dominated community (rockland hammock). In the absence of fire, some areas of pine rockland may have closed canopies, resulting in areas lacking enough available sunlight to support Florida prairie-clover. Most of these areas can be restored if habitats are managed with a combination of mechanical hardwood removal and prescribed fire.
                    </P>
                    <P>Rockland hammock is susceptible to fire, frost, canopy disruption, and ground water reduction. Rockland hammock can be the advanced successional stage of pine rockland, especially in cases where rockland hammock is adjacent to pine rockland. In such cases, when fire is excluded from pine rockland for 15 to 25 years, it can succeed to rockland hammock vegetation. Historically, rockland hammocks in south Florida evolved with fire in the landscape; fire most often extinguished near the edges when it encountered the hammock's moist microclimate and litter layer. However, rockland hammocks are susceptible to damage from fire during extreme drought or when the water table is lowered. In these cases, fire can cause tree mortality and consume the organic soil layer. Rockland hammocks are also sensitive to the strong winds and storm surge associated with infrequent hurricanes (FNAI 2010, p. 25).</P>
                    <P>
                        Coastal berms are deposited by storm waves along low-energy coasts. Their distance inland depends on the height of the storm surge. Coastal berms that are deposited far enough inland and remain long-undisturbed may in time succeed to hammock. This is a structurally variable community that may appear in various stages of succession following storm disturbance, from scattered herbaceous beach 
                        <PRTPAGE P="62573"/>
                        colonizers to a dense stand of tall shrubs (FNAI 2010, p. 73).
                    </P>
                    <P>The sparsely vegetated edges or interior portions laid open by canopy disruption are the areas of rockland hammock and coastal berm that have light levels sufficient to support Florida prairie-clover. However, the dynamic nature of these habitats means that areas not currently open may become open in the future because of canopy disruption from hurricanes, while areas currently open may develop denser canopy over time, eventually rendering those portions of rockland hammock or coastal berm unsuitable for Florida prairie-clover.</P>
                    <P>Disturbed sites that support Florida prairie-clover are typically maintained by infrequent mowing. Mowing is similar in effect to fire in that it limits encroachment of hardwood species and maintains open canopy conditions suitable for Florida prairie-clover. We consider fire to be the natural disturbance factor for pine rocklands and marl prairie; periodic hurricanes and storm surge are the natural disturbance factors for rockland hammock and coastal berm. In adjacent disturbed areas currently supporting the species, mowing serves some of the ecological function of fire and maintains suitable habitat conditions (open canopy) for the species.</P>
                    <P>
                        Therefore, based on the information above, we identify periodic natural (
                        <E T="03">e.g.,</E>
                         fire, hurricanes, and storm surge) or unnatural (
                        <E T="03">e.g.,</E>
                         prescribed fire, mowing) disturbance regimes that maintain open canopy conditions to be essential habitat features for Florida prairie-clover.
                    </P>
                    <HD SOURCE="HD3">Summary of Physical or Biological Features Essential to the Conservation of Florida Prairie-Clover</HD>
                    <P>Based on the best available science related to the life history and ecology of the species, as outlined in the discussion above, we have determined that the following physical or biological features are essential to the conservation of Florida prairie-clover:</P>
                    <P>South Florida pine rockland, marl prairie, rockland hammock, and coastal berm habitat and adjacent disturbed areas:</P>
                    <P>
                        (1) Consisting of limestone substrate that provides nutritional requirements and suitable growing conditions (
                        <E T="03">e.g.,</E>
                         pH, nutrients, anchoring, and drainage);
                    </P>
                    <P>(2) Characterized by an open canopy and understory with a high proportion of native plant species to provide for sufficient sunlight to permit growth and flowering;</P>
                    <P>(3) Subjected to a monthly mean temperature characteristic of the subtropical humid classification in Miami-Dade County or the tropical humid classification in Collier and Monroe Counties and short hydroperiods ranging up to 60 days each year;</P>
                    <P>
                        (4) Subjected to periodic natural (
                        <E T="03">e.g.,</E>
                         fire, hurricanes, and storm surge) or unnatural (
                        <E T="03">e.g.,</E>
                         prescribed fire, mowing) disturbance regimes to maintain open canopy conditions; and
                    </P>
                    <P>(5) Containing the presence of native pollinators for natural pollination and reproduction.</P>
                    <HD SOURCE="HD1">Special Management Considerations or Protection</HD>
                    <P>When designating critical habitat, we assess whether the specific areas within the geographical area occupied by the species at the time of listing contain features which are essential to the conservation of the species and which may require special management considerations or protection. The features essential to the conservation of Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover may require special management considerations or protection to reduce threats related to habitat loss, fragmentation, and modification primarily due to development; inadequate fire management; nonnative plants; hurricanes and storm surge; changes in disturbance regime; and sea level rise. (For an in-depth discussion of threats, see Summary of Biological Status and Threats in the October 11, 2016, proposed listing rule (81 FR 70282) and Summary of Factors Affecting the Species in the October 6, 2017, final listing rule (82 FR 46691)).</P>
                    <P>
                        Some of these threats (
                        <E T="03">e.g.,</E>
                         habitat loss, inadequate fire management) can be addressed by special management considerations or protection while others (
                        <E T="03">e.g.,</E>
                         sea level rise, hurricanes, storm surge) are beyond the control of landowners and managers. However, even when landowners or land managers may not be able to control all the threats, they may be able to address the results of the threats. Habitat loss is a primary threat to Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover. For example, in Miami-Dade County, development and agriculture have reduced pine rockland habitat by 90 percent in mainland south Florida. Recent vegetation mapping in ENP indicates there are a total of 14,211 ac (5,751 ha) of pine rocklands remaining in ENP, which includes the largest remaining area of pine rockland (approximately 10,895 ac (4,409 ha)) in Florida (Long Pine Key) (Ruiz et al. 2022). Outside of ENP, pine rockland habitat decreased from approximately 185,329 ac (75,000 ha) in the early 1900s to only 3,707 ac (1,500 ha) in 2014 (Possley et al. 2014, p. 154) and 2,275 ac (921 ha) in 2019 (USGS 2019, p. 28), leaving only about 1.2 percent of the pine rocklands on the Miami Rock Ridge remaining, and much of what is left are small remnants scattered throughout the Miami metropolitan area, isolated from other natural areas (Herndon 1998, p. 1). Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover occur on a mix of private and publicly owned lands, most of which are managed for conservation.
                    </P>
                    <P>Habitat fragmentation can have negative effects on populations, especially rare plants, and can affect survival and recovery (Aguilar et al. 2006, pp. 968-980; Aguilar et al. 2008, pp. 5177-5188; Potts et al. 2010, pp. 345-352). In general, habitat fragmentation causes habitat loss, habitat degradation, habitat isolation, changes in species composition, changes in species interactions, increased edge effects, and reduced habitat connectivity (Fahrig 2003, pp. 487-515; Fischer and Lindenmayer 2007, pp. 265-280). Habitat fragments are often functionally smaller than they appear because edge effects (such as increased nonnative, invasive species or wind speeds) impact the available habitat within the fragment (Lienert and Fischer 2003, p. 597).</P>
                    <P>
                        Populations of these species that occur on private land or non-conservation public land are vulnerable to habitat loss, while populations on conservation lands are vulnerable to the effects of habitat degradation if disturbance regimes are disrupted (
                        <E T="03">e.g.,</E>
                         through inadequate fire management or change in management practices on disturbed sites that support the species). Prolonged lack of fire in pine rockland typically results in succession to rockland hammock, and displacement of native species by invasive, nonnative plants often occurs. While Florida prairie-clover also occurs in rockland hammocks, the change from pine is a significant concern because pine rocklands are an extremely rare habitat. Changes in management practices at disturbed sites may include changes in mowing frequency or height, herbicide use, deposition of fill material, and sodding. Further development and degradation of pine rocklands, marl prairies, rockland hammock, and coastal berm increase fragmentation and decrease the conservation value of the remaining functioning habitats. In addition, pine rocklands and marl 
                        <PRTPAGE P="62574"/>
                        prairies are expected to be further degraded and fragmented due to anticipated sea level rise, which would fully or partially inundate these habitats, and cause increases in the salinity of the water table and soils resulting in vegetation shifts in additional pine rocklands in South Florida. Some existing pine rockland, marl prairie, rockland hammock, and coastal berm areas are also projected to be developed for housing as the human population grows and adjusts to changing sea levels.
                    </P>
                    <P>In summary, the features essential to the conservation of Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover may require special management considerations or protection to reduce threats and conserve these features. Actions that could ameliorate threats include, but are not limited to:</P>
                    <P>(1) Increase habitat restoration and management efforts, including fire management and nonnative plant control;</P>
                    <P>(2) Protect, restore, or enhance inland or higher elevation habitats where these species occur and are predicted to be unaffected or less affected by sea-level rise;</P>
                    <P>(3) Augment existing small populations; and</P>
                    <P>(4) Conduct annual or seasonal monitoring efforts, or conduct monitoring prior to, but coordinated with, habitat and fire management planning to refine management efforts over time.</P>
                    <HD SOURCE="HD1">Criteria Used To Identify Critical Habitat</HD>
                    <P>As required by section 4(b)(2) of the Act, we use the best scientific and commercial data available to designate critical habitat. In accordance with the Act and our implementing regulations at 50 CFR 424.12(b), we review available information pertaining to the habitat requirements of the species and identify specific areas within the geographical area occupied by the species at the time of listing and any specific areas outside the geographical area occupied by the species to be considered for designation as critical habitat.</P>
                    <P>We are proposing to designate critical habitat in areas within the geographical area occupied by these species at the time of their listing in 2017. We are not currently proposing to designate any areas outside the geographical area occupied by these species at the time of listing in 2017 because we have not identified any unoccupied areas that meet the definition of critical habitat.</P>
                    <HD SOURCE="HD2">Ranges</HD>
                    <HD SOURCE="HD3">Everglades Bully</HD>
                    <P>The historical range of Everglades bully includes Collier, Miami-Dade, and Monroe Counties, Florida. There are currently 14 extant populations of Everglades bully across these 3 counties. In Miami-Dade County, of 13 historical records for Everglades bully, 11 populations were extant at the time of listing, while 2 (Grant Hammock and Nixon-Smiley Preserve) were extirpated at the time of listing (Bradley et al. 2013, p. 1). The largest population (10,000-100,000 individuals) of Everglades bully in Miami-Dade County occurs at Long Pine Key in ENP (Hodges and Bradley 2006, p. 42; Gann et al. 2006, p. 11; Gann 2015, p. 9). In Monroe and Collier Counties, of two historical records for Everglades bully, two populations were extant at the time of listing in the Lostman's Pines section of Big Cypress National Preserve (BCNP; Monroe County). Since listing, an additional population was discovered in BCNP (extending into Collier County) that owing to the size and maturity of plants, was clearly extant at the time of listing (Lange et al. 2022, pp. 7-8).</P>
                    <P>The species was historically collected as far south as Key Largo, in the Florida Keys, but was extirpated at the time of listing and is still extirpated from the island. The species was not found during recent surveys of pine rocklands on Key Largo (Hodges and Bradley 2006, p. 42) or elsewhere in the Florida Keys (Gann et al. 2002, p. 526; Corogin and Judd 2014, p. 412).</P>
                    <P>Six out of 14 extant Everglades bully populations have fewer than 100 individuals (low resiliency). These small populations are at risk of adverse effects from reduced genetic variation, an increased risk of inbreeding depression, and reduced reproductive output. Many of these populations are small and isolated from each other, decreasing the likelihood that they could be naturally re-established if extinction from one location occurred.</P>
                    <HD SOURCE="HD3">Florida Pineland Crabgrass</HD>
                    <P>The historical range of Florida pineland crabgrass consists of central and southern Miami-Dade County along the Miami Rock Ridge, from the southern Miami to Long Pine Key region of ENP (Bradley and Gann 1999, p. 49) and BCNP in mainland Monroe County (Bradley et al. 2013, p. 2). The current range of Florida pineland crabgrass includes two extant populations, one in ENP (Miami-Dade County) and another in BCNP (mainland Monroe County). Since listing, surveys in BCNP have revealed that the population is more extensive than was known at the time of listing (Lange et al. 2022, p. 8). Outside these areas, of five historical records for Florida pineland crabgrass on Miami Rock Ridge, all were extirpated at the time of listing and remain extirpated.</P>
                    <P>The extant Florida pineland crabgrass population in ENP has 100,000-200,000 individuals (Gann 2015, p. 142; Maschinki and Lange 2015, p. 18), and the extant population in BCNP has more than 10,000 individuals (Bradley 2005 pers comm.), which suggests some level of resiliency. However, these two populations are isolated from one another, and redundancy is reduced from historical levels as several populations in Miami-Dade County have been extirpated. This increases the risk from catastrophic events and decreases the likelihood that they could naturally re-establish if extinction from one location occurred.</P>
                    <HD SOURCE="HD3">Pineland Sandmat</HD>
                    <P>The historical range of pineland sandmat includes Miami-Dade County, Florida, specifically within the southern portion of the Miami Rock Ridge, from the Richmond Pine Rocklands of southern Miami to the Long Pine Key region of ENP (Bradley and Gann 1999, p. 24). The current range of pineland sandmat includes 20 extant populations in Miami-Dade County, although 98 percent of the pine rocklands outside of the ENP have been lost to development. In Miami-Dade County, of 21 historical records for pineland sandmat, 20 populations were extant at the time of listing, while 1 (Larry Penny Thompson Park) was extirpated at the time of listing (J. Possley 2011, pers. comm.). The largest population of pineland sandmat in Miami-Dade County occurs at ENP.</P>
                    <P>Ten out of 20 extant pineland sandmat populations have fewer than 100 individuals (low resiliency). These small populations are at risk of adverse effects from reduced genetic variation, an increased risk of inbreeding depression, and reduced reproductive output. Many of these populations are small and isolated from each other, decreasing the likelihood that they could be naturally re-established in the event that extinction from one location would occur.</P>
                    <HD SOURCE="HD3">Florida Prairie-Clover</HD>
                    <P>
                        The historical range of Florida prairie-clover includes Miami-Dade, Monroe, Collier, and Palm Beach Counties (Gann et al. 2015, pp. 25-26). There have been no reports of this plant from Palm Beach County since 1918 (Bradley and Gann 1999, p. 42).
                        <PRTPAGE P="62575"/>
                    </P>
                    <P>In Miami-Dade County, of 12 historical records for Florida prairie-clover, 7 populations were extant at the time of listing, while 4 (Castellow Hammock, the Coral Gables area, Cox Hammock, and ENP) were considered extirpated at the time of listing (Bradley and Gann 1999, pp. 42-43; Maschinski et al. 2014, p. 39), and the status of one population (Pineland south of Miami River) was unknown (Bradley 2005 pers. comm.). In the final listing rule (82 FR 46691), the ENP populations were considered extirpated because the last official record was from 1964. Surveys were sporadic since that time, however, suitable habitat remained, and the species was recorded at ENP in 2018. Given the dynamic nature of this species and its response to localized disturbances, it likely occurs somewhat cryptically until mowing or fire produces suitable conditions for the species to be readily observed. Therefore, since Florida prairie-clover was found at ENP in 2018, only a year after listing, and was not introduced, we assume the species occurred at ENP at the time of listing in 2017.</P>
                    <P>The largest populations of Florida prairie-clover in Miami-Dade County occur at Crandon Park, Charles Deering Estate, and R. Hardy Matheson Preserve, with population sizes ranging from 98 to 500 plants (Maschinski et al. 2015, pp. 30-32) at each location.</P>
                    <P>In Monroe and Collier Counties, Florida prairie-clover is extant only within BCNP, where there is at least one population (Pernas 2021, pers. comm.).</P>
                    <P>The current range of Florida prairie-clover consists of 9 extant populations; 8 in Miami-Dade County, including at least one in ENP, and at least one extant population in Monroe and Collier Counties in BCNP (Pernas 2021, pers comm.). Many of these populations are small and isolated from each other, decreasing the likelihood that they could be naturally re-established if extinction from one location occurred.</P>
                    <P>We anticipate that full recovery for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover will require continued protection of the remaining extant populations and habitat and augmenting extant populations. It may also require reestablishing populations in occupied areas to provide connectivity among populations to there are adequate numbers of plants and stable populations. This will help to reduce the chance that catastrophic events, such as storms, will simultaneously affect all known populations. However, some of the historical locations no longer contain suitable habitat, and thus are not proposed as designated critical habitat. Accordingly, we have not identified unoccupied areas that are essential for the conservation of the species at this time.</P>
                    <HD SOURCE="HD2">Conservation Strategy</HD>
                    <P>In considering our proposal of critical habitat, we identified the following conservation strategy for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover:</P>
                    <P>(1) Conserve existing populations with sufficient native habitat;</P>
                    <P>(2) Work with partners to conserve existing populations, and implement efforts that will benefit the species and its habitat; and</P>
                    <P>(3) Augment existing populations and facilitate establishment/re-establishment of populations into suitable protected habitat.</P>
                    <P>To facilitate the application of our conservation strategy and goals for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover, we utilized the Shaffer and Stein (2000) methodology for conserving imperiled species known as the `three Rs': representation, resiliency, and redundancy. Resiliency is the ability to sustain populations through the natural range of favorable and unfavorable conditions. Representation ensures adaptive capacity within a species and allows it to respond to environmental changes. This can be facilitated by conserving not just genetic diversity, but also the species' associated habitat type and plant communities. Redundancy ensures an adequate number of sites with resilient populations such that the species has the ability to withstand catastrophic events. Implementation of this methodology has been widely accepted as a reasonable conservation strategy (Tear et al. 2005, p. 841).</P>
                    <P>The amount and distribution of critical habitat we are proposing for designation in occupied areas would allow existing and future established populations of Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover to:</P>
                    <P>(1) Maintain their existing distributions;</P>
                    <P>(2) Expand their distributions into suitable nearby areas (needed to offset habitat loss and fragmentation);</P>
                    <P>(3) Use habitat depending on habitat availability (response to changing nature of coastal habitat, including sea level rise) and support genetic diversity;</P>
                    <P>(4) Increase the size of each population to a level where the threats of genetic, demographic, and normal environmental uncertainties are diminished; and</P>
                    <P>(5) Maintain their ability to withstand local or unit-level environmental fluctuations or catastrophic events.</P>
                    <HD SOURCE="HD3">Everglades Bully</HD>
                    <P>Resiliency will continue to be limited by the reduced amount of pine rockland and marl prairie habitats remaining in Miami-Dade, Collier, and Monroe Counties. All Everglades bully populations, outside of ENP and BCNP, are on small remnant pine rockland and marl prairie and adjacent ecotonal areas (less than 1,000 ac (404 ha)) in Miami-Dade County. Therefore, the resiliency of the populations and redundancy of the species will continue to be influenced by the amount of habitat remaining in the Monroe, Collier, and Miami-Dade Counties. We are proposing to designate critical habitat units that contain the physical or biological features essential to the conservation of the species and that support extant populations at the time of listing. We have not identified any specific areas outside the geographical area occupied by the species at the time it was listed that are essential for the conservation of the species. Accordingly, we are not proposing any unoccupied areas as critical habitat.</P>
                    <HD SOURCE="HD3">Florida Pineland Crabgrass</HD>
                    <P>Resiliency will continue to be limited by the reduced amount of pine rockland and marl prairie habitats remaining in Miami-Dade, Collier, and Monroe Counties. All habitat for the historical Florida pineland crabgrass populations, outside of ENP and BCNP, is now on small remnant pine rockland, marl prairie, and ecotonal areas in Miami-Dade County. We are proposing critical habitat units that contain the physical or biological features essential to the conservation of the species and supported extant populations at the time of listing. We have not identified any specific areas outside the geographical area occupied by the species at the time it was listed that are essential for the conservation of the species. Accordingly, we are not proposing unoccupied areas as critical habitat.</P>
                    <HD SOURCE="HD3">Pineland Sandmat</HD>
                    <P>
                        Resiliency will continue to be limited by the reduced amount of pine rockland habitat remaining in Miami-Dade County. Most of the pineland sandmat populations, outside of ENP, are on small remnant pine rockland sites and adjacent ecotonal areas. Therefore, the resiliency of the populations and redundancy of the species will continue 
                        <PRTPAGE P="62576"/>
                        to be influenced by the amount of habitat remaining in the Miami-Dade County. We are proposing to designate as critical habitat for the pineland sandmat all pine rocklands remaining within the historical range of the species where the species was extant at the time of listing and that contain the physical or biological features essential to the conservation of the species. We have not identified any specific areas outside the geographical area occupied by the species at the time it was listed that are essential for the conservation of the species. Accordingly, we are not proposing any unoccupied areas as critical habitat.
                    </P>
                    <P>Resiliency will continue to be limited by the reduced amount of pine rockland, marl prairie, rockland hammock, and coastal berms habitats remaining in Miami-Dade, Collier, and Monroe Counties. Most Florida prairie-clover populations are on small remnant pine rockland sites and adjacent disturbed areas, with population sizes only ranging from the tens to hundreds of individuals. Five of the eight extant population have fewer than 25 individuals. Therefore, the resiliency of the populations and redundancy of the species will continue to be influenced by the amount of habitat remaining in the Monroe, Collier, and Miami-Dade Counties. We are proposing critical habitat units that contain the physical or biological features essential to the conservation of the species and supported extant populations at the time of listing. We have not identified any specific areas outside the geographical area occupied by the species at the time it was listed that are essential for the conservation of the species. Accordingly, we are not proposing any unoccupied areas as critical habitat.</P>
                    <HD SOURCE="HD2">Sources of Data to Identify Critical Habitat Boundaries</HD>
                    <P>We have determined that all areas known to be occupied at the time of listing should be proposed for critical habitat designation because all occupied sites are necessary to conserve the species. To determine the location and boundaries of occupied critical habitat, the Service used the following sources of data and information for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover:</P>
                    <P>(1) Species occurrence spatial data and ArcGIS geographic information system (GIS) software to spatially depict the location and extent of documented populations of Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover;</P>
                    <P>(2) Reports prepared by FNAI, Fairchild Tropical Botanical Garden (FTBG), Institute for Regional Conservation (IRC), National Park Service (NPS), and Florida Department of Environmental Protection (FDEP);</P>
                    <P>(3) Historical records found in reports and associated voucher specimens housed at herbaria, all of which are referenced in the above-mentioned reports;</P>
                    <P>(4) Digitally produced habitat maps provided by Miami-Dade, Collier, and Monroe Counties; and</P>
                    <P>(5) Aerial images of Miami-Dade, Collier, and Monroe Counties. The presence of pine rocklands and marl prairie was determined using GIS and spatial data depicting the current habitat status. These habitat data for Miami-Dade County were developed by Miami-Dade Department of Environmental Protection (DERM), for the Natural Forest Community (NFC) program, and include pine rocklands and marl prairie. Pine rockland, rockland hammock, and coastal berm habitat follow predictable landscape patterns and have a recognizable signature in the aerial imagery. Aerial imagery was utilized to identify these habitats in Monroe and Collier Counties and disturbed areas adjacent to marl prairie, pine rocklands, rockland hammock, and coastal berm.</P>
                    <P>We delineated critical habitat unit boundaries using the following criteria:</P>
                    <P>
                        (1) The delineation included space to allow for the successional nature of the habitats (
                        <E T="03">i.e.,</E>
                         gain and loss of areas with sufficient light availability due to disturbance of the vegetation, driven by natural events such as inundation and hurricanes and through prescribed fire), and habitat transition or loss due to sea level rise.
                    </P>
                    <P>
                        (2) All areas (
                        <E T="03">i.e.,</E>
                         physical or biological features) may require special management to be able to support a higher density of the plants within the occupied space. These areas generally are habitats where some of the habitat features have been degraded or lost through natural or human causes. These areas would help to offset the anticipated loss and degradation of habitat occurring or expected from the effects of climate change (such as sea level rise) or due to development.
                    </P>
                    <P>(3) The areal extent of a plant population is dynamic over time within suitable habitat, while a survey represents a snapshot in time. Unsurveyed areas near mapped populations likely support plants currently or did in the past.</P>
                    <HD SOURCE="HD2">Areas Occupied at the Time of Listing</HD>
                    <P>The proposed occupied critical habitat designation for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover focuses on areas within the plants' historical ranges that have retained the essential habitat features that will allow for the maintenance and expansion of existing populations. The proposed occupied critical habitat units were delineated around extant populations at the time of listing. These units include the mapped extent of the population that contains one or more of the essential physical or biological features essential to the conservation of the species.</P>
                    <P>For areas within the geographic area occupied by Everglades bully and Florida pineland crabgrass at the time of listing, we delineated critical habitat unit boundaries using the following criteria:</P>
                    <P>(1) Pine rockland and marl prairie habitat, and the transitional areas (ecotones) between these and other vegetation types that was occupied by the species at the time of listing; and</P>
                    <P>(2) Presence of suitable habitat and physical or biological essential features.</P>
                    <P>For Everglades bully, five occupied units are being proposed as critical habitat. These five units encompass the 14 extant populations of Everglades bully in Collier, Monroe, and Miami-Dade Counties. We consider pine rockland and marl prairies to be the primary habitat for Everglades bully. Adjacent ecotonal areas currently supporting the species are also considered essential when adjacent pine rocklands and marl prairies do not support an existing population or are of insufficient size or connectivity to support a population of the species. We have not identified any specific areas outside the geographical area occupied by the species at the time it was listed that are essential for the conservation of the species. Accordingly, we are not proposing unoccupied critical habitat for the Everglades bully.</P>
                    <P>
                        For Florida pineland crabgrass, two occupied units are being proposed as critical habitat. These two units encompass the two extant populations of Florida pineland crabgrass in Monroe and Miami-Dade Counties. We consider pine rockland and marl prairies to be the primary habitat for Florida pineland crabgrass. Adjacent ecotonal areas currently supporting the species are also considered essential when adjacent pine rocklands and marl prairies do not support an existing population or are of insufficient size or connectivity to support a population of the species. We have not identified any specific areas outside the geographical area occupied by the species at the time it was listed that are essential for the conservation of 
                        <PRTPAGE P="62577"/>
                        the species. Accordingly, we are not proposing unoccupied critical habitat for the Florida pineland crabgrass.
                    </P>
                    <P>For areas within the geographic area occupied by pineland sandmat at the time of listing, we delineated critical habitat unit boundaries using the following criteria:</P>
                    <P>(1) Pine rockland habitat and the transitional areas (ecotones) between pine rocklands and adjacent habitat that was occupied by the species at the time of listing;</P>
                    <P>(2) Pine rockland habitat that is currently occupied by the species; and</P>
                    <P>(3) Presence of essential physical or biological features.</P>
                    <P>For pineland sandmat, three occupied units are being proposed as critical habitat. These three units encompass the 20 extant populations of pineland sandmat in Miami-Dade County. We consider pine rockland to be the primary habitat for pineland sandmat. Adjacent ecotonal areas currently supporting the species are also considered essential when adjacent pine rocklands do not support an existing population or are of insufficient size or connectivity to support a population of the species. We have not identified any specific areas outside the geographical area occupied by the species at the time it was listed that are essential for the conservation of the species. Accordingly, we are not proposing unoccupied critical habitat for the pineland sandmat.</P>
                    <P>For areas within the geographic area occupied by Florida prairie-clover at the time of listing, we delineated critical habitat unit boundaries using the following criteria:</P>
                    <P>(1) Pine rockland, marl prairie, rockland hammock, and coastal berm habitat and the transitional areas (ecotones) between these and other vegetation types that was occupied by the species at the time of listing;</P>
                    <P>(2) Pine rockland, marl prairie, rockland hammock, and coastal berm habitat that is currently occupied by the species; and</P>
                    <P>(3) Presence of essential physical or biological features.</P>
                    <P>For Florida prairie-clover, four occupied units are being proposed as critical habitat. These four units encompass the eight extant populations of Florida prairie-clover in Collier and Miami-Dade Counties. We consider pine rockland, marl prairie, rockland hammock, and coastal berm to be the primary habitats for Florida prairie-clover. Adjacent disturbed areas currently supporting the species are also considered essential when adjacent pine rockland, marl prairie, rockland hammock, and coastal berm habitats do not support an existing population or are of insufficient size or connectivity to support a population of the species. In addition, because we have determined that occupied habitat is sufficient to conserve the species, we did not propose any unoccupied areas as critical habitat.</P>
                    <P>In summary, for areas within the geographical area occupied by Everglades bully and Florida pineland crabgrass, at the time of listing, we delineated critical habitat unit boundaries around extant populations at the time of listing and also evaluating habitat suitability of pine rockland and marl prairie habitats within the historical range of the plants. We retained those areas that contain some or all of the essential physical or biological features essential to the conservation of the species and that may require special management. For areas within the geographical area occupied by pineland sandmat at the time of listing, we delineated critical habitat unit boundaries around extant populations at the time of listing and also evaluating habitat suitability of pine rockland habitat within the historical range of the plant. We retained those areas that contain some or all of the essential physical or biological features essential to the conservation of the species and that may require special management. For areas within the geographical area occupied by Florida prairie-clover at the time of listing, we delineated critical habitat unit boundaries around extant populations at the time of listing and also evaluating habitat suitability of pine rockland, marl prairie, rockland hammock, and coastal berm habitats within the historical range of the plant. We retained those areas that contain some or all of the essential physical or biological features essential to the conservation of the species and that may require special management.</P>
                    <P>When determining proposed critical habitat boundaries, we made every effort to avoid including developed areas such as lands covered by buildings, pavement, and other structures because such lands lack physical or biological features essential to the conservation of the plants, nor are they essential to the conservation of the species themselves. The scale of the maps we prepared under the parameters for publication within the Code of Federal Regulations may not reflect the exclusion of such developed lands. Any such lands inadvertently left inside critical habitat boundaries shown on the maps of this proposed rule have been excluded by text in the proposed rule and are not proposed for designation as critical habitat. Therefore, if the critical habitat is finalized as proposed, a Federal action involving these lands would not trigger section 7 consultation with respect to critical habitat and the requirement of no adverse modification unless the specific action would affect the physical or biological features in the adjacent critical habitat.</P>
                    <P>
                        The critical habitat designations are defined by the map or maps, as modified by any accompanying regulatory text, presented at the end of this document under Proposed Regulation Promulgation. We include more detailed information on the boundaries of the critical habitat designations in the preamble of this document. We will make the coordinates or plot points or both on which each map is based available to the public on 
                        <E T="03">https://www.regulations.gov</E>
                         at Docket No. FWS-R4-ES-2022-0125, on our internet site at 
                        <E T="03">https://www.fws.gov/office/florida-ecological-services/library,</E>
                         and at the field office responsible for the designations (see 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        , above).
                    </P>
                    <HD SOURCE="HD1">Proposed Critical Habitat Designation for Everglades Bully</HD>
                    <P>We are proposing to designate approximately 179,680 ac (72,714 ha) in five units as critical habitat for Everglades bully. The critical habitat areas we describe below constitute our current best assessment of areas that meet the definition of critical habitat for Everglades bully. All areas with known extant populations at the time of listing are proposed for designation as critical habitat. Some units currently may contain multiple populations, but the number can vary over a 1- to 5-year period due to the dynamic nature of this species in response to disturbance. The five areas we propose as critical habitat are:</P>
                    <P>(1) EB1, Big Cypress National Preserve, Collier, Miami-Dade, and Monroe Counties, Florida;</P>
                    <P>(2) EB2, Everglades National Park, Miami-Dade County, Florida;</P>
                    <P>(3) EB3, Richmond Pine Rocklands, Miami-Dade County, Florida;</P>
                    <P>(4) EB4, Quail Roost Pineland, Miami-Dade County, Florida; and</P>
                    <P>(5) EB5, Navy Wells, Miami-Dade County, Florida.</P>
                    <P>
                        Land ownership within the proposed critical habitat consists of Federal (86 percent), State (0.1 percent), County (13 percent), and private and other (1 percent). Other lands include areas for which ownership information is unclear or unavailable. Table 1 shows these units by land ownership, area, and occupancy.
                        <PRTPAGE P="62578"/>
                    </P>
                    <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="s50,15,15,13,13,13,xs36">
                        <TTITLE>Table 1—Proposed Critical Habitat Units for Everglades Bully, Including Total Area, Area by Land Ownership, and Occupancy</TTITLE>
                        <TDESC>[All areas rounded to the nearest whole acre (ac) and hectare (ha).]</TDESC>
                        <BOXHD>
                            <CHED H="1">Unit</CHED>
                            <CHED H="1">
                                Total 
                                <LI>ac (ha)</LI>
                            </CHED>
                            <CHED H="1">
                                Federal 
                                <LI>ac (ha)</LI>
                            </CHED>
                            <CHED H="1">
                                State 
                                <LI>ac (ha)</LI>
                            </CHED>
                            <CHED H="1">
                                County 
                                <LI>ac (ha)</LI>
                            </CHED>
                            <CHED H="1">
                                Private/
                                <LI>other ac (ha)</LI>
                            </CHED>
                            <CHED H="1">Occupied</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">EB1—Big Cypress National Preserve</ENT>
                            <ENT>169,885 (68,750)</ENT>
                            <ENT>146,014 (59,090)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>22,411 (9,070)</ENT>
                            <ENT>1,460 (591)</ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">EB2—Everglades National Park</ENT>
                            <ENT>7,994 (3,235)</ENT>
                            <ENT>7,860 (3,181)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>133 (54)</ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">EB3— Richmond Pine Rocklands</ENT>
                            <ENT>987 (399)</ENT>
                            <ENT>191 (77)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>609 (247)</ENT>
                            <ENT>187 (76)</ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">EB4—Quail Roost Pineland</ENT>
                            <ENT>256 (104)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>103 (42)</ENT>
                            <ENT>47 (19)</ENT>
                            <ENT>107 (43)</ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">EB5—Navy Wells</ENT>
                            <ENT>558 (226)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>74 (30)</ENT>
                            <ENT>324 (131)</ENT>
                            <ENT>160 (65)</ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="03">Total</ENT>
                            <ENT>179,680 (72,714)</ENT>
                            <ENT>154,065 (62,348)</ENT>
                            <ENT>177 (72)</ENT>
                            <ENT>23,391 (9,467)</ENT>
                            <ENT>2,048 (829)</ENT>
                            <ENT/>
                        </ROW>
                        <ROW>
                            <ENT I="05">Percent of Total</ENT>
                            <ENT/>
                            <ENT>86</ENT>
                            <ENT>0.1</ENT>
                            <ENT>13</ENT>
                            <ENT>1</ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding or minor mapping discrepancies.
                        </TNOTE>
                    </GPOTABLE>
                    <P>Approximately 5.4 percent (9,763 ac (3,951 ha)) of the lands contained within units proposed as critical habitat for Everglades bully are already designated critical habitat for other federally listed species. Most of the lands proposed in this rule that are not designated as critical habitat for other federally listed species occur in the BCNP.</P>
                    <P>We present brief descriptions of the proposed critical habitat units and the justification for why they meet the definition of critical habitat for Everglades bully, below. All proposed critical habitat units were occupied at the time of listing and are currently occupied. All units contain all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <HD SOURCE="HD3">Unit EB1: Big Cypress National Preserve, Collier, Miami-Dade, and Monroe Counties, Florida</HD>
                    <P>Unit EB1 consists of approximately 169,885 ac (68,750 ha) in Collier, Miami-Dade, and Monroe Counties, Florida. The unit is comprised of lands in BCNP, including Federal lands in BCNP (146,014 ac (59,090 ha)) and County lands (22,411 ac (9,070 ha)) and parcels in private or other ownership (1,460 ac (591 ha)) within BCNP.</P>
                    <P>Special management considerations or protection may be required within this unit to address threats of nonnative plant and animal species, lack of fire, off-road vehicle use, oil and gas exploration and extraction, and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Everglades bully.</P>
                    <P>This unit is part of lands contained within the BCNP. Within this unit, as part of their 2019 Fire Management Plan (NPS 2019), the NPS conducts nonnative species control and prescribed fire in areas that could support Everglades bully.</P>
                    <P>
                        Unit EB1 does not contain previously designated critical habitat. The federally threatened eastern indigo snake (
                        <E T="03">Drymarchon couperi</E>
                        ), federally endangered Florida panther (
                        <E T="03">Puma</E>
                         (=
                        <E T="03">Felis</E>
                        ) 
                        <E T="03">concolor coryi</E>
                        ), and federally endangered Florida bonneted bat (
                        <E T="03">Eumops floridanus</E>
                        ) occur in this unit.
                    </P>
                    <HD SOURCE="HD3">Unit EB2: Everglades National Park, Miami-Dade County, Florida</HD>
                    <P>Unit EB2 consists of approximately 7,994 ac (3,235 ha) in Miami-Dade County. The unit is comprised of Federal lands in ENP (ENP) (7,860 ac (3,181 ha)) and parcels in private or other ownership (133 ac (54 ha)). The unit includes Long Pine Key and some of the surrounding areas in ENP.</P>
                    <P>Special management considerations or protection may be required within this unit to address threats of nonnative plant and animal species, lack of fire, and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Everglades bully.</P>
                    <P>This unit is part of lands contained within the ENP. Within this unit, as part of their General Management Plan (NPS 2015), the NPS conducts nonnative species control and prescribed fire in areas that support or could support Everglades bully.</P>
                    <P>
                        The entirety of Unit EB2 is designated critical habitat for the federally endangered Bartram's scrub-hairstreak (
                        <E T="03">Strymon acis bartrami</E>
                        ) and Florida leafwing (
                        <E T="03">Anaea troglodyta floridalis</E>
                        ) butterflies. The federally threatened eastern indigo snake occurs in this unit.
                    </P>
                    <HD SOURCE="HD3">Unit EB3: Richmond Pine Rocklands and Surrounding Areas, Miami-Dade County, Florida</HD>
                    <P>Unit EB3 consists of approximately 987 ac (399 ha) in Miami-Dade County. The unit is comprised of Federal lands owned by the U.S. Coast Guard, U.S. Army Corps of Engineers, Federal Bureau of Prisons, and National Oceanic and Atmospheric Administration (191 ac (77 ha)); County lands within and adjacent to Larry and Penny Thompson Park, Martinez Preserve, Zoo Miami, and Eachus Pineland (609 ac (247 ha)); and parcels in private or other ownership, including the preserve and mitigation area associated with the Coral Reef Commons Habitat Conservation Plan (HCP) (187 ac (76 ha)).</P>
                    <P>Special management considerations or protection may be required within this unit to address threats of nonnative plant and animal species, lack of fire, and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Everglades bully. Within this unit, the Miami-Dade DERM conducts nonnative species control, prescribed fire, and mechanical vegetation treatments on lands owned by Miami-Dade County. The U.S. Coast Guard also conducts nonnative species control and mechanical vegetation treatments on their property in this unit. The actions help improve habitat that supports Everglades bully.</P>
                    <P>
                        Within this unit, approximately 109.3 ac (44.2 ha) of land owned by Coral Reef Commons is proposed for critical habitat designation for Everglades bully. Everglades bully is a covered species under the Coral Reef Commons Habitat Conservation Plan. Because Everglades bully is a covered species under the Coral Reef Commons HCP and the preserve and mitigation area within this 
                        <PRTPAGE P="62579"/>
                        proposed critical habitat unit are being managed for the conservation of the species and pine rockland habitat, the on-site preserve and the off-site mitigation area are being considered for exclusion from critical habitat under section 4(b)(2) of the Act (please refer to Consideration of Impacts Under Section 4(b)(2) of the Act, below).
                    </P>
                    <P>
                        The entirety of unit EB3 is designated critical habitat for the following federally endangered species: Carter's small-flowered flax (
                        <E T="03">Linum carteri</E>
                         var. 
                        <E T="03">carteri</E>
                        ), Florida brickell-bush (
                        <E T="03">Brickellia mosieri</E>
                        ), and Bartram's scrub-hairstreak and Florida leafwing butterflies. The federally threatened eastern indigo snake and federally endangered Florida bonneted bat occur in this unit.
                    </P>
                    <HD SOURCE="HD3">Unit EB4: Quail Roost Pineland and Surrounding Areas, Miami-Dade County, Florida</HD>
                    <P>Unit EB4 consists of approximately 256 ac (104 ha) in Miami-Dade County. The unit is comprised of State lands within Quail Roost Pineland, Goulds Pineland and Addition, and Silver Palm Groves Pineland (103 ac (42 ha)); County lands, including Medsouth Park, Black Creek Forest, and Rock Pit #46 (47 ac (19 ha)); and parcels in private ownership (107 ac (43 ha)), including Porter-Russell Pineland owned by the Tropical Audubon Society.</P>
                    <P>Special management considerations or protection may be required within this unit to address threats of nonnative plant and animal species, lack of fire, and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Everglades bully. Within this unit, DERM conducts nonnative species control, prescribed fire, and mechanical vegetation treatments on lands owned by Miami-Dade County.</P>
                    <P>The entirety of unit EB4 is designated critical habitat for the federally endangered Carter's small-flowered flax and Florida brickell-bush, and much of the area is designated critical habitat for the federally endangered Bartram's scrub-hairstreak butterfly. The federally threatened eastern indigo snake and federally endangered Florida bonneted bat occur in this unit.</P>
                    <HD SOURCE="HD3">Unit EB5: Navy Wells Pineland Preserve and Surrounding Areas, Miami-Dade County, Florida</HD>
                    <P>Unit EB5 consists of approximately 558 ac (226 ha) of habitat in Miami-Dade County. The unit is comprised of State lands within Florida City Pineland, Palm Drive Pineland, Navy Wells Pineland Preserve (portion), and Navy Wells Pineland #39 (74 ac (30 ha)); County/local lands, including Navy Wells Pineland Preserve (portion) and Sunny Palms Pineland (324 ac (131 ha)); and parcels in private ownership (160 ac (65 ha)).</P>
                    <P>Special management considerations or protection may be required within this unit to address threats of nonnative plant and animal species, lack of fire, and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Everglades bully. Within this unit, DERM conducts nonnative species control, prescribed fire, and mechanical vegetation treatments on lands owned by Miami-Dade County.</P>
                    <P>The entirety of unit EB5 is designated critical habitat for the following federally endangered species: Carter's small-flowered flax, Florida brickell-bush, and Bartram's scrub-hairstreak and Florida leafwing butterflies. The federally threatened eastern indigo snake and federally endangered Florida bonneted bat occur in this unit.</P>
                    <HD SOURCE="HD1">Proposed Critical Habitat Designation for Florida Pineland Crabgrass</HD>
                    <P>We are proposing to designate approximately 177,879 ac (71,985 ha) in two units as critical habitat for Florida pineland crabgrass. The critical habitat areas we describe below constitute our current best assessment of areas that meet the definition of critical habitat for Florida pineland crabgrass. The two areas we propose as critical habitat are:</P>
                    <P>(1) FPCG1, Big Cypress National Preserve, Collier, Miami-Dade, and Monroe Counties, Florida; and</P>
                    <P>(2) FPCG2, Everglades National Park, Miami-Dade County, Florida.</P>
                    <P>Land ownership within the proposed critical habitat consists of Federal (86 percent), County (13 percent), and private and other (1 percent). Other lands include areas for which ownership information is unclear or unavailable. Table 2 shows these units by land ownership, area, and occupancy.</P>
                    <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="s50,15,15,13,13,13,xs36">
                        <TTITLE>Table 2—Proposed Critical Habitat Units for Florida Pineland Crabgrass, Including Area, Area by Land Ownership, and Occupancy</TTITLE>
                        <TDESC>[All areas rounded to the nearest whole acres (ac) and hectares (ha).]</TDESC>
                        <BOXHD>
                            <CHED H="1">Unit</CHED>
                            <CHED H="1">
                                Total 
                                <LI>ac (ha)</LI>
                            </CHED>
                            <CHED H="1">
                                Federal 
                                <LI>ac (ha)</LI>
                            </CHED>
                            <CHED H="1">
                                State 
                                <LI>ac (ha)</LI>
                            </CHED>
                            <CHED H="1">
                                County 
                                <LI>ac (ha)</LI>
                            </CHED>
                            <CHED H="1">
                                Private/
                                <LI>other ac (ha)</LI>
                            </CHED>
                            <CHED H="1">Occupied</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">FPCG1—Big Cypress National Preserve</ENT>
                            <ENT>169,885 (68,750)</ENT>
                            <ENT>146,014 (59,090)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>22,411 (9,070)</ENT>
                            <ENT>1,460 (591)</ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">FPCG2—Everglades National Park</ENT>
                            <ENT>7,994 (3,235)</ENT>
                            <ENT>7,860 (3,181)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>133 (54)</ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="03">Total</ENT>
                            <ENT>177,879 (71,985)</ENT>
                            <ENT>153,874 (62,271)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>22,411 (9,070)</ENT>
                            <ENT>1,593 (645)</ENT>
                            <ENT/>
                        </ROW>
                        <ROW>
                            <ENT I="05">Percent of Total</ENT>
                            <ENT/>
                            <ENT>86</ENT>
                            <ENT>0</ENT>
                            <ENT>13</ENT>
                            <ENT>1</ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding or minor mapping discrepancies.
                        </TNOTE>
                    </GPOTABLE>
                    <P>Approximately 5 percent (8,894 ac (3,599 ha)) of the area proposed as critical habitat for Florida pineland crabgrass is also currently designated under the Act as critical habitat for the federally endangered Bartram's scrub-hairstreak and Florida leafwing butterflies.</P>
                    <P>We present brief descriptions of the proposed critical habitat units and the justification for why they meet the definition of critical habitat for Florida pineland crabgrass, below.</P>
                    <P>Unit FPCG1: Big Cypress National Preserve, Collier, Miami-Dade, and Monroe Counties, Florida. All proposed critical habitat units were occupied at the time of listing and are currently occupied. All units contain all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <P>
                        Unit FPCG1 consists of approximately 169,885 ac (68,750 ha) in Collier, Miami-Dade, and Monroe Counties. The unit is comprised of Federal lands in BCNP (146,014 ac (59,090 ha)), County 
                        <PRTPAGE P="62580"/>
                        lands (22,411 ac (9,070 ha)), and parcels in private or other ownership (1,460 ac (591 ha)).
                    </P>
                    <P>Special management considerations or protection may be required within this unit to address threats of nonnative plant and animal species, lack of fire, off-road vehicle use, oil and gas exploration and extraction, and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Florida pineland crabgrass.</P>
                    <P>This unit is part of lands within BCNP. Within this unit, as part of their 2019 Fire Management Plan (NPS 2019), the NPS conducts nonnative species control and prescribed fire in areas that support or could support Florida pineland crabgrass.</P>
                    <P>Unit FPCG1 does not contain previously designated critical habitat. The federally threatened eastern indigo snake, federally endangered Florida panther, and federally endangered Florida bonneted bat occur in this unit.</P>
                    <HD SOURCE="HD3">Unit FPCG2: Everglades National Park, Miami-Dade County, Florida</HD>
                    <P>Unit FPCG2 consists of approximately 7,994 ac (3,235 ha) in Miami-Dade County. The unit is comprised of Federal lands in ENP (7,860 ac (3,181 ha) and parcels in private or other ownership (133 ac (54 ha)). The unit includes Long Pine Key and some of the surrounding areas in ENP.</P>
                    <P>Special management considerations or protection may be required within this unit to address threats of nonnative plant and animal species, lack of fire, and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Florida pineland crabgrass.</P>
                    <P>This unit is part of lands within ENP. Within this unit, as part of their General Management Plan (NPS 2015), the NPS conducts nonnative species control and prescribed fire in areas that support or could support Florida pineland crabgrass.</P>
                    <P>The entirety of unit FPCG2 is designated critical habitat for the federally endangered Bartram's scrub-hairstreak and Florida leafwing butterflies. The federally threatened eastern indigo snake, federally endangered Florida panther, and federally endangered Florida bonneted bat occur in this unit.</P>
                    <HD SOURCE="HD1">Proposed Critical Habitat Designation for Pineland Sandmat</HD>
                    <P>We are proposing to designate approximately 8,867 ac (3,588 ha) in three units as critical habitat for pineland sandmat. The critical habitat areas we describe below constitute our current best assessment of areas that meet the definition of critical habitat for pineland sandmat. All areas with known extant populations at the time of listing are proposed for designation as critical habitat. The units currently may contain multiple populations, but the number can vary over a 1- to 5-year period due to the dynamic nature of this species in response to disturbance. The three areas we propose as critical habitat are:</P>
                    <P>(1) PS1, Everglades National Park, Miami-Dade County, Florida;</P>
                    <P>(2) PS2, Camp Owaissa Bauer, Miami-Dade County, Florida; and</P>
                    <P>(3) PS3, Navy Wells, Miami-Dade County, Florida.</P>
                    <P>Land ownership within the proposed critical habitat consists of Federal (89 percent), State (1 percent), County (5 percent), and private and other (5 percent). Other lands include areas for which ownership information is unclear or unavailable. Table 3 shows these units by land ownership, area, and occupancy.</P>
                    <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="s50,15,15,13,13,13,xs36">
                        <TTITLE>Table 3—Proposed Critical Habitat Units for Pineland Sandmat, Including Area, Area by Land Ownership, and Occupancy</TTITLE>
                        <TDESC>[All areas rounded to the nearest whole acre (ac) and hectare (ha).]</TDESC>
                        <BOXHD>
                            <CHED H="1">Unit</CHED>
                            <CHED H="1">
                                Total 
                                <LI>ac (ha)</LI>
                            </CHED>
                            <CHED H="1">
                                Federal 
                                <LI>ac (ha)</LI>
                            </CHED>
                            <CHED H="1">
                                State 
                                <LI>ac (ha)</LI>
                            </CHED>
                            <CHED H="1">
                                County 
                                <LI>ac (ha)</LI>
                            </CHED>
                            <CHED H="1">
                                Private/
                                <LI>other ac (ha)</LI>
                            </CHED>
                            <CHED H="1">Occupied</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">PS1—Everglades National Park</ENT>
                            <ENT>7,994 (3,235)</ENT>
                            <ENT>7,860 (3,181)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>133 (54)</ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PS2—Camp Owaissa Bauer</ENT>
                            <ENT>315 (127)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>49 (20)</ENT>
                            <ENT>145 (59)</ENT>
                            <ENT>122 (49)</ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">PS3—Navy Wells</ENT>
                            <ENT>558 (226)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>74 (30)</ENT>
                            <ENT>310 (125)</ENT>
                            <ENT>174 (70)</ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="03">Total</ENT>
                            <ENT>8,867 (3,588)</ENT>
                            <ENT>7,860 (3,181)</ENT>
                            <ENT>123 (50)</ENT>
                            <ENT>455 (184)</ENT>
                            <ENT>429 (173)</ENT>
                            <ENT/>
                        </ROW>
                        <ROW>
                            <ENT I="05">Percent of Total</ENT>
                            <ENT/>
                            <ENT>89</ENT>
                            <ENT>1</ENT>
                            <ENT>5</ENT>
                            <ENT>5</ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding or small mapping discrepancies.
                        </TNOTE>
                    </GPOTABLE>
                    <P>Approximately 99.9 percent (8,854 ac (3,583 ha)) of the lands contained within units proposed as critical habitat for pineland sandmat are already designated critical habitat for other federally listed species.</P>
                    <P>We present brief descriptions of the proposed critical habitat units and the justification for why they meet the definition of critical habitat for pineland sandmat, below. All proposed critical habitat units were occupied at the time of listing and are currently occupied. All units contain all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <HD SOURCE="HD3">Unit PS1: Everglades National Park, Miami-Dade County, Florida</HD>
                    <P>Unit PS1 consists of approximately 7,994 ac (3,235 ha) in Miami-Dade County. The unit is comprised of Federal lands in ENP (7,860 ac (3,181 ha)) and parcels in private or other ownership (133 ac (54 ha)). The unit includes Long Pine Key and some of the surrounding areas in ENP.</P>
                    <P>Special management considerations or protection may be required within this unit to address threats of nonnative plant and animal species, lack of fire, and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports pineland sandmat.</P>
                    <P>This unit is part of lands within ENP. Within this unit, as part of their General Management Plan (NPS 2015), the NPS conducts nonnative species control and prescribed fire in areas that support or could support pineland sandmat.</P>
                    <P>
                        The entirety of unit PS1 is designated critical habitat for the federally endangered Bartram's scrub-hairstreak and Florida leafwing butterflies. The federally threatened eastern indigo snake, federally endangered Florida panther, and federally endangered Florida bonneted bat occur in this unit.
                        <PRTPAGE P="62581"/>
                    </P>
                    <HD SOURCE="HD3">Unit PS2: Camp Owaissa Bauer and Surrounding Areas, Miami-Dade County, Florida</HD>
                    <P>Unit PS2 consists of approximately 315 ac (127 ha) of habitat in Miami-Dade County. The unit is comprised of State lands within Owaissa Bauer Pineland Addition, West Biscayne Pineland, Ingram Pineland, and Fuchs Hammock Addition (49 ac (20 ha)); County lands, including Camp Owaissa Bauer, Pine Island Lake Park, Seminole Wayside Park, and Northrop Pineland (145 ac (59 ha)); and parcels in private ownership (122 ac (49 ha)), including the Pine Ridge Sanctuary (a private conservation area).</P>
                    <P>Special management considerations or protection may be required within this unit to address threats of nonnative plant and animal species, lack of fire, and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports pineland sandmat.</P>
                    <P>The entirety of unit PS2 is designated critical habitat for the following federally endangered species: Carter's small-flowered flax, Florida brickell-bush, and Bartram's scrub-hairstreak butterfly. The federally threatened eastern indigo snake occurs in this unit.</P>
                    <HD SOURCE="HD3">Unit PS3: Navy Wells Pineland Preserve and Surrounding Areas, Miami-Dade County, Florida</HD>
                    <P>Unit PS3 consists of approximately 558 ac (226 ha) of habitat in Miami-Dade County. The unit is comprised of State lands within Florida City Pineland, Palm Drive Pineland, Navy Wells Pineland Preserve (a portion), and Navy Wells Pineland #39 (74 ac (30 ha)); County lands, including Navy Wells Pineland Preserve (a portion) and Sunny Palms Pineland (310 ac (125 ha)); and parcels in private ownership (174 ac (70 ha)).</P>
                    <P>Special management considerations or protection may be required within this unit to address threats of nonnative plant and animal species, lack of fire, and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports pineland sandmat.</P>
                    <P>The entirety of unit PS3 is designated critical habitat for the following federally endangered species: Carter's small-flowered flax, Florida brickell-bush, and Bartram's scrub-hairstreak and Florida leafwing butterflies. The federally threatened eastern indigo snake occurs in this unit.</P>
                    <HD SOURCE="HD1">Proposed Critical Habitat Designation for Florida Prairie-Clover</HD>
                    <P>We are proposing to designate approximately 179,300 ac (72,560 ha) in four units as critical habitat for Florida prairie-clover. The critical habitat areas we describe below constitute our current best assessment of areas that meet the definition of critical habitat for Florida prairie-clover. All areas with known extant populations at the time of listing are proposed for designation as critical habitat. Some units currently contain multiple populations, but the number can vary over a 1- to 5-year period due to the dynamic nature of this species in response to disturbance. The four areas we propose as critical habitat are:</P>
                    <P>(1) FPC1, Big Cypress National Preserve, Collier, Miami-Dade, and Monroe Counties, Florida;</P>
                    <P>(2) FPC2, Everglades National Park, Miami-Dade County, Florida;</P>
                    <P>(3) FPC3, U.S. Department of Agriculture (USDA) Subtropical Horticultural Research Station, Miami-Dade County, Florida; and</P>
                    <P>(4) FPC4, Crandon Park, Miami-Dade County, Florida.</P>
                    <P>Land ownership within the proposed critical habitat consists of Federal (86.2 percent), State (0.7 percent), County (12.6 percent), and private and other (0.5 percent). Other lands include areas for which ownership information is unclear or unavailable. Table 4 shows these units by land ownership, area, and occupancy.</P>
                    <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="s50,16,16,13,14,10,xs36">
                        <TTITLE>Table 4—Proposed Critical Habitat Units for Florida Prairie-Clover, Including Area, Area by Land Ownership, and Occupancy</TTITLE>
                        <TDESC>[All areas rounded to the nearest whole acre (ac) and hectare (ha)]</TDESC>
                        <BOXHD>
                            <CHED H="1">Unit</CHED>
                            <CHED H="1">
                                Total ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                Federal ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                State ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                County ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">
                                Private/other ac
                                <LI>(ha)</LI>
                            </CHED>
                            <CHED H="1">Occupied</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">FPC1—Big Cypress National Preserve</ENT>
                            <ENT>169,885 (68,750)</ENT>
                            <ENT>146,014 (59,090)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>22,411 (9,070)</ENT>
                            <ENT>1,460 (591)</ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FPC2—Everglades National Park</ENT>
                            <ENT>8,728 (3,532)</ENT>
                            <ENT>8,595 (3,478)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>133 (54)</ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FPC3—USDA</ENT>
                            <ENT>630 (255)</ENT>
                            <ENT>145 (58)</ENT>
                            <ENT>253 (103)</ENT>
                            <ENT>192 (78)</ENT>
                            <ENT>40 (16)</ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">FPC4—Crandon Park</ENT>
                            <ENT>57 (23)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>57 (23)</ENT>
                            <ENT>0 (0)</ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="03">Total</ENT>
                            <ENT>179,300 (72,560)</ENT>
                            <ENT>154,754 (62,627)</ENT>
                            <ENT>253 (103)</ENT>
                            <ENT>22,660 (9,170)</ENT>
                            <ENT>1,633 (661)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Percent of Total</ENT>
                            <ENT/>
                            <ENT>86%</ENT>
                            <ENT>1%</ENT>
                            <ENT>13%</ENT>
                            <ENT>1%</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding or minor mapping discrepancies.
                        </TNOTE>
                    </GPOTABLE>
                    <P>Approximately 4.6 percent of the lands (8,310 ac (3,363 ha)) contained within units proposed as critical habitat for Florida prairie-clover are designated critical habitat for other federally listed species.</P>
                    <P>We present brief descriptions of the proposed critical habitat units and the justification for why they meet the definition of critical habitat for Florida prairie-clover, below. All proposed critical habitat units were occupied at the time of listing and are currently occupied. All units contain all the physical or biological features, including suitable climate, hydrology, substrate, associated native plant species, and disturbance regimes, essential to the conservation of the species.</P>
                    <HD SOURCE="HD3">Unit FPC1: Big Cypress National Preserve, Collier, Miami-Dade, and Monroe Counties, Florida</HD>
                    <P>
                        Unit FPC1 consists of approximately 169,885 ac (68,750 ha) in Collier, Miami-Dade, and Monroe County. The unit is comprised of Federal lands in BCNP (146,014 ac (59,090 ha)), County land (22,411 ac (9,070 ha), and parcels in private or other ownership (1,460 ac (591 ha)).
                        <PRTPAGE P="62582"/>
                    </P>
                    <P>Special management considerations or protection may be required within this unit to address threats of nonnative plant and animal species, lack of fire, off-road vehicle use, oil and gas exploration and extraction, and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Florida prairie-clover.</P>
                    <P>This unit is part of lands within BCNP. Within this unit, as part of their 2019 Fire Management Plan (NPS 2019), the NPS conducts nonnative species control and prescribed fire in areas that support or could support Florida prairie-clover.</P>
                    <P>Unit FPC1 does not contain previously designated critical habitat. The federally threatened eastern indigo snake, federally endangered Florida panther, and federally endangered Florida bonneted bat occur in this unit.</P>
                    <HD SOURCE="HD3">Unit FPC2: Everglades National Park, Miami-Dade County, Florida</HD>
                    <P>Unit FPC2 consists of approximately 8,728 ac (3,532 ha) in Miami-Dade County. The unit is comprised of Federal lands in ENP (8,595 ac (3,478 ha) and parcels in private or other ownership (133 ac (54 ha)). The unit includes Long Pine Key and some of the surrounding areas in ENP.</P>
                    <P>Special management considerations or protection may be required within this unit to address threats of nonnative plant and animal species, lack of fire, and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Florida prairie-clover.</P>
                    <P>This unit is part of lands within ENP. Within this unit, as part of their General Management Plan (NPS 2015), the NPS conducts nonnative species control and prescribed fire in areas that support or could support pineland sandmat. Most (91.6 percent) of unit FPC2 is designated critical habitat for the federally endangered Bartram's scrub-hairstreak and Florida leafwing butterflies. The federally threatened eastern indigo snake, federally endangered Florida panther, and federally endangered Florida bonneted bat occur in this unit.</P>
                    <HD SOURCE="HD3">Unit FPC3: USDA Subtropical Horticultural Research Station and Surrounding Areas, Miami-Dade County, Florida</HD>
                    <P>Unit FPC3 consists of approximately 630 ac (255 ha) of habitat in Miami-Dade County. The unit is comprised of Federal lands within the USDA Subtropical Horticultural Research Station (145 ac (58 ha)); State lands within the R. Hardy Matheson Preserve, Ludlam Pineland, Deering Estate at Cutler, and Deering Estate South Addition (253 ac (103 ha)); County lands within Bill Sadowski Park and Matheson Hammock (192 ac (78 ha)); and parcels in private ownership (40 ac (16 ha)).</P>
                    <P>Special management considerations or protection may be required within this unit to address threats of nonnative plant and animal species, lack of fire, and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Florida prairie-clover.</P>
                    <P>The entirety of unit FPC3 is designated critical habitat for the federally endangered Carter's small-flowered flax and Florida brickell-bush. The federally threatened eastern indigo snake occurs in this unit.</P>
                    <HD SOURCE="HD3">Unit FPC4: Crandon Park, Miami-Dade County, Florida</HD>
                    <P>Unit FPC4 consists of approximately 57 ac (23 ha) in Miami-Dade County. The unit is comprised entirely of land owned by Miami-Dade County. The unit includes coastal berm and rockland hammock on the east side of County Road 913 to the shoreline, from the vicinity of the Marjorie Stoneman Douglas Biscayne Nature Center to near the northern tip of the island.</P>
                    <P>Special management considerations or protection may be required within this unit to address threats of nonnative plant and animal species, lack of fire, and sea level rise. Nonnative species control, prescribed fire, and mechanical vegetation treatments are all actions that help improve habitat that supports Florida prairie-clover.</P>
                    <P>Unit FPC4 does not contain previously designated critical habitat. The federally threatened eastern indigo snake occurs in this unit.</P>
                    <HD SOURCE="HD1">Effects of Critical Habitat Designation</HD>
                    <HD SOURCE="HD2">Section 7 Consultation</HD>
                    <P>Section 7(a)(2) of the Act requires Federal agencies, including the Service, to ensure that any action they fund, authorize, or carry out is not likely to jeopardize the continued existence of any endangered species or threatened species or result in the destruction or adverse modification of designated critical habitat of such species. In addition, section 7(a)(4) of the Act requires Federal agencies to confer with the Service on any agency action which is likely to jeopardize the continued existence of any species proposed to be listed under the Act or result in the destruction or adverse modification of proposed critical habitat.</P>
                    <P>We published a final rule revising the definition of destruction or adverse modification on February 11, 2016 (81 FR 7214). (We also published a revised definition after that (on August 27, 2019)) Destruction or adverse modification means a direct or indirect alteration that appreciably diminishes the value of critical habitat for the conservation of a listed species. Such alterations may include, but are not limited to, those that alter the physical or biological features essential to the conservation of a species or that preclude or significantly delay development of such features.</P>
                    <P>
                        If a Federal action may affect a listed species or its critical habitat, the responsible Federal agency (action agency) must enter into consultation with us. Examples of actions that are subject to the section 7 consultation process are actions on State, Tribal, local, or private lands that require a Federal permit (such as a permit from the U.S. Army Corps of Engineers under section 404 of the Clean Water Act (33 U.S.C. 1251 
                        <E T="03">et seq.</E>
                        ) or a permit from the Service under section 10 of the Act) or that involve some other Federal action (such as funding from the Federal Highway Administration, Federal Aviation Administration, or the Federal Emergency Management Agency). Federal actions not affecting listed species or critical habitat—and actions on State, Tribal, local, or private lands that are not federally funded, authorized, or carried out by a Federal agency—do not require section 7 consultation.
                    </P>
                    <P>Compliance with the requirements of section 7(a)(2) is documented through our issuance of:</P>
                    <P>(1) A concurrence letter for Federal actions that may affect, but are not likely to adversely affect, listed species or critical habitat; or</P>
                    <P>(2) A biological opinion for Federal actions that may affect, and are likely to adversely affect, listed species or critical habitat.</P>
                    <P>When we issue a biological opinion concluding that a project is likely to jeopardize the continued existence of a listed species and/or destroy or adversely modify critical habitat, we provide reasonable and prudent alternatives to the project, if any are identifiable, that would avoid the likelihood of jeopardy and/or destruction or adverse modification of critical habitat. We define “reasonable and prudent alternatives” (at 50 CFR 402.02) as alternative actions identified during consultation that:</P>
                    <P>
                        (1) Can be implemented in a manner consistent with the intended purpose of the action,
                        <PRTPAGE P="62583"/>
                    </P>
                    <P>(2) Can be implemented consistent with the scope of the Federal agency's legal authority and jurisdiction,</P>
                    <P>(3) Are economically and technologically feasible, and</P>
                    <P>(4) Would, in the Service Director's opinion, avoid the likelihood of jeopardizing the continued existence of the listed species and/or avoid the likelihood of destroying or adversely modifying critical habitat.</P>
                    <P>Reasonable and prudent alternatives can vary from slight project modifications to extensive redesign or relocation of the project. Costs associated with implementing a reasonable and prudent alternative are similarly variable.</P>
                    <P>Regulations at 50 CFR 402.16 set forth requirements for Federal agencies to reinitiate formal consultation on previously reviewed actions. These requirements apply when the Federal agency has retained discretionary involvement or control over the action (or the agency's discretionary involvement or control is authorized by law) and, subsequent to the previous consultation: (a) if the amount or extent of taking specified in the incidental take statement is exceeded; (b) if new information reveals effects of the action that may affect listed species or critical habitat in a manner or to an extent not previously considered; (c) if the identified action is subsequently modified in a manner that causes an effect to the listed species or critical habitat that was not considered in the biological opinion; or (d) if a new species is listed or critical habitat designated that may be affected by the identified action. In such situations, Federal agencies sometimes may need to request reinitiation of consultation with us, but Congress also enacted some exceptions in 2018 to the requirement to reinitiate consultation on certain land management plans on the basis of a new species listing or new designation of critical habitat that may be affected by the subject Federal action (see the Consolidated Appropriations Act, 2018 (Pub. L. 115-141), Division O, 132 Stat. 1059 (2018)).</P>
                    <HD SOURCE="HD2">Application of the “Destruction or Adverse Modification” Standard</HD>
                    <P>The key factor related to the destruction or adverse modification determination is whether implementation of the proposed Federal action directly or indirectly alters the designated critical habitat in a way that appreciably diminishes the value of the critical habitat for the conservation of the listed species. As discussed above, the role of critical habitat is to support physical or biological features essential to the conservation of a listed species and provide for the conservation of the species.</P>
                    <P>Section 4(b)(8) of the Act requires us to briefly evaluate and describe, in any proposed or final regulation that designates critical habitat, activities involving a Federal action that may violate section 7(a)(2) of the Act by destroying or adversely modifying such habitat, or that may be affected by such designation.</P>
                    <P>Activities that we may, during a consultation under section 7(a)(2) of the Act, find are likely to destroy or adversely modify critical habitat for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover include, but are not limited to:</P>
                    <P>(1) Actions that would significantly alter the hydrology or substrate, such as ditching or filling. Such activities may include, but are not limited to, road construction or maintenance, and residential, commercial, or recreational development.</P>
                    <P>(2) Actions that would significantly alter vegetation structure or composition, such as clearing vegetation for construction of roads, residential and commercial development, recreational facilities, and trails.</P>
                    <P>(3) Actions that would introduce nonnative species that would significantly alter vegetation structure or composition. Such activities may include, but are not limited to, residential and commercial development and road construction.</P>
                    <HD SOURCE="HD1">Exemptions</HD>
                    <HD SOURCE="HD2">Application of Section 4(a)(3) of the Act</HD>
                    <P>Section 4(a)(3)(B)(i) of the Act (16 U.S.C. 1533(a)(3)(B)(i)) provides that the Secretary shall not designate as critical habitat any lands or other geographical areas owned or controlled by the Department of Defense (DOD), or designated for its use, that are subject to an integrated natural resources management plan (INRMP) prepared under section 101 of the Sikes Act Improvement Act of 1997 (16 U.S.C. 670a) (Sikes Act), if the Secretary determines in writing that such plan provides a benefit to the species for which critical habitat is proposed for designation. No DOD lands with a completed INRMP are within the proposed critical habitat designations for Everglades bully, Florida pineland crabgrass, pineland sandmat, or Florida prairie-clover.</P>
                    <HD SOURCE="HD1">Consideration of Impacts Under Section 4(b)(2) of the Act</HD>
                    <P>Section 4(b)(2) of the Act states that the Secretary shall designate and make revisions to critical habitat on the basis of the best available scientific data after taking into consideration the economic impact, national security impact, and any other relevant impact of specifying any particular area as critical habitat. The Secretary may exclude an area from designated critical habitat based on economic impacts, impacts on national security, or any other relevant impacts. Exclusion decisions are governed by the regulations at 50 CFR 424.19 and the Policy Regarding Implementation of Section 4(b)(2) of the Endangered Species Act (hereafter, the “2016 Policy”; 81 FR 7226, February 11, 2016), both of which were developed jointly with the National Marine Fisheries Service (NMFS). We also refer to a 2008 Department of the Interior Solicitor's opinion entitled, “The Secretary's Authority to Exclude Areas from a Critical Habitat Designation under Section 4(b)(2) of the Endangered Species Act” (M-37016). We explain each decision to exclude areas, as well as decisions not to exclude, to demonstrate that the decision is reasonable.</P>
                    <P>In considering whether to exclude a particular area from the designation, we identify the benefits of including the area in the designation, identify the benefits of excluding the area from the designation, and evaluate whether the benefits of exclusion outweigh the benefits of inclusion. If the analysis indicates that the benefits of exclusion outweigh the benefits of inclusion, the Secretary may exercise discretion to exclude the area only if such exclusion would not result in the extinction of the species. In making the determination to exclude a particular area, the statute on its face, as well as the legislative history, are clear that the Secretary has broad discretion regarding which factor(s) to use and how much weight to give to any factor. We describe below the process that we undertook for taking into consideration each category of impacts and our analyses of the relevant impacts.</P>
                    <HD SOURCE="HD2">Consideration of Economic Impacts</HD>
                    <P>
                        Section 4(b)(2) of the Act and its implementing regulations require that we consider the economic impact that may result from a designation of critical habitat. To assess the probable economic impacts of a designation, we must first evaluate specific land uses or activities and projects that may occur in the area of the critical habitat. We then must evaluate the impacts that a specific critical habitat designation may have on restricting or modifying specific activities for the benefit of the species and its habitat within the areas 
                        <PRTPAGE P="62584"/>
                        proposed. We then identify which conservation efforts may be the result of the species being listed under the Act versus those attributed solely to the designation of critical habitat for this particular species. The probable economic impact of a proposed critical habitat designation is analyzed by comparing scenarios both “with critical habitat” and “without critical habitat.”
                    </P>
                    <P>
                        The “without critical habitat” scenario represents the baseline for the analysis, which includes the existing regulatory and socio-economic burden imposed on landowners, managers, or other resource users potentially affected by the designation of critical habitat (
                        <E T="03">e.g.,</E>
                         under the Federal listing as well as other Federal, State, and local regulations). The baseline, therefore, represents the costs of all efforts attributable to the listing of the species under the Act (
                        <E T="03">i.e.,</E>
                         conservation of the species and its habitat incurred regardless of whether critical habitat is designated). The “with critical habitat” scenario describes the incremental impacts associated specifically with the designation of critical habitat for the species. The incremental conservation efforts and associated impacts would not be expected without the designation of critical habitat for the species. In other words, the incremental costs are those attributable solely to the designation of critical habitat, above and beyond the baseline costs. These are the costs we use when evaluating the benefits of inclusion and exclusion of particular areas from the final designation of critical habitat should we choose to conduct a discretionary 4(b)(2) exclusion analysis.
                    </P>
                    <P>Executive Orders (E.O.s) 12866 and 13563 direct Federal agencies to assess the costs and benefits of available regulatory alternatives in quantitative (to the extent feasible) and qualitative terms. Consistent with the E.O. regulatory analysis requirements, our effects analysis under the Act may take into consideration impacts to both directly and indirectly affected entities, where practicable and reasonable. If sufficient data are available, we assess to the extent practicable the probable impacts to both directly and indirectly affected entities. Section 3(f) of E.O. 12866 identifies four criteria when a regulation is considered a “significant” rulemaking, and requires additional analysis, review, and approval if met. The criterion relevant here is whether the designation of critical habitat may have an economic effect of greater than $100 million in any given year (section 3(f)(1)). Therefore, our consideration of economic impacts uses a screening analysis to assess whether a designation of critical habitat for these species is likely to exceed the economically significant threshold.</P>
                    <P>
                        For these particular designations, we developed an incremental effects memorandum (IEM) considering the probable incremental economic impacts that may result from the proposed designations of critical habitat. The information contained in our IEM was then used to develop a screening analysis of the probable effects of the designation of critical habitat for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover (IEc 2021, entire). We began by conducting a screening analysis of the proposed designations of critical habitat in order to focus our analysis on the key factors that are likely to result in incremental economic impacts. The purpose of the screening analysis is to filter out particular geographic areas of critical habitat that are already subject to such protections and are, therefore, unlikely to incur incremental economic impacts. In particular, the screening analysis considers baseline costs (
                        <E T="03">i.e.,</E>
                         absent critical habitat designation) and includes probable economic impacts where land and water use may be subject to conservation plans, land management plans, best management practices, or regulations that protect the habitat area as a result of the Federal listing status of the species. Ultimately, the screening analysis allows us to focus our analysis on evaluating the specific areas or sectors that may incur probable incremental economic impacts as a result of the designation. The presence of the listed species in occupied areas of critical habitat means that any destruction or adverse modification of those areas is also likely to jeopardize the continued existence of the species. Therefore, designating occupied areas as critical habitat typically causes little if any incremental impacts above and beyond the impacts of listing the species. Accordingly, the screening analysis focuses on areas of unoccupied critical habitat. The screening analysis also assesses whether units are unoccupied by the species and thus may require additional management or conservation efforts as a result of the critical habitat designation for the species; these additional efforts may incur incremental economic impacts. This screening analysis combined with the information contained in our IEM are what we consider our draft economic analysis (DEA) of the proposed critical habitat designations for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover; our DEA is summarized in the narrative below.
                    </P>
                    <P>As part of our screening analysis, we considered the types of economic activities that are likely to occur within the areas likely affected by the critical habitat designations. In our evaluation of the probable incremental economic impacts that may result from the proposed designations of critical habitat for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover, first we identified, in the IEM dated August 30, 2021, probable incremental economic impacts associated with the following categories of activities:</P>
                    <P>(1) Federal lands management (National Park Service, U.S. Fish and Wildlife Service, National Oceanic and Atmospheric Administration, U.S. Coast Guard, U.S. Army Corps of Engineers);</P>
                    <P>(2) Roadway and bridge construction and maintenance;</P>
                    <P>(3) Oil and gas exploration and extraction;</P>
                    <P>(4) Commercial or residential development; and</P>
                    <P>(5) Recreation (including construction and maintenance of recreation infrastructure).</P>
                    <P>We considered each industry or category individually. Additionally, we considered whether their activities have any Federal involvement. Critical habitat designation generally will not affect activities that do not have any Federal involvement; designation of critical habitat only affects activities conducted, funded, permitted, or authorized by Federal agencies. In areas where Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover are present, Federal agencies already are required to consult with the Service under section 7 of the Act on activities they authorize, fund, or carry out that may affect the species. If we finalize this proposed critical habitat designation, consultations to avoid the destruction or adverse modification of critical habitat would be incorporated into the existing consultation process.</P>
                    <P>
                        In our IEM, we attempted to clarify the distinction between the effects that will result from the species being listed and those attributable to the critical habitat designation (
                        <E T="03">i.e.,</E>
                         difference between the jeopardy and adverse modification standards) for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover. Because the designation of critical habitat for these species is being proposed several years after these species were listed under the Act, data from our consultation history are available to help us discern which 
                        <PRTPAGE P="62585"/>
                        conservation efforts are attributable to the species being listed and those which will result solely from the designation of critical habitat. The following specific circumstances help to inform our evaluation: (1) The essential physical or biological features identified for critical habitat are the same features essential for the life requisites of the species, and (2) any actions that would likely adversely affect the essential physical or biological features of occupied critical habitat are also likely to adversely affect these species. The IEM outlines our rationale concerning this limited distinction between baseline conservation efforts and incremental impacts of the designation of critical habitat for these species. This evaluation of the incremental effects has been used as the basis to evaluate the probable incremental economic impacts of these proposed designations of critical habitat.
                    </P>
                    <P>Approximately 179,680 ac (72,714 ha) in five units in Collier, Monroe, and Miami-Dade Counties, Florida, are being proposed for designation as critical habitat for the Everglades bully. All five units are occupied by Everglades bully. Approximately 177,879 ac (71,985 ha) in two units in Collier, Monroe, and Miami-Dade Counties, Florida, are being proposed for designation as critical habitat for Florida pineland crabgrass; both units are occupied by the species. Approximately 8,867 ac (3,588 ha) in three units in Miami-Dade County, Florida, are being proposed for designation as critical habitat for pineland sandmat. All three units are occupied by pineland sandmat. Approximately 179,300 ac (72,560 ha) in four units in Collier, Monroe, and Miami-Dade Counties, Florida, are being proposed for designation as critical habitat for Florida prairie-clover. All four units are occupied by Florida prairie-clover. Land ownership across the units for all four plants includes Federal lands (85 percent), State of Florida lands (less than 1 percent), county lands (13 percent), and private lands (1 percent). The majority of the proposed area for Everglades bully, Florida pineland crabgrass, and Florida prairie-clover is within BCNP. Approximately 6 percent of the total proposed designated critical habitat area for all four plants overlaps with existing designated critical habitat for other species.</P>
                    <P>Because all of the area proposed for designation is occupied, most actions that may adversely affect designated critical habitat would also adversely affect the species, and it is unlikely that any additional conservation efforts would be recommended to address the adverse modification standard over and above those recommended as necessary to avoid jeopardizing the continued existence of these four plants. Therefore, only administrative costs are expected in the proposed critical habitat designation. While the analysis for adverse modification of critical habitat will require time and resources by both the Federal action agency and the Service, it is believed that, in most circumstances, these costs would predominantly be administrative in nature and would not be significant.</P>
                    <P>The economic costs of critical habitat designation for these four plants will most likely be limited to additional administrative efforts to consider adverse modification in section 7 consultations. This finding is based on the following factors: (1) All of the proposed critical habitat units for the four plants are considered occupied by the species; (2) a number of additional baseline protections exist for the species due to the presence of other listed species and designated critical habitats, with approximately 6 percent of the proposed critical habitat overlapping with designated critical habitat for other species; and (3) nearly 100 percent of the proposed critical habitat is occupied by other federally listed species, including Florida panther and Florida bonneted bat. Several management plans and conservation plans also provide baseline protections to the species in proposed critical habitat areas.</P>
                    <P>In total, approximately 20 formal consultations, 123 informal consultations, and 29 technical assistance efforts that will include the four plants are anticipated to occur during the next 10 years in proposed critical habitat areas, with costs to the Service and Federal action agencies of approximately $43,600 annually. Although the specific geographic distribution of these costs is uncertain, it appears likely that most costs would occur in the BCNP units, which comprises 94 percent of proposed critical habitat in total for these four plants.</P>
                    <P>Potential private property value effects are possible due to public perception of impacts to private lands. The designation of critical habitat may cause some developers or landowners to perceive that private lands will be subject to use restrictions or litigation from third parties, resulting in costs. However, any costs associated with public perception are speculative and not possible to quantify. Further, only 1 percent of the proposed critical habitat designations is privately owned land, leading to at-most nominal incremental costs arising from changes in public perception of lands included in the designations.</P>
                    <P>The total annual incremental costs of critical habitat designation for these four plants are anticipated to be approximately $43,600 per year, and economic benefits are also anticipated to be small. Therefore, critical habitat designation for these four plants is unlikely to generate costs or benefits exceeding $100 million in a single year, and this rule is unlikely to meet the threshold for an economically significant rule, with regard to costs under E.O. 12866.</P>
                    <P>We are soliciting data and comments from the public on the DEA discussed above, as well as all aspects of this proposed rule and our required determinations. During the development of final designations, we will consider the information presented in the DEA and any additional information on economic impacts received during the public comment period to determine whether any specific areas should be excluded from the final critical habitat designations under authority of section 4(b)(2) and our implementing regulations at 50 CFR 424.19. We may exclude an area from critical habitat if we determine that the benefits of excluding the area outweigh the benefits of including the area, provided the exclusion will not result in the extinction of these species.</P>
                    <HD SOURCE="HD1">Exclusions</HD>
                    <HD SOURCE="HD2">Exclusions Based on Economic Impacts</HD>
                    <P>Under section 4(b)(2) of the Act, we consider the economic impacts of specifying any particular area as critical habitat. In order to consider economic impacts, we prepared an analysis of the probable economic impacts of the proposed critical habitat designations and related factors. At this time, we are not considering any exclusions based on economic impacts.</P>
                    <P>During the development of final designations, we will consider any additional economic impact information received through the public comment period, and as such, areas may be excluded from the final critical habitat designations under section 4(b)(2) of the Act and our implementing regulations at 50 CFR 424.19.</P>
                    <HD SOURCE="HD2">Consideration of National Security Impacts</HD>
                    <P>
                        Section 4(a)(3)(B)(i) of the Act may not cover all DoD lands or areas that pose potential national-security concerns (
                        <E T="03">e.g.,</E>
                         a DOD installation that is in the process of revising its INRMP for a newly listed species or a species 
                        <PRTPAGE P="62586"/>
                        previously not covered). If a particular area is not covered under section 4(a)(3)(B)(i), then national-security or homeland-security concerns are not a factor in the process of determining what areas meet the definition of “critical habitat.” However, the Service must still consider impacts on national security, including homeland security, on those lands or areas not covered by section 4(a)(3)(B)(i) because section 4(b)(2) requires the Service to consider those impacts whenever it designates critical habitat. Accordingly, if DOD, Department of Homeland Security (DHS), or another Federal agency has requested exclusion based on an assertion of national-security or homeland-security concerns, or we have otherwise identified national-security or homeland-security impacts from designating particular areas as critical habitat, we generally have reason to consider excluding those areas.
                    </P>
                    <P>However, we cannot automatically exclude requested areas. When DOD, DHS, or another Federal agency requests exclusion from critical habitat on the basis of national-security or homeland-security impacts, it must provide a reasonably specific justification of an incremental impact on national security that would result from the designation of that specific area as critical habitat. That justification could include demonstration of probable impacts, such as impacts to ongoing border-security patrols and surveillance activities, or a delay in training or facility construction, as a result of compliance with section 7(a)(2) of the Act. If the agency requesting the exclusion does not provide us with a reasonably specific justification, we will contact the agency to recommend that it provide a specific justification or clarification of its concerns relative to the probable incremental impact that could result from the designation. If we conduct an exclusion analysis because the agency provides a reasonably specific justification or because we decide to exercise the discretion to conduct an exclusion analysis, we will defer to the expert judgment of DOD, DHS, or another Federal agency as to: (1) Whether activities on its lands or waters, or its activities on other lands or waters, have national-security or homeland-security implications; (2) the importance of those implications; and (3) the degree to which the cited implications would be adversely affected in the absence of an exclusion. In that circumstance, in conducting a discretionary section 4(b)(2) exclusion analysis, we will give great weight to national-security and homeland-security concerns in analyzing the benefits of exclusion.</P>
                    <P>We have evaluated whether any of the lands within the proposed designations of critical habitat are owned by DOD or DHS or could lead to national-security or homeland-security impacts if designated. Below, we describe the areas within the proposed designations that are owned by DOD or DHS or for which designation could lead to national-security or homeland-security impacts. For each area, we describe the available information indicating whether we have reason to consider excluding the area from the designations. If, during the comment period, we identify or receive information about additional areas for which designations may result in incremental national-security or homeland-security impacts, then we may consider conducting a discretionary exclusion analysis to determine whether to exclude those additional areas under authority of section 4(b)(2) of the Act and our implementing regulations at 50 CFR 424.19.</P>
                    <HD SOURCE="HD3">DHS Land Parcel</HD>
                    <P>We have determined that some lands within the Richmond Pine Rocklands and surrounding areas unit (Unit EB3) of the proposed designation of critical habitat for Everglades bully are owned, managed, or utilized by the U.S. Coast Guard, which is part of the DHS.</P>
                    <P>The U.S. Coast Guard property is separated into two main areas: the Communication Station (COMMSTA) Miami and the Civil Engineering Unit (CEU). The COMMSTA houses transmitting and receiving antennas. The CEU plans and executes projects at regional shore facilities, such as construction and post-disaster assessments.</P>
                    <P>The U.S. Coast Guard parcel contains approximately 100 ac (40 ha) of standing pine rocklands. The remainder of the site, outside of the developed areas, is made up of scraped pine rocklands that are mowed three to four times per year for maintenance of a communications antenna field. While disturbed, this scraped area maintains sand substrate and many native pine rockland species, including documented occurrences of Everglades bully. As of the drafting of this proposed rule, the U.S. Coast Guard parcel has a draft management plan that includes management of pine rockland habitats, including vegetation control and prescribed fire and protection of lands from further development or degradation, and is anticipated to be finalized in late 2022. In addition, the standing pine rockland area is partially managed through an active recovery grant to the Institute for Regional Conservation. Under this grant, up to 39 ac (16 ha) of standing pine rocklands will undergo invasive vegetation control.</P>
                    <P>Based on a review of the specific mission of the U.S. Coast Guard facility in conjunction with the measures and efforts set forth in the draft management plan to preserve pine rockland habitat and protect sensitive and listed species, we have determined that it is unlikely that the critical habitat, if finalized as proposed, would negatively impact the facility or its operations. As a result, we do not anticipate any impact on national security. Consequently, the Secretary does not intend to exercise her discretion to exclude any areas from the final designations based on impacts on national security. We will, however, review this determination, in light of any new information and public comments we receive prior to making a decision in the final rule.</P>
                    <HD SOURCE="HD3">DOD Land Parcel</HD>
                    <P>As discussed above, we have determined that the U.S. Army Corps of Engineers (Corps), a branch of the DOD, retains ownership over a 121-ac (49-ha) parcel in Unit EB3 of the proposed designation of critical habitat for Everglades bully. More than 85 ac (34 ha) of this parcel are forested but not managed for preservation of natural resources. The Corps does not have an INRMP or any specific management plan for the Everglades bully or its habitat covering these lands. Activities conducted on this site are unknown, but we do not anticipate any impact on national security.</P>
                    <P>
                        Following our process for coordinating with Federal partners, we contacted the DOD and DHS about this designation and shared the IEM for their feedback. Neither agency identified any potential national-security impact, nor requested an exclusion from critical habitat based on potential national-security impacts. Consequently, the Secretary does not intend to exercise her discretion to exclude any areas from the final designations based on impacts on national security. However, if through the public comment period we receive information regarding impacts on national security or homeland security from designating particular areas as critical habitat, then as part of developing the final designations of critical habitat, we may consider conducting a discretionary exclusion analysis to determine whether to exclude those areas under authority of section 4(b)(2) of the Act and our 
                        <PRTPAGE P="62587"/>
                        implementing regulations at 50 CFR 424.19.
                    </P>
                    <HD SOURCE="HD2">Consideration of Other Relevant Impacts</HD>
                    <P>Under section 4(b)(2) of the Act, we consider any other relevant impacts, in addition to economic impacts and impacts on national security discussed above. To identify other relevant impacts that may affect the exclusion analysis, we consider a number of factors, including whether there are permitted conservation plans covering the species in the area—such as HCPs, safe harbor agreements (SHAs), or candidate conservation agreements with assurances (CCAAs)—or whether there are non-permitted conservation agreements and partnerships that may be impaired by designation of, or exclusion from, critical habitat. In addition, we look at whether Tribal conservation plans or partnerships, Tribal resources, or government-to-government relationships of the United States with Tribal entities may be affected by the designation. We also consider any State, local, or other impacts that might occur because of the designation. When analyzing other relevant impacts of including a particular area in a designation of critical habitat, we weigh those impacts relative to the conservation value of the particular area. To determine the conservation value of designating a particular area, we consider a number of factors, including, but not limited to, the additional regulatory benefits that the area would receive due to the protection from destruction or adverse modification as a result of actions with a Federal nexus, the educational benefits of mapping essential habitat for recovery of the listed species, and any benefits that may result from a designation due to State or Federal laws that may apply to critical habitat.</P>
                    <P>In the case of Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover, the benefits of critical habitat include public awareness of the presence of these four plant species and the importance of habitat protection, and, where a Federal nexus exists, habitat protection for the four species due to protection from destruction or adverse modification of critical habitat. Continued implementation of an ongoing management plan that provides conservation equal to or more than the protections that result from a critical habitat designation would reduce those benefits of including that specific area in the critical habitat designation.</P>
                    <P>After identifying the benefits of inclusion and the benefits of exclusion, we carefully weigh the two sides to evaluate whether the benefits of exclusion outweigh those of inclusion. If our analysis indicates that the benefits of exclusion outweigh the benefits of inclusion, we then determine whether exclusion would result in extinction of the species. If exclusion of an area from critical habitat will result in extinction, we will not exclude it from the designation.</P>
                    <HD SOURCE="HD3">Private or Other Non-Federal Conservation Plans Related to Permits Under Section 10 of the Act</HD>
                    <P>HCPs for incidental take permits under section 10(a)(1)(B) of the Act provide for partnerships with non-Federal entities to minimize and mitigate impacts to listed species and their habitat. In some cases, HCP permittees agree to do more for the conservation of the species and their habitats on private lands than designation of critical habitat would provide alone. We place great value on the partnerships that are developed during the preparation and implementation of HCPs.</P>
                    <P>CCAAs and SHAs are voluntary agreements designed to conserve candidate and listed species, respectively, on non-Federal lands. In exchange for actions that contribute to the conservation of species on non-Federal lands, participating property owners are covered by an “enhancement of survival” permit under section 10(a)(1)(A) of the Act, which authorizes incidental take of the covered species that may result from implementation of conservation actions, specific land uses, and, in the case of SHAs, the option to return to a baseline condition under the agreements. The Service also provides enrollees assurances that we will not impose further land-, water-, or resource-use restrictions, or require additional commitments of land, water, or finances, beyond those agreed to in the agreements.</P>
                    <P>
                        When we undertake a discretionary section 4(b)(2) exclusion analysis based on permitted conservation plans (
                        <E T="03">e.g.,</E>
                         CCAAs, SHAs, and HCPs), we anticipate consistently excluding such areas if incidental take caused by the activities in those areas is covered by the permit under section 10 of the Act and the CCAA/SHA/HCP meets all of the following three factors (see the 2016 Policy for additional details):
                    </P>
                    <P>a. The permittee is properly implementing the CCAA/SHA/HCP and is expected to continue to do so for the term of the agreement. A CCAA/SHA/HCP is properly implemented if the permittee is and has been fully implementing the commitments and provisions in the CCAA/SHA/HCP, implementing agreement, and permit.</P>
                    <P>b. The species for which critical habitat is being designated is a covered species in the CCAA/SHA/HCP, or very similar in its habitat requirements to a covered species. The recognition that the Services extend to such an agreement depends on the degree to which the conservation measures undertaken in the CCAA/SHA/HCP would also protect the habitat features of the similar species.</P>
                    <P>c. The CCAA/SHA/HCP specifically addresses that species' habitat and meets the conservation needs of the species in the planning area.</P>
                    <P>The proposed critical habitat designations include areas that are covered by the following permitted plan providing for the conservation of Everglades bully: Coral Reef Commons HCP.</P>
                    <P>
                        <E T="03">Coral Reef Commons Habitat Conservation Plan</E>
                        —In preparing this proposal, we have determined that lands associated with the Coral Reef Commons HCP within Unit EB3 for Everglades bully (Richmond Pine Rocklands and surrounding areas) are included within the boundaries of the proposed critical habitat.
                    </P>
                    <P>Coral Reef Commons is a mixed-use community, which consists of 900 apartments, retail stores, restaurants, and parking. In 2017, a HCP and associated permit under section 10 of the Act was developed and issued for the Coral Reef Commons development.</P>
                    <P>As part of the HCP and permit, an approximately 53-ac (21-ha) on-site preserve (same as the area for proposed critical habitat designation) was established under a conservation encumbrance that will be managed in perpetuity for pine rockland habitat and sensitive and listed species, including Everglades bully.</P>
                    <P>
                        The Center for Southeastern Tropical Advanced Remote Sensing (CSTARS) site is an offsite mitigation area for Coral Reef Commons comprised of 57 ac (23 ha). Both the on-site preserve and the off-site mitigation area are being managed to maintain healthy pine rockland habitat through the use of invasive, exotic plant management; mechanical treatment; and prescribed fire. Since initiating the Coral Reef Commons HCP, pine rockland restoration efforts have been conducted within all of the management units in both the on-site preserves and the off-site mitigation area. A second round of prescribed fire began in February 2021. Currently, the on-site preserves meet or exceed the success criteria described in the HCP.
                        <PRTPAGE P="62588"/>
                    </P>
                    <P>Critical habitat within (EB3) that is associated with the Coral Reef Commons HCP is limited to the on-site preserves and off-site mitigation area. Based on a cursory review of the HCP and proposed critical habitat for Everglades bully, we do not anticipate requesting any additional conservation measures for this species beyond those that are currently in place. Therefore, at this time, we are considering excluding those specific lands associated with the Coral Reef Commons HCP that are in the preserve and off-site mitigation area from the final designation of critical habitat for Everglades bully. However, we will more thoroughly review the HCP, its implementation of the conservation measures for Everglades bully and its habitat therein, and public comment on this issue prior to finalizing critical habitat, and, if appropriate, in the final rule, exclude from critical habitat for Everglades bully those lands associated with the Coral Reef Commons HCP that are in the on-site preserves and off-site mitigation area.</P>
                    <P>We have determined that there are no additional HCPs or other management plans for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover.</P>
                    <HD SOURCE="HD3">Tribal Lands</HD>
                    <P>Several Executive Orders, Secretarial Orders, and policies concern working with Tribes. These guidance documents generally confirm our trust responsibilities to Tribes, recognize that Tribes have sovereign authority to control Tribal lands, emphasize the importance of developing partnerships with Tribal governments, and direct the Service to consult with Tribes on a government-to-government basis.</P>
                    <P>
                        A joint Secretarial Order that applies to both the Service and the National Marine Fisheries Service (NMFS)—Secretarial Order 3206, 
                        <E T="03">American Indian Tribal Rights, Federal-Tribal Trust Responsibilities, and the Endangered Species Act</E>
                         (June 5, 1997) (S.O. 3206)—is the most comprehensive of the various guidance documents related to Tribal relationships and Act implementation, and it provides the most detail directly relevant to the designation of critical habitat. In addition to the general direction discussed above, the appendix to S.O. 3206 explicitly recognizes the right of Tribes to participate fully in any listing process that may affect Tribal rights or Tribal trust resources; this includes the designation of critical habitat. Section 3(B)(4) of the appendix requires the Service to consult with affected Tribes “when considering the designation of critical habitat in an area that may impact tribal trust resources, tribally-owned fee lands, or the exercise of tribal rights.” That provision also instructs the Service to avoid including Tribal lands within a critical habitat designation unless the area is essential to conserve a listed species, and it requires the Service to “evaluate and document the extent to which the conservation needs of the listed species can be achieved by limiting the designation to other lands.”
                    </P>
                    <P>Our implementing regulations at 50 CFR 424.19 and the 2016 Policy are consistent with S.O. 3206. When we undertake a discretionary exclusion analysis, in accordance with S.O. 3206 we consult with any Tribe whose Tribal trust resources, Tribally owned fee lands, or Tribal rights may be affected by including any particular areas in the designation, and we evaluate the extent to which the conservation needs of the species can be achieved by limiting the designation to other areas. When we undertake a discretionary 4(b)(2) exclusion analysis, we always consider exclusion of Tribal lands, and give great weight to Tribal concerns in analyzing the benefits of exclusion.</P>
                    <P>
                        However, S.O. 3206 does not override the Act's statutory requirement of designation of critical habitat. As stated above, we must consult with any Tribe when a designation of critical habitat may affect Tribal lands or resources. The Act requires us to identify areas that meet the definition of “critical habitat” (
                        <E T="03">i.e.,</E>
                         areas occupied at the time of listing that contain the essential physical or biological features that may require special management or protection and unoccupied areas that are essential to the conservation of a species), without regard to land ownership. While S.O. 3206 provides important direction, it expressly states that it does not modify the Secretary's statutory authority under the Act or other statutes.
                    </P>
                    <P>There are no Tribal lands in the proposed critical habitat designations for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover.</P>
                    <HD SOURCE="HD1">Summary of Exclusions Considered Under 4(b)(2) of the Act</HD>
                    <P>At this time, we are considering excluding those specific lands associated with the Coral Reef Commons HCP that are in the preserve and off-site mitigation area from the final designation of critical habitat for Everglades bully (unit ES3). In conclusion, we specifically solicit comments on the inclusion or exclusion of such areas.</P>
                    <P>During the development of final designations, we will consider any information currently available or received during the public comment period regarding other relevant impacts of the proposed designations and will determine whether these or any other specific areas should be considered for exclusion from the final critical habitat designations under authority of section 4(b)(2) of the Act and our implementing regulations at 50 CFR 424.19 and the 2016 Policy.</P>
                    <HD SOURCE="HD1">Required Determinations</HD>
                    <HD SOURCE="HD2">Clarity of the Rule</HD>
                    <P>We are required by Executive Orders 12866 and 12988 and by the Presidential Memorandum of June 1, 1998, to write all rules in plain language. This means that each rule we publish must:</P>
                    <P>(1) Be logically organized;</P>
                    <P>(2) Use the active voice to address readers directly;</P>
                    <P>(3) Use clear language rather than jargon;</P>
                    <P>(4) Be divided into short sections and sentences; and</P>
                    <P>(5) Use lists and tables wherever possible.</P>
                    <P>
                        If you feel that we have not met these requirements, send us comments by one of the methods listed in 
                        <E T="02">ADDRESSES</E>
                        . To better help us revise the rule, your comments should be as specific as possible. For example, you should tell us the numbers of the sections or paragraphs that are unclearly written, which sections or sentences are too long, the sections where you feel lists or tables would be useful, etc.
                    </P>
                    <HD SOURCE="HD2">Regulatory Planning and Review (Executive Orders 12866 and 13563)</HD>
                    <P>Executive Order 12866 provides that the Office of Information and Regulatory Affairs (OIRA) in the Office of Management and Budget will review all significant rules. OIRA has determined that this rule is not significant.</P>
                    <P>
                        Executive Order 13563 reaffirms the principles of E.O. 12866 while calling for improvements in the nation's regulatory system to promote predictability, to reduce uncertainty, and to use the best, most innovative, and least burdensome tools for achieving regulatory ends. The executive order directs agencies to consider regulatory approaches that reduce burdens and maintain flexibility and freedom of choice for the public where these approaches are relevant, feasible, and consistent with regulatory objectives. E.O. 13563 emphasizes further that regulations must be based on the best available science and that 
                        <PRTPAGE P="62589"/>
                        the rulemaking process must allow for public participation and an open exchange of ideas. We have developed this proposed rule in a manner consistent with these requirements.
                    </P>
                    <HD SOURCE="HD2">Regulatory Flexibility Act (5 U.S.C. 601 et seq.)</HD>
                    <P>
                        Under the Regulatory Flexibility Act (RFA; 5 U.S.C. 601 
                        <E T="03">et seq.</E>
                        ), as amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (SBREFA; 5 U.S.C. 801 
                        <E T="03">et seq.</E>
                        ), whenever an agency is required to publish a notice of rulemaking for any proposed or final rule, it must prepare and make available for public comment a regulatory flexibility analysis that describes the effects of the rule on small entities (
                        <E T="03">i.e.,</E>
                         small businesses, small organizations, and small government jurisdictions). However, no regulatory flexibility analysis is required if the head of the agency certifies the rule will not have a significant economic impact on a substantial number of small entities. The SBREFA amended the RFA to require Federal agencies to provide a certification statement of the factual basis for certifying that the rule will not have a significant economic impact on a substantial number of small entities.
                    </P>
                    <P>According to the Small Business Administration, small entities include small organizations such as independent nonprofit organizations; small governmental jurisdictions, including school boards and city and town governments that serve fewer than 50,000 residents; and small businesses (13 CFR 121.201). Small businesses include manufacturing and mining concerns with fewer than 500 employees, wholesale trade entities with fewer than 100 employees, retail and service businesses with less than $5 million in annual sales, general and heavy construction businesses with less than $27.5 million in annual business, special trade contractors doing less than $11.5 million in annual business, and agricultural businesses with annual sales less than $750,000. To determine if potential economic impacts to these small entities are significant, we considered the types of activities that might trigger regulatory impacts under these proposed designations as well as types of project modifications that may result. In general, the term “significant economic impact” is meant to apply to a typical small business firm's business operations.</P>
                    <P>Under the RFA, as amended, and as understood in light of recent court decisions, Federal agencies are required to evaluate the potential incremental impacts of rulemaking on those entities directly regulated by the rulemaking itself; in other words, the RFA does not require agencies to evaluate the potential impacts to indirectly regulated entities. The regulatory mechanism through which critical habitat protections are realized is section 7 of the Act, which requires Federal agencies, in consultation with the Service, to ensure that any action authorized, funded, or carried out by the agency is not likely to destroy or adversely modify critical habitat. Therefore, under section 7, only Federal action agencies are directly subject to the specific regulatory requirement (avoiding destruction and adverse modification) imposed by critical habitat designation. Consequently, it is our position that only Federal action agencies would be directly regulated if we adopt the proposed critical habitat designations. The RFA does not require evaluation of the potential impacts to entities not directly regulated. Moreover, Federal agencies are not small entities. Therefore, because no small entities would be directly regulated by this rulemaking, the Service certifies that, if made final as proposed, the proposed critical habitat designations will not have a significant economic impact on a substantial number of small entities.</P>
                    <P>In summary, we have considered whether the proposed designations would result in a significant economic impact on a substantial number of small entities. For the above reasons and based on currently available information, we certify that, if made final, the proposed critical habitat designations would not have a significant economic impact on a substantial number of small business entities. Therefore, an initial regulatory flexibility analysis is not required.</P>
                    <HD SOURCE="HD2">Energy Supply, Distribution, or Use—Executive Order 13211</HD>
                    <P>
                        Executive Order 13211 (Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use) requires agencies to prepare Statements of Energy Effects when undertaking certain actions. We do not foresee any energy development projects, supply, distribution, or use that may affect or be affected by the proposed critical habitat for pineland sandmat. There may be energy development projects (
                        <E T="03">i.e.,</E>
                         oil and gas exploration and extraction activities) at BCNP that may affect or be affected by the proposed critical habitat for Everglades bully, Florida pineland crabgrass, and Florida prairie-clover. However, in our evaluation of potential economic impacts, we did not find that the proposed critical habitat designations for Everglades bully, Florida pineland crabgrass, and Florida prairie-clover would significantly affect energy supplies, distribution, or use. Therefore, this action is not a significant energy action, and no Statement of Energy Effects is required.
                    </P>
                    <HD SOURCE="HD2">Unfunded Mandates Reform Act (2 U.S.C. 1501 et seq.)</HD>
                    <P>
                        In accordance with the Unfunded Mandates Reform Act (2 U.S.C. 1501 
                        <E T="03">et seq.</E>
                        ), we make the following finding:
                    </P>
                    <P>(1) This proposed rule would not produce a Federal mandate. In general, a Federal mandate is a provision in legislation, statute, or regulation that would impose an enforceable duty upon State, local, or tribal governments, or the private sector, and includes both “Federal intergovernmental mandates” and “Federal private sector mandates.” These terms are defined in 2 U.S.C. 658(5)-(7). “Federal intergovernmental mandate” includes a regulation that “would impose an enforceable duty upon State, local, or tribal governments” with two exceptions. It excludes “a condition of Federal assistance.” It also excludes “a duty arising from participation in a voluntary Federal program,” unless the regulation “relates to a then-existing Federal program under which $500,000,000 or more is provided annually to State, local, and tribal governments under entitlement authority,” if the provision would “increase the stringency of conditions of assistance” or “place caps upon, or otherwise decrease, the Federal Government's responsibility to provide funding,” and the State, local, or tribal governments “lack authority” to adjust accordingly. At the time of enactment, these entitlement programs were: Medicaid; Aid to Families with Dependent Children work programs; Child Nutrition; Food Stamps; Social Services Block Grants; Vocational Rehabilitation State Grants; Foster Care, Adoption Assistance, and Independent Living; Family Support Welfare Services; and Child Support Enforcement. “Federal private sector mandate” includes a regulation that “would impose an enforceable duty upon the private sector, except (i) a condition of Federal assistance or (ii) a duty arising from participation in a voluntary Federal program.”</P>
                    <P>
                        The designation of critical habitat does not impose a legally binding duty on non-Federal Government entities or private parties. Under the Act, the only regulatory effect is that Federal agencies must ensure that their actions do not destroy or adversely modify critical habitat under section 7. While non-Federal entities that receive Federal 
                        <PRTPAGE P="62590"/>
                        funding, assistance, or permits, or that otherwise require approval or authorization from a Federal agency for an action, may be indirectly impacted by the designation of critical habitat, the legally binding duty to avoid destruction or adverse modification of critical habitat rests squarely on the Federal agency. Furthermore, to the extent that non-Federal entities are indirectly impacted because they receive Federal assistance or participate in a voluntary Federal aid program, the Unfunded Mandates Reform Act would not apply, nor would critical habitat shift the costs of the large entitlement programs listed above onto State governments.
                    </P>
                    <P>(2) We do not believe that this rule would significantly or uniquely affect small governments. The government lands being proposed for critical habitat designation are owned by the State of Florida, Miami-Dade and Monroe Counties, and numerous Federal agencies (USCG, NOAA, Corps, FBP, USDA, and NPS). None of these government entities fit the definition of “small governmental jurisdiction.” Therefore, a Small Government Agency Plan is not required.</P>
                    <HD SOURCE="HD2">Takings—Executive Order 12630</HD>
                    <P>In accordance with E.O. 12630 (Government Actions and Interference with Constitutionally Protected Private Property Rights), we have analyzed the potential takings implications of designating critical habitat for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover in a takings implications assessment. The Act does not authorize the Service to regulate private actions on private lands or confiscate private property as a result of critical habitat designation. Designation of critical habitat does not affect land ownership, or establish any closures, or restrictions on use of or access to the designated areas. Furthermore, the designation of critical habitat does not affect landowner actions that do not require Federal funding or permits, nor does it preclude development of habitat conservation programs or issuance of incidental take permits to permit actions that do require Federal funding or permits to go forward. However, Federal agencies are prohibited from carrying out, funding, or authorizing actions that would destroy or adversely modify critical habitat. A takings implications assessment has been completed for the proposed designations of critical habitat for Everglades bully, Florida pineland crabgrass, pineland sandmat, and Florida prairie-clover, and it concludes that, if adopted, the designations of critical habitat do not pose significant takings implications for lands within or affected by the designations.</P>
                    <HD SOURCE="HD2">Federalism—Executive Order 13132</HD>
                    <P>In accordance with E.O. 13132 (federalism), this proposed rule does not have significant federalism effects. A federalism summary impact statement is not required. In keeping with Department of the Interior and Department of Commerce policy, we requested information from, and coordinated development of the proposed critical habitat designations with, appropriate State resource agencies. From a federalism perspective, the designation of critical habitat directly affects only the responsibilities of Federal agencies. The Act imposes no other duties with respect to critical habitat, either for States and local governments, or for anyone else. As a result, the proposed rule does not have substantial direct effects either on the States, or on the relationship between the Federal government and the States, or on the distribution of powers and responsibilities among the various levels of government. The proposed designations may have some benefit to these governments because the areas that contain the features essential to the conservation of the species are more clearly defined, and the physical or biological features of the habitat necessary for the conservation of the species are specifically identified. This information does not alter where and what federally sponsored activities may occur. However, it may assist State and local governments in long-range planning because they no longer have to wait for case-by-case section 7 consultations to occur.</P>
                    <P>Where State and local governments require approval or authorization from a Federal agency for actions that may affect critical habitat, consultation under section 7(a)(2) of the Act would be required. While non-Federal entities that receive Federal funding, assistance, or permits, or that otherwise require approval or authorization from a Federal agency for an action, may be indirectly impacted by the designation of critical habitat, the legally binding duty to avoid destruction or adverse modification of critical habitat rests squarely on the Federal agency.</P>
                    <HD SOURCE="HD2">Civil Justice Reform—Executive Order 12988</HD>
                    <P>In accordance with E.O. 12988 (Civil Justice Reform), the Office of the Solicitor has determined that this proposed rule would not unduly burden the judicial system and that it meets the requirements of sections 3(a) and 3(b)(2) of the order. We have proposed designating critical habitat in accordance with the provisions of the Act. To assist the public in understanding the habitat needs of the species, this proposed rule identifies the physical or biological features essential to the conservation of the species. The proposed areas of critical habitat are presented on maps, and the proposed rule provides several options for the interested public to obtain more detailed location information, if desired.</P>
                    <HD SOURCE="HD2">Paperwork Reduction Act of 1995 (44 U.S.C. 3501 et seq.)</HD>
                    <P>
                        This rulemaking does not contain information collection requirements, and a submission to the Office of Management and Budget (OMB) under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                        ) is not required. We may not conduct or sponsor and you are not required to respond to a collection of information unless it displays a currently valid OMB control number.
                    </P>
                    <HD SOURCE="HD2">National Environmental Policy Act (42 U.S.C. 4321 et seq.)</HD>
                    <P>
                        It is our position that, outside the jurisdiction of the U.S. Court of Appeals for the Tenth Circuit, we do not need to prepare environmental analyses pursuant to the National Environmental Policy Act (NEPA; 42 U.S.C. 4321 
                        <E T="03">et seq.</E>
                        ) in connection with designating critical habitat under the Act. We published a notice outlining our reasons for this determination in the 
                        <E T="04">Federal Register</E>
                         on October 25, 1983 (48 FR 49244). This position was upheld by the U.S. Court of Appeals for the Ninth Circuit (
                        <E T="03">Douglas County</E>
                         v. 
                        <E T="03">Babbitt,</E>
                         48 F.3d 1495 (9th Cir. 1995)).
                    </P>
                    <HD SOURCE="HD2">Government-to-Government Relationship With Tribes</HD>
                    <P>
                        In accordance with the President's memorandum of April 29, 1994 (Government-to-Government Relations with Native American Tribal Governments; 59 FR 22951), Executive Order 13175 (Consultation and Coordination with Indian Tribal Governments), and the Department of the Interior's manual at 512 DM 2, we readily acknowledge our responsibility to communicate meaningfully with recognized Federal Tribes on a government-to-government basis. In accordance with Secretarial Order 3206 of June 5, 1997 (American Indian Tribal Rights, Federal-Tribal Trust Responsibilities, and the Endangered Species Act), we readily acknowledge our responsibilities to work directly with Tribes in developing programs for healthy ecosystems, to acknowledge that 
                        <PRTPAGE P="62591"/>
                        Tribal lands are not subject to the same controls as Federal public lands, to remain sensitive to Indian culture, and to make information available to Tribes.
                    </P>
                    <P>As discussed above (see “Tribal Lands” under Exclusions), we have determined that no Tribal lands fall within the boundaries of the proposed critical habitat designations for Everglades bully, Florida pineland crabgrass, pineland sandmat, or Florida prairie-clover, so no Tribal lands would be affected by the proposed designations of critical habitat for these species.</P>
                    <HD SOURCE="HD1">References Cited</HD>
                    <P>
                        A complete list of references cited in this rulemaking is available on the internet at 
                        <E T="03">https://www.regulations.gov</E>
                         and upon request from the Florida Ecological Services Field Office (see 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        ).
                    </P>
                    <HD SOURCE="HD1">Authors</HD>
                    <P>The primary authors of this proposed rule are the staff members of the Fish and Wildlife Service's Florida Ecological Services Field Office.</P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 50 CFR Part 17</HD>
                        <P>Endangered and threatened species, Exports, Imports, Plants, Reporting and recordkeeping requirements, Transportation, Wildlife.</P>
                    </LSTSUB>
                    <HD SOURCE="HD1">Signing Authority</HD>
                    <P>Martha Williams, Director of the U.S. Fish and Wildlife Service, approved this action on September 20, 2022, for publication. On September 30, 2022, Martha Williams authorized the undersigned to sign the document electronically and submit it to the Office of the Federal Register for publication as an official document of the U.S. Fish and Wildlife Service.</P>
                    <HD SOURCE="HD1">Proposed Regulation Promulgation</HD>
                    <P>Accordingly, we propose to amend part 17, subchapter B of chapter I, title 50 of the Code of Federal Regulations, as set forth below:</P>
                    <PART>
                        <HD SOURCE="HED">PART 17—ENDANGERED AND THREATENED WILDLIFE AND PLANTS</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 17 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 16 U.S.C. 1361-1407; 1531-1544; 4201-4245, unless otherwise noted.</P>
                    </AUTH>
                    <AMDPAR>
                        2. In § 17.12, amend paragraph (h) by revising the entries for “
                        <E T="03">Chamaesyce deltoidea</E>
                         ssp. 
                        <E T="03">pinetorum</E>
                        ”, “
                        <E T="03">Dalea carthagenensis</E>
                         var. 
                        <E T="03">floridana</E>
                        ”, “
                        <E T="03">Digitaria pauciflora</E>
                        ”, and “
                        <E T="03">Sideroxylon reclinatum</E>
                         ssp. 
                        <E T="03">austrofloridense</E>
                        ” in the List of Endangered and Threatened Plants under FLOWERING PLANTS, to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 17.12</SECTNO>
                        <SUBJECT>Endangered and threatened plants.</SUBJECT>
                        <STARS/>
                        <P>(h) * * *</P>
                        <GPOTABLE COLS="5" OPTS="L1,i1" CDEF="s50,r50,r50,10C,r50">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1">Scientific name</CHED>
                                <CHED H="1">Common name</CHED>
                                <CHED H="1">Where listed</CHED>
                                <CHED H="1">Status</CHED>
                                <CHED H="1">Listing citations and applicable rules</CHED>
                            </BOXHD>
                            <ROW EXPSTB="04" RUL="s">
                                <ENT I="21">
                                    <E T="04">Flowering Plants</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Chamaesyce deltoidea</E>
                                     ssp. 
                                    <E T="03">pinetorum</E>
                                </ENT>
                                <ENT>Pineland sandmat</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>T</ENT>
                                <ENT>
                                    82 FR 46691, 10/6/2017; 50 CFR 17.96(a).
                                    <SU>CH</SU>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Dalea carthagenensis</E>
                                     var.
                                    <E T="03"> floridana</E>
                                </ENT>
                                <ENT>Florida prairie-clover</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    82 FR 46691, 10/6/2017; 50 CFR 17.96(a).
                                    <SU>CH</SU>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Digitaria pauciflora</E>
                                </ENT>
                                <ENT>Florida pineland crabgrass</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>T</ENT>
                                <ENT>
                                    82 FR 46691, 10/6/2017; 50 CFR 17.96(a).
                                    <SU>CH</SU>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Sideroxylon reclinatum</E>
                                     ssp.
                                    <E T="03"> austrofloridense</E>
                                </ENT>
                                <ENT>Everglades bully</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>T</ENT>
                                <ENT>
                                    82 FR 46691, 10/6/2017; 50 CFR 17.96(a).
                                    <SU>CH</SU>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                        </GPOTABLE>
                    </SECTION>
                    <AMDPAR>3. In § 17.96, amend paragraph (a) by:</AMDPAR>
                    <AMDPAR>
                        a. Adding an entry for “Family Euphorbiaceae: 
                        <E T="03">Chamaesyce deltoidea</E>
                         ssp. 
                        <E T="03">pinetorum,</E>
                         (pineland sandmat)” following the entry for “Family Ericaceae: 
                        <E T="03">Gonocalyx concolor”;</E>
                    </AMDPAR>
                    <AMDPAR>
                        b. Adding an entry for “Family Fabaceae: 
                        <E T="03">Dalea carthagenensis</E>
                         var. 
                        <E T="03">floridana</E>
                         (Florida prairie-clover)” following the entry for “Family Fabaceae: 
                        <E T="03">Astragalus pycnostachyus</E>
                         var. 
                        <E T="03">lanosissimus</E>
                         (Ventura Marsh milk-vetch)”;
                    </AMDPAR>
                    <AMDPAR>
                        c. Adding an entry for “Family Poaceae: 
                        <E T="03">Digitaria pauciflora</E>
                         (Florida pineland crabgrass)” following the entry for “Family Plantaginaceae: 
                        <E T="03">Penstemon debilis</E>
                         (Parachute penstemon)”; and
                    </AMDPAR>
                    <AMDPAR>
                        d. Adding an entry for “Family Sapotaceae: 
                        <E T="03">Sideroxylon reclinatum</E>
                         ssp. 
                        <E T="03">austrofloridense</E>
                         (Everglades bully)” following the entry for “Family Rubiaceae: 
                        <E T="03">Catesbaea melanocarpa</E>
                         (no common name)”.
                    </AMDPAR>
                    <P>The additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 17.96</SECTNO>
                        <SUBJECT>Critical habitat—plants.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Flowering plants.</E>
                        </P>
                        <STARS/>
                        <P>
                            Family Euphorbiaceae: 
                            <E T="03">Chamaesyce deltoidea</E>
                             ssp. 
                            <E T="03">pinetorum</E>
                             (pineland sandmat)
                        </P>
                        <P>(1) Critical habitat units are depicted for Miami-Dade County, Florida, on the maps in this entry.</P>
                        <P>(2) Within these areas, the physical or biological features essential to the conservation of the pineland sandmat are South Florida pine rockland and adjacent ecotonal areas:</P>
                        <P>
                            (i) Consisting of calcareous limestone substrate (often exposed with little soil development) that provides nutritional requirements and suitable growing conditions (
                            <E T="03">e.g.,</E>
                             pH, nutrients, anchoring, and drainage);
                        </P>
                        <P>
                            (ii) Characterized by an open canopy and understory with a high proportion of native pine rockland plant species to 
                            <PRTPAGE P="62592"/>
                            provide for sufficient sunlight to permit growth and flowering;
                        </P>
                        <P>(iii) Subjected to a monthly mean temperature characteristic of the subtropical humid classification in Miami-Dade County and short hydroperiods ranging up to 60 days each year;</P>
                        <P>
                            (iv) Subjected to periodic natural (
                            <E T="03">e.g.,</E>
                             hurricanes, fire) or unnatural (
                            <E T="03">e.g.,</E>
                             prescribed fire) disturbance regimes to maintain open canopy conditions; and
                        </P>
                        <P>(v) Containing the presence of native pollinators for natural pollination and reproduction.</P>
                        <P>(3) Critical habitat does not include human-made structures (such as buildings, aqueducts, runways, roads, and other paved areas) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using ESRI ArcGIS mapping software. The projection used was Albers Conical Equal Area (Florida Geographic Data Library), North American Datum (NAD) 1983 High Accuracy Reference Network (HARN). The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/office/florida-ecological-services,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R4-ES-2022-0125, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) Index map of critical habitat units for pineland sandmat follows: </P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Family Euphorbiaceae: 
                            <E T="03">Chamaesyce deltoidea</E>
                             ssp. 
                            <E T="03">pinetorum</E>
                             (pineland sandmat) paragraph (5)
                        </FP>
                        <BILCOD>BILLING CODE 4333-15-P</BILCOD>
                        <GPH SPAN="3" DEEP="450">
                            <GID>EP14OC22.031</GID>
                        </GPH>
                        <P>(6) PS1: Everglades National Park, Miami-Dade County, Florida.</P>
                        <P>
                            (i) Unit PS1 consists of approximately 7,994 acres (ac) (3,235 hectares (ha)) in Miami-Dade County, Florida. This unit is comprised of lands on Long Pine Key 
                            <PRTPAGE P="62593"/>
                            and surrounding areas in Everglades National Park.
                        </P>
                        <P>(ii) Map of Unit PS1 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 2 to Family Euphorbiaceae: 
                            <E T="03">Chamaesyce deltoidea</E>
                             ssp. 
                            <E T="03">pinetorum</E>
                             (pineland sandmat) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="459">
                            <GID>EP14OC22.032</GID>
                        </GPH>
                        <P>(7) PS2: Camp Owaissa Bauer and surrounding areas, Miami-Dade County, Florida.</P>
                        <P>(i) Unit PS2 consists of approximately 315 ac (127 ha) of habitat in Miami-Dade County, Florida. This unit is bordered on the north by SW 248 Street, on the south by SW 312 Street, on the east by SW 112 Avenue, and on the west by SW 217 Avenue.</P>
                        <P>(ii) Map of Unit PS2 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Family Euphorbiaceae: 
                            <E T="03">Chamaesyce deltoidea</E>
                             ssp. 
                            <E T="03">pinetorum</E>
                             (pineland sandmat) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="498">
                            <PRTPAGE P="62594"/>
                            <GID>EP14OC22.033</GID>
                        </GPH>
                        <P>(8) PS3: Navy Wells Pineland Preserve and surrounding areas, Miami-Dade County, Florida.</P>
                        <P>(i) Unit PS3 consists of approximately 558 ac (226 ha) of habitat in Miami-Dade County, Florida. This unit is bordered on the north by SW 320 Street, on the south by SW 368 Street, on the east by U.S. 1 (South Dixie Highway), and on the west by SW 217 Avenue.</P>
                        <P>(ii) Map of Unit PS3 follows:</P>
                        <P>
                            Figure 4 to Family Euphorbiaceae: 
                            <E T="03">Chamaesyce deltoidea</E>
                             ssp. 
                            <E T="03">pinetorum</E>
                             (pineland sandmat) paragraph (8)(ii)
                        </P>
                        <GPH SPAN="3" DEEP="459">
                            <PRTPAGE P="62595"/>
                            <GID>EP14OC22.034</GID>
                        </GPH>
                        <STARS/>
                        <FP SOURCE="FP-2">
                            Family Fabaceae: 
                            <E T="03">Dalea carthagenensis</E>
                             var. 
                            <E T="03">floridana</E>
                             (Florida prairie-clover)
                        </FP>
                        <P>(1) Critical habitat units are depicted for Collier, Miami-Dade County, and Monroe Counties, Florida, on the maps in this entry.</P>
                        <P>(2) Within these areas, the physical or biological features essential to the conservation of the Florida prairie-clover are South Florida pine rockland, marl prairie, rockland hammock, and coastal berm habitat and adjacent disturbed areas:</P>
                        <P>
                            (i) Consisting of limestone substrate that provides nutritional requirements and suitable growing conditions (
                            <E T="03">e.g.,</E>
                             pH, nutrients, anchoring, and drainage);
                        </P>
                        <P>(ii) Characterized by an open canopy and understory with a high proportion of native plant species to provide for sufficient sunlight to permit growth and flowering;</P>
                        <P>(iii) Subjected to a monthly mean temperature characteristic of the subtropical humid classification in Miami-Dade County or the tropical humid classification in Collier and Monroe Counties and short hydroperiods ranging up to 60 days each year;</P>
                        <P>
                            (iv) Subjected to periodic natural (
                            <E T="03">e.g.,</E>
                             fire, hurricanes, and storm surge) or unnatural (
                            <E T="03">e.g.,</E>
                             prescribed fire, mowing) disturbance regimes to maintain open canopy conditions; and
                        </P>
                        <P>(v) Containing the presence of native pollinators for natural pollination and reproduction.</P>
                        <P>(3) Critical habitat does not include human-made structures (such as buildings, aqueducts, runways, roads, and other paved areas) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using ESRI ArcGIS mapping software. The projection used was Albers Conical Equal Area (Florida Geographic Data Library), North American Datum (NAD) 1983 High Accuracy Reference Network (HARN). The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical 
                            <PRTPAGE P="62596"/>
                            habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/office/florida-ecological-services,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R4-ES-2022-0125, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) Index map of all critical habitat units for Florida prairie-clover follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Family Fabaceae: 
                            <E T="03">Dalea carthagenensis</E>
                             var. 
                            <E T="03">floridana</E>
                             (Florida prairie-clover) paragraph (5)
                        </FP>
                        <GPH SPAN="3" DEEP="565">
                            <GID>EP14OC22.035</GID>
                        </GPH>
                        <PRTPAGE P="62597"/>
                        <P>(6) FPC1: Big Cypress National Preserve, Collier, Miami-Dade, and Monroe Counties, Florida.</P>
                        <P>(i) Unit FPC1 consists of approximately 169,885 acres (ac) (68,750 hectares (ha)) in Collier, Miami-Dade, and Monroe County, Florida. The unit is comprised of lands primarily in Big Cypress National Preserve.</P>
                        <P>(ii) Map of Unit FPC1 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 2 to Family Fabaceae: 
                            <E T="03">Dalea carthagenensis</E>
                             var. 
                            <E T="03">floridana</E>
                             (Florida prairie-clover) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="538">
                            <GID>EP14OC22.036</GID>
                        </GPH>
                        <P>(7) FPC2: Everglades National Park, Miami-Dade County, Florida.</P>
                        <P>(i) Unit FPC2 consists of approximately 8,728 ac (3,532 ha) in Miami-Dade County, Florida. This unit is comprised of lands on Long Pine Key and surrounding areas in Everglades National Park.</P>
                        <P>(ii) Map of Unit FPC2 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Family Fabaceae: 
                            <E T="03">Dalea carthagenensis</E>
                             var. 
                            <E T="03">floridana</E>
                             (Florida prairie-clover) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="618">
                            <PRTPAGE P="62598"/>
                            <GID>EP14OC22.037</GID>
                        </GPH>
                        <P>(8) FPC3: U.S. Department of Agriculture Subtropical Horticultural Research Station and surrounding areas, Miami-Dade County, Florida.</P>
                        <P>(i) Unit FPCG3 consists of approximately 630 ac (255 ha) of habitat in Miami-Dade County, Florida.</P>
                        <P>(ii) Map of Unit FPC3 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Family Fabaceae: 
                            <E T="03">Dalea carthagenensis</E>
                             var. 
                            <E T="03">floridana</E>
                             (Florida prairie-clover) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="563">
                            <PRTPAGE P="62599"/>
                            <GID>EP14OC22.038</GID>
                        </GPH>
                        <P>(9) Unit FPC4: Crandon Park, Miami-Dade County, Florida.</P>
                        <P>(i) Unit FPC4 consists of approximately 57 ac (23 ha) in Miami-Dade County, Florida. The unit includes coastal berm and rockland hammock on the east side of County Road 913 to the shoreline, from the vicinity of the Marjorie Stoneman Douglas Biscayne Nature Center to near the northern tip of the island.</P>
                        <P>(ii) Map of Unit FPC4 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 5 to Family Fabaceae: 
                            <E T="03">Dalea carthagenensis</E>
                             var. 
                            <E T="03">floridana</E>
                             (Florida prairie-clover) paragraph (9)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="529">
                            <PRTPAGE P="62600"/>
                            <GID>EP14OC22.039</GID>
                        </GPH>
                        <STARS/>
                        <FP SOURCE="FP-1">
                            Family Poaceae: 
                            <E T="03">Digitaria pauciflora</E>
                             (Florida pineland crabgrass)
                        </FP>
                        <P>(1) Critical habitat units are depicted for Collier, Miami-Dade, and Monroe Counties, Florida, on the maps in this entry.</P>
                        <P>(2) Within these areas, the physical or biological features essential to the conservation of the Florida pineland crabgrass are South Florida pine rockland, marl prairie, and adjacent ecotonal areas:</P>
                        <P>
                            (i) Consisting of calcareous limestone substrate (often exposed with little soil development) that provides nutritional requirements and suitable growing conditions (
                            <E T="03">e.g.,</E>
                             pH, nutrients, anchoring, and drainage);
                        </P>
                        <P>(ii) Characterized by an open to semi-open canopy and understory with a high proportion of native plant species to provide for sufficient sunlight to permit growth and flowering;</P>
                        <P>(iii) Subjected to a monthly mean temperature characteristic of the subtropical humid classification in Miami-Dade County or the tropical humid classification in Collier and Monroe Counties and short hydroperiods ranging up to 60 days each year;</P>
                        <P>
                            (iv) Subjected to periodic natural (
                            <E T="03">e.g.,</E>
                             hurricanes, fire) or unnatural (
                            <E T="03">e.g.,</E>
                             prescribed fire) disturbance regimes to maintain open canopy conditions; and
                        </P>
                        <P>
                            (v) Containing the presence of native pollinators for natural pollination and reproduction.
                            <PRTPAGE P="62601"/>
                        </P>
                        <P>(3) Critical habitat does not include human-made structures (such as buildings, aqueducts, runways, roads, and other paved areas) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using ESRI ArcGIS mapping software. The projection used was Albers Conical Equal Area (Florida Geographic Data Library), North American Datum (NAD) 1983 High Accuracy Reference Network (HARN). The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/office/florida-ecological-services,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R4-ES-2022-0125, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) Index map of all critical habitat units for Florida pineland crabgrass follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Family Poaceae: 
                            <E T="03">Digitaria pauciflora</E>
                             (Florida pineland crabgrass) paragraph (5)
                        </FP>
                        <GPH SPAN="3" DEEP="575">
                            <PRTPAGE P="62602"/>
                            <GID>EP14OC22.040</GID>
                        </GPH>
                        <P>(6) FPCG1: Big Cypress National Preserve, Collier, Miami-Dade, and Monroe Counties, Florida.</P>
                        <P>(i) Unit FPCG1 consists of approximately 169,885 acres (ac) (68,750 hectares (ha)) in Collier, Miami-Dade, and Monroe Counties, Florida. This unit is comprised of lands primarily in Big Cypress National Preserve.</P>
                        <P>(ii) Map of Unit FPCG1 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 2 to Family Poaceae: 
                            <E T="03">Digitaria pauciflora</E>
                             (Florida pineland crabgrass) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="524">
                            <PRTPAGE P="62603"/>
                            <GID>EP14OC22.041</GID>
                        </GPH>
                        <P>(7) FPCG2: Everglades National Park, Monroe County, Florida.</P>
                        <P>(i) Unit FPCG2 consists of approximately 7,994 ac (3,235 ha) in Miami-Dade County, Florida. This unit is comprised of lands on Long Pine Key and surrounding areas in Everglades National Park.</P>
                        <P>(ii) Map of Unit FPCG2 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Family Poaceae: 
                            <E T="03">Digitaria pauciflora</E>
                             (Florida pineland crabgrass) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="521">
                            <PRTPAGE P="62604"/>
                            <GID>EP14OC22.042</GID>
                        </GPH>
                        <STARS/>
                        <FP SOURCE="FP-1">
                            Family Sapotaceae: 
                            <E T="03">Sideroxylon reclinatum</E>
                             ssp. 
                            <E T="03">austrofloridense</E>
                             (Everglades bully)
                        </FP>
                        <P>(1) Critical habitat units are depicted for Collier, Miami-Dade, and Monroe Counties, Florida, on the maps in this entry.</P>
                        <P>(2) Within these areas, the physical or biological features essential to the conservation of the Everglades bully are South Florida pine rockland, marl prairie, and adjacent ecotonal areas:</P>
                        <P>
                            (i) Consisting of calcareous limestone substrate (often exposed with little soil development) that provides nutritional requirements and suitable growing conditions (
                            <E T="03">e.g.,</E>
                             pH, nutrients, anchoring, and drainage);
                        </P>
                        <P>(ii) Characterized by an open to semi-open canopy and understory with a high proportion of native plant species to provide for sufficient sunlight to permit growth and flowering;</P>
                        <P>(iii) Subjected to a monthly mean temperature characteristic of the subtropical humid classification in Miami-Dade County or the tropical humid classification in Collier and Monroe Counties and short hydroperiods ranging up to 60 days each year;</P>
                        <P>
                            (iv) Subjected to periodic natural (
                            <E T="03">e.g.,</E>
                             hurricanes, fire) or unnatural (
                            <E T="03">e.g.,</E>
                             prescribed fire) disturbance regimes to maintain open canopy conditions; and
                        </P>
                        <P>(v) Containing the presence of native pollinators for natural pollination and reproduction.</P>
                        <P>
                            (3) Critical habitat does not include human-made structures (such as 
                            <PRTPAGE P="62605"/>
                            buildings, aqueducts, runways, roads, and other paved areas) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.
                        </P>
                        <P>
                            (4) Data layers defining map units were created using ESRI ArcGIS mapping software. The projection used was Albers Conical Equal Area (Florida Geographic Data Library), North American Datum (NAD) 1983 High Accuracy Reference Network (HARN). The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/office/florida-ecological-services/library,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R4-ES-2022-0125, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) Index maps of all critical habitat units for Everglades bully follows: </P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Family Sapotaceae: 
                            <E T="03">Sideroxylon reclinatum</E>
                             ssp. 
                            <E T="03">austrofloridense</E>
                             (Everglades bully) paragraph (5)
                        </FP>
                        <GPH SPAN="3" DEEP="452">
                            <GID>EP14OC22.043</GID>
                        </GPH>
                        <FP SOURCE="FP-1">
                            Figure 2 to Family Sapotaceae: 
                            <E T="03">Sideroxylon reclinatum</E>
                             ssp. 
                            <E T="03">austrofloridense</E>
                             (Everglades bully) paragraph (5)
                        </FP>
                        <GPH SPAN="3" DEEP="432">
                            <PRTPAGE P="62606"/>
                            <GID>EP14OC22.044</GID>
                        </GPH>
                        <P>(6) Unit EB1: Big Cypress National Preserve, Collier, Miami-Dade, and Monroe Counties, Florida.</P>
                        <P>(i) Unit EB1 consists of 169,885 ac (68,750 ha) in Collier, Miami-Dade, and Monroe County, Florida. The unit is comprised of lands primarily in Big Cypress National Preserve.</P>
                        <P>(ii) Map of Unit EB1 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Family Sapotaceae: 
                            <E T="03">Sideroxylon reclinatum</E>
                             ssp. 
                            <E T="03">austrofloridense</E>
                             (Everglades bully) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="434">
                            <PRTPAGE P="62607"/>
                            <GID>EP14OC22.045</GID>
                        </GPH>
                        <P>(7) Unit EB2: Everglades National Park, Miami-Dade County, Florida.</P>
                        <P>(i) Unit EB2 consists of approximately 7,994 ac (3,235 ha) in Miami-Dade County, Florida. This unit is comprised of lands on Long Pine Key and surrounding areas in Everglades National Park.</P>
                        <P>(ii) Map of Unit EB2 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Family Sapotaceae: 
                            <E T="03">Sideroxylon reclinatum</E>
                             ssp. 
                            <E T="03">austrofloridense</E>
                             (Everglades bully) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="466">
                            <PRTPAGE P="62608"/>
                            <GID>EP14OC22.046</GID>
                        </GPH>
                        <P>(8) Unit EB3: Richmond Pinelands and surrounding areas, Miami-Dade County, Florida.</P>
                        <P>(i) Unit EB3 consists of approximately 987 ac (399 ha) in Miami-Dade County, Florida. This unit is bordered on the north by SW 152 Street (Coral Reef Drive), on the south by SW 200 St (Quail Drive/SR 994), on the east by U.S. 1 (South Dixie Highway), and on the west by SW 177 Avenue (Krome Avenue).</P>
                        <P>(ii) Map of Unit EB3 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 5 to Family Sapotaceae: 
                            <E T="03">Sideroxylon reclinatum</E>
                             ssp. 
                            <E T="03">austrofloridense</E>
                             (Everglades bully) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="448">
                            <PRTPAGE P="62609"/>
                            <GID>EP14OC22.047</GID>
                        </GPH>
                        <P>(9) Unit EB4: Quail Roost Pineland and surrounding areas, Miami-Dade County, Florida.</P>
                        <P>(i) Unit EB4 consists of approximately 256 ac (104 ha) in Miami-Dade County, Florida. This unit is bordered on the north by SW 200 St (Quail Drive/SR 994), on the south by SW 248 Street, on the east by the Florida Turnpike, and on the west by SW 194 Avenue.</P>
                        <P>(ii) Map of Unit EB4 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 6 to Family Sapotaceae: 
                            <E T="03">Sideroxylon reclinatum</E>
                             ssp. 
                            <E T="03">austrofloridense</E>
                             (Everglades bully) paragraph (9)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="448">
                            <PRTPAGE P="62610"/>
                            <GID>EP14OC22.048</GID>
                        </GPH>
                        <P>(10) Unit EB5: Navy Wells Pineland Preserve and surrounding areas, Miami-Dade County, Florida.</P>
                        <P>(i) Unit EB5 consists of approximately 558 ac (226 ha) of habitat in Miami-Dade County, Florida. This unit is bordered on the north by SW 320 Street, on the south by SW 368 Street, on the east by U.S. 1 (South Dixie Highway), and on the west by SW 217 Avenue.</P>
                        <P>(ii) Map of Unit EB5 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 7 to Family Sapotaceae: 
                            <E T="03">Sideroxylon reclinatum</E>
                             ssp. 
                            <E T="03">austrofloridense</E>
                             (Everglades bully) paragraph (10)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="450">
                            <PRTPAGE P="62611"/>
                            <GID>EP14OC22.049</GID>
                        </GPH>
                        <STARS/>
                    </SECTION>
                    <SIG>
                        <NAME>Madonna Baucum,</NAME>
                        <TITLE>Chief, Policy and Regulations Branch, U.S. Fish and Wildlife Service.</TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 2022-21604 Filed 10-13-22; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 4333-15-C</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>87</VOL>
    <NO>198</NO>
    <DATE>Friday, October 14, 2022</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="62613"/>
            <PARTNO>Part IV</PARTNO>
            <AGENCY TYPE="P">Department of the Interior</AGENCY>
            <SUBAGY>Fish and Wildlife Service</SUBAGY>
            <HRULE/>
            <CFR>50 CFR Part 17</CFR>
            <TITLE>Endangered and Threatened Wildlife and Plants; Endangered Species Status for Rim Rock Crowned Snake and Key Ring-Necked Snake and Designation of Critical Habitat; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="62614"/>
                    <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                    <SUBAGY>Fish and Wildlife Service</SUBAGY>
                    <CFR>50 CFR Part 17</CFR>
                    <DEPDOC>[Docket No. FWS-R4-ES-2022-0022; FF09E21000 FXES1111090FEDR 223]</DEPDOC>
                    <RIN>RIN 1018-BE84</RIN>
                    <SUBJECT>Endangered and Threatened Wildlife and Plants; Endangered Species Status for Rim Rock Crowned Snake and Key Ring-Necked Snake and Designation of Critical Habitat</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Fish and Wildlife Service, Interior.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Proposed rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>
                            We, the U.S. Fish and Wildlife Service (Service), propose to list two Florida species, the Key ring-necked snake (
                            <E T="03">Diadophis punctatus acricus</E>
                            ) and the rim rock crowned snake (
                            <E T="03">Tantilla oolitica</E>
                            ), and propose to designate critical habitat under the Endangered Species Act of 1973, as amended (Act). This determination also serves as our 12-month finding on the petition to list the Key ring-necked snake and the rim rock crowned snake. After a review of the best available scientific and commercial information, we find that listing both species is warranted. Accordingly, we propose to list both species as endangered species under the Act. If we finalize this rule as proposed, it would add the species to the List of Endangered and Threatened Wildlife and extend the Act's protections to both species. We also propose to designate critical habitat for the Key ring-necked snake and the rim rock crowned snake under the Act. In total, approximately 2,604 acres (ac) (1,054) hectares (ha) in Monroe County, Florida, and approximately 5,972 ac (2,418 ha) in Miami-Dade County and Monroe County, Florida, fall within the boundaries of the proposed critical habitat designation for the Key ring-necked snake and the rim rock crowned snake, respectively. We announce the availability of a draft economic analysis of the proposed designation of critical habitat for both species.
                        </P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>
                            We will accept comments received or postmarked on or before December 13, 2022. Comments submitted electronically using the Federal eRulemaking Portal (see 
                            <E T="02">ADDRESSES</E>
                            , below) must be received by 11:59 p.m. Eastern Time on the closing date. We must receive requests for a public hearing, in writing, at the address shown in 
                            <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                             by November 28, 2022.
                        </P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>You may submit comments by one of the following methods:</P>
                        <P>
                            (1) 
                            <E T="03">Electronically:</E>
                             Go to the Federal eRulemaking Portal: 
                            <E T="03">https://www.regulations.gov.</E>
                             In the Search box, enter FWS-R4-ES-2022-0022, which is the docket number for this rulemaking. Then, click on the Search button. On the resulting page, in the Search panel on the left side of the screen, under the Document Type heading, check the Proposed Rule box to locate this document. You may submit a comment by clicking on “Comment.”
                        </P>
                        <P>
                            (2) 
                            <E T="03">By hard copy:</E>
                             Submit by U.S. mail to: Public Comments Processing, Attn: FWS-R4-ES-2022-0022, U.S. Fish and Wildlife Service, MS: PRB/3W, 5275 Leesburg Pike, Falls Church, VA 22041-3803.
                        </P>
                        <P>
                            We request that you send comments only by the methods described above. We will post all comments on 
                            <E T="03">https://www.regulations.gov.</E>
                             This generally means that we will post any personal information you provide us (see Information Requested, below, for more information).
                        </P>
                        <P>
                            <E T="03">Availability of supporting materials:</E>
                             For the proposed critical habitat designation, the coordinates or plot points or both from which the maps are generated are included in the decision file and are available at 
                            <E T="03">https://www.fws.gov/office/florida-ecological-services</E>
                             and at 
                            <E T="03">https://www.regulations.gov</E>
                             under Docket No. FWS-R4-ES-2022-0022. Additional supporting information that we developed for this proposed rule will be available on the Service's website, at 
                            <E T="03">https://www.regulations.gov,</E>
                             or both.
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            Lourdes Mena, Division Manager, Classification and Recovery, Florida Ecological Services Field Office, 7915 Baymeadows Way, Suite 200, Jacksonville, FL 32256-7517; 
                            <E T="03">lourdes_mena@fws.gov;</E>
                             telephone 904-731-3134. Individuals in the United States who are deaf, deafblind, hard of hearing, or have a speech disability may dial 711 (TTY, TDD, or TeleBraille) to access telecommunications relay services. Individuals outside the United States should use the relay services offered within their country to make international calls to the point-of-contact in the United States.
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <HD SOURCE="HD1">Executive Summary</HD>
                    <P>
                        <E T="03">Why we need to publish a rule.</E>
                         Under the Act, a species warrants listing if it meets the definition of an endangered species (in danger of extinction throughout all or a significant portion of its range) or a threatened species (likely to become endangered within the foreseeable future throughout all or a significant portion of its range). If we determine that a species warrants listing, we must list the species promptly and designate the species' critical habitat to the maximum extent prudent and determinable. We have determined that the Key ring-necked snake and the rim rock crowned snake both meet the Act's definition of an endangered species; therefore, we are proposing to list them as such and are proposing a designation of critical habitat for both species. Both listing a species as an endangered or threatened species and designating critical habitat can be completed only by issuing a rule through the Administrative Procedure Act rulemaking process.
                    </P>
                    <P>
                        <E T="03">What this document does.</E>
                         We propose to list both the Key ring-necked snake and the rim rock crowned snake as endangered species under the Act, and we propose to designate critical habitat for both species.
                    </P>
                    <P>
                        <E T="03">The basis for our action.</E>
                         Under the Act, we may determine that a species is an endangered or threatened species because of any of five factors: (A) The present or threatened destruction, modification, or curtailment of its habitat or range; (B) overutilization for commercial, recreational, scientific, or educational purposes; (C) disease or predation; (D) the inadequacy of existing regulatory mechanisms; or (E) other natural or manmade factors affecting its continued existence. We have determined that the Key ring-necked snake and the rim rock crowned snake are facing threats due to development (Factor A), fire suppression (Factor A), and effects associated with climate change, particularly sea level rise and saltwater intrusion (Factor E).
                    </P>
                    <P>
                        Section 4(a)(3) of the Act requires the Secretary of the Interior (Secretary) to designate critical habitat concurrent with listing to the maximum extent prudent and determinable. Section 3(5)(A) of the Act defines critical habitat as (i) the specific areas within the geographical area occupied by the species, at the time it is listed, on which are found those physical or biological features (I) essential to the conservation of the species and (II) which may require special management considerations or protections; and (ii) specific areas outside the geographical area occupied by the species at the time it is listed, upon a determination by the Secretary that such areas are essential for the conservation of the species. Section 4(b)(2) of the Act states that the Secretary must make the designation on the basis of the best scientific data 
                        <PRTPAGE P="62615"/>
                        available and after taking into consideration the economic impact, the impact on national security, and any other relevant impacts of specifying any particular area as critical habitat.
                    </P>
                    <HD SOURCE="HD1">Information Requested</HD>
                    <P>We intend that any final action resulting from this proposed rule will be based on the best scientific and commercial data available and be as accurate and as effective as possible. Therefore, we request comments or information from other governmental agencies, Native American Tribes, the scientific community, industry, or any other interested parties concerning this proposed rule.</P>
                    <P>We particularly seek comments concerning:</P>
                    <P>(1) The species' biology, range, and population trends, including:</P>
                    <P>(a) Biological or ecological requirements of the species, including habitat requirements for feeding, breeding, and sheltering;</P>
                    <P>(b) Genetics and taxonomy;</P>
                    <P>(c) Historical and current range, including distribution patterns;</P>
                    <P>(d) Historical and current population levels, and current and projected trends; and</P>
                    <P>(e) Past and ongoing conservation measures for the species, their habitats, or both.</P>
                    <P>(2) Factors that may affect the continued existence of the species, which may include habitat modification or destruction, overutilization, disease, predation, the inadequacy of existing regulatory mechanisms, or other natural or manmade factors.</P>
                    <P>(3) Biological, commercial trade, or other relevant data concerning any threats (or lack thereof) to these species and existing regulations that may be addressing those threats.</P>
                    <P>(4) Additional information concerning the historical and current status, range, distribution, and population size of these species, including the locations of any additional populations of these species.</P>
                    <P>(5) Information on the immediacy and magnitude of threats to the rim rock crowned snake in the upper and lower Florida Keys.</P>
                    <P>(6) Whether we should consider evaluating populations of the rim rock crowned snake as distinct population segments.</P>
                    <P>
                        (7) The reasons why we should or should not designate habitat as “critical habitat” under section 4 of the Act (16 U.S.C. 1531 
                        <E T="03">et seq.</E>
                        ), including information regarding the following factors that the regulations identify as reasons why designation of critical habitat may be not prudent:
                    </P>
                    <P>(a) The species are threatened by taking or other human activity and identification of critical habitat can be expected to increase the degree of such threat to the species; or</P>
                    <P>(b) Such designation of critical habitat would not be beneficial to the species. In determining whether a designation would not be beneficial, the factors the Services may consider include but are not limited to: Whether the present or threatened destruction, modification, or curtailment of a species' habitat or range is not a threat to the species, or whether any areas meet the definition of “critical habitat.”</P>
                    <P>(8) Specific information on:</P>
                    <P>(a) The amount and distribution of Key ring-necked snake and rim rock crowned snake habitat;</P>
                    <P>(b) Any additional areas occurring within the range of the species that should be included in the designation because they (1) are occupied at the time of listing and contain the physical or biological features that are essential to the conservation of the species and that may require special management considerations, or (2) are unoccupied at the time of listing and are essential for the conservation of the species.</P>
                    <P>(c) For areas not occupied at the time of listing that may be essential for the conservation of the species, we particularly seek comments on whether any additional unoccupied areas should be designated for either species. For the rim rock crowned snake, we ask for information on areas in the Environmentally Endangered Lands (EEL) program in Miami-Dade County that may be essential to the conservation of the rim rock crowned snake. For the Key ring-necked snake, we request information or additional survey data to determine whether we should designate unoccupied critical habitat on Key West for the Key ring-necked snake; and</P>
                    <P>(d) Special management considerations or protection that may be needed in critical habitat areas we are proposing, including managing for the potential effects of climate change.</P>
                    <P>(9) Land use designations and current or planned activities in the subject areas and their possible impacts on proposed critical habitat.</P>
                    <P>(10) Any probable economic, national security, or other relevant impacts of designating any area that may be included in the final designation, and the related benefits of including or excluding specific areas.</P>
                    <P>(11) Information on the extent to which the description of probable economic impacts in the draft economic analysis (DEA) is a reasonable estimate of the likely economic impacts and any additional information regarding probable economic impacts that we should consider.</P>
                    <P>(12) Whether any specific areas we are proposing for critical habitat designation should be considered for exclusion under section 4(b)(2) of the Act, and whether the benefits of potentially excluding any specific area outweigh the benefits of including that area under section 4(b)(2) of the Act. Specific information we seek includes the effectiveness of the Monroe County habitat conservation plan (HCP) in protecting pine rocklands and rockland hammock habitat and in providing for conservation of the Key ring-necked snake and the rim rock crowned snake.</P>
                    <P>(13) Whether we could improve or modify our approach to designating critical habitat in any way to provide for greater public participation and understanding, or to better accommodate public concerns and comments.</P>
                    <P>Please include sufficient information with your submission (such as scientific journal articles or other publications) to allow us to verify any scientific or commercial information you include. If you request exclusion of a particular area or areas from the final designation, please provide information regarding the existence of a meaningful economic or other relevant impact supporting the benefit of exclusion of that particular area.</P>
                    <P>Please note that submissions merely stating support for, or opposition to, the action under consideration without providing supporting information, although noted, do not provide substantial information necessary to support a determination. Section 4(b)(1)(A) of the Act directs that determinations as to whether any species is an endangered or a threatened species must be made solely on the basis of the best scientific and commercial data available, and section 4(b)(2) of the Act directs that the Secretary shall designate critical habitat on the basis of the best scientific data available.</P>
                    <P>
                        You may submit your comments and materials concerning this proposed rule by one of the methods listed in 
                        <E T="02">ADDRESSES</E>
                        . We request that you send comments only by the methods described in 
                        <E T="02">ADDRESSES</E>
                        .
                    </P>
                    <P>
                        If you submit information via 
                        <E T="03">https://www.regulations.gov,</E>
                         your entire submission—including any personal identifying information—will be posted on the website. If your submission is made via a hardcopy that includes personal identifying information, you may request at the top of your document that we withhold this information from public review. However, we cannot 
                        <PRTPAGE P="62616"/>
                        guarantee that we will be able to do so. We will post all hardcopy submissions on 
                        <E T="03">https://www.regulations.gov.</E>
                    </P>
                    <P>
                        Comments and materials we receive, as well as supporting documentation we used in preparing this proposed rule, will be available for public inspection on 
                        <E T="03">https://www.regulations.gov.</E>
                    </P>
                    <P>Because we will consider all comments and information we receive during the comment period, our final determinations may differ from this proposal. Based on the new information we receive (and any comments on that new information), we may conclude that either or both species are threatened instead of endangered, or we may conclude that either or both species do not warrant listing as either endangered species or threatened species. For critical habitat, our final designation may not include all areas proposed, may include some additional areas that meet the definition of critical habitat, or may exclude some areas if we find the benefits of exclusion outweigh the benefits of inclusion.</P>
                    <HD SOURCE="HD2">Public Hearing</HD>
                    <P>
                        Section 4(b)(5) of the Act provides for a public hearing on this proposal, if requested. Requests must be received by the date specified in 
                        <E T="02">DATES</E>
                        . Such requests must be sent to the address shown in 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        . We will schedule a public hearing on this proposal, if requested, and announce the date, time, and place of the hearing, as well as how to obtain reasonable accommodations, in the 
                        <E T="04">Federal Register</E>
                         and local newspapers at least 15 days before the hearing. We may hold the public hearing in person or virtually via webinar. We will announce any public hearing on our website, in addition to the 
                        <E T="04">Federal Register</E>
                        . The use of these virtual public hearings is consistent with our regulations at 50 CFR 424.16(c)(3).
                    </P>
                    <HD SOURCE="HD1">Previous Federal Actions</HD>
                    <P>Both the Key ring-necked snake and the rim rock crowned snake were included as Category 2 candidate species in our December 30, 1982 (47 FR 58454), September 18, 1985 (50 FR 37958), January 6, 1989 (54 FR 554), November 21, 1991 (56 FR 58804), and November 15, 1994 (59 FR 58982), candidate notices of review (CNORs). Category 2 included taxa for which information in our possession indicated that a proposed listing rule was possibly appropriate, but for which sufficient data on biological vulnerability and threats were not available to support a proposed rule.</P>
                    <P>In the CNOR published on February 28, 1996 (61 FR 7596), we announced a revised list of plant and animal taxa that were regarded as candidates for possible addition to the Lists of Endangered and Threatened Wildlife and Plants. The revised candidate list included only former Category 1 species. Former Category 2 species were removed from the candidate list in order to reduce confusion about the conservation status of these species and to clarify that we no longer regarded these species as candidates for listing. Since both the Key ring-necked snake and the rim rock crowned snake were Category 2 species, they were no longer recognized as candidate species as of the publication of the February 28, 1996, CNOR.</P>
                    <P>On July 11, 2012, we received a petition from the Center for Biological Diversity requesting that 53 species of reptiles and amphibians, including the Key ring-necked snake and the rim rock crowned snake, be listed as endangered or threatened and critical habitat be designated under the Act.</P>
                    <P>On July 1, 2015, we published a 90-day finding (80 FR 37568) that the petition presented substantial scientific or commercial information indicating that the petitioned action may be warranted for both the Key ring-necked snake and the rim rock crowned snake. This proposed rule constitutes our 12-month petition finding for both species.</P>
                    <HD SOURCE="HD1">Supporting Documents</HD>
                    <P>
                        A species status assessment (SSA) team prepared SSA reports for both the Key ring-necked snake and the rim rock crowned snake (Service 2021a, entire; Service 2021b, entire). The SSA teams were composed of Service biologists, in consultation with other species experts. The SSA reports represent a compilation of the best scientific and commercial data available concerning the status of the species, including the impacts of past, present, and future factors (both negative and beneficial) affecting the species. In accordance with our joint policy on peer review published in the 
                        <E T="04">Federal Register</E>
                         on July 1, 1994 (59 FR 34270), and our August 22, 2016, memorandum updating and clarifying the role of peer review of listing actions under the Act, we sent the Key ring-necked snake SSA report to five independent peer reviewers for review, including scientists with expertise in wildlife biology, herpetology, and conservation biology. We received two responses. We sent the rim rock crowned snake SSA report to five independent peer reviewers, including scientists with expertise in wildlife biology, herpetology, and conservation biology. We received three responses.
                    </P>
                    <HD SOURCE="HD1">I. Proposed Listing Determination</HD>
                    <HD SOURCE="HD1">Background</HD>
                    <HD SOURCE="HD2">Key Ring-Necked Snake</HD>
                    <P>
                        A thorough review of the taxonomy, life history, and ecology of the Key ring-necked snake (
                        <E T="03">Diadophis punctatus acricus</E>
                        ) is presented in the SSA report (version 1.0; Service 2021a, pp. 2-5). The Key ring-necked snake is one of 14 distinct subspecies of ring-necked snakes in North America, all of which are subspecies of 
                        <E T="03">D. punctatus.</E>
                         It is one of the smallest subspecies of the Family Dipsadidae; an adult specimen will average between 6 and 10 inches (in) (15.2 to 25.4 centimeters (cm)). A recent review of phylogenetic data supports the current subspecies classification for the Key ring-necked snake (Hoffman 2019, entire).
                    </P>
                    <P>This slender snake has a pale grayish-brown head; a grayish-black dorsal surface; and a yellow, orange, or bright red abdomen which fades to orange/red underneath the tail (Florida Fish and Wildlife Conservation Commission (FWC) 2013, p. 1). The pupil is round, and the juvenile color is similar to that of the adult (Ernst and Ernst 2003, p. 92; FWC 2013, p. 1). The characteristic neck ring is indistinct or virtually absent in both juveniles and adults.</P>
                    <P>Little life-history information is available on the Key ring-necked snake, especially as it relates to microhabitat, feeding, and reproduction. Life-history characteristics are thought to be similar to the southern ring-necked snake. In general, mating of ring-necked snakes can occur in the spring or fall, delayed fertilization is possible, and eggs are laid in June or early July. Females lay 1 to 10 eggs at a time each year (1 clutch/year) in covered, moist locations (Ernst and Ernst 2003, p. 95). Juveniles are thought to hatch in August and September.</P>
                    <P>
                        Suitable habitat appears to consist of pinelands, pine rocklands, tropical hammock, rockland hammock, limestone outcroppings, and rocky pine scrub areas (McDiarmid 1978, p. 41; Lazell 1989, p. 134; Auth and Scott 1996, p. 33; Enge et al. 2003, pp. 26-28). Most of the observations in the Florida Keys were from pine rocklands or nearby rockland hammocks. This subspecies appears to be restricted to areas near permanent freshwater that often occur as small holes in the oolitic (a sedimentary rock, usually limestone, composed of minute rounded concretions) substrate that underlies pine rocklands and rockland hammock habitat (Lazell 1989, pp. 134, 136). All 
                        <E T="03">Diadophis</E>
                         apparently require moist microhabitats to balance evaporative 
                        <PRTPAGE P="62617"/>
                        water loss from the body (Myers 1965, p. 4; Clark 1967, pp. 492-494).
                    </P>
                    <P>Key ring-necked snakes have been documented on seven lower Florida Keys: Key West, Big Pine Key, Little Torch Key, Middle Torch Key, No Name Key, Cudjoe Key, and Stock Island (Auth and Scott 1996, p. 33; FWC 2011, p. 3; 2013, p. 1; Mays and Enge 2016, pp. 11, 13; J. Mays 2020, pers. comm.) (see figure 1, below). A unique characteristic of the Florida Keys is the thin (&lt;3.94 in (10 cm)) layer of sediment on the islands beneath which lies a bed of limestone, and below that a shallow layer of freshwater referred to as a freshwater lens (U.S. Geological Survey (USGS) 2019a, p. 1). Because the density of freshwater is less than the underlying saltwater, it floats to the top and into the limestone rock formations where it becomes available to the island's biota. The volume of a freshwater lens fluctuates in response to rainfall, evapotranspiration, and human use (local wells).</P>
                    <P>Systematic recent surveys have not been conducted for the Key ring-necked snake across all of the Florida Keys; therefore, the true spatial distribution of populations throughout the Florida Keys is unclear and our current understanding of the subspecies' distribution is primarily based on historical records. Consequently, this subspecies may occur on Florida Keys other than those reported. </P>
                    <GPH SPAN="3" DEEP="320">
                        <GID>EP14OC22.050</GID>
                    </GPH>
                    <FP SOURCE="FP-1">Figure 1.—Distribution and occurrences of the Key ring-necked snake.</FP>
                    <HD SOURCE="HD2">Rim Rock Crowned Snake</HD>
                    <P>
                        A thorough review of the taxonomy, life history, and ecology of the rim rock crowned snake (
                        <E T="03">Tantilla oolitica</E>
                        ) is presented in the SSA report (version 1.0; Service 2021b, pp. 10-20). The rim rock crowned snake is in the family Colubridae, part of the black-headed, crowned, and flat-headed snake genus 
                        <E T="03">Tantilla,</E>
                         with 76 currently recognized species ranging from the southern United States to northern Argentina (Powell et al. 2016, pp. 395-400). The rim rock crowned snake is most closely related to the southeastern crowned snake (
                        <E T="03">T. coronata</E>
                        ) taxonomically, although it is located geographically closer to the Florida crowned snake (
                        <E T="03">T. relicta;</E>
                         Ernst and Ernst 2003, pp. 353-355). No genetic analysis has been conducted on the rim rock crowned snake.
                    </P>
                    <P>Rim rock crowned snakes have a black head (“cap”) that is continuous from snout to neck (“collar”), transitioning to tan or beige on its back, and a pinkish white to cream belly. There is often a pale blotch just behind the eye. Specimens from the Florida Keys may have a pale neckband that is not present in mainland specimens, separating the black cap from the black collar (Porras and Wilson 1979, pp. 218-220). Adults range 7-9 in (18-23 cm) in length. Females reach a greater length than do males, but have shorter tails (Ernst and Ernst 2003, pp. 353-355). Hatchlings range from 3-3.5 in (7.5-9.0 cm) in length.</P>
                    <P>
                        The reproduction, longevity, and diet of the rim rock crowned snake are unknown, but if it is similar to the closely related southeastern crowned snake, it probably matures at 2 years old and may live to be at least 5 years old in the wild (Todd et al. 2008, p. 392). There may be three eggs in a clutch, and they may be able to produce two clutches annually (Ernst and Ernst 2003, pp. 353-355). There is no information as to whether eggs or juvenile rim rock crowned snakes require different habitat than adults. Predators are likely larger snake species that inhabit the same areas. It may also be preyed upon by the 
                        <PRTPAGE P="62618"/>
                        slender brown scorpion (
                        <E T="03">Centruroides gracilis</E>
                        ), which is abundant in rockland habitat (Porras and Wilson 1979, pp. 218-220).
                    </P>
                    <P>The rim rock crowned snake is a mostly fossorial (underground) species that inhabits shallow soil over limestone formations, and it can sometimes be found in rotten stumps and under anthropogenic surface detritus, fallen logs, and rocks (Duellman and Schwarz 1958, p. 306; Rochford et al. 2010, p. 99; Yirka et al. 2010, p. 386; FWC 2011, p. 3; Hines 2011, p. 353). These snakes are vulnerable to desiccation, so they usually occupy moist microhabitats (Powell et al. 2016, pp. 395-400). Refugia in pine rocklands and rockland hammock are provided by holes and crevices in the limestone, piles of rock rubble, pockets of organic matter accumulating in solution holes, and shallow depressions in the limestone (Enge et al. 2003, pp. 27-28). Rim rock crowned snakes likely come to the surface after rains (Porras and Wilson 1979, pp. 218-220), possibly because of flooding of its underground refugia.</P>
                    <P>
                        The rim rock crowned snake has been historically found in the lower Florida Keys, in particular Key West and Big Pine Key; the upper Florida Keys; and the southeastern Florida peninsula within Miami-Dade County, in a variety of locations (see figure 2, below). Within this limited range, the rim rock crowned snake is found in pine rocklands and rockland hammock, which consist of a limestone substrate and outcroppings. Pine rocklands habitat is fire-maintained and dominated by pine trees and a diverse understory of grasses and forbs/herbs. In contrast, rockland hammock contains more hardwood shrubs and trees due to less fire influence. There are also occurrence records from human-altered habitats such as roadsides, vacant lots, and pastures with shrubby growth and slash pines (
                        <E T="03">Pinus elliottii</E>
                        ) (Duellman and Schwarz 1958, p. 306; Hines 2011, pp. 352-356).
                    </P>
                    <P>Because of the rim rock crowned snake's cryptic and fossorial nature, a method to formally census remaining populations throughout its range has not been developed. We do not have any information on the current status of the rim rock crowned snake in these areas and based our understanding of the species' range on observational records and habitat suitability. Limited dispersal is thought to occur between rim rock crowned snake populations within the Florida Keys because there is no evidence that indicates they readily swim to other islands. Additionally, areas in Miami-Dade County where populations may remain are likely isolated from others due to physical barriers from a dense urban interface.</P>
                    <GPH SPAN="3" DEEP="350">
                        <GID>EP14OC22.051</GID>
                    </GPH>
                    <FP SOURCE="FP-1">Figure 2.—Distribution and occurrences of the rim rock crowned snake.</FP>
                    <HD SOURCE="HD1">Regulatory and Analytical Framework</HD>
                    <HD SOURCE="HD2">Regulatory Framework</HD>
                    <P>
                        Section 4 of the Act (16 U.S.C. 1533) and the implementing regulations in title 50 of the Code of Federal Regulations set forth the procedures for determining whether a species is an endangered species or a threatened species, issuing protective regulations for threatened species, and designating 
                        <PRTPAGE P="62619"/>
                        critical habitat for threatened and endangered species. In 2019, jointly with the National Marine Fisheries Service, the Service issued final rules that revised the regulations in 50 CFR parts 17 and 424 regarding how we add, remove, and reclassify threatened and endangered species and the criteria for designating listed species' critical habitat (84 FR 45020 and 84 FR 44752; August 27, 2019). At the same time the Service also issued final regulations that, for species listed as threatened species after September 26, 2019, eliminated the Service's general protective regulations automatically applying to threatened species the prohibitions that section 9 of the Act applies to endangered species (collectively, the 2019 regulations).
                    </P>
                    <P>
                        However, on July 5, 2022, the U.S. District Court for the Northern District of California vacated the 2019 regulations (
                        <E T="03">Center for Biological Diversity</E>
                         v. 
                        <E T="03">Haaland,</E>
                         No. 4:19-cv-05206-JST, Doc. 168 (N.D. Cal. July 5, 2022) (
                        <E T="03">CBD</E>
                         v. 
                        <E T="03">Haaland</E>
                        )), reinstating the regulations that were in effect before the effective date of the 2019 regulations as the law governing species classification and critical habitat decisions. Accordingly, in developing the analysis contained in this proposal, we applied the pre-2019 regulations, which may be reviewed in the 2018 edition of the Code of Federal Regulations at 50 CFR 17.31, 17.71, 424.02, 424.11(d) and (e), and 424.12(a)(1) and (b)(2)). Because of the ongoing litigation regarding the court's vacatur of the 2019 regulations, and the resulting uncertainty surrounding the legal status of the regulations, we also undertook an analysis of whether the proposal would be different if we were to apply the 2019 regulations. That analysis, which we described in a separate memo in the decisional file and posted on 
                        <E T="03">https://www.regulations.gov,</E>
                         concluded that we would have reached the same proposal if we had applied the 2019 regulations. The differences in the 2009 Solicitor's opinion and 2019 regulations do not change our determination of what constitutes the foreseeable future for the rim rock crowned snake. Under either regulatory scheme we find that critical habitat is prudent for the two snakes. For the Key ring-necked snake, we did not identify any unoccupied areas essential for the conservation of the Key ring-necked snake, which is consistent with 2016 and 2019 regulations. For the rim rock crowned snake, by the year 2040, all suitable habitat in the lower Florida Keys and up to half of suitable habitat in the upper Florida Keys will be affected by sea level rise and saltwater intrusion. As such, we are also proposing to designate areas not currently occupied by the species, because we determined the unoccupied units are essential for the conservation of the rim rock crowned snake. It is reasonably certain that the unoccupied units will contribute to the conservation of the species by providing additional areas for rim rock crowned snake recovery actions, including population establishment, and the unoccupied units contain all of the physical or biological features that are essential to the conservation of the species and it has the abiotic and biotic features that currently or periodically contain the resources and conditions necessary to support one or more life processes of the rim rock crowned snake.
                    </P>
                    <P>
                        On September 21, 2022, the U.S. Circuit Court of Appeals for the Ninth Circuit stayed the district court's July 5, 2022, order vacating the 2019 regulations until a pending motion for reconsideration before the district court is resolved (
                        <E T="03">In re: Cattlemen's Ass'n,</E>
                         No. 22-70194). The effect of the stay is that the 2019 regulations are currently the governing law. Because a court order requires us to submit this proposal to the 
                        <E T="04">Federal Register</E>
                         by September 30, 2022, it is not feasible for us to revise the proposal in response to the Ninth Circuit's decision. Instead, we hereby adopt the analysis in the separate memo that applied the 2019 regulations as our primary justification for the proposal. However, due to the continued uncertainty resulting from the ongoing litigation, we also retain the analysis in this preamble that applies the pre-2019 regulations and we conclude that, for the reasons stated in our separate memo analyzing the 2019 regulations, this proposal would have been the same if we had applied the pre-2019 regulations.
                    </P>
                    <P>The Act defines an “endangered species” as a species that is in danger of extinction throughout all or a significant portion of its range, and a “threatened species” as a species that is likely to become an endangered species within the foreseeable future throughout all or a significant portion of its range. The Act requires that we determine whether any species is an endangered species or a threatened species because of any of the following factors:</P>
                    <P>(A) The present or threatened destruction, modification, or curtailment of its habitat or range;</P>
                    <P>(B) Overutilization for commercial, recreational, scientific, or educational purposes;</P>
                    <P>(C) Disease or predation;</P>
                    <P>(D) The inadequacy of existing regulatory mechanisms; or</P>
                    <P>(E) Other natural or manmade factors affecting its continued existence.</P>
                    <P>These factors represent broad categories of natural or human-caused actions or conditions that could have an effect on a species' continued existence. In evaluating these actions and conditions, we look for those that may have a negative effect on individuals of the species, as well as other actions or conditions that may ameliorate any negative effects or may have positive effects.</P>
                    <P>We use the term “threat” to refer in general to actions or conditions that are known to or are reasonably likely to negatively affect individuals of a species. The term “threat” includes actions or conditions that have a direct impact on individuals (direct impacts), as well as those that affect individuals through alteration of their habitat or required resources (stressors). The term “threat” may encompass—either together or separately—the source of the action or condition or the action or condition itself.</P>
                    <P>However, the mere identification of any threat(s) does not necessarily mean that the species meets the statutory definition of an “endangered species” or a “threatened species.” In determining whether a species meets either definition, we must evaluate all identified threats by considering the species' expected response and the effects of the threats—in light of those actions and conditions that will ameliorate the threats—on an individual, population, and species level. We evaluate each threat and its expected effects on the species, then analyze the cumulative effect of all of the threats on the species as a whole. We also consider the cumulative effect of the threats in light of those actions and conditions that will have positive effects on the species, such as any existing regulatory mechanisms or conservation efforts. The Secretary determines whether the species meets the definition of an “endangered species” or a “threatened species” only after conducting this cumulative analysis and describing the expected effect on the species now and in the foreseeable future.</P>
                    <P>
                        The Act does not define the term “foreseeable future,” which appears in the statutory definition of “threatened species.” Because the decision in 
                        <E T="03">CBD</E>
                         v. 
                        <E T="03">Haaland</E>
                         vacated our 2019 regulations with respect to our consideration of foreseeable future, we refer to a 2009 Department of the Interior Solicitor's opinion entitled “The Meaning of `Foreseeable Future' in Section 3(20) of the Endangered Species Act” (M-37021). The Solicitor's opinion 
                        <PRTPAGE P="62620"/>
                        states that the foreseeable future “must be rooted in the best available data that allow predictions into the future” and extends as far as those predictions are “sufficiently reliable to provide a reasonable degree of confidence in the prediction, in light of the conservation purposes of the Act.” 
                        <E T="03">Id.</E>
                         at 13.
                    </P>
                    <P>It is not always possible or necessary to define the foreseeable future as a particular number of years. Analysis of the foreseeable future uses the best scientific and commercial data available and should consider the timeframes applicable to the relevant threats and to the species' likely responses to those threats in view of its life-history characteristics. Data that are typically relevant to assessing the species' biological response include species-specific factors such as lifespan, reproductive rates or productivity, certain behaviors, and other demographic factors.</P>
                    <HD SOURCE="HD2">Analytical Framework</HD>
                    <P>
                        The SSA reports document the results of our comprehensive biological review of the best scientific and commercial data regarding the status of the two species, including assessment of the potential threats to the species. The SSA reports do not represent our decision on whether the species should be proposed for listing as endangered or threatened species under the Act. However, they do provide the scientific basis that informs our regulatory decisions, which involve the further application of standards within the Act and its implementing regulations and policies. The following is a summary of the key results and conclusions from the SSA reports, which can be found at Docket No. FWS-R4-ES-2022-0022 on 
                        <E T="03">https://www.regulations.gov</E>
                         and at 
                        <E T="03">https://www.fws.gov/office/florida-ecological-services.</E>
                    </P>
                    <P>To assess Key ring-necked snake and rim rock crowned snake viability, we used the three conservation biology principles of resiliency, redundancy, and representation (Shaffer and Stein 2000, pp. 306-310). Briefly, resiliency supports the ability of the species to withstand environmental and demographic stochasticity (for example, wet or dry, warm or cold years), redundancy supports the ability of the species to withstand catastrophic events (for example, droughts, large pollution events), and representation supports the ability of the species to adapt over time to long-term changes in the environment (for example, climate changes). In general, the more resilient and redundant a species is and the more representation it has, the more likely it is to sustain populations over time, even under changing environmental conditions. Using these principles, we identified the species' ecological requirements for survival and reproduction at the individual, population, and species levels, and described the beneficial and risk factors influencing the species' viability.</P>
                    <P>The SSA process can be categorized into three sequential stages. During the first stage, we evaluated the individual species' life-history needs. The next stage involved an assessment of the historical and current condition of the species' demographics and habitat characteristics, including an explanation of how the species arrived at its current condition. The final stage of the SSA involved making predictions about the species' responses to positive and negative environmental and anthropogenic influences. Throughout all of these stages, we used the best available information to characterize viability as the ability of a species to sustain populations in the wild over time. We use this information to inform our regulatory decision.</P>
                    <HD SOURCE="HD1">Summary of Biological Status and Threats</HD>
                    <P>In this discussion, we review the biological condition of the species and their resources, and the threats that influence the species' current and future conditions, to assess the species' overall viability and the risks to that viability.</P>
                    <HD SOURCE="HD2">Key Ring-Necked Snake—Population and Subspecies Needs</HD>
                    <P>In this discussion, we outline the resource needs of individuals and populations of the Key ring-necked snake. As part of the assessment, we first identify and describe the four most influential factors representing the individual and population needs for the subspecies: prey, refugia, water, and available suitable habitat. Due to the relative rarity of this subspecies and its secretive nature, many aspects of the life history of this taxon as well as information on population status and trends are poorly known. We rely upon ecologically and genetically similar species to draw inferences when data are lacking.</P>
                    <P>
                        For prey, the Key ring-necked snake is assumed to be similar to other 
                        <E T="03">Diadophis</E>
                         species (such as the southern ring-necked snake), which prey upon small insects, snakes, lizards (anoles, geckos), slugs, amphibians (frogs, tadpoles), and earthworms (Ernst and Ernst 2003, p. 96; FWC 2013, p. 2).
                    </P>
                    <P>Key ring-necked snakes require refugia to escape and hide from predators and to regulate body temperature. Refugia in pine rocklands and rockland hammock are likely provided by holes and crevices in the limestone, piles of rock rubble, and pockets of organic matter accumulating in solution holes and shallow depressions in the oolitic limestone (Enge et al. 2003, p. 28). Snakes are ectothermic organisms, which require an external heat source to warm their bodies in order to increase body function and productivity. Snakes can also become too hot, leading to desiccation. Therefore, a warm, moist habitat, typically subterranean or shielded from the sun, is likely a preferred refugium to escape from predators and to properly maintain homeostasis (suitable internal temperature and moisture levels).</P>
                    <P>Water is essential for Key ring-necked snake survival. This subspecies appears to be restricted to areas near permanent freshwater sources that often occur as small holes in the limestone (Lazell 1989, pp. 134, 136). The extensive network of holes, tunnels, and cavities in the limestone substrate most likely assists in creating more permanent water sources. During times of drought, these sources may become scarce and the Key ring-necked snakes may need to seek out other freshwater sources. Consequently, it is important for the Key ring-necked snake to have multiple freshwater sources in case one becomes depleted, contaminated, or unavailable. If all local water sources within a snake's home range become dry, the snake may need to expend more energy and time in search of new water sources.</P>
                    <P>
                        The most influential need for population viability is available suitable habitat. Home range is defined as the area a snake traverses for its normal daily activities (Burt 1943, pp. 350-351; Miller 2008, p. 16). The specific acreage associated with the Key ring-necked snake's home range is unknown; however, an individual was documented traveling 154.2 feet (ft) (47 meters (m)) between coverboards (Lazell 1989, p. 134). Over 400 mark recapture measurements of ring-necked snakes in Kansas indicated a mean travel distance of 262 ft (80m) with a maximum distance of 5,577 ft (1,700 m) (Fitch 1975, p. 25). In another study, a different ring-neck snake subspecies (
                        <E T="03">Diadophis punctatus</E>
                         ) in northern Michigan was documented to travel between 20 ft (6 m) and 1 mile (1,609 m) (Blanchard et al. 1979, pp. 382, 385). Thus, although ring-necked snakes generally only move within a small home range, they will occasionally disperse over longer distances through suitable habitat.
                        <PRTPAGE P="62621"/>
                    </P>
                    <P>In regard to population size and distribution of the Key ring-necked snake, there may be either distinct, non-interbreeding populations at each Key, or some occasional but rare level of dispersal from rafting (oceanic dispersal whereby a species travels between islands on a mass or raft of vegetation) between Keys, providing at least a small level of connectivity between individual populations. Because the Key ring-necked snake appears to be isolated to the Keys, the relatively small, archipelago of islands can each support only a small number of individuals (or separate populations).</P>
                    <P>Due to the cryptic nature of the Key ring-necked snake and limited research, there is virtually no information concerning the population structure and demographics exhibited by this subspecies. Additionally, no information exists on the abundance (number of individuals) or growth rate of these populations. Therefore, we base our assessment of the health and resiliency of these populations on the condition of its habitat as a proxy. That said, continued occurrence of populations over time at known locations suggest some ability to withstand stochastic events on the Keys, historically.</P>
                    <P>Populations of the Key ring-necked snake are supported by the existence of suitable available habitat (pine rocklands and rockland hammock) across the subspecies' range. Therefore, a strong correlation to habitat availability and Key ring-necked snake populations can be assumed but not at a level of certainty in which the presence of suitable pine rockland or rockland hammock habitat can be used as a surrogate for Key ring-necked snake presence.</P>
                    <P>Passive dispersal of individual Key ring-necked snakes among the Florida Keys may be occurring on a very limited and random basis. The level to which immigration and emigration via dispersal acts as a factor towards population resiliency and prevention against extinction for this subspecies is unknown. Many of the Florida Keys have yet to be surveyed for Key ring-necked snakes, but if occupied, they could act as “stepping stones” in the random dispersal of individual snakes by way of swimming or rafting. That said, due to the limited size of the Florida Keys, the distance between the Keys, and the fact that swimming has not been documented in Key ring-necked snakes, dispersal is not likely, and, thus, it has a limited influence on population dynamics. Overall, we lack detailed scientific information on the extent of the Key ring-necked snake's individual populations and population structure. Thus, our understanding of the factors influencing Key ring-necked snake resiliency is limited.</P>
                    <P>Because systematic recent surveys have not been conducted for the Key ring-necked snake across all of the Florida Keys, the true spatial distribution of populations throughout the Florida Keys is unclear and our current understanding of the subspecies' distribution is primarily based on historical records.</P>
                    <P>As discussed above, widely distributed populations offer better redundancy than if the populations all occur in close proximity and are vulnerable to similar threats at the same intensity or timing. Because of the Key ring-necked snake's limited geographic range, the species is exposed to threats concurrently and of similar frequency, intensity, and duration across its range. For example, the entire subspecies is vulnerable to the effects of a hurricane passing over the Florida Keys. Additionally, the extent of suitable habitat is naturally limited in the Keys. Consequently, there is little natural redundancy or “backup” for the available habitat, and natural expansion or movement of the subspecies to new areas is not probable. The minimum number of sufficiently resilient populations necessary to sustain the subspecies is unknown. Based on the presence of pine rocklands and rockland hammock habitat (total acreage 7,006 ac (2,835 ha)) in the upper Florida Keys, redundancy could be higher if discrete populations occur across the upper Florida Keys. However, the range of this subspecies appears to be restricted to the lower Florida Keys (Mays 2020, pers. comm.). Given the low likelihood of dispersal between islands, we considered islands in the lower Florida Keys (Key West, Big Pine Key, Little Torch Key, Middle Torch Key, No Name Key, Cudjoe Key, and Stock Island) as separate Key ring-necked snake populations.</P>
                    <P>As currently indicated, the Key ring-necked snake occupies a small geographic area, making it vulnerable to large-scale threats (for example, storm events/hurricanes, sea level rise) that affect the entire Florida Keys archipelago.</P>
                    <P>Because of the Key ring-necked snake's narrow geographic and ecological range, there is little variation in habitat types occupied. Also, the Key ring-necked snake does not occur across different ecosystems or have access to different systems in which to adapt. Therefore, the Key ring-necked snake has a narrow breadth of genetic and environmental diversity within and among populations.</P>
                    <HD SOURCE="HD2">Rim Rock Crowned Snake—Population and Species Needs</HD>
                    <P>As part of the population needs assessment for the rim rock crowned snake, we identified and described the most influential factors (available prey, water, refugia, and suitable habitat) representing the individual and population needs for the species.</P>
                    <P>
                        The diet of rim rock crowned snakes probably consists of centipedes, insects, and other small invertebrates, similar to the diet of other members of the genus 
                        <E T="03">Tantilla.</E>
                         Prey eaten by wild and captive 
                        <E T="03">T. coronata</E>
                         include tenebrionid beetle larvae, earthworms, snails, centipedes, spiders, cutworms, wireworms, and termites and their larvae (Ernst and Ernst 2003, pp. 353-355). We do not know what the prey-related requirements (abundance variety, range, etc.) are to maintain viability.
                    </P>
                    <P>
                        Water is essential for rim rock crowned snake survival. We have no specific information on the amount of water they require; however, similar species of 
                        <E T="03">Tantilla</E>
                         tend to survive in warm, moist conditions where water is intermittently available. Small amounts of water can be found in depressions and holes in the limestone substrate, which fill from rain fall or overnight dew. The extensive network of holes, tunnels, and cavities in the limestone substrate may also lead to more permanent water sources. During times of drought, these sources may become scarce, and the snake may need to seek out other fresh water sources. The rim rock crowned snake must have multiple fresh water sources in case one becomes depleted, contaminated, or unavailable. If all local water sources within a snake's home range become dry, the snake may need to expend more energy and time in search of new water sources.
                    </P>
                    <P>
                        Rim rock crowned snakes require refugia to escape and hide from predators and to regulate body temperature. Refugia in pine rocklands and rockland hammock are provided by holes and crevices in the limestone, piles of rock rubble, and pockets of organic matter accumulating in solution holes and shallow depressions in the limestone (Enge et al. 2003, pp. 27-28). Snakes are ectothermic organisms, which require an external heat source for homeostasis. Snakes can also become too hot, consequently leading to desiccation. Therefore, a warm, moist habitat, typically subterranean or shielded from the sun, is likely a preferred refugium to escape from 
                        <PRTPAGE P="62622"/>
                        predators and to properly maintain homeostasis.
                    </P>
                    <P>We do not know how much suitable habitat and habitat connectivity is required to maintain viability. An observation of a rim rock crowned snake was recorded (Hines 2011, pp. 352-356) at the Barnacle Historic State Park in Coconut Grove, Miami, Florida, a site that consists of only 6 ac (2 ha) of rockland hammock habitat. We do not know if pine rocklands or rockland hammocks are more suitable for the rim rock crowned snake, as they have been observed in both. Home range is defined as the area a snake traverses for its normal daily activities (Burt 1943, pp. 350-351; Miller 2008, p. 16). The rim rock crowned snake's home range size is unknown.</P>
                    <P>Rim rock crowned snake populations need abundant individuals within habitat patches of adequate area and quality to maintain survival and reproduction despite disturbance. Therefore, a strong correlation to habitat availability and rim rock crowned snake populations can be assumed, but not at a level of certainty in which the presence of suitable pine rockland or rockland hammock habitat can be used as a surrogate for rim rock crowned snake presence.</P>
                    <P>Despite these uncertainties, data indicate that the limited and patchy distribution of occupied suitable habitat is negatively affecting population resiliency across the species' range. The majority of suitable rim rock crowned snake habitat in southeastern Miami-Dade County and the Florida Keys has been developed and is highly impacted by human activities. Additionally, the Florida Keys are limited naturally in their land area.</P>
                    <P>Dispersal of individual snakes among the fragmented suitable habitat in Miami-Dade County could occur, but if it does, it is expected to be on a limited and random basis. The level to which immigration and emigration via dispersal influence population resiliency and extinction risk is unknown. Above-ground dispersal may not be as effective in a highly urbanized environment. The limited size of the suitable habitat and the distance of urban barriers between them suggest that dispersal is unlikely to currently influence the population dynamics. The extent to which rim rock crowned snakes are able to use subterranean cavities of the Miami limestone rock ridge to subvert urban barriers is unknown. Because the underlying rock ridge throughout Miami-Dade County is porous, there is potential for individuals to use it as a means of dispersal to avoid urban barriers. If used, it could allow more successful random dispersal of individual snakes than above-ground means. However, the extent of influence of dispersal remains largely unknown.</P>
                    <P>In the Florida Keys, passive dispersal of individual snakes among keys may be occurring on a very limited and random basis. The level to which immigration and emigration via dispersal acts as a factor towards population resiliency and prevention against extinction for this species is unknown. Many of the Florida Keys have yet to be searched, but if occupied, they could act as “stepping stones” in the random dispersal of individual snakes. However, the limited size of the Florida Keys and the distance between them means that dispersal is not likely; thus, it currently has a limited influence on population dynamics.</P>
                    <P>No recent surveys have been conducted for the rim rock crowned snake; therefore, the true spatial distribution of populations throughout Miami-Dade County and the Florida Keys is unclear, and our current image of the species' distribution is primarily based on historical records. Consequently, this species may very well occur on other areas in Miami-Dade County or the Florida Keys other than those reported, and the importance of the other areas (other than those with identified populations) to the overall species' resiliency is unclear. To date, no genetic analysis has been conducted on the rim rock crowned snake. Consequently, it is unknown whether or not genetically discrete populations exist in the upper or lower Florida Keys or Miami-Dade County where this species has been historically reported. No information exists on the abundance or growth rate of these populations.</P>
                    <P>Having multiple populations distributed across the landscape offers better redundancy than if the populations all occur in very close proximity and are vulnerable to stressors with the same intensity or timing. For example, the entire species is vulnerable to the effects of a hurricane passing over south Florida. Limited acreage of suitable habitat remains in Miami-Dade County and the Florida Keys; consequently, there is limited opportunity for natural expansion, and movement of the species to new areas is not probable.</P>
                    <P>Species redundancy for the rim rock crowned snake is provided by individuals being distributed across Miami-Dade County and the upper and lower Florida Keys. However, due to the lack of recent surveys conducted within Miami-Dade County and the Florida Keys, the current rim rock crowned snake's range is unknown. Despite a level of redundancy provided by the discrete populations and individuals found dispersed across Miami-Dade County and the Florida Keys, the rim rock crowned snake lacks redundancy because of its small endemic range. For some large-scale stressors (storm events and hurricanes) that affect southeastern Florida and the Florida Keys, the species is vulnerable to the timing and intensity of impacts. Overall, the rim rock crowned snake needs multiple, interconnected, healthy populations across its range.</P>
                    <P>Given the low likelihood of dispersal between islands, we considered islands in the Florida Keys as separate rim rock crowned snake populations. In the upper Keys, north Key Largo, south Key Largo, Plantation Key, Upper Matecombe Key, Lower Matecombe Key, and Marathon (Grassy and Vaca Keys) are considered separate populations. In the lower Keys, Big Pine Key and Key West are considered separate populations. Similarly, due to physical barriers (roads, structures, canals, etc.), we considered the Miami-Dade County locations as distinct populations: Arch Creek Park, Barnacle Historic State Park (BHSP), Bill Sadowski Park, Deering Estate/Ludlum Pineland Area/Chapman Field (DLC), Ned Glenn Pineland, Rockdale and Richmond Pine Rocklands Tract (Zoo Miami).</P>
                    <P>With regard to representation, the rim rock crowned snake occurs across a narrow geographic and ecological range. Consequently, there is no variation across distance or elevation as there is for other wider-ranging species. The rim rock crowned snake has not been found to occur across different ecosystems, and it is not known if it disperses farther from the limestone rock ridge in southeastern peninsular Florida.</P>
                    <P>As mentioned previously, no genetic analyses have been conducted on the rim rock crowned snake. Hence, the genetic diversity of this species is unknown, and there is little environmental diversity beyond the two habitat types where the species is found. Similarly, it is unclear if there are morphological or behavioral differences between different rim rock crowned snake populations.</P>
                    <HD SOURCE="HD2">Threats Discussion</HD>
                    <P>
                        We note that, by using the SSA framework to guide our analysis of the scientific information documented in the SSA reports, we have not only analyzed individual effects on the species, but we have also analyzed their potential cumulative effects. We incorporate the cumulative effects into our SSA analysis when we characterize the current and future condition of the 
                        <PRTPAGE P="62623"/>
                        species. To assess the current and future condition of the species, we undertake an iterative analysis that encompasses and incorporates the threats individually and then accumulates and evaluates the effects of all the factors that may be influencing the species, including threats and conservation efforts. Because the SSA framework considers not just the presence of the factors, but to what degree they collectively influence risk to the entire species, our assessment integrates the cumulative effects of the factors and replaces a standalone cumulative effects analysis.
                    </P>
                    <P>Following are summary evaluations of six threats analyzed in the SSAs for both the Key ring-necked snake and the rim rock crowned snake: Development (Factor A), fire suppression (Factor A), sea level rise (Factor A), saltwater intrusion (Factor A), shifts in seasonal patterns of rainfall and temperature (Factor A), and storm events (Factor A). We also evaluate existing regulatory mechanisms (Factor D) and ongoing conservation measures.</P>
                    <P>In the SSAs, we also considered four additional threats: Overutilization due to recreational, educational, and scientific use (Factor B); disease (Factor C); predation (Factor C); and invasive species (Factor E). We concluded that, as indicated by the best available scientific and commercial information, these threats are currently having little to no impact on either the Key ring-necked snake or the rim rock crowned snake and their habitat, and thus their overall effect now and into the future is expected to be minimal. Therefore, we will not present summary analyses of those threats in this document, but we will consider them in our cumulative assessment of impacts to the species. For full descriptions of all threats and how they impact the species, please see both SSA reports (Service 2021a, pp. 9-21; Service 2021b, pp. 25-40).</P>
                    <HD SOURCE="HD2">Key Ring-Necked Snake—Current Threats and Condition</HD>
                    <P>We do not have fine-scale information to determine different levels of threats within individual populations of the Key ring-necked snake. Thus, for this subspecies, we considered threats and population resiliency on the scale of individual islands in that area.</P>
                    <HD SOURCE="HD3">Development</HD>
                    <P>The Key ring-necked snake inhabits a variety of rockland habitat in Monroe County that has been and is still desirable for residential and commercial development (Service 1999, p. 3-174). Over half of the rockland habitat within the Florida Keys has been and continues to be altered, degraded, or destroyed for residential and commercial development (Hodges and Bradley 2006, pp. 8-9). Urban development and historical land use for agriculture have greatly reduced the extent of pine rocklands in the Florida Keys. Additionally, the quality of some pine rocklands has declined in the Keys because the remaining habitat patches are isolated and confined by surrounding urban development. Although individual snakes show some tolerance of habitat alteration, development and conversion of suitable snake habitat can impact all life stages of the Key ring-necked snake. In addition to direct impacts from loss of soils for nesting and movement and the loss of shelter and shade for adult snakes, ground cover and availability of invertebrate food sources can be reduced. Indirectly, connectivity is further decreased, hindering the finding of mates and the dispersal to new locations by juveniles.</P>
                    <P>Currently, total habitat area potentially available to Key ring-necked snakes in the lower Florida Keys consists of 1,899 ac (769 ha) of pine rocklands habitat and 3,806 ac (1,540 ha) of rockland hammock habitat (USGS 2019b, p. 4). While the hammock habitats are widespread across many islands in various sizes, pine rocklands remain on only five islands in the lower Florida Keys. One of these islands, Big Pine Key, has 1,480 ac (599 ha) (78 percent) of total pine rocklands area, while other Keys (Little Pine Key, No Name Key, Cudjoe Key, and Sugarloaf Key) contain only small areas of hardwood-invaded pine rocklands. The Florida Keys Carrying Capacity Study conducted in 2003 (Monroe County 2016, entire), concluded that development in the Florida Keys has surpassed the carrying capacity of upland habitats to maintain their ecological integrity, that any further development in the Florida Keys would exacerbate secondary and indirect impacts to remaining habitat, and that any further urbanization in areas dominated by native vegetation would exacerbate habitat loss and fragmentation.</P>
                    <P>Some habitat protections are currently in place for the Key ring-necked snake. In 2006, Monroe County implemented an HCP for Big Pine Key and No Name Key that incorporates guidelines and recommendations from the 2003 study. The primary goal of the HCP is to maintain and implement a system that directs future growth to meet goals, including to protect natural resources and to encourage a compact pattern of development. Subsequently, future development on these islands must meet the requirements of the HCP. Furthermore, to fulfill the HCP's mitigation requirement, Monroe County has been actively acquiring parcels of high-quality habitat for listed species and managing them for conservation, including pine rocklands habitat on Big Pine Key and No Name Key. Although the Key ring-necked snake is not a covered species under this HCP, we still expect the habitat protections afforded by the HCP to provide the Key ring-necked snake some protection from development.</P>
                    <P>Suitable habitat for the Key ring-necked snake is protected within preserves such as the Florida Keys National Wildlife Refuge Complex. The complex spans two Key ring-necked snake populations on No Name Key and Big Pine Key. Overall, 4,711.36 ac (1,906.62 ha) (82.6 percent) of pine rockland and rockland hammock habitats in the lower Keys are protected or under conservation (Florida Natural Areas Inventory (FNAI) 2019). The remaining suitable habitat for the Key ring-necked snake is extremely vulnerable to development. Other than these avenues to protect suitable habitat, the existing regulatory mechanisms and conservation measures do not address the impacts of development.</P>
                    <P>The effects of development have the potential to reduce individual survival of Key ring-necked snakes and, therefore, may decrease population resiliency. Resiliency may be further reduced due to loss of connectivity between populations, both as dispersal within populations as they become fragmented and dispersal between occurrences on individual islands. Similarly, because the Key ring-necked snake is endemic to only a few lower Florida Key islands, losing even a few populations to the effects of development would result in a substantial reduction in subspecies redundancy. The Monroe County HCP may prevent further development of pine rocklands, although population resiliency would continue to decline as habitats remain degraded due to impacts associated with development.</P>
                    <HD SOURCE="HD3">Fire Suppression</HD>
                    <P>
                        In addition to historical loss of habitat via urban development and agriculture, the quality of pine rocklands has declined due to fire suppression. Further, the quality of some pine rocklands has declined in the Keys because they are isolated and confined by surrounding urban development that restricts the use of prescribed fire, which is the principal management tool. Prescribed fire must be periodically 
                        <PRTPAGE P="62624"/>
                        introduced to sustain the pine rocklands community structure. In the absence of fire, pine rocklands are invaded by many of the species found in hardwood hammocks, they lose their herbaceous flora, and they move along a successional trajectory toward hammock (Service 1999, pp. 3-173). These rockland hammocks are generally present where pine rocklands were not burned for a long period of time, leading to pine rocklands fragmentation. This fragmentation in turn increases the risk of invasion by exotic vegetation along the interface with disturbed or developed areas, further altering, degrading, or destroying suitable habitat for the Key ring-necked snake.
                    </P>
                    <P>Although Key ring-necked snakes occur in areas where fire has been suppressed, pine rocklands habitat quality is reduced by lack of fire. Thus, fire suppression has the potential to reduce population resiliency through ongoing habitat degradation.</P>
                    <HD SOURCE="HD3">Climate Change</HD>
                    <P>The predominant threat currently affecting the Key ring-necked snake and its habitat is the rapid and intense shifts in climate occurring as a result of increasing greenhouse gas emissions. The entire Florida Keys archipelago is being affected by increases in sea level, saltwater intrusion, increases in tide and tidal flooding, and shifts in seasonal climate pattern. In the SSA report and this proposed rule, we discuss the effects of climate change on the Key ring-necked snake in terms of sea level rise, saltwater intrusion, shifts in seasonal patterns of rainfall and temperature, and storm events (Service 2021a, pp. 23-28).</P>
                    <P>
                        <E T="03">Sea level rise—</E>
                        The Key ring-necked snake is vulnerable to current and predicted sea level rise across its entire range because it is located only in the Florida Keys, where the effects of increasing sea levels, higher tidal surges, increased coastal and inland flooding, and saltwater intrusion are currently being experienced (Benedict et al. 2018, pp. 9, 13, 31, 7-i; Service 2019, p. 1). The Florida Keys are among the most vulnerable areas to the effects of sea level rise due to their low mean elevation of less than 4 ft (1.2 m) (Service 2019, p. 9). Consequently, the lowest parts of the Florida Keys are highly susceptible to flooding, with parts of the islands farther upland at risk of inundation and saltwater intrusion.
                    </P>
                    <P>Global sea level has increased by 8 to 9 in (0.20 to 0.23 m) since 1880, with the rate of increase doubling over the past 20 years (Service 2017, p. 5). From 1913 to 2018, the mean high-water line on Key West rose 0.09 in (0.23 cm) per year (National Oceanic and Atmospheric Administration (NOAA) 2019; Service 2021a, Figure 3). On Vaca Key, sea levels rose 0.14 in (0.36 cm) per year between 1971 (start of data collection) and 2018 (NOAA 2019; Service 2021a, Figure 3).</P>
                    <P>Recent analysis is now indicating an accelerated rate of sea level rise for the eastern United States above that of the global rate (Park and Sweet 2015, entire; Sweet et al. 2017, pp. 39-41, Sweet et al. 2022, pp. 20-21). The accelerated sea level rise in south Florida is being attributed to shifts in the Florida Current due to added ocean mass brought on by the melting Antarctic and Greenland ice packs and thermal expansion from the warming ocean (Park and Sweet 2015, entire; Rahmstorf et al. 2015, entire; Deconto and Pollard 2016, p. 596; Sweet et al. 2017, pp. vi, 14, 15, 18, Sweet et al. 2022, pp. 22-23). For this reason, adding approximately 15 percent to global mean sea level rise projections is recommended for southeast Florida and the Florida Keys (Park and Sweet 2015, entire; Southeast Florida Regional Climate Change Compact 2012, p. 35). The most recent intermediate sea level scenario for the Florida Keys projects a 1.1-1.2 m (3.6-3.9 ft) increase by 2100 (Sweet et al. 2022, pp. 20-21).</P>
                    <P>Based on a case study of Big Pine Key in the lower Florida Keys, saltwater intrusion due to sea level rise will begin to negatively affect the root zone of the island's upland vegetation as early as 2030, and increasing saltwater intrusion of groundwater has already been documented (USGS 2019a, pp. 1, 3). As a result, freshwater-dependent flora and fauna, which comprise much of the island's biota, will disappear. By 2040, under intermediate climate scenarios, approximately 88 percent of pine rocklands and 96 percent of rockland hammock habitat in the lower Florida Keys are expected to be impacted by sea level rise (USGS 2019a, entire). By 2040, under extreme climate scenarios, approximately 98 percent of pine rocklands and 99 percent of rockland hammock habitat in the lower Florida Keys are expected to be impacted by sea level rise (USGS 2019a, entire).</P>
                    <P>The effects of sea level rise could impact the Key ring-necked snake both through loss of individuals during flooding events, and alteration of suitable habitat, causing a loss in population resiliency. If flooding is severe enough, it could extirpate entire populations, leading to a substantial loss of redundancy.</P>
                    <P>Saltwater intrusion—Higher tidal surges, coastal and inland flooding, and saltwater intrusion due to increasing sea levels are currently being experienced in the Florida Keys. In the Florida Keys, high tide flooding events primarily affect low-lying coastal areas and exposed pine rockland and rockland hammock habitats. With worsening storms and extreme tidal events, storm surges along the Florida Keys will increase in frequency and severity over time and will impact habitats farther inland. Additionally, with continued increase in sea level rise, high tide/king tide flood frequencies are also expected to rapidly increase, with potentially severe damage to remaining rockland habitat. Pine rocklands species, particularly the dominant canopy species (slash pine), have little ability to tolerate saltwater (USGS 2019b, p. 2).</P>
                    <P>Salt from ocean water deposited during these high-water events has the potential to remain in place in and under the soil for long periods of time, which negatively impacts vegetative growth. For pine rockland and rockland hammock forests to be sustained in such an ecosystem, nutrient cycling must be extremely efficient (that is, there can be little leaching of nutrients beyond the root zone). In other instances, the effects of more powerful storm surges, rising sea levels, and saltwater intrusion of the islands' freshwater lens have contributed to the conversion and loss of pine forest habitat in the Florida Keys to more halophilic (salt-loving) vegetation such as mangroves and buttonwood (Alexander 1976, pp. 219-222; Ross et al. 1994, pp. 151-154). As discussed above in Background, a unique characteristic of the Florida Keys is the existence of a freshwater lens below each island that is critically important for humans, flora, fauna, and a variety of habitats. Consequently, pine rocklands habitat has already undergone a significant reduction in the Florida Keys due to sea level rise (Ross et al. 1994, p. 154). Currently, some of these areas are occupied by halophytic (salt-tolerant) vegetation such as mangroves and buttonwood (Alexander 1976, pp. 219-222) owing to high tide flooding as a result of rising sea level but also due to saltwater intrusion of the islands' freshwater lens. Over time, further vegetation succession will result in halophytic vegetation dominance on the remaining land and more expansive estuaries across much of the island.</P>
                    <P>
                        Overall, saltwater intrusion from storm surge and flooding causes the loss of habitat, habitat conversion, and reduction in the capacity of freshwater storage and the freshwater resources relied upon by the Key ring-necked snake to maintain its thermoregulatory requirements. These effects will 
                        <PRTPAGE P="62625"/>
                        continue to result in the loss of suitable habitat, displacement landward to less suitable habitat, and the loss of individual Key ring-necked snakes.
                    </P>
                    <P>Shifts in seasonal patterns of rainfall and temperature—In the United States, the average temperatures have increased by 1.3 to 1.9 degrees Fahrenheit (°F) (0.77 to 1.1 degrees Celsius (°C)) since recordkeeping began in 1895 (Service 2017, p. 2). The decade from 2000 to 2009 is documented as the warmest on record (Service 2017, p. 2). Since 1991, average temperatures in south Florida have increased 1.5 °F (0.83 °C) or more (Service 2017, p. 2). Continued increases in surface air temperature are expected even if there was an immediate and aggressive reduction in human-produced greenhouse gas emissions (Intergovernmental Panel on Climate Change (IPCC) 2018, pp. 1-11).</P>
                    <P>We presume that the normal range of temperatures in which activity occurs for the Key ring-necked snake is consistent with that which it has experienced in south Florida. Any continuously higher average number of hot days out of the Key ring-necked snake's optimum range or a permanent shift in average air temperature out of this range has the potential to cause physiological stress. In more extreme cases, once an ectothermic organism is exposed to a temperature outside of its activity temperature range, it is closer to reaching a critical thermal maximum/minimum, in which locomotion becomes uncoordinated and the animal loses its ability to escape conditions that will lead to its death (Zug et al. 2001, pp. 179-188). Key ring-necked snakes may become more vulnerable to situations involving critical thermal maximum when habitat loss and fragmentation limit its ability to move or find suitable microhabitats. Additionally, ambient temperature out of the optimal range will physically influence the environment of nests, which may modify incubation periods, embryo temperatures, egg survival, and hatching times. Physiological stress can also result in a variety of risks including increased predation, reduced reproductive performance, and reduced foraging success.</P>
                    <P>Precipitation patterns are also changing. Since 1900, annual average precipitation in south Florida has increased by 5 to 10 percent (Service 2017, p. 4). Shifts in seasonal rainfall events are also currently being documented (U.S. Global Change Research Program (USGCRP) 2018, pp. 745-808). The south Florida dry season (November through April) has become wetter, the rainy season (May through October) has become drier, and current projections show that this trend will continue. This could have detrimental effects on the Key ring-necked snake's seasonal feeding, breeding, and sheltering patterns. Heavy downpours are currently increasing and have especially increased over the last 30 to 50 years. The frequency and intensity of heavy downpours in the Florida Keys have increased by 27 percent since the 1970s (Service 2017, p. 4). Increased inland flooding is predicted during heavy rain events in low-lying areas. With worsening storms, storm surges along coastlines become stronger and push farther inland. Consequently, more powerful storm surges will exacerbate the effects of the increased sea level along the Florida Keys' shorelines.</P>
                    <P>Currently, the existing regulatory mechanisms and conservation measures do not address the impacts of shifting seasonal patterns of rainfall and temperature. Although changes in seasonal weather patterns in south Florida have been documented (Service 2017, entire), direct impacts on the Key ring-necked snake's habitat have not been observed. However, with increased flooding events associated with climate change and sea level rise, the magnitude of this threat could increase into the future, decreasing population resiliency across the range of the subspecies.</P>
                    <P>Storm events—There has been a substantial increase in Atlantic hurricane activity by most measures since the early 1980s, the period during which high-quality satellite data first became available. These include measures of intensity, frequency, and duration as well as the number of strongest (Category 4 and 5) storms (Walsh et al. 2014, p. 20). Strong rainstorms, tropical storms, and hurricanes are all-natural parts of a tropical ecosystem. However, although these events are common occurrences, the vulnerability of Key ring-necked snake populations increases as the quantity and quality of their habitat is compromised. This is especially true when the frequency of storm surges increases without adequate time for habitats to recover.</P>
                    <P>Hurricane activity has been above normal since the Atlantic Multi-Decadal Oscillation (AMO) (the natural variability of the sea surface temperature in the Atlantic Ocean) went into its warm phase around 1992. While the incidence of tropical storms in southeast Florida (including the Keys) is above normal, this frequency is expected to decrease with climate change, but the intensity of the storms is expected to increase by approximately 20 percent (Service 2017, p. 7). This increased intensity results in larger tidal storm surge and greater destruction than historically documented. Ecosystem resiliency is reduced when impacts by extreme events such as floods or storms occur (Service 2017, p. 7). Saltwater intrusion from storm surge and flooding results in displacement landward to less suitable habitat and the loss of individual Key ring-necked snakes. The limestone substrate, on which snakes likely rely for cover, prey, and nesting, will become flooded more frequently, resulting in a higher frequency and longevity of displacement and stress.</P>
                    <P>Information on how strong storms impact this subspecies is lacking. However, information does exist on the impacts to habitat from hurricanes and other strong storms that have occurred in the region, providing some insight of the potential damage and loss to the Key ring-necked snake from such storms. These events likely disturb and reduce the quantity and quality of their resources (such as food and cover) and may do so significantly depending upon the severity and proximity of the storm center. This is particularly true when storm surges bring in nutrient-rich sediment that exacerbate soil accretion, salt deposition, and vegetation loss (Dingler et al. 1995, p. 296; Jackson et al. 1995, p. 321).</P>
                    <P>Additionally, saltwater surges and short-term flooding of upland habitats from strong storms and hurricanes in the Keys have the potential to kill some Key ring-necked snakes and their prey. In 2005, Hurricane Wilma (Category 3) passed just north of the Florida Keys, causing maximum storm tides 5 to 6 ft (1.5 to 1.8 m) above mean sea level in Key West and flooding approximately 60 percent of the city. On Boca Chica and Big Pine Keys, Hurricane Wilma caused a storm surge of 5 to 8 ft (1.5 to 2.4 m) (Kasper 2007, pp. 10-16). In 2017, the combined effect of storm surge and the tide from Hurricane Irma produced maximum inundation levels of 5 to 8 ft (1.5 to 2.4 m) above ground level for portions of the lower Florida Keys from Cudjoe Key eastward to Big Pine Key and Bahia Honda Key, near and to the east of where Irma's center made landfall (Cangialosi et al. 2018, pp. 8-9). A storm surge of 13 ft (4 m) would completely submerge Big Pine Key (Lopez et al. 2004, p. 284).</P>
                    <P>
                        Currently, the existing regulatory mechanisms and conservation measures do not address the impacts of storm events. The effects of storm events have the potential to reduce individual survival, which could then lead to a reduction in the snake's resiliency and redundancy. While past storms have not resulted in complete inundation of 
                        <PRTPAGE P="62626"/>
                        islands, an increase in the intensity and frequency of storms or a direct hit from a strong hurricane could cause significant reductions in subspecies numbers, further limiting the subspecies' population resiliency and making it even more vulnerable to all other threats.
                    </P>
                    <HD SOURCE="HD3">Summary of Threats</HD>
                    <P>Multiple threats are currently impacting the Key ring-necked snake and its habitat. Although individual populations are no longer likely to be lost to development, ongoing habitat degradation associated with urbanization of both pine rocklands and rockland hammock habitat and fire suppression of pine rocklands are continuing to reduce the availability of the features that the Key ring-necked snake needs for feeding, breeding, and sheltering, thus decreasing population resiliency. Because of the current barriers to dispersal, recolonization is unlikely after a population is extirpated.</P>
                    <P>Even minor threats that impact just a few individuals in a population need to be considered for their additive effects. For example, threats like predation and invasive species may have low impacts on their own, but combined with impacts of other threats, they are further reducing already low numbers of Key ring-necked snakes. These minor threats were considered cumulatively for their effects to the Key ring-necked snake and, while they may reduce the numbers for some individual populations, were currently found not to impose negative effects at the population level.</P>
                    <P>Additionally, various threats can originate from a similar cause but produce interdependent effects on the subspecies. For example, greenhouse gas emissions increase the rate and severity of climactic changes, which act in combination as threats on the subspecies. These include sea level rise, seasonal shifts in timing and amounts of precipitation, shifts in temperature patterns, and increased storm intensities that affect the subspecies. Sea level rise reduces available habitat. Because the average high-water line is now higher than historical levels, areas not typically flooded are now flooded on a more regular basis. The rate of sea level rise in the Florida Keys—specifically at NOAA's KYWF1-8724580 Key West ocean data buoy—had been an average rate of 0.09 inch/year (2.3 mm/year) prior to the previous decade (1990s; NOAA 2016, unpaginated). In the early 2000s, sea level rise began to accelerate exponentially and was estimated at 0.3 inch/year (7.6 mm/year) in 2016 (NOAA 2016, unpaginated).</P>
                    <P>The severity of threats may also be exacerbated by the Key ring-necked snake's limited distribution and small population size. There are no records that demonstrate that the Key ring-necked snake was ever distributed beyond the lower Florida Keys. Thus, it has, and probably has always had, low natural redundancy. Currently, it is found only on seven lower Florida Key islands. Rarity is not in itself a threat; however, small population size can exacerbate the effects of ongoing threats, making the subspecies more vulnerable to extirpation. As discussed previously, the Key ring-necked snake is a narrow endemic, meaning it has naturally low redundancy to help it buffer against stochastic and catastrophic events.</P>
                    <P>Currently, the existing regulatory mechanisms and conservation measures do not address the impacts of climate change, sea level rise, and saltwater intrusion. As mentioned above, sea level has increased exponentially since the early 2000s (NOAA 2016, unpaginated). Therefore, the effects of saltwater intrusion have likely degraded existing habitat that supports the Key ring-necked snake, leading to reductions in the features (such as freshwater) that the subspecies needs, and thus reducing population resiliency. The effects of saltwater intrusion are primarily habitat-based, but some individual snakes could also be lost. Signs of saltwater intrusion impacts are currently documented on Big Pine Key, where pine trees have been replaced by salt-tolerant mangrove. The magnitude of this threat has the potential to greatly increase in the future with the projected severity of sea level rise.</P>
                    <HD SOURCE="HD3">Current Condition of Populations</HD>
                    <P>To characterize the current status of Key ring-necked snake populations, we assigned each stressor as low, moderate, or high impacts to the subspecies based on criteria (see table 1, below); these impacts are occurring at the individual (moderate risk) and population (high risk) levels. The risk of each threat, using the risk scoring criteria in tables 1 and 2, was applied to each population and used to assess the overall population condition (see table 3, below). More specifically, point values were summed for each threat (listed in table 1, below) to determine an overall population condition score (scoring criteria listed in table 2, below) and summarized to convey the current condition of each population of the subspecies (see table 3, below). An area with a high risk of threat as described in tables 1 and 2 will result in low population condition in table 3, and a low risk of threat will result in a high population condition. Each population received similar scores, due to limited information for the subspecies and its small endemic range. Based on the cumulative risk of threats to each population, we then estimated the current condition of each population and the likelihood of persistence of each population (Table 2). We defined populations in the SSA report and this proposed rule by the boundary of each island, as we lack information on possible population divisions within each island or about distribution between islands.</P>
                    <P>Overall, all populations of the Key ring-necked snake are in low condition and reduced from historical condition, with ongoing effects from habitat degradation, fire suppression, sea level rise, and saltwater intrusion. Though populations are currently extant on all known islands throughout the species' range, the species is only found on seven islands in a similar ecological setting. Thus, species representation and redundancy are low.</P>
                    <GPOTABLE COLS="4" OPTS="L2,nj,p7,7/8,i1" CDEF="s50,r50,r75,r75">
                        <TTITLE>Table 1—Current Conditions Based on Risk of Threats</TTITLE>
                        <BOXHD>
                            <CHED H="1">Threat</CHED>
                            <CHED H="1">Low risk (1)</CHED>
                            <CHED H="1">Moderate risk (2)</CHED>
                            <CHED H="1">High risk (3)</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Development</ENT>
                            <ENT>Development occurrence protected by land management plan</ENT>
                            <ENT>The level of development would affect suitable habitat and displace some individual snakes, but not at an extent to affect snake populations</ENT>
                            <ENT>A significant amount of suitable habitat would be lost due to development such that snake populations would be impacted.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Disease</ENT>
                            <ENT>No impacts</ENT>
                            <ENT>Some individual snakes would exhibit signs of disease, but impacts would not be widespread enough in the snake population to affect resiliency</ENT>
                            <ENT>Disease would be prevalent in populations across the range of the subspecies, decreasing population resiliency.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="62627"/>
                            <ENT I="01">Fire suppression in pine rocklands</ENT>
                            <ENT>Ongoing, regular fire maintenance</ENT>
                            <ENT>The level of fire suppression would affect some suitable habitat and displace some individual snakes, but not at an extent to affect population resiliency</ENT>
                            <ENT>A significant amount of suitable habitat would be lost due to fire suppression such that snake population resiliency would be impacted.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Predation</ENT>
                            <ENT>No impacts</ENT>
                            <ENT>Some individual snakes would be predated, but impacts would not be widespread throughout snake populations</ENT>
                            <ENT>Predation would be prevalent in populations across the range of the subspecies, decreasing population resiliency.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Invasive species</ENT>
                            <ENT>No impacts</ENT>
                            <ENT>Invasive plants would not outcompete native plants to the extent that a significant amount of suitable snake habitat is altered. Nonnative fauna would outcompete some individual snakes for food, or prey on some snakes, but the effects would not be widespread in the snake population</ENT>
                            <ENT>Invasive plants would outcompete native plants altering habitat so it is no longer suitable for the snake. Nonnative fauna may outcompete snakes for food, or prey on snakes such that populations are impacted.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sea level rise</ENT>
                            <ENT>No impacts</ENT>
                            <ENT>Individual snakes will be affected by increasing sea levels, higher tidal surges, and increased coastal and inland flooding</ENT>
                            <ENT>The severity of increasing sea levels, higher tidal surges, and increased coastal and inland flooding would impact snake populations and possibly extirpate areas.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Saltwater intrusion</ENT>
                            <ENT>No impacts</ENT>
                            <ENT>Some individual snakes will be displaced by the frequency and severity of saltwater intrusion and its impact to suitable snake habitat</ENT>
                            <ENT>The frequency and severity of saltwater intrusion and its impact to suitable snake habitat would impact snake populations, decreasing population resiliency.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Shifts in seasonal patterns of rainfall and temperature</ENT>
                            <ENT>No impacts</ENT>
                            <ENT>Individual snakes would be affected by the frequency and intensity in these seasonal patterns changes, but not to the extent that population resiliency would be affected</ENT>
                            <ENT>The frequency and intensity in these seasonal patterns changes would impact snake populations.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Storm events</ENT>
                            <ENT>No impacts</ENT>
                            <ENT>The intensity, frequency, and duration of storm events would be at a level in which the quantity and quality of individual snake needs are compromised, and some snakes would be displaced landward to less suitable habitat</ENT>
                            <ENT>The intensity, frequency, and duration of storm events would be at a significant level such that the quantity and quality of snake resources were reduced, and snake populations would be displaced.</ENT>
                        </ROW>
                    </GPOTABLE>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s75,12,r75,12">
                        <TTITLE>Table 2—Risk and Overall Population Condition Scoring Criteria for Current and Future Conditions of Populations </TTITLE>
                        <BOXHD>
                            <CHED H="1">Overall population condition</CHED>
                            <CHED H="1">Risk of threat</CHED>
                            <CHED H="1">Population persistence over 60 years</CHED>
                            <CHED H="1">
                                Probability of persistence
                                <LI>(%)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">High (9-13 points)</ENT>
                            <ENT>1</ENT>
                            <ENT>Very Likely</ENT>
                            <ENT>91-100</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Moderate (14-18 points)</ENT>
                            <ENT>2</ENT>
                            <ENT>Likely</ENT>
                            <ENT>51-90</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Low (19-24 points)</ENT>
                            <ENT>3</ENT>
                            <ENT>Unlikely to likely as not</ENT>
                            <ENT>0-50</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>Point values for each threat (see table 1, above) were summed within an analysis area to determine the overall population condition score.</P>
                    <GPOTABLE COLS="11" OPTS="L2,p7,7/8,i1" CDEF="s50,r30,r30,r25,r25,r25,r25,r25,r25,r25,r25">
                        <TTITLE>Table 3—The Risk of Threats and Their Effect on the Population Condition of the Key Ring-Necked Snake </TTITLE>
                        <BOXHD>
                            <CHED H="1">Area</CHED>
                            <CHED H="1">Development</CHED>
                            <CHED H="1">
                                Fire 
                                <LI>suppression </LI>
                                <LI>of pine </LI>
                                <LI>rocklands</LI>
                            </CHED>
                            <CHED H="1">Disease</CHED>
                            <CHED H="1">Predation</CHED>
                            <CHED H="1">Invasive species</CHED>
                            <CHED H="1">Sea level rise</CHED>
                            <CHED H="1">Saltwater intrusion</CHED>
                            <CHED H="1">Shifts in seasonal patterns of rainfall and temperature</CHED>
                            <CHED H="1">Storms</CHED>
                            <CHED H="1">Population condition</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Big Pine Key</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>Low.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Cudjoe Key</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>Low.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Key West</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>Low.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Little Torch Key</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>Low.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Middle Torch Key</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>Low.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">No Name Key</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>Low.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Stock Island</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>Low.</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>The subspecies was analyzed by island. Note that the first nine columns rank the condition of threats, while the final column ranks population condition. Thus, multiple columns of high threat risk result in low population condition.</P>
                    <HD SOURCE="HD2">Rim Rock Crowned Snake—Current Threats and Condition</HD>
                    <P>
                        We do not have fine-scale information to determine different levels of threats within individual populations of the rim rock crowned snake. Thus, for this species, we considered threats at a larger scale in three general areas: eastern Miami-Dade County, the upper Florida Keys, and the lower Florida Keys, and on individual islands where data were available. We also considered population resiliency in isolated habitat patches in the Miami-Dade area and on individual islands in the Florida Keys. We considered North Key Largo and 
                        <PRTPAGE P="62628"/>
                        Key Largo as two separate populations due to the distances between occurrences and due to several barriers to movement.
                    </P>
                    <HD SOURCE="HD3">Development</HD>
                    <P>The rim rock crowned snake inhabits upland rockland habitat (pine rocklands and rockland hammock) that is also desirable for residential and commercial development (Service 1999, p. 3-174). Urban development and agriculture have greatly reduced the extent of pine rocklands and rockland hammock habitat in eastern Miami-Dade County and the Florida Keys. Additionally, the quality of some pine rocklands has declined in the Keys because the remaining habitat patches are isolated and confined by surrounding urban development. Individual rim rock crowned snakes are occasionally documented in roadsides, vacant lots, trash piles, and pastures with shrubby growth and slash pines (FWC 2011, pp. 2-3; Hines 2011, pp. 352-356), but it is unknown whether these individuals are tolerating urban conditions or have been displaced. However, development and conversion of rockland habitat can impact all life stages of the rim rock crowned snake due to direct habitat loss and mortality. In addition to direct impacts from loss of soils for nesting and movement, ground cover and availability of invertebrate food sources can be reduced. Loss of habitat reduces shelter and shade for adults and decreases connectivity, thereby hindering dispersal by juveniles and finding of mates.</P>
                    <P>Extensive land clearing for human population growth, development, and agriculture in Miami-Dade and Monroe Counties has altered, degraded, or destroyed thousands of acres of suitable habitat for rim rock crowned snakes. Throughout south Florida, development and agriculture have reduced pine rocklands habitat to approximately 3 percent of historical levels. Currently, the total habitat area available in Miami-Dade County is approximately 2,275 ac (921 ha) of pine rocklands habitat and 609 ac (247 ha) of rockland hammock habitat, not including Everglades National Park (where the rim rock crowned snake has never been found), or less than 10 percent of the historical extent of this habitat. In the lower Florida Keys, the total area of pine rocklands habitat is approximately 1,899 ac (769 ha), and the total area of rockland hammock habitat is approximately 3,806 ac (1,540 ha), or less than half of the historical extent of this habitat. While the hammock habitats are widespread across many islands in various sizes, pine rocklands remain on only five islands in the lower Florida Keys and none of the upper Florida Keys. The total area covered by rockland hammock in the upper Florida Keys is 7,006 ac (2,835 ha).</P>
                    <P>Some habitat protections are currently in place for the rim rock crowned snake. Starting in 1990, Miami-Dade County's EEL program began acquiring pine rocklands and other natural areas to preserve and protect from development. Once acquired, the EEL program funds land management to maintain and protect the habitat. Since the program's inception, more than 1,500 ac (607 ha) of pine rocklands have become EEL preserves (Miami-Dade County 2019). Rim rock crowned snakes have been found at four EEL preserves.</P>
                    <P>Additionally, Monroe County implemented an HCP for Big Pine and No Name Keys starting in 2006. In 2007, a rim rock crowned snake was observed on Big Pine Key (Hines 2011, p. 353). Subsequently, development on these islands has to meet the requirements of the HCP in regard to future development. In order to fulfill the HCP's mitigation requirement, Monroe County has been actively acquiring parcels of high-quality habitat for listed species and managing them for conservation, including pine rocklands habitat on Big Pine and No Name Keys. Although the rim rock crowned snake is not a covered species under this HCP, we still expect the habitat protections afforded by the HCP to provide the rim rock crowned snake some protection from development, as the areas where the snakes occur will be avoided due to protections for species that are covered by the HCP.</P>
                    <P>Suitable habitat for the rim rock crowned snake is protected within Federal preserves such as Everglades National Park, Crocodile Lake National Wildlife Refuge, and the National Key Deer Refuge; however, the rim rock crowned snake has only been documented in the National Key Deer Wildlife Refuge and Crocodile Lake National Wildlife Refuge. Most of the other records are located on State, local government, or privately owned lands, which are all small fragments of suitable habitat. Extensive pine rocklands habitat is present in the Long Pine Key area of Everglades National Park. However, despite extensive survey efforts (Dalrymple et al. 1991, entire), no evidence of the rim rock crowned snake has been found in Everglades National Park.</P>
                    <P>Over 90 percent of suitable rockland habitat for rim rock crowned snakes has been lost due to human development in south Florida including the Florida Keys, meaning some populations (and thus redundancy) have already been lost. For example, rim rock crowned snakes were previously detected at sites in Miami near intersections of SW 27 Avenue/SW 24 Street, Old Cutler Road/Red Road, and US 1/SW 154 Ave. There are also numerous historical records detected at locations in the greater Miami metropolitan area (Kendall, Coral Gables, Ludlum, Homestead Air Base). However, no rim rock crowned snakes have been found at these locations since the 1980s. Furthermore, extensive urbanization surrounding these remaining habitats reduces survival, via rendering the species less able to withstand environmental and demographic stochasticity and disturbances (that is, reduced resiliency). Resiliency may be further reduced due to loss of connectivity between populations. Because the rim rock crowned snake is endemic to only the southeastern part of the Florida peninsula and the Florida Keys, losing even a few populations to the effects of development would result in a substantial reduction in species redundancy. However, most of the remaining habitat patches are protected, meaning few additional populations are likely to be extirpated due to development, although habitat degradation could result in continued decreases in population resiliency as the species' needs, such as prey and cover, are lost.</P>
                    <HD SOURCE="HD3">Fire Suppression</HD>
                    <P>
                        As discussed above under “Development,” urban development and historical conversion to agriculture has greatly reduced the extent of pine rocklands in southeastern Florida and the Florida Keys. The quality of remaining pine rocklands has declined because those areas are isolated by surrounding urban development that restricts the use of prescribed fire, which is the principal management tool for pine rocklands. Prescribed fire must be periodically introduced to sustain the pine rocklands community structure. In the absence of fire, pine rocklands are invaded by many of the species found in hardwood hammocks. They lose their herbaceous flora and move along a successional trajectory toward hammock (Service 1999, p. 3-173). These rockland hammocks are generally present where pine rocklands were not burned for a long period of time, creating more pine rocklands fragmentation. This fragmentation of pine rocklands in the South Florida and the Florida Keys increases the risk of invasion by exotic vegetation along the interface with disturbed or developed areas, further altering, degrading, or destroying 
                        <PRTPAGE P="62629"/>
                        suitable habitat for the rim rock crowned snake.
                    </P>
                    <P>Although rim rock crowned snakes can still persist in areas where fire has been suppressed, habitat quality is reduced by lack of fire. Thus, the effects of fire suppression in pine rocklands have the potential to reduce population resiliency through ongoing habitat degradation that impacts the rim rock crowned snake and its habitat.</P>
                    <HD SOURCE="HD3">Climate Change</HD>
                    <P>The predominant threat currently affecting the rim rock crowned snake and its habitat are the rapid and intense shifts in climate occurring as a result of increasing greenhouse gas emissions. South Florida and the Florida Keys are being affected by increases in sea level, saltwater intrusion, increases in tide and tidal flooding, and shifts in seasonal climate pattern. In the SSA report and this proposed rule, we discuss the effects of climate change on the rim rock crowned snake in terms of sea level rise, saltwater intrusion, shifts in seasonal patterns of rainfall and temperature, and storm events.</P>
                    <P>Sea level rise—The rim rock crowned snake is vulnerable to current and predicted sea level rise and saltwater intrusion across its entire range because it is located only in south Florida. South Florida, including the Florida Keys, are among the most vulnerable areas to the effects of sea level rise due to their low mean elevation of less than 1.2 m (4 ft) (Service 2019, p. 9). Consequently, south Florida is highly susceptible to flooding, with lands farther upland at risk of inundation and saltwater intrusion. The effects of increasing sea levels, higher tidal surges, coastal and inland flooding, and saltwater intrusion are currently being experienced in south Florida and the Florida Keys (Benedict et al. 2018, pp. 9, 13, 31, 7-i; Service 2019, p. 1).</P>
                    <P>
                        As discussed above in 
                        <E T="03">Key Ring-necked Snake—Current Condition</E>
                         under “Climate Change,” 
                        <E T="03">Sea level rise,</E>
                         the Florida Keys are particularly vulnerable to sea level rise, and the Florida Keys and South Florida are experiencing higher levels of sea level rise than other parts of the globe, as well as higher tidal surges, increased coastal and inland flooding, and saltwater intrusion (Benedict et al. 2018, pp. 9, 13, 31, 7-i; Service 2019, p. 1).
                    </P>
                    <P>Consequently, pine rocklands habitat has already undergone a significant reduction in the Florida Keys due to sea level rise (Ross et al. 1994, p. 154). As mentioned previously, some of these areas are currently occupied by halophytic (salt-tolerant) vegetation such as mangroves and buttonwood (Alexander 1976, pp. 219-222) owing to high tide flooding as a result of rising sea level but also due to saltwater intrusion of the islands' freshwater lens.</P>
                    <P>The effects of sea level rise could impact the rim rock crowned snake by loss of individuals during flooding events, causing a loss in population resiliency. If flooding is severe enough, it could extirpate entire populations, particularly in the lower Florida Keys, leading to a substantial loss of redundancy of the species.</P>
                    <P>
                        Saltwater intrusion—Higher tidal surges, coastal and inland flooding, and saltwater intrusion due to increasing sea levels are currently being experienced in south Florida and the Florida Keys. With worsening storms and extreme tidal events, storm surges along south Florida and the Keys will increase in frequency and severity over time and will impact habitats farther inland. As discussed above in 
                        <E T="03">Key Ring-necked Snake—Current Condition</E>
                         under “Climate Change,” 
                        <E T="03">Saltwater intrusion,</E>
                         this threat will result in habitat degradation and the loss of individual snakes. For the rim rock crowned snake, these effects have been primarily felt in populations in the Florida Keys, although some coastal populations in eastern Miami-Dade County may also experience some small amounts of saltwater intrusion.
                    </P>
                    <P>Currently, the existing regulatory mechanisms and conservation measures do not address the impacts of saltwater intrusion. As mentioned above, sea level has increased exponentially since the early 2000s (NOAA 2016, unpaginated). The effects of saltwater intrusion have likely degraded existing habitat that supports the rim rock crowned snake in the Keys, leading to reductions in the features (such as freshwater) that the species needs, and thus reducing population resiliency. The effects of saltwater intrusion are primarily habitat-based, but some individual snakes could also be lost. Signs of saltwater intrusion impacts have been documented on Big Pine Key, where pine trees have been replaced by salt-tolerant mangrove. The magnitude of this threat has the potential to greatly increase with the projected future severity of sea level rise.</P>
                    <P>
                        Shifts in seasonal patterns of rainfall and temperature—As discussed above in 
                        <E T="03">Key Ring-necked Snake—Current Condition</E>
                         under “Climate Change,” 
                        <E T="03">Shifts in seasonal patterns of rainfall and temperature,</E>
                         rising greenhouse gases are resulting in increasing temperatures and shifting precipitation patterns. Like the Key ring-necked snake, the rim rock crowned snake is a fossorial ectotherm and, therefore, dependent on gaining heat from its microhabitat or by coming into contact with the undersides of warm surfaces (for example, rocks) that are exposed to direct sunlight. As with the Key ring-necked snake, increased temperatures could result in a permanent shift in average air temperature out of rim rock crowned snake's optimal range, causing physiological stress. Physiological stress can manifest into a variety of risks including predation, reduced performance, and reduced foraging success. Altered precipitation patterns could have detrimental effects on the seasonal feeding, breeding, and sheltering patterns for the rim rock crowned snake. Increased inland flooding is predicted during heavy rain events in low-lying areas. With worsening storms, storm surges along coastlines can become stronger and push farther inland. Consequently, more powerful storm surges will exacerbate the effects of the increased sea level along south Florida and Florida Keys' shorelines and could have impacts on rockland habitat.
                    </P>
                    <P>Currently, the existing regulatory mechanisms and conservation measures do not address the impacts of shifting seasonal patterns of rainfall and temperature. Although changes in seasonal weather patterns in south Florida have been documented (Service 2017, entire), direct impacts on the rim rock crowned snake or its habitat have not been observed. However, with increased flooding events associated with sea level rise from climate change, the magnitude of this threat could increase into the future, particularly for populations in the Florida Keys and coastal areas of Miami-Dade County, decreasing population resiliency.</P>
                    <P>
                        Storm events—Changing patterns in hurricane activity are having similar effects to the rim rock crowned snake as to the Key ring-necked snake, as discussed above in 
                        <E T="03">Key Ring-necked Snake—Current Condition</E>
                         under “Climate Change,” 
                        <E T="03">Storm events.</E>
                         The health of the rim rock crowned snake becomes vulnerable when the quantity and quality of their resources (for example, food, cover/substrate) are compromised. This can particularly happen in the case of storm surges and with an increase in the number of incidences (for example, being impacted repeatedly without time to recover). Saltwater intrusion from storm surge and flooding results in displacement landward to less suitable habitat and the loss of individual rim rock crowned snakes. The limestone substrate, which rim rock crowned snakes likely rely on for cover, prey, and nesting, will become more frequently flooded, 
                        <PRTPAGE P="62630"/>
                        creating a higher frequency and longevity of displacement and stress. Storm events likely disturb and reduce the quantity and quality of the resources for the rim rock crowned snake.
                    </P>
                    <P>
                        Hurricane Andrew (1992) hit southern Miami-Dade County with sustained winds in excess of 145 miles per hour (233 kilometers per hour), impacting 99 percent of pine rocklands. Within 1 year of the event, many adult trees were dead, outbreaks of 
                        <E T="03">Ips</E>
                         beetles (including 
                        <E T="03">I. calligraphis, I. avulsus,</E>
                         and 
                        <E T="03">I. grandicollis</E>
                        ) had been reported, and two species of weevil (
                        <E T="03">Hylobius pales, Pachylobius picivorus</E>
                        ) had attacked juvenile trees. The outbreak has been attributed to the combination of wind damage and drought following a very dry spring, making the trees more susceptible to infestation. In a fall 1993 follow-up survey of Miami-Dade County pine rocklands, only 2 of 18 sites had living mature pines. The loss of the pines affected fire fuel production and could allow invasive species to further impact pine rocklands (Service 1999, p. 3-176).
                    </P>
                    <P>Currently, the existing regulatory mechanisms and conservation measures do not influence or address the storm events. The effects of storm events have the potential to reduce individual survival, which could then lead to a reduction in the snake's resiliency and redundancy. While past storms have not resulted in complete inundation of islands, an increase in the intensity and frequency of storms has the potential to produce complete inundation of suitable snake habitat, and therefore possible extirpation of the species.</P>
                    <HD SOURCE="HD3">Summary of Threats</HD>
                    <P>Multiple threats are currently impacting the rim rock crowned snake at the individual and population level and its habitat. The risk of each threat was based on the scoring criteria in tables 1 and 2, above, as applied to each population, and used to assess the overall population condition (see table 4, below).</P>
                    <P>Although individual populations are less likely to be lost to development, ongoing habitat degradation associated with urbanization and fire suppression in pine rocklands are continuing to reduce the availability of the features that the rim rock crowned snake needs for feeding, breeding, and sheltering, thus decreasing population resiliency. Additionally, all effects associated with climate change are interrelated, with shifts in the magnitude of severe storms contributing to increased flooding events that have the potential to extirpate entire populations of the rim rock crowned snake. Although a severe hurricane is unlikely to flood all populations at once, if a hurricane were to extirpate most populations, it would leave the remainder of the species significantly more vulnerable to other threats. Because of the current barriers to dispersal for populations in Miami-Dade County, recolonization is unlikely after a population is extirpated. Some populations, for example on Big Pine Key, may be able to recolonize extirpated sites because there are fewer barriers to dispersal due to less urbanization.</P>
                    <P>Even minor threats that impact just a few individuals in a population need to be considered for their additive effects. For example, threats like predation and invasive species may have low impacts on their own, but combined with impacts of other threats, they are further reducing already low numbers of rim rock crowned snakes. These minor threats were considered cumulatively for their effects to the rim rock crowned snake and, while they may reduce the numbers for some individual populations, were currently found not to impose negative effects at the population level.</P>
                    <P>Additionally, various threats can originate from a similar cause but produce a set of interdependent effects on the species. For example, greenhouse gas emissions increase the rate and severity of climactic changes, which act in combination as threats on the species. These include sea level rise, seasonal shifts in timing and amounts of precipitation, shifts in temperature patterns, and increased storm intensities that affect the species. Sea level rise further reduces available habitat. Because the average high-water line is now higher than historical levels, areas not typically flooded are now flooded on a more regular basis.</P>
                    <P>The severity of threats may also be exacerbated by the rim rock crowned snake's limited distribution and small population size. The rim rock crowned snake is not known to have occurred beyond the southeastern peninsula of Florida or the Florida Keys. Thus, it has, and probably has always had, low representation and redundancy. Currently, it is thought to exist in seven small and fragmented parcels in eastern Miami-Dade County, six islands in the upper Florida Keys, and two lower Florida Key islands. Rarity is not in itself a threat; however, small population size can exacerbate the effects of ongoing threats, making the species more vulnerable to threats.</P>
                    <HD SOURCE="HD3">Current Condition of Populations</HD>
                    <P>As with the Key ring-necked snake, to characterize the current status of the rim rock crowned snake, we assigned each stressor as low, moderate, or high impacts to the subspecies (table 1, table 2). We summarize the current condition of rim rock crowned snake populations in table 4. Overall, the current condition of populations in the Miami-Dade area is moderate, and the condition of populations in the Florida Keys is low.</P>
                    <P>Given the species' limited distribution and limited ecological setting, representation is currently low. However, the species has moderate redundancy, as it has multiple populations distributed throughout the Miami-Dade area and the Upper and Lower Florida Keys.</P>
                    <GPOTABLE COLS="11" OPTS="L2,p7,7/8,i1" CDEF="s50,r30,r30,r25,r25,r25,r25,r25,r25,r25,r25">
                        <TTITLE>Table 4—The Threat Risk and the Effect on the Current Condition of Rim Rock Crowned Snake Populations</TTITLE>
                        <BOXHD>
                            <CHED H="1">Population</CHED>
                            <CHED H="1">Development</CHED>
                            <CHED H="1">
                                Fire
                                <LI>suppression</LI>
                                <LI>in pine</LI>
                                <LI>rocklands</LI>
                            </CHED>
                            <CHED H="1">Disease</CHED>
                            <CHED H="1">Predation</CHED>
                            <CHED H="1">Invasive species</CHED>
                            <CHED H="1">Sea level rise</CHED>
                            <CHED H="1">Saltwater intrusion</CHED>
                            <CHED H="1">Shifts in seasonal patterns of rainfall and temperature</CHED>
                            <CHED H="1">Storms</CHED>
                            <CHED H="1">Population condition</CHED>
                        </BOXHD>
                        <ROW EXPSTB="10" RUL="s">
                            <ENT I="25">
                                <E T="02">MIAMI-DADE COUNTY</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Arch Creek</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>High</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BHSP</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>High</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Bill Sadowski</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>High</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">DLC</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>High</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Ned Glenn</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>High</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rockdale</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>High</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <PRTPAGE P="62631"/>
                            <ENT I="01">Richmond Pine Rocklands</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>High</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate.</ENT>
                        </ROW>
                        <ROW EXPSTB="10" RUL="s">
                            <ENT I="25">
                                <E T="02">UPPER FLORIDA KEYS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">North Key Largo</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>High</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>Low.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">South Key Largo</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>High</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>Low.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Plantation Key</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>High</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>Low.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Upper Matecombe Key</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>High</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>Low.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Lower Matecombe Key</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>High</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>Low.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Marathon</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>High</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>Low.</ENT>
                        </ROW>
                        <ROW EXPSTB="10" RUL="s">
                            <ENT I="25">
                                <E T="02">LOWER FLORIDA KEYS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Big Pine Key</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>Low.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Key West</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>High</ENT>
                            <ENT>Low.</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>Note that the first nine columns rank the condition of threats, while the final column ranks population condition. Thus, multiple columns of high threat risk result in low population condition.</P>
                    <HD SOURCE="HD2">Future Threats and Condition</HD>
                    <P>To examine the potential future condition of the snakes, four plausible future scenarios were developed. The scenarios focused on a range of conditions based on climate change scenarios and projections for land development. The range of what is likely to happen in each scenario is described based on current condition and how resiliency, representation, and redundancy would be expected to change. The levels of certainty or uncertainty are addressed in each scenario. Given that there is uncertainty as to exact future trends of many threats, these future scenarios are meant to explore the range of plausible future scenarios and examine the snakes' response across the range of these conditions.</P>
                    <P>
                        We define viability as the ability to sustain populations over time. For this to occur, a species must have a sufficient number and distribution of healthy populations to withstand changes in its biological (predators, disease) and physical (habitat loss, climate change) environment, environmental stochasticity (flooding, storm surge), and catastrophic events (hurricanes). In considering the future scenarios for the Key ring-necked snake and the rim rock crowned snake, we analyzed expected changes in development up through 2070 based on the timeframe forecast in the urban planning documents (Zwick and Carr 2006, entire), shifts in seasonal patterns of rainfall and temperature (up through 2100), and climate change (sea level rise and saltwater intrusion) from 2030 to 2100. That said, we focused on changes that are expected in the next 20 to 60 years (
                        <E T="03">i.e.,</E>
                         by 2040-2080) because virtually no habitat is forecasted to be present in the lower Florida Keys by 2080. The habitat in Miami-Dade County is forecasted to continue on the same trend up to 2100 as predicted from 2040-2080 (USGS 2019b, d, entire). We do not have any information on future trends of other threats (disease, predation, invasive species, and collection).
                    </P>
                    <P>We chose four plausible scenarios to examine the potential impacts to Key ring-necked snake and rim rock crowned snake populations from development, fire suppression of pine rocklands habitat, climate impacts (sea level rise and saltwater intrusion), storm events, and shifts in seasonal patterns of rainfall and temperature. We determined the population condition (using criteria described above in table 1) given our future projections of threats.</P>
                    <P>In order to understand the impacts of sea level rise and associated impacts on the Key ring-necked snake and the rim rock crowned snake, we contracted a study with the USGS to measure the potential future impacts on pine rocklands and rockland hammock habitat in the range of the Key ring-necked snake and the rim rock crowned snake (USGS 2019, entire). The study calculated the impacts of root zone salinization, regional sea level rise, and high tide effects on suitable habitat in Miami-Dade County and the Florida Keys in 10-year intervals between 2030 and 2100. In this proposed rule, we present a summary of those results. Detailed descriptions of the study and its results are available in the SSA reports for the Key ring-necked snake and the rim rock crowned snake (Service 2021a, pp. 25-27; Service 2021b, pp. 43-47).</P>
                    <HD SOURCE="HD2">Key Ring-Necked Snake—Future Threats and Condition</HD>
                    <P>Because we determined that the current condition of the Key ring-necked snake is consistent with an endangered species (see Determination of Species Status, below), we are not presenting the results of the future scenarios in this rule. For more information on the future condition, future threats, and future scenarios for the Key ring-necked snake, please see the SSA report (Service 2021a, pp. 21-33).</P>
                    <HD SOURCE="HD2">Rim Rock Crowned Snake—Future Threats and Condition</HD>
                    <HD SOURCE="HD3">Development—Future Impacts</HD>
                    <P>Future development is very likely to continue across the range of the rim rock crowned snake. Suitable habitat that is projected to be lost in all of these scenarios is privately owned and not currently under conservation.</P>
                    <P>
                        Miami-Dade and Monroe Counties are not anticipated to undergo dramatic land use changes by 2070, because most land in these counties is already allocated to development, agriculture, or conservation (Carr and Zwick 2016, pp. 20-22). Of remaining pine rocklands 
                        <PRTPAGE P="62632"/>
                        and rockland hammock habitat, 76 percent in eastern Miami-Dade County, 79 percent in the upper Florida Keys, and 83 percent in the lower Florida Keys are protected or conserved (FNAI 2019). However, because such limited habitat area remains, any remaining suitable unprotected habitat for the rim rock crowned snake is extremely vulnerable to development if left unprotected, and even the loss of one population (particularly in the Miami-Dade area) could have a significant effect on the species.
                    </P>
                    <P>Of the suitable habitat for rim rock crowned snake remaining in Miami-Dade County, between 19 and 21 percent is expected to be lost to development by 2070 (Carr and Zwick 2016, pp. 20-22). Although the expected population growth in Monroe County in the Florida Keys is relatively modest, all vacant private lands not protected for conservation purposes are projected to be developed, including lands currently inaccessible for development, such as islands not attached to the Overseas Highway (U.S. 1) (Zwick and Carr 2006, pp. 14-15). This development will have the potential to further reduce the amount of suitable habitat for the rim rock crowned snake.</P>
                    <HD SOURCE="HD3">Fire Suppression—Future Impacts</HD>
                    <P>Fire suppression has had considerable negative impacts on pine rocklands communities. The condition of some extant pine rocklands has declined and become degraded because of inadequate management or because they are isolated and confined by surrounding development that restricts the use of prescribed fire, which is the primary management tool. We do not expect the amount of prescribed burning to increase in the future, so we anticipate that existing habitat will continue to decline in quality and undergo habitat conversion to hammock habitats, particularly in eastern Miami-Dade County.</P>
                    <HD SOURCE="HD3">Climate Change—Future Impacts</HD>
                    <P>In Florida, sea level is projected to rise between 1 ft (0.4 m) at the low end and up to 8.4 ft (3.2 m) at the high end by 2100 (USGS 2019b, p. 1). Due to sea level rise, low-lying islands and coastal areas have increasingly become more vulnerable to high tide flooding, which is rapidly increasing in frequency, depth, and extent (Sweet et al. 2018, p. 3). In South Florida as well as the Keys, storm surge and high tide flooding events primarily affect low-lying coastal areas and exposed habitats such as pine rocklands and rockland hammocks. With continued increase in sea level rise, high tide/king tide flood frequencies are also expected to rapidly increase, with potentially severe damage to remaining rockland habitat in the Florida Keys. Pine rocklands species, particularly the dominant canopy species (slash pine), have little ability to tolerate saltwater (USGS 2019b, p. 2). As mentioned above, pine rocklands habitat has already undergone a significant reduction in the Florida Keys due to sea level rise (Ross et al. 1994, p. 154) and some of these areas are occupied by halophytic (salt-tolerant) vegetation such as mangroves and buttonwood (Alexander 1976, pp. 219-222). As discussed above in Background, a unique characteristic of the Florida Keys is the existence of a freshwater lens below each island that is critically important for humans, flora, fauna, and a variety of habitats.</P>
                    <P>In eastern Miami-Dade County, a shallow layer of highly permeable limestone forms the unconfined Biscayne aquifer. Because this aquifer is unconfined, the top-most layer makes up the water table and directly interacts with natural and humanmade bodies of water. The Biscayne aquifer merges with the floor of Biscayne Bay and the Atlantic Ocean, making it a coastal aquifer. Being a coastal aquifer, there is a potential for contamination from lowered water tables, primarily from over-pumping due to residential and commercial use, which could allow salt water intrusion and could be exacerbated by sea level rise.</P>
                    <P>The anticipated impacts of sea level rise and high tides for the rim rock crowned snake for our four future scenarios are shown below in tables 5-9. There is no table for pine rocklands habitat change in the upper Florida Keys, as there is no pine rocklands habitat there.</P>
                    <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12,12,14C,12,12">
                        <TTITLE>
                            Table 5—Predicted Pine Rocklands Habitat Changes With an Intermediate (I) or Extreme (E) RSLR (Relative Sea Level Rise; Sweet et al. 2017, pp. vi, vii, 12, 21) and Moderate High Tide Effect (2.7 ft (0.82 
                            <E T="01">m</E>
                            )), in the Years 2040, 2060 and 2080, in Eastern Miami-Dade County
                        </TTITLE>
                        <BOXHD>
                            <CHED H="1">Future scenario</CHED>
                            <CHED H="1">RSLR height (m)</CHED>
                            <CHED H="1">Year</CHED>
                            <CHED H="1">Current pine rocklands (ac) in Miami-Dade</CHED>
                            <CHED H="1">Area (ac) of pine rocklands affected by both RSLR and high tide</CHED>
                            <CHED H="1">Percent of pine rocklands affected by both RSLR and high tide</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">1</ENT>
                            <ENT>0.31</ENT>
                            <ENT>
                                2040 
                                <E T="02">I</E>
                            </ENT>
                            <ENT>2,275.02</ENT>
                            <ENT>4.3</ENT>
                            <ENT>0.19</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2</ENT>
                            <ENT>0.54</ENT>
                            <ENT>
                                2060 
                                <E T="02">I</E>
                            </ENT>
                            <ENT O="xl"/>
                            <ENT>13.6</ENT>
                            <ENT>0.60</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3</ENT>
                            <ENT>0.83</ENT>
                            <ENT>
                                2080 
                                <E T="02">I</E>
                            </ENT>
                            <ENT O="xl"/>
                            <ENT>51.5</ENT>
                            <ENT>2.26</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4</ENT>
                            <ENT>0.60</ENT>
                            <ENT>
                                2040 
                                <E T="02">E</E>
                            </ENT>
                            <ENT O="xl"/>
                            <ENT>20.3</ENT>
                            <ENT>0.89</ENT>
                        </ROW>
                    </GPOTABLE>
                    <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12,12,14C,12,12">
                        <TTITLE>
                            Table 6—Predicted Rockland Hammock Habitat Changes With an Intermediate (I) or Extreme (E) RSLR (Relative Sea Level Rise; Sweet et al. 2017, pp. vi, vii, 12, 21) and Moderate High Tide Effect (2.7 ft (0.82 
                            <E T="01">m</E>
                            )), in the Years 2040, 2060 and 2080, in Eastern Miami-Dade County
                        </TTITLE>
                        <BOXHD>
                            <CHED H="1">Future scenario</CHED>
                            <CHED H="1">RSLR height (m)</CHED>
                            <CHED H="1">Year</CHED>
                            <CHED H="1">
                                Current rockland hammock (ac) 
                                <LI>in Miami-Dade</LI>
                            </CHED>
                            <CHED H="1">
                                Area (ac) of rockland 
                                <LI>hammock affected by both RSLR and high tide</LI>
                            </CHED>
                            <CHED H="1">
                                Percent of rockland 
                                <LI>hammock affected by both RSLR and high tide</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">1</ENT>
                            <ENT>0.31</ENT>
                            <ENT>
                                2040 
                                <E T="02">I</E>
                            </ENT>
                            <ENT>609.37</ENT>
                            <ENT>58.0</ENT>
                            <ENT>9.51</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2</ENT>
                            <ENT>0.54</ENT>
                            <ENT>
                                2060 
                                <E T="02">I</E>
                            </ENT>
                            <ENT O="xl"/>
                            <ENT>78.9</ENT>
                            <ENT>12.95</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3</ENT>
                            <ENT>0.83</ENT>
                            <ENT>
                                2080 
                                <E T="02">I</E>
                            </ENT>
                            <ENT O="xl"/>
                            <ENT>113.4</ENT>
                            <ENT>18.61</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4</ENT>
                            <ENT>0.60</ENT>
                            <ENT>
                                2040 
                                <E T="02">E</E>
                            </ENT>
                            <ENT O="xl"/>
                            <ENT>85.7</ENT>
                            <ENT>14.06</ENT>
                        </ROW>
                    </GPOTABLE>
                    <PRTPAGE P="62633"/>
                    <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12,12,14C,12,12">
                        <TTITLE>
                            Table 7—Predicted Rockland Hammock Habitat Changes With an Intermediate (I) or Extreme (E) RSLR (Relative Sea Level Rise; Sweet et al. 2017, pp. vi, vii, 12, 21) and Moderate High Tide Effect (2.7 ft (0.82 
                            <E T="01">m</E>
                            )), in the Years 2040, 2060 and 2080, in the Upper Florida Keys
                        </TTITLE>
                        <BOXHD>
                            <CHED H="1">Future scenario</CHED>
                            <CHED H="1">RSLR height (m)</CHED>
                            <CHED H="1">Year</CHED>
                            <CHED H="1">Current rockland hammock (ac) in upper Keys</CHED>
                            <CHED H="1">Area (ac) of rockland hammock affected by both RSLR and high tide</CHED>
                            <CHED H="1">Percent of rockland hammock affected by both RSLR and high tide</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">1</ENT>
                            <ENT>0.31</ENT>
                            <ENT>
                                2040 
                                <E T="02">I</E>
                            </ENT>
                            <ENT>7,005.60</ENT>
                            <ENT>3,273.8</ENT>
                            <ENT>46.73</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2</ENT>
                            <ENT>0.54</ENT>
                            <ENT>
                                2060 
                                <E T="02">I</E>
                            </ENT>
                            <ENT O="xl"/>
                            <ENT>3,930.8</ENT>
                            <ENT>56.11</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3</ENT>
                            <ENT>0.83</ENT>
                            <ENT>
                                2080 
                                <E T="02">I</E>
                            </ENT>
                            <ENT O="xl"/>
                            <ENT>4,686.5</ENT>
                            <ENT>66.90</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4</ENT>
                            <ENT>0.60</ENT>
                            <ENT>
                                2040 
                                <E T="02">E</E>
                            </ENT>
                            <ENT O="xl"/>
                            <ENT>4,097.7</ENT>
                            <ENT>58.49</ENT>
                        </ROW>
                    </GPOTABLE>
                    <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12,12,14C,12,12">
                        <TTITLE>
                            Table 8—Predicted Pine Rocklands Habitat Changes With an Intermediate (I) or Extreme (E) RSLR (Relative Sea Level Rise; Sweet et al. 2017, pp. vi, vii, 12, 21) and Moderate High Tide Effect (2.7 ft (0.82 
                            <E T="01">m</E>
                            )), in the Years 2040, 2060 and 2080, in the Lower Florida Keys
                        </TTITLE>
                        <BOXHD>
                            <CHED H="1">Future scenario</CHED>
                            <CHED H="1">RSLR height (m)</CHED>
                            <CHED H="1">Year</CHED>
                            <CHED H="1">Current pine rocklands (ac) in lower Keys</CHED>
                            <CHED H="1">Area (ac) of pine rocklands affected by both RSLR and high tide</CHED>
                            <CHED H="1">Percent of pine rocklands affected by both RSLR and high tide</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">1</ENT>
                            <ENT>0.31</ENT>
                            <ENT>
                                2040 
                                <E T="02">I</E>
                            </ENT>
                            <ENT>1,899.35</ENT>
                            <ENT>1,674.4</ENT>
                            <ENT>88.16</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2</ENT>
                            <ENT>0.54</ENT>
                            <ENT>
                                2060 
                                <E T="02">I</E>
                            </ENT>
                            <ENT O="xl"/>
                            <ENT>1,834.9</ENT>
                            <ENT>96.61</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3</ENT>
                            <ENT>0.83</ENT>
                            <ENT>
                                2080 
                                <E T="02">I</E>
                            </ENT>
                            <ENT O="xl"/>
                            <ENT>1,898.9</ENT>
                            <ENT>99.98</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4</ENT>
                            <ENT>0.60</ENT>
                            <ENT>
                                2040 
                                <E T="02">E</E>
                            </ENT>
                            <ENT O="xl"/>
                            <ENT>1,864.9</ENT>
                            <ENT>98.19</ENT>
                        </ROW>
                    </GPOTABLE>
                    <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12,12,14C,12,12">
                        <TTITLE>
                            Table 9—Predicted Rockland Hammock Habitat Changes With an Intermediate (I) or Extreme (E) RSLR (Relative Sea Level Rise; Sweet et al. 2017, pp. vi, vii, 12, 21) and Moderate High Tide Effect (2.7 ft [0.82 
                            <E T="01">m</E>
                            ]), in the Years 2040, 2060 and 2080, in the Lower Florida Keys
                        </TTITLE>
                        <BOXHD>
                            <CHED H="1">Future scenario</CHED>
                            <CHED H="1">RSLR height (m)</CHED>
                            <CHED H="1">Year</CHED>
                            <CHED H="1">Current rockland hammock (ac) in lower Keys</CHED>
                            <CHED H="1">Area (ac) of rockland hammock affected by both RSLR and high tide</CHED>
                            <CHED H="1">Percent of rockland hammock affected by both RSLR and high tide</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">1</ENT>
                            <ENT>0.31</ENT>
                            <ENT>
                                2040 
                                <E T="02">I</E>
                            </ENT>
                            <ENT>3,805.60</ENT>
                            <ENT>3,668.3</ENT>
                            <ENT>96.39</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2</ENT>
                            <ENT>0.54</ENT>
                            <ENT>
                                2060 
                                <E T="02">I</E>
                            </ENT>
                            <ENT O="xl"/>
                            <ENT>3,749.5</ENT>
                            <ENT>98.53</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3</ENT>
                            <ENT>0.83</ENT>
                            <ENT>
                                2080 
                                <E T="02">I</E>
                            </ENT>
                            <ENT O="xl"/>
                            <ENT>3,778.4</ENT>
                            <ENT>99.29</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4</ENT>
                            <ENT>0.60</ENT>
                            <ENT>
                                2040 
                                <E T="02">E</E>
                            </ENT>
                            <ENT O="xl"/>
                            <ENT>3,758.2</ENT>
                            <ENT>98.75</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>Extreme weather events are another impact of climate change likely to impact pine rocklands and rockland hammock habitat. Plant species common to both habitats have little ability to tolerate salt stress due to saltwater intrusion or inundation owing to high tide events and sea level rise. Although the effects during severe storm events may be temporary, high mortality of pine rocklands and rockland hammock plant species may occur. Thus, climate change-induced storm events may reduce the resiliency of both pine rocklands and rockland hammock habitats.</P>
                    <P>
                        Annual average temperature over the contiguous United States is projected to rise. Increases of approximately 2.5 °F (1.4 °C) are projected for the period 2021-2050 relative to 1976-2005 in all representative concentration pathway (RCP) greenhouse gas emission scenarios, implying recent record-setting years may be common in the next few decades. Much larger increases in temperature are projected by late century (2071-2100): 2.8-7.3 °F (1.6-4.1 °C) in RCP 4.5 and 5.8-11.9 °F (3.2-6.6 °C) in RCP 8.5 (USGCRP 2018, p. 159). In addition, extreme heat events in Florida are projected to increase relative to 1986-2005 (Service 2017, p. 2). Due to the already released, human-induced emissions of greenhouse gases present in the environment, another 0.5 °F (0.3 °C) increase in surface air temperature would be expected, even if there was a sudden end to all human-induced greenhouse gas emissions (Carter 
                        <E T="03">et al</E>
                        . 2014, pp. 414-415). For the State of Florida, this would equate to an increase of more than 30 to 40 days of extreme heat events for Florida's coastal areas (Service 2017, p. 2). An increase in temperature also causes an increase in evapotranspiration in plants, which will change vegetation growth and survival, leading to changes in plant communities, which could indirectly affect rim rock crowned snakes.
                    </P>
                    <P>
                        Extreme rainfall events have increased in frequency and intensity in the southeastern United States, and there is high confidence they will continue to increase in the future. Both the frequency and severity of extreme precipitation events are projected to continue increasing in the southeast region (Easterling 
                        <E T="03">et al</E>
                        . 2017, p. 223). Future projections of average precipitation are uncertain, but an increase in intense rainfall is projected. Although average summer precipitation may not change, higher temperatures will increase the rate of soil moisture loss, and, thereby, droughts will likely be more intense (USGCRP 2018, pp. 1004, 1134). Dry consecutive days are expected to increase up to 30 percent in south Florida by 2100 (Service 2017, p. 7). Extreme conditions can be 
                        <PRTPAGE P="62634"/>
                        detrimental for the rim rock crowned snake. Decreased water availability, exacerbated by population growth and land-use change, will continue to increase competition for water (USGCRP 2018, p. 1112). Increasing drought intensity will likely trigger more frequent wildfire events, which may be beneficial to rim rock crowned snake by increasing habitat quality. Additionally, greater rainfall rates during hurricanes are expected with about a 20 percent increase near the center of storms, increasing risks of severe and damaging flooding (Service 2017, pp. 4-5). Periods of extreme drought and/or heavy rainfall can cause losses and alteration in plant and animal communities, which could affect the rim rock crowned snake directly or indirectly. For example, with an increase in flooding frequency, rim rock crowned snakes may be more frequently displaced from underground refugia, leading to higher mortality risk. Alternatively, more periods of extreme drought may reduce the abundance of prey, decreasing the ability of rim rock crowned snakes to feed. Climate change-induced shifts in seasonal patterns of rainfall and temperature may reduce the rim rock crowned snake's overall resiliency, especially when extreme events occur within areas of multiple populations.
                    </P>
                    <HD SOURCE="HD3">Future Scenarios</HD>
                    <P>In all four future scenarios, habitat supporting the rim rock crowned snake is expected to undergo significant losses due to regional sea level rise, particularly in the lower Florida Keys. Populations in Miami-Dade County would be the least impacted by regional sea level rise and saltwater intrusion. Under the highest climate impacts, by 2080, 18.6 percent of rockland hammock habitat and only 2.3 percent of pine rocklands habitat in Miami-Dade County would be affected by regional sea level rise (see tables 5 and 6, above; see also Service 2021b, table 13). Therefore, no additional mortality in that part of the range from regional sea level rise and high tide would be expected due to little habitat loss or alteration. However, as discussed earlier, land development pressure on remaining undeveloped lands in pine rocklands is expected to be high, as is fire suppression. Of the 2,898 ac (1,173 ha) of suitable habitat in Miami-Dade County, 82.6 percent is protected; however, these areas will still be affected by ongoing habitat degradation. The remaining unprotected habitat (17.4 percent) will likely be lost or degraded due to high development pressure, which could result in total loss, encroachment, or fire suppression of the habitat. The result of these impacts is a decrease in resiliency for all populations in Miami-Dade County under all future scenarios (Table 10).</P>
                    <P>Storm events and associated storm surges will be a greater source of mortality and habitat alteration throughout the Florida Keys in all future scenarios, therefore reducing population resiliency. Projected sea level rise will increase the inland penetration and residence time of saltwater during storm surge events, and impact the freshwater lens, both of which will accelerate habitat modification and loss. Additionally, sea level rise in the Florida Keys will increase saltwater intrusion and inundation, and root zone salinity over the coming decades. This will result in the loss of habitat, changes in freshwater-dependent habitat, and loss of individual snakes. In the upper Florida Keys, between 46.7 and 58.5 percent of rockland hammock habitat could be lost to sea level rise, with the severity and timing varying with each climate scenario (see table 7, above). The most severe impacts are expected in the lower Florida Keys, with habitat losses due to relative sea level rise and high tides of 88.2 and 96.4 percent of pine rocklands and rockland hammock habitats, respectively (see tables 8 and 9, above). Overall, we expect a trend toward a reduction of populations in the upper Florida Keys and probable extirpation of populations in the lower Florida Keys (table 10).</P>
                    <P>The ability of this species to adapt to changing environmental conditions is extremely limited. The rim rock crowned snake will not survive living in the anticipated more saline or more wet habitat, both of which will alter the vegetation community. This reduction in suitable habitat will lead to fewer populations and individuals occurring in the Keys. Therefore, a reduction in species representation in the lower and upper Florida Keys populations is expected. However, a reduction in species representation is not expected in the Miami-Dade County populations under any future scenario, despite a decline in resiliency of these populations.</P>
                    <P>Redundancy is currently low for the rim rock crowned snake, and with the continued loss or degradation to its habitat in the lower and upper Florida Keys as outlined above, we expect loss of populations, thereby further reducing the species' ability to withstand catastrophic events such as hurricanes. Although the rim rock crowned snake populations in Miami-Dade County are largely unaffected in all future scenarios in that they are projected to remain extant, the loss of populations in the lower (extirpation by 2040) and upper Florida Keys leaves the rim rock crowned snake more vulnerable to extinction.</P>
                    <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s40,r25,r30,r30,r30,r30">
                        <TTITLE>Table 10—Predicted Population Condition of the RRCS Under Four Scenarios</TTITLE>
                        <BOXHD>
                            <CHED H="1">Area</CHED>
                            <CHED H="1">Current</CHED>
                            <CHED H="1">2040I</CHED>
                            <CHED H="1">2060I</CHED>
                            <CHED H="1">2080I</CHED>
                            <CHED H="1">2040E</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Lower Florida Keys</ENT>
                            <ENT>Low</ENT>
                            <ENT>Possibly extirpated</ENT>
                            <ENT>Presumed extirpated</ENT>
                            <ENT>Presumed extirpated</ENT>
                            <ENT>Presumed extirpated</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Upper Florida Keys</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Miami-Dade County</ENT>
                            <ENT>Moderate</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                            <ENT>Low</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD1">Determination</HD>
                    <P>Section 4 of the Act (16 U.S.C. 1533) and its implementing regulations (50 CFR part 424) set forth the procedures for determining whether a species meets the definition of an endangered species or a threatened species. The Act defines an “endangered species” as a species in danger of extinction throughout all or a significant portion of its range, and a “threatened species” as a species likely to become an endangered species within the foreseeable future throughout all or a significant portion of its range. The Act requires that we determine whether a species meets the definition of endangered species or threatened species because of any of the following factors: (A) The present or threatened destruction, modification, or curtailment of its habitat or range; (B) overutilization for commercial, recreational, scientific, or educational purposes; (C) disease or predation; (D) the inadequacy of existing regulatory mechanisms; or (E) other natural or manmade factors affecting its continued existence.</P>
                    <P>
                        For both the Key ring-necked snake and the rim rock crowned snake, we 
                        <PRTPAGE P="62635"/>
                        presented summary evaluations of six threats analyzed in the SSAs: Development (Factor A), fire suppression (Factor A), sea level rise (Factor A), saltwater intrusion (Factor A), shifts in seasonal patterns of rainfall and temperature (Factor A), and storm events (Factor A). We also evaluated existing regulatory mechanisms (Factor D) and ongoing conservation measures. In the SSA, we also considered four additional potential threats: overutilization due to recreational, educational, and scientific use (Factor B); disease (Factor C); predation (Factor C), and invasive species (Factor E). We concluded that, as indicated by the best available scientific and commercial information, these four potential threats are currently having little to no impact on either the Key ring-necked snake or the rim rock crowned snake and their habitats, and thus their overall effects now and into the future are expected to be minimal. However, we consider them in the determination for each species, because although these minor threats may have low impacts on their own, combined with impacts of other threats, they could further reduce the already low number of Key ring-necked snakes or rim rock crowned snakes.
                    </P>
                    <P>In considering the foreseeable future for the Key ring-necked snake and the rim rock crowned snake, we analyzed expected changes in development through 2070 based on the available model datasets, shifts in seasonal patterns of rainfall and temperature through 2100, and climate change (sea level rise and saltwater intrusion) from 2030 to 2100. That said, we focused on changes that are expected in the next 60 years because virtually no habitat for either species is forecasted to be present in the lower Florida Keys by 2080. We determined that this timeframe represents a period of time for which we can reliably predict both the threats to the species and the species' response to those threats.</P>
                    <HD SOURCE="HD2">Key Ring-Necked Snake: Status Throughout All of Its Range</HD>
                    <P>The Key ring-necked snake is a narrow endemic that inhabits a limited range, with individuals recorded on seven islands. Historically, urban development and historical conversion of suitable habitat for agriculture greatly reduced the extent of suitable habitat for the Key ring-necked snake. Currently, degradation associated with urbanization and fire suppression of pine rocklands is decreasing the quality of remaining habitat, and thereby decreasing population resiliency. Much of the pine rockland habitat where the Key ring-necked snake is found is protected; however, the remaining parcels are at very high risk of development. Since the Key ring-necked snake's range is so limited, any development of habitat that supports the subspecies would have a high level of impact on the subspecies, decreasing both population resiliency and the already limited redundancy.</P>
                    <P>Furthermore, effects associated with climate change and sea level rise (that is, higher tidal surges, coastal and inland flooding, saltwater intrusion) are already being observed in the Florida Keys. Before the effects of inundation due to sea level rise are fully realized, vegetation succession to a halophytic dominated habitat occurs as pine rockland plant species, particularly the dominant canopy species (slash pine), have little ability to tolerate saltwater. Thus, saltwater intrusion has resulted in degradation and loss of suitable pine rocklands habitat as well as the freshwater sources on which the Key ring-necked snake relies. Currently, habitat succession due to saltwater intrusion has resulted in conversion of suitable habitat for the Key ring-necked snake from rockland or hammock habitat into habitat that is unsuitable for the species such as salt-tolerant mangroves. Sea level rise is exacerbated by effects from increased rainfall and higher than average storm surges from hurricanes and other tropical storms. Because of their low mean elevation of less than 4 ft (1.2 m), the lowest parts of the Florida Keys are highly susceptible to flooding, with parts of the islands farther upland at risk of inundation and saltwater intrusion from these storm events. As a result of these ongoing impacts and others identified above, the seven known populations of the Key ring-necked snake are currently in low condition, and the overall viability of the species is likely reduced from historical levels.</P>
                    <P>The primary threat currently facing the Key ring-necked snake is climate change and sea level rise. All effects associated with climate change are interrelated, with increases in the magnitude of severe storms contributing to increased flooding events that have the potential to extirpate populations of the Key ring-necked snake. Although a severe hurricane is unlikely to flood all populations at once, if a hurricane were to extirpate most populations, it would leave the remainder of the subspecies significantly more vulnerable to other threats. In addition to effects associated with current rates of sea level rise, storms are also becoming more frequent and intense, accelerating habitat modification and further reducing population resiliency.</P>
                    <P>After evaluating threats to the species and assessing the cumulative effect of the threats under the Act's section 4(a)(1) factors, we find that the Key ring-necked snake is currently experiencing significant impacts due to development, fire suppression, climate change, and sea level rise throughout its very limited range. Because the Key ring-necked snake is endemic to only the lower Florida Key islands, and all populations for the species are in low condition due to impacts of threats (such as ongoing habitat degradation, fire suppression, and impacts from saltwater intrusion), we find the species is at a high risk of extinction. Thus, after assessing the best available information, we conclude that the Key ring-necked snake is in danger of extinction throughout all of its range.</P>
                    <HD SOURCE="HD2">Key Ring-Necked Snake: Status Throughout a Significant Portion of Its Range</HD>
                    <P>
                        Under the Act and our implementing regulations, a species may warrant listing if it is in danger of extinction or likely to become so in the foreseeable future throughout all or a significant portion of its range. We have determined that the Key ring-necked snake is in danger of extinction throughout all of its range and accordingly did not undertake an analysis of any significant portion of its range. Because the Key ring-necked snake warrants listing as endangered throughout all of its range, our determination does not conflict with the decision in 
                        <E T="03">Center for Biological Diversity</E>
                         v. 
                        <E T="03">Everson,</E>
                         435 F. Supp. 3d 69 (D.D.C. 2020) (
                        <E T="03">Everson</E>
                        ), which vacated the provision of the SPR Policy providing that if the Services determine that a species is threatened throughout all of its range, the Services will not analyze whether the species is endangered in a significant portion of its range.
                    </P>
                    <HD SOURCE="HD2">Key Ring-Necked Snake: Determination of Status</HD>
                    <P>Our review of the best available scientific and commercial information indicates that the Key ring-necked snake meets the definition of an endangered species. Therefore, we propose to list the Key ring-necked snake as an endangered species in accordance with sections 3(6) and 4(a)(1) of the Act.</P>
                    <HD SOURCE="HD2">Rim Rock Crowned Snake: Status Throughout All of Its Range</HD>
                    <P>
                        The rim rock crowned snake is endemic to only the southeastern part of the Florida peninsula and the Florida Keys. Currently, the resiliency of the seven populations in the Miami-Dade area is moderate, and the resiliency of 
                        <PRTPAGE P="62636"/>
                        the eight populations in the Florida Keys is low. However, the rim rock crowned snake is facing a variety of threats across its range. The effects of urbanization and degradation are impacting the rim rock crowned snake across its range, but the effects are particularly severe in eastern Miami-Dade County. Although 75 percent of remaining suitable habitat for the rim rock crowned snake in that part of the range is protected, the habitat is spread across Miami-Dade County in small, isolated fragments. These fragments are undergoing degradation due to edge effects, and pine rocklands habitat is being further degraded due to fire suppression, which causes it to undergo transition to dense canopy that is less suitable for the rim rock crowned snake. Thus, although individual populations are currently less likely to be lost to new development, ongoing habitat degradation associated with urbanization and fire suppression in pine rocklands will continue to reduce the availability of features that the rim rock crowned snake needs, thus decreasing population resiliency. Although several populations in this part of the species' range are extant, we expect the effects of habitat degradation will increase in magnitude into the future, particularly in pine rocklands habitat where prescribed burning does not occur, further reducing resiliency.
                    </P>
                    <P>Rangewide, the rim rock crowned snake is also facing threats due to the ongoing occurrence of more severe storms and the increased incidence and intensity of storm surge that accompanies these storms. Increased rainfall, along with the threats of sea level rise and higher than average storm surges, is already reducing the amount of available habitat due to inundation, particularly within the Florida Keys. Because of their low mean elevation of less than 4 ft (1.2 m), the lowest parts of the Florida Keys are highly susceptible to flooding, with parts of the islands farther upland at risk of inundation and saltwater intrusion from these storm events. Saltwater intrusion has resulted in degradation and loss of suitable pine rocklands and rockland hammock habitats—through vegetation shifting to halophytic species—in the Florida Keys as well as the freshwater sources on which the rim rock crowned snake relies. All of this, in turn, negatively affects snake movement, reproduction, and food availability. Succession to more halophytic vegetation has likely altered the density and type of prey available to the rim rock crowned snake in these areas, decreasing population resiliency. In addition, the underground spaces, such as the limestone substrate that the rim rock crowned snake inhabits, are vulnerable to sea level rise, and increased frequency in flooding of underground areas increases the amount of time that species are displaced from refugia. This displacement makes them more vulnerable to predation, and combined with losses of foraging and breeding opportunities (reproduction), this further decreases population resiliency. Although a severe hurricane would be unlikely to flood all populations across the species' range at once, if a hurricane were to extirpate multiple populations, it would leave the remainder of the species significantly more vulnerable to other threats, including threats that currently only have a minor impact on the species.</P>
                    <P>Given the species' limited distribution and limited ecological setting, species representation is currently low. However, the species has moderate redundancy, as it has multiple populations distributed throughout the Miami-Dade area (7 populations in moderate condition) and the Upper and Lower Florida Keys (8 populations in low condition). Thus, although these threats may cause the species to become endangered in the foreseeable future, we do not find that threats at their current magnitude are reducing resiliency and redundancy such that the species is in danger of extinction now across the species' range.</P>
                    <P>In the foreseeable future, we anticipate that threats associated with climate change, including the effects of storm events (for example, storm surges, high tide), saltwater intrusion, and sea level rise, will continue to increase in magnitude and have the greatest influence on population resiliency, particularly in the Florida Keys. Tropical storms will continue to become more frequent and intense, accelerating habitat modification and reducing population resiliency. Additionally, the Florida Keys will continue to face increased saltwater intrusion and sea level rise, which will continue to cause habitat alteration and loss. Acting together, these threats will cause irreversible habitat modification and loss that will be further exacerbated by ongoing and increasing levels of inundation. Populations of the rim rock crowned snake in the lower and upper Florida Keys may begin experiencing significant losses in the next 10-20 years. By 2040, the upper Keys populations will experience loss of nearly half of its current habitat and the lower Keys populations may potentially be extirpated.</P>
                    <P>In Miami-Dade County, the effects of storm events (for example, storm surges, high tide), saltwater intrusion, and sea level rise would not exert much influence on population resiliency in the foreseeable future. However, given that there is a relatively low amount of suitable habitat to begin with (2,898 ac (1,172.8 ha)) when compared to the Florida Keys (12,711 ac (5,144 ha)), additional threats may exert pressure, which in combination, could stress the resiliency of the Miami-Dade populations, and further reduce species redundancy as a whole in the future. Dispersal of individual snakes to other populations is unlikely and would only occur in isolated, random circumstances.</P>
                    <P>The urban environment of metropolitan Miami presents many challenges for dispersing snakes, including roads, highways, commercial and residential development, canals, and vast storm water retention areas. Encroachment and degradation are likely to increase in magnitude in the foreseeable future for most remaining habitat, and risk of development of the 25 percent of unprotected suitable habitat in Miami-Dade County is high. As the urban interface of metropolitan Miami increases in density, the likelihood of prescribed burning decreases, which in turn decreases remaining habitat quality. If the habitat in Miami-Dade County is the only remaining habitat within the rim rock crowned snake's range due to the effects of climate change discussed above in the Florida Keys, extinction may occur much more quickly due to the small amount of suitable habitat left on the mainland, which will likely degrade in quality, with populations becoming increasingly isolated from one another.</P>
                    <P>
                        After evaluating threats to the species and assessing the cumulative effect of the threats under the Act's section 4(a)(1) factors, we find that the rim rock crowned snake is facing threats across its range due to development, fragmentation, and effects associated with climate change. However, the species currently maintains enough population resiliency and species redundancy that it is not in danger of extinction now. Within the foreseeable future, unprotected habitat in eastern Miami-Dade County will continue to be lost due to development, and protected habitat will continue to undergo degradation due to edge effects and fire suppression. In the Florida Keys, up to half of available habitat in the upper Keys and nearly all habitat in the lower Keys could be lost by 2040. Thus, after assessing the best available information, we conclude that the rim rock crowned 
                        <PRTPAGE P="62637"/>
                        snake is not currently in danger of extinction but is likely to become in danger of extinction within the foreseeable future throughout all of its range.
                    </P>
                    <HD SOURCE="HD2">Rim Rock Crowned Snake: Status Throughout a Significant Portion of Its Range</HD>
                    <P>
                        Under the Act and our implementing regulations, a species may warrant listing if it is in danger of extinction or likely to become so in the foreseeable future throughout all or a significant portion of its range. The court in 
                        <E T="03">Everson</E>
                         vacated the aspect of the Final Policy on Interpretation of the Phrase “Significant Portion of Its Range” in the Endangered Species Act's Definitions of “Endangered Species” and “Threatened Species” (Final Policy) (79 FR 37578; July 1, 2014) that provided that the Service does not undertake an analysis of significant portions of a species' range if the species warrants listing as threatened throughout all of its range. Therefore, we proceed to evaluating whether the species is endangered in a significant portion of its range—that is, whether there is any portion of the species' range for which both (1) the portion is significant; and (2) the species is in danger of extinction in that portion. Depending on the case, it might be more efficient for us to address the “significance” question or the “status” question first. We can choose to address either question first. Regardless of which question we address first, if we reach a negative answer with respect to the first question that we address, we do not need to evaluate the other question for that portion of the species' range.
                    </P>
                    <P>
                        Following the court's holding in 
                        <E T="03">Everson,</E>
                         we now consider whether there are any significant portions of the species' range where the species is in danger of extinction now (that is, endangered). In undertaking this analysis for the rim rock crowned snake, we choose to address the status question first—we consider information pertaining to the geographic distribution of both the species and the threats that the species faces to identify any portions of the range where the species is endangered.
                    </P>
                    <P>For the rim rock crowned snake, we considered whether there are any portions of the species' current range that may have a different status. We identified the Florida Keys portion of the species' range because all eight populations are currently in low condition. Within the Florida Keys, the effects associated with climate change and sea level rise (that is, higher tidal surges, coastal and inland flooding, saltwater intrusion) are already being observed. Before the effects of inundation due to sea level rise are fully realized, vegetation succession to a halophytic dominated habitat occurs as pine rockland species, particularly the dominant canopy species (slash pine), have little ability to tolerate saltwater. Thus, saltwater intrusion has resulted in degradation and loss of suitable pine rocklands habitat as well as the freshwater sources on which the rim rock crowned snake relies. Currently, habitat succession due to saltwater intrusion has resulted in conversion of suitable habitat for the rim rock crowned snake from rockland or hammock habitat into habitat that is unsuitable for the species, such as salt-tolerant mangroves. Succession to more halophytic vegetation has likely altered the density and type of prey available to the rim rock crowned snake in these areas, decreasing population resiliency.</P>
                    <P>Sea level rise is exacerbated by effects from increased rainfall and higher than average storm surges from hurricanes and other tropical storms. Underground spaces, such as the limestone substrate that the rim rock crowned snake inhabits, are vulnerable to sea level rise. Increased frequency in flooding of subterranean areas increases the amount of time that species are displaced from refugia, making them more vulnerable to predation and extreme temperatures. This, combined with losses of foraging and breeding opportunities, further decreases population resiliency.</P>
                    <P>As mentioned above, within the Florida Keys portion, the eight populations currently have low resiliency. Given the species' current condition within the Keys and ongoing impacts from climate change and sea level rise which are already being realized, we find that the Florida Keys portion of the rim rock crowned snake is in danger of extinction.</P>
                    <P>
                        We then proceeded to the significance question, asking whether this portion of the range (
                        <E T="03">i.e.,</E>
                         the Florida Keys portion of the rim rock crowned snake) is significant. The Service's most recent definition of “significant” within agency policy guidance has been invalidated by court order (see 
                        <E T="03">Desert Survivors</E>
                         v. 
                        <E T="03">U.S. Department of the Interior,</E>
                         321 F. Supp. 3d 1011, 1070-74 (N.D. Cal. 2018)). In undertaking this analysis for the rim rock crowned snake, we considered whether the Florida Keys portion of the species' range may be significant based on its biological importance to the overall viability of the rim rocked crown snake. Therefore, for the purposes of this analysis, when considering whether this portion is significant, we considered whether the portion may (1) occur in a unique habitat or ecoregion for the species, (2) contain high quality or high value habitat relative to the remaining portions of the range, for the species' continued viability in light of the existing threats, (3) contain habitat that is essential to a specific life-history function for the species and that is not found in the other portions (for example, the principal breeding ground for the species) or (4) contain a large geographic portion of the suitable habitat relative to the remaining portions of the range for the species.
                    </P>
                    <P>The Florida Keys portion of the range contains the largest patches of intact pine rockland and rockland hammock habitats within the rim rock crowned snake's range. Currently, the Florida Keys accounts for roughly 82 percent (12,711 of 15,595 ac (5,144 of 6,311 ha)) of suitable pine rockland and rockland hammock habitat and 53 percent (8 of 15) of extant populations within the range of the rim rock crowned snake. In the lower Florida Keys, the total area of pine rocklands habitat is approximately 1,899 ac (769 ha), and the total area of rockland hammock habitat is approximately 3,806 ac (1,540 ha). While the hammock habitats are widespread across many islands in various sizes, pine rocklands remain on only five islands in the lower Florida Keys and none of the upper Florida Keys. The total area covered by rockland hammock in the upper Florida Keys is 7,006 ac (2,835 ha). The Florida Keys portion constitutes a large geographic area relative to the remaining portions of the range, as this area encompasses 82 percent of the rangewide suitable habitat for the rim rock crowned snake. Therefore, having assessed the Florida Keys portion's biological significance in terms of the above habitat considerations, we find the information substantially indicates this portion is significant to the rim rock crowned snake.</P>
                    <P>
                        Accordingly, having determined that the Florida Keys portion of the species' range (1) is significant, and (2) is currently in danger of extinction, we find the rim rock crowned snake meets the definition of an endangered species. This is consistent with the courts' holdings in 
                        <E T="03">Desert Survivors</E>
                         v. 
                        <E T="03">Department of the Interior,</E>
                         321 F. Supp. 3d 1011 (N.D. Cal. 2018), and Center for Biological Diversity v. Jewell, 248 F. Supp. 3d, 946, 959 (D. Ariz. 2017)
                    </P>
                    <HD SOURCE="HD2">Rim Rock Crowned Snake: Determination of Status</HD>
                    <P>
                        Our review of the best available scientific and commercial information indicates that the rim rock crowned snake meets the Act's definition of an 
                        <PRTPAGE P="62638"/>
                        endangered species. Therefore, we propose to list the rim rock crowned snake as an endangered species in accordance with sections 3(6) and 4(a)(1) of the Act.
                    </P>
                    <HD SOURCE="HD1">Available Conservation Measures</HD>
                    <P>Conservation measures provided to species listed as endangered or threatened species under the Act include recognition as a listed species, planning and implementation of recovery actions, requirements for Federal protection, and prohibitions against certain practices. Recognition through listing results in public awareness, and conservation by Federal, State, Tribal, and local agencies, private organizations, and individuals. The Act encourages cooperation with the States and other countries and calls for recovery actions to be carried out for listed species. The protection required by Federal agencies, including the Service, and the prohibitions against certain activities are discussed, in part, below.</P>
                    <P>The primary purpose of the Act is the conservation of endangered and threatened species and the ecosystems upon which they depend. The ultimate goal of such conservation efforts is the recovery of these listed species, so that they no longer need the protective measures of the Act. Section 4(f) of the Act calls for the Service to develop and implement recovery plans for the conservation of endangered and threatened species. The goal of this process is to restore listed species to a point where they are secure, self-sustaining, and functioning components of their ecosystems.</P>
                    <P>
                        The recovery planning process begins with development of a recovery outline made available to the public soon after a final listing determination. The recovery outline guides the immediate implementation of urgent recovery actions while a recovery plan is being developed. Recovery teams (composed of species experts, Federal and State agencies, nongovernmental organizations, and stakeholders) may be established to develop and implement recovery plans. The recovery planning process involves the identification of actions that are necessary to halt and reverse the species' decline by addressing the threats to its survival and recovery. The recovery plan identifies recovery criteria for review of when a species may be ready for reclassification from endangered to threatened (“downlisting”) or removal from protected status (“delisting”), and methods for monitoring recovery progress. Recovery plans also establish a framework for agencies to coordinate their recovery efforts and provide estimates of the cost of implementing recovery tasks. Revisions of the plan may be done to address continuing or new threats to the species, as new substantive information becomes available. The recovery outline, draft recovery plan, final recovery plan, and any revisions will be available on our website as they are completed (
                        <E T="03">https://www.fws.gov/endangered</E>
                        ), or from our Florida Ecological Services Field Office (see 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        ).
                    </P>
                    <P>Implementation of recovery actions generally requires the participation of a broad range of partners, including other Federal agencies, States, Tribes, nongovernmental organizations, businesses, and private landowners. Examples of recovery actions include habitat restoration (for example, restoration of native vegetation), research, captive propagation and reintroduction, and outreach and education. The recovery of many listed species cannot be accomplished solely on Federal lands because their range may occur primarily or solely on non-Federal lands. To achieve recovery of these species requires cooperative conservation efforts on private, State, and Tribal lands.</P>
                    <P>
                        If these species are listed, funding for recovery actions will be available from a variety of sources, including Federal budgets, State programs, and cost-share grants for non-Federal landowners, the academic community, and nongovernmental organizations. Additionally, pursuant to section 6 of the Act, the State of Florida would be eligible for Federal funds to implement management actions that promote the protection or recovery of the Key ring-necked snake and the rim rock crowned snake. Information on our grant programs that are available to aid species recovery can be found at: 
                        <E T="03">https://www.fws.gov/service/financial-assistance.</E>
                    </P>
                    <P>
                        Although the Key ring-necked snake and the rim rock crowned snake are only proposed for listing under the Act at this time, please let us know if you are interested in participating in recovery efforts for these species. Additionally, we invite you to submit any new information on these species whenever it becomes available and any information you may have for recovery planning purposes (see 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        ).
                    </P>
                    <P>Section 7(a) of the Act requires Federal agencies to evaluate their actions with respect to any species that is proposed or listed as an endangered or threatened species and with respect to its critical habitat. Regulations implementing this interagency cooperation provision of the Act are codified at 50 CFR part 402. Section 7(a)(4) of the Act requires Federal agencies to confer with the Service on any action that is likely to jeopardize the continued existence of a species proposed for listing or result in destruction or adverse modification of proposed critical habitat. If a species is listed subsequently, section 7(a)(2) of the Act requires Federal agencies to ensure that activities they authorize, fund, or carry out are not likely to jeopardize the continued existence of the species or destroy or adversely modify its critical habitat. If a Federal action may affect a listed species or its critical habitat, the responsible Federal agency must enter into consultation with the Service.</P>
                    <P>
                        For the Key ring-necked snake, Federal agency actions within the species' habitat that may require conference, consultation, or both, with the Service as described in the preceding paragraph could include management and any other landscape-altering activities on Federal lands administered by the administered by the Service (National Key Deer Refuge); issuance of section 404 Clean Water Act (33 U.S.C. 1251 
                        <E T="03">et seq.</E>
                        ) permits by the U.S. Army Corps of Engineers; construction and management of pipeline and power line rights-of-way by the Federal Energy Regulatory Commission; construction and maintenance of roads, bridges, or highways by the Federal Highway Administration.
                    </P>
                    <P>
                        For the rim rock crowned snake, Federal agency actions within the species' habitat that may require conferencing with the Service as described in the preceding paragraph could include management and any other landscape-altering activities on Federal lands administered by the administered by the Service (National Key Deer Refuge, Crocodile Lake National Wildlife Refuge); issuance of section 404 Clean Water Act (33 U.S.C. 1251 
                        <E T="03">et seq.</E>
                        ) permits by the U.S. Army Corps of Engineers; construction and management of pipeline and power line rights-of-way by the Federal Energy Regulatory Commission; construction and maintenance of roads, bridges, or highways by the Federal Highway Administration.
                    </P>
                    <P>
                        The Act and its implementing regulations set forth a series of general prohibitions and exceptions that apply to endangered wildlife. The prohibitions of section 9(a)(1) of the Act, codified at 50 CFR 17.21, make it illegal for any person subject to the jurisdiction of the United States to take (which includes harass, harm, pursue, hunt, shoot, 
                        <PRTPAGE P="62639"/>
                        wound, kill, trap, capture, or collect; or to attempt any of these) endangered wildlife within the United States or on the high seas. In addition, it is unlawful to import; export; deliver, receive, carry, transport, or ship in interstate or foreign commerce in the course of commercial activity; or sell or offer for sale in interstate or foreign commerce any species listed as an endangered species. It is also illegal to possess, sell, deliver, carry, transport, or ship any such wildlife that has been taken illegally. Certain exceptions apply to employees of the Service, the National Marine Fisheries Service, other Federal land management agencies, and State conservation agencies.
                    </P>
                    <P>We may issue permits to carry out otherwise prohibited activities involving endangered wildlife under certain circumstances. Regulations governing permits are codified at 50 CFR 17.22. With regard to endangered wildlife, a permit may be issued for the following purposes: for scientific purposes, to enhance the propagation or survival of the species, and for incidental take in connection with otherwise lawful activities. The statute also contains certain exemptions from the prohibitions, which are found in sections 9 and 10 of the Act.</P>
                    <P>
                        It is our policy, as published in the 
                        <E T="04">Federal Register</E>
                         on July 1, 1994 (59 FR 34272), to identify to the maximum extent practicable at the time a species is listed those activities that would or would not constitute a violation of section 9 of the Act. The intent of this policy is to increase public awareness of the effect of a proposed listing on proposed and ongoing activities within the range of the species proposed for listing. Based on the best available information, the following actions are unlikely to result in a violation of section 9 for the Key ring-necked snake or the rim rock crowned snake, if these activities are carried out in accordance with existing regulations and permit requirements; this list is not comprehensive:
                    </P>
                    <P>(1) Recreational use with minimal ground disturbance (for example, hiking, walking); and</P>
                    <P>(2) Herbicide and pesticide use that is carried out in accordance with any existing regulations, permit and label requirements, and best management practices.</P>
                    <P>Based on the best available information, the following activities may potentially result in a violation of section 9 of the Act for the Key ring-necked snake or rim rock crowned snake if they are not authorized in accordance with applicable law; this list is not comprehensive:</P>
                    <P>(1) Unauthorized handling or collecting of the species;</P>
                    <P>(2) Sale or purchase of specimens, except for properly documented antique specimens of this taxon at least 100 years old, as defined by section 10(h)(1) of the Act.</P>
                    <P>(3) Activities resulting in ground disturbance in occupied Key ring-necked snake or rim rock crowned snake habitat (for example, plowing, mowing, burning, land leveling or clearing, grading, disking, soil compaction, soil removal, dredging, excavation, deposition of dredged or fill material, erosion and deposition of sediment/soil);</P>
                    <P>(4) Introduction of nonnative species that compete with or prey upon the Key ring-necked snake or rim rock crowned snakes.</P>
                    <P>
                        Questions regarding whether specific activities would constitute a violation of section 9 of the Act should be directed to the Florida Ecological Services Field Office (see 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        ).
                    </P>
                    <HD SOURCE="HD1">II. Critical Habitat for the Key Ring-Necked Snake and the Rim Rock Crowned Snake</HD>
                    <HD SOURCE="HD1">Background</HD>
                    <P>Critical habitat is defined in section 3 of the Act as:</P>
                    <P>(1) The specific areas within the geographical area occupied by the species, at the time it is listed in accordance with the Act, on which are found those physical or biological features:</P>
                    <P>(a) Essential to the conservation of the species, and</P>
                    <P>(b) Which may require special management considerations or protection; and</P>
                    <P>(2) Specific areas outside the geographical area occupied by the species at the time it is listed, upon a determination that such areas are essential for the conservation of the species.</P>
                    <P>
                        Our regulations at 50 CFR 424.02 define the geographical area occupied by the species as an area that may generally be delineated around species' occurrences, as determined by the Secretary (that is, range). Such areas may include those areas used throughout all or part of the species' life cycle, even if not used on a regular basis (
                        <E T="03">e.g.,</E>
                         migratory corridors, seasonal habitats, and habitats used periodically, but not solely by vagrant individuals).
                    </P>
                    <P>Conservation, as defined under section 3 of the Act, means to use and the use of all methods and procedures that are necessary to bring an endangered or threatened species to the point at which the measures provided pursuant to the Act are no longer necessary. Such methods and procedures include, but are not limited to, all activities associated with scientific resources management such as research, census, law enforcement, habitat acquisition and maintenance, propagation, live trapping, and transplantation, and, in the extraordinary case where population pressures within a given ecosystem cannot be otherwise relieved, may include regulated taking.</P>
                    <P>Critical habitat receives protection under section 7 of the Act through the requirement that Federal agencies ensure, in consultation with the Service, that any action they authorize, fund, or carry out is not likely to result in the destruction or adverse modification of critical habitat. The designation of critical habitat does not affect land ownership or establish a refuge, wilderness, reserve, preserve, or other conservation area. Such designation also does not allow the government or public to access private lands. Such designation does not require implementation of restoration, recovery, or enhancement measures by non-Federal landowners. Where a landowner requests Federal agency funding or authorization for an action that may affect a listed species or critical habitat, the Federal agency would be required to consult with the Service under section 7(a)(2) of the Act. However, even if the Service were to conclude that the proposed activity would result in destruction or adverse modification of the critical habitat, the Federal action agency and the landowner are not required to abandon the proposed activity, or to restore or recover the species; instead, they must implement “reasonable and prudent alternatives” to avoid destruction or adverse modification of critical habitat.</P>
                    <P>Under the first prong of the Act's definition of critical habitat, areas within the geographical area occupied by the species at the time it was listed are included in a critical habitat designation if they contain physical or biological features (1) which are essential to the conservation of the species and (2) which may require special management considerations or protection. For these areas, critical habitat designations identify, to the extent known using the best scientific data available, those physical or biological features that are essential to the conservation of the species (such as space, food, cover, and protected habitat).</P>
                    <P>
                        Under the second prong of the Act's definition of critical habitat, we can 
                        <PRTPAGE P="62640"/>
                        designate critical habitat in areas outside the geographical area occupied by the species at the time it is listed, upon a determination that such areas are essential for the conservation of the species. As discussed above, the court in 
                        <E T="03">CBD</E>
                         v. 
                        <E T="03">Haaland</E>
                         vacated the 2019 regulations which modified the criteria for designating critical habitat, including designating critical habitat in areas outside the geographical area occupied by the species. Therefore, the regulations that now govern designations of critical habitat, are those regulations that published on February 11, 2016 (81 FR 7438).
                    </P>
                    <P>
                        Section 4 of the Act requires that we designate critical habitat on the basis of the best scientific data available. Further, our Policy on Information Standards Under the Endangered Species Act (published in the 
                        <E T="04">Federal Register</E>
                         on July 1, 1994 (59 FR 34271)), the Information Quality Act (section 515 of the Treasury and General Government Appropriations Act for Fiscal Year 2001 (Pub. L. 106-554; H.R. 5658)), and our associated Information Quality Guidelines provide criteria, establish procedures, and provide guidance to ensure that our decisions are based on the best scientific data available. They require our biologists, to the extent consistent with the Act and with the use of the best scientific data available, to use primary and original sources of information as the basis for recommendations to designate critical habitat.
                    </P>
                    <P>When we are determining which areas should be designated as critical habitat, our primary source of information is generally the information from the SSA report and information developed during the listing process for the species. Additional information sources may include any generalized conservation strategy, criteria, or outline that may have been developed for the species; the recovery plan for the species; articles in peer-reviewed journals; conservation plans developed by States and counties; scientific status surveys and studies; biological assessments; other unpublished materials; or experts' opinions or personal knowledge.</P>
                    <P>Habitat is dynamic, and species may move from one area to another over time. We recognize that critical habitat designated at a particular point in time may not include all of the habitat areas that we may later determine are necessary for the recovery of the species. For these reasons, a critical habitat designation does not signal that habitat outside the designated area is unimportant or may not be needed for recovery of the species. Areas that are important to the conservation of the species, both inside and outside the critical habitat designation, will continue to be subject to: (1) Conservation actions implemented under section 7(a)(1) of the Act; (2) regulatory protections afforded by the requirement in section 7(a)(2) of the Act for Federal agencies to ensure their actions are not likely to jeopardize the continued existence of any endangered or threatened species; and (3) the prohibitions found in section 9 of the Act. Federally funded or permitted projects affecting listed species outside their designated critical habitat areas may still result in jeopardy findings in some cases. These protections and conservation tools will continue to contribute to recovery of these species. Similarly, critical habitat designations made on the basis of the best available information at the time of designation will not control the direction and substance of future recovery plans, HCPs, or other species conservation planning efforts if new information available at the time of those planning efforts calls for a different outcome.</P>
                    <HD SOURCE="HD1">Prudency Determination</HD>
                    <P>Section 4(a)(3) of the Act, as amended, and implementing regulations (50 CFR 424.12) require that, to the maximum extent prudent and determinable, the Secretary shall designate critical habitat at the time the species is determined to be an endangered or threatened species. Our regulations (50 CFR 424.12(a)(1)) state that a designation of critical habitat is not prudent when any of the following situations exist:</P>
                    <P>(i) The species is threatened by taking or other human activity, and identification of critical habitat can be expected to increase the degree of such threat to the species; or</P>
                    <P>(ii) Such designation of critical habitat would not be beneficial to the species. In determining whether a designation would not be beneficial, the factors the Services may consider include but are not limited to: Whether the present or threatened destruction, modification, or curtailment of a species' habitat or range is not a threat to the species, or whether any areas meet the definition of “critical habitat.”</P>
                    <P>As discussed earlier in this document, there is currently no imminent threat of collection or vandalism identified under Factor B for this species, and identification and mapping of critical habitat is not expected to initiate any such threat. In our SSAs and proposed listing determinations for the Key ring-necked snake and the rim rock crowned snake, we determined that the present or threatened destruction, modification, or curtailment of habitat or range is a threat to both species. Accordingly, critical habitat is likely to be beneficial for the species. Therefore, because none of the circumstances enumerated in our regulations at 50 CFR 424.12(a)(1) have been met and because the Secretary has not determined that designation of critical habitat would not be prudent based on the best scientific data available, we have determined that the designation of critical habitat is prudent for both the Key ring-necked snake and the rim rock crowned snake.</P>
                    <HD SOURCE="HD1">Critical Habitat Determinability</HD>
                    <P>Having determined that designation is prudent, under section 4(a)(3) of the Act we must find whether critical habitat for the Key ring-necked snake and the rim rock crowned snake is determinable. Our regulations at 50 CFR 424.12(a)(2) state that critical habitat is not determinable when one or both of the following situations exist:</P>
                    <P>(i) Data sufficient to perform required analyses are lacking, or</P>
                    <P>(ii) The biological needs of the species are not sufficiently well known to identify any area that meets the definition of “critical habitat.”</P>
                    <P>When critical habitat is not determinable, the Act allows the Service an additional year to publish a critical habitat designation (16 U.S.C. 1533(b)(6)(C)(ii)).</P>
                    <P>We reviewed the available information pertaining to the biological needs of the species and habitat characteristics where this species is located. This and other information representing the best scientific data available led us to conclude that the designation of critical habitat is determinable for the Key ring-necked snake and the rim rock crowned snake.</P>
                    <HD SOURCE="HD1">Physical or Biological Features</HD>
                    <P>
                        In accordance with section 3(5)(A)(i) of the Act and regulations at 50 CFR 424.12(b), in determining which areas we will designate as critical habitat from within the geographical area occupied by the species at the time of listing, we consider the physical or biological features that are essential to the conservation of the species and which may require special management considerations or protection. The regulations at 50 CFR 424.02 define “physical or biological features” as the features that support the life-history needs of the species, including, but not limited to, water characteristics, soil type, geological features, sites, prey, vegetation, symbiotic species, or other features. A feature may be a single habitat characteristic or a more complex 
                        <PRTPAGE P="62641"/>
                        combination of habitat characteristics. Features may include habitat characteristics that support ephemeral or dynamic habitat conditions. Features may also be expressed in terms relating to principles of conservation biology, such as patch size, distribution distances, and connectivity. For example, physical features essential to the conservation of the species might include gravel of a particular size required for spawning, alkaline soil for seed germination, protective cover for migration, or susceptibility to flooding or fire that maintains necessary early-successional habitat characteristics. Biological features might include prey species, forage grasses, specific kinds or ages of trees for roosting or nesting, symbiotic fungi, or absence of a particular level of nonnative species consistent with conservation needs of the listed species. The features may also be combinations of habitat characteristics and may encompass the relationship between characteristics or the necessary amount of a characteristic essential to support the life history of the species.
                    </P>
                    <P>In considering whether features are essential to the conservation of the species, we may consider an appropriate quality, quantity, and spatial and temporal arrangement of habitat characteristics in the context of the life-history needs, condition, and status of the species. These characteristics include, but are not limited to, space for individual and population growth and for normal behavior; food, water, air, light, minerals, or other nutritional or physiological requirements; cover or shelter; sites for breeding, reproduction, or rearing (or development) of offspring; and habitats that are protected from disturbance.</P>
                    <HD SOURCE="HD2">Space for Individual and Population Growth and for Normal Behavior</HD>
                    <P>The Key ring-necked snake and the rim rock crowned snake are endemic to, and occur exclusively within, pine rocklands and rockland hammock habitat; the Key ring-necked snake occurs only in the lower Florida Keys, and the rim rock crowned snake occurs in Miami-Dade County and throughout the Florida Keys. Pine rocklands are a fire-adapted/maintained ecosystem characterized by an open canopy (sparsely spaced pine trees) and understory (grasses and forbs/herbs) and a limestone substrate (often exposed) with sparse soils on top. This combination of ecosystem characteristics (open canopy and limestone substrate) occurs only in the pine rocklands habitat of south Florida.</P>
                    <P>
                        Pine rocklands habitat that supports the rim rock crowned snake is characterized by an open canopy of south Florida slash pine. Subcanopy development is rare in well-maintained pine rocklands with only occasional hardwoods such as wild tamarind (
                        <E T="03">Lysiloma bahamensis</E>
                        ) and live oak (
                        <E T="03">Quercus virginiana</E>
                        ). The shrub/understory layer is also characteristically open, although the height and density of the shrub layer varies based on fire frequency, with understory plants growing taller and denser as the time between fires increases.
                    </P>
                    <P>While the amount of pine rocklands and/or rockland hammock habitat necessary to support Key ring-necked snake and rim rock crowned snake individual and population growth and normal behavior is unknown, preservation of these features is essential for the species.</P>
                    <HD SOURCE="HD2">Food, Water, Air, Light, Minerals, or Other Nutritional or Physiological Requirements</HD>
                    <P>
                        The Key ring-necked snake diet is assumed to be similar to other 
                        <E T="03">Diadophis</E>
                         species (for example, the southern ring-necked snake), which prey upon small insects, snakes, lizards, slugs, amphibians, and earthworms (Ernst and Ernst 2003, p. 96; FWC 2013, p. 2). The rim rock crowned snake diet is assumed to be similar to other 
                        <E T="03">Tantilla</E>
                         species (for example, the southeastern crowned snake), which prey upon centipedes, insects, and other small invertebrates such as tenebrionid beetle larvae, earthworms, snails, centipedes, spiders, cutworms, wireworms, and termites and their larvae (Ernst and Ernst 2003, pp. 353-355). The prey-related requirements (abundance, diversity, range, etc.) for a population of either species to maintain viability is unknown.
                    </P>
                    <P>Water is essential for survival of the Key ring-necked snake and rim rock crowned snake. We have no specific information on the amount of water they require; however, the Key ring-necked snake and species of crowned snake similar to the rim rock crowned snake appear to be restricted to areas near permanent freshwater sources that often occur as small holes in the limestone (Lazell 1989, pp. 134, 136). Small amounts of water can be found in depressions and holes in the limestone substrate of pine rocklands and rockland hammock habitat, which fill from rain or overnight dew fall. The extensive network of holes, tunnels, and cavities in the limestone substrate most likely assists in creating more permanent water sources. During time of drought, these sources may become scarce and the Key ring-necked snake and the rim rock crowned snake may need to seek out other fresh water sources. Consequently, it is important for the Key ring-necked snake and the rim rock crowned snake to have multiple freshwater sources in case one becomes depleted, contaminated, or unavailable. If all local water sources within a snake's home range become dry, the snake may need to expend more energy and time in search of new water sources (Zug et al. 2001, p. 208).</P>
                    <HD SOURCE="HD2">Cover or Shelter</HD>
                    <P>Key ring-necked snakes and rim rock crowned snakes require refugia to escape and hide from predators and regulate body temperature. Currently, there is no specific information on the exact requirement for suitable refugia. The Key ring-necked snake and the rim rock crowned snake are mostly fossorial species that likely inhabit holes and crevices in the limestone, piles of rock rubble, and pockets of organic matter accumulating in solution holes and shallow depressions in the oolitic limestone (Enge et al. 2003, pp. 27-28). Snakes are ectothermic organisms which require an external heat source to warm their bodies in order to increase body function and productivity. Snakes can also become too hot, leading to desiccation. Therefore, a warm, moist microhabitat, typically subterranean or shielded from the sun, is likely preferred refugia to escape from predators and to properly maintain suitable internal temperature and moisture levels.</P>
                    <HD SOURCE="HD2">Sites for Breeding, Reproduction, or Rearing (or Development) of Offspring</HD>
                    <P>Life-history characteristics of the Key ring-necked snake are thought to be similar to the southern ring-necked snake. In general, mating of ring-necked snakes can occur in the spring or fall, delayed fertilization is possible, and females lay 1 to 10 eggs (1 clutch per year) in covered, moist locations in June or early July (Ernst and Ernst 2003, p. 95). Juveniles are thought to hatch in August and September. For the rim rock crowned snake, life-history characteristics are thought to be similar to the southeastern crowned snake. In general, females may lay up to three eggs in a clutch and may be able to produce two clutches annually (Ernst and Ernst 2003, pp. 353-355).</P>
                    <P>
                        Based on their small size and limited range, eggs, juveniles, and adults likely are found in the same habitat.
                        <PRTPAGE P="62642"/>
                    </P>
                    <HD SOURCE="HD2">Habitats That Are Protected From Disturbance or Are Representative of the Historic Geographical and Ecological Distributions of a Species</HD>
                    <P>Pine rocklands habitat is currently listed as critically imperiled globally (FNAI 2010, p. 3). Urban development and agriculture has greatly reduced the extent of pine rocklands in eastern Miami-Dade County and the Florida Keys. Within this range, the quality of remaining pine rocklands has declined because they are isolated and confined by surrounding urban development, which restricts the use of prescribed fire that is the principal management tool. Prescribed fire must be periodically introduced to sustain a proper community structure. In general, pine rocklands depend on a fire regime composed of a surface fire of low or mixed intensity, and a 5-7 year fire return interval.</P>
                    <P>In the absence of fire, pine rocklands are invaded by many of the species found in hardwood hammocks, they lose their herbaceous flora, and they move along a successional trajectory toward hammock (Service 1999, p. 3-173). These rockland hammocks are generally present where pine rocklands were not burned for a long period of time, creating more pine rocklands fragmentation. Rockland hammock consists of a more closed canopy containing more hardwood shrubs and trees due to a rare or infrequent fire regime. Rockland hammock is a hardwood forest that represents an advanced successional stage of pine rocklands that results from the absence of fire.</P>
                    <P>This fragmentation of pine rocklands and rockland hammock in eastern Miami-Dade County and the Florida Keys increases the risk of invasion by exotic vegetation along the interface with disturbed or developed areas, further altering, degrading, or destroying suitable habitat for the Key ring-necked snake and rim rock crowned snake.</P>
                    <P>Because the Key ring-necked snake and the rim rock crowned snake have been documented in both habitat types, it is not clear if one or the other is more suitable for either species. Populations of the Key ring-necked snake and the rim rock crowned snake are supported by the existence of suitable available habitat across their ranges. Therefore, a strong correlation to habitat availability and populations of these snakes can be assumed, but not at a level of certainty in which the presence of rockland hammock or pine rockland habitat can be used as a surrogate for presence. We do not know how much suitable habitat and habitat connectivity is required for populations of either the Key ring-necked snake or the rim rock crowned snake to maintain viability. That said, the most influential need at a population level for both species is available suitable habitat. There may be distinct, non-interbreeding populations at each island or isolated parcel, or there may be some rare dispersal between some parcels or from rafting between some islands providing at least a low level of connectivity between individual populations. Because the Key ring-necked snake appears to be isolated to the lower Florida Keys and the rim rock crowned snake appears restricted to the Florida Keys and eastern Miami-Dade County, the relatively small, patchily distributed islands or parcels can each support only a small number of individuals or separate populations. The distribution and quantity of available suitable habitat across the range necessary to support populations of either the Key ring-necked snake or the rim rock crowned snake are unknown.</P>
                    <HD SOURCE="HD2">Summary of Essential Physical or Biological Features</HD>
                    <P>
                        We derive the specific physical or biological features essential to the conservation of the Key ring-necked snake and the rim rock crowned snake from studies of the species' habitat, ecology, and life history as described above. Additional information can be found in the SSA reports (Service 2021a, entire; Service 2021b, entire), both of which are available on 
                        <E T="03">https://www.regulations.gov</E>
                         under Docket No. FWS-R4-ES-2022-0022. We have determined that the following physical or biological features are essential to the conservation of the Key ring-necked snake and the rim rock crowned snake:
                    </P>
                    <P>(1) Pine rocklands habitat that contains:</P>
                    <P>(a) Refugia consisting of a limestone rock substrate with holes, crevices, and shallow depressions; piles of rock rubble; and pockets of organic matter accumulating in solution holes;</P>
                    <P>(b) Suitable prey;</P>
                    <P>(c) Warm, moist microhabitats to maintain homeostasis; and</P>
                    <P>(d) A natural or prescribed fire regime at 5- to 7-year intervals that maintains the pine rocklands habitat and associated plant community.</P>
                    <P>(2) Rockland hammock habitat that contains:</P>
                    <P>(a) Refugia consisting of a limestone rock substrate with holes, crevices, and shallow depressions; piles of rock rubble; and pockets of organic matter accumulating in solution holes;</P>
                    <P>(b) Suitable prey;</P>
                    <P>(c) Warm, moist microhabitats to maintain homeostasis; and</P>
                    <P>(d) Little or no fire maintenance.</P>
                    <HD SOURCE="HD1">Special Management Considerations or Protection</HD>
                    <P>When designating critical habitat, we assess whether the specific areas within the geographical area occupied by the species at the time of listing contain features that are essential to the conservation of the species and which may require special management considerations or protection. The features essential to the conservation of the Key ring-necked snake and the rim rock crowned snake may require special management considerations or protection to reduce threats posed by: Land use conversion, primarily due to urban, agricultural, and recreational use; encroachment of invasive species; activities that cause surface or subsurface disturbance; fire suppression and low fire frequencies (pine rocklands); destructive fires in rockland hammock; random effects of drought or floods; and fragmentation from new roads or development. Management activities that could ameliorate these threats include (but are not limited to): Maintaining suitable pine rocklands and rockland hammock habitats in areas with existing populations through prescribed fire, mechanical treatments (that is, brush clearing, herbicide treatment), and invasive species control; restoring historical habitat and establishing new populations in the lower, middle, and upper Florida Keys or Miami-Dade County (rim rock crowned snake only); controlling exotic and invasive plant management plan; prohibiting management activities that could cause surface or subsurface disturbance unless carried out in accordance with a habitat management plan developed by a Federal, State, or County entity that identifies those areas where pine rocklands habitat is succeeding to hardwood-dominant habitat based on fire suppression, or to halophilic vegetation due to sea level rise; establishing and enhancing connectivity between currently occupied populations and adjacent suitable habitat; facilitating habitat restoration through the use of prescribed fire every 5 to 7 years for pine rocklands habitat; and implementing habitat management plans based on site-specific conditions for rockland hammock habitat.</P>
                    <HD SOURCE="HD1">Criteria Used To Identify Critical Habitat</HD>
                    <P>
                        As required by section 4(b)(2) of the Act, we use the best scientific data available to designate critical habitat. In accordance with the Act and our implementing regulations at 50 CFR 
                        <PRTPAGE P="62643"/>
                        424.12(b), we review available information pertaining to the habitat requirements of the species and identify specific areas within the geographical area occupied by the species at the time of listing and any specific areas outside the geographical area occupied by the species to be considered for designation as critical habitat.
                    </P>
                    <P>For the Key ring-necked snake, we are not currently proposing to designate any areas outside the geographical area occupied by the species because we have not identified any unoccupied areas that are essential for the conservation of the species.</P>
                    <P>For the rim rock crowned snake, we are proposing to designate critical habitat in areas outside the geographical area occupied by the species at the time of listing because we have determined that those areas are essential for the conservation of the species. We have determined that the unoccupied areas contain one or more of the physical or biological features essential to the species and are essential because by the year 2040, all suitable habitat for rim rock crowned snake in the lower Florida Keys and up to half of suitable habitat in the upper Florida Keys will be affected by sea level rise and saltwater intrusion. Therefore, we identified suitable habitat in Miami-Dade County that is essential to provide for species redundancy into the foreseeable future.</P>
                    <P>Sources of data for these two species and their habitat requirements include multiple databases maintained by museums, universities, and State agencies in Florida; papers by researchers involved in wildlife biology and conservation activities; peer-reviewed articles on these species and/or their relatives; State agency reports; and numerous survey reports for projects throughout the species' ranges.</P>
                    <P>For areas within the geographic area occupied by the Key ring-necked snake and the rim rock crowned snake at the time of listing, we delineated critical habitat unit boundaries using the following criteria:</P>
                    <P>(1) We determined occupied areas for each species by reviewing the best available scientific and commercial data on occurrence records. The range of survey records was selected due to scarcity of records throughout the range of each species. As discussed in Background, both species are extremely cryptic and spend most of their time underground. Because of their cryptic nature, we determined that if suitable habitat containing the physical or biological features was still present in an area where a Key ring-necked snake or a rim rock crowned snake was previously detected, that there was a high likelihood that the species would still be present even if it had not been recently detected. Therefore, based on the best available information, in order to determine occupied areas for the species, we used occurrence points ranging from 2010 to present for the Key ring-necked snake and 1996 to present for the rim rock crowned snake.</P>
                    <P>(2) We selected all suitable habitat (habitat that contained the physical or biological features) within a 1-mi (1.6-km) radius of an occurrence record. A 1-mi radius was based on the maximum recapture distance of 1 mi (1.6 km) recorded during a demographic study of the ringneck snake in Kansas (Fitch 1975, p. 25).</P>
                    <P>(3) We selected additional contiguous suitable habitat that contained all the physical or biological features (PBFs) that extended beyond the 1-mi (1.6-km) radius to include dispersal areas for the two species.</P>
                    <P>(4) We then constrained the boundary of a critical habitat unit based on potential effects of physical barriers (for example, roads wider than 2 lanes or water) that cause habitat fragmentation and prevent connectivity and dispersal opportunities within units, as we consider that individuals of either species would be unable or unlikely to pass such barriers.</P>
                    <P>We conclude that the occupied areas we are proposing for critical habitat provide for the conservation of both species, because they are suitable habitat that contain all the physical or biological features for all extant populations and facilitate connectivity and dispersal opportunities within units.</P>
                    <P>As previously stated, we also identified unoccupied areas for the rim rock crowned snake to be essential for its conservation. For areas outside the geographic area occupied by the species at the time of proposed listing for the rim rock crowned snake, we first looked for areas historically occupied by the rim rock crowned snake. However, many areas where rim rock crowned snakes were historically observed have been converted due to urban and agricultural development and are no longer suitable for the species. Further, populations in the Florida Keys are vulnerable to sea level rise now and will become more vulnerable in the foreseeable future. Therefore, we have determined that in order to recover the species, additional populations will need to be established in high-quality pine rockland or rockland hammock habitat that is actively protected and managed. We searched for other areas within the historical geographic area occupied by the species that contain high-quality pine rocklands or rockland hammock habitat and evaluated each site for its potential conservation based on quality of habitat, vulnerability to sea level rise, and existing protections and management of the habitat and sites. Based on these criteria, we identified two areas that contain appropriate habitat for the species (all physical or biological features essential for the conservation of the species are present in these areas) but for which we could not verify whether the areas were occupied. Accordingly, we find these areas unoccupied. The two unoccupied areas are located within the historical range as well as within Miami-Dade County far enough inland such that effects from projected sea level rise would have minimal impact to habitat. Therefore, we include these two areas as proposed critical habitat for the purpose of reestablishing populations, which are essential for the conservation of the species since populations are likely to be lost in the lower and upper Florida Keys due to projected sea level rise. Furthermore, the addition of two reestablished populations in Miami-Dade County would increase the redundancy of the species and reduce the chance that a catastrophic event would eliminate all populations in this area.</P>
                    <P>We conclude that these areas are essential for the conservation of the species because they provide areas for reestablishing populations, and they are high-quality habitat that contain all the physical or biological features for the rim rock crowned snake.</P>
                    <P>
                        When determining proposed critical habitat boundaries, we made every effort to avoid including developed areas such as lands covered by buildings, pavement, and other structures because such lands lack physical or biological features necessary for the Key ring-necked snake and the rim rock crowned snake. The scale of the maps we prepared under the parameters for publication within the Code of Federal Regulations may not reflect the exclusion of such developed lands. Any such lands inadvertently left inside critical habitat boundaries shown on the maps of this proposed rule have been excluded by text in the proposed rule and are not proposed for designation as critical habitat. Therefore, if the critical habitat is finalized as proposed, a Federal action involving these lands would not trigger section 7 consultation with respect to critical habitat and the requirement of no adverse modification unless the specific action would affect the physical or biological features in the adjacent critical habitat.
                        <PRTPAGE P="62644"/>
                    </P>
                    <P>For the Key ring-necked snake, we propose to designate as critical habitat lands that we have determined are occupied at the time of listing (that is, currently occupied) and that contain all of the physical or biological features that are essential to support life-history processes of the subspecies. Our proposed critical habitat designation includes all areas currently occupied by the species. For the rim rock crowned snake only, as discussed above, we have also identified, and propose for designation as critical habitat, unoccupied areas that are essential for the conservation of the species.</P>
                    <P>All units contain all of the identified physical or biological features and support multiple life-history processes, including all unoccupied units for the rim rock crowned snake.</P>
                    <P>
                        The proposed critical habitat designation is defined by the map or maps, as modified by any accompanying regulatory text, presented at the end of this document under Proposed Regulation Promulgation. We include more detailed information on the boundaries of the critical habitat designation in the preamble of this document. We will make the coordinates or plot points or both on which each map is based available to the public on 
                        <E T="03">https://www.regulations.gov</E>
                         at Docket No. FWS-R4-ES-2022-0022 and on our internet site (
                        <E T="03">https://www.fws.gov/office/florida-ecological-services</E>
                        ).
                    </P>
                    <HD SOURCE="HD1">Proposed Critical Habitat Designation for the Key Ring-Necked Snake</HD>
                    <P>We are proposing four units as critical habitat for the Key ring-necked snake. The critical habitat areas we describe below constitute our current best assessment of areas that meet the definition of critical habitat for the Key ring-necked snake. The four areas we propose as critical habitat are: (1) Big Pine Key, (2) Middle Torch Key, (3) Cudjoe Key, and (4) Stock Island. Table 11 shows the proposed critical habitat units, the land ownership, and the approximate area of each unit. All proposed units for the Key ring-necked snake are occupied.</P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s75,r100,15,10">
                        <TTITLE>Table 11—Proposed Critical Habitat Units for the Key Ring-Necked Snake</TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">Land ownership by type</CHED>
                            <CHED H="1">
                                Size of unit
                                <LI>in acres</LI>
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">1. Big Pine Key</ENT>
                            <ENT>Federal</ENT>
                            <ENT>1,174 (475)</ENT>
                            <ENT>Yes</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>State</ENT>
                            <ENT>366 (148)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Local/County</ENT>
                            <ENT>62 (25)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Private</ENT>
                            <ENT>77 (31)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Unknown/Undefined</ENT>
                            <ENT>54 (22)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2. Middle Torch Key</ENT>
                            <ENT>Federal</ENT>
                            <ENT>59 (24)</ENT>
                            <ENT>Yes</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>State</ENT>
                            <ENT>211 (85)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Private</ENT>
                            <ENT>57 (23)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Unknown/Undefined</ENT>
                            <ENT>29 (12)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3. Cudjoe Key</ENT>
                            <ENT>Federal</ENT>
                            <ENT>332 (134)</ENT>
                            <ENT>Yes</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>State</ENT>
                            <ENT>76 (31)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Local/County</ENT>
                            <ENT>45 (18)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Private</ENT>
                            <ENT>28 (11)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Unknown/Undefined</ENT>
                            <ENT>26 (10)</ENT>
                        </ROW>
                        <ROW RUL="n,n,s,n">
                            <ENT I="01">4. Stock Island</ENT>
                            <ENT>Local/County</ENT>
                            <ENT>8 (3)</ENT>
                            <ENT>Yes</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>2,604 (1,054)</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding.
                        </TNOTE>
                    </GPOTABLE>
                    <P>We present brief descriptions of all units and reasons why they meet the definition of critical habitat for the Key ring-necked snake, below.</P>
                    <HD SOURCE="HD2">Unit 1: Big Pine Key</HD>
                    <P>Unit 1 encompasses 1,734 ac (702 ha) within Monroe County in the lower Florida Keys and contains all of the essential physical or biological features for the subspecies. This unit is occupied. The northern portion of the unit is located in a primarily rural area. The habitat associated with the central and southern portions of the unit is located in rural areas but is sparsely fragmented by two-lane roads and residential and commercial development. The majority of habitat in this unit is federally owned by the Service, within the National Key Deer Wildlife Refuge, while other large tracts are owned by the National Park Service and the State of Florida. Smaller tracts of habitat are owned by Monroe County, local government, and private entities. The physical or biological features in this unit may require special management to protect them from development and fire suppression (in pine rocklands). This unit is also vulnerable to effects from sea level rise, saltwater intrusion, and storms.</P>
                    <HD SOURCE="HD2">Unit 2: Middle Torch Key</HD>
                    <P>Unit 2 encompasses approximately 356 ac (144 ha) within Monroe County in the lower Florida Keys and contains all of the essential physical or biological features for the subspecies. This unit is occupied. The State owns a significant portion of the habitat in this unit and a smaller portion is owned by both Federal and private entities. The State of Florida and the Service own and manage the Florida Keys Wildlife and Environmental Area and the National Key Deer Wildlife Refuge, respectively. The habitat is only slightly fragmented in the center and at the northern- and southern-most locations. The slight habitat fragmentation is due to a small amount of residential development and a two-lane road. The physical or biological features in this unit may require special management to protect them from development. This unit is also vulnerable to effects from sea level rise, saltwater intrusion, and storms.</P>
                    <HD SOURCE="HD2">Unit 3: Cudjoe Key</HD>
                    <P>
                        Unit 3 encompasses five subunits that total approximately 507 ac (205 ha) within Monroe County in the lower Florida Keys and contains all of the essential physical or biological features for the subspecies. This unit is occupied. In the two southern-most subunits, the habitat is fragmented by two- and four-lane roads and residential and commercial development. The habitat associated with the other three 
                        <PRTPAGE P="62645"/>
                        subunits is located in rural areas, only sparsely fragmented by two-lane roads and residential and commercial development. The majority of the habitat in this unit is owned and managed by the Service and associated with the National Key Deer Wildlife Refuge. The physical or biological features in this unit may require special management to protect them from development and fire suppression (in pine rocklands). This unit is also vulnerable to effects from sea level rise, saltwater intrusion, and storms.
                    </P>
                    <HD SOURCE="HD2">Unit 4: Stock Island</HD>
                    <P>Unit 4 encompasses approximately 8 ac (3 ha) within Monroe County in the lower Florida Keys and contains all of the essential physical or biological features for the subspecies. This unit is occupied. The habitat in this unit is surrounded and/or fragmented by residential and commercial development. The vast majority of habitat is owned by the City of Key West. The physical or biological features in this unit may require special management to protect them from development. This unit is also vulnerable to effects from sea level rise, saltwater intrusion, and storms.</P>
                    <HD SOURCE="HD1">Proposed Critical Habitat Designation for the Rim Rock Crowned Snake</HD>
                    <P>We are proposing 11 units as critical habitat for the rim rock crowned snake. The critical habitat areas we describe below constitute our current best assessment of areas that meet the definition of critical habitat for the rim rock crowned snake. The 11 areas we propose as critical habitat are: (1) Richmond Pine Rocklands, (2) Deering Estate Complex/Bill Sadowski Park, (3) Barnacle, (4) Camp Owaissa Bauer, (5) Navy Wells, (6) North Key Largo, (7) Key Largo, (8) Tavernier, (9) Vaca Key, (10) Big Pine Key, (11) Key West. Table 12 shows the proposed critical habitat units, the approximate area of each unit, the ownership of each unit, and whether the unit is occupied.</P>
                    <GPOTABLE COLS="4" OPTS="L2,nj,i1" CDEF="s100,r75,15,10">
                        <TTITLE>Table 12—Proposed Critical Habitat Units for the Rim Rock Crowned Snake</TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">Land ownership by type</CHED>
                            <CHED H="1">
                                Size of unit
                                <LI>in acres</LI>
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">1. Richmond Pine Rocklands</ENT>
                            <ENT>
                                Federal
                                <LI>Local/County</LI>
                                <LI>Private</LI>
                            </ENT>
                            <ENT>
                                160 (65)
                                <LI>513 (208)</LI>
                                <LI>144 (58)</LI>
                            </ENT>
                            <ENT>Yes</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2. Deering Estate Complex/Bill Sadowski Park</ENT>
                            <ENT>
                                State
                                <LI>Local/County</LI>
                                <LI>Private</LI>
                            </ENT>
                            <ENT>
                                241 (98)
                                <LI>19 (8)</LI>
                                <LI>31 (13)</LI>
                            </ENT>
                            <ENT>Yes</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3. Barnacle</ENT>
                            <ENT>
                                State
                                <LI>Private</LI>
                                <LI>Unknown/Undefined</LI>
                            </ENT>
                            <ENT>
                                3 (1)
                                <LI>1 (0.4)</LI>
                                <LI>1 (0.4)</LI>
                            </ENT>
                            <ENT>Yes</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4. Camp Owaissa Bauer</ENT>
                            <ENT>
                                State
                                <LI>Local/County</LI>
                                <LI>Private</LI>
                            </ENT>
                            <ENT>
                                9 (4)
                                <LI>83 (34)</LI>
                                <LI>4 (2)</LI>
                            </ENT>
                            <ENT>No</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">5. Navy Wells</ENT>
                            <ENT>
                                State
                                <LI>Local/County</LI>
                                <LI>Private</LI>
                            </ENT>
                            <ENT>
                                85 (34)
                                <LI>240 (97)</LI>
                                <LI>0.05 (0.02)</LI>
                            </ENT>
                            <ENT>No</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6. North Key Largo</ENT>
                            <ENT>
                                Federal
                                <LI>State</LI>
                                <LI>Local/County</LI>
                                <LI>Private</LI>
                            </ENT>
                            <ENT>
                                601 (243)
                                <LI>1,484 (601)</LI>
                                <LI>24 (9)</LI>
                                <LI>53 (21)</LI>
                            </ENT>
                            <ENT>Yes</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">7. Key Largo</ENT>
                            <ENT>
                                State
                                <LI>Local/County</LI>
                                <LI>Private</LI>
                            </ENT>
                            <ENT>
                                151 (61)
                                <LI>56 (23)</LI>
                                <LI>91 (37)</LI>
                            </ENT>
                            <ENT>Yes</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8. Tavernier</ENT>
                            <ENT>
                                State
                                <LI>Local/County</LI>
                                <LI>Private</LI>
                            </ENT>
                            <ENT>
                                98 (40)
                                <LI>30 (12)</LI>
                                <LI>54 (22)</LI>
                            </ENT>
                            <ENT>Yes</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9. Vaca Key</ENT>
                            <ENT>
                                County/Local
                                <LI>Private</LI>
                            </ENT>
                            <ENT>
                                1 (0.4)
                                <LI>58 (23)</LI>
                            </ENT>
                            <ENT>Yes</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10. Big Pine Key</ENT>
                            <ENT>
                                Federal
                                <LI>State</LI>
                                <LI>Local/County</LI>
                                <LI>Private</LI>
                            </ENT>
                            <ENT>
                                1,200 (486)
                                <LI>380 (154)</LI>
                                <LI>71 (29)</LI>
                                <LI>77 (31)</LI>
                            </ENT>
                            <ENT>Yes</ENT>
                        </ROW>
                        <ROW RUL="n,n,s,n">
                            <ENT I="01">11. Key West</ENT>
                            <ENT>
                                Local/County
                                <LI>Private</LI>
                            </ENT>
                            <ENT>
                                5 (2)
                                <LI>3 (1)</LI>
                            </ENT>
                            <ENT>Yes</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>5,972 (2,418)</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note</E>
                            : Area sizes may not sum due to rounding.
                        </TNOTE>
                    </GPOTABLE>
                    <P>We present brief descriptions of all units and reasons why they meet the definition of critical habitat for the rim rock crowned snake below.</P>
                    <HD SOURCE="HD2">Unit 1: Richmond Pine Rocklands</HD>
                    <P>
                        Unit 1 consists of 817 ac (331 ha) and contains all of the essential physical or biological features for the species. This unit is occupied. Located within Miami-Dade County, this unit is fragmented by commercial and residential development, Federal and local government installations, and the Zoo Miami facility. Unit 1 is completely surrounded by a dense urban matrix typical of the Miami metropolitan area. Habitat areas associated with Unit 1 have experienced a significant amount 
                        <PRTPAGE P="62646"/>
                        of sustained and recent urban development contributing to habitat loss but also have been the focus of land acquisition for conservation. A recent private land development project within the boundaries of the proposed unit has contributed to fragmentation and loss of suitable habitat. Several large tracts of suitable habitat are owned by Miami-Dade County, but only a fraction are managed and protected in perpetuity. The remainder are protected as Natural Forest Communities (NFCs). This program provides only temporary protection, habitat management is not required, and a portion of the parcel may be developed. Landowners include Federal Government agencies (U.S. Coast Guard, U.S. Army Corps of Engineers, and U.S. Office of Public Buildings), Miami-Dade County, University of Miami (private), and other private entities. Approximately 80 ac (32 ha) of the U.S. Coast Guard property is proposed for designation as critical habitat in this unit. The Coral Reef Commons HCP has been finalized to protect and manage 53 ac (21 ha) of pine rocklands (north end of Unit 1) within the project footprint, and an additional 57 ac (23 ha) to the south of the project footprint, but still within Unit 1. Thus, we are considering these two parcels in this unit for exclusion under the Coral Reef Commons HCP.
                    </P>
                    <P>The physical or biological features in this unit may require special management to protect them from development and fire suppression (in pine rocklands). This unit is also vulnerable to effects from storms.</P>
                    <HD SOURCE="HD2">Unit 2: Deering Estate Complex/Bill Sadowski Park</HD>
                    <P>Unit 2 consists of 291 ac (119 ha) and contains all of the essential physical or biological features for the species. This unit is occupied. Located within Miami-Dade County, this unit is fragmented by residential communities, light commercial development, and canals. The Biscayne Bay borders the majority of Unit 2 to the east, with suburban development surrounding the remaining areas. Habitat areas associated with Unit 2 have experienced a relatively stable environment as most are adjacent to neighborhoods or the Biscayne Bay but also have been the focus of land acquisition for conservation. The majority of lands within this unit are conserved and managed by the County as Bill Sadowski Park and Deering Estate. Landowners include the State of Florida, Miami-Dade County, the Deering Estate Foundation (private), and other private entities. The physical or biological features in this unit may require special management to protect them from development and fire suppression (in pine rocklands). This unit is also vulnerable to effects from storms.</P>
                    <HD SOURCE="HD2">Unit 3: Barnacle</HD>
                    <P>Unit 3 consists of 5 ac (2 ha) and contains all of the essential physical or biological features for the species. This unit is occupied. Located within Miami-Dade County, this unit is surrounded by an established urban matrix on all sides except the Biscayne Bay to the east. The majority of suitable habitat is within the boundaries of the Barnacle Historic State Park, a State of Florida property, and additional habitat is owned by private entities or is of unknown/undefined ownership. The physical or biological features in this unit may require special management to protect them from development and fire suppression (in pine rocklands). This unit is also vulnerable to effects from storms.</P>
                    <HD SOURCE="HD2">Unit 4: Camp Owaissa Bauer</HD>
                    <P>Unit 4 consists of 96 ac (39 ha) and contains all of the essential physical or biological features for the species. Located within Miami-Dade County, agriculture lands and light residential communities surround the unit, and a two-lane road separates the larger north portion from the south portion. The unit is considered unoccupied, as there are no records of rim rock crowned snake observations; however, it contains all physical or biological features, is within the species' historical range, and is located inland, away from projected habitat losses from sea level rise as predicted for the Florida Keys populations. Therefore, Unit 4 would serve as a suitable reestablishment site to increase species redundancy when population losses are expected to occur in the Florida Keys in the future; thus, this area is essential for the conservation of the species. The majority of the unit is owned by Miami-Dade County, and is managed by Miami-Dade County's Environmentally Endangered Lands program. Some small parcels are owned by the State of Florida and private or unknown/undefined entities.</P>
                    <HD SOURCE="HD2">Unit 5: Navy Wells</HD>
                    <P>Unit 5 consists of 325 ac (132 ha) and contains all of the essential physical or biological features for the species. It is located within Miami-Dade County; agriculture lands and light residential development surround the unit. The unit is considered unoccupied, as there are no records of rim rock crowned snake observations; however, it contains all physical or biological features, is within the species' historical range, and is located inland, away from projected habitat losses from sea level rise as predicted for the Florida Keys populations. Therefore, Unit 5 would serve as a suitable reestablishment site to increase species redundancy when population losses are expected to occur in the Florida Keys in the future; thus, this area is essential for the conservation of the species. The majority of the unit is owned by Miami-Dade County, and the State of Florida owns a large tract of land, both of which are managed by Miami-Dade County's Environmentally Endangered Lands program. Some small parcels are owned by private entities.</P>
                    <HD SOURCE="HD2">Unit 6: North Key Largo</HD>
                    <P>Unit 6 consists of 2,162 ac (875 ha) and contains all of the essential physical or biological features for the species. This unit is occupied. It is located within Monroe County and includes the city of Key Largo of the upper Florida Keys islands. This unit is surrounded by the Atlantic Ocean to the east and the Florida Bay to the west. Habitat consists primarily of contiguous habitat owned by several Federal agencies (National Park Service, Naval Air Station, U.S. Coast Guard, and the Service), in which the Service owns the majority as Crocodile Lake National Wildlife Refuge (Refuge). Other Federal land owners have turned over ownership to the Service (Dixon 2020, pers. comm.), but records may not reflect this yet. Parcels previously owned by the other Federal entities are embedded within the Refuge and have been managed as part of the Refuge. The State of Florida owns and manages Dagny Johnson Key Largo Hammock Botanical Park within this unit. Monroe County, local government, and private entities own additional habitat within this unit. The physical or biological features in this unit may require special management to protect them from development. This unit is also vulnerable to effects from sea level rise, saltwater intrusion, and storms.</P>
                    <HD SOURCE="HD2">Unit 7: Key Largo</HD>
                    <P>
                        Unit 7 consists of 298 ac (121 ha) and contains all of the essential physical or biological features for the species. This unit is occupied. Located within Monroe County and part of the city of Key Largo, of the upper Florida Keys islands, the habitat in this unit is surrounded and/or fragmented by suburban and urban development. The majority of habitat consists of habitat owned by private entities and the State of Florida (John Pennekamp Coral Reef State Park). Smaller portions of habitat are owned by Monroe County. Habitat connectivity among occurrences is lacking within the unit; fragmentation is 
                        <PRTPAGE P="62647"/>
                        from residential and light commercial development, as well as canals and two-lane roads. The physical or biological features in this unit may require special management to protect them from development. This unit is also vulnerable to effects from sea level rise, saltwater intrusion, and storms.
                    </P>
                    <HD SOURCE="HD2">Unit 8: Tavernier</HD>
                    <P>Unit 8 consists of 181 ac (73 ha) and contains all of the essential physical or biological features for the species. This unit is occupied. Located within Monroe County and part of the city of Tavernier, within the upper Florida Keys islands, the habitat in this unit is surrounded and/or fragmented by suburban and urban development, canals, and two-lane roads. The State of Florida (Dove Creek Hammock), county/local government, and private entities own land in this unit. The physical or biological features in this unit may require special management to protect them from development. This unit is also vulnerable to effects from sea level rise, saltwater intrusion, and storms.</P>
                    <HD SOURCE="HD2">Unit 9: Vaca Key</HD>
                    <P>Unit 9 consists of 59 ac (24 ha) and contains all of the essential physical or biological features for the species. This unit is occupied. Located within Monroe County and part of the city of Marathon, within the upper Florida Keys, the habitat in this unit is surrounded and/or fragmented by suburban and urban development. The majority of habitat is owned by private entities, including the Florida Keys Land Trust Inc. Additionally, Monroe County owns an important tract that is within dispersal distance of the land trust property. The physical or biological features in this unit may require special management to protect them from development and fire suppression (in pine rocklands). This unit is also vulnerable to effects from sea level rise, saltwater intrusion, and storms.</P>
                    <HD SOURCE="HD2">Unit 10: Big Pine Key</HD>
                    <P>Unit 10 consists of 1,729 ac (700 ha) and contains all of the essential physical or biological features for the species. This unit is occupied. Located within Monroe County within the lower Florida Keys, the central and southern portions of the unit are surrounded and/or fragmented by residential communities, some light commercial development, and two-lane roads. The northern portion of the unit is primarily rural with some two-lane roads and residential communities scattered throughout. The majority of habitat in this unit is federally owned, specifically as National Key Deer Wildlife Refuge. Large tracts are also owned by the National Park Service, other Federal ownership, and the State of Florida. Smaller tracts of habitat are owned by Monroe County, local government, and private entities. The physical or biological features in this unit may require special management to protect them from development and fire suppression (in pine rocklands). This unit is also vulnerable to effects from sea level rise, saltwater intrusion, and storms.</P>
                    <HD SOURCE="HD2">Unit 11: Key West</HD>
                    <P>Unit 11 consists of 9 ac (4 ha) and contains all of the essential physical or biological features for the species. This unit is occupied. It is located within Monroe County and part of the city of Key West, within the lower Florida Keys. Large resorts and hotels are located to the east, and the Key West International Airport is located to the south of this unit. The remaining areas around the unit are undeveloped. Unit 11 is owned by Monroe County, local government, and private entities. The physical or biological features in this unit may require special management to protect them from development and fire suppression (in pine rocklands). This unit is also vulnerable to effects from sea level rise, saltwater intrusion, and storms.</P>
                    <HD SOURCE="HD1">Effects of Critical Habitat Designation</HD>
                    <HD SOURCE="HD2">Section 7 Consultation</HD>
                    <P>Section 7(a)(2) of the Act requires Federal agencies, including the Service, to ensure that any action they fund, authorize, or carry out is not likely to jeopardize the continued existence of any endangered species or threatened species or result in the destruction or adverse modification of designated critical habitat of such species. In addition, section 7(a)(4) of the Act requires Federal agencies to confer with the Service on any agency action which is likely to jeopardize the continued existence of any species proposed to be listed under the Act or result in the destruction or adverse modification of proposed critical habitat.</P>
                    <P>
                        We published a final rule revising the definition of destruction or adverse modification on February 11, 2016 (81 FR 7214) (although we also published a revised definition after that (on August 27, 2019); that 2019 definition was subsequently vacated by the court in 
                        <E T="03">CBD</E>
                         v. 
                        <E T="03">Haaland</E>
                        ). Destruction or adverse modification means a direct or indirect alteration that appreciably diminishes the value of critical habitat for the conservation of a listed species. Such alterations may include, but are not limited to, those that alter the physical or biological features essential to the conservation of a species or that preclude or significantly delay development of such features.
                    </P>
                    <P>If a Federal action may affect a listed species or its critical habitat, the responsible Federal agency (action agency) must enter into consultation with us. Examples of actions that are subject to the section 7 consultation process are actions on State, Tribal, local, or private lands that require a Federal permit (such as a permit from the U.S. Army Corps of Engineers under section 404 of the Clean Water Act or a permit from the Service under section 10 of the Act) or that involve some other Federal action (such as funding from the Federal Highway Administration, Federal Aviation Administration, or the Federal Emergency Management Agency). Federal actions not affecting listed species or critical habitat—and actions on State, Tribal, local, or private lands that are not federally funded, authorized, or carried out by a Federal agency—do not require section 7 consultation.</P>
                    <P>Compliance with the requirements of section 7(a)(2) is documented through our issuance of:</P>
                    <P>(1) A concurrence letter for Federal actions that may affect, but are not likely to adversely affect, listed species or critical habitat; or</P>
                    <P>(2) A biological opinion for Federal actions that may affect, and are likely to adversely affect, listed species or critical habitat.</P>
                    <P>When we issue a biological opinion concluding that a project is likely to jeopardize the continued existence of a listed species and/or destroy or adversely modify critical habitat, we provide reasonable and prudent alternatives to the project, if any are identifiable, that would avoid the likelihood of jeopardy and/or destruction or adverse modification of critical habitat. We define “reasonable and prudent alternatives” (at 50 CFR 402.02) as alternative actions identified during consultation that:</P>
                    <P>(1) Can be implemented in a manner consistent with the intended purpose of the action,</P>
                    <P>(2) Can be implemented consistent with the scope of the Federal agency's legal authority and jurisdiction,</P>
                    <P>(3) Are economically and technologically feasible, and</P>
                    <P>
                        (4) Would, in the Service Director's opinion, avoid the likelihood of jeopardizing the continued existence of the listed species and/or avoid the likelihood of destroying or adversely modifying critical habitat.
                        <PRTPAGE P="62648"/>
                    </P>
                    <P>Reasonable and prudent alternatives can vary from slight project modifications to extensive redesign or relocation of the project. Costs associated with implementing a reasonable and prudent alternative are similarly variable.</P>
                    <P>Regulations at 50 CFR 402.16 set forth requirements for Federal agencies to reinitiate formal consultation on previously reviewed actions. These requirements apply when the Federal agency has retained discretionary involvement or control over the action (or the agency's discretionary involvement or control is authorized by law) and, subsequent to the previous consultation: (a) if the amount or extent of taking specified in the incidental take statement is exceeded; (b) if new information reveals effects of the action that may affect listed species or critical habitat in a manner or to an extent not previously considered; (c) if the identified action is subsequently modified in a manner that causes an effect to the listed species or critical habitat that was not considered in the biological opinion; or (d) if a new species is listed or critical habitat designated that may be affected by the identified action.</P>
                    <P>In such situations, Federal agencies sometimes may need to request reinitiation of consultation with us, but the regulations also specify some exceptions to the requirement to reinitiate consultation on specific land management plans after subsequently listing a new species or designating new critical habitat. See the regulations for a description of those exceptions.</P>
                    <HD SOURCE="HD2">Application of the “Destruction or Adverse Modification” Standard</HD>
                    <P>The key factor related to the destruction or adverse modification determination is whether implementation of the proposed Federal action directly or indirectly alters the designated critical habitat in a way that appreciably diminishes the value of the critical habitat for the conservation of the listed species. As discussed above, the role of critical habitat is to support physical or biological features essential to the conservation of a listed species and provide for the conservation of the species.</P>
                    <P>Section 4(b)(8) of the Act requires us to briefly evaluate and describe, in any proposed or final regulation that designates critical habitat, activities involving a Federal action that may violate section 7(a)(2) of the Act by destroying or adversely modifying such habitat, or that may be affected by such designation.</P>
                    <P>Activities that we may, during a consultation under section 7(a)(2) of the Act, consider likely to destroy or adversely modify critical habitat include, but are not limited to: Construction, land development, and agriculture that require clearing, digging, and/or otherwise altering suitable habitat. Clearing of vegetation and digging could remove vegetation cover, leaf litter, woody debris, and limestone substrate, which would contribute to losses of shelter, ability to thermo-regulate, prey, sites for laying and incubating eggs, and conditions for a warm, moist microhabitat. Additionally, development, agriculture, and construction projects can further fragment tracts of suitable habitat, inhibiting dispersal by the Key ring-necked snake and the rim rock crowned snake between remaining areas of suitable habitat, and cause habitat degradation by making it more difficult to conduct prescribed fire in pine rocklands habitat. Furthermore, in areas protected and managed for conservation, prescribed fire and other management activities (mechanical clearing, out-planting, etc.) have the potential to harm individuals; however, the long-term benefits typically far outweigh the potential harm.</P>
                    <HD SOURCE="HD1">Exemptions</HD>
                    <HD SOURCE="HD2">Application of Section 4(a)(3) of the Act</HD>
                    <P>Section 4(a)(3)(B)(i) of the Act (16 U.S.C. 1533(a)(3)(B)(i)) provides that the Secretary shall not designate as critical habitat any lands or other geographical areas owned or controlled by the Department of Defense (DoD), or designated for its use, that are subject to an integrated natural resources management plan (INRMP) prepared under section 101 of the Sikes Act Improvement Act of 1997 (16 U.S.C. 670a) (Sikes Act), if the Secretary determines in writing that such plan provides a benefit to the species for which critical habitat is proposed for designation. No DoD lands with a completed INRMP are within the proposed critical habitat designation for either the Key ring-necked snake or the rim rock crowned snake.</P>
                    <HD SOURCE="HD1">Consideration of Impacts Under Section 4(b)(2) of the Act</HD>
                    <P>Section 4(b)(2) of the Act states that the Secretary shall designate and make revisions to critical habitat on the basis of the best available scientific data after taking into consideration the economic impact, national security impact, and any other relevant impact of specifying any particular area as critical habitat. The Secretary may exclude an area from designated critical habitat based on economic impacts, impacts on national security, or any other relevant impacts. Exclusion decisions are governed by the regulations at 50 CFR 424.19 and the Policy Regarding Implementation of Section 4(b)(2) of the Endangered Species Act, 81 FR 7226 (Feb. 11, 2016) (2016 Policy)—both of which were developed jointly with the National Marine Fisheries Service (NMFS). We also refer to a 2008 Department of the Interior Solicitor's opinion entitled “The Secretary's Authority to Exclude Areas from a Critical Habitat Designation under Section 4(b)(2) of the Endangered Species Act” (M-37016). We explain each decision to exclude areas, as well as decisions not to exclude, to demonstrate that the decision is reasonable.</P>
                    <P>In considering whether to exclude a particular area from the designation, we identify the benefits of including the area in the designation, identify the benefits of excluding the area from the designation, and evaluate whether the benefits of exclusion outweigh the benefits of inclusion. If the analysis indicates that the benefits of exclusion outweigh the benefits of inclusion, the Secretary may exercise discretion to exclude the area only if such exclusion would not result in the extinction of the species. In making the determination to exclude a particular area, the statute on its face, as well as the legislative history, are clear that the Secretary has broad discretion regarding which factor(s) to use and how much weight to give to any factor. We describe below the process that we undertook for taking into consideration each category of impacts and our analyses of the relevant impacts.</P>
                    <HD SOURCE="HD2">Consideration of Economic Impacts</HD>
                    <P>
                        Section 4(b)(2) of the Act and its implementing regulations require that we consider the economic impact that may result from a designation of critical habitat. To assess the probable economic impacts of a designation, we must first evaluate specific land uses or activities and projects that may occur in the area of the critical habitat. We then must evaluate the impacts that a specific critical habitat designation may have on restricting or modifying specific land uses or activities for the benefit of the species and its habitat within the areas proposed. We then identify which conservation efforts may be the result of the species being listed under the Act versus those attributed solely to the designation of critical habitat for this particular species. The probable economic impact of a proposed critical habitat designation is analyzed by 
                        <PRTPAGE P="62649"/>
                        comparing scenarios both “with critical habitat” and “without critical habitat.”
                    </P>
                    <P>The “without critical habitat” scenario represents the baseline for the analysis, which includes the existing regulatory and socio-economic burden imposed on landowners, managers, or other resource users potentially affected by the designation of critical habitat (for example, under the Federal listing as well as other Federal, State, and local regulations). Therefore, the baseline represents the costs of all efforts attributable to the listing of the species under the Act (that is, conservation of the species and its habitat incurred regardless of whether critical habitat is designated). The “with critical habitat” scenario describes the incremental impacts associated specifically with the designation of critical habitat for the species. The incremental conservation efforts and associated impacts would not be expected without the designation of critical habitat for the species. In other words, the incremental costs are those attributable solely to the designation of critical habitat, above and beyond the baseline costs. These are the costs we use when evaluating the benefits of inclusion and exclusion of particular areas from the final designation of critical habitat should we choose to conduct a discretionary 4(b)(2) exclusion analysis.</P>
                    <P>Executive Orders (E.O.s) 12866 and 13563 direct Federal agencies to assess the costs and benefits of available regulatory alternatives in quantitative (to the extent feasible) and qualitative terms. Consistent with the E.O. regulatory analysis requirements, our effects analysis under the Act may take into consideration impacts to both directly and indirectly affected entities, where practicable and reasonable. If sufficient data are available, we assess, to the extent practicable, the probable impacts to both directly and indirectly affected entities. Section 3(f) of E.O. 12866 identifies four criteria when a regulation is considered a “significant” rulemaking, and requires additional analysis, review, and approval if met. The criteria relevant here is whether the designation of critical habitat may have an economic effect of greater than $100 million in any given year (section 3(f)(1)). Therefore, our consideration of economic impacts uses a screening analysis to assess whether a designation of critical habitat for the Key ring-necked snake or the rim rock crowned snake is likely to exceed the economically significant threshold.</P>
                    <P>For these particular designations, we developed incremental effects memorandums (IEMs) considering the probable incremental economic impacts that may result from this proposed designation of critical habitat. The information contained in our IEMs was then used to develop a screening analysis of the probable effects of the designation of critical habitat for the Key ring-necked snake and the rim rock crowned snake (Industrial Economics, Incorporated (IEc) 2021, entire). We began by conducting a screening analysis of the proposed designation of critical habitat in order to focus our analysis on the key factors that are likely to result in incremental economic impacts. The purpose of the screening analysis is to filter out particular geographic areas of critical habitat that are already subject to such protections and are, therefore, unlikely to incur incremental economic impacts. In particular, the screening analysis considers baseline costs (that is, absent critical habitat designation) and includes any probable incremental economic impacts where land and water use may already be subject to conservation plans, land management plans, best management practices, or regulations that protect the habitat area as a result of the Federal listing status of the species. Ultimately, the screening analysis allows us to focus our analysis on evaluating the specific areas or sectors that may incur probable incremental economic impacts as a result of the designation. The presence of the listed species in occupied areas of critical habitat means that any destruction or adverse modification of those areas will also likely jeopardize the continued existence of the species. Therefore, designating occupied areas as critical habitat typically causes little if any incremental impacts above and beyond the impacts of listing the species. Accordingly, the screening analysis focuses on areas of unoccupied critical habitat. If the proposed critical habitat designation contains any unoccupied units, the screening analysis assesses whether those units require additional management or conservation efforts that may incur incremental economic impacts. This screening analysis, combined with the information contained in our IEMs, constitute what we consider to be our draft economic analysis (DEA) of the proposed critical habitat designation for the Key ring-necked snake and the rim rock crowned snake; our DEA is summarized in the narrative below.</P>
                    <P>As part of our screening analysis, we considered the types of economic activities that are likely to occur within the areas that may be affected by the critical habitat designation. In our evaluation of the probable incremental economic impacts that may result from the proposed designation of critical habitat for the Key ring-necked snake and the rim rock crowned snake, first we identified, in the IEM dated April 19, 2021, probable incremental economic impacts associated with the following categories of activities: (1) Land development (commercial and residential); (2) agriculture development; (3) refuge activities (construction related to infrastructure, asphalt road and debris removal, mechanical treatments to support prescribed fire, invasive species removal, out planting, prescribed fire); and (4) recreational activities. We considered each industry or category individually. Additionally, we considered whether their activities have any Federal involvement. Critical habitat designation generally will not affect activities that do not have any Federal involvement; under the Act, designation of critical habitat only affects activities conducted, funded, permitted, or authorized by Federal agencies. If we list the species, in areas where the species is present, Federal agencies would be required to consult with the Service under section 7 of the Act on activities they fund, permit, or implement that may affect the species. If, when we list the species, we also finalize the proposed critical habitat designations, our consultation would include an evaluation of measures to avoid the destruction or adverse modification of critical habitat.</P>
                    <P>
                        In our IEMs, we attempted to clarify the distinction between the effects that would result from the species being listed and those attributable to the critical habitat designation (that is, difference between the jeopardy and adverse modification standards) for the Key ring-necked snake's and the rim rock crowned snake's critical habitat. Because the designations of critical habitat for Key ring-necked snake and the rim rock crowned snake are proposed concurrently with the listing, it has been our experience that it is more difficult to discern which conservation efforts are attributable to the species being listed and those which will result solely from the designation of critical habitat. However, the following specific circumstances in this case help to inform our evaluation: (1) The essential physical or biological features identified for critical habitat are the same features essential for the life requisites of the species, and (2) any actions that would likely adversely affect the essential physical or biological features of occupied critical habitat are also likely to adversely affect the 
                        <PRTPAGE P="62650"/>
                        species. The IEMs outline our rationale concerning this limited distinction between baseline conservation efforts and incremental impacts of the designation of critical habitat for this species. This evaluation of the incremental effects has been used as the basis to evaluate the probable incremental economic impacts of this proposed designation of critical habitat.
                    </P>
                    <P>The proposed critical habitat designation for the Key ring-necked snake totals approximately 2,604 ac (1,054 ha). All units are occupied. The proposed critical habitat for the rim rock crowned snake totals 5,972 ac (2,418 ha). Of the 11 critical habitat units for the rim rock crowned snake, 9 are occupied and 2 are considered unoccupied.</P>
                    <P>
                        When an action is proposed in an area of designated critical habitat, and the proposed activity has a Federal nexus, the need for consultation is triggered. Any incremental costs associated with consideration of potential effects to the critical habitat are a result of this consultation process. For all occupied areas, the economic costs of critical habitat designations will most likely be limited to additional administrative efforts to consider adverse modification in section 7 consultations, as the listing of both species is happening concurrently with critical habitat designation, and all occupied units would still need to undergo section 7 consultation due to listing regardless of critical habitat designation. While this additional analysis will require time and resources by both the Federal action agency and the Service, it is believed that, in most circumstances, these costs would predominantly be administrative in nature and would not be significant. In total, critical habitat designations for the Key ring-necked snake and the rim rock crowned snake are unlikely to generate costs or benefits exceeding $100 million in a single year. For the Key ring-necked snake, the analysis predicted that approximately one formal consultation, three informal consultations, and three technical assistance efforts are anticipated to occur annually in proposed critical habitat areas. For the rim rock crowned snake, the analysis predicted that approximately two formal consultations, eight informal consultations, and nine technical assistance efforts are anticipated to occur annually in proposed critical habitat areas (IEc 2021, p. 3). For the Key ring-necked snake, approximately 85 percent of the proposed areas overlap with existing designations for species including Bartram's scrub-hairstreak butterfly (
                        <E T="03">Strymon acis bartrami</E>
                        ), the Lower Florida Keys distinct population segment of the rice rat (
                        <E T="03">Oryzomys palustris natator</E>
                        ), and Florida semaphore cactus (
                        <E T="03">Consolea corallicola</E>
                        ). For the rim rock crowned snake, approximately 90 percent of the proposed areas overlaps with other designations, including Bartram's scrub-hairstreak butterfly, Florida leafwing butterfly (
                        <E T="03">Anaea troglodyta floridalis</E>
                        ), Florida brickell-bush (
                        <E T="03">Brickellia mosieri</E>
                        ), Carter's small-flowered flax (
                        <E T="03">Linum carteri</E>
                         var. 
                        <E T="03">carteri</E>
                        ), and the Florida distinct population segment of the American crocodile (
                        <E T="03">Crocodylus acutus</E>
                        ).
                    </P>
                    <P>Overall, we expect that agency administrative costs for consultation, incurred by the Service and the consulting Federal agency, would be minor (less than $6,000 per consultation effort) and, therefore, would not be significant (IEc 2021, p. 22). The total annual incremental costs of critical habitat designations for the Key ring-necked snake and rim rock crowned snake are anticipated to be less than $14,400 per year and $35,200 per year, respectively.</P>
                    <P>Incremental costs may occur outside of the section 7 consultation process if the designation of critical habitat triggers additional requirements or project modifications under State or local laws, regulations, or management strategies. These types of costs typically occur if the designation increases awareness of the presence of the species or the need for protection of its habitat. Given that both the Key ring-necked snake and the rim rock crowned snake are covered by certain existing Federal and State protections, project proponents may already be aware of the presence of the two species. For example, the rim rock crowned snake is a covered species under the Coral Reef Commons HCP, and both the Key ring-necked snake and rim rock crowned snake are listed as “State-designated Threatened” on Florida's Endangered and Threatened Species list. The species are further protected through habitat management and conservation under Florida's Imperiled Species Management Plan, the Florida Keys Wildlife and Environmental Area Management Plan, Monroe County Year 2030 Comprehensive Plan, and the National Key Deer Wildlife Refuge. Therefore, designating critical habitat is unlikely to provide information to State or local agencies that would result in new regulations or actions (IEc 2021, pp. 20-21).</P>
                    <P>With regard to the two unoccupied units for the rim rock crowned snake, additional costs are unlikely because the proposed units substantially overlap with critical habitat designations for other species (over 95 percent total overlap for each unit). In these areas, consultations for listed species and designated critical habitat are likely to have already resulted in protections for habitat suitable for the rim rock crowned snake even absent listing or critical habitat designation.</P>
                    <P>We are soliciting data and comments from the public on the DEA discussed above, as well as on all aspects of this proposed rule and our required determinations. During the development of a final designation, we will consider the information presented in the DEA and any additional information on economic impacts we receive during the public comment period to determine whether any specific areas should be excluded from the final critical habitat designation under authority of section 4(b)(2) of the Act and our implementing regulations at 50 CFR 424.19. We may exclude an area from critical habitat if we determine that the benefits of excluding the area outweigh the benefits of including the area, provided the exclusion will not result in the extinction of this species.</P>
                    <HD SOURCE="HD2">Consideration of National Security Impacts</HD>
                    <P>Section 4(a)(3)(B)(i) of the Act may not cover all DoD lands or areas that pose potential national-security concerns (for example, a DoD installation that is in the process of revising its INRMP for a newly listed species or a species previously not covered). If a particular area is not covered under section 4(a)(3)(B)(i), then national-security or homeland-security concerns are not a factor in the process of determining what areas meet the definition of “critical habitat.” However, the Service must still consider impacts on national security, including homeland security, on those lands or areas not covered by section 4(a)(3)(B)(i), because section 4(b)(2) requires the Service to consider those impacts whenever it designates critical habitat. Accordingly, if DoD, Department of Homeland Security (DHS), or another Federal agency has requested exclusion based on an assertion of national-security or homeland-security concerns, or we have otherwise identified national-security or homeland-security impacts from designating particular areas as critical habitat, we generally have reason to consider excluding those areas.</P>
                    <P>
                        However, we cannot automatically exclude requested areas. When DoD, DHS, or another Federal agency requests exclusion from critical habitat on the basis of national-security or homeland-
                        <PRTPAGE P="62651"/>
                        security impacts, it must provide a reasonably specific justification of an incremental impact on national security that would result from the designation of that specific area as critical habitat. That justification could include demonstration of probable impacts, such as impacts to ongoing border-security patrols and surveillance activities, or a delay in training or facility construction, as a result of compliance with section 7(a)(2) of the Act. If the agency requesting the exclusion does not provide us with a reasonably specific justification, we will contact the agency to recommend that it provide a specific justification or clarification of its concerns relative to the probable incremental impact that could result from the designation. If we conduct an exclusion analysis because the agency provides a reasonably specific justification or because we decide to exercise the discretion to conduct an exclusion analysis, we will defer to the expert judgment of DoD, DHS, or another Federal agency as to: (1) Whether activities on its lands or waters, or its activities on other lands or waters, have national-security or homeland-security implications; (2) the importance of those implications; and (3) the degree to which the cited implications would be adversely affected in the absence of an exclusion. In that circumstance, in conducting a discretionary section 4(b)(2) exclusion analysis, we will give great weight to national-security and homeland-security concerns in analyzing the benefits of exclusion.
                    </P>
                    <P>In preparing this proposal, we have determined that the lands within the proposed designation of critical habitat for the Key ring-necked snake are not owned or managed by the DoD or DHS, and, therefore, we anticipate no impact on national security or homeland security. For the rim rock crowned snake, as mentioned above, approximately 80 ac (32 ha) of the U.S. Coast Guard property is proposed for designation as critical habitat in the Richmond Pine Rocklands unit (Unit 1). This U.S. Coast Guard property is separated into two main areas: the Communication Station (COMMSTA) Miami and the Civil Engineering Unit (CEU). The COMMSTA houses transmitting and receiving antennas. The CEU plans and executes projects at regional shore facilities, such as construction and post-disaster assessments.</P>
                    <P>The U.S. Coast Guard parcel contains approximately 80 ac (32 ha) of pine rocklands. The U.S. Coast Guard parcel has a draft management plan that includes management of pine rockland habitats, including vegetation control and prescribed fire and protection of lands from further development or degradation. In addition, the standing pine rockland area is partially managed through an active recovery grant to the Institute for Regional Conservation. Under this grant, up to 39 ac (16 ha) of standing pine rocklands will undergo invasive vegetation control.</P>
                    <P>Based on a review of the specific mission of the U.S. Coast Guard facility in conjunction with the measures and efforts set forth in the draft management plan to preserve pine rockland habitat and protect sensitive and listed species, we have determined that it is unlikely that the critical habitat, if finalized as proposed, would negatively impact the facility or its operations. As a result, we do not anticipate any impact on national security.</P>
                    <P>However, if through the public comment period we receive information regarding impacts on national security or homeland security from designating particular areas as critical habitat, then as part of developing the final designation of critical habitat, we will conduct a discretionary exclusion analysis to determine whether to exclude those areas under authority of section 4(b)(2) and our implementing regulations at 50 CFR 424.19.</P>
                    <HD SOURCE="HD2">Consideration of Other Relevant Impacts</HD>
                    <P>Under section 4(b)(2) of the Act, we consider any other relevant impacts, in addition to economic impacts and impacts on national security discussed above. To identify other relevant impacts that may affect the exclusion analysis, we consider a number of factors, including whether there are permitted conservation plans covering the species in the area—such as HCPs, safe harbor agreements (SHAs), or candidate conservation agreements with assurances (CCAAs)—or whether there are non-permitted conservation agreements and partnerships that may be impaired by designation of, or exclusion from, critical habitat. In addition, we look at whether Tribal conservation plans or partnerships, Tribal resources, or government-to-government relationships of the United States with Tribal entities may be affected by the designation. We also consider any State, local, social, or other impacts that might occur because of the designation.</P>
                    <P>For the Key ring-necked snake, we have not identified any areas to consider for exclusion from critical habitat. In preparing this proposal, we have determined that there are currently no management plans for the Key ring-necked snake, and no HCPs where the Key ring-necked snake is a covered species. Additionally, the proposed designation does not include any Tribal lands or trust resources. Therefore, we anticipate no impact on Tribal lands, partnerships, or HCPs from this proposed critical habitat designation. However, during the development of a final designation, we will consider any information currently available or received during the public comment period. If we evaluate information regarding a request for an exclusion and we do not exclude, we will fully describe our rationale for not excluding in the final critical habitat determination.</P>
                    <P>For the rim rock crowned snake, we are considering a portion of one unit (Unit 1: Richmond Pine Rocklands) for exclusion due to other relevant impacts because of the presence of an HCP that includes the rim rock crowned snake as a covered species. When analyzing other relevant impacts of including a particular area in a designation of critical habitat, we weigh those impacts relative to the conservation value of the particular area. To determine the conservation value of designating a particular area, we consider a number of factors, including, but not limited to, the additional regulatory benefits that the area would receive due to the protection from destruction or adverse modification as a result of actions with a Federal nexus, the educational benefits of mapping essential habitat for recovery of the listed species, and any benefits that may result from a designation due to State or Federal laws that may apply to critical habitat.</P>
                    <P>In the case of the rim rock crowned snake, the benefits of critical habitat include public awareness of the presence of the rim rock crowned snake and the importance of habitat protection, and, where a Federal nexus exists, increased habitat protection for the rim rock crowned snake due to protection from destruction or adverse modification of critical habitat. Continued implementation of an ongoing management plan that provides conservation equal to or more than the protections that result from a critical habitat designation would reduce those benefits of including that specific area in the critical habitat designation.</P>
                    <P>
                        We evaluate the existence of a conservation plan when considering the benefits of inclusion. We consider a variety of factors, including, but not limited to, whether the plan is finalized; how it provides for the conservation of the essential physical or biological features; whether there is a reasonable expectation that the conservation 
                        <PRTPAGE P="62652"/>
                        management strategies and actions contained in a management plan will be implemented into the future; whether the conservation strategies in the plan are likely to be effective; and whether the plan contains a monitoring program or adaptive management to ensure that the conservation measures are effective and can be adapted in the future in response to new information.
                    </P>
                    <P>After identifying the benefits of inclusion and the benefits of exclusion, we carefully weigh the two sides to evaluate whether the benefits of exclusion outweigh those of inclusion. If our analysis indicates that the benefits of exclusion outweigh the benefits of inclusion, we then determine whether exclusion would result in extinction of the species. If exclusion of an area from critical habitat will result in extinction, we will not exclude it from the designation.</P>
                    <HD SOURCE="HD3">Private or Other Non-Federal Conservation Plans Related to Permits Under Section 10 of the Act</HD>
                    <P>HCPs for incidental take permits under section 10(a)(1)(B) of the Act provide for partnerships with non-Federal entities to minimize and mitigate impacts to listed species and their habitats. In some cases, HCP permittees agree to do more for the conservation of the species and their habitats on private lands than designation of critical habitat would provide alone. We place great value on the partnerships that are developed during the preparation and implementation of HCPs.</P>
                    <P>CCAAs and SHAs are voluntary agreements designed to conserve candidate and listed species, respectively, on non-Federal lands. In exchange for actions that contribute to the conservation of species on non-Federal lands, participating property owners are covered by an “enhancement of survival” permit under section 10(a)(1)(A) of the Act, which authorizes incidental take of the covered species that may result from implementation of conservation actions, specific land uses, and, in the case of SHAs, the option to return to a baseline condition under the agreements. We also provide enrollees assurances that we will not impose further land-, water-, or resource-use restrictions, or require additional commitments of land, water, or finances, beyond those agreed to in the agreements.</P>
                    <P>When we undertake a discretionary section 4(b)(2) exclusion analysis based on permitted conservation plans (such as CCAAs, SHAs, and HCPs), we anticipate consistently excluding such areas if incidental take caused by the activities in those areas is covered by the permit under section 10 of the Act and the CCAA/SHA/HCP meets all of the following three factors (see the 2016 Policy for additional details):</P>
                    <P>(a) The permittee is properly implementing the CCAA/SHA/HCP and is expected to continue to do so for the term of the agreement. A CCAA/SHA/HCP is properly implemented if the permittee is and has been fully implementing the commitments and provisions in the CCAA/SHA/HCP, Implementing Agreement, and permit.</P>
                    <P>(b) The species for which critical habitat is being designated is a covered species in the CCAA/SHA/HCP, or very similar in its habitat requirements to a covered species. The recognition that the Services extend to such an agreement depends on the degree to which the conservation measures undertaken in the CCAA/SHA/HCP would also protect the habitat features of the similar species.</P>
                    <P>(c) The CCAA/SHA/HCP specifically addresses that species' habitat and meets the conservation needs of the species in the planning area.</P>
                    <P>The proposed critical habitat designation includes areas that are covered by the following permitted plan providing for the conservation of the rim rock crowned snake: the Coral Reef Commons HCP.</P>
                    <P>
                        <E T="03">Coral Reef Commons Habitat Conservation Plan—</E>
                        In preparing this proposal, we have determined that lands associated with the Coral Reef Commons HCP within the Richmond Pine Rocklands unit (Unit 1) are included within the boundaries of the proposed critical habitat.
                    </P>
                    <P>Coral Reef Commons is a mixed-use community, which consists of 900 apartments, retail stores, restaurants, and parking. In 2017, an HCP and associated permit under section 10 of the Act was developed and issued for the Coral Reef Commons development. As part of the HCP and permit, an approximately 53-ac (21-ha) on-site preserve (same as the area for proposed critical habitat designation) was established under a conservation encumbrance that will be managed in perpetuity for pine rocklands habitat and sensitive and listed species, including the rim rock crowned snake. An additional pine rocklands area of approximately 57 ac (23 ha) on the University of Miami's Center for Southeastern Tropical Advanced Remote Sensing site is an off-site mitigation area for Coral Reef Commons. Both the on-site preserve and the off-site mitigation area are being managed to maintain healthy pine rocklands habitat through the use of invasive, exotic plant management; mechanical treatment; and prescribed fire. Since initiating the Coral Reef Commons HCP, pine rocklands restoration efforts have been conducted within all of the management units in both the on-site preserves and the off-site mitigation area. A second round of prescribed fire began in February 2021. Currently, the on-site preserves meet or exceed the success criteria described in the HCP.</P>
                    <P>Critical habitat within Unit 1 that is associated with the Coral Reef Commons HCP is limited to the on-site preserves and off-site mitigation area. Based on our review of the HCP and proposed critical habitat for the rim rock crowned snake, we do not anticipate needing any additional conservation measures for the species beyond those that are currently in place. Therefore, we are considering excluding those specific lands associated with the Coral Reef Commons HCP that are in the preserve and off-site mitigation area from the final designation of critical habitat for the rim rock crowned snake. After consideration of public comment on this issue, we will analyze in the final rule whether the benefits of excluding the lands described above from the final designation of critical habitat for the rim rock crowned snake outweigh the benefits of designating those lands as critical habitat. Based on that analysis, the Secretary may exercise her discretion to exclude the lands from the final designation.</P>
                    <HD SOURCE="HD1">Summary of Exclusions Considered Under 4(b)(2) of the Act</HD>
                    <P>
                        For the Key ring-necked snake, we are not considering at this time any exclusions from the proposed designation based on economic impacts, national security impacts, or other relevant impacts—such as partnerships, management, or protection afforded by cooperative management efforts—under section 4(b)(2) of the Act. However, in this proposed rule, we seek information from the public with respect to whether there are any areas that should be considered for exclusion from the critical habitat designation. (Please see 
                        <E T="02">ADDRESSES</E>
                         for instructions on how to submit comments).
                    </P>
                    <P>We are considering whether to exclude the following areas under section 4(b)(2) of the Act from the final critical habitat designation for the rim rock crowned snake: a portion of Unit 1 (Richmond Pine Rocklands) covered by the Coral Reef Commons HCP (102 ac (41.3 ha)), which includes onsite preserves and offsite mitigation areas.</P>
                    <P>
                        In conclusion, for the rim rock crowned snake, we are considering exclusions based on other relevant 
                        <PRTPAGE P="62653"/>
                        impacts. We specifically solicit comments on the inclusion or exclusion of such areas. During the development of a final designation, we will consider any information currently available or received during the public comment period regarding other relevant impacts of the proposed designation and will determine whether these or any other specific areas should be excluded from the final critical habitat designation under authority of section 4(b)(2) and our implementing regulations at 50 CFR 424.19, and the 2016 Policy.
                    </P>
                    <HD SOURCE="HD1">Required Determinations</HD>
                    <HD SOURCE="HD2">Clarity of the Rule</HD>
                    <P>We are required by Executive Orders 12866 and 12988 and by the Presidential Memorandum of June 1, 1998, to write all rules in plain language. This means that each rule we publish must:</P>
                    <P>(1) Be logically organized;</P>
                    <P>(2) Use the active voice to address readers directly;</P>
                    <P>(3) Use clear language rather than jargon;</P>
                    <P>(4) Be divided into short sections and sentences; and</P>
                    <P>(5) Use lists and tables wherever possible.</P>
                    <P>
                        If you feel that we have not met these requirements, send us comments by one of the methods listed in 
                        <E T="02">ADDRESSES</E>
                        . To better help us revise the rule, your comments should be as specific as possible. For example, you should tell us the numbers of the sections or paragraphs that are unclearly written, which sections or sentences are too long, the sections where you feel lists or tables would be useful, etc.
                    </P>
                    <HD SOURCE="HD2">Regulatory Planning and Review (Executive Orders 12866 and 13563)</HD>
                    <P>Executive Order 12866 provides that the Office of Information and Regulatory Affairs (OIRA) in the Office of Management and Budget will review all significant rules. OIRA has determined that this rule is not significant.</P>
                    <P>Executive Order 13563 reaffirms the principles of E.O. 12866 while calling for improvements in the nation's regulatory system to promote predictability, to reduce uncertainty, and to use the best, most innovative, and least burdensome tools for achieving regulatory ends. The Executive order directs agencies to consider regulatory approaches that reduce burdens and maintain flexibility and freedom of choice for the public where these approaches are relevant, feasible, and consistent with regulatory objectives. E.O. 13563 emphasizes further that regulations must be based on the best available science and that the rulemaking process must allow for public participation and an open exchange of ideas. We have developed this proposed rule in a manner consistent with these requirements.</P>
                    <HD SOURCE="HD2">Regulatory Flexibility Act (5 U.S.C. 601 et seq.)</HD>
                    <P>
                        Under the Regulatory Flexibility Act (RFA; 5 U.S.C. 601 
                        <E T="03">et seq.</E>
                        ), as amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (SBREFA; 5 U.S.C. 801 
                        <E T="03">et seq.</E>
                        ), whenever an agency is required to publish a notice of rulemaking for any proposed or final rule, it must prepare and make available for public comment a regulatory flexibility analysis that describes the effects of the rule on small entities (that is, small businesses, small organizations, and small government jurisdictions). However, no regulatory flexibility analysis is required if the head of the agency certifies the rule will not have a significant economic impact on a substantial number of small entities. The SBREFA amended the RFA to require Federal agencies to provide a certification statement of the factual basis for certifying that the rule will not have a significant economic impact on a substantial number of small entities.
                    </P>
                    <P>According to the Small Business Administration, small entities include small organizations such as independent nonprofit organizations; small governmental jurisdictions, including school boards and city and town governments that serve fewer than 50,000 residents; and small businesses (13 CFR 121.201). Small businesses include manufacturing and mining concerns with fewer than 500 employees, wholesale trade entities with fewer than 100 employees, retail and service businesses with less than $5 million in annual sales, general and heavy construction businesses with less than $27.5 million in annual business, special trade contractors doing less than $11.5 million in annual business, and agricultural businesses with annual sales less than $750,000. To determine whether potential economic impacts to these small entities are significant, we considered the types of activities that might trigger regulatory impacts under this designation as well as types of project modifications that may result. In general, the term “significant economic impact” is meant to apply to a typical small business firm's business operations.</P>
                    <P>Under the RFA, as amended, and as understood in light of recent court decisions, Federal agencies are required to evaluate the potential incremental impacts of rulemaking on those entities directly regulated by the rulemaking itself; in other words, the RFA does not require agencies to evaluate the potential impacts to indirectly regulated entities. The regulatory mechanism through which critical habitat protections are realized is section 7 of the Act, which requires Federal agencies, in consultation with the Service, to ensure that any action authorized, funded, or carried out by the agency is not likely to destroy or adversely modify critical habitat. Therefore, under section 7, only Federal action agencies are directly subject to the specific regulatory requirement (avoiding destruction and adverse modification) imposed by critical habitat designation. Consequently, it is our position that only Federal action agencies would be directly regulated if we adopt the proposed critical habitat designation. The RFA does not require evaluation of the potential impacts to entities not directly regulated. Moreover, Federal agencies are not small entities. Therefore, because no small entities would be directly regulated by this rulemaking, the Service certifies that, if made final as proposed, the proposed critical habitat designation will not have a significant economic impact on a substantial number of small entities.</P>
                    <P>In summary, we have considered whether the proposed designation would result in a significant economic impact on a substantial number of small entities. For the above reasons and based on currently available information, we certify that, if made final, the proposed critical habitat designation would not have a significant economic impact on a substantial number of small business entities. Therefore, an initial regulatory flexibility analysis is not required.</P>
                    <HD SOURCE="HD2">Energy Supply, Distribution, or Use—Executive Order 13211</HD>
                    <P>
                        Executive Order 13211 (Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use) requires agencies to prepare Statements of Energy Effects when undertaking certain actions. In our economic analysis, we did not find that this proposed critical habitat designation would significantly affect energy supplies, distribution, or use, as there are no energy facilities within the boundaries of the proposed critical habitat units for either the Key ring-necked snake or the rim rock crowned snake. Therefore, this action is not a significant energy action, and no Statement of Energy Effects is required.
                        <PRTPAGE P="62654"/>
                    </P>
                    <HD SOURCE="HD2">Unfunded Mandates Reform Act (2 U.S.C. 1501 et seq.)</HD>
                    <P>
                        In accordance with the Unfunded Mandates Reform Act (2 U.S.C. 1501 
                        <E T="03">et seq.</E>
                        ), we make the following finding:
                    </P>
                    <P>(1) This proposed rule would not produce a Federal mandate. In general, a Federal mandate is a provision in legislation, statute, or regulation that would impose an enforceable duty upon State, local, or Tribal governments, or the private sector, and includes both “Federal intergovernmental mandates” and “Federal private sector mandates.” These terms are defined in 2 U.S.C. 658(5)-(7). “Federal intergovernmental mandate” includes a regulation that “would impose an enforceable duty upon State, local, or Tribal governments” with two exceptions. It excludes “a condition of Federal assistance.” It also excludes “a duty arising from participation in a voluntary Federal program,” unless the regulation “relates to a then-existing Federal program under which $500,000,000 or more is provided annually to State, local, and Tribal governments under entitlement authority,” if the provision would “increase the stringency of conditions of assistance” or “place caps upon, or otherwise decrease, the Federal Government's responsibility to provide funding,” and the State, local, or Tribal governments “lack authority” to adjust accordingly. At the time of enactment, these entitlement programs were: Medicaid; Aid to Families with Dependent Children work programs; Child Nutrition; Food Stamps; Social Services Block Grants; Vocational Rehabilitation State Grants; Foster Care, Adoption Assistance, and Independent Living; Family Support Welfare Services; and Child Support Enforcement. “Federal private sector mandate” includes a regulation that “would impose an enforceable duty upon the private sector, except (i) a condition of Federal assistance or (ii) a duty arising from participation in a voluntary Federal program.”</P>
                    <P>The designation of critical habitat does not impose a legally binding duty on non-Federal Government entities or private parties. Under the Act, the only regulatory effect is that Federal agencies must ensure that their actions do not destroy or adversely modify critical habitat under section 7. While non-Federal entities that receive Federal funding, assistance, or permits, or that otherwise require approval or authorization from a Federal agency for an action, may be indirectly impacted by the designation of critical habitat, the legally binding duty to avoid destruction or adverse modification of critical habitat rests squarely on the Federal agency. Furthermore, to the extent that non-Federal entities are indirectly impacted because they receive Federal assistance or participate in a voluntary Federal aid program, the Unfunded Mandates Reform Act would not apply, nor would critical habitat shift the costs of the large entitlement programs listed above onto State governments.</P>
                    <P>(2) We do not believe that this proposed rule would significantly or uniquely affect small governments because it will not produce a Federal mandate of $100 million or greater in any year, that is, it is not a “significant regulatory action” under the Unfunded Mandates Reform Act. The designation of critical habitat imposes no obligations on State or local governments and, as such, a Small Government Agency Plan is not required.</P>
                    <HD SOURCE="HD2">Takings—Executive Order 12630</HD>
                    <P>In accordance with E.O. 12630 (Government Actions and Interference with Constitutionally Protected Private Property Rights), we have analyzed the potential takings implications of designating critical habitat for the Key ring-necked snake and the rim rock crowned snake in a takings implications assessment. The Act does not authorize the Service to regulate private actions on private lands or confiscate private property as a result of critical habitat designation. Designation of critical habitat does not affect land ownership, or establish any closures, or restrictions on use of or access to the designated areas. Furthermore, the designation of critical habitat does not affect landowner actions that do not require Federal funding or permits, nor does it preclude development of habitat conservation programs or issuance of incidental take permits to permit actions that do require Federal funding or permits to go forward. However, Federal agencies are prohibited from carrying out, funding, or authorizing actions that would destroy or adversely modify critical habitat. A takings implications assessment has been completed for the proposed designation of critical habitat for the Key ring-necked snake and the rim rock crowned snake, and it concludes that, if adopted, this designation of critical habitat does not pose significant takings implications for lands within or affected by the designation.</P>
                    <HD SOURCE="HD2">Federalism—Executive Order 13132</HD>
                    <P>In accordance with E.O. 13132 (Federalism), this proposed rule does not have significant Federalism effects. A federalism summary impact statement is not required. In keeping with Department of the Interior and Department of Commerce policy, we requested information from, and coordinated development of this proposed critical habitat designation with, appropriate State resource agencies. From a federalism perspective, the designation of critical habitat directly affects only the responsibilities of Federal agencies. The Act imposes no other duties with respect to critical habitat, either for States and local governments, or for anyone else. As a result, the proposed rule does not have substantial direct effects either on the States, or on the relationship between the national government and the States, or on the distribution of powers and responsibilities among the various levels of government. The proposed designation may have some benefit to these governments because the areas that contain the features essential to the conservation of the species are more clearly defined, and the physical or biological features of the habitat necessary for the conservation of the species are specifically identified. This information does not alter where and what federally sponsored activities may occur. However, it may assist State and local governments in long-range planning because they no longer have to wait for case-by-case section 7 consultations to occur.</P>
                    <P>Where State and local governments require approval or authorization from a Federal agency for actions that may affect critical habitat, consultation under section 7(a)(2) of the Act would be required. While non-Federal entities that receive Federal funding, assistance, or permits, or that otherwise require approval or authorization from a Federal agency for an action, may be indirectly impacted by the designation of critical habitat, the legally binding duty to avoid destruction or adverse modification of critical habitat rests squarely on the Federal agency.</P>
                    <HD SOURCE="HD2">Civil Justice Reform—Executive Order 12988</HD>
                    <P>
                        In accordance with E.O. 12988 (Civil Justice Reform), the Office of the Solicitor has determined that the rule would not unduly burden the judicial system and that it meets the requirements of sections 3(a) and 3(b)(2) of the order. We have proposed designating critical habitat in accordance with the provisions of the Act. To assist the public in understanding the habitat needs of the species, this proposed rule identifies the physical or biological features essential to the conservation of the species. The proposed areas of critical habitat are 
                        <PRTPAGE P="62655"/>
                        presented on maps, and the proposed rule provides several options for the interested public to obtain more detailed location information, if desired.
                    </P>
                    <HD SOURCE="HD2">Paperwork Reduction Act of 1995 (44 U.S.C. 3501 et seq.)</HD>
                    <P>
                        This rule does not contain information collection requirements, and a submission to the Office of Management and Budget (OMB) under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                        ) is not required. We may not conduct or sponsor and you are not required to respond to a collection of information unless it displays a currently valid OMB control number.
                    </P>
                    <HD SOURCE="HD2">National Environmental Policy Act (42 U.S.C. 4321 et seq.)</HD>
                    <P>
                        It is our position that, outside the jurisdiction of the U.S. Court of Appeals for the Tenth Circuit, we do not need to prepare environmental analyses pursuant to the National Environmental Policy Act (NEPA; 42 U.S.C. 4321 
                        <E T="03">et seq.</E>
                        ) in connection with regulations adopted pursuant to section 4(a) of the Act. We published a notice outlining our reasons for this determination in the 
                        <E T="04">Federal Register</E>
                         on October 25, 1983 (48 FR 49244). This position was upheld by the U.S. Court of Appeals for the Ninth Circuit (
                        <E T="03">Douglas County</E>
                         v. 
                        <E T="03">Babbitt,</E>
                         48 F.3d 1495 (9th Cir. 1995), cert. denied 516 U.S. 1042 (1996)).
                    </P>
                    <HD SOURCE="HD2">Government-to-Government Relationship With Tribes</HD>
                    <P>In accordance with the President's memorandum of April 29, 1994 (Government-to-Government Relations with Native American Tribal Governments; 59 FR 22951), E.O. 13175 (Consultation and Coordination with Indian Tribal Governments), and the Department of the Interior's manual at 512 DM 2, we readily acknowledge our responsibility to communicate meaningfully with recognized Federal Tribes on a government-to-government basis. In accordance with Secretarial Order 3206 of June 5, 1997 (American Indian Tribal Rights, Federal-Tribal Trust Responsibilities, and the Endangered Species Act), we readily acknowledge our responsibilities to work directly with Tribes in developing programs for healthy ecosystems, to acknowledge that Tribal lands are not subject to the same controls as Federal public lands, to remain sensitive to Indian culture, and to make information available to Tribes. We have determined that no Tribal lands fall within the boundaries of the proposed critical habitat for the Key ring-necked snake or the rim rock crowned snake, so no Tribal lands would be affected by the proposed designation.</P>
                    <HD SOURCE="HD1">References Cited</HD>
                    <P>
                        A complete list of references cited in this rulemaking is available on the internet at 
                        <E T="03">https://www.regulations.gov</E>
                         and upon request from the Florida Ecological Services Field Office (see 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        ).
                    </P>
                    <HD SOURCE="HD1">Authors</HD>
                    <P>The primary authors of this proposed rule are the staff members of the Fish and Wildlife Service's Species Assessment Team and the Florida Ecological Services Field Office.</P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 50 CFR Part 17</HD>
                        <P>Endangered and threatened species, Exports, Imports, Plants, Reporting and recordkeeping requirements, Transportation, Wildlife.</P>
                    </LSTSUB>
                    <HD SOURCE="HD1">Proposed Regulation Promulgation</HD>
                    <P>Accordingly, we propose to amend part 17, subchapter B of chapter I, title 50 of the Code of Federal Regulations, as set forth below:</P>
                    <PART>
                        <HD SOURCE="HED">PART 17—ENDANGERED AND THREATENED WILDLIFE AND PLANTS</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 17 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 16 U.S.C. 1361-1407; 1531-1544; and 4201-4245, unless otherwise noted.</P>
                    </AUTH>
                    <AMDPAR>2. In § 17.11, amend paragraph (h) by adding entries to the List of Endangered and Threatened Wildlife for “Snake, Key ring-necked” and “Snake, rim rock crowned” in alphabetical order under REPTILES to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 17.11</SECTNO>
                        <SUBJECT> Endangered and threatened wildlife.</SUBJECT>
                        <STARS/>
                        <P>(h) * * *</P>
                        <GPOTABLE COLS="5" OPTS="L1,tp0,i1" CDEF="s50,r50,r50,8C,r75">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1">Common name</CHED>
                                <CHED H="1">Scientific name</CHED>
                                <CHED H="1">Where listed</CHED>
                                <CHED H="1">Status</CHED>
                                <CHED H="1">Listing citations and applicable rules</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW EXPSTB="04">
                                <ENT I="21">
                                    <E T="02">Reptiles</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Snake, Key ring-necked</ENT>
                                <ENT>
                                    <E T="03">Diadophis punctatus acricus</E>
                                </ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    [
                                    <E T="02">Federal Register</E>
                                     citation when published as a final rule]; 50 CFR 17.95(c).
                                    <SU>CH</SU>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Snake, rim rock crowned</ENT>
                                <ENT>
                                    <E T="03">Tantilla oolitica</E>
                                </ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    [
                                    <E T="02">Federal Register</E>
                                     citation when published as a final rule]; 50 CFR 17.95(c).
                                    <SU>CH</SU>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                        </GPOTABLE>
                    </SECTION>
                    <AMDPAR>3. In §  17.95, amend paragraph (c) by:</AMDPAR>
                    <AMDPAR>
                        a. Adding an entry for “Key Ring-necked Snake (
                        <E T="03">Diadophis punctatus acricus</E>
                        )” immediately following the entry for “New Mexican Ridge-Nosed Rattlesnake (
                        <E T="03">Crotalus willardi obscurus</E>
                        )”; and
                    </AMDPAR>
                    <AMDPAR>
                        b. Adding an entry for “Rim Rock Crowned Snake (
                        <E T="03">Tantilla oolitica</E>
                        )” immediately following the entry for “Key Ring-necked Snake (
                        <E T="03">Diadophis punctatus acricus</E>
                        )”.
                    </AMDPAR>
                    <P>The additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 17.95</SECTNO>
                        <SUBJECT> Critical habitat—fish and wildlife.</SUBJECT>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">Reptiles.</E>
                        </P>
                        <STARS/>
                        <HD SOURCE="HD3">
                            Key Ring-Necked Snake (
                            <E T="03">Diadophis punctatus acricus</E>
                            )
                        </HD>
                        <P>(1) Critical habitat units are depicted for Monroe County, Florida, on the maps in this entry.</P>
                        <P>
                            (2) Within these areas, the physical or biological features essential to the conservation of the Key ring-necked 
                            <PRTPAGE P="62656"/>
                            snake consist of the following components:
                        </P>
                        <P>(i) Pine rocklands habitat that contains:</P>
                        <P>(A) Refugia consisting of a limestone rock substrate with holes, crevices, and shallow depressions; piles of rock rubble; and pockets of organic matter accumulating in solution holes; </P>
                        <P>(B) Suitable prey; </P>
                        <P>(C) Warm, moist microhabitats to maintain homeostasis; and </P>
                        <P>(D) A natural or prescribed fire regime at 5- to 7-year intervals that maintains the pine rocklands habitat and associated plant community. </P>
                        <P>(ii) Rockland hammock habitat that contains:</P>
                        <P>(A) Refugia consisting of a limestone substrate with holes, crevices, and shallow depressions; piles of rock rubble; and pockets of organic matter accumulating in solution holes;</P>
                        <P>(B) Suitable prey;</P>
                        <P>(C) Warm, moist microhabitat to maintain homeostasis; and</P>
                        <P>(D) Little or no fire maintenance.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings, aqueducts, runways, roads, and other paved areas) and the land on which they are located existing within the legal boundaries on [EFFECTIVE DATE OF THE FINAL RULE].</P>
                        <P>
                            (4) Data layers defining map units were created using ESRI ArcGIS mapping software along with various spatial data layers. ArcGIS was also used to calculate the size of habitat areas. The projection used in mapping and calculating distances and locations within the units was Albers Conical Equal Area (Florida Geographic Data Library), North American Datum of 1983 (NAD 1983) High Accuracy Reference Network (HARN). The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/office/florida-ecological-services,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R4-ES-2022-0022, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) Index map follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Key Ring-necked Snake (
                            <E T="03">Diadophis punctatus acricus</E>
                            ) paragraph (5)
                        </FP>
                        <BILCOD>BILLING CODE 4333-15-P</BILCOD>
                        <GPH SPAN="3" DEEP="526">
                            <PRTPAGE P="62657"/>
                            <GID>EP14OC22.052</GID>
                        </GPH>
                        <P>(6) Unit 1: Big Pine Key, Monroe County, Florida.</P>
                        <P>(i) Unit 1 encompasses 1,734 acres (ac) (702 hectares (ha)) north of U.S. 1 within Monroe County, within the lower Florida Keys. The majority of habitat in this unit (1,174 ac (475 ha)) is owned and managed by the Service and associated with the National Key Deer Wildlife Refuge and by the National Park Service; other large tracts are owned by the State of Florida (366 ac (148 ha)). Smaller tracts of habitat are owned by Monroe County, local government, and private entities (194 ac (79 ha)).</P>
                        <P>(ii) Map of Unit 1 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 2 to Key Ring-necked Snake (
                            <E T="03">Diadophis punctatus acricus</E>
                            ) paragraph (6)(ii) 
                        </FP>
                        <GPH SPAN="3" DEEP="552">
                            <PRTPAGE P="62658"/>
                            <GID>EP14OC22.053</GID>
                        </GPH>
                        <P>(7) Unit 2: Middle Torch Key, Monroe County, Florida.</P>
                        <P>(i) Unit 2 encompasses approximately 356 ac (144 ha) north of U.S. 1 and east and west of Middle Torch Road within Monroe County. The State owns a significant portion of the habitat (211 ac (85 ha)), and a smaller portion is owned by both Federal (59 ac (24 ha)) and private entities (86 ac (35 ha)).</P>
                        <P>(ii) Map of Unit 2 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Key Ring-necked Snake (
                            <E T="03">Diadophis punctatus acricus</E>
                            ) paragraph(7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="552">
                            <PRTPAGE P="62659"/>
                            <GID>EP14OC22.054</GID>
                        </GPH>
                        <P>(8) Unit 3: Cudjoe Key, Monroe County, Florida.</P>
                        <P>(i) Unit 3 encompasses five subunits that total approximately 507 ac (205 ha) north of U.S. 1 and east and west of Blimp Road within Monroe County. The majority of the habitat in this unit is owned and managed by the Service and associated with the National Key Deer Wildlife Refuge (332 ac (134 ha)). The remainder of the unit is owned by State, local, and private entities (175 ac (71 ha)).</P>
                        <P>(ii) Map of Unit 3 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Key Ring-necked Snake (
                            <E T="03">Diadophis punctatus acricus</E>
                            ) paragraph (8)(ii) 
                        </FP>
                        <GPH SPAN="3" DEEP="552">
                            <PRTPAGE P="62660"/>
                            <GID>EP14OC22.055</GID>
                        </GPH>
                        <P>(9) Unit 4: Stock Island, Monroe County, Florida.</P>
                        <P>(i) Unit 4 encompasses approximately 8 ac (3 ha) north of U.S. 1 and east of College Road within Monroe County, within the lower Florida Keys. Nearly all habitat in this unit is owned by the City of Key West.</P>
                        <P>(ii) Map of Unit 4 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 5 to Key Ring-necked Snake (
                            <E T="03">Diadophis punctatus acricus</E>
                            ) paragraph (9)(ii) 
                        </FP>
                        <GPH SPAN="3" DEEP="552">
                            <PRTPAGE P="62661"/>
                            <GID>EP14OC22.056</GID>
                        </GPH>
                        <HD SOURCE="HD3">
                            Rim Rock Crowned Snake (
                            <E T="03">Tantilla oolitica</E>
                            )
                        </HD>
                        <P>(1) Critical habitat units are depicted for Miami-Dade and Monroe Counties, Florida, on the maps in this entry.</P>
                        <P>(2) Within these areas, the physical or biological features essential to the conservation of the rim rock crowned snake consist of the following components:</P>
                        <P>(i) Pine rocklands habitat that contains:</P>
                        <P>(A) Refugia consisting of a limestone rock substrate with holes, crevices, and shallow depressions; piles of rock rubble; and pockets of organic matter accumulating in solution holes;</P>
                        <P>(B) Suitable prey;</P>
                        <P>(C) Warm, moist microhabitats to maintain homeostasis; and</P>
                        <P>(D) A natural or prescribed fire regime at 5- to 7-year intervals that maintains the pine rocklands habitat and associated plant community.</P>
                        <P>(ii) Rockland hammock habitat that contains:</P>
                        <P>
                            (A) Refugia consisting of a limestone substrate with holes, crevices, and shallow depressions; piles of rock rubble; and pockets of organic matter accumulating in solution holes;
                            <PRTPAGE P="62662"/>
                        </P>
                        <P>(B) Suitable prey;</P>
                        <P>(C) Warm, moist microhabitat to maintain homeostasis; and</P>
                        <P>(D) Little or no fire maintenance.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings, aqueducts, runways, roads, and other paved areas) and the land on which they are located existing within the legal boundaries on [EFFECTIVE DATE OF THE FINAL RULE].</P>
                        <P>
                            (4) Data layers defining map units were created using ESRI ArcGIS mapping software along with various spatial data layers. ArcGIS was also used to calculate the size of habitat areas. The projection used in mapping and calculating distances and locations within the units was Albers Conical Equal Area (Florida Geographic Data Library), NAD 1983 HARN. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/office/florida-ecological-services,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R4-ES-2022-0022, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) Index map follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Rim Rock Crowned Snake (
                            <E T="03">Tantilla oolitica</E>
                            ) paragraph (5)
                        </FP>
                        <GPH SPAN="3" DEEP="552">
                            <PRTPAGE P="62663"/>
                            <GID>EP14OC22.057</GID>
                        </GPH>
                        <P>(6) Unit 1: Richmond Pine Rocklands, Miami-Dade County, Florida.</P>
                        <P>(i) Unit 1 consists of 819 acres (ac) (331 hectares (ha)) in Miami-Dade County. It is composed of 160 ac (65 ha) of Federal land and 659 ac (267 ha) of County and private lands. This unit is bordered on the north by SW 152 Street (Coral Reef Drive), on the south by SW 200 St (Quail Drive/SR 994), on the east by U.S. 1 (South Dixie Highway), and on the west by SW 177 Avenue (Krome Avenue).</P>
                        <P>(ii) Map of Unit 1 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 2 to Rim Rock Crowned Snake (
                            <E T="03">Tantilla oolitica</E>
                            ) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="551">
                            <PRTPAGE P="62664"/>
                            <GID>EP14OC22.058</GID>
                        </GPH>
                        <P>(7) Unit 2: Deering Estate Complex/Bill Sadowski Park, Miami-Dade County, Florida.</P>
                        <P>(i) Unit 2 consists of 293 ac (119 ha) in Miami-Dade County, including 241 ac (98 ha) of State land, 19 ac (8 ha) of County owned lands, and 31 ac (12 ha) of private lands. The majority of lands within this unit are conserved and managed by the County as Bill Sadowski Park and Deering Estate. The majority of the unit is bordered on the north by Coral Reef Drive, on the west by Old Cutler Road, to the south by Eureka Drive, and to the east by unsuitable habitat within the Deering Estate, which is further bordered by the Biscayne Bay. A small parcel of the Deering Estate included in Unit 2 is located west of Old Cutler Road, and is bordered on the east by SW 7th Avenue and by residential property on the north and south. Bill Sadowski Park, an outparcel of Unit 2, is bordered by Cutler Drain (Canal C-100) on the north, SW 79th Avenue on the west, SW 78th Avenue on the east, and SW 178th Terrace on the south.</P>
                        <P>(ii) Map of Unit 2 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Rim Rock Crowned Snake (
                            <E T="03">Tantilla oolitica</E>
                            ) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="551">
                            <PRTPAGE P="62665"/>
                            <GID>EP14OC22.059</GID>
                        </GPH>
                        <P>(8) Unit 3: Barnacle, Miami-Dade County, Florida.</P>
                        <P>(i) Unit 3 consists of 6 ac (2 ha) in Miami-Dade County, including 3 ac (1 ha) of State land. The remaining acres are local or private ownership. The majority of the unit is within the boundaries of the Barnacle Historic State Park. This unit is bordered by Main Highway on the northwest, Via Abitare Way on the southwest, an unnamed residential road on the northeast, and the Biscayne Bay on the southeast.</P>
                        <P>(ii) Map of Unit 3 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Rim Rock Crowned Snake (
                            <E T="03">Tantilla oolitica</E>
                            ) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="551">
                            <PRTPAGE P="62666"/>
                            <GID>EP14OC22.060</GID>
                        </GPH>
                        <P>(9) Unit 4: Camp Owaissa Bauer, Miami-Dade County, Florida.</P>
                        <P>(i) Unit 4 consists of 96 ac (39 ha) in Miami-Dade County, with 9 ac (4 ha) of State land, 83 ac (34 ha) of County owned lands, and 4 ac (2 ha) of private lands. The majority of the unit is owned by Miami-Dade County and is managed by Miami-Dade County's Environmentally Endangered Lands program. The unit is bordered by State Road 997 on the west and SW 167th Avenue on the east.</P>
                        <P>(ii) Map of Unit 4 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 5 to Rim Rock Crowned Snake (
                            <E T="03">Tantilla oolitica</E>
                            ) paragraph (9)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="551">
                            <PRTPAGE P="62667"/>
                            <GID>EP14OC22.061</GID>
                        </GPH>
                        <P>(10) Unit 5: Navy Wells, Miami-Dade County, Florida.</P>
                        <P>(i) Unit 5 consists of 326 ac (132 ha) in Miami-Dade County. It includes 85 ac (34 ha) of State lands and 240 ac (97 ha) of County owned land. The unit is bordered by State Road 9336 on the east, and Lucille Drive (SW 360th Street) on the south. The majority of the unit is owned by Miami-Dade County, and the State of Florida owns a large tract of land, both of which are managed by Miami-Dade County's Environmentally Endangered Lands program.</P>
                        <P>(ii) Map of Unit 5 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 6 to Rim Rock Crowned Snake (
                            <E T="03">Tantilla oolitica</E>
                            ) paragraph (10)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="551">
                            <PRTPAGE P="62668"/>
                            <GID>EP14OC22.062</GID>
                        </GPH>
                        <P>(11) Unit 6: North Key Largo, Monroe County, Florida.</P>
                        <P>(i) Unit 6 consists of 2,161 ac (875 ha) in Monroe County, Florida, in the upper Florida Keys. This unit is surrounded by the Atlantic Ocean to the east and the Florida Bay to the west. The unit is bisected by County Road 905 and U.S. Highway 1, which runs in a northeast to southwest direction in the center of North Key Largo south to Key Largo. It consists of 601 ac (243 ha) of Federal lands, 1,484 ac (601 ha) of State lands, 24 ac (9 ha) of locally owned lands, and 53 ac (21 ha) of private lands. The majority of Federal land in this unit is owned and managed by the Service and associated with Crocodile Lake National Wildlife Refuge.</P>
                        <P>(ii) Map of Unit 6 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 7 to Rim Rock Crowned Snake (
                            <E T="03">Tantilla oolitica</E>
                            ) paragraph (11)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="551">
                            <PRTPAGE P="62669"/>
                            <GID>EP14OC22.063</GID>
                        </GPH>
                        <P>(12) Unit 7: Key Largo, Monroe County, Florida.</P>
                        <P>(i) Unit 7 consists of 298 ac (121 ha) in Monroe County, Florida, in the upper Florida Keys. This unit is bordered by U.S. Highway 1 on the northwest. It consists of 151 ac (40 ha) of State lands, 56 ac (23 ha) of County/local government owned lands, and 91 ac (37 ha) of private lands. The majority of habitat consists of habitat owned by private entities and the State of Florida (John Pennekamp Coral Reef State Park).</P>
                        <P>(ii) Map of Unit 7 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 8 to Rim Rock Crowned Snake (
                            <E T="03">Tantilla oolitica</E>
                            ) paragraph (12)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="551">
                            <PRTPAGE P="62670"/>
                            <GID>EP14OC22.064</GID>
                        </GPH>
                        <P>(13) Unit 8: Tavernier, Monroe County, Florida.</P>
                        <P>(i) Unit 8 consists of 181 ac (73 ha) in Monroe County, Florida, in the upper Florida Keys. The majority of the unit is bordered by U.S. Highway 1 on the northwest, and Peace Avenue on the north. Two outparcels are bordered by U.S. Highway 1 on the southeast. Located within Monroe County and part of the city of Tavernier, within the upper Florida Keys islands, the habitat in this unit is surrounded and/or fragmented by suburban and urban development, canals, and two-lane roads. It consists of 98 ac (40 ha) of State lands, 30 ac (12 ha) of County/local government owned lands, and 54 ac (22 ha) of private lands.</P>
                        <P>(ii) Map of Unit 8 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 9 to Rim Rock Crowned Snake (
                            <E T="03">Tantilla oolitica</E>
                            ) paragraph (13)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="551">
                            <PRTPAGE P="62671"/>
                            <GID>EP14OC22.065</GID>
                        </GPH>
                        <P>(14) Unit 9: Vaca Key, Monroe County, Florida.</P>
                        <P>(i) Unit 9 consists of 59 ac (24 ha) of habitat in Monroe County, Florida, in the upper Florida Keys. This unit is bordered by U.S. Highway on the south. It is composed of 58 ac (23.5 ha) of privately owned land, and 1 ac (0.4 ha) of lands owned by County/local government.</P>
                        <P>(ii) Map of Unit 9 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 10 to Rim Rock Crowned Snake (
                            <E T="03">Tantilla oolitica</E>
                            ) paragraph (14)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="551">
                            <PRTPAGE P="62672"/>
                            <GID>EP14OC22.066</GID>
                        </GPH>
                        <P>(15) Unit 10: Big Pine Key, Monroe County, Florida.</P>
                        <P>(i) Unit 10 consists of 1,729 ac (700 ha) in Monroe County, Florida, in the lower Florida Keys. This unit is bordered by U.S. Highway 1 on the south. It consists of 1,200 ac (486 ha) of Federal land, 380 ac (154 ha) of State lands, 71 ac (29 ha) of locally owned lands, and 77 ac (31 ha) of private lands. The majority of this unit is owned and managed by the Service and associated with the National Key Deer Wildlife Refuge.</P>
                        <P>(ii) Map of Unit 10 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 11 to Rim Rock Crowned Snake (
                            <E T="03">Tantilla oolitica</E>
                            ) paragraph (15)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="552">
                            <PRTPAGE P="62673"/>
                            <GID>EP14OC22.067</GID>
                        </GPH>
                        <P>(16) Unit 11: Key West, Monroe County, Florida.</P>
                        <P>(i) Unit 11 consists of 9 ac (4 ha) in Monroe County, Florida, in the lower Florida Keys. Large resorts and hotels are located to the east and the Key West International Airport is located to the south of this unit. It consists of 5 ac (2 ha) of local/County-owned land and 3 ac (1 ha) of private land.</P>
                        <P>(ii) Map of Unit 11 follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 12 to Rim Rock Crowned Snake (
                            <E T="03">Tantilla oolitica</E>
                            ) paragraph (16)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="552">
                            <PRTPAGE P="62674"/>
                            <GID>EP14OC22.068</GID>
                        </GPH>
                        <STARS/>
                    </SECTION>
                    <SIG>
                        <NAME>Martha Williams,</NAME>
                        <TITLE>Director, U.S. Fish and Wildlife Service.</TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 2022-21543 Filed 10-13-22; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 4333-15-C</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>87</VOL>
    <NO>198</NO>
    <DATE>Friday, October 14, 2022</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="62675"/>
            <PARTNO>Part V</PARTNO>
            <AGENCY TYPE="P">Department of Commerce</AGENCY>
            <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
            <HRULE/>
            <CFR>50 CFR Part 660</CFR>
            <TITLE>Magnuson-Stevens Act Provisions; Fisheries Off West Coast States; Pacific Coast Groundfish Fishery; Pacific Coast Groundfish Fishery Management Plan; Amendment 30; 2023-24 Biennial Specifications and Management Measure; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="62676"/>
                    <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                    <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                    <CFR>50 CFR Part 660</CFR>
                    <DEPDOC>[Docket No. 220915-0191]</DEPDOC>
                    <RIN>RIN 0648-BL48</RIN>
                    <SUBJECT>Magnuson-Stevens Act Provisions; Fisheries Off West Coast States; Pacific Coast Groundfish Fishery; Pacific Coast Groundfish Fishery Management Plan; Amendment 30; 2023-24 Biennial Specifications and Management Measures</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; notice of availability of a draft environmental assessment; request for comments.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>This proposed rule would establish the 2023-24 harvest specifications for groundfish caught in the U.S. exclusive economic zone seaward of Washington, Oregon, and California, consistent with the Magnuson-Stevens Fishery Conservation and Management Act and the Pacific Coast Groundfish Fishery Management Plan. This proposed rule would also revise management measures intended to keep the total annual catch of each groundfish stock or stock complex within the annual catch limits. These proposed measures are intended to help prevent overfishing, rebuild overfished stocks, achieve optimum yield, and ensure management measures are based on the best scientific information available. This proposed rule would also make minor corrections to the regulations. Additionally, this proposed rule announces the receipt of exempted fishing permit applications. NMFS has made a preliminary determination that these applications warrant further consideration. NMFS requests public comment on these applications. This action also would implement portions of Amendment 30 to the Pacific Coast Groundfish Fishery Management Plan, which would specify a shortbelly rockfish catch threshold to initiate Council review; extend the length of the limited entry fixed gear sablefish primary season; change the use of Rockfish Conservation Area boundaries; expand the use of Block Area Closures to control catch of groundfish; and correct the definition of Block Area Closures. In accordance with the National Environmental Policy Act of 1969, as amended, NMFS also announces the availability of a draft environmental assessment that analyzes the potential effects of the associated proposed rule.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>Comments must be received no later than November 14, 2022.</P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>Submit your comments on the proposed rule, draft environmental assessment, and exempted fishing permit applications, identified by NOAA-NMFS-2022-0080, by the following method:</P>
                        <P>
                            • 
                            <E T="03">Electronic Submissions:</E>
                             Submit all electronic public comments via the Federal e-Rulemaking Portal. Go to 
                            <E T="03">www.regulations.gov</E>
                             and enter NOAA-NMFS-2022-0080 in the Search box. Click the “Comment” icon, complete the required fields, and enter or attach your comments. The exempted fishing permit (EFP) applications will be available under Supporting Documents through the same link.
                        </P>
                        <P>
                            <E T="03">Instructions:</E>
                             Comments must be submitted by the above method to ensure that the comments are received, documented, and considered by NMFS. Comments sent by any other method, to any other address or individual, or received after the end of the comment period, may not be considered. All comments received are a part of the public record and NMFS will post 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 is publicly accessible. NMFS will accept anonymous comments (enter “N/A” in the required fields if you wish to remain anonymous). Please specify whether the comments provided are associated with the proposed rule, draft environmental assessment, or EFP applications.
                        </P>
                    </ADD>
                    <HD SOURCE="HD1">Electronic Access</HD>
                    <P>
                        This rule is accessible via the internet at the Office of the Federal Register website at 
                        <E T="03">https://www.federalregister.gov/.</E>
                         The draft Environmental Assessment (EA) which addresses the National Environmental Policy Act, Presidential Executive Order 12866, and the Regulatory Flexibility Act, is accessible via the internet at the NMFS West Coast Region website at 
                        <E T="03">https://www.fisheries.noaa.gov/region/west-coast.</E>
                         Background information and documents including an analysis for this action (Analysis), which addresses the statutory requirements of the Magnuson Stevens Fishery Conservation and Management Act (Magnuson-Stevens Act) are available from the Pacific Fishery Management Council's website at 
                        <E T="03">https://www.pcouncil.org.</E>
                         The final 2022 Stock Assessment and Fishery Evaluation (SAFE) report for Pacific Coast groundfish, as well as the SAFE reports for previous years, are available from the Pacific Fishery Management Council's website at 
                        <E T="03">https://www.pcouncil.org.</E>
                    </P>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            Brian Hooper, Fishery Management Specialist, at 206-526-6117 or 
                            <E T="03">brian.hooper@noaa.gov.</E>
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P/>
                    <HD SOURCE="HD1">I. Background</HD>
                    <P>Chapter 5 of the Pacific Coast Groundfish Fishery Management Plan (PCGFMP) requires the Pacific Fishery Management Council (Council) to assess the biological, social, and economic conditions of the Pacific coast groundfish fishery and use this information to develop harvest specifications and management measures at least biennially. This proposed rule is based on the Council's final recommendations for harvest specifications and management measures for the 2023-24 biennium made at its April and June 2022 meetings.</P>
                    <P>The Council deemed the proposed regulations necessary and appropriate to implement these actions in an August 29, 2022, letter from Council Executive Director, Merrick Burden, to Acting Regional Administrator Scott Rumsey. Under the Magnuson-Stevens Act, NMFS is required to publish proposed rules for comment after preliminarily determining whether they are consistent with applicable law. We are seeking comment on the proposed regulations in this action and whether they are consistent with the PCGFMP, the Magnuson-Stevens Act and its National Standards, and other applicable law.</P>
                    <P>
                        Concurrent with this proposed rule, NMFS also published a Notice of Availability (NOA) to announce the proposed Amendment 30 to the PCGFMP. The NOA requests public review and comment on proposed changes to the Council fishery management plan document (87 FR 54445; September 6, 2022). Public comments are being solicited on the amendment through November 7, 2022, the end of the comment period for the NOA. Public comments on the proposed rule must be received by the end of the comment period on the Amendment, as published in the NOA, to be considered in the approval/disapproval decision on the Amendment. All comments received by the end of the comment period on the amendment, whether specifically directed to the Amendment, or the proposed rule, will be considered in the 
                        <PRTPAGE P="62677"/>
                        approval/disapproval decision. Comments received after that date will not be considered in the approval/disapproval decision on the amendment. To be considered, comments must be received by close of business on the last day of the comment period; that does not mean postmarked or otherwise transmitted by that date.
                    </P>
                    <P>An action included in this proposed rule would affect the season dates for the retention of incidentally caught halibut in the sablefish primary fishery north of Point Chehalis. The Northern Pacific Halibut Act of 1982 (Halibut Act), 16 U.S.C. 773-773k, gives the Secretary of Commerce (Secretary) responsibility for implementing the provisions of the Convention between Canada and the United States for the Preservation of the Halibut Fishery of the North Pacific Ocean and Bering Sea (Halibut Convention), signed at Ottawa, Ontario, on March 2, 1953, as amended by a Protocol Amending the Convention (signed at Washington, DC, on March 29, 1979). The Halibut Act requires that the Secretary adopt regulations to carry out the purposes and objectives of the Halibut Convention and Halibut Act (16 U.S.C. 773c). Additionally, as provided in the Halibut Act, the Regional Fishery Management Councils having authority for the geographic area concerned may develop, and the Secretary of Commerce may implement, regulations governing harvesting privileges among U.S. fishermen in U.S. waters that are in addition to, and not in conflict with, approved International Pacific Halibut Commission (IPHC) regulations (16 U.S.C. 773c(c)).</P>
                    <HD SOURCE="HD2">A. Specification and Management Measure Development Process</HD>
                    <P>
                        In 2021, the Northwest Fisheries Science Center (NWFSC) conducted full stock assessments for Dover sole, lingcod, vermilion rockfish/sunset rockfish, and spiny dogfish. The NWFSC conducted data moderate assessments for copper rockfish, quillback rockfish, and squarespot rockfish off California. The NWFSC conducted an update assessment of sablefish. Additionally, the NWFSC reviewed catch-only assessment updates for a number of previously assessed stocks (arrowtooth flounder, petrale sole, canary rockfish and darkblotched rockfish), as well as a new yelloweye rockfish catch report. The NWFSC did not update assessments for the remaining stocks, so harvest specifications for these stocks are based on assessments from previous years. The full stock assessments used to set catch limits for this biennium are available on the Council's website (
                        <E T="03">https://www.pcouncil.org/</E>
                        ).
                    </P>
                    <P>The Council's stock assessment review panel (STAR panel) reviewed the stock assessments, including assessments on stocks for which some biological indicators are available, as described below, for technical merit, and to determine that each stock assessment document was sufficiently complete. Finally, the Council's Scientific and Statistical Committee (SSC) reviewed the stock assessments and STAR panel reports and made its recommendations to the Council (Agenda Item G.5, June 2021 Council meeting; Agenda Item C.6, September 2021 Council Meeting; Agenda Item E.2, November 2021 Council Meeting).</P>
                    <P>
                        The Council considered the new stock assessments, stock assessment updates, catch-only updates, public comment, recommendations from the SSC, and advice from its advisory bodies over the course of six Council meetings during development of its recommendations for the 2023-24 harvest specifications and management measures. At each Council meeting between June 2021 and June 2022, the Council made a series of decisions and recommendations that were, in some cases, refined after further analysis and discussion. Agenda Item G.6, Supplemental Revised Attachment 1, June 2021 describes the Council's meeting schedule for developing the 2023-24 biennial harvest specifications. Additionally, detailed information, including the supporting documentation the Council considered at each meeting, is available at the Council's website, 
                        <E T="03">www.pcouncil.org.</E>
                    </P>
                    <P>
                        The 2023-24 biennial management cycle was the fourth cycle following PCGFMP Amendment 24 (80 FR 12567, March 10, 2015), which established default harvest control rules and was analyzed through an Environmental Impact Statement (EIS) (Final Environmental Impact Statement for Pacific Coast Groundfish Harvest Specifications and Management Measures for 2015-2016 and Biennial Periods Thereafter, and Amendment 24 to the PCGFMP, published January 2015). The EIS described the ongoing implementation of the PCGFMP and default harvest control rules. Under Amendment 24, the default harvest control rules used to determine the previous biennium's harvest specifications (
                        <E T="03">i.e.,</E>
                         overfishing limits (OFLs), acceptable biological catches (ABCs), and annual catch limits (ACLs)) are applied automatically to the best scientific information available to determine the future biennium's harvest specifications. NMFS implements harvest specifications based on the default harvest control rules used in the previous biennium unless the Council makes a recommendation to deviate from the default. Therefore, this rule implements the default harvest control rules, consistent with the last biennium (2021-22), for most stocks, and discusses Council-recommended departures from the defaults. The draft EA supporting this action identifies the preferred harvest control rules, management measures, and other management changes that were not described in the 2015 EIS, and will be posted on the NMFS West Coast Region webpage (see Electronic Access).
                    </P>
                    <P>Information regarding the OFLs, ABCs, and ACLs proposed for groundfish stocks and stock complexes in 2023-24 is presented below, followed by a discussion of the proposed management measures for commercial and recreational groundfish fisheries.</P>
                    <HD SOURCE="HD1">II. Proposed Harvest Specifications</HD>
                    <P>This proposed rule would set 2023-24 harvest specifications and management measures for 127 of the 128 groundfish stocks or management units which currently have ACLs or ACL contributions to stock complexes managed under the PCGFMP, except for Pacific whiting. Pacific whiting harvest specifications are established annually through a separate bilateral process with Canada.</P>
                    <P>
                        The proposed OFLs, ABCs, and ACLs are based on the best available biological and socioeconomic data, including projected biomass trends, information on assumed distribution of stock biomass, and revised technical methods used to calculate stock biomass. The PCGFMP specifies a series of three stock categories for the purpose of setting maximum sustainable yield (MSY),
                        <SU>1</SU>
                        <FTREF/>
                         OFLs, ABCs, ACLs, and rebuilding standards. Category one represents the highest level of information quality available, while category three represents the lowest. Category one stocks are the relatively few stocks for which the NWFSC can conduct a “data rich” quantitative stock assessment that incorporates catch-at-age, catch-at-length, or other data. The SSC can generally calculate OFLs and overfished/rebuilding thresholds for these stocks, as well as ABCs, based on the uncertainty of the biomass estimated within an assessment or the variance in biomass estimates between assessments for all stocks in this category. The set of category two stocks includes a large number of stocks for which some 
                        <PRTPAGE P="62678"/>
                        biological indicators are available, yet status is based on a “data-moderate” quantitative stock assessment. The category three stocks include minor stocks which are caught, but for which there is, at best, only information on landed biomass. For stocks in this category, there is limited data available for the SSC to quantitatively determine MSY, OFL, or an overfished threshold. Typically, catch-based methods (
                        <E T="03">e.g.,</E>
                         depletion-based stock reduction analysis, depletion corrected average catch, and average catches) are used to determine the OFL for category three stocks. A detailed description of each of these categories can be found in Section 4.2 of the PCGFMP.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             MSY is the largest long-term average catch that can be taken from a fish stock under prevailing environmental and fishery conditions.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">A. Proposed OFLs for 2023 and 2024</HD>
                    <P>
                        The OFL serves as the maximum amount of fish that can be caught in a year without resulting in overfishing. Overfishing occurs when a stock has a harvest rate, denoted as F
                        <E T="52">x</E>
                        <E T="0112">%</E>
                        , is set higher than the rate that produces the stock's MSY. The SSC derives OFLs for groundfish stocks with stock assessments by applying the harvest rate to the current estimated biomass (B). Harvest rates represent the rates of fishing mortality (F) that will reduce the female spawning potential ratio (SPR) to X percent of its unfished level. As an example, a harvest rate of F
                        <E T="52">40</E>
                        <E T="0112">%</E>
                         is more aggressive than F
                        <E T="52">45</E>
                        <E T="0112">%</E>
                         or F
                        <E T="52">50</E>
                        <E T="0112">%</E>
                         harvest rates because F
                        <E T="52">40</E>
                        <E T="0112">%</E>
                         allows more fishing mortality on a stock (as it allows a harvest rate that would reduce the stock to 40 percent of its unfished level). The OFL does not account for scientific or management uncertainty, so the SSC typically recommends an ABC that is lower than the OFL in order to account for this uncertainty. Usually, the greater the amount of scientific uncertainty, the lower the ABC is set compared to the OFL.
                    </P>
                    <P>
                        For 2023-24, the Council maintained its policy of using a default harvest rate as a proxy for the fishing mortality rate that is expected to achieve F
                        <E T="52">MSY</E>
                        . The Council also maintained the same default harvest rate proxies as used in the 2021-22 biennium, based on the SSC's recommendations: F
                        <E T="52">30</E>
                        <E T="0112">%</E>
                         for flatfish (meaning an SPR harvest rate that would reduce the stock to 30 percent of its unfished level), F
                        <E T="52">50</E>
                        <E T="0112">%</E>
                         for rockfish (including longspine and shortspine thornyheads), F
                        <E T="52">50</E>
                        <E T="0112">%</E>
                         for elasmobranchs, and F
                        <E T="52">45</E>
                        <E T="0112">%</E>
                         for other groundfish such as sablefish and lingcod. For unassessed stocks, the Council recommended using a historical catch-based approach (
                        <E T="03">e.g.,</E>
                         average catch, depletion-corrected average catch, or depletion-based stock reduction analysis) to set the OFL. See Tables 1a and 2a to Part 660, Subpart C in the proposed regulatory text supporting this rule for the proposed 2023-24 OFLs.
                    </P>
                    <P>
                        The SAFE document for 2022, includes a detailed description of the scientific basis for all of the SSC-recommended OFLs proposed in this rule, and is available at the Council's website, 
                        <E T="03">www.pcouncil.org.</E>
                    </P>
                    <HD SOURCE="HD2">B. Proposed ABCs for 2023 and 2024</HD>
                    <P>The ABC is the stock or stock complex's OFL reduced by an amount associated with scientific uncertainty. The SSC-recommended P star-sigma approach determines the amount by which the OFL is reduced to account for this uncertainty. Under this approach, the SSC recommends a sigma (σ) value. The σ value is generally based on the scientific uncertainty in the biomass estimates generated from stock assessments and is usually related to the stock category. After the SSC determines the appropriate σ value, the Council chooses a P star (P*) based on its chosen level of risk aversion to address the consequences of the stock being elsewhere within the uncertainty represented by sigma.</P>
                    <P>A P* of 0.5 equates to no additional reduction beyond the σ value reduction. The PCGFMP specifies the upper limit of P* will be 0.45. The P*-sigma approach is discussed in detail in the proposed and final rules for the 2011-12 (75 FR 67810, November 3, 2010; 76 FR 27508, May 11, 2011) and 2013-14 (77 FR 67974, November 12, 2012; 78 FR 580, January 3, 2013) biennial harvest specifications and management measures.</P>
                    <P>The SSC quantified major sources of scientific uncertainty in the estimates of OFLs and generally recommended a σ value of 0.5 for category one stocks, a σ value of 1.0 for category two stocks, and a σ value of 2.0 for category three stocks. For category two and three stocks, there is greater scientific uncertainty in the OFL estimate because the assessments for these stocks are informed by less data than the assessments for category one stocks. Therefore, the scientific uncertainty buffer is generally greater than that recommended for stocks with data-rich stock assessments. Assuming the same P* is applied, a larger σ value results in a larger reduction from the OFL. For 2023-24, the Council continued the general policy of using the SSC-recommended σ values for each stock category.</P>
                    <P>For 2023-24, the Council maintained the P* policies it established for the previous biennium for most stocks, except when calculating the contribution of black rockfish to the Oregon blue/deacon/black rockfish complex. The Council considered alternative P* values for lingcod south of 40°0′ N lat., lingcod north of 40°10′ N lat., sablefish, spiny dogfish, vermilion and sunset rockfishes south of 4010′ N lat., and vermilion and sunset rockfishes north of 40°0′ N lat., but ultimately decided to maintain the default P* value used in the previous biennium. The Council recommended using P* values of 0.45 for all individually managed category one stocks, except yelloweye rockfish. Combining the category one σ value of 0.5 with the P* value of 0.45 results in a reduction of 6.1 percent from the OFL when deriving the ABC. For category two stocks, the Council's general policy was to apply a P* of 0.4, with a few exceptions. The Council recommended applying a P* of 0.45 for big skate, English sole, lingcod south of 40°10′ N lat., lingcod north of 40°10′ N lat., longnose skate, Pacific ocean perch, and all of the stocks managed in the Oregon blue/deacon/black rockfish complex, Nearshore Rockfish complexes, Shelf Rockfish Complexes, Slope Rockfish complexes, and the Other Fish complex. When combined with the σ values of 1.00 for category two, a P* value of 0.45 corresponds to an 11.8 percent reduction and a P* value of 0.40 corresponds to a 22.4 percent reduction. For category three stocks, the Council's general policy was to apply a P* value of 0.45 for these stocks, except the Council recommended a P* value of 0.40 for cowcod between 40°10′ N lat. and 34°27′ N lat., Pacific cod, starry flounder, and all stocks in the Other Flatfish complex. When combined with the σ values of 2.00 for category three, a P* value of 0.45 corresponds to 22.2 percent reduction and a P* value of 0.40 corresponds to a 39.8 percent reduction. See Table 1-3 of Agenda F.3, Supplemental Revised Attachment 1, April 2022 Council meeting for the full description of σ and P* values by stock. See Tables 1a and 2a to Part 660, Subpart C in the in the proposed regulatory text of this proposed rule for the proposed 2023-24 ABCs.</P>
                    <HD SOURCE="HD2">C. Proposed ACLs for 2023 and 2024</HD>
                    <P>
                        The Council recommends ACLs for each groundfish stock or management unit as defined in the PCGFMP. To determine the ACL for each stock, the Council will determine the best estimate of current stock abundance and its relation to the precautionary and overfished/rebuilding thresholds. Under the PCGFMP, the biomass level that produces MSY, or B
                        <E T="52">MSY</E>
                        , is defined as the precautionary threshold. When the biomass for an assessed category one or 
                        <PRTPAGE P="62679"/>
                        two stock falls below B
                        <E T="52">MSY</E>
                        , the ACL is set below the ABC using a harvest rate reduction to help the stock return to the B
                        <E T="52">MSY</E>
                         level, which is the management target for groundfish stocks. If a stock biomass is larger than B
                        <E T="52">MSY</E>
                        , the ACL may be set equal to the ABC, or the ACL may be set below the ABC to address conservation objectives, socioeconomic concerns, management uncertainty, or other factors necessary to meet management objectives. The overfished/rebuilding threshold is 25 percent of the estimated unfished biomass level for non-flatfish stocks or 50 percent of B
                        <E T="52">MSY</E>
                        , if known. The overfishing/rebuilding threshold for flatfish stocks is 12.5 percent of the estimated unfished biomass level. When a stock is below B
                        <E T="52">MSY</E>
                         (the precautionary threshold) but above the overfishing/rebuilding threshold, it is considered to be in the precautionary zone.
                    </P>
                    <P>Under PCGFMP Amendment 24, the Council set up default harvest control rules, which established default policies that would be applied to the best available scientific information to set ACLs each biennial cycle, unless the Council has reasons to diverge from that harvest control rule. A complete description of the default harvest control rules for setting ACLs is described in the proposed and final rule for the 2015-16 harvest specifications and management measures and PCGFMP Amendment 24 (80 FR 687, January 6, 2015; 80 FR 12567, March 10, 2015).</P>
                    <P>
                        The PCGFMP defines the 40-10 harvest control rule for stocks with a B
                        <E T="52">MSY</E>
                         proxy of B
                        <E T="52">40</E>
                        <E T="0112">%</E>
                         that are in the precautionary zone as the standard reduction. The analogous harvest control rule with the standard reduction for assessed flatfish stocks is the 25-5 harvest control rule for flatfish stocks with a B
                        <E T="52">MSY</E>
                         proxy of B
                        <E T="52">25</E>
                        <E T="0112">%</E>
                        . The further the stock biomass is below the precautionary threshold, the greater the reduction in ACL relative to the ABC, until at B
                        <E T="52">10</E>
                        <E T="0112">%</E>
                         for a stock with a B
                        <E T="52">MSY</E>
                         proxy of B
                        <E T="52">40</E>
                        <E T="0112">%</E>
                        , or B
                        <E T="52">5</E>
                        <E T="0112">%</E>
                         for a stock with a B
                        <E T="52">MSY</E>
                         proxy of B
                        <E T="52">25</E>
                        <E T="0112">%</E>
                        , the ACL would be set at zero.
                    </P>
                    <P>Under the PCGFMP, harvest control rules are typically applied at the component species level for stock complexes to calculate ACLs. Resulting contribution values of each component species, or ACL contributions, are summed to equal the stock complex ACLs. For example the ACL contributions of black rockfish off of Oregon and quillback rockfish contribute to the overall ACL for Oregon black/deacon/blue rockfish stock complex and the Nearshore Rockfish complexes respectively.</P>
                    <P>Under the PCGFMP, the Council may recommend setting the ACL at a different level than what the default harvest control rules specify as long as the ACL does not exceed the ABC and complies with the requirements of the Magnuson-Stevens Act (see the Analysis for information on the Magnuson-Stevens Act). For most of the stocks and stock complexes managed with harvest specifications for 2023-24, the Council chose to maintain the default harvest control rules from the previous biennial cycle. For the Oregon black/deacon/blue rockfish stock complex and the Nearshore Rockfish complexes, the Council recommended deviating from the default harvest control rule by changing how the contribution of black rockfish off of Oregon and quillback rockfish off of California are calculated. Table 1 presents a summary table of the proposed changes to default harvest control rules for certain stocks for 2023-24. Each of these changes is discussed further below.</P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,r50,r100,r100">
                        <TTITLE>Table 1—Proposed Changes to Harvest Control Rules for 2023-24</TTITLE>
                        <BOXHD>
                            <CHED H="1">
                                Stock complex
                                <LI>component</LI>
                            </CHED>
                            <CHED H="1">Alternative</CHED>
                            <CHED H="1">Harvest control rule</CHED>
                            <CHED H="1">
                                ACL contribution to stock complex 
                                <SU>a</SU>
                                 
                                <SU>b</SU>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Black Rockfish off of Oregon</ENT>
                            <ENT>Default</ENT>
                            <ENT>ACL contribution = ABC (P* = 0.45)</ENT>
                            <ENT>477 mt (2023), 471 mt (2024).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Proposed change</ENT>
                            <ENT>ACL contribution = 2020 ABC</ENT>
                            <ENT>512 mt (2023), 512 mt (2024).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Quillback Rockfish off of California</ENT>
                            <ENT>Default</ENT>
                            <ENT>
                                ACL contribution &lt; ABC with the 40-10 adjustment 
                                <SU>c</SU>
                                 off California only (P* = 0.45)
                            </ENT>
                            <ENT>2023 statewide ACL contribution = 0.11 mt; 2024 statewide ACL contribution = 0.42 mt.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Proposed change</ENT>
                            <ENT>ACL contribution &lt; ABC (SPR 0.55; P* 0.45)</ENT>
                            <ENT>2023 statewide ACL contribution = 1.76 mt; 2024 statewide ACL contribution = 1.93 mt.</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>a</SU>
                             Default ACL is for 2023 and 2024 under the default harvest control rule, Proposed change ACL is for 2023 and 2024 under the alternative harvest specifications.
                        </TNOTE>
                        <TNOTE>
                            <SU>b</SU>
                             The ACL contribution for quillback rockfish off of California are apportioned to create the ACL contributions to the nearshore rockfish complexes north and south of 40° 10′ N lat. The apportionment was determined by the proportion of catch between 2005 and 2020 north and south of 40°10′ N lat. in California where 49.6 percent of the statewide ACL is apportioned to the area between 42° and 40°10′ N lat. for the California contribution to the northern complex, and 50.4 percent to the area south of 40°10′ N lat. for the contribution to the southern complex.
                        </TNOTE>
                        <TNOTE>
                            <SU>c</SU>
                             The 40-10 adjustment is applied to only some component species when calculating the complex ACL, where a precautionary reduction is warranted, per the PCGFMP at section 4.6.1. The 40-10 adjustment reduces the harvest rate to help the stock return to the maximum sustainable yield level.
                        </TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD3">Oregon Black Rockfish</HD>
                    <P>Oregon black rockfish is a category two stock, managed as part of the Oregon blue/deacon/black rockfish complex. Oregon black rockfish was first assessed as a single stock in 2015. In 2019, the Oregon black rockfish stock was estimated to be at 56 percent of its unfished spawning output. For 2021-22, the NWFSC conducted a catch-only update to the 2015 assessment by adding realized catch data from 2015-2018 and estimates of catch for 2019 and 2020. For 2021-2022, the Council recommended and NMFS approved a departure from the default harvest control rule on a case-specific basis to adopt an ABC for both years equal to the 2020 value (512 metric tons). The intent of the departure was to provide fishery stability, without significantly affecting stock status.</P>
                    <P>
                        Black rockfish is the primary target stock for nearshore recreational and commercial fisheries in Oregon and attainment of the ACL contribution is high. In 2017, Oregon recreational fisheries were shut down early because of black rockfish concerns, and the Council received public testimony as to the severe negative consequences for charter business operators and tourist-revenue dependent coastal communities resulting from this closure. Due to the constraining nature of black rockfish in Oregon and the biomass level being above the precautionary threshold, the Oregon Department of Fish and Wildlife (ODFW) recommended an alternative harvest control rule where the 2020 ABC of 512 mt is specified in 2023 and 2024, and the ACL contributions are set equal to ABCs. The Magnuson-Stevens Act and the PCGFMP allow the SSC to recommend an ABC that differs from the 
                        <PRTPAGE P="62680"/>
                        ABC control rule on a case by case basis, provided the SSC offers justification for its recommended deviation. In 2025, the current default harvest control rule (ABC=ACL, P* of 0.45) would once again apply to Oregon black rockfish.
                    </P>
                    <P>Catch-only projections for black rockfish (Agenda Item E.3, Attachment 3, November 2021) were completed for two scenarios that differed according to the timeframe for which ABCs/ACL contributions of 512 mt were assumed (2021-2022 vs 2021-2024). For both scenarios, previously assumed catch projections for 2019 and 2020 were replaced with the lower observed catches for those years. Under both scenarios, the long-term projections result in a projected stock biomass at 54 percent of its unfished spawning output in 2032. Stocks with biomass estimates greater than 40 percent depletion are above the precautionary thresholds in the PCGFMP. Because the biomass is the same under either scenario, the SSC endorsed this alternative harvest control rule for use in 2023-24.</P>
                    <P>Therefore based on the Analysis, the Council has recommended and NMFS is proposing alternative harvest specifications for black rockfish off of Oregon as part of the Oregon blue/deacon/black rockfish complex. The alternative harvest control rule would implement an ACL for the 2023 and 2024 biennium of 512 mt in each year. This ACL contributes to the overall stock complex ACL.</P>
                    <HD SOURCE="HD3">Quillback Rockfish Off California</HD>
                    <P>
                        Quillback rockfish is managed as part of the Nearshore Rockfish complexes north and south of 40°10′ N lat. Quillback rockfish was assessed in 2021 (Agenda Item E.2, Attachment 4, November 2021). Due to differences in data availability and fishery exploitation, the quillback rockfish assessment split the species into three separate assessment areas by state boundary line. For purposes of stock status determination (
                        <E T="03">i.e.,</E>
                         whether the stock or stock complex is subject to overfishing or overfished), the assessments were combined to reflect (1) the status of quillback rockfish as a part of the nearshore rockfish complexes and (2) that quillback rockfish off California are not a stock defined separately from quillback rockfish off Oregon and Washington. However, the individual assessment areas suggested differences in abundance and potential localized depletion, which are addressed through this action as described below. The assessment for the portion of quillback rockfish off California indicated that portion is depleted.
                    </P>
                    <P>
                        The Council recommended, and NMFS proposes, applying the default harvest control rule, P* 0.45, for quillback rockfish off of Washington and Oregon. Under the default harvest control rule for the portion quillback rockfish off of California, a precautionary adjustment (
                        <E T="03">i.e.,</E>
                         the 40-10 adjustment) would be applied. However, the Council anticipated scientific information about the population dynamics of the various stocks would improve over time. This information would result in improved estimates of appropriate harvest rates and the default values from the 40-10 adjustment could be replaced. In response to the best available scientific information related to the depletion specific to the portion of quillback rockfish off California estimated in the assessment, the Council recommended additional steps to reduce mortality in that assessment area. The Council considered a range of alternative harvest control rules for the portion of quillback rockfish off California based on the January 2022 draft rebuilding analysis which is available at 
                        <E T="03">https://www.pcouncil.org/stock-assessments-star-reports-stat-reports-rebuilding-analyses-terms-of-reference/groundfish-stock-assessment-documents/.</E>
                         The Council's SSC endorsed the rebuilding analysis for use in management, with which the alternative harvest control rules are consistent. However, as noted above, because for status determination purposes in the 2023-2024 biennium, quillback rockfish off California are not a stock defined separately from quillback rockfish off Oregon and Washington and are part of a stock complex. NMFS has not determined that any stock or stock complex is overfished and development of a rebuilding plan is not required.
                    </P>
                    <P>The Council recommended setting the California statewide ACL contribution of quillback rockfish to the complexes below the statewide ABC contribution of quillback rockfish to the complexes to allow the spawning output of quillback rockfish in this assessment area to increase toward the management target. The statewide harvest specifications were then apportioned to create the ACL contributions to the nearshore rockfish complexes north and south of 40°10′ N lat. The apportionment was determined by the proportion of catch between 2005 and 2020 north and south of 40°10′ N lat. in California where 49.6 percent of the statewide ACL is apportioned to the area between 42° and 40°10′ N lat. for the California contribution to the northern complex, and 50.4 percent to the area south of 40°10′ N lat. for the contribution to the southern complex. The California statewide ACL was used to inform the Council's recommendation on harvest specifications for the nearshore rockfish complexes, and precautionary management measures for quillback rockfish (see Sections III.G, III.M, and III.N).</P>
                    <P>Therefore, based on the best scientific information available as detailed in the Analysis and Agenda Item F.6.a Supplemental Groundfish Management Team Report 2, June 2022, the Council has recommended, and NMFS is proposing, alternative harvest specifications for quillback rockfish as part of the Nearshore Rockfish complexes north and south of 40°10′ N lat. The alternative harvest control rule would implement a statewide ACL contribution of 1.76 mt in 2023 and 1.93 mt in 2024. Based on the apportionment described above, the ACL contribution for the portion of quillback rockfish off of California to the Nearshore Rockfish complex north of 40°10′ N lat. would be 0.87 mt in 2023 and 0.89 mt in 2024. The ACL contribution for the portion of quillback rockfish off of California to the Nearshore Rockfish complex south of 40°10′ N lat. would be 0.96 mt in 2023 and 0.97 mt in 2024.</P>
                    <HD SOURCE="HD3">Stocks in Rebuilding Plans</HD>
                    <P>
                        When NMFS declares a stock overfished, the Council must develop and manage the stock in accordance with a rebuilding plan. For overfished stocks in the PCGFMP, this means that the harvest control rule for overfished stocks sets the ACL based on the rebuilding plan. The proposed rules for the 2011-12 (75 FR 67810, November 3, 2010) and 2013-14 (77 FR 67974, November 14, 2012) harvest specifications and management measures contain extensive discussions on the management approach used for overfished stocks, which are not repeated here. In addition, the SAFE document posted on the Council's website at 
                        <E T="03">https://www.pcouncil.org/groundfish/safe-documents/</E>
                         contains a detailed description of each overfished stock, its status and management, as well as the SSC's approach for rebuilding analyses. This document provides information on yelloweye rockfish, which is the only remaining rebuilding stock in the PCGFMP. NMFS declared yelloweye rockfish overfished in 2002. The Council adopted a rebuilding plan for the stock in 2004, and revised the rebuilding plan in 2011 under Amendment 16-4 to the PCGFMP, and again during the 2019-20 biennium (83 FR 63970, December 12, 2018). The Council proposed yelloweye rockfish ACLs for 2023 and 2024 are 
                        <PRTPAGE P="62681"/>
                        based on the current yelloweye rockfish rebuilding plan, so additional details are not repeated here. Appendix F to the PCGFMP contains the most recent rebuilding plan parameters, as well as a history of each overfished stock, and can be found at 
                        <E T="03">https://www.pcouncil.org/groundfish/fisherymanagement-plan/.</E>
                    </P>
                    <P>Additionally, the Council recommended, and NMFS is proposing, to establish annual catch targets (ACTs) within the non-trawl allocation harvest guideline (HG). The non-trawl sector includes the limited entry fixed gear (LEFG) and open access (OA) fisheries as well as the recreational fisheries for Washington, Oregon, and Californ ia. The nearshore fisheries occur seaward of Oregon and California and are subject to both Federal and state HGs as well as other state-specific management measures. The non-nearshore fisheries include the limited entry and Federal open access fixed gear fleets. Tables 2 and 3 outline the proposed harvest specifications for 2023 and 2024 for yelloweye rockfish.</P>
                    <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12,12,12,12,12">
                        <TTITLE>Table 2—2023 Harvest Specifications for Yelloweye Rockfish</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">
                                OFL
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="1">
                                ABC
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="1">
                                ACL
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="1">
                                HG
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="1">
                                ACT
                                <LI>(mt)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">All sectors</ENT>
                            <ENT>123</ENT>
                            <ENT>103</ENT>
                            <ENT>66</ENT>
                            <ENT>55.3</ENT>
                            <ENT/>
                        </ROW>
                        <ROW>
                            <ENT I="03">Non-trawl</ENT>
                            <ENT/>
                            <ENT/>
                            <ENT/>
                            <ENT>50.9</ENT>
                            <ENT>39.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Non-Nearshore</ENT>
                            <ENT/>
                            <ENT/>
                            <ENT/>
                            <ENT>10.7</ENT>
                            <ENT>8.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05" O="xl">Nearshore</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Washington Recreational</ENT>
                            <ENT/>
                            <ENT/>
                            <ENT/>
                            <ENT>13.2</ENT>
                            <ENT>10.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Oregon Recreational</ENT>
                            <ENT/>
                            <ENT/>
                            <ENT/>
                            <ENT>11.7</ENT>
                            <ENT>9.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">California Recreational</ENT>
                            <ENT/>
                            <ENT/>
                            <ENT/>
                            <ENT>15.3</ENT>
                            <ENT>12.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Trawl</ENT>
                            <ENT/>
                            <ENT/>
                            <ENT/>
                            <ENT>4.4</ENT>
                            <ENT/>
                        </ROW>
                    </GPOTABLE>
                    <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12,12,12,12,12">
                        <TTITLE>Table 3—2024 Harvest Specifications for Yelloweye Rockfish</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">
                                OFL
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="1">
                                ABC
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="1">
                                ACL
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="1">
                                HG
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="1">
                                ACT
                                <LI>(mt)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">All sectors</ENT>
                            <ENT>123</ENT>
                            <ENT>103</ENT>
                            <ENT>66</ENT>
                            <ENT>55.3</ENT>
                            <ENT/>
                        </ROW>
                        <ROW>
                            <ENT I="03">Non-trawl</ENT>
                            <ENT/>
                            <ENT/>
                            <ENT/>
                            <ENT>50.9</ENT>
                            <ENT>39.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Non-Nearshore</ENT>
                            <ENT/>
                            <ENT/>
                            <ENT/>
                            <ENT>10.7</ENT>
                            <ENT>8.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05" O="xl">Nearshore</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Washington Recreational</ENT>
                            <ENT/>
                            <ENT/>
                            <ENT/>
                            <ENT>13.2</ENT>
                            <ENT>10.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Oregon Recreational</ENT>
                            <ENT/>
                            <ENT/>
                            <ENT/>
                            <ENT>11.7</ENT>
                            <ENT>9.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">California Recreational</ENT>
                            <ENT/>
                            <ENT/>
                            <ENT/>
                            <ENT>15.3</ENT>
                            <ENT>12.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Trawl</ENT>
                            <ENT/>
                            <ENT/>
                            <ENT/>
                            <ENT>4.4</ENT>
                            <ENT/>
                        </ROW>
                    </GPOTABLE>
                    <P>The Council recommended using ACTs for the non-trawl sector as a precaution. As discussed in the Analysis, because yelloweye rockfish catch has been restricted for many years, it is difficult to project encounter rates. This precautionary approach to higher catch limits would allow more access to target fisheries for the non-trawl sector, while also managing for the uncertainty and volatility in catch of this rebuilding stock by this sector.</P>
                    <HD SOURCE="HD2">D. Summary of ACL Changes From 2022 to 2023-24</HD>
                    <P>Table 4 compares the ACLs for major stocks and stock complexes for 2022 and 2023-24. Under this proposed rule, of the 42 stocks and stock complexes managed with ACLs in 2022, 8 stocks would have higher ACLs in 2023 and 2024 than in 2022, 23 would have ACLs that would decrease in 2023 from 2022, and 7 would have ACLs that would be close to the amount in place in 2022. Three stocks (Dover sole, Pacific cod, and starry flounder), and one stock complex (Other fish), would have the same ACLs in 2022, 2023, and 2024. Under this proposed rule, the ACL for yelloweye rockfish would increase by 29.4 percent. This is based on the projections from the 2017 rebuilding analysis and the default harvest control rule specifying ACLs based on the SPR harvest rate of 65 percent. This predicted slow rate of rebuilding is anticipated for this slow growing species. One stock (arrowtooth flounder) has an ACL that would increase more than 100 percent. This increase is due to new information provided in the 2021 catch-only assessment update. The 37.5 percent increase in sablefish north of 36° N lat. is due to new information from the update assessment of sablefish. The 31.1 percent decrease in lingcod south of 40°10′ N lat. is due to new information provided in the 2021 stock assessment.</P>
                    <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,r50,12,12,12,12">
                        <TTITLE>Table 4—ACLs for Major Stocks and Management Units for 2022, and 2023-24</TTITLE>
                        <BOXHD>
                            <CHED H="1">Stock/complex</CHED>
                            <CHED H="1">Area</CHED>
                            <CHED H="1">
                                ACL
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="2">2022</CHED>
                            <CHED H="2">2023</CHED>
                            <CHED H="2">2024</CHED>
                            <CHED H="1">
                                Percent change
                                <LI>2022 to 2023</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">YELLOWEYE ROCKFISH</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>51</ENT>
                            <ENT>66</ENT>
                            <ENT>66</ENT>
                            <ENT>29.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Arrowtooth Flounder</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>8,458</ENT>
                            <ENT>18,632</ENT>
                            <ENT>14,178</ENT>
                            <ENT>120.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Big Skate</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,389</ENT>
                            <ENT>1,320</ENT>
                            <ENT>1,267</ENT>
                            <ENT>−5.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Black Rockfish</ENT>
                            <ENT>WA</ENT>
                            <ENT>291</ENT>
                            <ENT>290</ENT>
                            <ENT>289</ENT>
                            <ENT>−0.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Black Rockfish</ENT>
                            <ENT>CA</ENT>
                            <ENT>341</ENT>
                            <ENT>334</ENT>
                            <ENT>329</ENT>
                            <ENT>−2.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Bocaccio</ENT>
                            <ENT>S of 40°10′</ENT>
                            <ENT>1,724</ENT>
                            <ENT>1,842</ENT>
                            <ENT>1,828</ENT>
                            <ENT>6.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Cabezon</ENT>
                            <ENT>CA</ENT>
                            <ENT>195</ENT>
                            <ENT>182</ENT>
                            <ENT>171</ENT>
                            <ENT>−6.7</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="62682"/>
                            <ENT I="01">Cabezon/Kelp Greenling</ENT>
                            <ENT>WA</ENT>
                            <ENT>17</ENT>
                            <ENT>20</ENT>
                            <ENT>17</ENT>
                            <ENT>17.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Cabezon/Kelp Greenling</ENT>
                            <ENT>OR</ENT>
                            <ENT>190</ENT>
                            <ENT>185</ENT>
                            <ENT>180</ENT>
                            <ENT>−2.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">California Scorpionfish</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>275</ENT>
                            <ENT>262</ENT>
                            <ENT>252</ENT>
                            <ENT>−4.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Canary Rockfish</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,307</ENT>
                            <ENT>1,284</ENT>
                            <ENT>1,267</ENT>
                            <ENT>−1.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Chilipepper</ENT>
                            <ENT>S of 40°10′</ENT>
                            <ENT>2,259</ENT>
                            <ENT>2,183</ENT>
                            <ENT>2,121</ENT>
                            <ENT>−3.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Cowcod</ENT>
                            <ENT>S of 40°10′</ENT>
                            <ENT>82</ENT>
                            <ENT>80</ENT>
                            <ENT>79</ENT>
                            <ENT>−2.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Darkblotched Rockfish</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>831</ENT>
                            <ENT>785</ENT>
                            <ENT>750</ENT>
                            <ENT>−5.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Dover Sole</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>50,000</ENT>
                            <ENT>50,000</ENT>
                            <ENT>50,000</ENT>
                            <ENT>0.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">English Sole</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>9,101</ENT>
                            <ENT>9,018</ENT>
                            <ENT>8,960</ENT>
                            <ENT>−0.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Lingcod</ENT>
                            <ENT>N of 40°10′</ENT>
                            <ENT>4,958</ENT>
                            <ENT>4,378</ENT>
                            <ENT>3,854</ENT>
                            <ENT>−11.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Lingcod</ENT>
                            <ENT>S of 40°10′</ENT>
                            <ENT>1,172</ENT>
                            <ENT>726</ENT>
                            <ENT>722</ENT>
                            <ENT>−38.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Longnose Skate</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,761</ENT>
                            <ENT>1,708</ENT>
                            <ENT>1,660</ENT>
                            <ENT>−3.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Longspine Thornyhead</ENT>
                            <ENT>N of 34°27′</ENT>
                            <ENT>2,452</ENT>
                            <ENT>2,295</ENT>
                            <ENT>2,162</ENT>
                            <ENT>−6.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Longspine Thornyhead</ENT>
                            <ENT>S of 34°27′</ENT>
                            <ENT>774</ENT>
                            <ENT>725</ENT>
                            <ENT>683</ENT>
                            <ENT>−6.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pacific Cod</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,600</ENT>
                            <ENT>1,600</ENT>
                            <ENT>1,600</ENT>
                            <ENT>0.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pacific Ocean Perch</ENT>
                            <ENT>N of 40°10′</ENT>
                            <ENT>3,711</ENT>
                            <ENT>3,573</ENT>
                            <ENT>3,443</ENT>
                            <ENT>−3.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Petrale Sole</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>3,660</ENT>
                            <ENT>3,485</ENT>
                            <ENT>3,285</ENT>
                            <ENT>−4.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sablefish</ENT>
                            <ENT>N of 36°</ENT>
                            <ENT>6,172</ENT>
                            <ENT>8,486</ENT>
                            <ENT>7,780</ENT>
                            <ENT>37.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sablefish</ENT>
                            <ENT>S of 36°</ENT>
                            <ENT>2,203</ENT>
                            <ENT>2,338</ENT>
                            <ENT>2,143</ENT>
                            <ENT>6.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Shortspine Thornyhead</ENT>
                            <ENT>N of 34°27′</ENT>
                            <ENT>1,393</ENT>
                            <ENT>1,359</ENT>
                            <ENT>1,328</ENT>
                            <ENT>−2.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Shortspine Thornyhead</ENT>
                            <ENT>S of 34°27′</ENT>
                            <ENT>737</ENT>
                            <ENT>719</ENT>
                            <ENT>702</ENT>
                            <ENT>−2.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Spiny Dogfish</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,585</ENT>
                            <ENT>1,456</ENT>
                            <ENT>1,407</ENT>
                            <ENT>−8.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Splitnose</ENT>
                            <ENT>S of 40°10′</ENT>
                            <ENT>1,630</ENT>
                            <ENT>1,592</ENT>
                            <ENT>1,553</ENT>
                            <ENT>−2.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Starry Flounder</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>392</ENT>
                            <ENT>392</ENT>
                            <ENT>392</ENT>
                            <ENT>0.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Widow Rockfish</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>13,788</ENT>
                            <ENT>12,624</ENT>
                            <ENT>11,482</ENT>
                            <ENT>−8.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Yellowtail Rockfish</ENT>
                            <ENT>N of 40°10′</ENT>
                            <ENT>5,831</ENT>
                            <ENT>5,666</ENT>
                            <ENT>5,560</ENT>
                            <ENT>−2.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Blue/Deacon/Black Rockfish</ENT>
                            <ENT>OR</ENT>
                            <ENT>600</ENT>
                            <ENT>597</ENT>
                            <ENT>594</ENT>
                            <ENT>−0.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Nearshore Rockfish North</ENT>
                            <ENT>N of 40°10′</ENT>
                            <ENT>77</ENT>
                            <ENT>93</ENT>
                            <ENT>91</ENT>
                            <ENT>20.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Nearshore Rockfish South</ENT>
                            <ENT>S of 40°10′</ENT>
                            <ENT>1,010</ENT>
                            <ENT>887</ENT>
                            <ENT>891</ENT>
                            <ENT>−11.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Other Fish</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>223</ENT>
                            <ENT>223</ENT>
                            <ENT>223</ENT>
                            <ENT>0.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Other Flatfish</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>4,838</ENT>
                            <ENT>4,862</ENT>
                            <ENT>4,874</ENT>
                            <ENT>0.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Shelf Rockfish North</ENT>
                            <ENT>N of 40°10′</ENT>
                            <ENT>1,450</ENT>
                            <ENT>1,283</ENT>
                            <ENT>1,278</ENT>
                            <ENT>−11.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Shelf Rockfish South</ENT>
                            <ENT>S of 40°10′</ENT>
                            <ENT>1,428</ENT>
                            <ENT>1,469</ENT>
                            <ENT>1,469</ENT>
                            <ENT>2.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Slope Rockfish North</ENT>
                            <ENT>N of 40°10′</ENT>
                            <ENT>1,568</ENT>
                            <ENT>1,540</ENT>
                            <ENT>1,516</ENT>
                            <ENT>−1.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Slope Rockfish South</ENT>
                            <ENT>S of 40°10′</ENT>
                            <ENT>705</ENT>
                            <ENT>701</ENT>
                            <ENT>697</ENT>
                            <ENT>−0.6</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Rebuilding stocks are capitalized.
                        </TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD1">III. Proposed Management Measures</HD>
                    <P>
                        This section describes proposed management measures used to further allocate the ACLs to the various components of the fishery (
                        <E T="03">i.e.,</E>
                         biennial fishery harvest guidelines and set-asides) and management measures to control fishing. Management measures for the commercial fishery modify fishing behavior during the fishing year to ensure catch does not exceed the ACL, and include trip and cumulative landing limits, time/area closures, size limits, and gear restrictions. Management measures for the recreational fisheries include bag limits, size limits, gear restrictions, fish dressing requirements, and time/area closures.
                    </P>
                    <HD SOURCE="HD2">A. Deductions From the ACLs</HD>
                    <P>Before making allocations to the primary commercial and recreational components of groundfish fisheries, the Council recommends “off-the-top deductions,” or deductions from the ACLs to account for anticipated mortality for certain types of activities: harvest in Pacific Coast treaty Indian tribal fisheries; harvest in scientific research activities; harvest in non-groundfish fisheries (incidental catch); and harvest that occurs under EFPs. These off-the-top deductions are proposed for individual stocks or stock complexes and can be found in the footnotes to Tables 1a and 2a to part 660, subpart C in the regulatory text of this proposed rule. The details of the EFPs are discussed below in Section III.H.</P>
                    <HD SOURCE="HD2">B. Tribal Fisheries</HD>
                    <P>
                        The Quileute Tribe, Quinault Indian Nation, Makah Indian Tribe, and Hoh Indian Tribe (collectively, “the Pacific Coast Tribes”) implement management measures for Tribal fisheries both independently as sovereign governments and cooperatively with the management measures in the Federal regulations. The Pacific Coast Tribes work through the Pacific Fishery Management Council process to maintain groundfish set-asides, harvest guidelines, and allocations pursuant to treaty fishing rights and as co-managers of the resource. The Pacific Coast Tribes may adjust their Tribal fishery management measures inseason to stay within the Tribal set-asides and allocations and within the estimated impacts to overfished stocks. Table 5 provides the proposed Tribal harvest set-asides and allocations proposed for the 2023-24 biennium for groundfish species other than Pacific whiting, which is allocated through a separate annual specifications process. These targets are consistent with the 2022 targets, with the exception of Pacific ocean perch (increased to 130 mt) and darkblotched rockfish (increased to 5 mt).
                        <PRTPAGE P="62683"/>
                    </P>
                    <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s100,12,12">
                        <TTITLE>Table 5—Proposed Tribal Harvest Set-Asides and Allocations for the 2023-24 Biennium Compared to Those in Place in 2022</TTITLE>
                        <BOXHD>
                            <CHED H="1">Stock</CHED>
                            <CHED H="1">Off the top deduction</CHED>
                            <CHED H="2">
                                2022
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="2">
                                2023-2024
                                <LI>(mt)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Arrowtooth Flounder</ENT>
                            <ENT>2,041</ENT>
                            <ENT>2,041</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Big Skate</ENT>
                            <ENT>15</ENT>
                            <ENT>15</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">WA Black Rockfish</ENT>
                            <ENT>18</ENT>
                            <ENT>18</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Canary Rockfish</ENT>
                            <ENT>50</ENT>
                            <ENT>50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Darkblotched Rockfish</ENT>
                            <ENT>0.2</ENT>
                            <ENT>5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Dover Sole</ENT>
                            <ENT>1,497</ENT>
                            <ENT>1,497</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">English Sole</ENT>
                            <ENT>200</ENT>
                            <ENT>200</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Lingcod N of 40°10′ N lat</ENT>
                            <ENT>250</ENT>
                            <ENT>250</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Longnose Skate</ENT>
                            <ENT>220</ENT>
                            <ENT>220</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Longspine Thornyhead N of 34°27′ N lat</ENT>
                            <ENT>30</ENT>
                            <ENT>30</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pacific cod</ENT>
                            <ENT>500</ENT>
                            <ENT>500</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pacific Ocean Perch</ENT>
                            <ENT>9.2</ENT>
                            <ENT>130</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Petrale Sole</ENT>
                            <ENT>350</ENT>
                            <ENT>350</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Sablefish N of 36° N lat.
                                <SU>a</SU>
                            </ENT>
                            <ENT>656.6</ENT>
                            <ENT>
                                849 (2023)
                                <LI>778 (2024)</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Shortspine Thornyhead S of 34°27′ N lat</ENT>
                            <ENT>50</ENT>
                            <ENT>50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Spiny Dogfish</ENT>
                            <ENT>275</ENT>
                            <ENT>275</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Widow rockfish</ENT>
                            <ENT>200</ENT>
                            <ENT>200</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Yellowtail Rockfish</ENT>
                            <ENT>1,000</ENT>
                            <ENT>1,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">WA Cabezon/Kelp Greenling</ENT>
                            <ENT>2</ENT>
                            <ENT>2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Nearshore Rockfish North</ENT>
                            <ENT>1.5</ENT>
                            <ENT>1.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Other Flatfish</ENT>
                            <ENT>60</ENT>
                            <ENT>60</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Shelf Rockfish North</ENT>
                            <ENT>30</ENT>
                            <ENT>30</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Slope Rockfish North</ENT>
                            <ENT>36</ENT>
                            <ENT>36</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>a</SU>
                             Sablefish is allocated according to Amendment 6 of the PCGFMP and 50 CFR 660.50(f)(2).
                        </TNOTE>
                    </GPOTABLE>
                    <P>The Pacific Coast Tribes proposed trip limit management in Tribal fisheries for 2023-24—for several stocks, including several rockfish stocks and stock complexes. This rule proposes the trip limits for Tribal fisheries as provided to the Council at its June 2022 meeting in Supplemental Tribal Report 1, Agenda Item F.6.a. For rockfish stocks, Tribal regulations will continue to require full retention of all overfished rockfish stocks and marketable non-overfished rockfish stocks. The Pacific Coast Tribes will continue to develop management measures, including depth, area, and time restrictions, in the directed Tribal Pacific halibut fishery in order to minimize incidental catch of yelloweye rockfish.</P>
                    <HD SOURCE="HD2">C. Biennial Fishery Allocations</HD>
                    <P>The Council routinely recommends 2-year trawl and non-trawl allocations during the biennial specifications process for stocks without formal allocations (as defined in Section 6.3.2 of the PCGFMP) or stocks where the long-term allocation is suspended because the stock is declared overfished.</P>
                    <P>The trawl and non-trawl allocations, with the exception of sablefish north of 36° N lat., are based on the fishery harvest guideline. The fishery harvest guideline is the tonnage that remains after subtracting the off-the-top deductions described in Section III., A, entitled “Deductions from the ACLs,” in this preamble. The trawl and non-trawl allocations and recreational harvest guidelines are designed to accommodate anticipated mortality in each sector as well as variability and uncertainty in those mortality estimates. Additional information on the Council's allocation framework and formal allocations can be found in Section 6.3 of the PCGFMP and § 660.55 of the Federal regulations. Allocations described below are detailed in the harvest specification tables appended to 50 CFR part 660, subpart C in the regulatory text of this proposed rule.</P>
                    <HD SOURCE="HD3">Big Skate</HD>
                    <P>The Council recommended and NMFS is proposing the allocations shown in Table 6 for big skate in 2023 and 2024. These allocations are anticipated to accommodate estimates of mortality of big skate, by sector, in 2023-24. Allocations of big skate are determined on a biennial basis. For 2023-24, the Council elected to maintain the current big skate split of 95 percent to the trawl fishery and 5 percent to the non-trawl fishery. This results in a trawl allocation of 1,197.2 mt and a non-trawl allocation of 63 mt in 2023, as well as a trawl allocation of 1,146.8 mt and a non-trawl allocation of 60.4 mt in 2024. No further allocations or deductions are made.</P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,12,15,15">
                        <TTITLE>Table 6—2023 and 2024 Trawl/Non-Trawl Allocations of Big Skate</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">Percentage</CHED>
                            <CHED H="1">
                                2023 Allocation
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="1">
                                2024 Allocation
                                <LI>(mt)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Trawl</ENT>
                            <ENT>95</ENT>
                            <ENT>1,197.2</ENT>
                            <ENT>1,146.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Non-trawl</ENT>
                            <ENT>5</ENT>
                            <ENT>63</ENT>
                            <ENT>60.4</ENT>
                        </ROW>
                    </GPOTABLE>
                    <PRTPAGE P="62684"/>
                    <HD SOURCE="HD3">Bocaccio South of 40°10′ N Lat.</HD>
                    <P>Specifications for bocaccio are determined through the biennial specifications process. For 2023-24, the Council recommended and NMFS is proposing the allocations shown in Table 7 for bocaccio in 2023 and 2024, which maintain the allocation structure from the previous biennium. These allocations are anticipated to accommodate estimates of mortality of bocaccio, by sector, in 2023-24. In each year, the fishery harvest guideline is split with 39 percent going to the trawl sectors and 61 percent to the non-trawl sectors. For the trawl sector this results in an allocation of 700.3 mt in 2023 and 694.9 mt in 2024. The non-trawl sectors would receive 1,093.5 mt in 2023 and 1,085 mt in 2024. The non-trawl allocation is then distributed between the commercial (nearshore and non-nearshore fisheries) and California recreational fisheries. In 2023, the commercial sector would receive 30.9 percent of the non-trawl allocation or 337.9 mt, and the California recreational sector would receive 755.6 mt. In 2024, the same percentage would remain in place with the commercial sector receiving 335.3 mt and the California recreational sector receiving 749.7 mt.</P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,12,15,15">
                        <TTITLE>Table 7—2023 and 2024 Allocations of Bocaccio</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">Percentage</CHED>
                            <CHED H="1">
                                2023
                                <LI>Allocation</LI>
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="1">
                                2024
                                <LI>Allocation</LI>
                                <LI>(mt)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Trawl</ENT>
                            <ENT>39</ENT>
                            <ENT>700.3</ENT>
                            <ENT>694.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Non-trawl 
                                <SU>a</SU>
                            </ENT>
                            <ENT>61</ENT>
                            <ENT>1,093.5</ENT>
                            <ENT>1,085</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>a</SU>
                             The California recreational sector share of the non-trawl allocation is 755.6 mt in 2023 and 749.7 mt in 2024.
                        </TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD3">Canary Rockfish</HD>
                    <P>The Council recommended and NMFS is proposing the allocations in Table 8 for canary rockfish in 2023 and 2024, which maintain the status quo proportions from the 2021-22 biennium. These allocations are anticipated to accommodate estimates of mortality of canary rockfish, by sector, in 2023-24. For canary rockfish, the fishery harvest guideline is distributed to the trawl and non-trawl sectors with trawl receiving 72.3 percent and non-trawl sectors receiving 27.7 percent each year. In 2023, the trawl sector would receive 880.7 mt of canary rockfish, of which 36 mt would be deducted to account for bycatch in the at-sea sectors, and the remaining 844.7 mt would be distributed to the shorebased individual fishing quota (IFQ) sector. In 2023, the non-trawl sector would receive 337.4 mt which is distributed to the commercial non-trawl (121.5 mt), WA recreational (41.5 mt), OR recreational (62.4 mt), and CA recreational (112.0 mt) fisheries. In 2024, the trawl sector would receive 868.4 mt of canary rockfish, of which 36 mt would be deducted to account for bycatch in the at-sea sectors, and the remaining 832.4 mt would be distributed to the shorebased IFQ sector. The non-trawl sector would receive 332.7 mt, which is distributed to the commercial non-trawl sector (119.8 mt), WA recreational (40.9 mt), OR recreational (61.5 mt), and CA recreational (110.5 mt) fisheries.</P>
                    <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s50,15,15">
                        <TTITLE>Table 8—2023 and 2024 Allocations of Canary Rockfish</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">
                                2023
                                <LI>Allocation</LI>
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="1">
                                2024
                                <LI>Allocation</LI>
                                <LI>(mt)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Shorebased IFQ Program</ENT>
                            <ENT>844.7</ENT>
                            <ENT>832.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">At-sea Sectors</ENT>
                            <ENT>36</ENT>
                            <ENT>36</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Nearshore/Non-nearshore</ENT>
                            <ENT>121.5</ENT>
                            <ENT>119.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Washington recreational</ENT>
                            <ENT>41.5</ENT>
                            <ENT>40.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Oregon recreational</ENT>
                            <ENT>62.4</ENT>
                            <ENT>61.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">California recreational</ENT>
                            <ENT>112.0</ENT>
                            <ENT>110.5</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD3">Cowcod</HD>
                    <P>
                        For 2023-24, the Council recommended and NMFS is proposing to remove the 50 mt ACT for cowcod south of 40°10′ N lat. that was in place during the 2021-22 biennium. The ACT was included in the 2021-22 biennium out of concern of the risk of exceeding the ACL and to account for stock assessment uncertainty. Improved inseason monitoring tools have been effective at monitoring cowcod mortality and reducing management uncertainty. Therefore, the Council recommended removing the 50 mt ACT to provide additional flexibility and stability to the non-trawl sector south of 40°10′ N lat. Table 9 shows the trawl/non-trawl allocations for cowcod for 2023 and 2024. NMFS anticipates the proposed allocation structure will accommodate estimates of mortality of cowcod, by sector, in 2023-24. The fishery harvest guideline is distributed to the trawl and non-trawl sectors, with the trawl sector receiving 36 percent and the non-trawl sector receiving 64 percent each year. The trawl sector would receive 24.8 mt of cowcod in 2023 and 24.4 mt in 2024. The non-trawl sector would receive 44.0 mt in 2023 and 43.4 mt in 2024, which is distributed to the commercial and recreational sectors as a 50/50 split. The Council also recommended, and NMFS proposes, sector-specific ACTs based on the 50/50 split. For 2023 the commercial sector ACT would be 22 mt and the recreational sector ACT would be 22 mt. For 2024 the commercial sector ACT would be 21.7 mt and the recreational sector ACT would be 21.7 mt. Utilizing sector-specific ACTs within the non-trawl sector, in addition to maintaining the proposed zero retention requirement in the non-trawl sector, should help to reduce management uncertainty with the proposed removal of the 50 mt ACT below the fishery harvest guideline.
                        <PRTPAGE P="62685"/>
                    </P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,12,15,15">
                        <TTITLE>Table 9—2023 and 2024 Trawl/Non-Trawl Allocations of Cowcod</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">Percentage</CHED>
                            <CHED H="1">
                                2023 Allocation
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="1">
                                2024 Allocation
                                <LI>(mt)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Trawl</ENT>
                            <ENT>36</ENT>
                            <ENT>24.8</ENT>
                            <ENT>24.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Non-trawl</ENT>
                            <ENT>64</ENT>
                            <ENT>44.1</ENT>
                            <ENT>43.4</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD3">Lingcod South of 40°10′ N Lat.</HD>
                    <P>The Council recommended and NMFS is proposing the trawl/non-trawl allocations for lingcod south of 40°10′ N lat. in Table 10. These allocations are anticipated to accommodate estimates of mortality of lingcod, by sector, in 2023-24.</P>
                    <P>Specifications for the lingcod south of 40°10′ N lat. were established through the biennial process with a trawl/non-trawl allocation for the 2023-24 specifications of 40 percent of the harvest guideline to trawl sector and 60 percent to non-trawl sector. In 2023, the distribution results in 285.2 mt to the trawl sector and 427.8 mt to the non-trawl sectors. In 2024, the distribution results in 285.2 mt to the trawl sectors and 425.4 mt to the non-trawl sectors. No further allocations or distributions are made.</P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,12,15,15">
                        <TTITLE>Table 10—2023 and 2024 Trawl/Non-Trawl Allocations of Lingcod South of 40°10′ N Lat.</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">Percentage</CHED>
                            <CHED H="1">
                                2023 Allocation
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="1">
                                2024 Allocation
                                <LI>(mt)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Trawl</ENT>
                            <ENT>40</ENT>
                            <ENT>285.2</ENT>
                            <ENT>283.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Non-trawl</ENT>
                            <ENT>60</ENT>
                            <ENT>427.8</ENT>
                            <ENT>425.4</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD3">Longnose Skate</HD>
                    <P>The Council recommended and NMFS is proposing the trawl/non-trawl allocations for longnose skate in Table 11. The allocation percentages, 90 percent to trawl and 10 percent to non-trawl, reflect historical catch of longnose skate in the two sectors. These allocations are anticipated to accommodate estimates of mortality of longnose skate, by sector, in 2023-24. In 2023, the 90/10 distribution results in 1,311.0 mt to the trawl sectors and 145.7 mt to the non-trawl sectors. In 2024, the distribution results in 1,267.8 mt to the trawl sectors and 140.9 mt to the non-trawl sectors.</P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,12,15,15">
                        <TTITLE>Table 11—2023 and 2024 Trawl/Non-Trawl Allocations of Longnose Skate</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">Percentage</CHED>
                            <CHED H="1">
                                2023 Allocation
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="1">
                                2024 Allocation
                                <LI>(mt)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Trawl</ENT>
                            <ENT>90</ENT>
                            <ENT>1,311.0</ENT>
                            <ENT>1,267.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Non-trawl</ENT>
                            <ENT>10</ENT>
                            <ENT>145.7</ENT>
                            <ENT>140.9</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD3">Minor Shelf Rockfish</HD>
                    <P>Allocations for Minor Shelf Rockfish are recommended by the Council and proposed by NMFS for each biennial cycle. The proposed allocations for 2023 and 2024 are shown in Table 12. Specifications for the shelf rockfish complex north of 40°10′ N lat. were established through the biennial process with a trawl/non-trawl allocation for the 2023-24 specifications of 60.2 percent to trawl sectors and 39.8 percent to non-trawl sectors. In 2023, the distribution results in 729.7 mt to the trawl sectors and 482.4 mt to the non-trawl sectors. In 2024, the distribution results in 726.7 mt to the trawl sectors and 480.4 mt to the non-trawl sectors. Of the amount going to the trawl sectors, 35 mt is deducted each year from the trawl allocation to account for bycatch in the at-sea whiting sectors, with the remaining 694.7 mt in 2023 and 691.7 mt in 2024 going to the shorebased IFQ fishery. No further allocations or distributions are made.</P>
                    <P>Specifications for the shelf rockfish complex south of 40°10′ N lat. were established through the biennial process with a trawl/non-trawl allocation for the 2023-24 specifications of 12.2 percent to trawl sectors and 87.8 percent to non-trawl sectors. In 2023 and 2024, the distribution results in 163.9 mt to the trawl sectors and 1,173.2 mt to the non-trawl sectors. No further allocations or distributes are made.</P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,12,15,15">
                        <TTITLE>Table 12—Trawl/Non-Trawl Allocations for Minor Shelf Rockfish North and South of 40°10′ N Lat.</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">Percentage</CHED>
                            <CHED H="1">
                                2023 Allocations
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="1">
                                2024 Allocations
                                <LI>(mt)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22">Minor Shelf Rockfish north of 40°10′ N lat.:</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Trawl</ENT>
                            <ENT>60.2</ENT>
                            <ENT>729.7</ENT>
                            <ENT>726.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Non-trawl</ENT>
                            <ENT>39.8</ENT>
                            <ENT>482.4</ENT>
                            <ENT>480.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Minor Shelf Rockfish south of 40°10′ N lat.:</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Trawl</ENT>
                            <ENT>12.2</ENT>
                            <ENT>163.0</ENT>
                            <ENT>163.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Non-trawl</ENT>
                            <ENT>87.8</ENT>
                            <ENT>1,173.2</ENT>
                            <ENT>1,173.2</ENT>
                        </ROW>
                    </GPOTABLE>
                    <PRTPAGE P="62686"/>
                    <HD SOURCE="HD3">Slope Rockfish Complex</HD>
                    <P>Allocations for slope rockfish complex south of 40°10′ N lat., including custom shares for blackgill rockfish, are recommended by the Council and proposed by NMFS for each biennial cycle. The proposed allocations for 2023 and 2024 are shown in Table 13. The Council recommended blackgill rockfish within the slope rockfish complex south of 40°10′ N lat. be managed by setting an HG for blackgill rockfish that was equal to the species specific ACL contribution to the slope rockfish complex south of 40°10′ N lat. The blackgill rockfish HG was then used to allocate 41 percent to the trawl sector and 59 percent to the non-trawl sector. Then, trawl (63 percent) and non-trawl (37 percent) allocations were applied to the remaining species in the complex. Finally, the off-the top set-asides are then deducted to produce the final two-year allocations. In 2023, the distribution results in 378.7 mt to the trawl sectors and 279.3 mt to the non-trawl sectors. In 2024, the distribution results in 381.mt to the trawl sectors and 280.2 mt to the non-trawl sectors.</P>
                    <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,12,12,12,12">
                        <TTITLE>Table 13—Trawl/Non-Trawl Allocations for Minor Slope Rockfish South of 40°10′ N Lat.</TTITLE>
                        <BOXHD>
                            <CHED H="1">Category</CHED>
                            <CHED H="1">
                                2023 Allocations
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="2">Trawl</CHED>
                            <CHED H="2">Non-trawl</CHED>
                            <CHED H="1">
                                2024 Allocations
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="2">Trawl</CHED>
                            <CHED H="2">Non-trawl</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Blackgill rockfish share</ENT>
                            <ENT>70.7 (41%)</ENT>
                            <ENT>101.7 (59%)</ENT>
                            <ENT>69.7 (41%)</ENT>
                            <ENT>100.2 (59%)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">“Other slope rockfish” share</ENT>
                            <ENT>330.5 (63%)</ENT>
                            <ENT>194.1 (37%)</ENT>
                            <ENT>334.6 (63%)</ENT>
                            <ENT>196.5 (37%)</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">Share (mt)</ENT>
                            <ENT>401.2</ENT>
                            <ENT>295.8</ENT>
                            <ENT>404.3</ENT>
                            <ENT>296.7</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="03">Total</ENT>
                            <ENT A="01">697.0</ENT>
                            <ENT A="01">701.0</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Percentage of total share</ENT>
                            <ENT>57.56%</ENT>
                            <ENT>42.44%</ENT>
                            <ENT>57.67%</ENT>
                            <ENT>42.33%</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="03">Total combined off-top</ENT>
                            <ENT A="01">39</ENT>
                            <ENT A="01">39</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Apportioned off-top</ENT>
                            <ENT>22.4</ENT>
                            <ENT>16.6</ENT>
                            <ENT>22.5</ENT>
                            <ENT>16.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Final two year allocation</ENT>
                            <ENT>378.7</ENT>
                            <ENT>279.3</ENT>
                            <ENT>381.8</ENT>
                            <ENT>280.2</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD3">Petrale Sole</HD>
                    <P>The Council recommended and NMFS is proposing the trawl/non-trawl allocations for petrale sole in Table 14. These allocations are anticipated to accommodate estimates of mortality of petrale sole, by sector, in 2023-24. For the 2023-24 biennium, 30 mt of petrale sole would be allocated to the non-trawl sector and the remainder would go to the trawl sector each year. In 2023, the distribution results in 3,068.8 mt to the trawl sector. In 2024, the trawl sector would receive 2,868.8 mt.</P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,12,15,15">
                        <TTITLE>Table 14—2023 and 2024 Trawl/Non-Trawl Allocations of Petrale Sole</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">Percentage</CHED>
                            <CHED H="1">
                                2023 Allocation
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="1">
                                2024 Allocation
                                <LI>(mt)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Trawl</ENT>
                            <ENT/>
                            <ENT>3,068.8</ENT>
                            <ENT>2,868.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Non-trawl</ENT>
                            <ENT/>
                            <ENT>30</ENT>
                            <ENT>30</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD3">Widow Rockfish</HD>
                    <P>The Council recommended and NMFS is proposing the trawl/non-trawl allocations for widow rockfish in Table 15. These allocations are anticipated to accommodate estimates of mortality of widow rockfish, by sector, in 2023-24. For the 2023-24 biennium, 400 mt of widow rockfish would be allocated to the non-trawl sector and the remainder would go to the trawl sector each year. In 2023, the distribution results in 11,985.7 mt to the trawl sector. In 2024, the trawl sector would receive 10,843.7 mt.</P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,12,15,15">
                        <TTITLE>Table 15—2023 and 2024 Trawl/Non-Trawl Allocations of Widow Rockfish</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">Percentage</CHED>
                            <CHED H="1">
                                2023 Allocation
                                <LI>(mt)</LI>
                            </CHED>
                            <CHED H="1">
                                2024 Allocation
                                <LI>(mt)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Trawl</ENT>
                            <ENT/>
                            <ENT>11,985.7</ENT>
                            <ENT>10,843.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Non-trawl</ENT>
                            <ENT/>
                            <ENT>400</ENT>
                            <ENT>400</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD2">D. Corrections and Additional Waypoints for Rockfish Conservation Areas</HD>
                    <P>Rockfish Conservation Areas (RCAs) are large area closures intended to reduce the catch of a stock or stock complex by restricting fishing activity at specific depths. The boundaries for RCAs are defined by straight lines connecting a series of latitude and longitude coordinates that approximate depth contours. These sets of coordinates, or lines, are not gear or fishery specific, but can be used in combination to define an area. NMFS then implements fishing restrictions for a specific gear and/or fishery within each defined area.</P>
                    <P>
                        For the 2023-24 biennium, the Council recommended and NMFS is proposing line modifications seaward of California around Eel Canyon (near Eureka), Mendocino Canyon, Mattole Canyon, the Farallon Islands (near San Francisco), the Channel Islands (near Santa Barbara and east of Anacapa Island), Redondo Canyon, Santa 
                        <PRTPAGE P="62687"/>
                        Catalina Island, Lasuen Knoll, and Santa Clemente Island, as well as in near Albion, Monterey Bay, Point Sur, Morro Bay, Port Hueneme, Santa Monica Bay, Point Vincente, Huntington Beach, and San Diego. These modifications would better align existing RCA coordinates with chart-based depth contours, reduce boundary line crossovers, and address enforcement concerns. See Section 2.1 of the Analysis for more details on these changes.
                    </P>
                    <P>The Council's recommendation would have deleted point (130) on the boundary line approximating the 50 fathoms (fm) (91 m) depth contour. This was the only point for this boundary line at 36° N lat. Points at each commonly used geographic coordinates (latitudes) defined in paragraph (2) at § 660.11 “North-South management area” should be retained to maintain functionality and enforceability of these depth-based lines when they are used to form closed areas such as Block Area Closures or the Non-trawl Rockfish Conservation Area. Therefore, NMFS is making an administrative change to modify the point instead of deleting it. This will maintain the shape of the boundary line the Council recommended, but will also maintain the functionality and enforceability needed. This is an administrative change and does not change the on-the-water location of the line that was recommended by the Council at its June 2022 meeting.</P>
                    <P>NMFS is republishing § 660.72(j)(220) through (222) to correct the paragraph designation of paragraph (j)(221). The “1” was mistakenly omitted during prior revisions so it was published as a second paragraph (j)(22) in that section. This correction is not substantive, and does not change the on-the-water effects of these regulations, aside from reducing potential confusion about multiple paragraphs (j)(22).</P>
                    <HD SOURCE="HD2">E. Limited Entry Trawl</HD>
                    <P>The limited entry trawl fishery is made up of the shorebased IFQ program, whiting and non-whiting, and the at-sea whiting sectors. For some stocks and stock complexes with a trawl allocation, an amount is first set-aside for the at-sea whiting sector with the remainder of the trawl allocation going to the shorebased IFQ sector. Set-asides are not managed by NMFS or the Council except in the case of a risk to the ACL.</P>
                    <HD SOURCE="HD3">At-Sea Set Asides</HD>
                    <P>For several species, the trawl allocation is reduced by an amount set-aside for the at-sea whiting sector. This amount is designed to accommodate catch by the at-sea whiting sector when they are targeting Pacific whiting. The Council is recommending and NMFS is proposing the set-asides in Table 16 for the 2023-24 biennium. The Council considered a set-aside for Pacific spiny dogfish but did not recommend establishing one.</P>
                    <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s75,r75,15">
                        <TTITLE>Table 16—2023-24 At-Sea Set-Asides for Vessels Targeting Pacific Whiting While Fishing as Part of the At-Sea Sector</TTITLE>
                        <BOXHD>
                            <CHED H="1">Stock or stock complex</CHED>
                            <CHED H="1">Area</CHED>
                            <CHED H="1">
                                At-sea set-aside
                                <LI>amount</LI>
                                <LI>(mt)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Arrowtooth Flounder</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>70</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Canary rockfish</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>36</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Darkblotched rockfish</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>76.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Dover sole</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>10</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Lingcod</ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>15</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Longnose skate</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Minor shelf rockfish</ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>35</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Minor slope rockfish</ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>300</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Other flatfish</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>35</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pacific halibut</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>10</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pacific ocean perch</ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>300</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Petrale sole</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sablefish</ENT>
                            <ENT>N of 36° N lat</ENT>
                            <ENT>100</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Shortspine thornyhead</ENT>
                            <ENT>N of 34°27′ N lat</ENT>
                            <ENT>70</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Widow rockfish</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>476</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Yellowtail rockfish</ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>320</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD3">Incidental Trip Limits for IFQ Vessels</HD>
                    <P>For vessels fishing in the Shorebased IFQ Program, with either groundfish trawl gear or non-trawl gears, the following incidentally-caught stocks are managed with trip limits: </P>
                    <P>Minor Nearshore Rockfish north and south, Washington black rockfish, Oregon black/blue/deacon rockfish, cabezon (46°16′ to 40°10′ N lat. and south of 40°10′ N lat.), spiny dogfish, longspine thornyhead south of 34° N lat., big skate, California scorpionfish, longnose skate, Pacific whiting, and the Other Fish complex. For all these stocks, this rule proposes maintaining the same IFQ fishery trip limits for these stocks for the start of the 2023-24 biennium as those in place in 2022. Additionally, this rule proposes maintaining the trip limit for blackgill rockfish within the southern slope rockfish complex. The trip limit would be unlimited to start the 2023 fishing year. The purpose of the blackgill trip limit would be to allow the Council to reduce targeting of blackgill rockfish inseason, if needed. Trip limits for the IFQ fishery can be found in Table 1 North and Table 1 South to part 660, subpart D. Changes to trip limits would be considered a routine measure under § 660.60(c), and may be implemented or adjusted, if determined necessary, through inseason action.</P>
                    <HD SOURCE="HD2">F. LEFG and OA Non-Trawl Fishery</HD>
                    <P>
                        Management measures for the LEFG and OA non-trawl fisheries tend to be similar because the majority of participants in both fisheries use hook-and-line gear. Management measures, including area restrictions (
                        <E T="03">e.g.,</E>
                         non-trawl RCA) and trip limits in these non-trawl fisheries, are generally designed to allow harvest of target stocks while keeping catch of overfished stocks low. LEFG trip limits are specified in Table 2 (North) and Table 2 (South) to subpart E. OA trip limits are specified in Table 3 (North) and Table 3 (South) to subpart F in the regulatory text of this proposed rule.
                        <PRTPAGE P="62688"/>
                    </P>
                    <HD SOURCE="HD3">Sablefish Trip Limits</HD>
                    <P>Sablefish are managed separately north and south of 36° N lat. For the portion of the stock north of 36° N lat., the Council recommended and NMFS proposes removing the daily trip limit for the OA fishery and maintaining the same weekly and bimonthly trip limits as were in place in the start of 2022. For the portion south of 36° N lat., the Council recommended, and NMFS proposes, the same weekly and bimonthly trip limits as were in place in the start of 2022. The proposed sablefish trip limits for 2023-24 are shown in Table 17.</P>
                    <GPOTABLE COLS="8" OPTS="L2,i1" CDEF="s50,r50,r25,r25,r25,r25,r25,r25">
                        <TTITLE>Table 17—Sablefish Trip Limits for Limited Entry and Open Access Sectors North and South of 36° N Lat.</TTITLE>
                        <BOXHD>
                            <CHED H="1">Sector</CHED>
                            <CHED H="1">Area</CHED>
                            <CHED H="1">Jan-Feb</CHED>
                            <CHED H="1">Mar-Apr</CHED>
                            <CHED H="1">May-Jun</CHED>
                            <CHED H="1">Jul-Aug</CHED>
                            <CHED H="1">Sept-Oct</CHED>
                            <CHED H="1">Nov-Dec</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Limited entry</ENT>
                            <ENT>north of 36° N lat</ENT>
                            <ENT A="L05">2,400 lb (1089 kg)/week; not to exceed 4,800 lb (2,177 kg) bi-monthly.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>south of 36° N lat</ENT>
                            <ENT A="L05">2,500 lb (1,134 kg)/week.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Open access</ENT>
                            <ENT>north of 36° N lat</ENT>
                            <ENT A="L05">2,000 lb (907 kg)/week; not to exceed 4,000 lb (1,814 kg) bi-monthly.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>south of 36° N lat</ENT>
                            <ENT A="L05">2,000 lb (907 kg)/week; not to exceed 4,000 lb (1,814 kg) bi-monthly.</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD3">LEFG and OA Trip Limits</HD>
                    <P>The Council recommended, and NMFS is proposing, status quo trip limits for LEFG and OA fisheries in 2023. The Council considered changes to the quillback rockfish and copper rockfish trip limits off California but reaffirmed the limits set through inseason action for 2022 (86 FR 72863; December 23, 2021). That action intended to reduce mortality of quillback and copper rockfish by implementing sub-trip limits of 75 lbs (34 kg) per 2 months within the 2,000 lbs (907 kg) per 2 months Minor Nearshore Rockfish limit for the areas between 42°-40°10′ N lat., and south of 40°10′ N lat. The Council could recommend further adjustment to the sub-trip limits through additional inseason action once more data on the current limits is collected and the effects on mortality, particularly discard mortality, are better understood. NMFS notes that allowing the continuation of fishery-dependent data collection through minimal retention would be very beneficial for future stock assessments. Additionally, further reductions on quillback rockfish, an important species in the live fish market, in the commercial Nearshore Fishery could destabilize the niche fishery. More information on these trip limits can be found in the Analysis.</P>
                    <HD SOURCE="HD3">Primary Sablefish Tier Limits</HD>
                    <P>Some limited entry fixed gear permits are endorsed to receive annual sablefish quota, or tier limits. Vessels registered with one, two, or up to three of these permits may participate in the primary sablefish fishery. The proposed tier limits are as follows: in 2023, Tier 1 at 72,904 lb (33,069 kg), Tier 2 at 33,138 lb (15,031 kg), and Tier 3 at 18,936 lb (8,589 kg). For 2024, Tier 1 at 66,805 lb (30,302 kg), Tier 2 at 30,366 lb (13,774 kg), and Tier 3 at 17,352 lb (7,871 kg).</P>
                    <HD SOURCE="HD2">G. Recreational Fisheries</HD>
                    <P>This section describes the recreational fisheries management measures proposed for 2023-24. The Council primarily recommends depth restrictions and groundfish conservation areas to constrain catch within the recreational harvest guidelines for each stock. Washington, Oregon, and California each proposed, and the Council recommended, different combinations of seasons, bag limits, area closures, and size limits for stocks targeted in recreational fisheries. These measures are designed to limit catch of overfished stocks found in the waters adjacent to each state while allowing target fishing opportunities in their particular recreational fisheries. The following sections describe the recreational management measures proposed in each state.</P>
                    <HD SOURCE="HD3">Washington</HD>
                    <P>The state of Washington manages its marine fisheries in four areas: Marine Area 1 extends from the Oregon/Washington border to Leadbetter Point; Marine Area 2 extends from Leadbetter Point to the mouth of the Queets Rivers; Marine Area 3 extends from the Queets River to Cape Alava; and Marine Area 4 extends from Cape Alava to the Sekiu River. This proposed rule would adopt the following season structure in Table 18.</P>
                    <GPH SPAN="3" DEEP="313">
                        <PRTPAGE P="62689"/>
                        <GID>EP14OC22.073</GID>
                    </GPH>
                    <P>The Washington recreational fishery would be open from the second Saturday in March through the third Saturday in October. The aggregate groundfish bag limits in waters adjacent to Washington would continue to be nine fish in all areas with a sub-bag limit for cabezon (one per day), rockfish (seven per day), lingcod (two per day). The flatfish limit would continue to be five fish, and is not counted towards the groundfish bag limit of nine but is in addition to it.</P>
                    <P>The retention of copper rockfish, quillback rockfish, and vermilion rockfish during the months of May, June, and July would be prohibited. As stated by the Washington Department of Fish and Wildlife (WDFW) in its analysis for this proposal, these prohibitions for copper rockfish and quillback rockfish are projected to keep mortality below the species specific ACL contributions. For vermilion, the prohibition is expected to lower mortality while maintaining some data flow needed for stock assessments (Agenda Item F.6.a, WDFW Report 1, June 2022).</P>
                    <P>Consistent with the 2021-22 biennium, the Council recommended and NMFS is proposing to continue to prohibit recreational fishing for groundfish and Pacific halibut inside the North Coast Recreational Yelloweye Rockfish Conservation Area (YRCA), a C-shaped closed area off the northern Washington coast. The South Coast Recreational YRCA and the Westport Offshore YRCA would remain open to recreational fishing for the 2023-24 biennium. Coordinates for YRCAs are defined at § 660.70.</P>
                    <HD SOURCE="HD3">Oregon</HD>
                    <P>
                        The Council recommend that Oregon recreational fisheries in 2023-24 would operate under an all months all depths season structure to start the 2023 fishing year. The Council recommended maintaining the 2021-22 aggregate bag limits and size limits in Oregon recreational fisheries for 2023-24. The proposed limits are: three lingcod per day, with a minimum size of 22 in (56 cm); 25 flatfish per day, excluding Pacific halibut; and a marine fish aggregate bag limit of 10 fish per day, where cabezon have a minimum size of 16 in (41 cm). Oregon long-leader gear fishing and “all-depth” Pacific halibut fishing would continue to be allowed on the same trip. This rule proposes sablefish, Pacific cod, and other flatfish species (sole, flounder, sanddab) may be retained on “all-depth” halibut trips. This measure would provide additional opportunity for anglers participating in the “all depth” halibut fishery and reduce potential regulatory discards. Based on the Analysis, additional effort would not be expected (
                        <E T="03">i.e.,</E>
                         no new trips occurring), because anglers would just have this additional opportunity on trips they are already taking. Therefore, no additional impacts to yelloweye rockfish, Chinook salmon, or coho salmon would be expected.
                    </P>
                    <P>Oregon often adopts more restrictive measures in state rule. This enables the ODFW to tighten or ease restrictions inseason based on quota status and projected mortality. The Federal rules serve as a backstop, while state rules can be adjusted more rapidly in response to inseason circumstances, improving management responsiveness and the ability to achieve conservation and opportunity objectives. For example, ODFW anticipates continuing the prohibition on retaining quillback rockfish in the recreational fishery (and all non-trawl commercial fisheries) in 2023-24.</P>
                    <HD SOURCE="HD3">California</HD>
                    <P>
                        The Council manages recreational fisheries in waters seaward of California in five separate management areas. Season and area closures differ between California management areas to limit incidental catch of overfished stocks and stocks of concern while providing as much recreational fishing opportunity as possible. The Council's 
                        <PRTPAGE P="62690"/>
                        recommended California season structure for 2023 and 2024 is a substantial departure from 2021 and 2022. In order to reduce total mortality of quillback rockfish and copper rockfish, each management area would incur a reduction in fishing time in nearshore waters of 30 percent or more. This, in combination with the proposed novel utilization of the RCA described in Section III.N, would create an “offshore only fishery” during certain months. Recreational fishing for groundfish would continue to be prohibited in waters less than 100 fm (183 m) around Cordell Bank as described in § 660.360(c)(3)(i)(C).
                    </P>
                    <P>In the Northern Management Area (42° N lat. to 40°10′ N lat.), the fishery for California rockfish, cabezon, greenling complex (RCG complex), as defined at § 660.360(c)(3)(ii), and the fishery for lingcod would be closed January 1 to May 14, open in all depths from May 15 to October 15, and closed October 16 to December 31.</P>
                    <P>In the Mendocino Management Area (40°10′ N lat. to 38°57.5′ N lat.), and the San Francisco Management Area (38°57.5′ N lat. to 37°11′ N lat.) the RCG complex fishery and the lingcod fishery would be closed January 1 to May 14, open May 15 to July 15 seaward of the 50 fm (91 m) RCA line, and open in all depths from July 16 to December 31.</P>
                    <P>In the Central Management Area (37°11′ N lat. to 34°27′ N lat.), the RCG complex fishery and the lingcod fishery would be closed January 1 to April 30, open May 1 to September 30 in all depths, and open October 1 to December 31 seaward of the 50 fm (91 m) RCA line.</P>
                    <P>In the Southern Management Area (34°27′ N lat. to U.S./Mexico border), the RCG complex fishery and the lingcod fishery would be closed January 1 to March 31, open April 1 to September 15 in all depths, and open September 16 to December 31 seaward of the 50 fm (91 m) RCA line.</P>
                    <P>Table 19 shows the proposed season structure and depth limits by management area in 2023 and 2024 for the RCG complex fishery and lingcod fishery.</P>
                    <GPH SPAN="3" DEEP="295">
                        <GID>EP14OC22.074</GID>
                    </GPH>
                    <P>
                        In times and areas where an RCA is closed seaward of an RCA line (
                        <E T="03">i.e.,</E>
                         when an “off-shore only” fishery is active in that management area) the following would be prohibited: (1) possession or retention of nearshore rockfish (defined as black rockfish, blue rockfish, black and yellow rockfish, brown rockfish, China rockfish, copper rockfish, calico rockfish, gopher rockfish, kelp rockfish, grass rockfish, olive rockfish, quillback rockfish, and treefish), cabezon, and greenlings in all depths of the Exclusive Economic Zone (EEZ) throughout the management area; (2) possession and retention of all rockfish, cabezon, greenlings, and lingcod would be prohibited shoreward of the RCA boundary line within the EEZ, except that vessels may transit through waters shoreward of the RCA line with no fishing gear in the water.
                    </P>
                    <P>In all Management Areas, California scorpionfish, “Other Flatfish” (as defined at § 660.11), petrale sole and starry flounder, leopard shark, and “Other Federal Groundfish” would be open year-round at all depths. “Other Federal groundfish” as defined in state regulations, (Section 28.49, Title 14, California Code of Regulations) include soupfin shark, Dover sole, English sole, arrowtooth flounder, spiny dogfish, skates, ratfish, grenadiers, finescale codling, Pacific cod, Pacific whiting, sablefish and thornyheads.</P>
                    <P>The Council recommended that size limits and bag limits would remain the same as 2022 for all stocks. The Council also recommended and NMFS is proposing to continue sub-bag limits of one quillback rockfish, one copper rockfish, and four vermilion rockfish within the 10-fish RCG daily bag and possession limit.</P>
                    <P>
                        Continuing the one-fish sub-bag limits for quillback and copper rockfish would allow for fishery-dependent data 
                        <PRTPAGE P="62691"/>
                        collection, specifically biological data. Maintaining the flow of this data is very important for future stock assessments as data gaps would add uncertainty in the results of future assessments. As described in Section 11 of the Analysis, the Council analyzed quillback rockfish, copper rockfish, and vermilion rockfish sub-bag limits ranging from 10 to 0 fish (
                        <E T="03">i.e.,</E>
                         no retention) within the 10-fish RCG bag limit. California Department of Fish and Wildlife (CDFW) tracks groundfish mortality inseason on a weekly and/or monthly basis to ensure that mortality remains within allowable limits. Further changes to the sub-bag limit or to prohibit retention may be recommended by the Council inseason, as necessary, to limit mortality and achieve specifications.
                    </P>
                    <P>In addition to the regulatory management measures to reduce mortality of copper and quillback rockfish in 2022 (86 FR 72863; December 23, 2021), the fishery industry has undertaken several voluntary measures including dissemination of enhanced species identification information, avoidance procedures, and no retention when a biological sampler is not aboard. Per public testimony at the June 2022 Council meeting, the industry plans to continue these voluntary measures in 2023 and 2024. NMFS expects these mandatory and voluntary measures would substantially reduce mortality of quillback and copper rockfish.</P>
                    <HD SOURCE="HD2">H. Exempted Fishing Permits</HD>
                    <P>Issuing EFPs is authorized by regulations implementing the Magnuson-Stevens Act at 50 CFR 600.745, which state that EFPs may be used to authorize fishing activities that would otherwise be prohibited.</P>
                    <P>At its June 2022 meeting, the Council recommended NMFS approve five EFP applications for the 2023 fishing year and preliminarily approve the EFP applications for the 2024 fishing year. The Council considered these EFP applications concurrently with the 2023-2024 biennial harvest specifications and management process because expected catch under most EFP projects is included in the catch limits for groundfish stocks. All of the EFP applications are renewals. Two EFP applications request to test the use of natural bait while fishing inside the non-trawl Rockfish Conservation Area (NT-RCA), which is proposed to be prohibited as part of measures allowing non-trawl vessels to use select hook and line gear configurations within the NT-RCA (see part J of this section). One EFP application requests to test whether removing certain gear, time, and area restrictions may impact the nature and extent of bycatch of protected and prohibited species. The final two EFP applications request to retain certain prohibited species in order to collect fishery-dependent data for potential use in upcoming stock assessments. A summary of each EFP application is provided below:</P>
                    <P>
                        • 
                        <E T="03">Groundfish EFP Proposal—Yellowtail Rockfish Jig Fishing off California:</E>
                         Barbara Emley of the San Francisco Community Fishing Association and private open access fisherman Daniel Platt submitted a renewal application for research that has been conducted since 2013 (herein referred to as the “Emley-Platt EFP”). From 2013-2022, this EFP tested the efficacy of a commercial jig gear configured to target underutilized, midwater yellowtail and shelf rockfish species while avoiding the rebuilding, bottom-dwelling yelloweye rockfish inside the NT-RCA. As part of this 2023-24 harvest specifications and management measures action, the Council recommended, and NMFS proposed, this EFP gear type be approved for legal use inside the NT-RCA (see part J of this section). Therefore, if this rulemaking is implemented as proposed, the associated exemptions from the prohibitions on fishing and/or transiting inside the non-trawl RCA with non-trawl gear would no longer be needed for this EFP project beginning in 2023. However, the application contains a new request for 2023 and 2024, which is to test the effect of using natural bait on the shrimp fly gear. Even if the commercial jig gear is legalized for use inside the NT-RCA through this action, there would still be a requirement to use artificial bait, which has been used in the EFP project since 2013. Testing the use of natural bait could gather data to inform the Council on changes to catch composition while using natural bait compared to artificial bait. If this proposed rule and EFP proposal are approved, this EFP project would require exemptions from: (1) the prohibition on fishing with natural bait inside the NT-RCA (see proposed regulation below at § 660.330 (b)(3)(i)(D)); and (2) the open access trip limits in Table 3 (South) to part 660, subpart F (vessels that fish between 40°10′ N lat. and 34°27′ have specified EFP catch limits). If this EFP gear type is not approved for legal use inside the NT-RCA as proposed in this rulemaking, then this EFP project would require additional exemptions from: (1) the prohibition to fish inside the non-trawl RCA with non-trawl gear (see § 660.330(d)(12)(i)); (2) the prohibition on transiting through the non-trawl RCA without non-trawl gear stowed (see § 660.330(d)(12)(ii)); and (3) the prohibition on retaining and landing groundfish harvested from inside the non-trawl RCA with non-trawl gear (see § 660.330(d)(12)(iii)). In addition to the request to use natural bait, the 2023-24 application also requests a geographic expansion of the EFP to include additional area in northern and southern California. If approved, NMFS would authorize up to 7 vessels to test the use of natural bait inside the non-trawl RCA off the California coast—specifically between the Oregon/California border (was previously limited to 40°10′ N lat.) and the U.S./Mexico border (was previously limited to Point Conception, California), at depths ranging from 35 to 150 fathoms (64 to 274 meters (m)). The EFP Director did not request any additional EFP allocations for the geographic expansion north of 40°10′ N lat.; those vessels would fish under the open access trip limits in Table 3 (North) to part 660, subpart F.
                    </P>
                    <P>
                        • 
                        <E T="03">Groundfish EFP Proposal—Monterey Bay Regional EFP Targeting Chilipepper Rockfish:</E>
                         Real Good Fish of Moss Landing, California submitted a renewal application to continue research that has been conducted since 2019. Similar to the Emley-Platt EFP, the Council recommended this gear type be approved for legal use inside the NT-RCA, but with the requirement to use artificial bait. Therefore, this application also includes a request to test the use of natural bait on the groundfish troll gear. If this proposed rule and EFP proposal are approved, this EFP project would require exemptions from: (1) the prohibition on fishing with natural bait inside the NT-RCA (see proposed regulation below at § 660.330 (b)(3)(ii)(E)); and (2) the open access trip limits in Table 3 (South) to part 660, subpart F. If this EFP gear type is not approved for legal use inside the NT-RCA as proposed in this rulemaking, then this EFP project would require additional exemptions from: (1) the prohibition to fish inside the non-trawl RCA with non-trawl gear (see § 660.330(d)(12)(i)); (2) the prohibition on transiting through the non-trawl RCA without non-trawl gear stowed (see § 660.330(d)(12)(ii)); and (3) the prohibition on retaining and landing groundfish harvested from inside the non-trawl RCA with non-trawl gear (see § 660.330(d)(12)(iii)). If approved, NMFS would authorize up to 10 vessels to test the use of natural bait inside the non-trawl RCA off the California coast—
                        <PRTPAGE P="62692"/>
                        specifically in areas with canyon edges and walls that have historically produced high volumes of chilipepper rockfish catch and at depths ranging from 40 to 150 fathoms (73 to 274 m).
                    </P>
                    <P>
                        • 
                        <E T="03">Groundfish EFP Proposal—Year-round Coastwide Midwater Rockfish EFP: Monitoring and Minimizing Salmon Bycatch When Targeting Rockfish in the Shorebased IFQ Fishery, 2023-2024:</E>
                         West Coast Seafood Processors, Oregon Trawl Commission, Midwater Trawlers Cooperative, and the Environmental Defense Fund submitted a renewal application to continue research that has been conducted since 2017; the multi-year EFP project is collectively referred to as the “Trawl Gear EFP.” The purpose of the EFP is for vessels participating in the West Coast Groundfish Trawl Rationalization Program's Limited Entry Shorebased Individual Fishing Quota (IFQ) Program to test whether removing certain gear, time, and area restrictions may impact the nature and extent of bycatch of protected and prohibited species (
                        <E T="03">i.e.,</E>
                         Chinook salmon, coho, eulachon, and green sturgeon). The EFP project would require exemptions for vessels fishing with bottom trawl groundfish gear from: (1) the requirement to use selective flatfish trawl gear, and the prohibition on using small footrope gear other than selective flatfish trawl gear between 42° and 40°10′ North latitude and shoreward of the boundary line approximating the 100 fathom (fm) depth contour (see § 660.130(c)(2)(i) and (c)(2)(ii)); and (2) the requirement that selective flatfish trawl must be a two-seamed net with no more than two riblines, excluding the codend (see § 660.130(b)(1)(ii)(A)). The EFP project would require exemptions for vessels fishing with midwater trawl groundfish gear from: (1) the prohibition on fishing outside the primary season dates for the Pacific whiting IFQ fishery (see § 660.112(b)(1)(x) and § 660.130(c)(3)); and (2) the prohibition on fishing south of 40°10′ N lat. shoreward of the boundary line approximating the 150 fm depth contour (see § 660.130(c)(3)(ii) and (c)(4)(ii)(B)). The EFP project would require exemptions for vessels fishing with either midwater or bottom trawl groundfish gear from: (1) the prohibition on retaining certain prohibited species (see § 660.12 (a)(1)); and (2) the requirement to discard certain prohibited species at sea (see § 660.140(g)(1)). If this EFP is approved, NMFS would set a bycatch limit of 1,000 Chinook salmon north of 42° N lat. and 100 Chinook salmon south of 42° N lat. for vessels declared into the EFP, regardless of gear type. If either of these bycatch limits are reached, NMFS would revoke the EFP for both gear types in the respective management area (
                        <E T="03">i.e.,</E>
                         north or south of 42° N lat.). Participating vessels would also be required to retain all salmon (excluding salmon already sampled by NMFS' West Coast Groundfish Observer Program) until offloading. If approved, NMFS would authorize up to 60 vessels to participate in the EFP.
                    </P>
                    <P>
                        • 
                        <E T="03">Groundfish EFP Proposal—California Department of Fish and Wildlife 2023-2024 EFP:</E>
                         The California Department of Fish and Wildlife (CDFW) submitted a renewal application for research that has been conducted since 2021. The purpose of the EFP project is to collect fishery-dependent biological data for cowcod for inclusion in future stock assessments. The EFP project would require an exemption from the prohibition to retain cowcod in the California recreational fishery (see § 660.360(c)(3)). The EFP would also provide that any cowcod taken and retained would not count against the recreational bag limit for the aggregate of rockfish, cabezon, and greenlings. If approved, NMFS would authorize up to 20 vessels that participate in the California recreational fishery to retain cowcod and transfer the cowcod to CDFW groundfish staff upon landing.
                    </P>
                    <P>
                        • 
                        <E T="03">Groundfish EFP Proposal—Washington Department of Fish Wildlife Enhanced Yelloweye Recreational Fishery Biological Sampling EFP:</E>
                         The Washington Department of Fish and Wildlife (WDFW) submitted a renewal application for research that has been conducted since 2021. The purpose of the EFP project is to collect fishery-dependent biological data for yelloweye rockfish for inclusion in future stock assessments. The EFP project would require an exemption from the prohibition to retain yelloweye rockfish in the Washington recreational fishery (see § 660.360(c)(1)(ii)). The EFP would also provide that any yelloweye rockfish taken and retained would not count against the recreational bag limit for rockfish. If approved, NMFS would authorize up to 15 vessels that participate in the Washington recreational fishery to retain yelloweye rockfish and transfer the yelloweye rockfish to WDFW staff upon landing.
                    </P>
                    <P>
                        During the 2-year period of EFP activities from 2023 to 2024, all vessels participating in the non-trawl RCA EFP projects (
                        <E T="03">i.e.,</E>
                         the renewal applications submitted by Emley-Platt and Real Good Fish) would adhere to EFP set-asides for targeted and incidental groundfish and other species, which were considered and approved by the Council at their June 2022 meeting. The one exception would be for Emley-Platt vessels fishing north of 40°10′ N lat., which would fish pursuant to open access trip limits in Table 3 (North) to part 660, subpart F, as the EFP Director did not request additional EFP set-asides for this area. These EFP set-asides are off-the-top deductions from the 2023-2024 applicable ACLs, meaning any landings and discards that occur under these EFPs would be accounted for within the applicable ACLs. EFP set-asides would not be needed for the Trawl Gear EFP as landings and discards of IFQ species would be accounted for through the participating vessel's IFQ. Vessels participating in the non-trawl RCA EFP projects and the Trawl Gear EFP would be required to have 100 percent observer coverage. All cowcod mortality under the CDFW EFP project is expected to occur in conjunction with routine recreational fishing activities and would be calculated as part of the normal recreational catch estimation process. All yelloweye rockfish taken under the WDFW EFP project would be counted against the Washington recreational harvest guideline for yelloweye rockfish. NMFS would not require 100 percent observer coverage for vessels participating in the CDFW and WDFW EFP projects because recreational vessels do not meet the minimum size requirements under Federal regulations to carry an observer.
                    </P>
                    <P>
                        NMFS does not expect any impacts to the environment, essential fish habitat, or protected or prohibited species from these EFPs beyond those analyzed for the groundfish fishery as a whole in applicable biological opinions (available at: 
                        <E T="03">https://www.fisheries.noaa.gov/species/west-coast-groundfish#management</E>
                        ), the draft EA for the Pacific Coast Groundfish Fishery 2023-2024 Harvest Specifications and Management Measures (see 
                        <E T="02">ADDRESSES</E>
                        ), or the EA for the 2018 Trawl Gear EFP dated December 2017 (available at: 
                        <E T="03">https://www.fisheries.noaa.gov/region/west-coast</E>
                        ).
                    </P>
                    <P>
                        After publication of this document in the 
                        <E T="04">Federal Register</E>
                        , NMFS may approve and issue permits for the proposed EFP projects for the 2023 fishing year after the close of the public comment period. All five EFP applications are available under “Supporting and Related Materials” (see 
                        <E T="02">ADDRESSES</E>
                        ). NMFS will consider comments submitted in deciding whether to approve the applications as requested. NMFS may approve the applications in their entirety or may make any alterations needed to achieve the goals of the EFP projects. NMFS would not issue another 
                        <E T="04">
                            Federal 
                            <PRTPAGE P="62693"/>
                            Register
                        </E>
                         notice soliciting public comment on renewing these EFP projects for 2024 unless: (1) the applicants modify and resubmit their applications to NMFS; (2) changes to relevant fisheries regulations warrant a revised set of exemptions authorized under the EFP projects; or (3) NMFS' understanding of the current biological and economic impacts from EFP fishing activities substantially changes.
                    </P>
                    <HD SOURCE="HD2">I. Shortbelly Rockfish 2,000 mt Catch Threshold To Initiate Council Review</HD>
                    <P>Shortbelly rockfish is one of the most abundant rockfish species in the California Current Ecosystem and is a key forage species for many fish, birds, and marine mammals. The Council recommended and NMFS approved the designation of shortbelly rockfish as an ecosystem component (EC) species through Amendment 29 to the PCGFMP, as part of the 2021-2022 groundfish management measure process (85 FR 79880, December 11, 2020). The Notice of Availability for Amendment 29 (85 FR 54529, September 2, 2020) provides additional background on shortbelly rockfish. The Council monitors and tracks shortbelly rockfish mortality inseason. Shortbelly rockfish are not, and have not historically been, a directed target of commercial or recreational fisheries. Due to their small size, shortbelly rockfish are not currently marketable. However, concerns over the potential future development of a directed fishery prompted the Council to note during the 2021-2022 groundfish management measure process that it would consider taking action if mortality of shortbelly rockfish in the fishery exceeds, or is projected to exceed, 2,000 mt in a calendar year. This guidance was not formalized in the PCGFMP as part of Amendment 29. Therefore, the Council recommended and NMFS is proposing to amend the PCGFMP to add language stating that if shortbelly rockfish mortalities exceed, or are projected to exceed, 2,000 mt in a calendar year, the Council would review relevant fishery information and consider if management changes were warranted, including, but not limited to reconsideration of its current classification as an EC species. To estimate mortality and provide for catch accounting, NMFS proposes a sorting requirement for shortbelly rockfish in the LEFG and OA fisheries. For more information on this measure, see the NOA for Amendment 30 and the Analysis.</P>
                    <P>NMFS notes that routine management measures as laid out in 50 CFR 660.60(c) are not currently available for shortbelly rockfish management because shortbelly rockfish is an EC species. Shortbelly rockfish would need to be redesignated as “in the fishery” prior to routine management measures being available for inseason use. However, the Council could recommend, consistent with the points of concern framework (FMP Section 6.2.2), management measures to minimize bycatch or bycatch mortality of EC species as laid out in 50 CFR 600.305(c)(5). Depending on the issue triggering the need for management measures, this pathway might require revisiting the EC designation.</P>
                    <HD SOURCE="HD2">J. Non-Bottom Contact Hook-and-Line Gear Allowance in the Non-Trawl Rockfish Conservation Area</HD>
                    <P>
                        In order to provide additional opportunity to commercial non-trawl fisheries to target healthy stocks, relieve pressure on overfished or constraining nearshore stocks, and limit impacts to sensitive habitats, the Council recommended, and NMFS proposes, allowing non-trawl vessels to use select hook-and-line gear configurations within the NT-RCA which were tested through EFPs as described above in Section III.H. The non-trawl fisheries are distinguished by the types of gears permitted to be used to harvest their catch. OA fisheries are allowed to use any “open access” gear, including hook-and-line, pot, and troll gear. Limited entry fixed gear (LEFG) vessels are restricted to using the gear endorsed on their registered permit (longline or pot/trap) or are held to the lower landing limits associated with the OA sector when using alternative gears. Vessels participating in the shorebased IFQ sector with fixed gear (
                        <E T="03">i.e.,</E>
                         gear switchers) are permitted to use any legal groundfish gear. Participants in all three fisheries are prohibited from fishing in the NT-RCA unless permitted (
                        <E T="03">e.g.,</E>
                         fishing for other flatfish or through an EFP).
                    </P>
                    <P>This proposed action would allow vessels in the directed open access fishery targeting groundfish to operate inside the NT-RCA from 46°16′ N lat. to the U.S./Mexico border with non-bottom contact hook-and-line gear only, subject to the specifications below. Prohibited bottom contact hook-and-line gears would include bottom longline, commercial vertical hook-and-line gear (anchored to the bottom), and dinglebar gear. Vessels would need to declare their intent to fish within the NT-RCA and their gear type prior to departure. Vessels could fish inside and outside of the non-trawl RCA on the same trip but could only carry one type of legal non-bottom contact hook-and-line gear on-board the vessel when fishing occurs in the NT-RCA. Vessels that typically fish in the LEFG or IFQ sector would be required to declare into the OA fishery to utilize this proposed management measure and would be subject to the lower OA trip limits.</P>
                    <P>
                        The proposed action would include a new gear definition. Legal “non-bottom contact hook-and-line gear” would be defined as stationary vertical jig gear attached to the vessel and not anchored to the bottom, and groundfish troll gear. The following requirements would apply to stationary vertical jig gear: (1) must be a minimum of 50 feet between the bottom weight and the lowest fishing hook; (2) no more than 4 vertical mainlines may be used at one time with no more than 25 hooks on each mainline, and; (3) no more than 100 hooks may be in the water at one time, with no more than 25 extra hooks on board the vessel. “Groundfish troll gear” would be defined as a horizontally-suspended monofilament mainline attached to a troll wire. The following requirements would apply to groundfish troll gear: (1) must be a minimum of 50 feet between the bottom weight and the troll wire's connection to the horizontal mainline; (2) no more than 1 mainline may be used at one time; and (3) no more than 500 hooks may be in the water at one time, with no more than 25 extra hooks on board the vessel; hooks must be spaced apart by a visible marker (
                        <E T="03">e.g.,</E>
                         floats, line wraps, colored lines splices), with no more than 25 hooks between each marker and no more than 20 markers on the mainline.
                    </P>
                    <P>Under the proposed action both stationary vertical jig gear and groundfish troll gear could be equipped with artificial lures and flies. Natural bait or weighted hooks could not be used nor be on board the vessel during the trip. This restriction is expected to mitigate any potential additional seabird bycatch effects, as seabirds are known to dive on baited hooks and potentially become entangled.</P>
                    <P>In order to fish inside the NT-RCA, vessels would be required to declare into the directed open access fishery, and would not be permitted to declare into any other fishery if fishing inside the NT-RCA.</P>
                    <P>
                        This proposed management measure may provide increased opportunity for West Coast vessels to expand their portfolios, especially in light of the proposed restrictions related to quillback and copper rockfishes (see Section III.G), but it is likely that a limited group of vessels will take advantage of this opportunity given its limitations. Effort would likely be constrained by fuel prices, potential offshore travel danger to “sport-like” 
                        <PRTPAGE P="62694"/>
                        OA vessels, and the Vessel Monitoring System (VMS) requirement. Given the barriers to access the area, it is unlikely the non-trawl allocations for midwater rockfish would be exceeded.
                    </P>
                    <P>
                        Based on the Analysis (Section 8) and data from the non-trawl EFPs (
                        <E T="03">i.e.,</E>
                         Emley-Platt and Real Good Fish EFPs), the gear configurations proposed have relatively low bycatch of groundfish species of concern while being able to harvest healthy midwater rockfish. Under this proposal, non-trawl attainments of healthy midwater rockfish species would likely increase, while impacts to nearshore stocks of concern including quillback and copper rockfish would be limited. Under this proposed new gear and area flexibility, mortality of yelloweye rockfish and cowcod could increase but is expected to remain within the proposed harvest specifications. Additionally, because the gears are designed to not contact the bottom, the proposed gear types have minimal impacts on habitat.
                    </P>
                    <HD SOURCE="HD2">K. LEFG Sablefish Primary Season Extension</HD>
                    <P>
                        This proposed action would permanently extend the LEFG primary sablefish tier fishery (hereinafter referred to as primary fishery) season end date from October 31 to December 31. The primary fishery would close on December 31, or close for an individual vessel owner when the tier limit for the sablefish endorsed permit(s) registered to the vessel has been reached, whichever is earlier. This proposed action would also extend the incidental halibut retention allowance provision for the primary fishery north of Point Chehalis, Washington from October 31 to the date/time specified by the International Pacific Halibut Commission (IPHC) annually for the closure of commercial fisheries coastwide, or until the quota is taken, whichever comes first. After the specified date/time, any incidental halibut would need to be discarded as a prohibited species. The proposed action would not change any other aspects of the program (
                        <E T="03">e.g.,</E>
                         stacking privileges, transferability).
                    </P>
                    <P>The primary sablefish fishery tier program is a limited access privilege program set up under Amendment 14 to PCGFMP (66 FR 41152, August 7, 2001). Participants hold limited entry permits with a pot gear and/or longline gear endorsement and a sablefish endorsement.</P>
                    <P>Under Amendment 14, as set out in 50 CFR 660.231, the permit holder of a sablefish-endorsed permit receives a tier limit, which is an annual share of the sablefish catch allocation to this sector. NMFS sets three different tier limits through the biennial harvest specifications and management measures process (see Section III.F for the proposed 2023 limits); and up to three permits may be stacked at one time on a vessel participating in the fishery. Stacked tier limits are combined to provide a cumulative catch limit for that vessel. After vessels have caught their full tier limits, they are allowed to move into other fisheries for sablefish, specifically the limited entry or open access trip limit fishery, or fisheries for other species.</P>
                    <P>Under Amendment 14, the sablefish primary season has historically been open from April 1 through October 31 of each year, though individual permit holders may only fish up to their tier limits and so may be required to cease fishing prior to October 31. These season dates were put into regulation during the development and implementation of the fishery under Amendment 14 to the PCFMP. Prior to the implementation of Amendment 14, the sablefish fishery had operated as a `derby' style fishery, with a season length lasting a few weeks to a few days. Under Amendment 14, the fishery began operating under a seven-month season. The seven-month season structure, as opposed to a year-long season, was intended to allow for timely catch accounting so that the sector allocation was not exceeded. As of 2017, commercial vessels landing sablefish are required to submit e-tickets within 24 hours of offload, “to improve timeliness and accuracy of sablefish catch reporting in the limited entry fixed gear fisheries and open access fisheries” (§ 660.213). Given the increase in speed of modern catch accounting, the original reason for the seven-month season is no longer applicable.</P>
                    <P>In response to industry requests and Council recommendation, NMFS issued emergency rules in 2020 and 2021 (85 FR 68001, October 27, 2020; 86 FR 59873, October 29, 2021) to temporarily extend the sablefish primary fishery from October 31 to December 31. These emergency actions were intended to mitigate COVID-19 pandemic related disruptions in the fishery by allowing participants more time to harvest their full tier limits.</P>
                    <P>The Analysis discusses that the primary fishery has experienced lower than average attainment since 2019 amidst higher than average sablefish allocations. Even with the season extension in 2020 and 2021, attainment was only 80 and 74 percent of the sector allocation, respectively. A season extension could provide opportunity and flexibility for vessels to fish their full tier limits and maximize economic benefits.</P>
                    <P>As detailed in the Analysis, the additional two months proposed in this measure would give primary tier vessels the flexibility to make safer decisions and plan their season based on markets and weather with the ultimate goal of increasing attainment and profitability. Habitat and gear-related impacts resulting from this proposed measure would likely be similar to those of an October 31st season end date, because roughly the same number of fixed gear vessels are expected to participate in the groundfish fishery as a whole. The overall amount of permits in this sector is static; however, some permits are not used every year, or vessels may stack permits, which ultimately reduces the potential number of participants. This proposed measure could increase the amount of time that humpback whales are likely to co-occur with the primary tier fishery. However, the proposed measure would likely have negligible additional impact on humpback whales compared to the 7-month season because, (1) based on migration patterns the likelihood of humpback whale aggregations interacting with fishing gear decreases from October to December, (2) the majority of the effort during the entire sablefish primary fishery season would continue to occur via bottom longline gear and not pot gear, and (3) extending the season would be unlikely to increase the overall amount of pot gear used throughout the season due to restrictions on gear endorsements.</P>
                    <P>Vessels in the primary fishery north of Point Chehalis, Washington using bottom longline gear are also allowed to retain incidentally caught Pacific halibut up to a specific limit specified at 50 CFR 660.231(b)(3)(iv). Halibut are encountered regularly in the normal operation of the sablefish primary fishery due to the co-occurrence of halibut and sablefish in the same environments, and the design and function of fixed gear. This retention is allowed until the sablefish primary season ends and it contributes additional economic value to this sector. The extended retention allowance proposed in this action would ensure additional economic benefits and reduce regulatory discards of commercially valuable incidental halibut.</P>
                    <P>
                        The IPHC adopts a closure date for Pacific halibut in all commercial fisheries, which the primary fishery is subject to, and closure dates are typically set at mid- to late-November but was set at December 7 in 2021 and 2022. The IPHC typically sets the season 
                        <PRTPAGE P="62695"/>
                        closure date in late January of that year during its annual meeting. Per 50 CFR 300.62, NMFS publishes the IPHC's regulations setting forth annual management measures in the 
                        <E T="04">Federal Register</E>
                         by March 15 each year. For example, NMFS published the 2022 annual management measures governing the Pacific halibut fishery on March 7, 2022 (87 FR 12604).
                    </P>
                    <P>Extending the incidental Pacific halibut allowance for the primary tier fishery to the date annually specified by the IPHC would reduce regulatory discards, provide more opportunity for an important alternative income source, and result in minimal additional impacts to Pacific halibut mortality.</P>
                    <HD SOURCE="HD2">L. Correction to the Definition of Block Area Closures</HD>
                    <P>
                        NMFS proposes a minor change to the PCGFMP to resolve a mismatch between the FMP and current regulatory text. The salmon bycatch minimization measures action (86 FR 10857; February 23, 2021) established Block Area Closures (BACs) as a tool to minimize salmon bycatch. BACs are described in multiple regulation sections (
                        <E T="03">e.g.,</E>
                         50 CFR 660.11 Conservation area(s); § 660.111 Block area closures; § 660.60(c)(3)(i)). The regulations articulate the Council's intent to manage incidental salmon bycatch by vessels using groundfish midwater trawl gear in the EEZ off of Washington, Oregon, and California with Block Area Closures (BACs). However, inadvertently, the FMP was not updated to be consistent with regulations. To avoid potential future implementation delays, updates would be made to the FMP that are consistent with Council intent described in the salmon bycatch mitigation rulemaking document (86 FR 10857, February 23, 2021). The FMP would be revised to include language that BACs are available in the EEZ seaward of Washington, Oregon and California state waters for vessels using limited entry bottom trawl gear and in the EEZ seaward of Washington, Oregon and California state waters for vessels using midwater trawl gear. For more information on this measure, see the NOA for Amendment 30 and the Analysis.
                    </P>
                    <HD SOURCE="HD2">M. Annual Catch Targets for Quillback and Copper Rockfish</HD>
                    <P>The 2021 stock assessments indicated that the portion of quillback rockfish and copper rockfish off the coast of California are likely experiencing localized depletion. An Annual Catch Target (ACT), as defined at 50 CFR 660.11, is a management target set below the ACL to account for management uncertainty. ACTs may be used as an accountability measure to ensure against exceeding an ACL or accomplish management objectives. As they are part of a stock complex, the ACL contributions for copper rockfish and quillback rockfish are combined with the ACL contributions from the other stocks in the complex to set ACLs for the Nearshore Rockfish complexes north and south of 40°10′ N lat. In setting specifications, the Council, for analytic purposes, calculated three ACL contributions for quillback rockfish that corresponded to state boundaries, which were combined and then apportioned based on historical catch to determine the overall ACL contribution for quillback rockfish to each Nearshore Rockfish complex (see Section II.C).</P>
                    <P>The Council recommended, and NMFS proposes, setting ACTs for copper rockfish and quillback rockfish. For copper rockfish, the ACT would be set equal to its ACL contribution for the portion of the stock found off of California and would be set at 91.54 mt in 2023, and 94.72 mt in 2024. For quillback rockfish, an ACT would be set for the portion of the stock found off of California and would be set at 1.86 mt in 2023, and 1.97 mt in 2024.</P>
                    <P>Given quillback and copper rockfish are managed in a stock complex, the proposed ACTs would essentially formalize the ACL contributions for management purposes. Setting the ACTs equal to the ACL contributions would allow the Council to recommend necessary management measures inseason when the ACL contribution is met or projected to be met. Exceeding the ACL contribution for stocks in a complex would otherwise typically not trigger a Council response or accountability measure. In order to allow tracking of mortality against the ACT, this proposed rule also includes sorting requirements for quillback and copper rockfish.</P>
                    <P>
                        CDFW closely monitors commercial and recreational landings of quillback and copper rockfish and the Council would receive updates on landings at each Council meeting. The management response to an overage or projected overage would be highly situational. Therefore, as an accountability measure, should the ACT be exceeded or projected to be exceeded, the Council would consider routine inseason management measures (
                        <E T="03">e.g.,</E>
                         bag limit reductions or depth restrictions) at regular Council meetings.
                    </P>
                    <HD SOURCE="HD2">N. Novel Utilization of Existing Rockfish Conservation Area Boundary Lines</HD>
                    <P>The Council recommended, and NMFS proposes, a novel utilization of the previously established Rockfish Conservation Area (RCA) boundary lines for the recreational fishery seaward of California (§ 660.360(c)(3)). Recreational RCA boundary lines are a set of connecting waypoints which approximate a depth contour (§ 660.71 through § 660.73). These lines have historically been used to allow fishing shoreward of a specific RCA boundary line and prohibit fishing seaward of that line. This proposed rule would also allow fishing seaward of a specified RCA boundary line and prohibit fishing shoreward of that line. For example, fishing could be prohibited in Federal waters shoreward of the 30, 40, 50, 60, 75, 100, or 125, fathom line. Additionally, this novel use of the RCA would allow logistical flexibility for the management of overfished species like yelloweye rockfish (current RCA utilization) and non-overfished species that include species of concern such as quillback rockfish, copper rockfish, or cowcod (novel RCA utilization). This new management measure, if approved, may be used during the regular season setting process through the biennial specifications and management measures or as an inseason action to achieve harvest specifications.</P>
                    <P>
                        This proposed measure is intended to be a tool to reduce mortality for nearshore rockfish species of concern (
                        <E T="03">e.g.,</E>
                         quillback rockfish, copper rockfish, or cowcod) or rebuilding yelloweye rockfish by shifting fishing effort away from the habitats and depths where those stocks are most commonly encountered, and onto shelf and slope waters to target other, healthier groundfish stocks. This measure would provide more flexibility in managing groundfish fisheries seaward of California and is designed to be combined with other season structure options and bag limit options to create a suite of management measures which take steps to achieve harvest specifications and minimize impacts to California fisheries and coastal communities. The effectiveness of this proposed management tool would be limited based on the prevalence of each species in state waters as compared to in the EEZ. The majority of fishery effort for copper and quillback rockfish off California is in state waters, therefore, the overall effectiveness of this management measure may be constrained.
                    </P>
                    <P>
                        The Analysis discusses uncertainty with model projections when RCA boundary lines are utilized in this novel way, especially for species with a deeper depth distribution, like cowcod and yelloweye rockfish. The California Department of Fish and Wildlife's 
                        <PRTPAGE P="62696"/>
                        weekly and monthly tracking processes have been an effective and reliable tool to closely monitor recreational inseason mortality and provide timely and accurate information to apply inseason adjustments, such as changes to depth limits, season length, or bag limits, to fisheries.
                    </P>
                    <P>This proposed measure is intended to limit the negative socioeconomic impacts that could otherwise occur as a result of the need to reduce mortality for quillback and copper rockfishes, and stay within harvest guidelines for yelloweye rockfish and cowcod.</P>
                    <P>The Analysis discusses the impact of this measure on the recreational boat-based groundfish fisheries in California. Short-term and long-term impacts would likely occur as the sector adjusts to new regulations and fishery operations. Loss of fishing vessels, captains and crew leaving the industry and the potential closures of landings and fishing tackle providers are possible. Innovations in fishing gears or a shift in angler preference for target species could provide new opportunities for anglers, businesses, and communities. These changes could have positive long-term effects, but would not bring immediate relief to communities that would be negatively impacted by fisheries reductions related to quillback rockfish.</P>
                    <P>Changes to angler behavior are difficult to predict, but anglers may choose to opt out of the groundfish fishery due to fuel costs and other difficulties in reaching fishing grounds, safety concerns related to fishing offshore, logistical constraints associated with smaller vessels, such as vessel size and fuel capacity, and the physical effort of reeling fish up from deeper depths. It is likely the increased distance and travel time associated with offshore RCA lines would reduce small vessel effort. Effort may shift to other state and federally managed fisheries such as Pacific halibut, salmon, California scorpionfish, highly migratory species, coastal pelagic species, California sheephead, California halibut, striped bass, kelp bass, and others as anglers search for other available fishing targets.</P>
                    <P>In a report (Agenda Item F.6.a, June 2022) to the Council, the Groundfish Advisory Subpanel (GAP) noted that once shelf rockfish species are aboard, it restricts fishermen's ability to fish inshore waters. The GAP stated that mornings are when the outer waters are most accessible due to weather patterns. During the afternoons, winds generally make exposed deep waters unfishable and that is when inshore access is most needed.</P>
                    <P>As described in Section III.G, in addition to the regulatory management measures to reduce mortality of copper and quillback rockfish in 2022 (and proposed for 2023-2024), the fishery industry has untaken several voluntary measures including dissemination of enhanced species identification information, avoidance procedures, and no retention when a biological sampler is not aboard. It is expected that these mandatory and voluntary measures will substantially reduce mortality. If mortality is lower than expected through the regular inseason monitoring and reporting, the Council and NMFS would consider relieving restrictions during the biennium in order to reduce socioeconomic impacts, while keeping mortality within the recommended ACTs.</P>
                    <P>For more information on this measure, see the NOA for Amendment 30 and the Analysis.</P>
                    <HD SOURCE="HD2">O. Block Area Closures for Groundfish Mitigation</HD>
                    <P>This proposed rule would make Block Area Closures (BACs) available as a routine management measure to control catch of groundfish by midwater trawl and bottom trawl vessels. BACs could be implemented in the EEZ seaward of Washington, Oregon, and California. BACs could be implemented within tribal Usual and Accustomed (U&amp;A) fishing areas but would only apply to non-tribal vessels. This proposed rule would prohibit midwater trawl and/or bottom trawl fishing within the BAC boundaries.</P>
                    <P>
                        BACs are size variable spatial closures bounded by latitude lines, defined at 50 CFR 660.11, and depth contour approximations defined at 50 CFR 660.71 through 660.74 ((10 fm (18 m) through 250 fm (457 m)), and §  660.76 (700 fm (1280 m)). Amendment 28 to the FMP (84 FR 63966; November 19, 2019) first established BACs as a management tool. The salmon bycatch minimization measures action (86 FR 10857; February 23, 2021) established BACs as a tool to minimize salmon bycatch. This proposed measure would align the outermost available depth boundaries (
                        <E T="03">i.e.,</E>
                         700 fathoms) across all midwater and bottom trawl BACs used to control groundfish catch.
                    </P>
                    <P>
                        The BAC tool would allow the Council to recommend, and NMFS to implement, size variable area closures as a routine management measure to address specific areas of high catch or bycatch of one or more specific groundfish species rather than large fixed closure areas (
                        <E T="03">e.g.,</E>
                         Bycatch Reduction Area or BRA). BACs would allow for the trawl fishery to remain open in areas outside of the BACs.
                    </P>
                    <P>
                        This proposed rule would not implement specific individual BACs. BACs could not be used to close an area to any type of fishing other than groundfish bottom or midwater trawling. This proposed rule would allow NMFS to close or reopen BACs preseason (
                        <E T="03">e.g.,</E>
                         before the start of the fishing year or before the start of the Pacific whiting fishery) or inseason. The approach would be consistent with existing “routine inseason” frameworks already in the FMP and regulations. Most trip, bag, and size limits, and some Groundfish Conservation Area closures in the groundfish fishery, including BRAs and BACs, have been designated “routine” management measures in the PCGFMP and in § 660.60(c). The Council can use routine management measures to rapidly implement or modify these management measures through a single Council meeting process. Inseason changes to routine management measures are announced in the 
                        <E T="04">Federal Register</E>
                         pursuant to the requirements of the Administrative Procedures Act. If good cause exists under the Administrative Procedure Act to waive notice and comment, a single 
                        <E T="04">Federal Register</E>
                         notice will announce routine inseason BACs approved by NMFS.
                    </P>
                    <P>
                        When deciding whether to recommend BACs for NMFS to implement, consistent with the PCGFMP, the Council will consider environmental impacts, including economic impacts, and public comment via the Council process. Depending on the circumstances, NMFS may close areas for a defined period of time, for example, a few months or the remainder of the fishing year, or maintain the closure for an indefinite period of time, for example, until reopened by a subsequent action. NMFS may close one or more BACs and the size of the BACs can vary. A 
                        <E T="04">Federal Register</E>
                         notice will announce the geographic boundaries (described with coordinates in codified regulations) of one or more BACs, the effective dates, applicable gear/fishery restrictions, as well as the purpose and rationale. NMFS would also disseminate this information on BACs through public notices and posting on the West Coast Region website (see 
                        <E T="02">ADDRESSES</E>
                         for electronic access information).
                    </P>
                    <P>
                        This action is needed because fishery managers do not currently have appropriate scaled spatial tools to mitigate trawl-based groundfish catches, while also minimizing economic impacts to the fishing industry. BAC could be an important tool to manage a species like Pacific spiny dogfish, which 
                        <PRTPAGE P="62697"/>
                        exhibit spatial and seasonal aggregations, that may be limiting based on recent stock assessment outlook.
                    </P>
                    <P>During development of this measure, the Council noted BACs should be considered a last-resort measure behind industry implemented avoidance measures. The Council also noted BAC were not intended to be used for habitat protection because of their flexible nature.</P>
                    <HD SOURCE="HD2">P. Corrections</HD>
                    <P>This rule proposes minor corrections to the regulations at 50 CFR 600. These regulations are associated with Amendment 29 (85 FR 79880, December 11, 2020), Amendment 21-4 to the PCGFMP (84 FR 68799, December 17, 2019), and the 2019-2020 biennial harvest specifications (83 FR 63970, December 12, 2018). These minor corrections are necessary to reduce confusion and inconsistencies in the regulatory text and ensure the regulations accurately implement the Council's intent.</P>
                    <P>The Council recommended and NMFS approved the designation of shortbelly rockfish as an ecosystem component species through Amendment 29, as part of the 2021-2022 groundfish management measure process. That rule erroneously did not update the definition of “Ecosystem component species” at § 660.11 to reflect that designation. This rule proposes to include shortbelly rockfish in the list of species designated as ecosystem component species at § 660.11. Additionally, Amendment 29 erroneously included shortbelly rockfish trip limits for limited entry fixed gear and open access vessels. As an ecosystem component species, shortbelly rockfish is not managed “in the fishery,” and therefore should not be subject to trip limits. This rule proposes to remove the shortbelly rockfish trip limit from Table 2 (North) and Table 2 (South) to Part 660, Subpart E, as well as Table 3 (North) and Table 3 (South) to Part 660, Subpart F.</P>
                    <P>The final rule for Amendment 29 made changes to the trawl/non-trawl allocations established through Amendment 21 to the PCGFMP (75 FR 32993, June 10, 2010). That rule erroneously did not update § 660.55(c)(1) Table 1 to reflect those changes. This rule proposes to correct § 660.55(c)(1) Table 1 by removing the allocations for canary rockfish, as well as petrale sole, widow rockfish, lingcod south of 40°10′ N lat., and the slope rockfish complex south of 40°10′ N lat.. Per Amendment 29, these allocations between the trawl and non-trawl fisheries are determined through the biennial harvest specifications process to better align these allocations with current harvest trends. The Council's recommended and NMFS' proposed allocations through the 2023-2024 specifications process are shown Tables 1b and 2b in the proposed regulatory text for this proposed rule.</P>
                    <P>Amendment 21-4 moved darkblotched rockfish, pacific ocean perch, and widow rockfish from at-sea allocations to set-asides. That rule erroneously did not update § 660.140 to reflect those changes. This rule proposes to amend § 660.140 to remove these species from paragraph (c)(3)(iii) and add them to paragraph (c)(3)(iv).</P>
                    <P>Amendment 29 removed the at-sea set-asides from Table 1d to Subpart C of part 660. However, cross references indicating that the at-sea set-asides are located at Table 1d to Subpart C remain, erroneously. This rule proposes removing these cross references in § 660.150 and § 660.160 and clarifying that the at-sea set-asides are described in the biennial specifications.</P>
                    <P>The final rule for the 2019-2020 biennial harvest specifications contained a revision to the depth boundary within which commercial fixed gear and recreational gear are allowed to operate in the Western Cowcod Conservation Area. Fishing was permitted shoreward of the 20 fathom (fm) (36.6 m) depth contour prior to the 2019-2020 biennial harvest specifications final rule. The final rule revised the depth boundary to allow fishing shoreward of the 40 fm (73 m) depth contour. In the regulations for this change at § 660.360(c)(3)(i)(B), NMFS did not explicitly describe how the 40 fm (73 m) depth contour is delineated, or cross reference the depth contour definition in existing regulations. This rule proposes to correct these regulations to note that a coordinate list describing the 40 fm (73 m) depth contour can be found in §  660.71.</P>
                    <HD SOURCE="HD1">IV. Classification</HD>
                    <P>Pursuant to section 304 (b)(1)(A) of the Magnuson-Stevens Act, the NMFS Assistant Administrator has determined that this proposed rule is consistent with the PCGFMP, other provisions of the Magnuson-Stevens Act, and other applicable law, subject to further consideration after public comment. In making its final determination, NMFS will take into account the complete record, including the data, views, and comments received during the comment period.</P>
                    <P>Regulations governing the U.S. fisheries for Pacific halibut are developed by the IPHC, the Pacific Fishery Management Council, the North Pacific Fishery Management Council, and the Secretary of Commerce. Section 5 of the Northern Pacific Halibut Act of 1982 (Halibut Act, 16 U.S.C. 773c) allows the Regional Council, having authority for a particular geographical area, to develop regulations governing the allocation and catch of halibut in U.S. Convention waters as long as those regulations do not conflict with IPHC regulations. The proposed action is consistent with the Council's authority to allocate halibut catches among fishery participants in the waters in and off the United States.</P>
                    <P>Pursuant to Executive Order 13175, this proposed rule was developed after meaningful consultation and collaboration with tribal officials from the area covered by the PCGFMP. Under the Magnuson-Stevens Act at 16 U.S.C. 1852(b)(5), one of the voting members of the Pacific Council must be a representative of an Indian tribe with federally recognized fishing rights from the area of the Council's jurisdiction. In addition, regulations implementing the PCGFMP establish a procedure by which the tribes with treaty fishing rights in the area covered by the PCGFMP request new allocations or regulations specific to the tribes, in writing, before the first of the two meetings at which the Council considers groundfish management measures. The regulations at 50 CFR 660.50 further direct NMFS to develop tribal allocations and regulations in consultation with the affected tribes. The tribal management measures in this proposed rule have been developed following these procedures. The tribal representative on the Council made a motion to adopt the non-whiting tribal management measures, which was passed by the Council. Those management measures, which were developed and proposed by the tribes, are included in this proposed rule.</P>
                    <P>This proposed rule has been determined to be not significant for purposes of Executive Order 12866.</P>
                    <P>
                        NMFS prepared an analyses for this action, which address the statutory requirements of the Magnuson-Stevens Act, Presidential Executive Order 12866, and the Regulatory Flexibility Act. The full suite of alternatives analyzed by the Council can be found on the Council's website at 
                        <E T="03">www.pcouncil.org.</E>
                         NMFS addressed the statutory requirements of the National Environmental Policy Act through preparation of an EIS and an EA. NMFS prepared an EIS for the 2015-16 biennial harvest specifications and management measures and is available from NMFS (see 
                        <E T="02">ADDRESSES</E>
                        ). This EIS examined the harvest specifications and 
                        <PRTPAGE P="62698"/>
                        management measures for 2015-16 and 10-year projections for routinely adjusted harvest specifications and management measures. The 10-year projections evaluated the impacts of the ongoing implementation of harvest specifications and management measures and to evaluate the impacts of the routine adjustments that are the main component of each biennial cycle. Therefore, the EA for the 2023-24 cycle tiers from the 2015-16 EIS and focuses on the harvest specifications and management measures that were not within the scope of the 10-year projections in the 2015-16 EIS. A copy of the draft EA is available from NMFS (see 
                        <E T="02">ADDRESSES</E>
                        ). This action also announces a public comment period on the draft EA.
                    </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 adopted, would not have a significant economic impact on a substantial number of small entities. An estimated six businesses primarily engaged in seafood product preparation and packaging and employing 750 or fewer persons may be affected by this action. An estimated 629 commercial fishing businesses with less than $11 million in annual gross receipts may be affected by this action. An estimated 431 charter fishing boats may be affected by this action, all of which are assumed to have annual receipts of less than $7.5 million and therefore be considered small businesses. One governmental jurisdiction, with a population of less than 50,000 persons and therefore considered small, may be affected by this action. An estimated five not-for-profit organizations with combined annual receipts of less than $7.5 million may be affected by this action. An estimated eight small trust, estates, and agency accounts with annual receipts of less than $32.5 million may be affected by this action. The purpose of this proposed rule is to conserve Pacific Coast groundfish stocks by preventing overfishing, while still allowing harvest opportunity among the various fishery sectors. This will be accomplished by implementing the 2023-2024 annual specifications in the U.S. exclusive economic zone off the West Coast. The harvest specifications affect large and small entities similarly, and for this biennium, several of the catch limits are proposed to increase, providing benefit to all participants. Additionally, this proposed rule contains several of new management measures that are likely to benefit vessels, specifically openings of previously closed fishing grounds. As a result, an initial regulatory flexibility analysis is not required and none has been prepared.</P>
                    <P>This proposed rule contains no new information collection burden under the Paperwork Reduction Act of 1995. This action will require non-trawl sector participants to declare into the open access fishery and specify the non-bottom contact gear type to be used if fishing in the non-trawl RCA. The collection of such information was previously approved by the Office of Management and Budget (OMB) under OMB Control Number 0648-0573.</P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 50 CFR Part 660</HD>
                        <P>Fisheries, Fishing, Reporting and recordkeeping requirements.</P>
                    </LSTSUB>
                    <SIG>
                        <DATED>Dated: September 16, 2022.</DATED>
                        <NAME>Samuel D. Rauch, III,</NAME>
                        <TITLE>Deputy Assistant Administrator for Regulatory Programs, National Marine Fisheries Service.</TITLE>
                    </SIG>
                    <P>For the reasons set out in the preamble, 50 CFR part 660 is proposed to be amended as follows:</P>
                    <PART>
                        <HD SOURCE="HED">PART 660—FISHERIES OFF WEST COAST STATES</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 660 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            16 U.S.C. 1801 
                            <E T="03">et seq.,</E>
                             16 U.S.C. 773 
                            <E T="03">et seq.,</E>
                             and 16 U.S.C. 7001 
                            <E T="03">et seq.</E>
                        </P>
                    </AUTH>
                    <AMDPAR>2. Amend § 660.11 by:</AMDPAR>
                    <AMDPAR>a. Revising paragraph (1)(vi)(c) under the definition of “Conservation areas(s)”;</AMDPAR>
                    <AMDPAR>b. Revising paragraph (1) under the definition of “Fishing gear” and adding a paragraph (12);</AMDPAR>
                    <AMDPAR>c. Revising paragraph (10) under the definition of “Groundfish”.</AMDPAR>
                    <P>The revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 660.11</SECTNO>
                        <SUBJECT>General definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Conservation area(s)</E>
                             * * *
                        </P>
                        <P>(1) * * *</P>
                        <P>(vi) * * *</P>
                        <P>
                            (C) 
                            <E T="03">Recreational RCAs.</E>
                             Recreational RCAs are closed areas intended to protect overfished rockfish species. In the EEZ seaward of California, recreational RCAs are also intended to limit catch of non-overfished groundfish species. Recreational RCAs may either have boundaries defined by general depth contours or boundaries defined by specific latitude and longitude coordinates approximating depth contours. Boundaries for the recreational RCAs throughout the year are provided in the text in subpart G of this part under each state (Washington, Oregon and California) and may be modified by NMFS inseason pursuant to § 660.60(c).
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Fishing gear</E>
                             includes the following types of gear and equipment:
                        </P>
                        <P>
                            (1) 
                            <E T="03">Bottom contact gear</E>
                             means fishing gear designed or modified to make contact with the bottom. This includes, but is not limited to, beam trawl, bottom trawl, dredge, fixed gear, set net, demersal seine, dinglebar gear, and other gear (including experimental gear) designed or modified to make contact with the bottom. Gear used to harvest bottom dwelling organisms (
                            <E T="03">e.g.</E>
                             by hand, rakes, and knives) are also considered bottom contact gear for purposes of this subpart. Non-bottom contact gear is defined in paragraph (12) of this definition.
                        </P>
                        <STARS/>
                        <P>
                            (12) 
                            <E T="03">Non-bottom contact gear</E>
                             means fishing gear designed or modified to not make contact with the bottom. This includes, but is not limited to, commercial vertical hook-and-line gear not anchored to the bottom (
                            <E T="03">e.g.,</E>
                             vertical jig gear or rod-and-reel gear with weights suspended off the bottom) and troll gear.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Groundfish</E>
                             * * *
                        </P>
                        <STARS/>
                        <P>(10) “Ecosystem component species” means species that are included in the PCGFMP but are not “in the fishery” and therefore not actively managed and do not require harvest specifications. Ecosystem component species are not targeted in any fishery, not generally retained for sale or personal use, and are not determined to be subject to overfishing, approaching an overfished condition, or overfished, nor are they likely to become subject to overfishing or overfished in the absence of conservation and management measures. Ecosystem component species include: All skates listed here in paragraph (2), except longnose skate and big skate; all grenadiers listed here in paragraph (5); soupfin shark; ratfish; finescale codling; and shortbelly rockfish as listed here in paragraph (7)(ii).</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>3. In §  660.25, revise paragraphs (b)(4)(v)(C) and (b)(4)(vi)(D) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 660.25</SECTNO>
                        <SUBJECT>Permits.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(4) * * *</P>
                        <P>(v) * * *</P>
                        <P>
                            (C) 
                            <E T="03">Sablefish-endorsed permits.</E>
                             If a permit owner submits an application to register a sablefish-endorsed limited 
                            <PRTPAGE P="62699"/>
                            entry permit to a new permit owner or vessel owner during the primary sablefish season described at § 660.231 (generally April 1 through December 31), the initial permit owner must certify on the application form the cumulative quantity, in round weight, of primary season sablefish landed against that permit as of the application signature date for the then current primary season. The new permit owner or vessel owner must sign the application form acknowledging the amount of landings to date given by the initial permit owner. This certified amount should match the total amount of primary season sablefish landings reported on state landing receipts. As required at § 660.12(b), any person landing sablefish must retain on board the vessel from which sablefish is landed, and provide to an authorized officer upon request, copies of any and all reports of sablefish landings from the primary season containing all data, and in the exact manner, required by the applicable state law throughout the primary sablefish season during which a landing occurred and for 15 days thereafter.
                        </P>
                        <STARS/>
                        <P>(vi) * * *</P>
                        <P>
                            (D) 
                            <E T="03">Sablefish-endorsed permits.</E>
                             If a permit owner submits an application to register a sablefish-endorsed limited entry permit to a new vessel during the primary sablefish season described at § 660.231 (generally April 1 through December 31), the initial permit owner must certify on the application form the cumulative quantity, in round weight, of primary season sablefish landed against that permit as of the application signature date for the then current primary season. The new permit owner or vessel owner associated with the new vessel must sign the application form acknowledging the amount of landings to date given by the initial permit owner. This certified amount should match the total amount of primary season sablefish landings reported on state landing receipts. As required at § 660.12(b), any person landing sablefish must retain on board the vessel from which sablefish is landed, and provide to an authorized officer upon request, copies of any and all reports of sablefish landings from the primary season containing all data, and in the exact manner, required by the applicable state law throughout the primary sablefish season during which a landing occurred and for 15 days thereafter.
                        </P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>4. In § 660.50, revise paragraph (f)(2)(ii) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 660.50</SECTNO>
                        <SUBJECT>Pacific Coast treaty Indian fisheries.</SUBJECT>
                        <STARS/>
                        <P>(f) * * *</P>
                        <P>(2) * * *</P>
                        <P>(ii) The Tribal allocation is 849 mt in 2023 and 778 mt in 2024 per year. This allocation is, for each year, 10 percent of the Monterey through Vancouver area (North of 36° N lat.) ACL. The Tribal allocation is reduced by 1.7 percent for estimated discard mortality.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>5. In § 660.55, revise Table 1 to paragraph (c)(1) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 660.55</SECTNO>
                        <SUBJECT>Allocations.</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(1) * * *</P>
                        <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s56,15,15">
                            <TTITLE>
                                Table 1 to Paragraph (
                                <E T="01">c</E>
                                )(1)—Allocation Amounts and Percentages for Limited Entry Trawl and Non-Trawl Sectors Specified for FMP Groundfish Stocks and Stock Complexes
                            </TTITLE>
                            <BOXHD>
                                <CHED H="1">Stock or complex</CHED>
                                <CHED H="1">
                                    All non-treaty 
                                    <LI>LE trawl sectors</LI>
                                </CHED>
                                <CHED H="1">
                                    All non-treaty 
                                    <LI>non-trawl sectors</LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">Arrowtooth Flounder</ENT>
                                <ENT>95%</ENT>
                                <ENT>5%</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Chilipepper Rockfish S  of 40°10′ N  lat</ENT>
                                <ENT>75%</ENT>
                                <ENT>25%</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Darkblotched Rockfish</ENT>
                                <ENT>95%</ENT>
                                <ENT>5%</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Dover Sole</ENT>
                                <ENT>95%</ENT>
                                <ENT>5%</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">English Sole</ENT>
                                <ENT>95%</ENT>
                                <ENT>5%</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Lingcod N of 40°10′ N  lat</ENT>
                                <ENT>45%</ENT>
                                <ENT>55%</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Longspine Thornyhead N  of 34°27′ N  lat</ENT>
                                <ENT>95%</ENT>
                                <ENT>5%</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Pacific Cod</ENT>
                                <ENT>95%</ENT>
                                <ENT>5%</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Pacific Ocean Perch</ENT>
                                <ENT>95%</ENT>
                                <ENT>5%</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Sablefish S of 36° N  lat</ENT>
                                <ENT>42%</ENT>
                                <ENT>58%</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Shortspine Thornyhead N  of 34°27′ N  lat</ENT>
                                <ENT>95%</ENT>
                                <ENT>5%</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Shortspine Thornyhead S  of 34°27′ N  lat</ENT>
                                <ENT>50 mt</ENT>
                                <ENT>Remaining Yield</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Splitnose Rockfish S  of 40°10′ N  lat</ENT>
                                <ENT>95%</ENT>
                                <ENT>5%</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Starry Flounder</ENT>
                                <ENT>50%</ENT>
                                <ENT>50%</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Yellowtail Rockfish N  of 40°10′ N  lat</ENT>
                                <ENT>88%</ENT>
                                <ENT>12%</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Minor Slope Rockfish N rth of 40°10′ N  lat</ENT>
                                <ENT>81%</ENT>
                                <ENT>19%</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Other Flatfish</ENT>
                                <ENT>90%</ENT>
                                <ENT>10%</ENT>
                            </ROW>
                        </GPOTABLE>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>6. Amend § 660.71 by:</AMDPAR>
                    <AMDPAR>a. Removing paragraphs (e)(193), (e)(277), and (r)(20);</AMDPAR>
                    <AMDPAR>b. Redesignating paragraphs (e)(194) through (276) as (e)(193) through (275), (e)(278) through (336) as (e)(276) through (334), (o)(113) through (218) as (o)(114) through (219), (q)(25) as (q)(26), and (r)(21) through (r)(23) as (r)(20) through (r)(22);</AMDPAR>
                    <AMDPAR>c. Revising paragraphs (e)(144) and (e)(192); newly redesignated paragraphs (e)(263), (e)(274), (e)(280), (e)(287), (e)(307), and paragraphs (h)(13), (i)(1), (i)(9), (i)(14), (i)(20), (i)(34), (j)(27), (j)(30), (j)(40)</AMDPAR>
                    <AMDPAR>d. Revising paragraphs (o)(95), (o)(97), (o)(112);</AMDPAR>
                    <AMDPAR>e. Adding new paragraphs (o)(113);</AMDPAR>
                    <AMDPAR>f. Revising newly redesignated paragraphs (o)(181), (o)(193), (0)(215), and (o)(216) and paragraphs (q)(8), (q)(14), (q)(19), (q)(24);</AMDPAR>
                    <AMDPAR>g. Adding new paragraph (q)(25); and</AMDPAR>
                    <AMDPAR>h. Revising newly redesignated paragraphs (r)(8), (r)(15).</AMDPAR>
                    <P>The additions and revisions read as follows:</P>
                    <SECTION>
                        <SECTNO> § 660.71</SECTNO>
                        <SUBJECT>Latitude/longitude coordinates defining the 10-fm (18-m) through 40-fm (73-m) depth contours.</SUBJECT>
                        <STARS/>
                        <P>(e) * * *</P>
                        <STARS/>
                        <PRTPAGE P="62700"/>
                        <P>(144) 39°16.88′ N lat., 123°49.29′ W long.;</P>
                        <STARS/>
                        <P>(192) 36°33.20′ N lat., 121°57.50′ W long.;</P>
                        <STARS/>
                        <P>(263) 34°06.13′ N lat., 119°15.26′ W long.;</P>
                        <STARS/>
                        <P>(274) 34°04.66′ N lat., 119°04.51′ W long.;</P>
                        <STARS/>
                        <P>(280) 33°59.78′ N lat., 118°47.26′ W long.;</P>
                        <STARS/>
                        <P>(287) 33°50.29′ N lat., 118°24.58′ W long.;</P>
                        <STARS/>
                        <P>(307) 33°35.26′ N lat., 118°02.55′ W long.;</P>
                        <STARS/>
                        <P>(h) * * *</P>
                        <STARS/>
                        <P>(13) 33 °56.75′ N lat., 119°49.13′ W long.;</P>
                        <STARS/>
                        <P>(i) * * *</P>
                        <STARS/>
                        <P>(1) 33°02.98′ N lat., 118°37.64′ W long.;</P>
                        <STARS/>
                        <P>(9) 32°54.79′ N lat., 118°33.34′ W long.;</P>
                        <STARS/>
                        <P>(14) 32°48.05′ N lat., 118°26.81′ W long.;</P>
                        <STARS/>
                        <P>(20) 32°49.04′ N lat., 118°20.71′ W long.;</P>
                        <STARS/>
                        <P>(34) 33°02.98′ N lat., 118°37.64′ W long.;</P>
                        <STARS/>
                        <P>(j) * * *</P>
                        <STARS/>
                        <P>(27) 33°28.77′ N lat., 118°32.95′ W long.;</P>
                        <STARS/>
                        <P>(30) 33°27.58′ N lat., 118°29.51′ W long.;</P>
                        <STARS/>
                        <P>(40) 33°20.21′ N lat., 118°18.50′ W long.;</P>
                        <STARS/>
                        <P>(o) * * *</P>
                        <STARS/>
                        <P>(95) 40 °22.41′ N lat., 124°24.19′ W long.;</P>
                        <STARS/>
                        <P>(97) 40°18.71′ N lat., 124°22.63′ W long.;</P>
                        <STARS/>
                        <P>(112) 39°22.63′ N lat., 123°51.03′ W long.;</P>
                        <P>(113) 39°11.86′ N lat., 123°48.83′ W long.;</P>
                        <STARS/>
                        <P>(181) 34°08.23′ N lat., 119°13.21′ W long.;</P>
                        <STARS/>
                        <P>(193) 33°49.87′ N lat., 118° 24.15′ W long.;</P>
                        <STARS/>
                        <P>(215) 32°51.90′ N lat., 117°16.32′ W long.;</P>
                        <P>(216) 32°52.11′ N lat., 117°19.33′ W long.;</P>
                        <STARS/>
                        <P>(q) * * *</P>
                        <STARS/>
                        <P>(8) 32° 54.78′ N lat., 118°33.44′ W long.;</P>
                        <STARS/>
                        <P>(14) 32°45.53′ N lat., 118°24.82′ W long.;</P>
                        <STARS/>
                        <P>(19) 32°49.70′ N lat., 118°21.04′ W long.;</P>
                        <STARS/>
                        <P>(24) 33°02.98′ N lat., 118°35.40′ W long.;</P>
                        <P>(25) 33°03.36′ N lat., 118°37.57′ W long.; and</P>
                        <STARS/>
                        <P>(r) * * *</P>
                        <STARS/>
                        <P>(8) 33°20.88′ N lat., 118°30.54′ W long.;</P>
                        <STARS/>
                        <P>(15) 33°22.24′ N lat., 118°19.99′ W long.;</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>7. Amend § 660.72 by:</AMDPAR>
                    <AMDPAR>a. Revising paragraphs (a)(74) and (75), (a)(106) and (107), (a)(130), (a)(132) and (133),</AMDPAR>
                    <AMDPAR>b. Redesignating paragraphs (a)(134) through (200) as (a)(135) through (201);</AMDPAR>
                    <AMDPAR>c. Adding new paragraph (a)(134);</AMDPAR>
                    <AMDPAR>d. Revising paragraphs (a)(147) and (148), (a)(162), (a)(169), (a)(171), (a)(173), (a)(174)</AMDPAR>
                    <AMDPAR>e. Revising paragraphs (c)(18), (c)(33), (d)(2) through (4), (f)(89), (f)(96), (f)(129), (f)(143) and (144), (f)(146), (f)(155), (f)(159), (f)(169), (f)(175) and (176), (f)(208), (g)(17), (h)(2), (h)(4) through (6), (i)(6);</AMDPAR>
                    <AMDPAR>f. Removing paragraph (j)(140);</AMDPAR>
                    <AMDPAR>g. Redesignating paragraphs (j)(99) through (139) as (j)(100) through (140);</AMDPAR>
                    <AMDPAR>h. Adding new paragraph (j)(99);</AMDPAR>
                    <AMDPAR>i. Revising newly redesignated paragraphs (j)(100), and (j)(109) and paragraphs (j)(154), (j)(157), (j)(166), (j)(186) and (187), (j)(189) and (190), (j)(206), (j)(208) through (210), (j)(215), (j)(220) through (222), (j)(227), (k)(29), (l)(3), (m)(1), (m)(3) and (4), (m)(6), (m)(15), and (m)(18).</AMDPAR>
                    <P>The additions and revisions read as follows:</P>
                    <SECTION>
                        <SECTNO> § 660.72</SECTNO>
                        <SUBJECT>Latitude/longitude coordinates defining the 50 fm (91 m) through 75 fm (137 m) depth contours.</SUBJECT>
                        <STARS/>
                        <P>(a) * * *</P>
                        <STARS/>
                        <P>(74) 40°23.71′ N lat., 124°28.32′ W long.;</P>
                        <P>(75) 40°22.53′ N lat., 124°24.67′ W long.;</P>
                        <STARS/>
                        <P>(106) 37°49.84′ N lat., 123°16.05′ W long.;</P>
                        <P>(107) 37°35.67′ N lat., 122°55.43′ W long.;</P>
                        <STARS/>
                        <P>(130) 36°00.00′ N lat., 121°34.95′ W long.;</P>
                        <STARS/>
                        <P>(132) 35°40.44′ N lat., 121° 22.43′ W long.;</P>
                        <P>(133) 35°27.11′ N lat., 121°03.55′ W long.;</P>
                        <P>(134) 35°14.91′ N lat., 120°56.67′ W long.;</P>
                        <STARS/>
                        <P>(147) 34°07.83′ N lat., 119°13.48′ W long.;</P>
                        <P>(148) 34°07.71′ N lat., 119°13.29′ W long.;</P>
                        <STARS/>
                        <P>(162) 33°51.33′ N lat., 118°36.00′ W long.;</P>
                        <STARS/>
                        <P>(169) 33°48.25′ N lat., 118°26.97′ W long.;</P>
                        <STARS/>
                        <P>(171) 33°44.11′ N lat., 118°25.23′ W long.;</P>
                        <STARS/>
                        <P>(173) 33°38.16′ N lat., 118°15.65′ W long.;</P>
                        <P>(174) 33°37.47′ N lat., 118° 16.62′ W long.;</P>
                        <STARS/>
                        <P>(c) * * *</P>
                        <STARS/>
                        <P>(18) 33°58.76′ N lat., 119°32.27′ W long.;</P>
                        <STARS/>
                        <P>(33) 34°02.47′ N lat., 120°30.00′ W long.;</P>
                        <STARS/>
                        <P>(d) * * *</P>
                        <STARS/>
                        <P>(2) 33°02.53′ N lat., 118°34.25′ W long.;</P>
                        <P>(3) 32°55.51′ N lat., 118°28.92′ W long.;</P>
                        <P>(4) 32°54.99′ N lat., 118°27.72′ W long.;</P>
                        <STARS/>
                        <P>(f) * * *</P>
                        <STARS/>
                        <PRTPAGE P="62701"/>
                        <P>(89) 40°34.26′ N lat., 124°29.52′ W long.;</P>
                        <STARS/>
                        <P>(96) 40°21.58′ N lat., 124°24.87′ W long.;</P>
                        <STARS/>
                        <P>(129) 36°51.42′ N lat., 121°57.62′ W long.;</P>
                        <STARS/>
                        <P>(143) 36°10.30′ N lat., 121°43.00′ W long.;</P>
                        <P>(144) 36°02.54′ N lat., 121°36.43′ W long.;</P>
                        <STARS/>
                        <P>(146) 35°58.21′ N lat., 121°32.88′ W long.;</P>
                        <STARS/>
                        <P>(155) 34°23.05′ N lat., 119°56.25′ W long.;</P>
                        <STARS/>
                        <P>(159) 34°03.80′ N lat., 119°12.70′ W long.;</P>
                        <STARS/>
                        <P>(169) 33°55.20′ N lat., 118°33.18′ W long.;</P>
                        <STARS/>
                        <P>(175) 33°49.93′ N lat., 118°26.36′ W long.;</P>
                        <P>(176) 33°50.68′ N lat., 118°26.15′ W long.;</P>
                        <STARS/>
                        <P>(208) 32°43.03′ N lat., 117°20.43′ W long.;</P>
                        <STARS/>
                        <P>(g) * * *</P>
                        <STARS/>
                        <P>(17) 33°59.22′ N lat., 119°55.49′ W long.;</P>
                        <STARS/>
                        <P>(h) * * *</P>
                        <STARS/>
                        <P>(2) 33°02.56′ N lat., 118°34.19′ W long.;</P>
                        <STARS/>
                        <P>(4) 32°55.01′ N lat., 118°27.70′ W long.;</P>
                        <P>(5) 32°49.77′ N lat., 118°20.92′ W long.;</P>
                        <P>(6) 32°48.38′ N lat., 118°20.02′ W long.;</P>
                        <STARS/>
                        <P>(i) * * *</P>
                        <STARS/>
                        <P>(6) 33°25.39′ N lat., 118°22.80′ W long.;</P>
                        <STARS/>
                        <P>(j) * * *</P>
                        <STARS/>
                        <P>(99) 40°39.40′ N lat., 124°28.90′ W long.;</P>
                        <P>(100) 40°36.96′ N lat., 124°28.02′ W long.;</P>
                        <STARS/>
                        <P>(109) 40°21.65′ N lat., 124°24.89′ W long.;</P>
                        <STARS/>
                        <P>(154) 37°04.49′ N lat., 122°38.50′ W long.;</P>
                        <STARS/>
                        <P>(157) 37°01.16′ N lat., 122°24.50′ W long.;</P>
                        <STARS/>
                        <P>(166) 36°49.80′ N lat., 121°57.93′ W long.;</P>
                        <STARS/>
                        <P>(186) 36°10.35′ N lat., 121°43.03′ W long.;</P>
                        <P>(187) 36°02.50′ N lat., 121°36.47′ W long.;</P>
                        <STARS/>
                        <P>(189) 36°00.00′ N lat., 121°35.32′ W long.;</P>
                        <P>(190) 35°58.20′ N lat., 121°32.97′ W long.;</P>
                        <STARS/>
                        <P>(206) 34°03.70′ N lat., 119°12.77′ W long.;</P>
                        <STARS/>
                        <P>(208) 34°04.44′ N lat., 119°04.90′ W long.;</P>
                        <P>(209) 34°02.94′ N lat., 119°02.89′ W long.;</P>
                        <P>(210) 34°01.30′ N lat., 119°00.48′ W long.;</P>
                        <STARS/>
                        <P>(215) 33°58.99′ N lat., 118°47.33′ W long.;</P>
                        <STARS/>
                        <P>(220) 33°49.85′ N lat., 118°32.31′ W long.;</P>
                        <P>(221) 33°49.61′ N lat., 118°28.07′ W long.;</P>
                        <P>(222) 33°49.77′ N lat., 118°26.34′ W long.;</P>
                        <STARS/>
                        <P>(227) 33°44.07′ N lat., 118°25.28′ W long.;</P>
                        <STARS/>
                        <P>(k) * * *</P>
                        <STARS/>
                        <P>(29) 33°51.69′ N lat., 120°07.98′ W long.;</P>
                        <STARS/>
                        <P>(l) * * *</P>
                        <STARS/>
                        <P>(3) 32°55.57′ N lat., 118°28.84′ W long.;</P>
                        <STARS/>
                        <P>(m) * * *</P>
                        <P>(1) 33°28.13′ N lat., 118°38.25′ W long.;</P>
                        <STARS/>
                        <P>(3) 33°28.94′ N lat., 118°30.81′ W long.;</P>
                        <P>(4) 33°26.73′ N lat., 118°27.35′ W long.;</P>
                        <STARS/>
                        <P>(6) 33°25.42′ N lat., 118°22.76′ W long.;</P>
                        <STARS/>
                        <P>(15) 33°24.94′ N lat., 118°32.29′ W long.;</P>
                        <STARS/>
                        <P>(18) 33°28.13′ N lat., 118°38.25′ W long.;</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>8. Amend § 660.73 by:</AMDPAR>
                    <AMDPAR>a. Revising paragraphs (a)(159) through (322);</AMDPAR>
                    <AMDPAR>b. Adding new paragraphs (a)(323) through (329);</AMDPAR>
                    <AMDPAR>c. Revising paragraphs (d)(10), (e)(188) and (189), (e)(264), (e)(272), (e)(274) through (276), (e)(284) through (286), (e)(290), (e)(318) through (323), (e)(350) through (363);</AMDPAR>
                    <AMDPAR>d. Adding new paragraphs (e)(364) through (371); and</AMDPAR>
                    <AMDPAR>e. Revising paragraphs (f), (g)(12) and (13), (h) and (l).</AMDPAR>
                    <P>The additions and revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 660.73 </SECTNO>
                        <SUBJECT> Latitude/longitude coordinates defining the 100 fm (183 m) through 150 fm (274 m) depth contours.</SUBJECT>
                        <STARS/>
                        <P>(a) * * *</P>
                        <P>(159) 40°39.44′ N lat., 124°29.08′ W long.;</P>
                        <P>(160) 40°37.08′ N lat., 124°28.29′ W long.;</P>
                        <P>(161) 40°34.76′ N lat., 124°29.82′ W long.;</P>
                        <P>(162) 40°36.78′ N lat., 124°37.06′ W long.;</P>
                        <P>(163) 40°32.44′ N lat., 124°39.58′ W long.;</P>
                        <P>(164) 40°30.37′ N lat., 124°37.30′ W long.;</P>
                        <P>(165) 40°28.48′ N lat., 124°36.95′ W long.;</P>
                        <P>(166) 40°24.82′ N lat., 124°35.12′ W long.;</P>
                        <P>(167) 40°23.30′ N lat., 124°31.60′ W long.;</P>
                        <P>(168) 40°23.52′ N lat., 124°28.78′ W long.;</P>
                        <P>(169) 40°22.43′ N lat., 124°25.00′ W long.;</P>
                        <P>(170) 40°21.72′ N lat., 124°24.94′ W long.;</P>
                        <P>(171) 40°21.87′ N lat., 124°27.96′ W long.;</P>
                        <P>(172) 40°21.40′ N lat., 124°28.74′ W long.;</P>
                        <P>(173) 40°19.68′ N lat., 124°28.49′ W long.;</P>
                        <P>(174) 40°17.73′ N lat., 124°25.43′ W long.;</P>
                        <P>(175) 40°18.37′ N lat., 124°23.35′ W long.;</P>
                        <P>(176) 40°15.75′ N lat., 124°26.05′ W long.;</P>
                        <P>(177) 40°16.75′ N lat., 124°33.71′ W long.;</P>
                        <P>(178) 40°16.29′ N lat., 124°34.36′ W long.;</P>
                        <P>(179) 40°10.13′ N lat., 124°21.92′ W long.;</P>
                        <P>
                            (180) 40°07.70′ N lat., 124°18.44′ W long.;
                            <PRTPAGE P="62702"/>
                        </P>
                        <P>(181) 40°08.84′ N lat., 124°15.86′ W long.;</P>
                        <P>(182) 40°06.39′ N lat., 124°17.26′ W long.;</P>
                        <P>(183) 40°03.15′ N lat., 124°14.43′ W long.;</P>
                        <P>(184) 40°02.19′ N lat., 124°12.85′ W long.;</P>
                        <P>(185) 40°02.89′ N lat., 124°11.78′ W long.;</P>
                        <P>(186) 40°02.78′ N lat., 124°10.70′ W long.;</P>
                        <P>(187) 40°04.57′ N lat., 124°10.08′ W long.;</P>
                        <P>(188) 40°06.06′ N lat., 124°08.30′ W long.;</P>
                        <P>(189) 40°04.05′ N lat., 124°08.93′ W long.;</P>
                        <P>(190) 40°01.17′ N lat., 124°08.80′ W long.;</P>
                        <P>(191) 40°01.00′ N lat., 124°09.96′ W long.;</P>
                        <P>(192) 39°58.07′ N lat., 124°11.81′ W long.;</P>
                        <P>(193) 39°56.39′ N lat., 124°08.69′ W long.;</P>
                        <P>(194) 39°54.64′ N lat., 124°07.30′ W long.;</P>
                        <P>(195) 39°53.86′ N lat., 124°07.95′ W long.;</P>
                        <P>(196) 39°51.95′ N lat., 124°07.63′ W long.;</P>
                        <P>(197) 39°48.78′ N lat., 124°03.29′ W long.;</P>
                        <P>(198) 39°47.36′ N lat., 124°03.31′ W long.;</P>
                        <P>(199) 39°40.08′ N lat., 123°58.37′ W long.;</P>
                        <P>(200) 39°36.16′ N lat., 123°56.90′ W long.;</P>
                        <P>(201) 39°30.75′ N lat., 123°55.86′ W long.;</P>
                        <P>(202) 39°31.62′ N lat., 123°57.33′ W long.;</P>
                        <P>(203) 39°30.91′ N lat., 123°57.88′ W long.;</P>
                        <P>(204) 39°01.79′ N lat., 123°56.59′ W long.;</P>
                        <P>(205) 38°59.42′ N lat., 123°55.67′ W long.;</P>
                        <P>(206) 38°58.89′ N lat., 123°56.28′ W long.;</P>
                        <P>(207) 38°57.50′ N lat., 123°56.28′ W long.;</P>
                        <P>(208) 38°54.72′ N lat., 123°55.68′ W long.;</P>
                        <P>(209) 38°48.95′ N lat., 123°51.85′ W long.;</P>
                        <P>(210) 38°36.67′ N lat., 123°40.20′ W long.;</P>
                        <P>(211) 38°33.82′ N lat., 123°39.23′ W long.;</P>
                        <P>(212) 38°29.02′ N lat., 123°33.52′ W long.;</P>
                        <P>(213) 38°18.88′ N lat., 123°25.93′ W long.;</P>
                        <P>(214) 38°14.12′ N lat., 123°23.26′ W long.;</P>
                        <P>(215) 38°11.07′ N lat., 123°22.07′ W long.;</P>
                        <P>(216) 38°03.18′ N lat., 123°20.77′ W long.;</P>
                        <P>(217) 38°00.00′ N lat., 123°23.08′ W long.;</P>
                        <P>(218) 37°55.07′ N lat., 123°26.81′ W long.;</P>
                        <P>(219) 37°50.66′ N lat., 123°23.06′ W long.;</P>
                        <P>(220) 37°45.18′ N lat., 123°11.88′ W long.;</P>
                        <P>(221) 37°35.67′ N lat., 123°01.20′ W long.;</P>
                        <P>(222) 37°26.81′ N lat., 122°55.57′ W long.;</P>
                        <P>(223) 37°26.78′ N lat., 122°53.91′ W long.;</P>
                        <P>(224) 37°25.74′ N lat., 122°54.13′ W long.;</P>
                        <P>(225) 37°25.33′ N lat., 122°53.59′ W long.;</P>
                        <P>(226) 37°25.29′ N lat., 122°52.57′ W long.;</P>
                        <P>(227) 37°24.50′ N lat., 122°52.09′ W long.;</P>
                        <P>(228) 37°23.25′ N lat., 122°53.12′ W long.;</P>
                        <P>(229) 37°15.58′ N lat., 122°48.36′ W long.;</P>
                        <P>(230) 37°11.00′ N lat., 122°44.50′ W long.;</P>
                        <P>(231) 37°07.00′ N lat., 122°41.25′ W long.;</P>
                        <P>(232) 37°03.18′ N lat., 122°38.15′ W long.;</P>
                        <P>(233) 37°00.48′ N lat., 122°33.93′ W long.;</P>
                        <P>(234) 36°58.70′ N lat., 122°27.22′ W long.;</P>
                        <P>(235) 37°00.85′ N lat., 122°24.70′ W long.;</P>
                        <P>(236) 36°58.00′ N lat., 122°24.14′ W long.;</P>
                        <P>(237) 36°58.74′ N lat., 122°21.51′ W long.;</P>
                        <P>(238) 36°56.97′ N lat., 122°21.32′ W long.;</P>
                        <P>(239) 36°51.52′ N lat., 122°10.68′ W long.;</P>
                        <P>(240) 36°48.39′ N lat., 122°07.60′ W long.;</P>
                        <P>(241) 36°47.43′ N lat., 122°03.22′ W long.;</P>
                        <P>(242) 36°50.95′ N lat., 121°58.03′ W long.;</P>
                        <P>(243) 36°49.92′ N lat., 121°58.01′ W long.;</P>
                        <P>(244) 36°48.86′ N lat., 121°58.80′ W long.;</P>
                        <P>(245) 36°47.76′ N lat., 121°58.68′ W long.;</P>
                        <P>(246) 36°48.39′ N lat., 121°51.10′ W long.;</P>
                        <P>(247) 36°45.74′ N lat., 121°54.17′ W long.;</P>
                        <P>(248) 36°45.51′ N lat., 121°57.72′ W long.;</P>
                        <P>(249) 36°38.84′ N lat., 122°01.32′ W long.;</P>
                        <P>(250) 36°35.62′ N lat., 122°00.98′ W long.;</P>
                        <P>(251) 36°32.46′ N lat., 121°59.15′ W long.;</P>
                        <P>(252) 36°32.79′ N lat., 121°57.67′ W long.;</P>
                        <P>(253) 36°31.98′ N lat., 121°56.55′ W long.;</P>
                        <P>(254) 36°31.79′ N lat., 121°58.40′ W long.;</P>
                        <P>(255) 36°30.73′ N lat., 121°59.70′ W long.;</P>
                        <P>(256) 36°30.31′ N lat., 122°00.22′ W long.;</P>
                        <P>(257) 36°29.35′ N lat., 122°00.28′ W long.;</P>
                        <P>(258) 36°27.66′ N lat., 121°59.80′ W long.;</P>
                        <P>(259) 36°26.22′ N lat., 121°58.35′ W long.;</P>
                        <P>(260) 36°21.20′ N lat., 122°00.72′ W long.;</P>
                        <P>(261) 36°20.47′ N lat., 122°02.92′ W long.;</P>
                        <P>(262) 36°18.46′ N lat., 122°04.51′ W long.;</P>
                        <P>(263) 36°15.92′ N lat., 122°01.33′ W long.;</P>
                        <P>(264) 36°13.81′ N lat., 121°57.40′ W long.;</P>
                        <P>(265) 36°14.43′ N lat., 121°55.43′ W long.;</P>
                        <P>(266) 36°10.24′ N lat., 121°43.08′ W long.;</P>
                        <P>(267) 36°07.66′ N lat., 121°40.91′ W long.;</P>
                        <P>(268) 36°02.49′ N lat., 121°36.51′ W long.;</P>
                        <P>(269) 36°01.08′ N lat., 121°36.63′ W long.;</P>
                        <P>(270) 36°00.00′ N lat., 121°35.41′ W long.;</P>
                        <P>(271) 35°57.84′ N lat., 121°32.81′ W long.;</P>
                        <P>(272) 35°50.36′ N lat., 121°29.32′ W long.;</P>
                        <P>(273) 35°39.03′ N lat., 121°22.86′ W long.;</P>
                        <P>(274) 35°24.27′ N lat., 121°02.74′ W long.;</P>
                        <P>(275) 35°16.53′ N lat., 121°00.39′ W long.;</P>
                        <P>(276) 35°04.82′ N lat., 120°53.96′ W long.;</P>
                        <P>(277) 34°52.51′ N lat., 120°51.62′ W long.;</P>
                        <P>(278) 34°43.36′ N lat., 120°52.12′ W long.;</P>
                        <P>(279) 34°38.06′ N lat., 120°49.65′ W long.;</P>
                        <P>(280) 34°30.85′ N lat., 120°44.76′ W long.;</P>
                        <P>(281) 34°27.00′ N lat., 120°39.00′ W long.;</P>
                        <P>(282) 34°21.90′ N lat., 120°25.25′ W long.;</P>
                        <P>(283) 34°24.86′ N lat., 120°16.81′ W long.;</P>
                        <P>(284) 34°22.80′ N lat., 119°57.06′ W long.;</P>
                        <P>
                            (285) 34°18.59′ N lat., 119°44.84′ W long.;
                            <PRTPAGE P="62703"/>
                        </P>
                        <P>(286) 34°15.04′ N lat., 119°40.34′ W long.;</P>
                        <P>(287) 34°14.40′ N lat., 119°45.39′ W long.;</P>
                        <P>(288) 34°12.32′ N lat., 119°42.41′ W long.;</P>
                        <P>(289) 34°09.71′ N lat., 119°28.85′ W long.;</P>
                        <P>(290) 34°04.70′ N lat., 119°15.38′ W long.;</P>
                        <P>(291) 34°03.33′ N lat., 119°12.93′ W long.;</P>
                        <P>(292) 34°02.72′ N lat., 119°07.01′ W long.;</P>
                        <P>(293) 34°03.90′ N lat., 119°04.64′ W long.;</P>
                        <P>(294) 34°02.75′ N lat., 119°02.88′ W long.;</P>
                        <P>(295) 33°59.44′ N lat., 119°03.43′ W long.;</P>
                        <P>(296) 33°59.12′ N lat., 118°59.59′ W long.;</P>
                        <P>(297) 33°59.84′ N lat., 118°57.29′ W long.;</P>
                        <P>(298) 33°58.83′ N lat., 118°46.69′ W long.;</P>
                        <P>(299) 33°58.73′ N lat., 118°41.76′ W long.;</P>
                        <P>(300) 33°55.09′ N lat., 118°34.11′ W long.;</P>
                        <P>(301) 33°54.09′ N lat., 118°38.42′ W long.;</P>
                        <P>(302) 33°51.00′ N lat., 118°36.66′ W long.;</P>
                        <P>(303) 33°49.06′ N lat., 118°31.86′ W long.;</P>
                        <P>(304) 33°49.69′ N lat., 118°26.49′ W long.;</P>
                        <P>(305) 33°49.35′ N lat., 118°26.04′ W long.;</P>
                        <P>(306) 33°47.60′ N lat., 118°31.13′ W long.;</P>
                        <P>(307) 33°39.82′ N lat., 118°18.31′ W long.;</P>
                        <P>(308) 33°35.68′ N lat., 118°16.81′ W long.;</P>
                        <P>(309) 33°32.85′ N lat., 118°09.41′ W long.;</P>
                        <P>(310) 33°35.14′ N lat., 118°04.95′ W long.;</P>
                        <P>(311) 33°33.56′ N lat., 118°00.63′ W long.;</P>
                        <P>(312) 33°34.25′ N lat., 117°53.44′ W long.;</P>
                        <P>(313) 33°31.65′ N lat., 117°49.21′ W long.;</P>
                        <P>(314) 33°16.07′ N lat., 117°34.74′ W long.;</P>
                        <P>(315) 33°07.06′ N lat., 117°22.71′ W long.;</P>
                        <P>(316) 33°02.81′ N lat., 117°21.17′ W long.;</P>
                        <P>(317) 33°01.76′ N lat., 117°20.51′ W long.;</P>
                        <P>(318) 32°59.90′ N lat., 117°19.38′ W long.;</P>
                        <P>(319) 32°57.29′ N lat., 117°18.94′ W long.;</P>
                        <P>(320) 32°56.15′ N lat., 117°19.54′ W long.;</P>
                        <P>(321) 32°55.30′ N lat., 117°19.38′ W long.;</P>
                        <P>(322) 32°54.27′ N lat., 117°17.17′ W long.;</P>
                        <P>(323) 32°52.94′ N lat., 117°17.11′ W long.;</P>
                        <P>(324) 32°52.66′ N lat., 117°19.67′ W long.;</P>
                        <P>(325) 32°50.95′ N lat., 117°21.17′ W long.;</P>
                        <P>(326) 32°47.11′ N lat., 117°22.98′ W long.;</P>
                        <P>(327) 32°45.60′ N lat., 117°22.64′ W long.;</P>
                        <P>(328) 32°42.79′ N lat., 117°21.16′ W long.; and</P>
                        <P>(329) 32°34.22′ N lat., 117°21.20′ W long.</P>
                        <STARS/>
                        <P>(d) * * *</P>
                        <STARS/>
                        <P>(10) 34°02.97′ N lat., 119°16.89′ W long.;</P>
                        <STARS/>
                        <P>(e) * * *</P>
                        <STARS/>
                        <P>(188) 40°22.32′ N lat., 124°25.15′ W long.;</P>
                        <P>(189) 40°21.85′ N lat., 124°25.09′ W long.;</P>
                        <STARS/>
                        <P>(264) 36°51.44′ N lat., 122°10.79′ W long.;</P>
                        <STARS/>
                        <P>(272) 36°45.52′ N lat., 121°57.74′ W long.;</P>
                        <STARS/>
                        <P>(274) 36°38.84′ N lat., 122°01.44′ W long.;</P>
                        <P>(275) 36°35.62′ N lat., 122°01.06′ W long.;</P>
                        <P>(276) 36°32.41′ N lat., 121°59.18′ W long.;</P>
                        <STARS/>
                        <P>(284) 36°13.66′ N lat., 121°57.17′ W long.;</P>
                        <P>(285) 36°14.35′ N lat., 121°55.38′ W long.;</P>
                        <P>(286) 36°10.18′ N lat., 121°43.26′ W long.;</P>
                        <STARS/>
                        <P>(290) 35°59.96′ N lat., 121°35.39′ W long.;</P>
                        <STARS/>
                        <P>(318) 34°07.06′ N lat., 120°10.42′ W long.;</P>
                        <P>(319) 34°08.93′ N lat., 120°18.34′ W long.;</P>
                        <P>(320) 34°11.04′ N lat., 120°25.20′ W long.;</P>
                        <P>(321) 34°13.01′ N lat., 120°29.29′ W long.;</P>
                        <P>(322) 34°09.41′ N lat., 120°37.69′ W long.;</P>
                        <P>(323) 34°03.20′ N lat., 120°34.52′ W long.;</P>
                        <STARS/>
                        <P>(350) 33°48.70′ N lat., 118°31.99′ W long.;</P>
                        <P>(351) 33°48.87′ N lat., 118°29.47′ W long.;</P>
                        <P>(352) 33°48.37′ N lat., 118°29.40′ W long.;</P>
                        <P>(353) 33°47.63′ N lat., 118°31.57′ W long.;</P>
                        <P>(354) 33°39.78′ N lat., 118°18.40′ W long.;</P>
                        <P>(355) 33°35.50′ N lat., 118°16.85′ W long.;</P>
                        <P>(356) 33°32.46′ N lat., 118°10.90′ W long.;</P>
                        <P>(357) 33°32.81′ N lat., 118°07.30′ W long.;</P>
                        <P>(358) 33°34.38′ N lat., 118°05.94′ W long.;</P>
                        <P>(359) 33°34.42′ N lat., 118°03.95′ W long.;</P>
                        <P>(360) 33°33.40′ N lat., 118°01.26′ W long.;</P>
                        <P>(361) 33°34.11′ N lat., 117°54.07′ W long.;</P>
                        <P>(362) 33°31.61′ N lat., 117°49.30′ W long.;</P>
                        <P>(363) 33°16.36′ N lat., 117°35.48′ W long.;</P>
                        <P>(364) 33°06.81′ N lat., 117°22.93′ W long.;</P>
                        <P>(365) 32°59.28′ N lat., 117°19.69′ W long.;</P>
                        <P>(366) 32°55.37′ N lat., 117°19.55′ W long.;</P>
                        <P>(367) 32°53.12′ N lat., 117°17.49′ W long.;</P>
                        <P>(368) 32°52.56′ N lat., 117°20.75′ W long.;</P>
                        <P>(369) 32°46.42′ N lat., 117°23.45′ W long.;</P>
                        <P>(370) 32°42.71′ N lat., 117°21.45′ W long.; and</P>
                        <P>(371) 32°34.54′ N lat., 117°23.04′ W long.</P>
                        <STARS/>
                        <P>(f) The 125 fm (229 m) depth contour around San Clemente Island off the state of California is defined by straight lines connecting all of the following points in the order stated:</P>
                        <P>(1) 33°04.86′ N lat., 118°37.89′ W long.;</P>
                        <P>(2) 33°02.67′ N lat., 118°34.07′ W long.;</P>
                        <P>(3) 32°55.97′ N lat., 118°28.95′ W long.;</P>
                        <P>(4) 32°55.06′ N lat., 118°27.66′ W long.;</P>
                        <P>(5) 32°49.79′ N lat., 118°20.84′ W long.;</P>
                        <P>(6) 32°48.02′ N lat., 118°19.49′ W long.;</P>
                        <P>(7) 32°47.37′ N lat., 118°21.72′ W long.;</P>
                        <P>(8) 32°43.58′ N lat., 118°24.54′ W long.;</P>
                        <P>
                            (9) 32°47.74′ N lat., 118°30.39′ W long.;
                            <PRTPAGE P="62704"/>
                        </P>
                        <P>(10) 32°49.74′ N lat., 118°32.11′ W long.;</P>
                        <P>(11) 32 °53.36′ N lat., 118°33.44′ W long.;</P>
                        <P>(12) 32 °54.89′ N lat., 118°35.37′ W long.;</P>
                        <P>(13) 33 °00.20′ N lat., 118°38.72′ W long.;</P>
                        <P>(14) 33 °03.15′ N lat., 118°39.80′ W long.; and</P>
                        <P>(15) 33 °04.86′ N lat., 118°37.89′ W long.;</P>
                        <STARS/>
                        <P>(g) * * *</P>
                        <STARS/>
                        <P>(12) 33°19.85′ N lat., 118°32.25′ W long.;</P>
                        <P>(13) 33°20.82′ N lat., 118°32.98′ W long.;</P>
                        <STARS/>
                        <P>(h) The 125 fm (229 m) depth contour around Lasuen Knoll off the state of California is defined by straight lines connecting all of the following points in the order stated:</P>
                        <P>(1) 33°24.50′ N lat., 118°01.08′ W long.;</P>
                        <P>(2) 33°23.35′ N lat., 117°59.83′ W long.;</P>
                        <P>(3) 33°23.69′ N lat., 117°58.47′ W long.;</P>
                        <P>(4) 33°24.76′ N lat., 117°59.33′ W long.; and</P>
                        <P>(5) 33°24.50′ N lat., 118°01.08′ W long.</P>
                        <STARS/>
                        <P>(l) The 150 fm (274 m) depth contour used around Lasuen Knoll off the state of California is defined by straight lines connecting all of the following points in the order stated:</P>
                        <P>(1) 33°25.07′ N lat., 117°59.26′ W long.;</P>
                        <P>(2) 33°23.69′ N lat., 117°58.13′ W long.;</P>
                        <P>(3) 33°23.18′ N lat., 117°59.87′ W long.;</P>
                        <P>(4) 33°24.61′ N lat., 118°01.31′ W long.; and</P>
                        <P>(5) 33°25.07′ N lat., 117°59.26′ W long.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>9. In § 660.74, revise paragraphs (d), (j), and (p)(3) through (7) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 660.74 </SECTNO>
                        <SUBJECT> Latitude/longitude coordinates defining the 180 fm (329 m) through 250 fm (457 m) depth contours.</SUBJECT>
                        <STARS/>
                        <P>(d) The 180 fm (329 m) depth contour used around Lasuen Knoll off the state of California is defined by straight lines connecting all of the following points in the order stated:</P>
                        <P>(1) 33°25.05′ N lat., 118°01.70′ W long.;</P>
                        <P>(2) 33°25.41′ N lat., 117°59.36′ W long.;</P>
                        <P>(3) 33°23.49′ N lat., 117°57.47′ W long.;</P>
                        <P>(4) 33°23.02′ N lat., 117°59.78′ W long.;</P>
                        <P>(5) 33°23.85′ N lat., 118°00.88′ W long.; and</P>
                        <P>(6) 33°25.05′ N lat., 118°01.70′ W long.</P>
                        <STARS/>
                        <P>(j) The 200 fm (366 m) depth contour used around Lasuen Knoll off the state of California is defined by straight lines connecting all of the following points in the order stated:</P>
                        <P>(1) 33°25.91′ N lat., 117°59.44′ W long.;</P>
                        <P>(2) 33°23.37′ N lat., 117°56.97′ W long.;</P>
                        <P>(3) 33°22.88′ N lat., 117°59.72′ W long.;</P>
                        <P>(4) 33°23.85′ N lat., 118°01.03′ W long.;</P>
                        <P>(5) 33°25.20′ N lat., 118°01.89′ W long.; and</P>
                        <P>(6) 33°25.91′ N lat., 117°59.44′ W long.</P>
                        <STARS/>
                        <P>(p) * * *</P>
                        <STARS/>
                        <P>(3) 33°23.83′ N lat., 117°56.19′ W long.;</P>
                        <P>(4) 33°22.24′ N lat., 117°57.20′ W long.;</P>
                        <P>(5) 33°22.78′ N lat., 117°59.68′ W long.;</P>
                        <P>(6) 33°23.79′ N lat., 118°01.32′ W long.;</P>
                        <P>(7) 33°25.79′ N lat., 118°02.25′ W long.;</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>10. Revise Tables 1a through 1c to part 660, subpart C, to read as follows:</AMDPAR>
                    <STARS/>
                    <GPOTABLE COLS="6" OPTS="L2,p7,7/7,i1" CDEF="s50,r50,12,12,12,12">
                        <TTITLE>
                            Table 1
                            <E T="01">a.</E>
                             to Part 660, Subpart C—2023, Specifications of OFL, ABC, ACL, ACT and Fishery HG 
                        </TTITLE>
                        <TDESC>[(Weights in metric tons). Capitalized stocks are rebuilding.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Stocks</CHED>
                            <CHED H="1">Area</CHED>
                            <CHED H="1">OFL</CHED>
                            <CHED H="1">ABC</CHED>
                            <CHED H="1">
                                ACL 
                                <SU>a</SU>
                            </CHED>
                            <CHED H="1">
                                Fishery HG 
                                <SU>b</SU>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                YELLOWEYE ROCKFISH 
                                <SU>c</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>123</ENT>
                            <ENT>103</ENT>
                            <ENT>66</ENT>
                            <ENT>55.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Arrowtooth Flounder 
                                <SU>d</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>26,391</ENT>
                            <ENT>18,632</ENT>
                            <ENT>18,632</ENT>
                            <ENT>16,537</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Big Skate 
                                <SU>e</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,541</ENT>
                            <ENT>1,320</ENT>
                            <ENT>1,320</ENT>
                            <ENT>1,260.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Black Rockfish 
                                <SU>f</SU>
                            </ENT>
                            <ENT>California (S of 42° N lat)</ENT>
                            <ENT>368</ENT>
                            <ENT>334</ENT>
                            <ENT>334</ENT>
                            <ENT>332.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Black Rockfish 
                                <SU>g</SU>
                            </ENT>
                            <ENT>Washington (N of 46°16′ N lat)</ENT>
                            <ENT>319</ENT>
                            <ENT>290</ENT>
                            <ENT>290</ENT>
                            <ENT>271.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Bocaccio 
                                <SU>h</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>2,009</ENT>
                            <ENT>1,842</ENT>
                            <ENT>1,842</ENT>
                            <ENT>1,793.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Cabezon 
                                <SU>i</SU>
                            </ENT>
                            <ENT>California (S of 42° N lat)</ENT>
                            <ENT>197</ENT>
                            <ENT>182</ENT>
                            <ENT>182</ENT>
                            <ENT>180.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                California Scorpionfish 
                                <SU>j</SU>
                            </ENT>
                            <ENT>S of 34°27′ N lat</ENT>
                            <ENT>290</ENT>
                            <ENT>262</ENT>
                            <ENT>262</ENT>
                            <ENT>258.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Canary Rockfish 
                                <SU>k</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,413</ENT>
                            <ENT>1,284</ENT>
                            <ENT>1,284</ENT>
                            <ENT>1,215.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Chilipepper 
                                <SU>l</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>2,401</ENT>
                            <ENT>2,183</ENT>
                            <ENT>2,183</ENT>
                            <ENT>2,085</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Cowcod 
                                <SU>m</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>113</ENT>
                            <ENT>80</ENT>
                            <ENT>80</ENT>
                            <ENT>68.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Cowcod</ENT>
                            <ENT>(Conception)</ENT>
                            <ENT>94</ENT>
                            <ENT>69</ENT>
                            <ENT>NA</ENT>
                            <ENT>NA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Cowcod</ENT>
                            <ENT>(Monterey)</ENT>
                            <ENT>19</ENT>
                            <ENT>11</ENT>
                            <ENT>NA</ENT>
                            <ENT>NA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Darkblotched Rockfish 
                                <E T="0731">n</E>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>856</ENT>
                            <ENT>785</ENT>
                            <ENT>785</ENT>
                            <ENT>761.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Dover Sole 
                                <SU>o</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>63,834</ENT>
                            <ENT>59,685</ENT>
                            <ENT>50,000</ENT>
                            <ENT>48,402.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                English Sole 
                                <SU>p</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>11,133</ENT>
                            <ENT>9,018</ENT>
                            <ENT>9,018</ENT>
                            <ENT>8,758.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Lingcod 
                                <SU>q</SU>
                            </ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>5,010</ENT>
                            <ENT>4,378</ENT>
                            <ENT>4,378</ENT>
                            <ENT>4,098.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Lingcod 
                                <SU>r</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>846</ENT>
                            <ENT>739</ENT>
                            <ENT>726</ENT>
                            <ENT>710.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Longnose Skate 
                                <SU>s</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,993</ENT>
                            <ENT>1,708</ENT>
                            <ENT>1,708</ENT>
                            <ENT>1,456.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Longspine Thornyhead 
                                <SU>t</SU>
                            </ENT>
                            <ENT>N of 34°27′ N lat</ENT>
                            <ENT>4,616</ENT>
                            <ENT>3,019</ENT>
                            <ENT>2,295</ENT>
                            <ENT>2,241.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Longspine Thornyhead 
                                <SU>u</SU>
                            </ENT>
                            <ENT>S of 34°27′ N lat</ENT>
                            <ENT>725</ENT>
                            <ENT>722.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Pacific Cod 
                                <SU>v</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>3,200</ENT>
                            <ENT>1,926</ENT>
                            <ENT>1,600</ENT>
                            <ENT>1,094</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Pacific Ocean Perch 
                                <SU>w</SU>
                            </ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>4,248</ENT>
                            <ENT>3,573</ENT>
                            <ENT>3,573</ENT>
                            <ENT>3,427.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Pacific Whiting 
                                <SU>x</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>x</ENT>
                            <ENT>x</ENT>
                            <ENT>x</ENT>
                            <ENT>x</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Petrale Sole 
                                <SU>y</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>3,763</ENT>
                            <ENT>3,485</ENT>
                            <ENT>3,485</ENT>
                            <ENT>3,098.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Sablefish 
                                <SU>z</SU>
                            </ENT>
                            <ENT>N of 36° N lat</ENT>
                            <ENT>11,577</ENT>
                            <ENT>10,825</ENT>
                            <ENT>8,486</ENT>
                            <ENT>See Table 1c</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Sablefish 
                                <SU>aa</SU>
                            </ENT>
                            <ENT>S of 36° N lat</ENT>
                            <ENT>2,338</ENT>
                            <ENT>2,310.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Shortspine Thornyhead 
                                <SU>bb</SU>
                            </ENT>
                            <ENT>N of 34°27′ N lat</ENT>
                            <ENT>3,177</ENT>
                            <ENT>2,078</ENT>
                            <ENT>1,359</ENT>
                            <ENT>1,280.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Shortspine Thornyhead 
                                <SU>cc</SU>
                            </ENT>
                            <ENT>S of 34°27′ N lat</ENT>
                            <ENT>719</ENT>
                            <ENT>712.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Spiny Dogfish 
                                <SU>dd</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,911</ENT>
                            <ENT>1,456</ENT>
                            <ENT>1,456</ENT>
                            <ENT>1,104.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Splitnose 
                                <SU>ee</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>1,803</ENT>
                            <ENT>1,592</ENT>
                            <ENT>1,592</ENT>
                            <ENT>1,573.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Starry Flounder 
                                <SU>ff</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>652</ENT>
                            <ENT>392</ENT>
                            <ENT>392</ENT>
                            <ENT>343.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Widow Rockfish 
                                <SU>gg</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>13,633</ENT>
                            <ENT>12,624</ENT>
                            <ENT>12,624</ENT>
                            <ENT>12,385.7</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">
                                Yellowtail Rockfish 
                                <SU>hh</SU>
                            </ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>6,178</ENT>
                            <ENT>5,666</ENT>
                            <ENT>5,666</ENT>
                            <ENT>4,638.5</ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <PRTPAGE P="62705"/>
                            <ENT I="21">
                                <E T="02">Stock Complexes</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">
                                Blue/Deacon/Black Rockfish 
                                <SU>ii</SU>
                            </ENT>
                            <ENT>Oregon</ENT>
                            <ENT>679</ENT>
                            <ENT>597</ENT>
                            <ENT>597</ENT>
                            <ENT>595.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Cabezon/Kelp Greenling 
                                <SU>jj</SU>
                            </ENT>
                            <ENT>Oregon</ENT>
                            <ENT>202</ENT>
                            <ENT>185</ENT>
                            <ENT>185</ENT>
                            <ENT>184.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Cabezon/Kelp Greenling 
                                <SU>kk</SU>
                            </ENT>
                            <ENT>Washington</ENT>
                            <ENT>25</ENT>
                            <ENT>20</ENT>
                            <ENT>20</ENT>
                            <ENT>18.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Nearshore Rockfish North 
                                <SU>ll</SU>
                            </ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>110</ENT>
                            <ENT>93</ENT>
                            <ENT>93</ENT>
                            <ENT>89.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Nearshore Rockfish South 
                                <SU>mm</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>1,089</ENT>
                            <ENT>897</ENT>
                            <ENT>887</ENT>
                            <ENT>882.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Other Fish 
                                <SU>nn</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>286</ENT>
                            <ENT>223</ENT>
                            <ENT>223</ENT>
                            <ENT>201.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Other Flatfish 
                                <SU>oo</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>7,887</ENT>
                            <ENT>4,862</ENT>
                            <ENT>4,862</ENT>
                            <ENT>4,641</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Shelf Rockfish North 
                                <SU>pp</SU>
                            </ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>1,614</ENT>
                            <ENT>1,283</ENT>
                            <ENT>1,283</ENT>
                            <ENT>1,212.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Shelf Rockfish South 
                                <SU>qq</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>1,835</ENT>
                            <ENT>1,469</ENT>
                            <ENT>1,469</ENT>
                            <ENT>1,336.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Slope Rockfish North 
                                <SU>rr</SU>
                            </ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>1,819</ENT>
                            <ENT>1,540</ENT>
                            <ENT>1,540</ENT>
                            <ENT>1,474.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Slope Rockfish South 
                                <SU>ss</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>870</ENT>
                            <ENT>701</ENT>
                            <ENT>701</ENT>
                            <ENT>662.1</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>a</SU>
                             Annual catch limits (ACLs), annual catch targets (ACTs) and harvest guidelines (HGs) are specified as total catch valueS
                        </TNOTE>
                        <TNOTE>
                            <SU>b</SU>
                             Fishery HGs means the HG or quota after subtracting Pacific Coast treaty Indian tribes allocations and projected catch, projected research catch, deductions for fishing mortality in non-groundfish fisheries, and deductions for EFPs from the ACL or ACT.
                        </TNOTE>
                        <TNOTE>
                            <SU>c</SU>
                             Yelloweye rockfish. The 66 mt ACL is based on the current rebuilding plan with a target year to rebuild of 2029 and an SPR harvest rate of 65 percent. 10.7 mt is deducted from the ACL to accommodate the Tribal fishery (5 mt), EFP fishing (0.12 mt), research catch (2.92 mt), and incidental open access mortality (2.66 mt) resulting in a fishery HG of 55.3 mt. The non-trawl HG is 50.9 mt. The combined non-nearshore/nearshore HG is 10.7 mt. Recreational HGs are: 13.2 mt (Washington); 11.7 mt (Oregon); and 15.3 mt (California). In addition, the non-trawl ACT is 39.9 mt, and the combined non-nearshore/nearshore ACT is 8.4 mt. Recreational ACTs are: 10.4 mt (Washington), 9.2 mt (Oregon), and 12.0 mt (California).
                        </TNOTE>
                        <TNOTE>
                            <SU>d</SU>
                             Arrowtooth flounder. 2,094.98 mt is deducted from the ACL to accommodate the Tribal fishery (2,041 mt), research catch (12.98 mt) and incidental open access mortality (41 mt), resulting in a fishery HG of 16,537 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>e</SU>
                             Big skate. 59.8 mt is deducted from the ACL to accommodate the Tribal fishery (15 mt), research catch (5.49 mt), and incidental open access mortality (39.31 mt), resulting in a fishery HG of 1,260.2 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>f</SU>
                             Black rockfish (California). 2.26 mt is deducted from the ACL to accommodate EFP fishing (1.0 mt), research catch (0.08 mt), and incidental open access mortality (1.18 mt), resulting in a fishery HG of 332.1 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>g</SU>
                             Black rockfish (Washington). 18.1 mt is deducted from the ACL to accommodate the Tribal fishery (18 mt) and research catch (0.1 mt), resulting in a fishery HG of 271.8 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>h</SU>
                             Bocaccio south of 40°10′ N lat. Bocaccio are managed with stock-specific harvest specifications south of 40°10′ N lat. and within the Minor Shelf Rockfish complex north of 40°10′ N lat. 48.12 mt is deducted from the ACL to accommodate EFP fishing (40 mt), research catch (5.6 mt), and incidental open access mortality (2.52 mt), resulting in a fishery HG of 1,793.9 mt. The California recreational fishery south of 40°10′ N lat. has an HG of 755.6 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>i</SU>
                             Cabezon (California). 1.63 mt is deducted from the ACL to accommodate EFP fishing (1 mt), research catch (0.02 mt), and incidental open access fishery mortality (0.61 mt), resulting in a fishery HG of 180.4 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>j</SU>
                             California scorpionfish south of 34°27′ N lat. 3.89 mt is deducted from the ACL to accommodate research (0.18 mt) and the incidental open access fishery (3.71 mt), resulting in a fishery HG of 258.4 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>k</SU>
                             Canary rockfish. 68.91 mt is deducted from the ACL to accommodate the Tribal fishery (50 mt), EFP fishing (6 mt), and research catch (10.08 mt), and incidental open access mortality (2.83 mt), resulting in a fishery HG of 1,215.1 mt. The combined nearshore/non-nearshore HG is 121.2 mt. Recreational HGs are: 41.4 mt (Washington); 62.3 mt (Oregon); and 111.7 mt (California).
                        </TNOTE>
                        <TNOTE>
                            <SU>l</SU>
                             Chilipepper rockfish south of 40°10′ N lat. Chilipepper are managed with stock-specific harvest specifications south of 40°10′N lat. and within the Minor Shelf Rockfish complex north of 40°10′ N lat. 97.7 mt is deducted from the ACL to accommodate EFP fishing (70 mt), research catch (14.04 mt), incidental open access fishery mortality (13.66 mt), resulting in a fishery HG of 2,085 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>m</SU>
                             Cowcod south of 40°10′ N lat. Cowcod are managed with stock-specific harvest specifications south of 40°10′ N lat. and within the Minor Shelf Rockfish complex north of 40°10′ N lat. 11.17 mt is deducted from the ACL to accommodate EFP fishing (1 mt), research catch (10 mt), and incidental open access mortality (0.17 mt), resulting in a fishery HG of 68.8 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>n</SU>
                             Darkblotched rockfish. 23.76 mt is deducted from the ACL to accommodate the Tribal fishery (5 mt), EFP fishing (0.5 mt), research catch (8.46 mt), and incidental open access mortality (9.8 mt) resulting in a fishery HG of 761.2 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>o</SU>
                             Dover sole. 1,597.11 mt is deducted from the ACL to accommodate the Tribal fishery (1,497 mt), research catch (50.84 mt), and incidental open access mortality (49.27 mt), resulting in a fishery HG of 48,402.9 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>p</SU>
                             English sole. 259.52 mt is deducted from the ACL to accommodate the Tribal fishery (200 mt), research catch (17 mt), and incidental open access mortality (42.52 mt), resulting in a fishery HG of 8,758.5 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>q</SU>
                             Lingcod north of 40°10′ N lat. 279.63 mt is deducted from the ACL for the Tribal fishery (250 mt), research catch (17.71 mt), and incidental open access mortality (11.92 mt) resulting in a fishery HG of 4,098.4 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>r</SU>
                             Lingcod south of 40°10′ N lat. 15.5 mt is deducted from the ACL to accommodate EFP fishing (4 mt), research catch (3.19 mt), and incidental open access mortality (8.31 mt), resulting in a fishery HG of 710.5 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>s</SU>
                             Longnose skate. 251.3 mt is deducted from the ACL to accommodate the Tribal fishery (220 mt), research catch (12.46 mt), and incidental open access mortality (18.84 mt), resulting in a fishery HG of 1,456.7 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>t</SU>
                             Longspine thornyhead north of 34°27′ N lat. 53.71 mt is deducted from the ACL to accommodate the Tribal fishery (30 mt), research catch (17.49 mt), and incidental open access mortality(6.22 mt), resulting in a fishery HG of 2,241.3 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>u</SU>
                             Longspine thornyhead south of 34°27′ N lat. 2.24 mt is deducted from the ACL to accommodate research catch (1.41 mt) and incidental open access mortality (0.83 mt), resulting in a fishery HG of 722.8 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>v</SU>
                             Pacific cod. 506 mt is deducted from the ACL to accommodate the Tribal fishery (500 mt), research catch (5.47 mt), and incidental open access mortality (0.53 mt), resulting in a fishery HG of 1,094 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>w</SU>
                             Pacific ocean perch north of 40°10′ N lat. Pacific ocean perch are managed with stock-specific harvest specifications north of 40°10′ N lat. and within the Minor Slope Rockfish complex south of 40°10′ N lat. 145.48 mt is deducted from the ACL to accommodate the Tribal fishery (130 mt), research catch (5.39 mt), and incidental open access mortality (10.09 mt), resulting in a fishery HG of 3,427.5 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>x</SU>
                             Pacific whiting. Pacific whiting are assessed annually. The final specifications will be determined consistent with the U.S-Canada Pacific Whiting Agreement and will be announced after the Council′s April 2023 meeting.
                        </TNOTE>
                        <TNOTE>
                            <SU>y</SU>
                             Petrale sole. 386.24 mt is deducted from the ACL to accommodate the Tribal fishery (350 mt), EFP fishing (1 mt), research catch (24.14 mt), and incidental open access mortality (11.1 mt), resulting in a fishery HG of 3,098.8 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>z</SU>
                             Sablefish north of 36° N lat. The sablefish coastwide ACL value is not specified in regulationS The coastwide sablefish ACL value is apportioned north and south of 36° N lat., using the rolling 5-year average estimated swept area biomass from the NMFS NWFSC trawl survey, with 78.4 percent apportioned north of 36° N lat. and 21.6 percent apportioned south of 36° N lat. The northern ACL is 8,486 mt and is reduced by 849 mt for the Tribal allocation (10 percent of the ACL north of 36° N lat.). The 849 mt Tribal allocation is reduced by 1.7 percent to account for discard mortality. Detailed sablefish allocations are shown in Table 1c.
                        </TNOTE>
                        <TNOTE>
                            <SU>aa</SU>
                             Sablefish south of 36° N lat. The ACL for the area south of 36° N lat. is 2,338 mt (21.6 percent of the calculated coastwide ACL value). 27.4 mt is deducted from the ACL to accommodate research catch (2.40 mt) and incidental open access mortality (25 mt), resulting in a fishery HG of 2,310.6 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>bb</SU>
                             Shortspine thornyhead north of 34°27′ N lat. 78.3 mt is deducted from the ACL to accommodate the Tribal fishery (50 mt), research catch (10.48 mt), and incidental open access mortality (17.82 mt), resulting in a fishery HG of 1,280.7 mt for the area north of 34°27′ N lat.
                        </TNOTE>
                        <TNOTE>
                            <SU>cc</SU>
                             Shortspine thornyhead south of 34°27′ N lat. 6.71 mt is deducted from the ACL to accommodate research catch (0.71 mt) and incidental open access mortality (6 mt), resulting in a fishery HG of 712.3 mt for the area south of 34°27′ N lat.
                        </TNOTE>
                        <TNOTE>
                            <SU>dd</SU>
                             Spiny dogfish. 351.48 mt is deducted from the ACL to accommodate the Tribal fishery (275 mt), EFP fishing (1 mt), research catch (41.85 mt), and incidental open access mortality (33.63 mt), resulting in a fishery HG of 1,104.5 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>ee</SU>
                             Splitnose rockfish south of 40°10′ N lat. 18.42 mt is deducted from the ACL to accommodate EFP fishing (1.5 mt), research catch (11.17 mt), and incidental open access mortality (5.75 mt), resulting in a fishery HG of 1,573.4 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>ff</SU>
                             Starry flounder. 48.28 mt is deducted from the ACL to accommodate the Tribal fishery (2 mt), research catch (0.57 mt), and incidental open access mortality (45.71 mt), resulting in a fishery HG of 343.7 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>gg</SU>
                             Widow rockfish. 238.32 mt is deducted from the ACL to accommodate the Tribal fishery (200 mt), EFP fishing (18 mt), research catch (17.27 mt), and incidental open access mortality (3.05 mt), resulting in a fishery HG of 12,385.7 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>hh</SU>
                             Yellowtail rockfish north of 40°10′ N lat. Yellowtail rockfish are managed with stock-specific harvest specifications north of 40°10′ N lat. and within the Minor Shelf Rockfish complex south of 40°10′ N lat. 1,027.55 mt is deducted from the ACL to accommodate the Tribal fishery (1,000 mt), research catch (20.55 mt), and incidental open access mortality (7 mt), resulting in a fishery HG of 4,638.5 mt.
                            <PRTPAGE P="62706"/>
                        </TNOTE>
                        <TNOTE>
                            <SU>ii</SU>
                             Black rockfish/Blue rockfish/Deacon rockfish (Oregon). 1.82 mt is deducted from the ACL to accommodate research catch (0.08 mt) and incidental open access mortality (1.74 mt), resulting in a fishery HG of 595.2 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>jj</SU>
                             Cabezon/kelp greenling (Oregon). 0.79 mt is deducted from the ACL to accommodate research catch (0.05 mt), and incidental open access mortality (0.74 mt), resulting in a fishery HG of 184.2 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>kk</SU>
                             Cabezon/kelp greenling (Washington). 2 mt is deducted from the ACL to accommodate the Tribal fishery, resulting in a fishery HG is 18 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>ll</SU>
                             Nearshore Rockfish north of 40°10′ N lat. 3.27 mt is deducted from the ACL to accommodate the Tribal fishery (1.5 mt), research catch (0.47 mt), and incidental open access mortality (1.3 mt), resulting in a fishery HG of 89.7 mt. State specific HGs are Washington (17.7 mt), Oregon (32.0 mt), and California (39.6 mt). The ACT for copper rockfish (California) is 6.93 mt. The ACT for quillback rockfish (California) is 0.87 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>mm</SU>
                             Nearshore Rockfish south of 40°10′ N lat. 4.54 mt is deducted from the ACL to accommodate research catch (2.68 mt) and incidental open access mortality (1.86 mt), resulting in a fishery HG of 882.5 mt. The ACT for copper rockfish is 84.61 mt. The ACT for quillback rockfish is 0.89 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>nn</SU>
                             Other Fish. The Other Fish complex is comprised of kelp greenling off California and leopard shark coastwide. 21.24 mt is deducted from the ACL to accommodate research catch (6.29 mt) and incidental open access mortality (14.95 mt), resulting in a fishery HG of 201.8 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>oo</SU>
                             Other Flatfish. The Other Flatfish complex is comprised of flatfish species managed in the PCGFMP that are not managed with stock-specific OFLs/ABCs/ACLS Most of the species in the Other Flatfish complex are unassessed and include: butter sole, curlfin sole, flathead sole, Pacific sanddab, rock sole, sand sole, and rex sole. 220.79 mt is deducted from the ACL to accommodate the Tribal fishery (60 mt), research catch (23.63 mt), and incidental open access mortality (137.16 mt), resulting in a fishery HG of 4,641.2 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>pp</SU>
                             Shelf Rockfish north of 40°10′ N lat. 70.94 mt is deducted from the ACL to accommodate the Tribal fishery (30 mt), research catch (15.32 mt), and incidental open access mortality (25.62 mt), resulting in a fishery HG of 1,212.1 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>qq</SU>
                             Shelf Rockfish south of 40°10′ N lat. 132.77 mt is deducted from the ACL to accommodate EFP fishing (50 mt), research catch (15.1 mt), and incidental open access mortality (67.67 mt) resulting in a fishery HG of 1,336.2 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>rr</SU>
                             Slope Rockfish north of 40°10′ N lat. 65.39 mt is deducted from the ACL to accommodate the Tribal fishery (36 mt), and research catch (10.51 mt), and incidental open access mortality (18.88 mt), resulting in a fishery HG of 1,474.6 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>ss</SU>
                             Slope Rockfish south of 40°10′ N lat. 38.94 mt is deducted from the ACL to accommodate EFP fishing (1 mt), research catch (18.21 mt), and incidental open access mortality (19.73 mt), resulting in a fishery HG of 662.1 mt. Blackgill rockfish has a stock-specific HG for the entire groundfish fishery south of 40°10′ N lat. set equal to the species′ contribution to the ACL. Harvest of blackgill rockfish in all groundfish fisheries south of 40°10′ N lat. counts against this HG of 172.4 mt.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="7" OPTS="L2,p7,7/8,i1" CDEF="s50,r50,12,12,12,12,12">
                        <TTITLE>
                            Table 1
                            <E T="01">b.</E>
                             to Part 660, Subpart C—2023, Allocations by Species or Species Group
                        </TTITLE>
                        <TDESC>[Weight in metric tons]</TDESC>
                        <BOXHD>
                            <CHED H="1">Stocks/stock complexes</CHED>
                            <CHED H="1">Area</CHED>
                            <CHED H="1">
                                Fishery HG 
                                <LI>or ACT</LI>
                            </CHED>
                            <CHED H="1">Trawl</CHED>
                            <CHED H="2">%</CHED>
                            <CHED H="2">Mt</CHED>
                            <CHED H="1">Non-trawl</CHED>
                            <CHED H="2">%</CHED>
                            <CHED H="2">Mt</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                YELLOWEYE ROCKFISH 
                                <SU>a</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>55.3</ENT>
                            <ENT>8</ENT>
                            <ENT>4.4</ENT>
                            <ENT>92</ENT>
                            <ENT>50.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Arrowtooth flounder</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>16,537</ENT>
                            <ENT>95</ENT>
                            <ENT>15,710.2</ENT>
                            <ENT>5</ENT>
                            <ENT>826.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Big skate 
                                <SU>a</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,260.2</ENT>
                            <ENT>95</ENT>
                            <ENT>1,197.2</ENT>
                            <ENT>5</ENT>
                            <ENT>63</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Bocaccio 
                                <SU>a</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>1,793.9</ENT>
                            <ENT>39.04</ENT>
                            <ENT>700.3</ENT>
                            <ENT>60.96</ENT>
                            <ENT>1,093.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Canary rockfish 
                                <SU>a</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,215.1</ENT>
                            <ENT>72.281</ENT>
                            <ENT>878.3</ENT>
                            <ENT>27.719</ENT>
                            <ENT>336.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Chilipepper rockfish</ENT>
                            <ENT>S of 40°10′N lat</ENT>
                            <ENT>2,085</ENT>
                            <ENT>75</ENT>
                            <ENT>1,563.8</ENT>
                            <ENT>25</ENT>
                            <ENT>521.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Cowcod 
                                <SU>a</SU>
                                 
                                <SU>b</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>68.8</ENT>
                            <ENT>36</ENT>
                            <ENT>24.8</ENT>
                            <ENT>64</ENT>
                            <ENT>44.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Darkblotched rockfish</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>761.2</ENT>
                            <ENT>95</ENT>
                            <ENT>723.2</ENT>
                            <ENT>5</ENT>
                            <ENT>38.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Dover sole</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>48,402.8</ENT>
                            <ENT>95</ENT>
                            <ENT>45,982.7</ENT>
                            <ENT>5</ENT>
                            <ENT>2,420.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">English sole</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>8,758.5</ENT>
                            <ENT>95</ENT>
                            <ENT>8,320.6</ENT>
                            <ENT>5</ENT>
                            <ENT>437.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Lingcod</ENT>
                            <ENT>N of 40′10° N lat</ENT>
                            <ENT>4,098.4</ENT>
                            <ENT>45</ENT>
                            <ENT>1,844.3</ENT>
                            <ENT>55</ENT>
                            <ENT>2,254.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Lingcod 
                                <SU>a</SU>
                            </ENT>
                            <ENT>S of 40′10° N lat</ENT>
                            <ENT>710.5</ENT>
                            <ENT>40</ENT>
                            <ENT>284.2</ENT>
                            <ENT>60</ENT>
                            <ENT>426.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Longnose skate 
                                <SU>a</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,456.7</ENT>
                            <ENT>90</ENT>
                            <ENT>1,311</ENT>
                            <ENT>10</ENT>
                            <ENT>145.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Longspine thornyhead</ENT>
                            <ENT>N of 34°27′ N lat</ENT>
                            <ENT>2,241.3</ENT>
                            <ENT>95</ENT>
                            <ENT>2,129.2</ENT>
                            <ENT>5</ENT>
                            <ENT>112.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pacific cod</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,094</ENT>
                            <ENT>95</ENT>
                            <ENT>1,039.3</ENT>
                            <ENT>5</ENT>
                            <ENT>54.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pacific ocean perch</ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>3,427.5</ENT>
                            <ENT>95</ENT>
                            <ENT>3,256.1</ENT>
                            <ENT>5</ENT>
                            <ENT>171.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Pacific whiting 
                                <SU>c</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>TBD</ENT>
                            <ENT>100</ENT>
                            <ENT>TBD</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW RUL="n,n,n,s">
                            <ENT I="01">
                                Petrale sole 
                                <SU>a</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>3,098.8</ENT>
                            <ENT/>
                            <ENT>3,068.8</ENT>
                            <ENT/>
                            <ENT>30</ENT>
                        </ROW>
                        <ROW RUL="n,n,n,s">
                            <ENT I="01">Sablefish</ENT>
                            <ENT>N of 36° N lat</ENT>
                            <ENT>NA</ENT>
                            <ENT A="03">See Table 1c</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sablefish</ENT>
                            <ENT>S of 36° N lat</ENT>
                            <ENT>2,310.6</ENT>
                            <ENT>42</ENT>
                            <ENT>970.5</ENT>
                            <ENT>58</ENT>
                            <ENT>1,340.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Shortspine thornyhead</ENT>
                            <ENT>N of 34°27′ N lat</ENT>
                            <ENT>1,280.7</ENT>
                            <ENT>95</ENT>
                            <ENT>1,216.7</ENT>
                            <ENT>5</ENT>
                            <ENT>64</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Shortspine thornyhead</ENT>
                            <ENT>S of 34°27′ N lat</ENT>
                            <ENT>712.3</ENT>
                            <ENT/>
                            <ENT>50</ENT>
                            <ENT/>
                            <ENT>662.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Splitnose rockfish</ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>1,572.4</ENT>
                            <ENT>95</ENT>
                            <ENT>1,494.7</ENT>
                            <ENT>5</ENT>
                            <ENT>78.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Starry flounder</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>343.7</ENT>
                            <ENT>50</ENT>
                            <ENT>171.9</ENT>
                            <ENT>50</ENT>
                            <ENT>171.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Widow rockfish 
                                <SU>a</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>12,385.7</ENT>
                            <ENT/>
                            <ENT>11,985.7</ENT>
                            <ENT/>
                            <ENT>400</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Yellowtail rockfish</ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>4,638.5</ENT>
                            <ENT>88</ENT>
                            <ENT>4,081.8</ENT>
                            <ENT>12</ENT>
                            <ENT>556.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Other Flatfish</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>4,641.2</ENT>
                            <ENT>90</ENT>
                            <ENT>4,177.1</ENT>
                            <ENT>10</ENT>
                            <ENT>464.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Shelf Rockfish 
                                <SU>a</SU>
                            </ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>1,212.1</ENT>
                            <ENT>60.2</ENT>
                            <ENT>729.7</ENT>
                            <ENT>39.8</ENT>
                            <ENT>482.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Shelf Rockfish 
                                <SU>a</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>1,336.2</ENT>
                            <ENT>12.2</ENT>
                            <ENT>163</ENT>
                            <ENT>87.8</ENT>
                            <ENT>1,173.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Slope Rockfish</ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>1,474.6</ENT>
                            <ENT>81</ENT>
                            <ENT>1,194.4</ENT>
                            <ENT>19</ENT>
                            <ENT>280.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Slope Rockfish 
                                <SU>a</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>662.1</ENT>
                            <ENT>63</ENT>
                            <ENT>417.1</ENT>
                            <ENT>37</ENT>
                            <ENT>245</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>a</SU>
                             Allocations decided through the biennial specification process.
                        </TNOTE>
                        <TNOTE>
                            <SU>b</SU>
                             The cowcod non-trawl allocation is further split 50:50 between the commercial and recreational sectors. This results in a sector-specific ACT of 22 mt for the commercial sector and 22 mt for the recreational sector.
                        </TNOTE>
                        <TNOTE>
                            <SU>c</SU>
                             Consistent with regulations at § 660.55(i)(2), the commercial harvest guideline for Pacific whiting is allocated as follows: 3 4 percent for the C/P Coop Program; 24 percent for the MS Coop Program; and 42 percent for the Shorebased IFQ Program. No more than 5 percent of the Shorebased IFQ Program allocation may be taken and retained south of 42° N lat. before the start of the primary Pacific whiting season north of 42° N lat.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="11" OPTS="L2,p7,7/8,i1" CDEF="s25,10C,10C,12C,10C,10C,10C,9C,9C,9C,9C">
                        <TTITLE>
                            Table 1
                            <E T="01">c.</E>
                             to Part 660, Subpart C—Sablefish North of 36° N Lat. Allocations, 2023
                        </TTITLE>
                        <TDESC>[Weight in metric tons]</TDESC>
                        <BOXHD>
                            <CHED H="1">Year</CHED>
                            <CHED H="1">ACL</CHED>
                            <CHED H="1">Set-asides</CHED>
                            <CHED H="2">
                                Tribal 
                                <SU>a</SU>
                            </CHED>
                            <CHED H="2">Research</CHED>
                            <CHED H="1">Recreational estimate</CHED>
                            <CHED H="1">EFP</CHED>
                            <CHED H="1">Commercial HG</CHED>
                            <CHED H="1">Limited entry HG</CHED>
                            <CHED H="2">Percent</CHED>
                            <CHED H="2">mt</CHED>
                            <CHED H="1">Open access HG</CHED>
                            <CHED H="2">Percent</CHED>
                            <CHED H="2">
                                mt 
                                <SU>b</SU>
                            </CHED>
                        </BOXHD>
                        <ROW RUL="s">
                            <ENT I="01">2023</ENT>
                            <ENT>8,486</ENT>
                            <ENT>849</ENT>
                            <ENT>30.7</ENT>
                            <ENT>6</ENT>
                            <ENT>1</ENT>
                            <ENT>7,600</ENT>
                            <ENT>90.6</ENT>
                            <ENT>6,885</ENT>
                            <ENT>9.4</ENT>
                            <ENT>714</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">Year</ENT>
                            <ENT O="oi0">LE all</ENT>
                            <ENT A="03">
                                Limited entry trawl 
                                <SU>c</SU>
                            </ENT>
                            <ENT A="04">
                                Limited entry fixed gear 
                                <SU>d</SU>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="oi0">All trawl</ENT>
                            <ENT O="oi0">At-sea whiting</ENT>
                            <ENT A="01">Shorebased IFQ</ENT>
                            <ENT O="oi0">All FG</ENT>
                            <ENT A="01">Primary</ENT>
                            <ENT A="01">DTL</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2023</ENT>
                            <ENT>6,885</ENT>
                            <ENT>3,994</ENT>
                            <ENT>100</ENT>
                            <ENT A="01">3,893.5</ENT>
                            <ENT>2,892</ENT>
                            <ENT A="01">2,458</ENT>
                            <ENT A="01">434</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>a</SU>
                             The tribal allocation is further reduced by 1.7 percent for discard mortality resulting in 834.6 mt in 2023.
                            <PRTPAGE P="62707"/>
                        </TNOTE>
                        <TNOTE>
                            <SU>b</SU>
                             The open access HG is taken by the incidental OA fishery and the directed OA fishery.
                        </TNOTE>
                        <TNOTE>
                            <SU>c</SU>
                             The trawl allocation is 58 percent of the limited entry HG.
                        </TNOTE>
                        <TNOTE>
                            <SU>d</SU>
                             The limited entry fixed gear allocation is 42 percent of the limited entry HG.
                        </TNOTE>
                    </GPOTABLE>
                    <AMDPAR>11. Revise Tables 2a through 2c to Part 660, Subpart C, to read as follows:</AMDPAR>
                    <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,r50,12,12,12,12">
                        <TTITLE>
                            Table 2
                            <E T="01">a</E>
                            . to Part 660, Subpart C—2024, and Beyond, Specifications of OFL, ABC, ACL, ACT and Fishery Harvest Guidelines 
                        </TTITLE>
                        <TDESC>[Weights in metric tons. Capitalized stocks are overfished.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Stocks</CHED>
                            <CHED H="1">Area</CHED>
                            <CHED H="1">OFL</CHED>
                            <CHED H="1">ABC</CHED>
                            <CHED H="1">
                                ACL 
                                <SU>a</SU>
                            </CHED>
                            <CHED H="1">
                                Fishery HG 
                                <SU>b</SU>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                YELLOWEYE ROCKFISH 
                                <SU>c</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>123</ENT>
                            <ENT>103</ENT>
                            <ENT>66</ENT>
                            <ENT>55.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Arrowtooth Flounder 
                                <SU>d</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>20,459</ENT>
                            <ENT>14,178</ENT>
                            <ENT>14,178</ENT>
                            <ENT>12,083</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Big Skate 
                                <SU>e</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,492</ENT>
                            <ENT>1,267</ENT>
                            <ENT>1,267</ENT>
                            <ENT>1,207.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Black Rockfish 
                                <SU>f</SU>
                            </ENT>
                            <ENT>California (S of 42° N lat.)</ENT>
                            <ENT>364</ENT>
                            <ENT>329</ENT>
                            <ENT>329</ENT>
                            <ENT>326.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Black Rockfish 
                                <SU>g</SU>
                            </ENT>
                            <ENT>Washington (N of 46°16′ N lat.)</ENT>
                            <ENT>319</ENT>
                            <ENT>289</ENT>
                            <ENT>289</ENT>
                            <ENT>270.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Bocaccio 
                                <SU>h</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat.</ENT>
                            <ENT>2,002</ENT>
                            <ENT>1,828</ENT>
                            <ENT>1,828</ENT>
                            <ENT>1,779.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Cabezon 
                                <SU>i</SU>
                            </ENT>
                            <ENT>California (S of 42° N lat.)</ENT>
                            <ENT>185</ENT>
                            <ENT>171</ENT>
                            <ENT>171</ENT>
                            <ENT>169.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                California Scorpionfish 
                                <SU>j</SU>
                            </ENT>
                            <ENT>S of 34°27′ N lat.</ENT>
                            <ENT>280</ENT>
                            <ENT>252</ENT>
                            <ENT>252</ENT>
                            <ENT>248</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Canary Rockfish 
                                <SU>k</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,401</ENT>
                            <ENT>1,267</ENT>
                            <ENT>1,267</ENT>
                            <ENT>1,198.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Chilipepper 
                                <SU>l</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat.</ENT>
                            <ENT>2,346</ENT>
                            <ENT>2,121</ENT>
                            <ENT>2,121</ENT>
                            <ENT>2,023.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Cowcod 
                                <SU>m</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat.</ENT>
                            <ENT>112</ENT>
                            <ENT>79</ENT>
                            <ENT>79</ENT>
                            <ENT>67.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Cowcod</ENT>
                            <ENT>(Conception)</ENT>
                            <ENT>93</ENT>
                            <ENT>67</ENT>
                            <ENT>NA</ENT>
                            <ENT>NA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Cowcod</ENT>
                            <ENT>(Monterey)</ENT>
                            <ENT>19</ENT>
                            <ENT>12</ENT>
                            <ENT>NA</ENT>
                            <ENT>NA</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Darkblotched Rockfish 
                                <SU>n</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>822</ENT>
                            <ENT>750</ENT>
                            <ENT>750</ENT>
                            <ENT>726.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Dover Sole 
                                <SU>o</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>55,859</ENT>
                            <ENT>51,949</ENT>
                            <ENT>50,000</ENT>
                            <ENT>48,402.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                English Sole 
                                <SU>p</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>11,158</ENT>
                            <ENT>8,960</ENT>
                            <ENT>8,960</ENT>
                            <ENT>8,700.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Lingcod 
                                <SU>q</SU>
                            </ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>4,455</ENT>
                            <ENT>3,854</ENT>
                            <ENT>3,854</ENT>
                            <ENT>3,574.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Lingcod 
                                <SU>r</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>855</ENT>
                            <ENT>740</ENT>
                            <ENT>722</ENT>
                            <ENT>706.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Longnose Skate 
                                <SU>s</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,955</ENT>
                            <ENT>1,660</ENT>
                            <ENT>1,660</ENT>
                            <ENT>1,408.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Longspine Thornyhead 
                                <SU>t</SU>
                            </ENT>
                            <ENT>N of 34°27′ N lat</ENT>
                            <ENT>4,433</ENT>
                            <ENT>2,846</ENT>
                            <ENT>2,162</ENT>
                            <ENT>2,108.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Longspine Thornyhead 
                                <SU>u</SU>
                            </ENT>
                            <ENT>S of 34°27′ N lat</ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>683</ENT>
                            <ENT>680.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Pacific Cod 
                                <SU>v</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>3,200</ENT>
                            <ENT>1,926</ENT>
                            <ENT>1,600</ENT>
                            <ENT>1,094</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Pacific Ocean Perch 
                                <SU>w</SU>
                            </ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>4,133</ENT>
                            <ENT>3,443</ENT>
                            <ENT>3,443</ENT>
                            <ENT>3,297.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Pacific Whiting 
                                <SU>x</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>
                                (
                                <SU>x</SU>
                                )
                            </ENT>
                            <ENT>
                                (
                                <SU>x</SU>
                                )
                            </ENT>
                            <ENT>
                                (
                                <SU>x</SU>
                                )
                            </ENT>
                            <ENT>
                                (
                                <SU>x</SU>
                                )
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Petrale Sole 
                                <SU>y</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>3,563</ENT>
                            <ENT>3,285</ENT>
                            <ENT>3,285</ENT>
                            <ENT>2,898.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Sablefish 
                                <SU>z</SU>
                            </ENT>
                            <ENT>N of 36° N lat</ENT>
                            <ENT>10,670</ENT>
                            <ENT>9,923</ENT>
                            <ENT>7,780</ENT>
                            <ENT>See Table 2c</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Sablefish 
                                <SU>aa</SU>
                            </ENT>
                            <ENT>S of 36° N lat</ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>2,143</ENT>
                            <ENT>2,115.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Shortspine Thornyhead 
                                <SU>bb</SU>
                            </ENT>
                            <ENT>N of 34°27′ N lat</ENT>
                            <ENT>3,162</ENT>
                            <ENT>2,030</ENT>
                            <ENT>1,328</ENT>
                            <ENT>1,249.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Shortspine Thornyhead 
                                <SU>cc</SU>
                            </ENT>
                            <ENT>S of 34°27′ N lat</ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>702</ENT>
                            <ENT>695.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Spiny Dogfish 
                                <SU>dd</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,883</ENT>
                            <ENT>1,407</ENT>
                            <ENT>1,407</ENT>
                            <ENT>1,055.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Splitnose 
                                <SU>ee</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>1,766</ENT>
                            <ENT>1,553</ENT>
                            <ENT>1,553</ENT>
                            <ENT>1,534.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Starry Flounder 
                                <SU>ff</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>652</ENT>
                            <ENT>392</ENT>
                            <ENT>392</ENT>
                            <ENT>343.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Widow Rockfish 
                                <SU>gg</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>12,453</ENT>
                            <ENT>11,482</ENT>
                            <ENT>11,482</ENT>
                            <ENT>11,243.7</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">
                                Yellowtail Rockfish 
                                <SU>hh</SU>
                            </ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>6,090</ENT>
                            <ENT>5,560</ENT>
                            <ENT>5,560</ENT>
                            <ENT>4,532.5</ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Stock Complexes</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">
                                Blue/Deacon/Black Rockfish 
                                <SU>ii</SU>
                            </ENT>
                            <ENT>Oregon</ENT>
                            <ENT>671</ENT>
                            <ENT>594</ENT>
                            <ENT>594</ENT>
                            <ENT>592.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Cabezon/Kelp Greenling 
                                <SU>jj</SU>
                            </ENT>
                            <ENT>Washington</ENT>
                            <ENT>22</ENT>
                            <ENT>17</ENT>
                            <ENT>17</ENT>
                            <ENT>15</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Cabezon/Kelp Greenling 
                                <SU>kk</SU>
                            </ENT>
                            <ENT>Oregon</ENT>
                            <ENT>198</ENT>
                            <ENT>180</ENT>
                            <ENT>180</ENT>
                            <ENT>179.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Nearshore Rockfish North 
                                <SU>ll</SU>
                            </ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>109</ENT>
                            <ENT>91</ENT>
                            <ENT>91</ENT>
                            <ENT>87.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Nearshore Rockfish South 
                                <SU>mm</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>1,097</ENT>
                            <ENT>902</ENT>
                            <ENT>891</ENT>
                            <ENT>886.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Other Fish 
                                <SU>nn</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>286</ENT>
                            <ENT>223</ENT>
                            <ENT>223</ENT>
                            <ENT>201.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Other Flatfish 
                                <SU>oo</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>7,946</ENT>
                            <ENT>4,874</ENT>
                            <ENT>4,874</ENT>
                            <ENT>4,653.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Shelf Rockfish North 
                                <SU>pp</SU>
                            </ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>1,610</ENT>
                            <ENT>1,278</ENT>
                            <ENT>1,278</ENT>
                            <ENT>1,207</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Shelf Rockfish South 
                                <SU>qq</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>1,838</ENT>
                            <ENT>1,469</ENT>
                            <ENT>1,469</ENT>
                            <ENT>1,336.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Slope Rockfish North 
                                <SU>rr</SU>
                            </ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>1,797</ENT>
                            <ENT>1,516</ENT>
                            <ENT>1,516</ENT>
                            <ENT>1,450.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Slope Rockfish South 
                                <SU>ss</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>868</ENT>
                            <ENT>697</ENT>
                            <ENT>697</ENT>
                            <ENT>658.1</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>a</SU>
                             Annual catch limits (ACLs), annual catch targets (ACTs) and harvest guidelines (HGs) are specified as total catch values.
                        </TNOTE>
                        <TNOTE>
                            <SU>b</SU>
                             Fishery HGs means the HG or quota after subtracting Pacific Coast treaty Indian tribes allocations and projected catch, projected research catch, deductions for fishing mortality in non-groundfish fisheries, and deductions for EFPs from the ACL or ACT.
                        </TNOTE>
                        <TNOTE>
                            <SU>c</SU>
                             Yelloweye rockfish. The 66 mt ACL is based on the current rebuilding plan with a target year to rebuild of 2029 and an SPR harvest rate of 65 percent. 10.7 mt is deducted from the ACL to accommodate the Tribal fishery (5 mt), EFP fishing (0.12 mt), research catch (2.92 mt), and incidental open access mortality (2.66 mt) resulting in a fishery HG of 55.3 mt. The non-trawl HG is 50.9 mt. The combined non-nearshore/nearshore HG is 10.7 mt. Recreational HGs are: 13.2 mt (Washington); 11.7 mt (Oregon); and 15.3 mt (California). In addition, the non-trawl ACT is 39.9, and the combined non-nearshore/nearshore ACT is 8.4 mt. Recreational ACTs are: 10.4 mt (Washington), 9.2 (Oregon), and 12.0 mt (California).
                        </TNOTE>
                        <TNOTE>
                            <SU>d</SU>
                             Arrowtooth flounder. 2,094.98 mt is deducted from the ACL to accommodate the Tribal fishery (2,041 mt), research catch (12.98 mt) and incidental open access mortality (41 mt), resulting in a fishery HG of 12,083 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>e</SU>
                             Big skate. 59.8 mt is deducted from the ACL to accommodate the Tribal fishery (15 mt), research catch (5.49 mt), and incidental open access mortality (39.31 mt), resulting in a fishery HG of 1,207.2 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>f</SU>
                             Black rockfish (California). 2.26 mt is deducted from the ACL to accommodate EFP fishing (1.0 mt), research catch (0.08 mt), and incidental open access mortality (1.18 mt), resulting in a fishery HG of 326.6 mt.
                            <PRTPAGE P="62708"/>
                        </TNOTE>
                        <TNOTE>
                            <SU>g</SU>
                             Black rockfish (Washington). 18.1 mt is deducted from the ACL to accommodate the Tribal fishery (18 mt) and research catch (0.1 mt), resulting in a fishery HG of 270.5 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>h</SU>
                             Bocaccio south of 40°10′ N lat. Bocaccio are managed with stock-specific harvest specifications south of 40°10′ N lat. and within the Minor Shelf Rockfish complex north of 40°10′ N lat. 48.12 mt is deducted from the ACL to accommodate EFP fishing (40 mt), research catch (5.6 mt), and incidental open access mortality (2.52 mt), resulting in a fishery HG of 1,779.9 mt. The California recreational fishery south of 40°10′ N lat. has an HG of 749.7 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>i</SU>
                             Cabezon (California). 1.63 mt is deducted from the ACL to accommodate EFP fishing (1 mt), research catch (0.02 mt), and incidental open access mortality (0.61 mt), resulting in a fishery HG of 169.4 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>j</SU>
                             California scorpionfish south of 34°27′ N lat. 3.89 mt is deducted from the ACL to accommodate research catch (0.18 mt) and incidental open access mortality (3.71 mt), resulting in a fishery HG of 248 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>k</SU>
                             Canary rockfish. 68.91 mt is deducted from the ACL to accommodate the Tribal fishery (50 mt), EFP fishing (6 mt), research catch (10.08 mt), and incidental open access mortality (2.83 mt), resulting in a fishery HG of 1,198.1 mt. The combined nearshore/non-nearshore HG is 119.4 mt. Recreational HGs are: 40.8 mt (Washington); 61.4 mt (Oregon); and 110.2 mt (California).
                        </TNOTE>
                        <TNOTE>
                            <SU>l</SU>
                             Chilipepper rockfish south of 40°10′ N lat. Chilipepper are managed with stock-specific harvest specifications south of 40°10′ N lat. and within the Minor Shelf Rockfish complex north of 40°10′ N lat. 97.7 mt is deducted from the ACL to accommodate EFP fishing (70 mt), research catch (14.04 mt), incidental open access mortality (13.66 mt), resulting in a fishery HG of 2,023.4 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>m</SU>
                             Cowcod south of 40°10′ N lat. Cowcod are managed with stock-specific harvest specifications south of 40°10′ N lat. and within the Minor Shelf Rockfish complex north of 40°10′ N lat. 11.17 mt is deducted from the ACL to accommodate EFP fishing (1 mt), research catch (10 mt), and incidental open access mortality (0.17 mt), resulting in a fishery HG of 67.8 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>n</SU>
                             Darkblotched rockfish. 23.76 mt is deducted from the ACL to accommodate the Tribal fishery (5 mt), EFP fishing (0.5 mt), research catch (8.46 mt), and incidental open access mortality (9.8 mt) resulting in a fishery HG of 726.2 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>o</SU>
                             Dover sole. 1,597.11 mt is deducted from the ACL to accommodate the Tribal fishery (1,497 mt), research catch (50.84 mt), and incidental open access mortality (49.27 mt), resulting in a fishery HG of 48,402.9 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>p</SU>
                             English sole. 259.52 mt is deducted from the ACL to accommodate the Tribal fishery (200 mt), research catch (17 mt), and incidental open access mortality (42.52 mt), resulting in a fishery HG of 8,700.5 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>q</SU>
                             Lingcod north of 40°10′ N lat. 279.63 mt is deducted from the ACL for the Tribal fishery (250 mt), research catch (17.71 mt), and incidental open access mortality (11.92 mt) resulting in a fishery HG of 3,574.4 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>r</SU>
                             Lingcod south of 40°10′ N lat. 15.5 mt is deducted from the ACL to accommodate EFP fishing (4 mt), research catch (3.19 mt), and incidental open access mortality (8.31 mt), resulting in a fishery HG of 706.5 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>s</SU>
                             Longnose skate. 251.3 mt is deducted from the ACL to accommodate the Tribal fishery (220 mt), and research catch (12.46 mt), and incidental open access mortality (18.84 mt), resulting in a fishery HG of 1,408.7 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>t</SU>
                             Longspine thornyhead north of 34°27′ N lat. 53.71 mt is deducted from the ACL to accommodate the Tribal fishery (30 mt), research catch (17.49 mt), and incidental open access mortality (6.22 mt), resulting in a fishery HG of 2,108.3 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>u</SU>
                             Longspine thornyhead south of 34°27′ N lat. 2.24 mt is deducted from the ACL to accommodate research catch (1.41 mt) and incidental open access mortality (0.83 mt), resulting in a fishery HG of 680.8 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>v</SU>
                             Pacific cod. 506 mt is deducted from the ACL to accommodate the Tribal fishery (500 mt), research catch (5.47 mt), and incidental open access mortality (0.53 mt), resulting in a fishery HG of 1,094 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>w</SU>
                             Pacific ocean perch north of 40°10′ N lat. Pacific ocean perch are managed with stock-specific harvest specifications north of 40°10′ N lat. and within the Minor Slope Rockfish complex south of 40°10′ N lat. 145.48 mt is deducted from the ACL to accommodate the Tribal fishery (130 mt), EFP fishing, research catch (5.39 mt), and incidental open access mortality (10.09 mt), resulting in a fishery HG of 3,297.5 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>x</SU>
                             Pacific whiting. Pacific whiting are assessed annually. The final specifications will be determined consistent with the U.S.-Canada Pacific Whiting Agreement and will be announced after the Council's April 2023 meeting.
                        </TNOTE>
                        <TNOTE>
                            <SU>y</SU>
                             Petrale sole. 386.24 mt is deducted from the ACL to accommodate the Tribal fishery (350 mt), EFP fishing (1 mt), research catch (24.14 mt), and incidental open access mortality (11.1 mt), resulting in a fishery HG of 2,898.8 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>z</SU>
                             Sablefish north of 36° N lat. The sablefish coastwide ACL value is not specified in regulations. The sablefish coastwide ACL value is apportioned north and south of 36° N lat., using the rolling 5-year average estimated swept area biomass from the NMFS NWFSC trawl survey, with 78.4 percent apportioned north of 36° N lat. and 21.6 percent apportioned south of 36° N lat. The northern ACL is 7,780 mt and is reduced by 778 mt for the Tribal allocation (10 percent of the ACL north of 36° N lat.). The 778 mt Tribal allocation is reduced by 1.7 percent to account for discard mortality. Detailed sablefish allocations are shown in Table 1c.
                        </TNOTE>
                        <TNOTE>
                            <SU>aa</SU>
                             Sablefish south of 36° N lat. The ACL for the area south of 36° N lat. is 2,143 mt (21.6 percent of the calculated coastwide ACL value). 27.4 mt is deducted from the ACL to accommodate research catch (2.40 mt) and the incidental open access fishery (25 mt), resulting in a fishery HG of 2,115.6 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>bb</SU>
                             Shortspine thornyhead north of 34°27′ N lat. 78.3 mt is deducted from the ACL to accommodate the Tribal fishery (50 mt), research catch (10.48 mt), and incidental open access mortality (17.82 mt), resulting in a fishery HG of 1,249.7 mt for the area north of 34°27′ N lat.
                        </TNOTE>
                        <TNOTE>
                            <SU>cc</SU>
                             Shortspine thornyhead south of 34°27′ N lat. 6.71 mt is deducted from the ACL to accommodate research catch (0.71 mt) and incidental open access mortality (6 mt), resulting in a fishery HG of 695.3 mt for the area south of 34°27′ N lat.
                        </TNOTE>
                        <TNOTE>
                            <SU>dd</SU>
                             Spiny dogfish. 351.48 mt is deducted from the ACL to accommodate the Tribal fishery (275 mt), EFP fishing (1 mt), research catch (41.85 mt), and incidental open access mortality (33.63 mt), resulting in a fishery HG of 1,055.5 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>ee</SU>
                             Splitnose rockfish south of 40°10′ N lat. Splitnose rockfish in the north is managed in the Slope Rockfish complex and with stock-specific harvest specifications south of 40°10′ N lat. 18.42 mt is deducted from the ACL to accommodate EFP fishing (1.5 mt), research catch (11.17 mt), and incidental open access mortality (5.75 mt), resulting in a fishery HG of 1,534.3 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>ff</SU>
                             Starry flounder. 48.28 mt is deducted from the ACL to accommodate the Tribal fishery (2 mt), research catch (0.57 mt), and incidental open access mortality (45.71 mt), resulting in a fishery HG of 343.7 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>gg</SU>
                             Widow rockfish. 238.32 mt is deducted from the ACL to accommodate the Tribal fishery (200 mt), EFP fishing (18 mt), research catch (17.27 mt), and incidental open access mortality (3.05 mt), resulting in a fishery HG of 11,243.7 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>hh</SU>
                             Yellowtail rockfish north of 40°10′ N lat. Yellowtail rockfish are managed with stock-specific harvest specifications north of 40°10′ N lat. and within the Minor Shelf Rockfish complex south of 40°10′ N lat. 1,027.55 mt is deducted from the ACL to accommodate the Tribal fishery (1,000 mt), research catch (20.55 mt), and incidental open access mortality (7 mt), resulting in a fishery HG of 4,532.5 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>ii</SU>
                             Black rockfish/Blue rockfish/Deacon rockfish (Oregon). 1.82 mt is deducted from the ACL to accommodate research catch (0.08 mt), and incidental open access mortality (1.74 mt), resulting in a fishery HG of 592.2 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>jj</SU>
                             Cabezon/kelp greenling (Washington). 2 mt is deducted from the ACL to accommodate the Tribal fishery, resulting in a fishery HG is 15 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>kk</SU>
                             Cabezon/kelp greenling (Oregon). 0.79 mt is deducted from the ACL to accommodate research catch (0.05 mt) and incidental open access mortality (0.74 mt), resulting in a fishery HG of 179.2 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>ll</SU>
                             Nearshore Rockfish north of 40°10′ N lat. 3.27 mt is deducted from the ACL to accommodate the Tribal fishery (1.5 mt), research catch (0.47 mt), and incidental open access mortality (1.31 mt), resulting in a fishery HG of 87.7 mt. State-specific HGs are 17.2 mt (Washington), 30.9 mt (Oregon), and 39.9 mt (California). The ACT for copper rockfish (California) is 6.99 mt. The ACT for quillback rockfish (California) is 0.96 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>mm</SU>
                             Nearshore Rockfish south of 40°10′ N lat. 4.54 mt is deducted from the ACL to accommodate research catch (2.68 mt) and incidental open access mortality (1.86 mt), resulting in a fishery HG of 886.5 mt. The ACT for copper rockfish is 87.73 mt. The ACT for quillback rockfish is 0.97 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>nn</SU>
                             Other Fish. The Other Fish complex is comprised of kelp greenling off California and leopard shark coastwide. 21.24 mt is deducted from the ACL to accommodate research catch (6.29 mt) and incidental open access mortality (14.95 mt), resulting in a fishery HG of 201.8 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>oo</SU>
                             Other Flatfish. The Other Flatfish complex is comprised of flatfish species managed in the PCGFMP that are not managed with stock-specific OFLs/ABCs/ACLs. Most of the species in the Other Flatfish complex are unassessed and include: butter sole, curlfin sole, flathead sole, Pacific sanddab, rock sole, sand sole, and rex sole. 220.79 mt is deducted from the ACL to accommodate the Tribal fishery (60 mt), research catch (23.63 mt), and incidental open access mortality (137.16 mt), resulting in a fishery HG of 4,653.2 mt.
                            <PRTPAGE P="62709"/>
                        </TNOTE>
                        <TNOTE>
                            <SU>pp</SU>
                             Shelf Rockfish north of 40°10′ N lat. 70.94 mt is deducted from the ACL to accommodate the Tribal fishery (30 mt), research catch (15.32 mt), and incidental open access mortality (25.62 mt), resulting in a fishery HG of 1,207.1 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>qq</SU>
                             Shelf Rockfish south of 40°10′ N lat. 132.77 mt is deducted from the ACL to accommodate EFP fishing (50 mt), research catch (15.1 mt), and incidental open access mortality (67.67 mt) resulting in a fishery HG of 1,336.2 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>rr</SU>
                            r Slope Rockfish north of 40°10′ N lat. 65.39 mt is deducted from the ACL to accommodate the Tribal fishery (36 mt), research catch (10.51 mt), and incidental open access mortality (18.88 mt), resulting in a fishery HG of 1,450.6 mt.
                        </TNOTE>
                        <TNOTE>
                            <SU>ss</SU>
                             Slope Rockfish south of 40°10′ N lat. 38.94 mt is deducted from the ACL to accommodate EFP fishing (1 mt), research catch (18.21 mt), and incidental open access mortality (19.73 mt), resulting in a fishery HG of 658.1 mt. Blackgill rockfish has a stock-specific HG for the entire groundfish fishery south of 40°10′ N lat. set equal to the species' contribution to the 40-10-adjusted ACL. Harvest of blackgill rockfish in all groundfish fisheries south of 40°10′ N lat. counts against this HG of 169.9 mt.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="7" OPTS="L2,p7,7/8,i1" CDEF="s50,r50,12,12,12,12,12">
                        <TTITLE>
                            Table 
                            <E T="01">2b.</E>
                             to Part 660, Subpart C—2024, and Beyond, Allocations by Species or Species Group
                        </TTITLE>
                        <TDESC>[Weight in metric tons]</TDESC>
                        <BOXHD>
                            <CHED H="1">Stocks/stock complexes</CHED>
                            <CHED H="1">Area</CHED>
                            <CHED H="1">
                                Fishery HG 
                                <LI>or ACT</LI>
                            </CHED>
                            <CHED H="1">Trawl</CHED>
                            <CHED H="2">%</CHED>
                            <CHED H="2">Mt</CHED>
                            <CHED H="1">Non-trawl</CHED>
                            <CHED H="2">%</CHED>
                            <CHED H="2">Mt</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                YELLOWEYE ROCKFISH 
                                <SU>a</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>55.3</ENT>
                            <ENT>8</ENT>
                            <ENT>4.4</ENT>
                            <ENT>92</ENT>
                            <ENT>50.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Arrowtooth flounder</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>12,083</ENT>
                            <ENT>95</ENT>
                            <ENT>11,478.9</ENT>
                            <ENT>5</ENT>
                            <ENT>604.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Big skate 
                                <SU>a</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,207.2</ENT>
                            <ENT>95</ENT>
                            <ENT>1,146.8</ENT>
                            <ENT>5</ENT>
                            <ENT>60.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Bocaccio 
                                <SU>a</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>1,779.9</ENT>
                            <ENT>39.04</ENT>
                            <ENT>694.9</ENT>
                            <ENT>60.96</ENT>
                            <ENT>1,085</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Canary rockfish 
                                <SU>a</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,198.1</ENT>
                            <ENT>72.3</ENT>
                            <ENT>866.2</ENT>
                            <ENT>27.7</ENT>
                            <ENT>331.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Chilipepper rockfish</ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>2,023.4</ENT>
                            <ENT>75</ENT>
                            <ENT>1,517.6</ENT>
                            <ENT>25</ENT>
                            <ENT>505.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Cowcod 
                                <SU>a</SU>
                                 
                                <SU>b</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>67.8</ENT>
                            <ENT>36</ENT>
                            <ENT>24.4</ENT>
                            <ENT>64</ENT>
                            <ENT>43.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Darkblotched rockfish</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>726.2</ENT>
                            <ENT>95</ENT>
                            <ENT>689.9</ENT>
                            <ENT>5</ENT>
                            <ENT>36.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Dover sole</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>4,8402.9</ENT>
                            <ENT>95</ENT>
                            <ENT>45,982.7</ENT>
                            <ENT>5</ENT>
                            <ENT>2,420.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">English sole</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>8,700.5</ENT>
                            <ENT>95</ENT>
                            <ENT>8265.5</ENT>
                            <ENT>5</ENT>
                            <ENT>435</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Lingcod</ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>3,574.4</ENT>
                            <ENT>45</ENT>
                            <ENT>1,608.5</ENT>
                            <ENT>55</ENT>
                            <ENT>1,965.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Lingcod 
                                <SU>a</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>706.5</ENT>
                            <ENT>40</ENT>
                            <ENT>282.6</ENT>
                            <ENT>60</ENT>
                            <ENT>423.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Longnose skate 
                                <SU>a</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,408.7</ENT>
                            <ENT>90</ENT>
                            <ENT>1,267.8</ENT>
                            <ENT>10</ENT>
                            <ENT>140.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Longspine thornyhead</ENT>
                            <ENT>N of 34°27′ N lat</ENT>
                            <ENT>2,108.3</ENT>
                            <ENT>95</ENT>
                            <ENT>2,002.9</ENT>
                            <ENT>5</ENT>
                            <ENT>105.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pacific cod</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>1,094</ENT>
                            <ENT>95</ENT>
                            <ENT>1,039.3</ENT>
                            <ENT>5</ENT>
                            <ENT>54.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pacific ocean perch</ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>3,297.5</ENT>
                            <ENT>95</ENT>
                            <ENT>3,132.6</ENT>
                            <ENT>5</ENT>
                            <ENT>164.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Pacific whiting 
                                <SU>c</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>TBD</ENT>
                            <ENT>100</ENT>
                            <ENT>TBD</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW RUL="n,n,n,s">
                            <ENT I="01">
                                Petrale sole 
                                <SU>a</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>2898.8</ENT>
                            <ENT/>
                            <ENT>2,868.8</ENT>
                            <ENT/>
                            <ENT>30</ENT>
                        </ROW>
                        <ROW RUL="n,n,n,s">
                            <ENT I="01">Sablefish</ENT>
                            <ENT>N of 36° N lat</ENT>
                            <ENT>NA</ENT>
                            <ENT A="03">See Table 2c</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sablefish</ENT>
                            <ENT>S of 36° N lat</ENT>
                            <ENT>2,115.6</ENT>
                            <ENT>42</ENT>
                            <ENT>888.6</ENT>
                            <ENT>58</ENT>
                            <ENT>1,227</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Shortspine thornyhead</ENT>
                            <ENT>N of 34°27′ N lat</ENT>
                            <ENT>1,249.7</ENT>
                            <ENT>95</ENT>
                            <ENT>1,187.2</ENT>
                            <ENT>5</ENT>
                            <ENT>62.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Shortspine thornyhead</ENT>
                            <ENT>S of 34°27′ N lat</ENT>
                            <ENT>695.3</ENT>
                            <ENT/>
                            <ENT>50</ENT>
                            <ENT/>
                            <ENT>645.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Splitnose rockfish</ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>1,534.3</ENT>
                            <ENT>95</ENT>
                            <ENT>1,457.6</ENT>
                            <ENT>5</ENT>
                            <ENT>76.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Starry flounder</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>343.7</ENT>
                            <ENT>50</ENT>
                            <ENT>171.9</ENT>
                            <ENT>50</ENT>
                            <ENT>171.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Widow rockfish 
                                <SU>a</SU>
                            </ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>11,243.7</ENT>
                            <ENT/>
                            <ENT>10,843.7</ENT>
                            <ENT/>
                            <ENT>400</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Yellowtail rockfish</ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>4,532.5</ENT>
                            <ENT>88</ENT>
                            <ENT>3,988.6</ENT>
                            <ENT>12</ENT>
                            <ENT>543.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Other Flatfish</ENT>
                            <ENT>Coastwide</ENT>
                            <ENT>4,653.2</ENT>
                            <ENT>90</ENT>
                            <ENT>4,187.9</ENT>
                            <ENT>10</ENT>
                            <ENT>465.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Shelf Rockfish 
                                <SU>a</SU>
                            </ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>1,207.1</ENT>
                            <ENT>60.2</ENT>
                            <ENT>726.7</ENT>
                            <ENT>39.8</ENT>
                            <ENT>480.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Shelf Rockfish 
                                <SU>a</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>1,336.2</ENT>
                            <ENT>12.2</ENT>
                            <ENT>163</ENT>
                            <ENT>87.8</ENT>
                            <ENT>1,173.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Slope Rockfish</ENT>
                            <ENT>N of 40°10′ N lat</ENT>
                            <ENT>1,450.6</ENT>
                            <ENT>81</ENT>
                            <ENT>1,175</ENT>
                            <ENT>19</ENT>
                            <ENT>275.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Slope Rockfish 
                                <SU>a</SU>
                            </ENT>
                            <ENT>S of 40°10′ N lat</ENT>
                            <ENT>658.1</ENT>
                            <ENT>63</ENT>
                            <ENT>414.6</ENT>
                            <ENT>37</ENT>
                            <ENT>243.5</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>a</SU>
                             Allocations decided through the biennial specification process.
                        </TNOTE>
                        <TNOTE>
                            <SU>b</SU>
                             The cowcod non-trawl allocation is further split 50:50 between the commercial and recreational sectors. This results in a sector-specific ACT of 21.7 mt for the commercial sector and 21.7 mt for the recreational sector.
                        </TNOTE>
                        <TNOTE>
                            <SU>c</SU>
                             Consistent with regulations at § 660.55(i)(2), the commercial harvest guideline for Pacific whiting is allocated as follows: 34 percent for the C/P Coop Program; 24 percent for the MS Coop Program; and 42 percent for the Shorebased IFQ Program. No more than 5 percent of the Shorebased IFQ Program allocation may be taken and retained south of 42° N lat. before the start of the primary Pacific whiting season north of 42° N lat.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="11" OPTS="L2,p7,7/8,i1" CDEF="s25,10C,10C,12C,10C,10C,10C,9C,9C,9C,9C">
                        <TTITLE>
                            Table 
                            <E T="01">2c.</E>
                             to Part 660, Subpart C—Sablefish North of 36° N Lat. Allocations, 2024 and Beyond
                        </TTITLE>
                        <TDESC>[Weights in metric tons]</TDESC>
                        <BOXHD>
                            <CHED H="1">Year</CHED>
                            <CHED H="1">ACL</CHED>
                            <CHED H="1">Set-asides</CHED>
                            <CHED H="2">
                                Tribal 
                                <SU>a</SU>
                            </CHED>
                            <CHED H="2">Research</CHED>
                            <CHED H="1">
                                Recreational
                                <LI>estimate</LI>
                            </CHED>
                            <CHED H="1">EFP</CHED>
                            <CHED H="1">Commercial HG</CHED>
                            <CHED H="1">Limited entry HG</CHED>
                            <CHED H="2">Percent</CHED>
                            <CHED H="2">mt</CHED>
                            <CHED H="1">Open access HG</CHED>
                            <CHED H="2">Percent</CHED>
                            <CHED H="2">
                                mt 
                                <SU>b</SU>
                            </CHED>
                        </BOXHD>
                        <ROW RUL="s">
                            <ENT I="01">2024</ENT>
                            <ENT>7,780</ENT>
                            <ENT>778</ENT>
                            <ENT>30.7</ENT>
                            <ENT>6</ENT>
                            <ENT>1</ENT>
                            <ENT>6,964</ENT>
                            <ENT>90.6</ENT>
                            <ENT>6,309</ENT>
                            <ENT>9.4</ENT>
                            <ENT>665</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">Year</ENT>
                            <ENT O="oi0">LE All</ENT>
                            <ENT A="03">
                                Limited Entry Trawl 
                                <SU>c</SU>
                            </ENT>
                            <ENT A="04">
                                Limited Entry Fixed Gear 
                                <SU>d</SU>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="oi0">All Trawl</ENT>
                            <ENT O="oi0">At-sea whiting</ENT>
                            <ENT A="01">Shorebased IFQ</ENT>
                            <ENT O="oi0">All FG</ENT>
                            <ENT A="01">Primary</ENT>
                            <ENT A="01">DTL</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2024</ENT>
                            <ENT>6,309</ENT>
                            <ENT>3,659</ENT>
                            <ENT>100</ENT>
                            <ENT A="01">3,559</ENT>
                            <ENT>2,650</ENT>
                            <ENT A="01">2,252</ENT>
                            <ENT A="01">397</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>a</SU>
                             The tribal allocation is further reduced by 1.7 percent for discard mortality resulting in 764.8 mt in 2024.
                        </TNOTE>
                        <TNOTE>
                            <SU>b</SU>
                             The open access HG is taken by the incidental OA fishery and the directed OA fishery.
                        </TNOTE>
                        <TNOTE>
                            <SU>c</SU>
                             The trawl allocation is 58 percent of the limited entry HG.
                        </TNOTE>
                        <TNOTE>
                            <SU>d</SU>
                             The limited entry fixed gear allocation is 42 percent of the limited entry HG.
                        </TNOTE>
                    </GPOTABLE>
                    <STARS/>
                    <AMDPAR>12. In § 660.111, revise the definition of “Block area closures or BACs” to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 660.111 </SECTNO>
                        <SUBJECT>Trawl fishery—definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Block area closures</E>
                             or 
                            <E T="03">BACs</E>
                             are a type of groundfish conservation area, defined at § 660.11, bounded on the north and south by commonly used geographic coordinates, defined at § 660.11, and on the east and west by the EEZ, and 
                            <PRTPAGE P="62710"/>
                            boundary lines approximating depth contours, defined with latitude and longitude coordinates at §§ 660.71 through 660.74 (10 fm through 250 fm), and § 660.76 (700 fm). BACs may be implemented or modified as routine management measures, per regulations at § 660.60(c). BACs may be implemented in the EEZ seaward of Washington, Oregon and California for vessels using limited entry bottom trawl and/or midwater trawl gear. BACs may be implemented within tribal Usual and Accustomed fishing areas but may only apply to non-tribal vessels. BACs may close areas to specific trawl gear types (
                            <E T="03">e.g.,</E>
                             closed for midwater trawl, bottom trawl, or bottom trawl unless using selective flatfish trawl) and/or specific programs within the trawl fishery (
                            <E T="03">e.g.,</E>
                             Pacific whiting fishery or MS Coop Program). BACs may vary in their geographic boundaries and duration. Their geographic boundaries, applicable gear type(s) and/or specific trawl fishery program, and effective dates will be announced in the 
                            <E T="04">Federal Register</E>
                            . BACs may have a specific termination date as described in the 
                            <E T="04">Federal Register</E>
                            , or may be in effect until modified. BACs that are in effect until modified by Council recommendation and subsequent NMFS action are set out in Tables 1 (North) and 1 (South) of this subpart.
                        </P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>13. In § 660.140, revise paragraphs (c)(3)(iii) and (iv), and Table 1 to paragraph (d)(1)(ii)(D) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 660.140 </SECTNO>
                        <SUBJECT> Shorebased IFQ Program.</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(3) * * *</P>
                        <P>(iii) For IFQ species listed in the trawl/non-trawl allocation table, specified at § 660.55(c), subpart C, allocations are determined by applying the trawl column percent to the fishery harvest guideline minus any set-asides for the mothership and C/P sectors for that species.</P>
                        <P>(iv) The remaining IFQ species (canary rockfish, bocaccio, cowcod, yelloweye rockfish, darkblotched rockfish, POP, widow rockfish, minor shelf rockfish N of 40°10′ N lat., and minor shelf rockfish S of 40°10′ N lat., and minor slope rockfish S of 40°10′ N lat.) are allocated through the biennial specifications and management measures process minus any set-asides for the mothership and C/P sectors for that species.</P>
                        <STARS/>
                        <P>(d) * * *</P>
                        <P>(1) * * *</P>
                        <P>(ii) * * *</P>
                        <P>(D) * * *</P>
                        <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,r50,15,15">
                            <TTITLE>
                                Table 1 to Paragraph 
                                <E T="01">(d)(1)(ii)(D)</E>
                                —Shorebased Trawl Allocations for 2023 and 2024
                            </TTITLE>
                            <BOXHD>
                                <CHED H="1">IFQ species</CHED>
                                <CHED H="1">Area</CHED>
                                <CHED H="1">
                                    2023 Shorebased
                                    <LI>trawl allocation</LI>
                                    <LI>(mt)</LI>
                                </CHED>
                                <CHED H="1">
                                    2024 Shorebased
                                    <LI>trawl allocation</LI>
                                    <LI>(mt)</LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">YELLOWEYE ROCKFISH</ENT>
                                <ENT>Coastwide</ENT>
                                <ENT>4.42</ENT>
                                <ENT>4.42</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Arrowtooth flounder</ENT>
                                <ENT>Coastwide</ENT>
                                <ENT>15,640.17</ENT>
                                <ENT>11,408.87</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Bocaccio</ENT>
                                <ENT>South of 40°10′ N lat</ENT>
                                <ENT>700.33</ENT>
                                <ENT>694.87</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Canary rockfish</ENT>
                                <ENT>Coastwide</ENT>
                                <ENT>842.50</ENT>
                                <ENT>830.22</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Chilipepper</ENT>
                                <ENT>South of 40°10′ N lat</ENT>
                                <ENT>1,563.80</ENT>
                                <ENT>1517.60</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Cowcod</ENT>
                                <ENT>South of 40°10′ N lat</ENT>
                                <ENT>24.80</ENT>
                                <ENT>24.42</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Darkblotched rockfish</ENT>
                                <ENT>Coastwide</ENT>
                                <ENT>646.78</ENT>
                                <ENT>613.53</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Dover sole</ENT>
                                <ENT>Coastwide</ENT>
                                <ENT>45,972.75</ENT>
                                <ENT>45,972.75</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">English sole</ENT>
                                <ENT>Coastwide</ENT>
                                <ENT>8,320.56</ENT>
                                <ENT>8,265.46</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Lingcod</ENT>
                                <ENT>North of 40°10′ N lat</ENT>
                                <ENT>1,829.27</ENT>
                                <ENT>1,593.47</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Lingcod</ENT>
                                <ENT>South of 40°10′ N lat</ENT>
                                <ENT>284.20</ENT>
                                <ENT>282.60</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Longspine thornyhead</ENT>
                                <ENT>North of 34°27′ N lat</ENT>
                                <ENT>2,129.23</ENT>
                                <ENT>2,002.88</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Pacific cod</ENT>
                                <ENT>Coastwide</ENT>
                                <ENT>1,039.30</ENT>
                                <ENT>1,039.30</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    Pacific halibut (IBQ) 
                                    <SU>a</SU>
                                </ENT>
                                <ENT>North of 40°10′ N lat</ENT>
                                <ENT>TBD</ENT>
                                <ENT>TBD</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Pacific ocean perch</ENT>
                                <ENT>North of 40°10′ N lat</ENT>
                                <ENT>2,956.14</ENT>
                                <ENT>2,832.64</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    Pacific whiting 
                                    <SU>a</SU>
                                </ENT>
                                <ENT>Coastwide</ENT>
                                <ENT>TBD</ENT>
                                <ENT>TBD</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Petrale sole</ENT>
                                <ENT>Coastwide</ENT>
                                <ENT>3,063.76</ENT>
                                <ENT>2,863.76</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Sablefish</ENT>
                                <ENT>North of 36° N lat</ENT>
                                <ENT>3,893.50</ENT>
                                <ENT>3,559.38</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Sablefish</ENT>
                                <ENT>South of 36° N lat</ENT>
                                <ENT>970.00</ENT>
                                <ENT>889.00</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Shortspine thornyhead</ENT>
                                <ENT>North of 34°27′ N lat</ENT>
                                <ENT>1,146.67</ENT>
                                <ENT>1,117.22</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Shortspine thornyhead</ENT>
                                <ENT>South of 34°27′ N lat</ENT>
                                <ENT>50</ENT>
                                <ENT>50</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Splitnose rockfish</ENT>
                                <ENT>South of 40°10′ N lat</ENT>
                                <ENT>1,494.70</ENT>
                                <ENT>1,457.60</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Starry flounder</ENT>
                                <ENT>Coastwide</ENT>
                                <ENT>171.86</ENT>
                                <ENT>171.86</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Widow rockfish</ENT>
                                <ENT>Coastwide</ENT>
                                <ENT>11,509.68</ENT>
                                <ENT>10,367.68</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Yellowtail rockfish</ENT>
                                <ENT>North of 40°10′ N lat</ENT>
                                <ENT>3,761.84</ENT>
                                <ENT>3,668.56</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Other Flatfish complex</ENT>
                                <ENT>Coastwide</ENT>
                                <ENT>4,142.09</ENT>
                                <ENT>4,152.89</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Shelf Rockfish complex</ENT>
                                <ENT>North of 40°10′ N lat</ENT>
                                <ENT>694.70</ENT>
                                <ENT>691.65</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Shelf Rockfish complex</ENT>
                                <ENT>South of 40°10′ N lat</ENT>
                                <ENT>163.02</ENT>
                                <ENT>163.02</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Slope Rockfish complex</ENT>
                                <ENT>North of 40°10′ N lat</ENT>
                                <ENT>894.43</ENT>
                                <ENT>874.99</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Slope Rockfish complex</ENT>
                                <ENT>South of 40°10′ N lat</ENT>
                                <ENT>417.1</ENT>
                                <ENT>414.58</ENT>
                            </ROW>
                            <TNOTE>
                                <SU>a</SU>
                                 Managed through an international process. These allocation will be updated when announced.
                            </TNOTE>
                        </GPOTABLE>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>14. In §  660.150, revise paragraph (c)(1) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 660.150 </SECTNO>
                        <SUBJECT>Mothership (MS) Coop Program.</SUBJECT>
                        <STARS/>
                        <P>
                            (c) * * *—(1) 
                            <E T="03">MS Coop Program species.</E>
                             All species other than Pacific whiting are managed with set-asides for the MS and C/P Coop Programs, as described in the biennial specifications.
                        </P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>15. In §  660.160, revise paragraph (c)(1)(ii) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 660.160 </SECTNO>
                        <SUBJECT>Catcher/processor (C/P) Coop Program.</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>
                            (1) * * *
                            <PRTPAGE P="62711"/>
                        </P>
                        <P>(ii) Species with set-asides for the MS and C/P Programs, as described in the biennial specifications.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>16. In §  660.213, revise paragraph (d)(2) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 660.213 </SECTNO>
                        <SUBJECT>Fixed gear fishery—recordkeeping and reporting.</SUBJECT>
                        <STARS/>
                        <P>(d) * * *</P>
                        <P>(2) For participants in the sablefish primary season, the cumulative limit period to which this requirement applies is April 1 through December 31 or, for an individual vessel owner, when the tier limit for the permit(s) registered to the vessel has been reached, whichever is earlier.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>17. In § 660.230, revise (c)(2)(i) through (iii) and add paragraph (d)(11)(v) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 660.230 </SECTNO>
                        <SUBJECT> Fixed gear fishery—management measures.</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(2) * * *</P>
                        <P>
                            (i) 
                            <E T="03">Coastwide</E>
                            —arrowtooth flounder, big skate, black rockfish, blue/deacon rockfish, canary rockfish, darkblotched rockfish, Dover sole, English sole, lingcod, longnose skate, longspine thornyhead, petrale sole, minor nearshore rockfish, minor shelf rockfish, minor slope rockfish, other fish, other flatfish, Pacific cod, Pacific whiting, rougheye/blackspotted rockfish, sablefish, shortbelly rockfish, shortraker rockfish, shortspine thornyhead, spiny dogfish, starry flounder, widow rockfish, and yelloweye rockfish;
                        </P>
                        <P>
                            (ii) 
                            <E T="03">North of 40°10′ N lat.</E>
                            —cabezon (California), copper rockfish (California), Oregon cabezon/kelp greenling complex, POP, quillback rockfish (California), Washington cabezon/kelp greenling complex, yellowtail rockfish; and
                        </P>
                        <P>
                            (iii) 
                            <E T="03">South of 40°10′ N lat.</E>
                            —blackgill rockfish, bocaccio, bronzespotted rockfish, cabezon, California scorpionfish, chilipepper rockfish, copper rockfish, cowcod, minor shallow nearshore rockfish, minor deeper nearshore rockfish, Pacific sanddabs, quillback rockfish, splitnose rockfish, and vermilion rockfish.
                        </P>
                        <P>(d) * * *</P>
                        <P>(11) * * *</P>
                        <P>(v) It is lawful to fish within the non-trawl RCA seaward of Oregon and California (between 46°16′ N lat. and the U.S./Mexico border) with open access non-bottom contact hook-and-line gear configurations as specified at § 660.330(b)(3)(i-ii), subject to applicable crossover provisions at § 660.60(h)(7), and provided that a valid declaration report as required at § 660.13(d) has been filed with NMFS OLE.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>18. In §  660.231, revise paragraphs (b)(1), (b)(3)(i), and (b)(3)(iv) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 660.231 </SECTNO>
                        <SUBJECT>Limited entry fixed gear sablefish primary fishery.</SUBJECT>
                        <STARS/>
                        <P>
                            (b) * * *—(1) 
                            <E T="03">Season dates.</E>
                             North of 36° N lat., the sablefish primary season for the limited entry, fixed gear, sablefish-endorsed vessels begins at 12 noon local time on April 1 and closes at 12 noon local time on December 31, or closes for an individual vessel owner when the tier limit for the sablefish endorsed permit(s) registered to the vessel has been reached, whichever is earlier, unless otherwise announced by the Regional Administrator through the routine management measures process described at § 660.60(c).
                        </P>
                        <STARS/>
                        <P>(3) * * *</P>
                        <P>
                            (i) A vessel participating in the primary season will be constrained by the sablefish cumulative limit associated with each of the permits registered for use with that vessel. During the primary season, each vessel authorized to fish in that season under paragraph (a) of this section may take, retain, possess, and land sablefish, up to the cumulative limits for each of the permits registered for use with that vessel (
                            <E T="03">i.e.,</E>
                             stacked permits). If multiple limited entry permits with sablefish endorsements are registered for use with a single vessel, that vessel may land up to the total of all cumulative limits announced in this paragraph for the tiers for those permits, except as limited by paragraph (b)(3)(ii) of this section. Up to 3 permits may be registered for use with a single vessel during the primary season; thus, a single vessel may not take and retain, possess or land more than 3 primary season sablefish cumulative limits in any one year. A vessel registered for use with multiple limited entry permits is subject to per vessel limits for species other than sablefish, and to per vessel limits when participating in the daily trip limit fishery for sablefish under § 660.232. In 2023, the following annual limits are in effect: Tier 1 at 72,904 lb (33,069 kg), Tier 2 at 33,138 lb (15,031 kg), and Tier 3 at 18,936 lb (8,589 kg). In 2024 and beyond, the following annual limits are in effect: Tier 1 at 66,805 lb (30,302 kg), Tier 2 at 30,366 lb (13,774 kg), and Tier 3 at 17,352 lb (7,871 kg).
                        </P>
                        <STARS/>
                        <P>
                            (iv) 
                            <E T="03">Incidental Pacific halibut retention north of Pt. Chehalis, WA (46°53.30′ N lat.).</E>
                             From April 1 through the closure date set by the International Pacific Halibut Commission for Pacific halibut in all commercial fisheries, vessels authorized to participate in the sablefish primary fishery, licensed by the International Pacific Halibut Commission for commercial fishing in Area 2A (waters off Washington, Oregon, California), and fishing with longline gear north of Pt. Chehalis, WA (46°53.30′ N lat.) may possess and land up to 150 lb (68 kg) dressed weight of Pacific halibut for every 1,000 lb (454 kg) dressed weight of sablefish landed, and up to two additional Pacific halibut in excess of the 150-lbs-per-1,000-pound limit per landing. NMFS publishes the International Pacific Halibut Commission's regulations setting forth annual management measures, including the closure date for Pacific halibut in all commercial fisheries, in the 
                            <E T="04">Federal Register</E>
                             by March 15 each year, 50 CFR 300.62. “Dressed” Pacific halibut in this area means halibut landed eviscerated with their heads on. Pacific halibut taken and retained in the sablefish primary fishery north of Pt. Chehalis may only be landed north of Pt. Chehalis and may not be possessed or landed south of Pt. Chehalis.
                        </P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>19. Revise Table 2 (North) to part 660, subpart E, to read as follows:</AMDPAR>
                    <HD SOURCE="HD1">Non-Trawl Rockfish Conservation Areas and Trip Limits for Limited Entry Fixed Gear North of 40°10′ N Lat.</HD>
                    <BILCOD>BILLING CODE 3510-22-P</BILCOD>
                    <GPH SPAN="3" DEEP="395">
                        <PRTPAGE P="62712"/>
                        <GID>EP14OC22.000</GID>
                    </GPH>
                    <STARS/>
                    <PRTPAGE P="62713"/>
                    <AMDPAR>20. Review Table 2 (South) to part 660, subpart E, to read as follows:</AMDPAR>
                    <GPH SPAN="3" DEEP="477">
                        <GID>EP14OC22.001</GID>
                    </GPH>
                    <STARS/>
                    <AMDPAR>22. In § 660.330, add paragraphs (b)(3) and (d)(12)(v), and revise paragraphs (c)(2)(i) through (iii) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 660.330 </SECTNO>
                        <SUBJECT>Open access fishery—management measures.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>
                            (3) 
                            <E T="03">Non-trawl RCA gear.</E>
                             Inside the non-trawl RCA, only legal non-bottom contact hook-and-line gear configurations may be used for target fishing for groundfish by vessels that participate in the directed open access sector as defined at § 660.11. Legal non-bottom contact hook-and-line gear means stationary vertical jig gear attached to the vessel and not anchored to the bottom, and groundfish troll gear, subject to the specifications below.
                        </P>
                        <P>
                            (i) 
                            <E T="03">Stationary vertical jig gear.</E>
                             The following requirements apply to stationary vertical jig gear:
                        </P>
                        <P>(A) Must be a minimum of 50 feet between the bottom weight and the lowest fishing hook;</P>
                        <P>(B) No more than 4 vertical mainlines may be used in the water at one time with no more than 25 hooks on each mainline;</P>
                        <P>(C) No more than 100 hooks may be in the water at one time, with no more than 25 extra hooks on board the vessel; and</P>
                        <P>(D) Natural bait or weighted hooks may not be used nor be on board the vessel. Artificial lures and flies are permitted.</P>
                        <P>
                            (ii) 
                            <E T="03">Groundfish troll gear.</E>
                             The following requirements apply to groundfish troll gear:
                        </P>
                        <P>
                            (A) Must be a minimum of 50 feet between the bottom weight and the troll 
                            <PRTPAGE P="62714"/>
                            wire's connection to the horizontal mainline;
                        </P>
                        <P>(B) No more than 1 mainline may be used in the water at one time;</P>
                        <P>(C) No more than 500 hooks may be in the water at one time, with no more than 25 extra hooks on board the vessel;</P>
                        <P>
                            (D) Hooks must be spaced apart by a visible maker (
                            <E T="03">e.g.,</E>
                             floats, line wraps, colored line splices), with no more than 25 hooks between each marker and no more than 20 markers on the mainline; and
                        </P>
                        <P>(E) Natural bait or weighted hooks may not be used nor be on board the vessel. Artificial lures and flies are permitted.</P>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(2) * * *</P>
                        <P>
                            (i) 
                            <E T="03">Coastwide</E>
                            —arrowtooth flounder, big skate, black rockfish, blue/deacon rockfish, canary rockfish, darkblotched rockfish, Dover sole, English sole, lingcod, longnose skate, longspine thornyhead, minor nearshore rockfish, minor shelf rockfish, minor slope rockfish, other fish, other flatfish, Pacific cod, Pacific sanddabs, Pacific whiting, petrale sole, shortbelly rockfish, shortraker rockfish, rougheye/blackspotted rockfish, sablefish, shortspine thornyhead, spiny dogfish, starry flounder, widow rockfish, and yelloweye rockfish;
                        </P>
                        <P>
                            (ii) 
                            <E T="03">North of 40°10′ N lat.</E>
                            —cabezon (California), copper rockfish (California), Oregon cabezon/kelp greenling complex, POP, quillback rockfish (California), Washington cabezon/kelp greenling complex, yellowtail rockfish; and
                        </P>
                        <P>
                            (iii) 
                            <E T="03">South of 40°10′ N lat.</E>
                            —blackgill rockfish, bocaccio, bronzespotted rockfish, cabezon, chilipepper rockfish, copper rockfish, cowcod, minor shallow nearshore rockfish, minor deeper nearshore rockfish, quillback rockfish, splitnose rockfish, and vermilion rockfish.
                        </P>
                        <P>(d) * * *</P>
                        <P>(12) * * *</P>
                        <P>(v) Target fishing for groundfish off Oregon and California (between 46°16′ N. lat. and the U.S./Mexico border) is allowed within the non-trawl RCA for vessels participating in the directed open access sector as defined at § 660.11, subject to the gear restrictions at § 660.330(b)(3)(i-ii), and provided a valid declaration report as required at § 660.13(d) has been filed with NMFS OLE.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>23. Revise Table 3 (North) to part 660, subpart F, to read as follows:</AMDPAR>
                    <HD SOURCE="HD1">Table 3 (North) to Part 660, Subpart F—Non-Trawl Rockfish Conservation Areas and Trip Limits for Open Access Gears North of 40°10′ N Lat.</HD>
                    <GPH SPAN="3" DEEP="463">
                        <PRTPAGE P="62715"/>
                        <GID>EP14OC22.002</GID>
                    </GPH>
                    <STARS/>
                    <PRTPAGE P="62716"/>
                    <AMDPAR>24. Revise Table 3 (South) to part 660, subpart F, to read as follows:</AMDPAR>
                    <HD SOURCE="HD1">Table 3 (South) to Part 660, Subpart F—Non-Trawl Rockfish Conservation Areas and Trip Limits for Open Access Gears South of 40°10′ N Lat.</HD>
                    <GPH SPAN="3" DEEP="385">
                        <GID>EP14OC22.003</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="388">
                        <PRTPAGE P="62717"/>
                        <GID>EP14OC22.004</GID>
                    </GPH>
                    <STARS/>
                    <AMDPAR>25. Amend § 660.360 by:</AMDPAR>
                    <AMDPAR>a. Adding paragraph (c)(3)(iv)(A) through (D);</AMDPAR>
                    <AMDPAR>
                        b. Revising Table 1 to paragraph (c)(1)(i)(D), paragraphs (c)(1)(ii), (c)(2)(i)(B), (c)(2)(iii)(D), (c)(3) introductory text, (c)(3)(i)(A), (c)(3)(i)(B), (c)(3)(ii), (c)(3)(ii)(A)(
                        <E T="03">1</E>
                        ) through (
                        <E T="03">5</E>
                        ), (c)(3)(iii)(A)(
                        <E T="03">1</E>
                        ) through (
                        <E T="03">5</E>
                        ), (c)(3)(iv), and (c)(3)(v)(A).
                    </AMDPAR>
                    <P>The additions and revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 660.360 </SECTNO>
                        <SUBJECT>Recreational fishery—management measures.</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(1) * * *</P>
                        <P>(i) * * *</P>
                        <P>(D) * * *</P>
                        <GPH SPAN="3" DEEP="347">
                            <PRTPAGE P="62718"/>
                            <GID>EP14OC22.072</GID>
                        </GPH>
                        <P>
                            (ii) 
                            <E T="03">Rockfish.</E>
                             In areas of the EEZ seaward of Washington (Washington Marine Areas 1-4) that are open to recreational groundfish fishing, there is a 7 rockfish per day bag limit. Taking and retaining yelloweye rockfish is prohibited in all Marine Areas. Taking and retaining copper rockfish, quillback rockfish, and vermilion rockfish is prohibited in all Marine Areas during May, June and July.
                        </P>
                        <STARS/>
                        <P>(2) * * *</P>
                        <P>(i) * * *</P>
                        <P>
                            (B) 
                            <E T="03">Recreational rockfish conservation area (RCA).</E>
                             Fishing for groundfish with recreational gear is prohibited within the recreational RCA, a type of closed area or groundfish conservation area, except with long-leader gear (as defined at § 660.351). It is unlawful to take and retain, possess, or land groundfish taken with recreational gear within the recreational RCA, except with long-leader gear (as defined at § 660.351). A vessel fishing in the recreational RCA may not be in possession of any groundfish unless otherwise stated. [For example, if a vessel fishes in the recreational salmon fishery within the recreational RCA, the vessel cannot be in possession of groundfish while within the recreational RCA. The vessel may, however, on the same trip fish for and retain groundfish shoreward of the recreational RCA on the return trip to port.] Off Oregon, from January 1 through December 31, recreational fishing for groundfish is allowed in all depths. Coordinates approximating boundary lines at the 10-fm (18-m) through 100-fm (183-m) depth contours can be found at § 660.71 through § 660.73.
                        </P>
                        <STARS/>
                        <P>(iii) * * *</P>
                        <P>
                            (D) 
                            <E T="03">In the Pacific halibut fisheries.</E>
                             Retention of groundfish is governed in part by annual management measures for Pacific halibut fisheries, which are published in the 
                            <E T="04">Federal Register</E>
                            . Between the Columbia River and Humbug Mountain, during days open to the “all-depth” sport halibut fisheries, when Pacific halibut are onboard the vessel, no groundfish, except sablefish, Pacific cod, and other species of flatfish (sole, flounder, sanddab), may be taken and retained, possessed or landed, except with long-leader gear (as defined at § 660.351). “All-depth” season days are established in the annual management measures for Pacific halibut fisheries, which are published in the 
                            <E T="04">Federal Register</E>
                             and are announced on the NMFS Pacific halibut hotline, 1-800-662-9825.
                        </P>
                        <BILCOD>BILLING CODE 3510-22-C</BILCOD>
                        <STARS/>
                        <P>
                            (3) 
                            <E T="03">California.</E>
                             Seaward of California, for groundfish species not specifically mentioned in this paragraph, fishers are subject to the overall 20-fish bag limit for all species of finfish, of which no more than 10 fish of any one species may be taken or possessed by any one person. Petrale sole, Pacific sanddab, and starry flounder are not subject to a bag limit. Recreational spearfishing for all federally-managed groundfish, is exempt from closed areas and seasons, consistent with Title 14 of the California Code of Regulations. This exemption applies only to recreational vessels and divers provided no other fishing gear, except spearfishing gear, is on board the vessel. California state law may provide regulations similar to Federal regulations for kelp greenlings. Retention of cowcod, yelloweye rockfish, and bronzespotted rockfish, is prohibited in the recreational fishery seaward of California all year in all 
                            <PRTPAGE P="62719"/>
                            areas. Retention of species or species groups for which the season is closed is prohibited in the recreational fishery seaward of California all year in all areas, unless otherwise authorized in this section. For each person engaged in recreational fishing in the EEZ seaward of California, the following closed areas, seasons, bag limits, and size limits apply:
                        </P>
                        <P>(i) * * *</P>
                        <P>
                            (A) 
                            <E T="03">Recreational rockfish conservation areas.</E>
                             The recreational RCAs are areas that are closed to recreational fishing for certain groundfish. Fishing for the California rockfish, cabezon, greenling complex (RCG Complex), as defined in § 660.360(c)(3)(ii), and lingcod with recreational gear is prohibited within the recreational RCA. It is unlawful to take and retain, possess, or land the RCG Complex and lingcod taken with recreational gear within the recreational RCA, unless otherwise authorized in this section. A vessel fishing in the recreational RCA may not be in possession of any species prohibited by the restrictions that apply within the recreational RCA. For example, if a vessel fishes in the recreational salmon fishery within the recreational RCA, the vessel cannot be in possession of the RCG Complex and lingcod while in the recreational RCA. The vessel may, however, on the same trip fish for and retain rockfish shoreward of the recreational RCA on the return trip to port. If the season is closed for a species or species group, fishing for that species or species group is prohibited both within the recreational RCA and outside of the recreational RCA, unless otherwise authorized in this section. In times and areas where a recreational RCA is closed shoreward of a recreational RCA line (
                            <E T="03">i.e.,</E>
                             when an “off-shore only” fishery is active in that management area) possession or retention of nearshore rockfish (defined as black rockfish, blue rockfish, black and yellow rockfish, brown rockfish, China rockfish, copper rockfish, calico rockfish, gopher rockfish, kelp rockfish, grass rockfish, olive rockfish, quillback rockfish, and treefish), cabezon, and greenlings is prohibited in all depths throughout the area; and possession and retention of all rockfish, cabezon, greenlings, and lingcod is prohibited shoreward of the recreational RCA boundary line, except that vessels may transit through waters shoreward of the recreational RCA line with no fishing gear in the water. Coordinates approximating boundary lines at the 30 fm (55 m) through 100 fm (183 m) depth contours can be found at § 660.71 through § 660.73. The recreational fishing season structure and RCA depth boundaries seaward of California by management area and month are as follows:
                        </P>
                        <P>
                            (
                            <E T="03">1</E>
                            ) Between 42° N lat. (California/Oregon border) and 40°10′ N lat. (Northern Management Area), recreational fishing for the RCG Complex and lingcod is closed from January 1 through May 14, is open at all depths from May 15 through October 15, and is closed October 16 through December 31.
                        </P>
                        <P>
                            (
                            <E T="03">2</E>
                            ) Between 40°10′ N lat. and 38°57.50′ N lat. (Mendocino Management Area), recreational fishing for the RCG Complex and lingcod is closed from January 1 through May 14; prohibited in the EEZ shoreward of the boundary line approximating the 50 fm (91 m) depth contour along the mainland coast and along islands and offshore seamounts from May 15 through July 15 (seaward of 50 fm is open), and is open at all depths from July 16 through December 31.
                        </P>
                        <P>
                            (
                            <E T="03">3</E>
                            ) Between 38°57.50′ N lat. and 37°11′ N lat. (San Francisco Management Area), recreational fishing for the RCG Complex and lingcod s closed from January 1 through May 14; is prohibited in the EEZ shoreward of the boundary line approximating the 50 fm (91 m) depth contour along the mainland coast and along islands and offshore seamounts from May 15 through July 15 (seaward of 50 fm is open), and is open at all depths from July 16 through December 31. Closures around Cordell Bank (see paragraph (c)(3)(i)(C) of this section) also apply in this area.
                        </P>
                        <P>
                            (
                            <E T="03">4</E>
                            ) Between 37°11′ N lat. and 34°27′ N lat. (Central Management Area), recreational fishing for the RCG Complex and lingcod is closed from January 1 through April 30, is open at all depths from May 1 through September 30; and is prohibited in the EEZ shoreward of a boundary line approximating the 50 fm (91 m) depth contour along the mainland coast and along islands and offshore seamounts from October 1 through December 31 (seaward of 50 fm is open).
                        </P>
                        <P>
                            (
                            <E T="03">5</E>
                            ) South of 34°27′ N lat. (Southern Management Area), recreational fishing for the RCG Complex and lingcod is closed from January 1 through March 31, open at all depths from April 1 through September 15; and is prohibited in the EEZ shoreward of a boundary line approximating the 50 fm (91 m) depth contour from September 16 through December 31 along the mainland coast and along islands and offshore seamounts (seaward of 50 fm is open), except in the CCAs where fishing is prohibited seaward of the 40 fm (73 m) depth contour when the fishing season is open (see paragraph (c)(3)(i)(B) of this section).
                        </P>
                        <P>
                            (B) 
                            <E T="03">Cowcod conservation areas.</E>
                             The latitude and longitude coordinates of the Cowcod Conservation Areas (CCAs) boundaries are specified at § 660.70. Recreational fishing for all groundfish is prohibited within the CCAs, except as specified in this paragraph. Fishing for California scorpionfish, petrale sole, starry flounder, and “Other Flatfish” is permitted within the CCAs as specified in paragraphs (c)(3)(iv) and (c)(3)(v) of this section. Recreational fishing for the following species is permitted shoreward of the boundary line approximating the 40 fm (37 m) depth contour when the season, as specified in paragraphs (c)(3)(ii)(A)(5) and (c)(3)(iii)(A)(5) of this section, for those species is open south of 34°27′ N lat.: Minor nearshore rockfish, cabezon, kelp greenling, lingcod, and shelf rockfish. Retention of all groundfish except California scorpionfish, petrale sole, starry flounder, and “Other Flatfish”, is prohibited within the CCA. Coordinates for the boundary line approximating the 40 fm (73 m) depth contour are listed in §  660.71. It is unlawful to take and retain, possess, or land groundfish taken within the CCAs, except for species authorized in this section.
                        </P>
                        <STARS/>
                        <P>
                            (ii) 
                            <E T="03">RCG complex.</E>
                             The California rockfish, cabezon, greenling complex (RCG Complex) includes all rockfish, kelp greenling, rock greenling, and cabezon. This category does not include California scorpionfish, also known as “sculpin”.
                        </P>
                        <P>(A) * * *</P>
                        <P>
                            (
                            <E T="03">1</E>
                            ) Between 42° N lat. (California/Oregon border) and 40°10′ N lat. (North Management Area), recreational fishing for the RCG complex is open from May 15 through October 15 (
                            <E T="03">i.e.,</E>
                             recreational fishing for the RCG complex is closed from January 1 through May 14, and October 16 through December 31).
                        </P>
                        <P>
                            (
                            <E T="03">2</E>
                            ) Between 40°10′ N lat. and 38°57.50′ N lat. (Mendocino Management Area), recreational fishing for the RCG Complex is open from May 15 through December 31 (
                            <E T="03">i.e.,</E>
                             recreational fishing for the RCG complex is closed from January 1 through May 14).
                        </P>
                        <P>
                            (
                            <E T="03">3</E>
                            ) Between 38°57.50′ N lat. and 37°11′ N lat. (San Francisco Management Area), recreational fishing for the RCG complex is open from May 15 through December 31 (
                            <E T="03">i.e.,</E>
                             recreational fishing for the RCG complex is closed from January 1 through May 14).
                        </P>
                        <P>
                            (
                            <E T="03">4</E>
                            ) Between 37°11′ N lat. and 34°27′ N lat. (Central Management Area), 
                            <PRTPAGE P="62720"/>
                            recreational fishing for the RCG complex is open from May 1 through December 31 (
                            <E T="03">i.e.,</E>
                             recreational fishing for the RCG complex is closed from January 1 through April 30).
                        </P>
                        <P>
                            (
                            <E T="03">5</E>
                            ) South of 34°27′ N lat. (Southern Management Area), recreational fishing for the RCG Complex is open from April 1 through December 31 (
                            <E T="03">i.e.,</E>
                             recreational fishing for the RCG complex is closed from January 1 through the March 31).
                        </P>
                        <STARS/>
                        <P>(iii) * * *</P>
                        <P>(A) * * *</P>
                        <P>
                            (
                            <E T="03">1</E>
                            ) Between 42° N lat. (California/Oregon border) and 40°10′ N lat. (Northern Management Area), recreational fishing for lingcod is open from May 15 through October 15 (
                            <E T="03">i.e.,</E>
                             recreational fishing for lingcod is closed from January 1 through May 14, and October 16 through December 31).
                        </P>
                        <P>
                            (
                            <E T="03">2</E>
                            ) Between 40°10′ N lat. and 38°57.50′ N lat. (Mendocino Management Area), recreational fishing for lingcod is open from May 15 through December 31 (
                            <E T="03">i.e.,</E>
                             recreational fishing for lingcod is closed from January 1 through May 14).
                        </P>
                        <P>
                            (
                            <E T="03">3</E>
                            ) Between 38°57.50′ N lat. and 37°11′ N lat. (San Francisco Management Area), recreational fishing for lingcod is open from May 15 through December 31 (
                            <E T="03">i.e.,</E>
                             recreational fishing for lingcod is closed from January 1 through May 14).
                        </P>
                        <P>
                            (
                            <E T="03">4</E>
                            ) Between 37°11′ N lat. and 34°27′ N lat. (Central Management Area), recreational fishing for lingcod is open from May 1 through December 31 (
                            <E T="03">i.e.,</E>
                             recreational fishing for lingcod is closed from January 1 through April 30).
                        </P>
                        <P>
                            (
                            <E T="03">5</E>
                            ) South of 34°27′ N lat. (Southern Management Area), recreational fishing for lingcod is open from April 1 through December 31 (
                            <E T="03">i.e.,</E>
                             recreational fishing for lingcod is closed from January 1 through March 31)
                        </P>
                        <STARS/>
                        <P>
                            (iv) 
                            <E T="03">“Other Flatfish,” petrale sole, and starry flounder.</E>
                             “Other Flatfish” are defined at § 660.11, and include butter sole, curlfin sole, flathead sole, Pacific sanddab, rex sole, rock sole, and sand sole.
                        </P>
                        <P>
                            (A) 
                            <E T="03">Seasons.</E>
                             Recreational fishing for “Other Flatfish,” petrale sole, and starry flounder is open from January 1 through December 31. When recreational fishing for “Other Flatfish,” petrale sole, and starry flounder is open, it is permitted both outside and within the recreational RCAs described in paragraph (c)(3)(i) of this section and the CCAs described in paragraph (c)(3)(i)(B) of this section.
                        </P>
                        <P>
                            (B) 
                            <E T="03">Bag limits, hook limits.</E>
                             In times and areas where the recreational season for “Other Flatfish,” petrale sole, and starry flounder is open, “Other Flatfish” are subject to the overall 20-fish bag limit for all species of finfish, of which there may be no more than 10 fish of any one species; there is no daily bag limit for petrale sole, starry flounder and Pacific sanddab.
                        </P>
                        <P>
                            (C) 
                            <E T="03">Size limits.</E>
                             There are no size limits for “Other Flatfish,” petrale sole, and starry flounder.
                        </P>
                        <P>
                            (D) 
                            <E T="03">Dressing/Filleting.</E>
                             “Other Flatfish,” petrale sole, and starry flounder may be filleted at sea. Fillets may be of any size, but must bear intact a one-inch (2.6 cm) square patch of skin.
                        </P>
                        <P>(v) * * *</P>
                        <P>
                            (A) 
                            <E T="03">Seasons.</E>
                             When recreational fishing for California scorpionfish is open, it is permitted both outside of and within the recreational RCAs described in paragraph (c)(3)(i) of this section. Recreational fishing for California scorpionfish is open from January 1 through December 31.
                        </P>
                        <STARS/>
                    </SECTION>
                </SUPLINF>
                <FRDOC>[FR Doc. 2022-20430 Filed 10-13-22; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 3510-22-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
</FEDREG>
