<?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>89</VOL>
    <NO>50</NO>
    <DATE>Wednesday, March 13, 2024</DATE>
    <UNITNAME>Contents</UNITNAME>
    <CNTNTS>
        <AGCY>
            <EAR>
                Agriculture
                <PRTPAGE P="iii"/>
            </EAR>
            <HD>Agriculture Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Forest Service</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>18371</PGS>
                    <FRDOCBP>2024-05314</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Antitrust Division</EAR>
            <HD>Antitrust Division</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Changes under the National Cooperative Research and Production Act:</SJ>
                <SJDENT>
                    <SJDOC>ASTM International, </SJDOC>
                    <PGS>18437</PGS>
                    <FRDOCBP>2024-05304</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Cooperative Research Group on Numerical Propulsion System Simulation, </SJDOC>
                    <PGS>18439</PGS>
                    <FRDOCBP>2024-05312</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Cooperative Research Group on Separation Technology Research Program:  Phase 3, </SJDOC>
                    <PGS>18438</PGS>
                    <FRDOCBP>2024-05311</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Expeditionary Missions Consortium—Crane, </SJDOC>
                    <PGS>18439-18440</PGS>
                    <FRDOCBP>2024-05301</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Maritime Sustainment and Technology Innovation Consortium, </SJDOC>
                    <PGS>18440</PGS>
                    <FRDOCBP>2024-05315</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Armaments Consortium, </SJDOC>
                    <PGS>18441</PGS>
                    <FRDOCBP>2024-05318</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Naval Surface Technology and Innovation Consortium, </SJDOC>
                    <PGS>18440-18441</PGS>
                    <FRDOCBP>2024-05316</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Pistoia Alliance, Inc., </SJDOC>
                    <PGS>18437</PGS>
                    <FRDOCBP>2024-05303</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>R Consortium, Inc., </SJDOC>
                    <PGS>18438-18439</PGS>
                    <FRDOCBP>2024-05309</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Resilient Infrastructure and Secure Energy Consortium, </SJDOC>
                    <PGS>18438</PGS>
                    <FRDOCBP>2024-05319</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>The Institute of Electrical and Electronics Engineers, Inc., </SJDOC>
                    <PGS>18441</PGS>
                    <FRDOCBP>2024-05306</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Utility Broadband Alliance, </SJDOC>
                    <PGS>18437</PGS>
                    <FRDOCBP>2024-05317</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Z-Wave Alliance, Inc., </SJDOC>
                    <PGS>18438</PGS>
                    <FRDOCBP>2024-05308</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Centers Medicare</EAR>
            <HD>Centers for Medicare &amp; Medicaid Services</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>18411-18413</PGS>
                    <FRDOCBP>2024-05291</FRDOCBP>
                      
                    <FRDOCBP>2024-05332</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Civil Rights</EAR>
            <HD>Civil Rights Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Arizona Advisory Committee, </SJDOC>
                    <PGS>18371-18372</PGS>
                    <FRDOCBP>2024-05324</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Coast Guard</EAR>
            <HD>Coast Guard</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Safety Zone:</SJ>
                <SJDENT>
                    <SJDOC>Inner Harbor, Baltimore MD, </SJDOC>
                    <PGS>18366-18368</PGS>
                    <FRDOCBP>2024-05339</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>18425-18427</PGS>
                    <FRDOCBP>2024-05336</FRDOCBP>
                      
                    <FRDOCBP>2024-05337</FRDOCBP>
                      
                    <FRDOCBP>2024-05340</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Commerce</EAR>
            <HD>Commerce Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Foreign-Trade Zones Board</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Industry and Security Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>International Trade Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Institute of Standards and Technology</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Oceanic and Atmospheric Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Community Living Administration</EAR>
            <HD>Community Living Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>National Survey of Older Americans Act Participants, </SJDOC>
                    <PGS>18413-18415</PGS>
                    <FRDOCBP>2024-05310</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Defense Department</EAR>
            <HD>Defense Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Board of Visitors, National Defense University, </SJDOC>
                    <PGS>18397-18398</PGS>
                    <FRDOCBP>2024-05347</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>Braille Training Program, </SJDOC>
                    <PGS>18398-18403</PGS>
                    <FRDOCBP>2024-05290</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Election</EAR>
            <HD>Election Assistance Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Election Supporting Technology Evaluation Program Anomaly Reporting Forms, </SJDOC>
                    <PGS>18403-18404</PGS>
                    <FRDOCBP>2024-05302</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>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Annual Public Water Systems Compliance Report, </SJDOC>
                    <PGS>18407-18408</PGS>
                    <FRDOCBP>2024-05285</FRDOCBP>
                </SJDENT>
                <SJ>Proposed Settlement Agreement:</SJ>
                <SJDENT>
                    <SJDOC>Petition for Writ of Mandamus, </SJDOC>
                    <PGS>18408-18409</PGS>
                    <FRDOCBP>2024-05287</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Aviation</EAR>
            <HD>Federal Aviation Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Airworthiness Directives:</SJ>
                <SJDENT>
                    <SJDOC>GE Aviation Czech s.r.o. (Type Certificate Previously Held by WALTER Engines a.s., Walter a.s., and MOTORLET a.s.) Engines, </SJDOC>
                    <PGS>18348-18350</PGS>
                    <FRDOCBP>2024-05247</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Pratt and Whitney Canada Corp. Engines, </SJDOC>
                    <PGS>18350-18353</PGS>
                    <FRDOCBP>2024-05238</FRDOCBP>
                </SJDENT>
                <SJ>Special Conditions:</SJ>
                <SJDENT>
                    <SJDOC>Gulfstream Aerospace Corporation Model GVIII-G700 and GVIII-G800 Series Airplanes; Dynamic Test Requirements for Single- and Multiple-Occupant Side-Facing Seats With or Without Airbag Systems, </SJDOC>
                    <PGS>18341-18348</PGS>
                    <FRDOCBP>2024-05226</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Waiver with Respect to Land:</SJ>
                <SJDENT>
                    <SJDOC>Grand Rapids/Itasca County Airport, Grand Rapids, MN, </SJDOC>
                    <PGS>18476</PGS>
                    <FRDOCBP>2024-05248</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Communications</EAR>
            <HD>Federal Communications Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Location-Based Routing for Wireless 911 Calls, </DOC>
                    <PGS>18488-18524</PGS>
                    <FRDOCBP>2024-03157</FRDOCBP>
                </DOCENT>
                <SJ>Television Broadcasting Services:</SJ>
                <SJDENT>
                    <SJDOC>Greenville, SC, </SJDOC>
                    <PGS>18364-18365</PGS>
                    <FRDOCBP>2024-05307</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Hearings, Meetings, Proceedings, etc., </DOC>
                    <PGS>18409-18410</PGS>
                    <FRDOCBP>2024-05313</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Energy</EAR>
            <HD>Federal Energy Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Combined Filings, </DOC>
                    <PGS>18404-18407</PGS>
                    <FRDOCBP>2024-05230</FRDOCBP>
                      
                    <FRDOCBP>2024-05329</FRDOCBP>
                      
                    <FRDOCBP>2024-05330</FRDOCBP>
                </DOCENT>
                <SJ>Initial Market-Based Rate Filings Including Requests for Blanket Section 204 Authorizations:</SJ>
                <SJDENT>
                    <SJDOC>Sierra Estrella Energy Storage LLC, </SJDOC>
                    <PGS>18404-18405</PGS>
                    <FRDOCBP>2024-05327</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <PRTPAGE P="iv"/>
                    <SJDOC>Superstition Energy Storage LLC, </SJDOC>
                    <PGS>18405-18406</PGS>
                    <FRDOCBP>2024-05326</FRDOCBP>
                </SJDENT>
                <SJ>Withdrawal of Staff Protest:</SJ>
                <SJDENT>
                    <SJDOC>Kern River Gas Transmission Company, </SJDOC>
                    <PGS>18406</PGS>
                    <FRDOCBP>2024-05328</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Maritime</EAR>
            <HD>Federal Maritime Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agreements Filed, </DOC>
                    <PGS>18410</PGS>
                    <FRDOCBP>2024-05344</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Motor</EAR>
            <HD>Federal Motor Carrier Safety Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Request for Information:</SJ>
                <SJDENT>
                    <SJDOC>Drivers' Leasing Agreements for Commercial Motor Vehicles, </SJDOC>
                    <PGS>18476-18477</PGS>
                    <FRDOCBP>2024-05342</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Railroad</EAR>
            <HD>Federal Railroad Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Petition for Extension of Waiver of Compliance, </DOC>
                    <PGS>18477-18479</PGS>
                    <FRDOCBP>2024-05282</FRDOCBP>
                      
                    <FRDOCBP>2024-05283</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Petition for Waiver of Compliance, </DOC>
                    <PGS>18479</PGS>
                    <FRDOCBP>2024-05280</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Reserve</EAR>
            <HD>Federal Reserve System</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Change in Bank Control:</SJ>
                <SJDENT>
                    <SJDOC>Acquisitions of Shares of a Bank or Bank Holding Company, </SJDOC>
                    <PGS>18410</PGS>
                    <FRDOCBP>2024-05235</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Formations of, Acquisitions by, and Mergers of Bank Holding Companies, </DOC>
                    <PGS>18411</PGS>
                    <FRDOCBP>2024-05323</FRDOCBP>
                </DOCENT>
            </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>Proposed Small Dispensers Assessment Under the Drug Supply Chain Security Act, </SJDOC>
                    <PGS>18415-18418</PGS>
                    <FRDOCBP>2024-05294</FRDOCBP>
                </SJDENT>
                <SJ>Determination of Regulatory Review Period for Purposes of Patent Extension:</SJ>
                <SJDENT>
                    <SJDOC>DAURISMO, </SJDOC>
                    <PGS>18423-18424</PGS>
                    <FRDOCBP>2024-05305</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Determination That Romidepsin Injection, 10 Milligrams/2 Milliliters (5 Milligrams/Milliliter) and 27.5 Milligrams/5.5 Milliliters (5 Milligrams/Milliliter), Were Not Withdrawn From Sale for Reasons of Safety or Effectiveness, </DOC>
                    <PGS>18420-18421</PGS>
                    <FRDOCBP>2024-05298</FRDOCBP>
                </DOCENT>
                <SJ>Guidance:</SJ>
                <SJDENT>
                    <SJDOC>Annual Reportable Labeling Changes for New Drug Applications and Abbreviated New Drug Applications for Nonprescription Drug Products, </SJDOC>
                    <PGS>18418-18420</PGS>
                    <FRDOCBP>2024-05293</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Select Updates for the Premarket Cybersecurity; Federal Food, Drug, and Cosmetic Act, </SJDOC>
                    <PGS>18421-18423</PGS>
                    <FRDOCBP>2024-05295</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Foreign Trade</EAR>
            <HD>Foreign-Trade Zones Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Proposed Production Activity:</SJ>
                <SJDENT>
                    <SJDOC>Flextronics America, LLC, Foreign-Trade Zone 183, Austin, TX, </SJDOC>
                    <PGS>18372</PGS>
                    <FRDOCBP>2024-05264</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Forest</EAR>
            <HD>Forest Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Bears Ears National Monument in Utah, Draft Resource Management Plan, </SJDOC>
                    <PGS>18428-18430</PGS>
                    <FRDOCBP>2024-05203</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 Medicare &amp; Medicaid Services</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Community Living Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Food and Drug Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Health Resources and Services Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Health Resources</EAR>
            <HD>Health Resources and Services Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Advisory Committee on Infant and Maternal Mortality, </SJDOC>
                    <PGS>18424-18425</PGS>
                    <FRDOCBP>2024-05300</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Homeland</EAR>
            <HD>Homeland Security Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Coast Guard</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Indian Affairs</EAR>
            <HD>Indian Affairs Bureau</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Civil Monetary Penalty Inflation Adjustment, </DOC>
                    <PGS>18359-18363</PGS>
                    <FRDOCBP>2024-05275</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Indian Gaming;</SJ>
                <SJDENT>
                    <SJDOC>Approval of Tribal-State Class III Gaming Compact between the Shakopee Mdewakanton Sioux Community of Minnesota and the State of Minnesota for Blackjack, </SJDOC>
                    <PGS>18427-18428</PGS>
                    <FRDOCBP>2024-05276</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Industry</EAR>
            <HD>Industry and Security Bureau</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Clarification of Controls:</SJ>
                <SJDENT>
                    <SJDOC>Radiation Hardened Integrated Circuits and expansion of License Exception GOV, </SJDOC>
                    <PGS>18353-18359</PGS>
                    <FRDOCBP>2024-05267</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Interior</EAR>
            <HD>Interior Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Indian Affairs Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Land Management Bureau</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Internal Revenue</EAR>
            <HD>Internal Revenue Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>18484-18486</PGS>
                    <FRDOCBP>2024-05333</FRDOCBP>
                      
                    <FRDOCBP>2024-05334</FRDOCBP>
                      
                    <FRDOCBP>2024-05335</FRDOCBP>
                </DOCENT>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Carryover of Passive Activity losses and Credits and At-Risk Losses to Bankruptcy Estates of Individuals, </SJDOC>
                    <PGS>18484</PGS>
                    <FRDOCBP>2024-05257</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International Trade Adm</EAR>
            <HD>International Trade Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Antidumping or Countervailing Duty Investigations, Orders, or Reviews:</SJ>
                <SJDENT>
                    <SJDOC>Lightweight Thermal Paper from Japan, </SJDOC>
                    <PGS>18372-18373</PGS>
                    <FRDOCBP>2024-05265</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International Trade Com</EAR>
            <HD>International Trade Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Antidumping or Countervailing Duty Investigations Orders or Reviews:</SJ>
                <SJDENT>
                    <SJDOC>Fine Denier Polyester Staple Fiber, </SJDOC>
                    <PGS>18435-18437</PGS>
                    <FRDOCBP>2024-05338</FRDOCBP>
                </SJDENT>
                <SJ>Investigations; Determinations, Modifications, and Rulings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Certain Marine Air Conditioning Systems, Components Thereof, and Products Containing the Same, </SJDOC>
                    <PGS>18433-18434</PGS>
                    <FRDOCBP>2024-05274</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Certain Replacement Automotive Lamps, </SJDOC>
                    <PGS>18434-18435</PGS>
                    <FRDOCBP>2024-05272</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Certain Replacement Automotive Lamps II, </SJDOC>
                    <PGS>18431-18432</PGS>
                    <FRDOCBP>2024-05273</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>18431</PGS>
                    <FRDOCBP>2024-05484</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Justice Department</EAR>
            <HD>Justice Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Antitrust Division</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Land</EAR>
            <HD>Land Management Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Application:</SJ>
                <SJDENT>
                    <SJDOC>Permanent Withdrawal and Transfer of Jurisdiction, CO, </SJDOC>
                    <PGS>18430-18431</PGS>
                    <FRDOCBP>2024-05341</FRDOCBP>
                    <PRTPAGE P="v"/>
                </SJDENT>
                <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Bears Ears National Monument in Utah, Draft Resource Management Plan, </SJDOC>
                    <PGS>18428-18430</PGS>
                    <FRDOCBP>2024-05203</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>NASA</EAR>
            <HD>National Aeronautics and Space Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Advisory Council, Science Committee, </SJDOC>
                    <PGS>18441-18442</PGS>
                    <FRDOCBP>2024-05129</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Institute</EAR>
            <HD>National Institute of Standards and Technology</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Manufacturing USA Institute Competition:</SJ>
                <SJDENT>
                    <SJDOC>AI for Resilient Manufacturing, </SJDOC>
                    <PGS>18373-18375</PGS>
                    <FRDOCBP>2024-05228</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Oceanic</EAR>
            <HD>National Oceanic and Atmospheric Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Pacific Halibut Fisheries of the West Coast:</SJ>
                <SJDENT>
                    <SJDOC>Management Measures for the 2024 Area 2A Pacific Halibut Directed Commercial Fishery, </SJDOC>
                    <PGS>18368-18370</PGS>
                    <FRDOCBP>2024-05289</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Charter Amendments, Establishments, Renewals and Terminations:</SJ>
                <SJDENT>
                    <SJDOC>Advisory Committee on Excellence in Space, Formerly the Advisory Committee on Commercial Remote Sensing, </SJDOC>
                    <PGS>18394-18395</PGS>
                    <FRDOCBP>2024-05284</FRDOCBP>
                </SJDENT>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Atlantic Highly Migratory Species; Atlantic Bluefin Tuna Fishery regarding the Harpoon Category, </SJDOC>
                    <PGS>18375-18376</PGS>
                    <FRDOCBP>2024-05299</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>New England Fishery Management Council, </SJDOC>
                    <PGS>18377-18378</PGS>
                    <FRDOCBP>2024-05460</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>North Pacific Fishery Management Council, </SJDOC>
                    <PGS>18393-18394</PGS>
                    <FRDOCBP>2024-05325</FRDOCBP>
                </SJDENT>
                <SJ>Permits; Applications, Issuances, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Atlantic Coastal Fisheries Cooperative Management Act Provisions; General Provisions for Domestic Fisheries, </SJDOC>
                    <PGS>18395-18397</PGS>
                    <FRDOCBP>2024-05262</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>General Provisions for Domestic Fisheries, </SJDOC>
                    <PGS>18376-18377</PGS>
                    <FRDOCBP>2024-05271</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Marine Mammals and Endangered Species; File No. 27671, </SJDOC>
                    <PGS>18397</PGS>
                    <FRDOCBP>2024-05261</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Marine Mammals; File No. 27938, </SJDOC>
                    <PGS>18378</PGS>
                    <FRDOCBP>2024-05263</FRDOCBP>
                </SJDENT>
                <SJ>Taking or Importing of Marine Mammals:</SJ>
                <SJDENT>
                    <SJDOC>Parallel Thimble Shoal Tunnel Project, Virginia Beach, VA, </SJDOC>
                    <PGS>18378-18393</PGS>
                    <FRDOCBP>2024-05321</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Science</EAR>
            <HD>National Science Foundation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Grantee Reporting Requirements for the Small Business Innovation Research and the Small Business Technology Transfer Programs, </SJDOC>
                    <PGS>18442-18443</PGS>
                    <FRDOCBP>2024-05270</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Nuclear Regulatory</EAR>
            <HD>Nuclear Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Notices, Instructions, and Reports to Workers: Inspection and Investigations, </SJDOC>
                    <PGS>18443-18444</PGS>
                    <FRDOCBP>2024-05320</FRDOCBP>
                </SJDENT>
                <SJ>Establishment of Atomic Safety and Licensing Board:</SJ>
                <SJDENT>
                    <SJDOC>Pacific Gas and Electric Co., </SJDOC>
                    <PGS>18443</PGS>
                    <FRDOCBP>2024-05277</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Pension Benefit</EAR>
            <HD>Pension Benefit Guaranty Corporation</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Allocation of Assets in Single-Employer Plans; Interest Assumptions for Valuing Benefits, </DOC>
                    <PGS>18363-18364</PGS>
                    <FRDOCBP>2024-05249</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Pipeline</EAR>
            <HD>Pipeline and Hazardous Materials Safety Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hazardous Materials:</SJ>
                <SJDENT>
                    <SJDOC>Clarification of Applications for Special Permits Submitted in the Public Interest, </SJDOC>
                    <PGS>18482-18484</PGS>
                    <FRDOCBP>2024-05250</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Frequently Asked Questions-Training Requirements, </SJDOC>
                    <PGS>18479-18482</PGS>
                    <FRDOCBP>2024-05268</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Postal Regulatory</EAR>
            <HD>Postal Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>New Postal Products, </DOC>
                    <PGS>18444-18445</PGS>
                    <FRDOCBP>2024-05288</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Presidential Documents</EAR>
            <HD>Presidential Documents</HD>
            <CAT>
                <HD>PROCLAMATIONS</HD>
                <SJ>Special Observances:</SJ>
                <SJDENT>
                    <SJDOC>U.S. Hostage and Wrongful Detainee Day (Proc. 10709), </SJDOC>
                    <PGS>18339-18340</PGS>
                    <FRDOCBP>2024-05441</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>ADMINISTRATIVE ORDERS</HD>
                <DOCENT>
                    <DOC>Iran; Continuation of National Emergency (Notice of March 12, 2024), </DOC>
                    <PGS>18525-18528</PGS>
                    <FRDOCBP>2024-05568</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>18447-18465</PGS>
                    <FRDOCBP>2024-05251</FRDOCBP>
                      
                    <FRDOCBP>2024-05256</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Nasdaq PHLX LLC, </SJDOC>
                    <PGS>18465-18466</PGS>
                    <FRDOCBP>2024-05252</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>New York Stock Exchange LLC, </SJDOC>
                    <PGS>18466-18468</PGS>
                    <FRDOCBP>2024-05253</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>NYSE American LLC, </SJDOC>
                    <PGS>18445-18447</PGS>
                    <FRDOCBP>2024-05254</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>NYSE Chicago, Inc., </SJDOC>
                    <PGS>18468-18470</PGS>
                    <FRDOCBP>2024-05255</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Small Business</EAR>
            <HD>Small Business Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Reinvestor Small Business Investment Company License Educational Public Webinar, </SJDOC>
                    <PGS>18341</PGS>
                    <FRDOCBP>2024-05266</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>18471-18475</PGS>
                    <FRDOCBP>2024-05296</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>State Department</EAR>
            <HD>State Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Reta Jo Lewis Local Diplomat Program—City Applications, </SJDOC>
                    <PGS>18475</PGS>
                    <FRDOCBP>2024-05278</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Determination under of the Department of State, Foreign Operations, and Related Programs Appropriations Act, 2022, </DOC>
                    <PGS>18476</PGS>
                    <FRDOCBP>2024-05343</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Transportation Department</EAR>
            <HD>Transportation Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Aviation Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Motor Carrier Safety Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Railroad Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Pipeline and Hazardous Materials Safety Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Treasury</EAR>
            <HD>Treasury Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Internal Revenue Service</P>
            </SEE>
        </AGCY>
        <PTS>
            <HD SOURCE="HED">Separate Parts In This Issue</HD>
            <HD>Part II</HD>
            <DOCENT>
                <DOC>Federal Communications Commission, </DOC>
                <PGS>18488-18524</PGS>
                <FRDOCBP>2024-03157</FRDOCBP>
            </DOCENT>
            <HD>Part III</HD>
            <DOCENT>
                <DOC>Presidential Documents, </DOC>
                <PGS>18525-18528</PGS>
                <FRDOCBP>2024-05568</FRDOCBP>
            </DOCENT>
        </PTS>
        <AIDS>
            <PRTPAGE P="vi"/>
            <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>89</VOL>
    <NO>50</NO>
    <DATE>Wednesday, March 13, 2024</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <RULES>
        <RULE>
            <PREAMB>
                <PRTPAGE P="18341"/>
                <AGENCY TYPE="F">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <CFR>13 CFR Parts 107 and 121</CFR>
                <SUBJECT>SBA Reinvestor (“Fund-of-Funds”) Small Business Investment Company (SBIC) License Educational Public Webinar</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Small Business Administration (SBA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notification of public webinar.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The SBA is holding a webinar to educate the public on the new Reinvestor SBIC License introduced to the market as part of the 
                        <E T="03">SBIC Investment Diversification and Growth Final Rule</E>
                         that went into effect on August 17, 2023.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The public webinar will be held on Friday, March 22, 2024, from 1 p.m. to 2 p.m. Eastern Time.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Information about applying for and managing a Reinvestor (“fund-of-funds”) SBIC License. The Webinar will be live streamed on Microsoft Teams for the public.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        The meeting will be live streamed to the public, and anyone wishing to attend or needing accommodations because of a disability can contact Gretchen Kittel, SBA, Office of Investment &amp; Innovation (OII), (202) 578-5502, 
                        <E T="03">investinnovate@sba.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>On August 17, 2023, the U.S. Small Business Administration (“SBA”) implemented new regulations for the Small Business Investment Company (“SBIC”) program as part of the SBIC Investment Diversification and Growth rulemaking. The new regulations significantly reduce barriers to program participation for new SBIC fund managers and funds investing in underserved communities and geographies, capital intensive investments, and technologies critical to national security and economic development. The proposed rule introduced two additional types of SBIC Licensees, Reinvestor SBICs and Accrual SBICs, to increase program investment diversification and equity-oriented financing for American small businesses and innovative startups. Reinvestor SBICs expand SBA's network of emerging fund managers, micro-funds, and funds addressing underserved communities and geographies and undercapitalized industries.</P>
                <HD SOURCE="HD1">II. Questions</HD>
                <P>
                    For the public webinar, OII strongly encourages questions be submitted in advance by March 20, 2024. Individuals may email 
                    <E T="03">investinnovate@sba.gov</E>
                     with subject line—“[Name/Organization] Question for 03/22/24 Public Webinar.” During the live event, attendees will be in listen-only mode and may submit additional questions via the Q&amp;A Chat feature.
                </P>
                <HD SOURCE="HD1">III. Information on Service for Individuals With Disabilities</HD>
                <P>
                    For information on services for individuals with disabilities or to request special assistance, contact Gretchen Kittel at the telephone number or email address indicated under the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this notice.
                </P>
                <SIG>
                    <NAME>Bailey DeVries,</NAME>
                    <TITLE>Associate Administrator, Office of Investment &amp; Innovation, U.S. Small Business Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05266 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8026-09-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 25</CFR>
                <DEPDOC>[Docket No. FAA-2023-2435; Special Conditions No. 25-862-SC]</DEPDOC>
                <SUBJECT>Special Conditions: Gulfstream Aerospace Corporation Model GVIII-G700 and GVIII-G800 Series Airplanes; Dynamic Test Requirements for Single- and Multiple-Occupant Side-Facing Seats With or Without Airbag Systems</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final special conditions.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>These special conditions are issued for the Gulfstream Aerospace Corporation (Gulfstream) Model GVIII-G700 and GVIII-G800 series airplanes. These airplanes will have a novel or unusual design feature when compared to the state of technology envisioned in the airworthiness standards for transport category airplanes. This design feature is side-facing seats oriented in the aircraft with the occupant facing 90 degrees to the direction of aircraft travel. The applicable airworthiness regulations do not contain adequate or appropriate safety standards for this design feature. These special conditions contain the additional safety standards that the Administrator considers necessary to establish a level of safety equivalent to that established by the existing airworthiness standards.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective March 13, 2024.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Myra Kuck, Cabin Safety, AIR-624, Technical Policy Branch, Policy and Standards Division, Aircraft Certification Service, Federal Aviation Administration, Aircraft Certification Policy and Standards, 3960 Paramount Blvd., Suite 100, Lakewood, CA 90712; telephone and fax 405-666-1059; email 
                        <E T="03">Myra.J.Kuck@faa.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>On December 31, 2019, Gulfstream applied for an amendment to Type Certificate No. T00015AT to include the new Model GVIII-G700 and GVIII-G800 series airplanes. These airplanes, which will be derivatives of the Model GVI currently approved under Type Certificate No. T00015AT, are twin-engine, transport-category airplanes, with seating for 19 passengers, and a maximum take-off weight of 107,600 pounds (GVIII-G700) and 105,600 pounds (GVIII-G800).</P>
                <HD SOURCE="HD1">Type Certification Basis</HD>
                <P>
                    Under the provisions of title 14, Code of Federal Regulations (14 CFR) 21.101, Gulfstream must show that the Model GVIII-G700 and GVIII-G800 series airplanes meet the applicable provisions of the regulations listed in Type Certificate No. T00015AT, or the applicable regulations in effect on the date of application for the change, except for earlier amendments as agreed upon by the FAA.
                    <PRTPAGE P="18342"/>
                </P>
                <P>If the Administrator finds that the applicable airworthiness regulations do not contain adequate or appropriate safety standards for the Gulfstream Model GVIII-G700 and GVIII-G800 series airplanes because of a novel or unusual design feature, special conditions are prescribed under the provisions of §  21.16.</P>
                <P>Special conditions are initially applicable to the model for which they are issued. Should the type certificate for that model be amended later to include any other model that incorporates the same novel or unusual design feature, or should any other model already included on the same type certificate be modified to incorporate the same novel or unusual design feature, these special conditions would also apply to the other model under §  21.101.</P>
                <P>In addition to the applicable airworthiness regulations and special conditions, the Gulfstream Model GVIII-G700 and GVIII-G800 series airplanes must comply with the exhaust-emission requirements of 14 CFR part 34, and the noise-certification requirements of 14 CFR part 36.</P>
                <P>The FAA issues special conditions, as defined in 14 CFR 11.19, in accordance with 14 CFR 11.38, and they become part of the type certification basis under §  21.101.</P>
                <HD SOURCE="HD1">Novel or Unusual Design Feature</HD>
                <P>The Gulfstream Model GVIII-G700 and GVIII-G800 airplanes will incorporate the following novel or unusual design feature:</P>
                <P>Side-facing seats, oriented in the aircraft with the occupant facing 90 degrees to the direction of aircraft travel, with or without incorporation of an airbag systems or inflatables.</P>
                <HD SOURCE="HD1">Discussion</HD>
                <P>On June 16, 1988, 14 CFR part 25 was amended to revise the emergency landing conditions that must be considered in the design of transport category airplanes. This amendment (25-64) revised the static load conditions in §  25.561 and added a new §  25.562 that required dynamic testing for all seats approved for occupancy during takeoff and landing. The intent of Amendment 25-64 was to provide an improved level of safety for occupants on transport category airplanes; however, because most seating on transport category airplanes is forward-facing, the pass/fail criteria developed in Amendment 25-64 focused primarily on these seats.</P>
                <P>
                    Prior to 2012, the FAA granted exemptions 
                    <SU>1</SU>
                    <FTREF/>
                     for the multiple-place side-facing-seat installations because the existing test methods and acceptance criteria did not produce a level of safety equivalent to the level of safety provided for forward-and aft-facing seats. These exemptions were subject to many conditions that reflected the injury-evaluation criteria and mitigation strategies available at the time of the exemption issuance. The FAA also issued special conditions to address single-place side-facing seats because it determined, at the time, that those conditions provided the same level of safety as for forward- and aft-facing seats.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See, generally,</E>
                         Exemption Nos. 7120C, 7878A, and 9900.
                    </P>
                </FTNT>
                <P>
                    Due to the novelty of side-facing seats in transport category airplanes, acceptable safety measures for §  25.562 were unknown. The FAA conducted research to develop an acceptable method of compliance with §§  25.562 and 25.785(b) for side-facing seat installations. That research has identified injury considerations and evaluation criteria in addition to those previously used to approve side-facing seats (see published report DOT/FAA/AR-09/41, July 2011 
                    <SU>2</SU>
                    <FTREF/>
                    ). One particular concern that was identified during the FAA's research program but not addressed in special conditions prior to 2012 was the significant leg injuries that can occur to occupants of both single- and multiple-place side-facing seats. Because this type of injury does not occur on forward- and aft-facing seats, the FAA determined that to achieve the level of safety envisioned in Amendment 25-64, additional requirements would be needed as compared to previously issued special conditions. Nonetheless, the research has now allowed the development of a single set of special conditions that is applicable to all fully side-facing seats.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Document available at 
                        <E T="03">https://www.tc.faa.gov/its/worldpac/techrpt/ar09-41.pdf</E>
                        .
                    </P>
                </FTNT>
                <P>On November 5, 2012, the FAA released PS-ANM-25-03-R1, “Technical Criteria for Approving Side-Facing Seats,” to update existing FAA certification policy on §§  25.562 and 25.785(a) and (b) at Amendment 25-64 for single- and multiple-place side-facing seats. This policy addressed both the technical criteria for approving side-facing seats and the implementation of those criteria. The FAA methodology detailed in PS-ANM-25-03-R1 has been used to develop these special conditions. Some of the conditions issued for previous exemptions are still relevant and are included in these special conditions; however, others have been replaced by different criteria that reflect current research findings described above, as well as design features from the Gulfstream GVII model side-facing seat design.</P>
                <P>The special conditions contain the additional safety standards that the Administrator considers necessary to establish a level of safety equivalent to that established by the existing airworthiness standards.</P>
                <HD SOURCE="HD1">Discussion of Comments</HD>
                <P>
                    The FAA issued Notice of Proposed Special Conditions No. 25-23-07-SC for the Gulfstream Model GVIII-G700 and GVIII-G800 airplanes, which was published in the 
                    <E T="04">Federal Register</E>
                     on February 1, 2024 (89 FR 6443).
                </P>
                <P>The FAA received responses from two anonymous commenters. One commenter stated that they support the special conditions as proposed. The second commenter requested the FAA make the following changes to the proposed special conditions:</P>
                <P>1. The commenter requested the FAA replace the term “airbag” with “automatically deploying safety system.” The commenter stated that it should be clear that the installation of a different kind of automatically deploying safety system would necessitate the issuance of a new special condition. The FAA acknowledges that the current automatically-deploying safety systems proposed by applicants are airbag systems. If in the future the technology proposed by applicants should change, then there may be need for another special condition. No changes were made to these special conditions as a result of this comment.</P>
                <P>2. The commenter stated that the proposed special conditions paragraph 1.e(1)(b) may cause confusion, in that the word “bottom” is singular and the word “feet” is plural. This wording, according to the commenter, could lead to an interpretation that the force of about 20 pounds (lbs) may be applied to each foot, plus it is not specified that the force be applied uniformly. The commenter also suggested a specific revision to the text of this paragraph to address these concerns. The FAA disagrees that there is ambiguity or that a change is necessary. The 20 lbs of force is the total force applied to the bottom of the feet. The text of the special condition is similar to the language of FAA Policy Statement PS-ANM-25-03-R1 “Technical Criteria for Approving Side-Facing Seats.” No changes were made to these special conditions as a result of this comment.</P>
                <P>
                    3. The commenter suggested several changes to the formatting and technical 
                    <PRTPAGE P="18343"/>
                    content of paragraph 2.g. of the special conditions. The commenter suggested adding a colon at the end of paragraph g., and that subsequent special conditions should be numbered below that paragraph. The commenter also stated that paragraph 2.g. does not explicitly state when lap belt tension must be limited to 250 lbs, and that the rationale for the limit in the Civil Aerospace Medical Institute (CAMI) report does not have to be specified in the proposed special conditions. The commenter further stated that paragraph 2.g. has a typographical error in that data should be filtered at “CFC 600” as defined in SAE JS211-1 “Surface Vehicle Recommended Practice.” The FAA agrees with most of the comments received on paragraph 2.g. The FAA has revised the formatting of paragraph 2.g. to reflect the requirements clearly. The FAA does not concur with the commenter that the data should be filtered at CFC 600 versus 60. Sixty is the correct value for belt loads in SAE JS211-1.
                </P>
                <P>4. The commenter made two comments regarding paragraph 4.a. of these special conditions. The commenter suggested the FAA revise the phrase “that range of occupants” because it is missing explanation as to which range of occupants is being referred to. The FAA disagrees. The range of occupants is provided in Paragraph 3.b. Paragraph 3. states that “For all airbag systems in the shoulder harness and for leg flail the following apply” . . . Paragraph b. states that the means of protection must take into consideration a range of stature from a 2-year-old child to a 95th percentile male.</P>
                <P>The commenter further stated that in paragraph 4.a., the situations that must be considered do not account for the possibility that the seat occupant is a child in a child restraint device or booster seat. The FAA disagrees. Booster seats are not allowed. If a child restraint device is installed, the installation must show it would not harm the occupant, otherwise an operating limitation would need to limit to no child restraint device per condition 4.b. No changes were made to these special conditions as a result of this comment.</P>
                <P>Except as discussed above, the special conditions are adopted as proposed.</P>
                <HD SOURCE="HD1">Applicability</HD>
                <P>As discussed above, these special conditions are applicable to the Gulfstream Model GVIII-G700 and GVIII-G800 series airplanes. Should Gulfstream apply at a later date for a change to the type certificate to include another model that incorporates the same novel or unusual design feature, or should any other model already included on the same type certificate be modified to incorporate the same novel or unusual design feature, these special conditions would apply to the other model as well.</P>
                <P>
                    Under standard practice, the effective date of final special conditions would be 30 days after the date of publication in the 
                    <E T="04">Federal Register</E>
                    . However, as the certification date for the Gulfstream Model GVIII-G700 and GVIII-G800 series airplanes is imminent, the FAA finds that good cause exists to make these special conditions effective upon publication.
                </P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>This action affects only a certain novel or unusual design feature on Gulfstream Model GVIII-G700 and GVIII-G800 series of airplanes. It is not a rule of general applicability.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 25</HD>
                    <P>Aircraft, Aviation safety, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <HD SOURCE="HD1">Authority Citation</HD>
                <P>The authority citation for these special conditions is as follows:</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>49 U.S.C. 106(f), 106(g), 40113, 44701, 44702, 44704.</P>
                </AUTH>
                <HD SOURCE="HD1">The Special Conditions</HD>
                <P>Accordingly, pursuant to the authority delegated to me by the Administrator, the following special conditions are issued as part of the type certification basis for Gulfstream Model GVIII-G700 and GVIII-G800 series airplanes.</P>
                <P>In addition to the airworthiness standards in §§ 25.562 and 25.785, the FAA issues the following special conditions as part of the type certification basis for the Gulfstream Model GVIII-G700 and GVIII-G800 series aircraft. Items 1 through 3 are applicable to all side-facing seat installations on these airplanes. Item 4 imposes additional requirements applicable to side-facing seats equipped with an airbag system in the shoulder belt. Item 5 imposes additional requirements applicable to side-facing seats equipped with leg-flail airbag systems.</P>
                <P>1. Additional requirements applicable to tests or rational analysis conducted to show compliance with §§ 25.562 and 25.785 for side-facing seats:</P>
                <P>
                    a. The longitudinal test(s) conducted in accordance with § 25.562(b)(2) to show compliance with the seat-strength requirements of § 25.562(c)(7) and (8), and these special conditions must have an ES-2re anthropomorphic test dummy (ATD) (49 CFR part 572 subpart U) or equivalent, or a Hybrid-II ATD (49 CFR part 572, subpart B as specified in § 25.562) or equivalent, occupying each seat position and including all items contactable by the occupant (
                    <E T="03">e.g.,</E>
                     armrest, interior wall, or furnishing) if those items are necessary to restrain the occupant. If included, the floor representation and contactable items must be located such that their relative position, with respect to the center of the nearest seat place, is the same at the start of the test as before floor misalignment is applied. For example, if floor misalignment rotates the centerline of the seat place nearest the contactable item 8 degrees clockwise about the aircraft x-axis, then the item and floor representations must be rotated by 8 degrees clockwise also to maintain the same relative position to the seat place, as shown in Figure 1. Each ATD's relative position to the seat after application of floor misalignment must be the same as before misalignment is applied. The ATD pelvis must remain supported by the seat pan, and the restraint system must remain on the pelvis and shoulder of the ATD until rebound begins. No injury-criteria evaluation is necessary for tests conducted only to assess seat-strength requirements.
                </P>
                <P>
                    b. The longitudinal test(s) conducted in accordance with § 25.562(b)(2), to show compliance with the injury assessments required by § 25.562(c) and these special conditions, may be conducted separately from the test(s) to show structural integrity. Structural-assessment tests must be conducted as specified in paragraph 1.a., above, and the injury-assessment test must be conducted without yaw or floor misalignment. Injury assessments may be accomplished by testing with ES-2re ATD (49 CFR part 572 subpart U) or equivalent at all places. Alternatively, these assessments may be accomplished by multiple tests that use an ES-2re at the seat place being evaluated, and a Hybrid-II ATD (49 CFR part 572, subpart B, as specified in § 25.562) or equivalent used in all seat places forward of the one being assessed, to evaluate occupant interaction. Seat places aft of the one being assessed may be unoccupied. If a seat installation includes adjacent items that are contactable by the occupant, the injury potential of that contact must be assessed. To make this assessment, tests may be conducted that include the actual item, located, and attached in a representative fashion. Alternatively, the injury potential may be assessed by a combination of tests with items having 
                    <PRTPAGE P="18344"/>
                    the same geometry as the actual item, but having stiffness characteristics that would create the worst case for injury (injuries due to both contact with the item and lack of support from the item).
                </P>
                <P>
                    c. If a seat is installed aft of structure (
                    <E T="03">e.g.,</E>
                     an interior wall or furnishing) that does not have a homogeneous surface contactable by the occupant, additional analysis and/or test(s) may be required to demonstrate that the injury criteria are met for the area which an occupant could contact. For example, different yaw angles could result in different injury considerations and may require additional analysis or separate test(s) to evaluate.
                </P>
                <P>d. To accommodate a range of occupant heights (5th percentile female to 95th percentile male), the surface of items contactable by the occupant must be homogenous 7.3 inches (185 mm) above and 7.9 inches (200 mm) below the point (center of area) that is contacted by the 50th percentile male size ATD's head during the longitudinal test(s) conducted in accordance with paragraphs a, b, and c, above. Otherwise, additional head-injury criteria (HIC) assessment tests may be necessary. Any surface (inflatable or otherwise) that provides support for the occupant of any seat place must provide that support in a consistent manner regardless of occupant stature. For example, if an inflatable shoulder belt is used to mitigate injury risk, then it must be demonstrated by inspection to bear against the range of occupants in a similar manner before and after inflation. Likewise, the means of limiting lower-leg flail must be demonstrated by inspection to provide protection for the range of occupants in a similar manner.</P>
                <P>e. For longitudinal test(s) conducted in accordance with § 25.562(b)(2) and these special conditions, the ATDs must be positioned, clothed, and have lateral instrumentation configured as follows:</P>
                <P>
                    (1) 
                    <E T="03">ATD positioning:</E>
                </P>
                <P>Lower the ATD vertically into the seat while simultaneously (see Figure 2 for illustration):</P>
                <P>(a) Aligning the midsagittal plane (a vertical plane through the midline of the body; dividing the body into right and left halves) with approximately the middle of the seat place.</P>
                <P>(b) Applying a horizontal x-axis direction (in the ATD coordinate system) force of about 20 pounds (lbs) (89 Newtons [N]) to the bottom of the feet of the ATD with the legs straight, to compress the seat back cushion.</P>
                <P>(c) Keeping the legs nearly horizontal by supporting them just behind the ankles.</P>
                <P>(d) Once all lifting devices have been removed from the ATD:</P>
                <P>(i) Rock it slightly to settle it in the seat.</P>
                <P>(ii) Gently lower the ankles of the ATD bending the legs at the knee joints. Do not allow the pelvis of the ATD to be moved when the lower legs are lowered. The seat back cushion must remain compressed. Separate the knees by about 4 inches (100 mm).</P>
                <P>(iii) Set the ES-2re's head at approximately the midpoint of the available range of z-axis rotation (to align the head and torso midsagittal planes).</P>
                <P>(iv) Position the ES-2re's arms at the joint's mechanical detent that puts them at approximately a 40-degree angle with respect to the torso. Position the Hybrid-II ATD hands on top of its upper legs.</P>
                <P>(v) Position the feet such that the centerlines of the lower legs are approximately parallel to a lateral vertical plane (in the aircraft coordinate system).</P>
                <P>
                    (2) 
                    <E T="03">ATD clothing:</E>
                     Clothe each ATD in form-fitting, mid-calf-length (minimum) pants and shoes (size 11E) weighing about 2.5 lb (1.1 Kg) total. The color of the clothing should be in contrast to the color of the restraint system. The ES-2re jacket is sufficient for torso clothing, although a form-fitting shirt may be used in addition if desired.
                </P>
                <P>
                    (3) 
                    <E T="03">ES-2re ATD lateral instrumentation:</E>
                     The rib-module linear slides are directional, 
                    <E T="03">i.e.,</E>
                     deflection occurs in either a positive or negative ATD y-axis direction. The modules must be installed such that the moving end of the rib module is toward the front of the aircraft. The three abdominal-force sensors must be installed such that they are on the side of the ATD toward the front of the aircraft.
                </P>
                <P>f. The combined horizontal/vertical test, required by § 25.562(b)(1) and these special conditions, must be conducted with a Hybrid II ATD (49 CFR part 572 subpart B as specified in § 25.562), or equivalent, occupying each seat position.</P>
                <P>
                    g. 
                    <E T="03">Restraint systems:</E>
                </P>
                <P>(1) If inflatable restraint systems are used, they must be active during all dynamic tests conducted to show compliance with § 25.562.</P>
                <P>(2) The design and installation of seat-belt buckles must prevent unbuckling due to applied inertial forces or impact of the hands/arms of the occupant during an emergency landing.</P>
                <P>2. Additional performance measures applicable to tests and rational analysis conducted to show compliance with §§ 25.562 and 25.785 for side-facing seats:</P>
                <P>
                    a. 
                    <E T="03">Body-to-body contact:</E>
                     Contact between the head, pelvis, torso, or shoulder area of one ATD with the adjacent-seated ATD's head, pelvis, torso, or shoulder area is not allowed. Contact during rebound is allowed.
                </P>
                <P>
                    b. 
                    <E T="03">Thoracic:</E>
                     The deflection of any of the ES-2re ATD upper, middle, and lower ribs must not exceed 1.73 inches (44 mm). Data must be processed as defined in Federal Motor Vehicle Safety Standards (FMVSS) 571.214.
                </P>
                <P>
                    c. 
                    <E T="03">Abdominal:</E>
                     The sum of the measured ES-2re ATD front, middle, and rear abdominal forces must not exceed 562 lbs (2,500 N). Data must be processed as defined in FMVSS 571.214.
                </P>
                <P>
                    d. 
                    <E T="03">Pelvic:</E>
                     The pubic symphysis force measured by the ES-2re ATD must not exceed 1,350 lbs (6,000 N). Data must be processed as defined in FMVSS 571.214.
                </P>
                <P>
                    e. 
                    <E T="03">Leg:</E>
                     Axial rotation of the upper-leg (femur) must be limited to 35 degrees in either direction from the nominal seated position.
                </P>
                <P>
                    f. 
                    <E T="03">Neck:</E>
                     As measured by the ES-2re ATD and filtered at CFC 600 as defined in SAE J211:
                </P>
                <P>(1) The upper-neck tension force at the occipital condyle (O.C.) location must be less than 405 lb (1,800 N).</P>
                <P>(2) The upper-neck compression force at the O.C. location must be less than 405 lb (1,800 N).</P>
                <P>(3) The upper-neck bending torque about the ATD x-axis at the O.C. location must be less than 1,018 in-lb (115 Nm).</P>
                <P>(4) The upper-neck resultant shear force at the O.C. location must be less than 186 lb (825 N).</P>
                <P>
                    g. 
                    <E T="03">Occupant (ES-2re ATD) retention:</E>
                     The upper-torso restraint straps (if present) must remain on the ATD's shoulder during the impact. The pelvic restraint must remain on the ES-2re ATD's pelvis during the impact. The pelvic restraint must remain on the ES-2re ATD's pelvis during rebound unless the following criteria are met.
                </P>
                <P>
                    (1) A measurement of the belt loop load during the time when the belt moves above the pelvis (submarining) must not exceed 500 lbs (2,225 N) 
                    <E T="03">(a 250 lb (1112.5 N) lap belt tension limit).</E>
                     Data must be filtered at CFC 60 as defined in SAE J211. To evaluate the pelvic restraint performance using this criterion, three things are needed:
                </P>
                <P>
                    (a) A clear indication of when the belt moves above the pelvis. Loose clothing can make it difficult to determine where the top of the pelvis is, and in turn make it hard to discern exactly when the belt moved above it. This can be improved by marking the top of the pelvis clearly and by positioning the cameras so that 
                    <PRTPAGE P="18345"/>
                    the position of the belt, relative to the top of the pelvis can be observed throughout the test (see Figure 3).
                </P>
                <P>(b) A measurement of the belt tension during the time when the belt moves above the pelvis. Place the webbing transducer to measure the total tension in the forward lap belt segment. If a split (combined body-centered and conventional) leading belt is used, measure the tension in the common section so that it reflects the contribution of each segment. Since this placement typically produces contact between the ATD and the transducer, it is important to use a webbing transducer that is not sensitive to contact.</P>
                <P>(c) Record useful video and belt load data until significant ATD rebound motion stops. Extra recording time is necessary because submarining usually occurs later in the test than other injury criteria maximums. To completely capture ATD rebound, the necessary time could exceed 500 ms.</P>
                <P>
                    h. 
                    <E T="03">Occupant (ES-2re ATD) support:</E>
                </P>
                <P>
                    (1) 
                    <E T="03">Pelvis excursion:</E>
                     The load-bearing portion of the bottom of the ATD pelvis must not translate beyond the edges of its seat's bottom seat-cushion supporting structure.
                </P>
                <P>
                    (2) 
                    <E T="03">Upper-torso support:</E>
                     The lateral flexion of the ATD torso must not exceed 40 degrees from the normal upright position during the impact.
                </P>
                <P>3. For all airbag systems in the shoulder harness and for leg flail, the following apply:</P>
                <P>a. Show that the airbag system will deploy and provide protection under crash conditions where it is necessary to prevent serious injury.</P>
                <P>b. The means of protection must take into consideration a range of stature from a 2-year-old child to a 95th percentile male.</P>
                <P>c. The airbag system must provide adequate protection for each occupant regardless of the number of occupants of the seat assembly, considering that unoccupied seats may have an active airbag system.</P>
                <P>d. It must be shown that the airbag system is not susceptible to inadvertent deployment as a result of wear and tear, or inertial loads resulting from in-flight or ground maneuvers (including gusts and hard landings), and other operating and environmental conditions (vibrations, moisture, etc.) likely to occur in service.</P>
                <P>e. Deployment of the airbag system must not introduce injury mechanisms to the seated occupant, or result in injuries that could impede rapid egress. This assessment should include an occupant whose seat belt is loosely fastened.</P>
                <P>f. It must be shown that inadvertent deployment of the airbag system, during the most critical part of the flight, will either meet the requirement of § 25.1309(b) or not cause a hazard to the airplane or its occupants.</P>
                <P>g. It must be shown that the airbag system will not impede rapid egress of occupants 10 seconds after airbag deployment.</P>
                <P>h. The airbag system must be protected from lightning and high-intensity radiated fields (HIRF). The threats to the airplane specified in existing regulations regarding lighting, § 25.1316, and HIRF, § 25.1317, are adopted by reference for the purpose of measuring lightning and HIRF protection.</P>
                <P>i. The airbag system must function properly after loss of normal aircraft electrical power, and after a transverse separation of the fuselage at the most critical location. A separation at the location of the airbag system does not have to be considered.</P>
                <P>j. It must be shown that the airbag system will not release hazardous quantities of gas or particulate matter into the cabin.</P>
                <P>k. The airbag system installation must be protected from the effects of fire such that no hazard to occupants will result.</P>
                <P>
                    l. A means must be available for a crewmember to verify the integrity of the airbag system prior to each flight, or it must be demonstrated to reliably operate between inspection intervals. The FAA considers that the loss of the airbag-system deployment function alone (
                    <E T="03">i.e.,</E>
                     independent of the conditional event that requires the airbag-system deployment) is a major-failure condition.
                </P>
                <P>m. The inflatable material may not have an average burn rate of greater than 2.5 inches/minute when tested using the horizontal flammability test defined in part 25, appendix F, part I, paragraph (b)(5).</P>
                <P>
                    n. The airbag system, once deployed, must not adversely affect the emergency-lighting system (
                    <E T="03">i.e.,</E>
                     block floor proximity lights to the extent that the lights no longer meet their intended function).
                </P>
                <P>
                    o. The airbag system must perform its intended function after impact from other proximate assemblies (
                    <E T="03">e.g.,</E>
                     life raft) that may become detached under the loads specified in §§ 25.561 and 25.562.
                </P>
                <P>4. For seats with an airbag system in the shoulder belts, the following apply:</P>
                <P>a. The airbag system in the shoulder belt must provide a consistent approach to energy absorption throughout that range of occupants. The airbag system must be included in each of the certification tests as it would be installed in the airplane. In addition, the following situations must be considered:</P>
                <P>(1) The seat occupant is holding an infant.</P>
                <P>(2) The seat occupant is a pregnant woman.</P>
                <P>b. The design must prevent the airbag system in the shoulder belt from being either incorrectly buckled or incorrectly installed, such that the airbag system in the shoulder belt would not properly deploy. Alternatively, it must be shown that such deployment is not hazardous to the occupant, and will provide the required injury protection.</P>
                <P>5. For seats using an airbag system to meet the leg-flail conditions of 2.e. the following apply:</P>
                <P>a. At some buttock popliteal length and effective seat bottom depth the lower legs will not be able to make a 90-degree angle with the upper leg; at this point the lower leg flail would not occur. The leg flail airbag system must provide a consistent approach to prevention of leg flail throughout that range of occupants whose lower legs can make a 90-degree angle with the upper legs when seated upright in the seat. Items that need to be considered include, but are not limited to the range of occupants' popliteal height, the range of occupants' buttock popliteal length, the design of the seat effective height above the floor, and the effective depth of the seat bottom cushion.</P>
                <P>b. For all g-levels, if the design of the leg flail limited device does absorb some of the impact energy and returns only a portion to the legs (a qualitative assessment), then a rebound leg flail of greater than 35 degrees is acceptable.</P>
                <P>c. Threshold test severity must be shown to be non-injurious (less than the post-mortem human subject (PMHS) low-g research testing) for g-levels up to the point where the leg flail airbag is designed to deploy.</P>
                <BILCOD>BILLING CODE 4910-13-P</BILCOD>
                <GPH SPAN="3" DEEP="546">
                    <PRTPAGE P="18346"/>
                    <GID>ER13MR24.005</GID>
                </GPH>
                <GPH SPAN="3" DEEP="349">
                    <PRTPAGE P="18347"/>
                    <GID>ER13MR24.006</GID>
                </GPH>
                <GPH SPAN="3" DEEP="253">
                    <GID>ER13MR24.007</GID>
                </GPH>
                <SIG>
                    <PRTPAGE P="18348"/>
                    <DATED>Issued in Kansas City, Missouri, on March 6, 2024.</DATED>
                    <NAME>James David Foltz,</NAME>
                    <TITLE>Manager, Technical Policy Branch, Policy and Standards Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05226 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-C</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2023-2149; Project Identifier MCAI-2023-00136-E; Amendment 39-22675; AD 2024-03-05]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; GE Aviation Czech s.r.o. (Type Certificate Previously Held by WALTER Engines a.s., Walter a.s., and MOTORLET a.s.) Engines</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA is superseding Airworthiness Directive (AD) 2022-13-16 for all GE Aviation Czech s.r.o. (GEAC) (type certificate previously held by WALTER Engines a.s., Walter a.s., and MOTORLET a.s.) Model M601D-11 engines; and AD 2022-14-12, for certain GEAC Model M601D-11, M601E-11, M601E-11A, M601E-11AS, M601E-11S, and M601F engines. AD 2022-13-16 required revising the airworthiness limitations section (ALS) of the existing engine maintenance manual (EMM) to incorporate a visual inspection of the centrifugal compressor case for cracks. AD 2022-14-12 required replacing the propeller shaft for Model M601F engines. AD 2022-14-12 also required calculating the accumulated life of the propeller shaft and replacing the propeller shaft, if necessary, for model M601D-11, M601E-11, M601E-11A, M601E-11AS, and M601E-11S engines. Since the FAA issued AD 2022-13-16 and AD 2022-14-12, the manufacturer revised the ALS of the existing EMM to introduce new and more restrictive tasks and limitations, expand the applicability to all Model M601 engines, and incorporate certain requirements addressed by AD 2021-13-07 and AD 2023-01-10, which prompted this AD. This AD requires revising the ALS of the existing EMM and the operator's existing approved engine maintenance or inspection program, as applicable, to incorporate new and more restrictive tasks and limitations, as specified in a European Union Aviation Safety Agency (EASA) AD, which is incorporated by reference. The FAA is issuing this AD to address the unsafe condition on these products.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This AD is effective April 17, 2024.</P>
                    <P>The Director of the Federal Register approved the incorporation by reference of a certain publication listed in this AD as of April 17, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        <E T="03">AD Docket:</E>
                         You may examine the AD docket at 
                        <E T="03">regulations.gov</E>
                         under Docket No.FAA-2023-2149; or in person at Docket Operations between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this final rule, the mandatory continuing airworthiness information (MCAI), any comments received, and other information. The address for Docket Operations is U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE, Washington, DC 20590.
                    </P>
                    <P>
                        <E T="03">Material Incorporated by Reference:</E>
                    </P>
                    <P>
                        • For service information identified in this final rule, contact EASA, Konrad-Adenauer-Ufer 3, 50668 Cologne, Germany; phone: +49 221 8999 000; email: 
                        <E T="03">ADs@easa.europa.eu;</E>
                         website: 
                        <E T="03">easa.europa.eu.</E>
                         You may find this material on the EASA website at 
                        <E T="03">ad.easa.europa.eu.</E>
                    </P>
                    <P>
                        • You may view this service information at the FAA, Airworthiness Products Section, Operational Safety Branch, 1200 District Avenue, Burlington, MA 01803. For information on the availability of this material at the FAA, call (817) 222-5110. It is also available at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2023-2149.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Barbara Caufield, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; phone: (781) 238-7146; email: 
                        <E T="03">barbara.caufield@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>The FAA issued a notice of proposed rulemaking (NPRM) to amend 14 CFR part 39 to supersede AD 2022-13-16, Amendment 39-22102 (87 FR 37986, June 27, 2022) (AD 2022-13-16); and AD 2022-14-12, Amendment 39-22117 (87 FR 42066, July 14, 2022) (AD 2022-14-12).</P>
                <P>AD 2022-13-16 applied to all GEAC Model M601D-11 engines and required revising the ALS of the existing EMM to incorporate a visual inspection of the centrifugal compressor case. The FAA issued AD 2022-13-16 to prevent failure of the centrifugal compressor case.</P>
                <P>AD 2022-14-12 applied to certain GEAC Model M601D-11, M601E-11, M601E-11A, M601E-11AS, M601E-11S, and M601F engines. For Model M601F engines, AD 2022-14-12 required replacement of the propeller shaft. For Model M601D-11, M601E-11, M601E-11A, M601E-11AS, and M601E-11S engines, AD 2022-14-12 required calculating the accumulated life of the propeller shaft and replacing the propeller shaft if necessary.</P>
                <P>
                    The NPRM published in the 
                    <E T="04">Federal Register</E>
                     on November 14, 2023 (88 FR 77918). The NPRM was prompted by EASA AD 2023-0020, dated January 23, 2023 (EASA AD 2023-0020) (also referred to as the MCAI), issued by EASA, which is the Technical Agent for the Member States of the European Union. The MCAI states that the manufacturer revised the ALS to incorporate new and more restrictive tasks and limitations, expand the applicability to all model M601 series engines, and include certain requirements that were previously addressed by EASA Emergency AD 2021-0125-E and EASA AD 2021-0264. The MCAI also states that the manufacturer published service information that specifies instructions to determine the accumulated life of certain propeller shafts.
                </P>
                <P>
                    You may examine the MCAI in the AD docket at 
                    <E T="03">regulations.gov</E>
                     under Docket No. FAA-2023-2149.
                </P>
                <P>In the NPRM, the FAA proposed to require revising the ALS of the existing EMM and the operator's existing approved engine maintenance or inspection program, as applicable, to incorporate new and more restrictive tasks and limitations.</P>
                <HD SOURCE="HD1">Discussion of Final Airworthiness Directive</HD>
                <HD SOURCE="HD1">Comments</HD>
                <P>The FAA received no comments on the NPRM or on the determination of the costs.</P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>
                    These products have been approved by the aviation authority of another country and are approved for operation in the United States. Pursuant to the FAA's bilateral agreement with this State of Design Authority, it has notified the FAA of the unsafe condition described in the MCAI referenced above. The FAA reviewed the relevant data and determined that air safety requires adopting this AD as proposed. Accordingly, the FAA is issuing this AD to address the unsafe condition on these 
                    <PRTPAGE P="18349"/>
                    products. Except for minor editorial changes, this AD is adopted as proposed in the NPRM.
                </P>
                <HD SOURCE="HD1">Related Service Information Under 1 CFR Part 51</HD>
                <P>The FAA reviewed EASA AD 2023-0020, which specifies procedures for accomplishment of the actions specified in the ALS, including performing maintenance tasks, replacing life-limited parts, and revising the existing approved maintenance or inspection program, as applicable, by incorporating the instructions and associated thresholds and intervals described in the ALS, as applicable to engine model and depending on engine configuration.</P>
                <P>
                    This service information is reasonably available because the interested parties have access to it through their normal course of business or by the means identified in 
                    <E T="02">ADDRESSES</E>
                    .
                </P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>The FAA estimates that this AD affects 42 engines installed on airplanes of U.S. registry.</P>
                <P>The FAA estimates the following costs to comply with this AD:</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,r75,12,12,12">
                    <TTITLE>Estimated Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Action</CHED>
                        <CHED H="1">Labor cost</CHED>
                        <CHED H="1">Parts cost</CHED>
                        <CHED H="1">
                            Cost per 
                            <LI>product</LI>
                        </CHED>
                        <CHED H="1">Cost on U.S. operators</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Revise the ALS</ENT>
                        <ENT>1 work-hours x $85 per hour = $85</ENT>
                        <ENT>$0</ENT>
                        <ENT>$85</ENT>
                        <ENT>$3,570</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII: Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
                <P>The FAA is issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701: General requirements. Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>The FAA has determined that this AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>For the reasons discussed above, I certify that this AD:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
                <P>(2) Will not affect intrastate aviation in Alaska, and</P>
                <P>(3) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                </PART>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 39.13 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>2. The FAA amends § 39.13 by:</AMDPAR>
                    <AMDPAR>a. Removing Airworthiness Directive 2022-13-16, Amendment 39-22102 (87 FR 37986, June 27, 2022); and Airworthiness Directive 2022-14-12, Amendment 39-22117 (87 FR 42066, July 14, 2022); and</AMDPAR>
                    <AMDPAR>b. Adding the following new airworthiness directive:</AMDPAR>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            <E T="04">2024-03-05 GE Aviation Czech s.r.o. (Type Certificate Previously Held by WALTER Engines a.s., Walter a.s., and MOTORLET a.s.):</E>
                             Amendment 39-22675; Docket No. FAA-2023-2149; Project Identifier MCAI-2023-00136-E.
                        </FP>
                        <HD SOURCE="HD1">(a) Effective Date</HD>
                        <P>This airworthiness directive (AD) is effective April 17, 2024.</P>
                        <HD SOURCE="HD1">(b) Affected ADs</HD>
                        <P>(1) This AD affects AD 2021-13-07, Amendment 39-21612 (86 FR 31601, June 15, 2021) (AD 2021-13-07).</P>
                        <P>(2) This AD replaces AD 2022-13-16, Amendment 39-22102 (87 FR 37986, June 27, 2022).</P>
                        <P>(3) This AD replaces AD 2022-14-12, Amendment 39-22117 (87 FR 42066, July 14, 2022).</P>
                        <P>(4) This AD affects AD 2023-01-10, Amendment 39-22304 (88 FR 7578, February 6, 2023) (AD 2023-01-10).</P>
                        <HD SOURCE="HD1">(c) Applicability</HD>
                        <P>This AD applies to GE Aviation Czech s.r.o. (GEAC) (type certificate previously held by WALTER Engines a.s., Walter a.s., and MOTORLET a.s.) Model M601D-11, M601E-11, M601E-11A, M601E-11AS, M601E-11S, and M601F engines.</P>
                        <HD SOURCE="HD1">(d) Subject</HD>
                        <P>Joint Aircraft System Component (JASC) Code 7210, Turbine Engine Reduction Gear.</P>
                        <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                        <P>This AD was prompted by the manufacturer revising the airworthiness limitations section (ALS) of the existing engine maintenance manual (EMM) to introduce new and more restrictive tasks and limitations and associated thresholds and intervals for life-limited parts. The FAA is issuing this AD to prevent failure of the engine. The unsafe condition, if not addressed, could result in uncontained release of a critical part, damage to the engine, and damage to the airplane.</P>
                        <HD SOURCE="HD1">(f) Compliance</HD>
                        <P>Comply with this AD within the compliance times specified, unless already done.</P>
                        <HD SOURCE="HD1">(g) Required Actions</HD>
                        <P>(1) Except as specified in paragraph (h) of this AD: Perform all required actions within the compliance times specified in, and in accordance with, European Union Aviation Safety Agency (EASA) AD 2023-0020, dated January 23, 2023 (EASA AD 2023-0020).</P>
                        <P>(2) The action required by paragraph (g)(1) of this AD may be performed by the owner/operator (pilot) holding at least a private pilot certificate and must be entered into the aircraft records showing compliance with this AD in accordance with 14 CFR 43.9(a) and 91.417(a)(2)(v). The record must be maintained as required by 14 CFR 91.417, 121.380, or 135.439.</P>
                        <HD SOURCE="HD1">(h) Exceptions to EASA AD 2023-0020</HD>
                        <P>
                            (1) Where EASA AD 2023-0020 defines the AMP as “The Aircraft Maintenance Programme (AMP) contains the tasks on the basis of which the scheduled maintenance is conducted to ensure the continuing airworthiness of each operated engine,” replace that text with “the aircraft 
                            <PRTPAGE P="18350"/>
                            maintenance program containing the tasks on the basis of which the scheduled maintenance is conducted to ensure the continuing airworthiness of each operated airplane.”
                        </P>
                        <P>(2) Where EASA AD 2023-0020 specifies the ALS as “The Airworthiness Limitations Section of the GEAC Engine Maintenance Manual (EMM) No. 0982309 Revision 21,” replace that text with “The Airworthiness Limitations Section of the GEAC Engine Maintenance Manual (EMM) No. 0982309 Revision 22.” The ALS in Revision 22 of the EMM is unchanged from Revision 21.</P>
                        <P>(3) Where EASA AD 2023-0020 refers to its effective date, this AD requires using the effective date of this AD.</P>
                        <P>(4) Where paragraph (3) of EASA AD 2023-0020 specifies “Within 12 months after the effective date of this AD, revise the approved AMP,” replace that text with “Within 90 days after the effective date of this AD, revise the ALS of the existing approved engine maintenance or inspection program, as applicable.”</P>
                        <P>(5) This AD does not require compliance with paragraphs (1), (2), (4), and (5) of EASA AD 2023-0020.</P>
                        <P>(6) This AD does not adopt the Remarks paragraph of EASA AD 2023-0020.</P>
                        <HD SOURCE="HD1">(i) Provisions for Alternative Actions and Intervals</HD>
                        <P>After performing the actions required by paragraph (g) of this AD, no alternative actions and associated thresholds and intervals, including life limits, are allowed unless they are approved as specified in the provisions of the “Ref. Publications” section of EASA AD 2023-0020.</P>
                        <HD SOURCE="HD1">(j) Terminating Action for Certain Actions Required by Affected ADs</HD>
                        <P>(1) Accomplishing the actions required by paragraph (g) of this AD terminates the requirements of paragraphs (g)(1) through (3) of AD 2021-13-07 for model M601D-11, M601E-11, M601E-11A, M601E-11AS, M601E-11S, and M601F engines only.</P>
                        <P>(2) Accomplishing the actions required by paragraph (g) of this AD terminates the requirements of paragraphs (g)(1) through (3) of AD 2023-01-10 for model M601E-11, M601E-11A, M601E-11AS, M601E-11S, and M601F engines only.</P>
                        <HD SOURCE="HD1">(k) Alternative Methods of Compliance (AMOCs)</HD>
                        <P>
                            (1) The Manager, International Validation Branch, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the manager of the International Validation Branch, send it to the attention of the person identified in paragraph (l) of this AD and email to 
                            <E T="03">ANE-AD-AMOC@faa.gov.</E>
                        </P>
                        <P>(2) Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office.</P>
                        <HD SOURCE="HD1">(l) Additional Information</HD>
                        <P>
                            For more information about this AD, contact Barbara Caufield, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; phone: (781) 238-7146; email: 
                            <E T="03">barbara.caufield@faa.gov.</E>
                        </P>
                        <HD SOURCE="HD1">(m) Material Incorporated by Reference</HD>
                        <P>(1) The Director of the Federal Register approved the incorporation by reference of the service information listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.</P>
                        <P>(2) You must use this service information as applicable to do the actions required by this AD, unless the AD specifies otherwise.</P>
                        <P>(i) European Union Aviation Safety Agency (EASA) AD 2023-0020, dated January 23, 2023.</P>
                        <P>(ii) [Reserved]</P>
                        <P>
                            (3) For EASA AD 2023-0020, contact EASA, Konrad-Adenauer-Ufer 3, 50668 Cologne, Germany; phone: +49 221 8999 000; email: 
                            <E T="03">ADs@easa.europa.eu;</E>
                             website: 
                            <E T="03">easa.europa.eu.</E>
                             You may find this EASA AD on the EASA website at 
                            <E T="03">ad.easa.europa.eu.</E>
                        </P>
                        <P>(4) You may view this service information at FAA, Airworthiness Products Section, Operational Safety Branch, 1200 District Avenue, Burlington, MA 01803. For information on the availability of this material at the FAA, call (817) 222-5110.</P>
                        <P>
                            (5) You may view this material at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, visit: 
                            <E T="03">www.archives.gov/federal-register/cfr/ibr-locations</E>
                             or email: 
                            <E T="03">fr.inspection@nara.gov.</E>
                        </P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued on February 7, 2024.</DATED>
                    <NAME>Victor Wicklund,</NAME>
                    <TITLE>Deputy Director, Compliance &amp; Airworthiness Division,Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05247 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2024-0458; Project Identifier MCAI-2024-00116-E; Amendment 39-22694; AD 2024-04-51]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Pratt &amp; Whitney Canada Corp. Engines</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA is adopting a new airworthiness directive (AD) for all Pratt &amp; Whitney Canada Corp. (P&amp;WC) Model PT6A-64, PT6A-66, PT6A-66A, PT6A-66B, PT6A-66D, PT6A-67, PT6A-67A, PT6A-67AF, PT6A-67AG, PT6A-67B, PT6A-67D, PT6A-67F, PT6A-67P, PT6A-67R, PT6A-67RM, PT6A-67T, PT6A-68, PT6A-68D, PT6E-67XP, and PT6E-66XT engines. The FAA previously sent this AD as an emergency AD to all known U.S. owners and operators of these engines. This AD was prompted by reports of second-stage power turbine (PT2) blade failures. This AD requires removal of affected PT2 blades prior to the next flight and prohibits installation of affected PT2 blades, as specified in a Transport Canada Emergency AD, which is incorporated by reference. The FAA is issuing this AD to address the unsafe condition on these products.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This AD is effective March 28, 2024. Emergency AD 2024-04-51, issued on February 16, 2024, which contained the requirements of this amendment, was effective with actual notice.</P>
                    <P>The Director of the Federal Register approved the incorporation by reference of a certain publication identified in this AD as of March 28, 2024.</P>
                    <P>The FAA must receive comments on this AD by April 29, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments, using the procedures found in 14 CFR 11.43 and 11.45, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (202) 493-2251.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE, Washington, DC 20590.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         Deliver to Mail address above between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        <E T="03">AD Docket:</E>
                         You may examine the AD docket at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2024-0458; or in person at Docket Operations between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this final rule, the mandatory continuing airworthiness information (MCAI), any comments received, and other information. The street address for Docket Operations is listed above.
                    </P>
                    <P>
                        <E T="03">Material Incorporated by Reference:</E>
                    </P>
                    <P>
                        • For service information identified in this final rule, contact Transport Canada, Transport Canada National Aircraft Certification, 159 Cleopatra Drive, Nepean, Ontario K1A 0N5, Canada; phone: (888) 663-3639; email: 
                        <E T="03">TC.AirworthinessDirectives-Consignesdenavigabilite.TC@tc.gc.ca;</E>
                         website: 
                        <E T="03">tc.canada.ca/en/aviation.</E>
                    </P>
                    <P>
                        • You may view this material at the FAA, Airworthiness Products Section, 
                        <PRTPAGE P="18351"/>
                        Operational Safety Branch, 2200 South 216th Street, Des Moines, WA. For information on the availability of this material at the FAA, call (817) 222-5110. It is also available at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2024-0458.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Barbara Caufield, Aviation Safety Engineer, FAA, 2200 South 216th Street, Des Moines, WA 98198; phone: (781) 238-7146; email: 
                        <E T="03">barbara.caufield@faa.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>
                    The FAA invites you to send any written data, views, or arguments about this final rule. Send your comments to an address listed under 
                    <E T="02">ADDRESSES</E>
                    . Include “Docket No. FAA-2024-0458; Project Identifier MCAI-2024-00116-E” at the beginning of your comments. The most helpful comments reference a specific portion of the final rule, explain the reason for any recommended change, and include supporting data. The FAA will consider all comments received by the closing date and may amend this final rule because of those comments.
                </P>
                <P>
                    Except for Confidential Business Information (CBI) as described in the following paragraph, and other information as described in 14 CFR 11.35, the FAA will post all comments received, without change, to 
                    <E T="03">regulations.gov,</E>
                     including any personal information you provide. The agency will also post a report summarizing each substantive verbal contact received about this final rule.
                </P>
                <HD SOURCE="HD1">Confidential Business Information</HD>
                <P>CBI is commercial or financial information that is both customarily and actually treated as private by its owner. Under the Freedom of Information Act (FOIA) (5 U.S.C. 552), CBI is exempt from public disclosure. If your comments responsive to this AD contain commercial or financial information that is customarily treated as private, that you actually treat as private, and that is relevant or responsive to this AD, it is important that you clearly designate the submitted comments as CBI. Please mark each page of your submission containing CBI as “PROPIN.” The FAA will treat such marked submissions as confidential under the FOIA, and they will not be placed in the public docket of this AD. Submissions containing CBI should be sent to Barbara Caufield, Aviation Safety Engineer, FAA, 2200 South 216th Street, Des Moines, WA 98198. Any commentary that the FAA receives which is not specifically designated as CBI will be placed in the public docket for this rulemaking.</P>
                <HD SOURCE="HD1">Background</HD>
                <P>The FAA issued Emergency AD 2024-04-51, dated February 16, 2024 (the emergency AD), to address an unsafe condition on P&amp;WC Model PT6A-64, PT6A-66, PT6A-66A, PT6A-66B, PT6A-66D, PT6A-67, PT6A-67A, PT6A-67AF, PT6A-67AG, PT6A-67B, PT6A-67D, PT6A-67F, PT6A-67P, PT6A-67R, PT6A-67RM, PT6A-67T, PT6A-68, PT6A-68D, PT6E-67XP, and PT6E-66XT engines. The FAA sent the emergency AD to all known U.S. owners and operators of these engines. The emergency AD requires removal of affected PT2 blades prior to the next flight. The emergency AD also prohibits installation of affected PT2 blades.</P>
                <P>The emergency AD was prompted by Transport Canada Emergency AD CF-2024-05, dated February 15, 2024 (Transport Canada Emergency AD CF-2024-05) (referred to after this as the MCAI), issued by Transport Canada, which is the aviation authority for Canada, to correct an unsafe condition on P&amp;WC Model PT6A-64, PT6A-66, PT6A-66A, PT6A-66B, PT6A-66D, PT6A-66T, PT6A-67, PT6A-67A, PT6A-67AF, PT6A-67AG, PT6A-67B, PT6A-67D, PT6A-67F, PT6A-67P, PT6A-67R, PT6A-67RM, PT6A-67T, PT6A-68, PT6A-68B, PT6A-68C, PT6A-68D, PT6A-68T, PT6E-67XP, and PT6E-66XT engines. The MCAI states that there has been a recent in-service report of a PT2 blade failure on a model PT6A-67 engine and two reports of PT2 blade failures during testing at the manufacturer's facility. The PT2 blade failures were contained. The manufacturer is investigating the root cause of the PT2 blade failures, but the preliminary investigation determined that the affected power turbine modules contained PT2 blades with part number 3056693-01, which were newly manufactured from the same raw material. In all cases, the PT2 blades had accumulated less than 25 hours air time since new. Transport Canada Emergency AD CF-2024-05 specifies removal of the suspect blades prior to the next flight and prohibits installation of the suspect blades. Transport Canada Emergency AD CF-2024-05 states that the corrective actions are interim actions until the root cause investigation is completed. This condition, if not addressed, could result in engine power loss or engine in-flight shut down, resulting in consequent emergency landing or reduced control of the airplane. The FAA is issuing this AD to address the unsafe condition on these products.</P>
                <P>
                    You may examine the MCAI in the AD docket at 
                    <E T="03">regulations.gov</E>
                     under Docket No. FAA-2024-0458.
                </P>
                <HD SOURCE="HD1">Related Service Information Under 1 CFR Part 51</HD>
                <P>
                    The FAA reviewed Transport Canada Emergency AD CF-2024-05, which requires replacing the affected PT2 blades. Transport Canada Emergency AD CF-2024-05 also prohibits the installation of the affected PT2 blades. This material is reasonably available because the interested parties have access to it through their normal course of business or by the means identified in 
                    <E T="02">ADDRESSES.</E>
                </P>
                <HD SOURCE="HD1">FAA's Determination</HD>
                <P>This product has been approved by the aviation authority of another country and is approved for operation in the United States. Pursuant to the FAA's bilateral agreement with this State of Design Authority, it has notified the FAA of the unsafe condition described in the MCAI and service information described above. The FAA is issuing this AD after determining that the unsafe condition described previously is likely to exist or develop in other products of the same type design.</P>
                <HD SOURCE="HD1">AD Requirements</HD>
                <P>This AD requires accomplishing the actions specified in the MCAI, except as discussed under “Differences Between this AD and the MCAI.”</P>
                <HD SOURCE="HD1">Differences Between This AD and the MCAI</HD>
                <P>The MCAI applies to P&amp;WC Model PT6A-66T, PT6A-68B, PT6A-68C, and PT6A-68T engines, but this emergency AD does not as these engines are not U.S. type-certificated.</P>
                <HD SOURCE="HD1">Interim Action</HD>
                <P>The FAA considers that this AD is an interim action. The manufacturer is currently investigating the root cause of the unsafe condition identified in this AD. If final action is later identified, the FAA might consider further rulemaking.</P>
                <HD SOURCE="HD1">Justification for Immediate Adoption and Determination of the Effective Date</HD>
                <P>
                    Section 553(b)(3)(B) of the Administrative Procedure Act (APA) (5 U.S.C. 551 
                    <E T="03">et seq.</E>
                    ) authorizes agencies to dispense with notice and comment procedures for rules when the agency, for “good cause,” finds that those procedures are “impracticable, unnecessary, or contrary to the public interest.” Under this section, an agency, upon finding good cause, may issue a final rule without providing notice and seeking comment prior to issuance. 
                    <PRTPAGE P="18352"/>
                    Further, section 553(d) of the APA authorizes agencies to make rules effective in less than thirty days, upon a finding of good cause.
                </P>
                <P>An unsafe condition exists that required the immediate adoption of Emergency AD 2024-04-51, issued on February 16, 2024, to all known U.S. owners and operators of these engines. The FAA found that the risk to the flying public justified waiving notice and comment prior to adoption of this rule because failure of the PT2 blade could result in engine power loss or engine in-flight shut down, and consequent emergency landing or reduced control of the airplane. Given the significance of the risk presented by this unsafe condition, it must be immediately addressed. Thus, the FAA has determined that the affected PT2 blades must be removed before further flight. These conditions still exist, therefore, notice and opportunity for prior public comment are impracticable and contrary to the public interest pursuant to 5 U.S.C. 553(b)(3)(B).</P>
                <P>In addition, the FAA finds that good cause exists pursuant to 5 U.S.C. 553(d) for making this amendment effective in less than 30 days, for the same reasons the FAA found good cause to forego notice and comment.</P>
                <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
                <P>The requirements of the Regulatory Flexibility Act (RFA) do not apply when an agency finds good cause pursuant to 5 U.S.C. 553 to adopt a rule without prior notice and comment. Because FAA has determined that it has good cause to adopt this rule without prior notice and comment, RFA analysis is not required.</P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>The FAA estimates that this AD affects 75 engines installed on aircraft of U.S. registry. The FAA does not know how many affected PT2 blades are installed on each engine. This cost estimate therefore reflects the cost of replacing one affected PT2 blade per engine. Replacing more than one affected PT2 blade at the same time would not incur additional labor costs.</P>
                <P>The FAA estimates the following costs to comply with this AD:</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,r75,12,12,12">
                    <TTITLE>Estimated Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Action</CHED>
                        <CHED H="1">Labor cost</CHED>
                        <CHED H="1">
                            Parts cost 
                            <LI>(average </LI>
                            <LI>pro-rated cost)</LI>
                        </CHED>
                        <CHED H="1">
                            Cost per 
                            <LI>product</LI>
                        </CHED>
                        <CHED H="1">Cost on U.S. operators</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Replace PT2 blade</ENT>
                        <ENT>8 work-hours x $85 per hour = $680</ENT>
                        <ENT>$4,001</ENT>
                        <ENT>$4,681</ENT>
                        <ENT>$351,075</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The FAA has included all known costs in its cost estimate. According to the manufacturer, however, all of the costs of this AD may be covered under warranty, thereby reducing the cost impact on affected operators.</P>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII: Aviation Programs describes in more detail the scope of the Agency's authority.</P>
                <P>The FAA is issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701: General requirements. Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>This AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>For the reasons discussed above, I certify that this AD:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866, and</P>
                <P>(2) Will not affect intrastate aviation in Alaska.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                </PART>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 39.13</SECTNO>
                    <SUBJECT> [Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>2. The FAA amends § 39.13 by adding the following new airworthiness directive:</AMDPAR>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            <E T="04">2024-04-51 Pratt &amp; Whitney Canada Corp.:</E>
                             Amendment 39-22694; Docket No. FAA-2024-0458; Project Identifier MCAI-2024-00116-E.
                        </FP>
                        <HD SOURCE="HD1">(a) Effective Date</HD>
                        <P>The FAA issued emergency Airworthiness Directive (AD) 2024-04-51 on February 16, 2024, directly to affected owners and operators. As a result of such actual notice, the emergency AD was effective for those owners and operators on the date it was received. This AD contains the same requirements as the emergency AD and, for those who did not receive actual notice, is effective on March 28, 2024.</P>
                        <HD SOURCE="HD1">(b) Affected ADs</HD>
                        <P>None.</P>
                        <HD SOURCE="HD1">(c) Applicability</HD>
                        <P>This AD applies to Pratt &amp; Whitney Canada Corp. Model PT6A-64, PT6A-66, PT6A-66A, PT6A-66B, PT6A-66D, PT6A-67, PT6A-67A, PT6A-67AF, PT6A-67AG, PT6A-67B, PT6A-67D, PT6A-67F, PT6A-67P, PT6A-67R, PT6A-67RM, PT6A-67T, PT6A-68, PT6A-68D, PT6E-67XP, and PT6E-66XT engines.</P>
                        <HD SOURCE="HD1">(d) Subject</HD>
                        <P>Joint Aircraft System Component (JASC) Code, 7250 Turbine Section.</P>
                        <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                        <P>This AD was prompted by reports from the manufacturer of the failure of second-stage power turbine (PT2) blades. The FAA is issuing this AD to prevent the failure of PT2 blades. The unsafe condition, if not addressed, could result in engine power loss or engine in-flight shut down, resulting in consequent emergency landing or reduced control of the airplane.</P>
                        <HD SOURCE="HD1">(f) Compliance</HD>
                        <P>Comply with this AD within the compliance times specified, unless already done.</P>
                        <HD SOURCE="HD1">(g) Required Actions</HD>
                        <P>
                            Except as specified in paragraph (h) of this AD: Comply with all required actions and compliance times specified in, and in 
                            <PRTPAGE P="18353"/>
                            accordance with, Transport Canada Emergency AD CF-2024-05, dated February 15, 2024 (Transport Canada Emergency AD CF-2024-05).
                        </P>
                        <HD SOURCE="HD1">(h) Exceptions to Transport Canada Emergency AD CF-2024-05</HD>
                        <P>(1) Where Transport Canada Emergency AD CF-2024-05 refers to its effective date, this AD requires using the effective date of this AD.</P>
                        <P>(2) Where Transport Canada Emergency AD CF-2024-05 refers to hours air time, this AD requires using flight hours.</P>
                        <P>(3) Where paragraph B of Transport Canada Emergency AD CF-2024-05 specifies “After the effective date of this AD,” replace that text with “As of the effective date of this AD.”</P>
                        <HD SOURCE="HD1">(i) Alternative Methods of Compliance (AMOCs)</HD>
                        <P>
                            (1) The Manager, AIR-520 Continued Operational Safety Branch, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or responsible Flight Standards Office, as appropriate. If sending information directly to the manager of the AIR-520 Continued Operational Safety Branch, send it to the attention of the person identified in paragraph (j) of this AD and email it to 
                            <E T="03">ANE-AD-AMOC@faa.gov.</E>
                        </P>
                        <P>(2) Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local Flight Standards District Office/certificate holding district office.</P>
                        <HD SOURCE="HD1">(j) Additional Information</HD>
                        <P>
                            For more information about this AD, contact Barbara Caufield, Aviation Safety Engineer, FAA, 2200 South 216th Street, Des Moines, WA 98198; phone: (781) 238-7146; email: 
                            <E T="03">barbara.caufield@faa.gov.</E>
                        </P>
                        <HD SOURCE="HD1">(k) Material Incorporated by Reference</HD>
                        <P>(1) The Director of the Federal Register approved the incorporation by reference of the service information listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.</P>
                        <P>(2) You must use this service information as applicable to do the actions required by this AD, unless the AD specifies otherwise.</P>
                        <P>(i) Transport Canada Emergency AD CF-2024-05, dated February 15, 2024.</P>
                        <P>(ii) [Reserved]</P>
                        <P>
                            (3) For Transport Canada Emergency AD CF-2024-05, contact Transport Canada, Transport Canada National Aircraft Certification, 159 Cleopatra Drive, Nepean, Ontario K1A 0N5, Canada; phone: (888) 663-3639; email: 
                            <E T="03">TC.AirworthinessDirectives-Consignesdenavigabilite.TC@tc.gc.ca;</E>
                             website: 
                            <E T="03">tc.canada.ca/en/aviation.</E>
                        </P>
                        <P>(4) You may view this service information at FAA, Airworthiness Products Section, Operational Safety Branch, 2200 South 216th Street, Des Moines, WA. For information on the availability of this material at the FAA, call (817) 222-5110.</P>
                        <P>
                            (5) You may view this material at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, visit: 
                            <E T="03">www.archives.gov/federal-register/cfr/ibr-locations</E>
                             or email: 
                            <E T="03">fr.inspection@nara.gov.</E>
                        </P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued on February 29, 2024.</DATED>
                    <NAME>Victor Wicklund,</NAME>
                    <TITLE>Deputy Director, Compliance &amp; Airworthiness Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05238 Filed 3-8-24; 11:15 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Bureau of Industry and Security</SUBAGY>
                <CFR>15 CFR Parts 740, 770, and 774</CFR>
                <DEPDOC>[Docket No. 240221-0054]</DEPDOC>
                <RIN>RIN 0694-AJ38</RIN>
                <SUBJECT>Clarification of Controls on Radiation Hardened Integrated Circuits and Expansion of License Exception GOV</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Industry and Security, Department of Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Interim final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Bureau of Industry and Security (BIS) is amending the Export Administration Regulations (EAR) to clarify controls on radiation hardened integrated circuits, including controls on computer and telecommunications equipment incorporating such radiation hardened integrated circuits. This rule also addresses certain scenarios that apply to certain integrated circuits acquired, tested, or otherwise used by or for the United States Government and affirms the availability of License Exception GOV for such items when pursuant to an official written request or directive from the Department of Defense or the Department of Energy. Lastly, this rule expands the availability of License Exception GOV for microelectronics items being exported, reexported, or transferred (in-country) in furtherance of a contract between the exporter, reexporter, or transferor and a department or agency of the U.S. Government when the contract provides for the export, reexport, transfer (in-country) of the item by the exporter, reexporter, or transferor in order to remove export control obstacles for official business of the U.S. Government, including the Department of Energy and the Department of Defense.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P/>
                    <P>
                        <E T="03">Effective date:</E>
                         This rule is effective March 13, 2024.
                    </P>
                    <P>
                        <E T="03">Comments due date:</E>
                         Comments must be received by BIS no later than April 12, 2024.
                    </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments on this rule may be submitted to the Federal rulemaking portal (
                        <E T="03">www.regulations.gov</E>
                        ). The 
                        <E T="03">regulations.gov</E>
                         ID for this rule is: BIS-2023-0038. Please refer to RIN 0694-AJ38 in all comments.
                    </P>
                    <P>All filers using the portal should use the name of the person or entity submitting the comments as the name of their files, in accordance with the instructions below. Anyone submitting business confidential information should clearly identify the business confidential portion at the time of submission, file a statement justifying nondisclosure and referring to the specific legal authority claimed, and provide a non-confidential version of the submission.</P>
                    <P>
                        For comments submitted electronically containing business confidential information, the file name of the business confidential version should begin with the characters “BC.” Any page containing business confidential information must be clearly marked “BUSINESS CONFIDENTIAL” on the top of that page. The corresponding non-confidential version of those comments must be clearly marked “PUBLIC.” The file name of the non-confidential version should begin with the character “P.” Any submissions with file names that do not begin with either a “BC” or a “P” will be assumed to be public and will be made publicly available through 
                        <E T="03">https://www.regulations.gov.</E>
                         Commenters submitting business confidential information are encouraged to scan a hard copy of the non-confidential version to create an image of the file, rather than submitting a digital copy with redactions applied, to avoid inadvertent redaction errors which could enable the public to read business confidential information.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Brian Baker, Office of National Security and Technology Transfer Controls, Bureau of Industry and Security, Phone: (202) 482-9135; Email: 
                        <E T="03">Brian.Baker@bis.doc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    Department of Defense (DOD) Leadership established the Strategic Radiation Hardened Electronics Council (SRHEC) in September, 2018 with the goal of to ensuring continued access to Strategic Radiation Hardened (SRH) and Radiation Hardened (RH) electronics and the long-term viability of the domestic infrastructure that are critical to the Nation's security and defense. In support of that effort, the Bureau of Industry and Security (BIS) is amending 
                    <PRTPAGE P="18354"/>
                    the Export Administration Regulations (EAR, 15 CFR parts 730-774) to clarify the scope of controls on radiation hardened integrated circuits, including controls on computer and telecommunications equipment incorporating such radiation hardened integrated circuits. Additionally, this rule addresses certain scenarios that apply to certain integrated circuits acquired, tested, or otherwise used by or for the United States Government and affirms the availability of License Exception GOV (15 CFR 740.11) for such items when exported, reexported, or transferred (in-country) pursuant to an official written request or directive from the Department of Defense or the Department of Energy. This rule also expands the availability of License Exception GOV for microelectronics items being exported, reexported, or transferred (in-country) in furtherance of a contract between the exporter, reexporter, and transferor and a department or agency of the U.S. Government (USG) when the contract provides for the export, reexport, or transfer (in-country) of the item by the exporter, reexporter, or transferor. This change will remove the obstacle of obtaining export authorization that currently hinders contract performance work in producing microelectronics items subject to the EAR by, for or at the direction of USG, where some exports, reexports or transfers (in-country) between onshore and offshore “development” or “production” partners may transpire.
                </P>
                <HD SOURCE="HD1">§ 740.11 License Exception GOV</HD>
                <P>This rule revises paragraph (b)(1) by adding the phrase “for or at the direction of” and adding “or the Department of Energy,” to the first sentence.</P>
                <P>
                    This rule also revises paragraph (b)(2)(iv) by adding “or the Department of Energy” to the heading of paragraph (b)(2)(iv) and “or the Department of Energy” to the same paragraph. Also, for clarification this rule adds “department or” in front of “agency of the U.S. Government. BIS was made aware that the authorization provided in paragraph (b)(2)(iv) (
                    <E T="03">i.e.,</E>
                     authorization to export, reexport or transfer (in country) items subject to the EAR pursuant to an official request or directive issued by DOD) is also needed by the Department of Energy (DOE) in order to ensure the continued availability, access and assurance of the strategic radiation hardened electronics that are critical to the nation's security and defense; therefore BIS is ensuring that authorization is available to DOE by making the revisions described.
                </P>
                <P>BIS is also adding paragraph (b)(2)(vii), to authorize the export, reexport, or transfer (in-country) of microelectronics items in furtherance of a contract between the exporter, reexporter, or transferor and a department or agency of the USG, if the contract provides for such export, reexport, or transfer (in-country) of the microelectronics item by the exporter, reexporter, or transferor. This ensures the continued availability, access, and assurance of the strategic microelectronics that are critical to the nation's security and defense.</P>
                <HD SOURCE="HD1">§ 770.2 Item Interpretations</HD>
                <P>
                    This rule revises § 770.2 to add paragraph (o) 
                    <E T="03">Interpretation 15: Certain integrated circuits acquired, tested, or otherwise used by or for the United States Government.</E>
                     This new paragraph provides the public with guidance about the classification of integrated circuits (IC) on the Commerce Control List (CCL) of supplement no. 1 to part 774 of the EAR when there is USG involvement in the fabrication of the IC, such as testing or modification requests. BIS is also adding two example scenarios to help the public understand the provisions of this new paragraph.
                </P>
                <HD SOURCE="HD1">Supplement No. 1 to Part 774—Commerce Control List</HD>
                <P>This rule revises Export Control Classification Numbers (ECCNs) 4A001, 4A101, 5A001, 6A203, and 6A999 on the CCL to add a note to the Related Controls paragraph of each of these ECCNs to explain that the act of incorporating a radiation hardened integrated circuit into commodities specified under other ECCNs on the CCL or designated as EAR99 does not, in and of itself, cause the commodity into which the radiation hardened integrated circuit is incorporated to meet the radiation hardened specifications of ECCNs 4A001.a.2, 4A101.b, 5A001.a.2, 6A203.d, or 6A999.b. For example, the incorporation of a radiation hardened integrated circuit classified under ECCN 3A001.a.1 into a computer classified under ECCN 4A994 does not, in and of itself, change the classification of the computer to ECCN 4A001.a.2.</P>
                <HD SOURCE="HD1">Export Control Reform Act of 2018</HD>
                <P>On August 13, 2018, the President signed into law the John S. McCain National Defense Authorization Act for Fiscal Year 2019, which included the Export Control Reform Act of 2018 (ECRA) (codified, as amended, at 50 U.S.C. 4801-4852). ECRA provides the legal basis for BIS's principal authorities and serves as the authority under which BIS issues this rule.</P>
                <HD SOURCE="HD1">Rulemaking Requirements</HD>
                <P>1. This interim final rule has been designated a “significant regulatory action” under Executive Order 12866.</P>
                <P>
                    2. Notwithstanding any other provision of law, no person is required to respond to, nor shall any person be subject to a penalty for failure to comply with, a collection of information subject to the requirements of the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ) (PRA), unless that collection of information displays a currently valid Office of Management and Budget (OMB) Control Number.
                </P>
                <P>This rule involves the following OMB-approved collections of information subject to the PRA:</P>
                <P>• 0694-0088, “Multi-Purpose Application,” which carries a burden hour estimate of 29.4 minutes for a manual or electronic submission;</P>
                <P>• 0694-0096, “Five Year Records Retention Period,” which carries a burden hour estimate of less than 1 minute;</P>
                <P>• 0694-0122, “Licensing Responsibilities and Enforcement;” and</P>
                <P>• 0607-0152, “Automated Export System (AES) Program,” which carries a burden hour estimate of 3 minutes per electronic submission.</P>
                <P>
                    BIS expects the burden hours associated with these collections to remain the same, because the revisions in this rule are intended to preempt future licensing delays and volume to USG programs and their industry/DIB contract performers, rather than address current license application burden. Additional information regarding these collections of information—including all background materials—can be found at 
                    <E T="03">https://www.reginfo.gov/public/do/PRAMain</E>
                     by using the search function to enter either the title of the collection or the OMB Control Number.
                </P>
                <P>3. This rule does not contain policies with federalism implications as that term is defined in Executive Order 13132.</P>
                <P>4. Pursuant to section 1762 of ECRA (50 U.S.C. 4821), this action is exempt from the Administrative Procedure Act (APA) (5 U.S.C. 553) requirements for notice of proposed rulemaking, opportunity for public participation, and delay in effective date. While section 1762 of ECRA provides sufficient authority for such an exemption, this action is also independently exempt from these APA requirements because it involves a military or foreign affairs function of the United States (5 U.S.C. 553(a)(1)).</P>
                <P>
                    5. Because a notice of proposed rulemaking and an opportunity for public comment are not required to be 
                    <PRTPAGE P="18355"/>
                    given for this rule by 5 U.S.C. 553, or by any other law, the analytical requirements of the Regulatory Flexibility Act, 5 U.S.C. 601, 
                    <E T="03">et seq.,</E>
                     are not applicable. Accordingly, no regulatory flexibility analysis is required, and none has been prepared.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>15 CFR Part 740</CFR>
                    <P>Administrative practice and procedure, Exports, Reporting and recordkeeping requirements.</P>
                    <CFR>15 CFR Part 770</CFR>
                    <P>Exports.</P>
                    <CFR>15 CFR Part 774</CFR>
                    <P>Exports, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <P>For the reasons stated in the preamble, parts 740, 770, and 774 of the Export Administration Regulations (15 CFR parts 730 through 774) are amended as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 740—LICENSE EXCEPTIONS</HD>
                </PART>
                <REGTEXT TITLE="15" PART="740">
                    <AMDPAR>1. The authority citation for part 740 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            50 U.S.C. 4801-4852; 50 U.S.C. 4601 
                            <E T="03">et seq.;</E>
                             50 U.S.C. 1701 
                            <E T="03">et seq.;</E>
                             22 U.S.C. 7201 
                            <E T="03">et seq.;</E>
                             E.O. 13026, 61 FR 58767, 3 CFR, 1996 Comp., p. 228; E.O. 13222, 66 FR 44025, 3 CFR, 2001 Comp., p. 783.
                        </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="15" PART="740">
                    <AMDPAR>2. Section 740.11 is amended by revising paragraphs (b)(1) and (b)(2)(iv), and adding paragraph (b)(2)(vii), to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 740.11 </SECTNO>
                        <SUBJECT>Governments, international organizations, international inspections under the Chemical Weapons Convention, and the International Space Station (GOV).</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>
                            (1) 
                            <E T="03">Scope.</E>
                             The provisions of this paragraph (b) authorize exports, reexports, and transfers (in-country) to personnel and agencies of the U.S. Government and certain exports by, for or at the direction of the Department of Defense or the Department of Energy. “Agency of the U.S. Government” includes all civilian and military departments, branches, missions, government-owned corporations, and other agencies of the U.S. Government but does not include such national agencies as the American Red Cross or international organizations in which the United States participates such as the Organization of American States. Therefore, shipments may not be made to these non-governmental national or international agencies, except as provided in paragraph (b)(2)(i) of this section for U.S. representatives to these organizations.
                        </P>
                        <STARS/>
                        <P>(2) * * *</P>
                        <P>
                            (iv) 
                            <E T="03">Items exported at the direction of the U.S. Department of Defense or the Department of Energy.</E>
                             This paragraph authorizes items to be exported, reexported, or transferred (in-country) pursuant to an official written request or directive from a department or agency of the U.S. Department of Defense or the Department of Energy.
                        </P>
                        <STARS/>
                        <P>(vii) This paragraph authorizes the export, reexport, or transfer (in-country) of microelectronics items in furtherance of a contract between the exporter, reexporter, or transferor and a department or agency of the U.S. Government, if the contract provides for such export, reexport, or transfer (in-country) of the microelectronics item by the exporter, reexporter, or transferor.</P>
                    </SECTION>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 770—INTERPRETATIONS</HD>
                </PART>
                <REGTEXT TITLE="15" PART="770">
                    <AMDPAR>3. The authority citation for part 770 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            50 U.S.C. 4801-4852; 50 U.S.C. 4601 
                            <E T="03">et seq.;</E>
                             50 U.S.C. 1701 
                            <E T="03">et seq.;</E>
                             E.O. 13222, 66 FR 44025, 3 CFR, 2001 Comp., p. 783.
                        </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="15" PART="770">
                    <AMDPAR>4. Section 770.2 is amended by adding paragraph (o) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 770.2 </SECTNO>
                        <SUBJECT>Item interpretations.</SUBJECT>
                        <STARS/>
                        <P>
                            (o) 
                            <E T="03">Interpretation 15: Certain integrated circuits acquired, tested, or otherwise used by or for the United States Government—</E>
                            (1) 
                            <E T="03">Classification of the integrated circuit (IC).</E>
                             Integrated circuits (ICs), including packaged “electronic assemblies” of ICs described by this section, that are manufactured using existing commercial fabrication process technologies and which are acquired, tested, or otherwise used by, for, or under contract with the United States Government (USG), are not considered to be radiation hardened (
                            <E T="03">e.g.,</E>
                             designed to withstand a specified radiation dose or upset) or temperature rated (
                            <E T="03">e.g.,</E>
                             rated to operate at prescribed temperatures) as may otherwise be specified under an Export Control Classification Number (ECCN) on the Commerce Control List (CCL) in supplement no. 1 to part 774 of the EAR, provided all of the following apply:
                        </P>
                        <P>(i) During “development”, the IC is not designed, rated, or certified (except by or for the USG) to meet the radiation or temperature specifications of any ECCN; and</P>
                        <P>(ii) All commercial testing (including by the manufacturer during fabrication, sort, packaging or assembly) regarding radiation or temperature is limited to standard commercial tools and techniques, or else by means funded or furnished by the USG for their use in the commercial setting for these specified ICs.</P>
                        <P>
                            (2) 
                            <E T="03">Activities that do not change the classification of “software” or “technology” for the commercial fabrication of ICs.</E>
                             The “development”, “production,” or subsequent use of the ICs described by this section does not change the classification of any underlying standard commercial process “software” or “technology” used to manufacture or test these ICs, provided all of the following apply:
                        </P>
                        <P>(i) Any utilized existing commercial “software” or “technology” specified under ECCNs 3D991, 3E991, 3E001, 9D515.d, 9D515.e, 9E515.d or 9E515.e does not meet the “required” standard (as defined in part 772 of the EAR) of any other ECCN on the CCL; and</P>
                        <NOTE>
                            <HD SOURCE="HED">Note 1 to paragraph (o)(2)(i):</HD>
                            <P>The use of existing commercial “software” or “technology” by or for the USG for the purposes described in paragraph (o)(1) of this section does not, in and of itself, establish the “required” standard to meet the specifications of any ECCN on the CCL.</P>
                        </NOTE>
                        <P>
                            (ii) The functional capability of the hardware, “software,” or “technology” existing within the standard commercial fabrication process has not been modified (
                            <E T="03">e.g.,</E>
                             by addition of special process steps or unique interpretation of design data), except as may be required or requested by the USG (
                            <E T="03">e.g.,</E>
                             as a stipulation of contract performance) where all of the following apply:
                        </P>
                        <P>
                            (A) The modifications do not change the ECCN of any item subject to the EAR (except to a less restrictive classification, 
                            <E T="03">e.g.,</E>
                             from an ECCN on the CCL to EAR99); and
                        </P>
                        <P>(B) The modifications are limited to the manufacture or testing of ICs by or for the USG as specified in paragraph (o)(1) of this section.</P>
                        <P>
                            (3) 
                            <E T="03">Examples.</E>
                             Scenarios addressed by this section include the following:
                        </P>
                        <P>(i) If a commercially fabricated IC specified under ECCN 3A991 is tested by the USG (or by a person or entity in a contractual relationship with the USG) and meets the radiation-hardened parameters in ECCN 3A001.a.1, the classification of the IC does not change from ECCN 3A991 and the classifications of the underlying standard process “technology”, “equipment” and “software” do not change from their original ECCNs.</P>
                        <P>
                            (ii) If a standard commercial process for fabricating ICs includes certain “technology” specified under ECCN 3E001 (
                            <E T="03">e.g.,</E>
                             for ICs specified under 
                            <PRTPAGE P="18356"/>
                            ECCN 3A001.a.1), or ECCN 9E515 (
                            <E T="03">e.g.,</E>
                             for discrete electronic components specified under ECCNs 9A515.d or .e) and those process “technologies” are used to manufacture ICs and discrete electronic components for the U.S. Government, only the portion of the “technology” that is “required” meets the specifications under ECCN 3E001 or 9E515. Moreover, the use of these standard commercial processes does not presumptively result in the control of the resulting U.S. Government ICs under ECCN paragraphs 3A001.a.1 or 9A515.d or .e; instead, the ECCNs of the U.S. Government ICs subject to the EAR would be determined according to paragraph (o)(1) of this section.
                        </P>
                        <P>
                            (iii) If a standard commercial IC fabrication process at a particular foundry is comprised of tools specified under ECCNs 3B001 or 3B991 or as EAR99, and where the “technology” is limited to “technology” specified under ECCN 3E991 or as EAR99, and that foundry (which typically produces ICs specified under ECCN 3A991 or as EAR99) were to deviate from its standard fabrication process (
                            <E T="03">e.g.,</E>
                             by adding special process steps or design features) to produce a family of ICs designed to meet or exceed the radiation hardened parameters in ECCN paragraphs 3A001.a.1 or 9A515.d. or .e and intended for sale to U.S. and non-U.S. commercial and government customers, then the ECCN of the additional process “technology” that is “required” for producing those specific radiation hardened ICs would need to be separately evaluated and determined (
                            <E T="03">e.g.,</E>
                             under ECCNs 3E001 and 9E515, as applicable).
                        </P>
                    </SECTION>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 774—THE COMMERCE CONTROL LIST</HD>
                </PART>
                <REGTEXT TITLE="15" PART="774">
                    <AMDPAR>5. The authority citation for part 774 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            50 U.S.C. 4801-4852; 50 U.S.C. 4601 
                            <E T="03">et seq.;</E>
                             50 U.S.C. 1701 
                            <E T="03">et seq.;</E>
                             10 U.S.C. 8720; 10 U.S.C. 8730(e); 22 U.S.C. 287c, 22 U.S.C. 3201 
                            <E T="03">et seq.;</E>
                             22 U.S.C. 6004; 42 U.S.C. 2139a; 15 U.S.C. 1824; 50 U.S.C. 4305; 22 U.S.C. 7201 
                            <E T="03">et seq.;</E>
                             22 U.S.C. 7210; E.O. 13026, 61 FR 58767, 3 CFR, 1996 Comp., p. 228; E.O. 13222, 66 FR 44025, 3 CFR, 2001 Comp., p. 783.
                        </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="15" PART="774">
                    <AMDPAR>6. Supplement no. 1 to part 774 is amended by revising ECCNs 4A001, 4A101, 5A001, 6A203, and 6A999, to read as follows:</AMDPAR>
                    <HD SOURCE="HD1">Supplement No. 1 to Part 774—The Commerce Control List</HD>
                    <EXTRACT>
                        <STARS/>
                        <FP SOURCE="FP-2">
                            <E T="04">4A001 Electronic computers and related equipment, having any of the following (see List of Items Controlled), and “electronic assemblies” and “specially designed” “components” therefor.</E>
                        </FP>
                        <HD SOURCE="HD1">License Requirements</HD>
                        <FP SOURCE="FP-1">
                            <E T="03">Reason for Control:</E>
                             NS, MT, AT, NP
                        </FP>
                        <GPOTABLE COLS="2" OPTS="L0,tp0,i1" CDEF="s10,r10">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1">
                                    <E T="03">Control(s)</E>
                                </CHED>
                                <CHED H="1">
                                    <E T="03">Country chart</E>
                                    <LI>
                                        <E T="03">(see Supp. No. 1</E>
                                    </LI>
                                    <LI>
                                        <E T="03">to part 738)</E>
                                    </LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">NS applies to entire entry</ENT>
                                <ENT>NS Column 2.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">MT applies to items in 4A001.a when the parameters in 4A101 are met or exceeded</ENT>
                                <ENT>MT Column 1.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">AT applies to entire entry</ENT>
                                <ENT>AT Column 1.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">NP applies, unless a License Exception is available. See § 742.3(b) of the EAR for information on applicable licensing review policies</ENT>
                                <ENT>N/A.</ENT>
                            </ROW>
                        </GPOTABLE>
                        <HD SOURCE="HD1">Reporting Requirements</HD>
                        <FP SOURCE="FP-1">See § 743.1 of the EAR for reporting requirements for exports under License Exceptions, and Validated End-User authorizations.</FP>
                        <HD SOURCE="HD1">List Based License Exceptions (See Part 740 for a Description of All License Exceptions)</HD>
                        <FP SOURCE="FP-1">
                            <E T="03">LVS:</E>
                             $5000 for 4A001.a; N/A for MT.
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">GBS:</E>
                             N/A
                        </FP>
                        <HD SOURCE="HD1">Special Conditions for STA</HD>
                        <FP SOURCE="FP-1">
                            <E T="03">STA:</E>
                             License Exception STA may not be used to ship any commodity in 4A001.a.2 to any of the destinations listed in Country Group A:6 (See Supplement No.1 to part 740 of the EAR).
                        </FP>
                        <HD SOURCE="HD1">List of Items Controlled</HD>
                        <FP SOURCE="FP-1">
                            <E T="03">Related Controls:</E>
                             (1) See also 4A101 and 4A994. Equipment designed or rated for transient ionizing radiation is “subject to the ITAR” (see 22 CFR parts 120 through 130). (2) The act of incorporating a radiation hardened integrated circuit into a computer that is specified under ECCN 4A994 or designated as EAR99 does not, in and of itself, cause the computer to meet the parameters of ECCN paragraph 4A001.a.2.
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">Related Definitions:</E>
                             For the purposes of integrated circuits in 4A001.a.2, 5 × 10
                            <SU>3</SU>
                             Gy(Si) = 5 × 10
                            <SU>5</SU>
                             Rads (Si); 5 × 10
                            <SU>6</SU>
                             Gy (Si)/s = 5 × 10
                            <SU>8</SU>
                             Rads (Si)/s.
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">Items:</E>
                        </FP>
                        <P>a. “Specially designed” to have any of the following:</P>
                        <P>a.1. [Reserved]</P>
                        <P>a.2. Radiation hardened to exceed any of the following specifications:</P>
                        <P>
                            a.2.a. A total dose of 5 × 10
                            <SU>3</SU>
                             Gy (Si);
                        </P>
                        <P>
                            a.2.b. A dose rate upset of 5 × 10
                            <SU>6</SU>
                             Gy (Si)/s; or
                        </P>
                        <P>
                            a.2.c. Single Event Upset of 1 × 10
                            <E T="51">−</E>
                            <SU>8</SU>
                             Error/bit/day;
                        </P>
                        <P>
                            <E T="04">Note:</E>
                              
                            <E T="03">4A001.a.2 does not apply to computers “specially designed” for “civil aircraft” applications.</E>
                        </P>
                        <P>b. [Reserved]</P>
                        <STARS/>
                        <FP SOURCE="FP-2">
                            <E T="04">4A101 Analog computers, “digital computers” or digital differential analyzers, other than those controlled by 4A001 designed or modified for use in “missiles”, having any of the following (see List of Items Controlled).</E>
                        </FP>
                        <HD SOURCE="HD1">License Requirements</HD>
                        <FP SOURCE="FP-1">
                            <E T="03">Reason for Control:</E>
                             MT, AT
                        </FP>
                        <GPOTABLE COLS="2" OPTS="L0,tp0,i1" CDEF="s10,r10">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1">
                                    <E T="03">Control(s)</E>
                                </CHED>
                                <CHED H="1">
                                    <E T="03">Country chart</E>
                                    <LI>
                                        <E T="03">(see Supp. No. 1</E>
                                    </LI>
                                    <LI>
                                        <E T="03">to part 738)</E>
                                    </LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">MT applies to entire entry</ENT>
                                <ENT>MT Column 1.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">AT applies to entire entry</ENT>
                                <ENT>AT Column 1.</ENT>
                            </ROW>
                        </GPOTABLE>
                        <HD SOURCE="HD1">List Based License Exceptions (See Part 740 for a Description of All License Exceptions)</HD>
                        <FP SOURCE="FP-1">
                            <E T="03">LVS:</E>
                             N/A
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">GBS:</E>
                             N/A
                        </FP>
                        <HD SOURCE="HD1">List of Items Controlled</HD>
                        <FP SOURCE="FP-1">
                            <E T="03">Related Controls:</E>
                             The act of incorporating a radiation hardened integrated circuit into a computer that is specified under ECCN 4A994 or designated as EAR99 does not, in and of itself, cause the computer to meet the parameters of ECCN paragraph 4A101.b.
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">Related Definitions:</E>
                             N/A
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">Items:</E>
                        </FP>
                        <P>
                            a. Rated for continuous operation at temperatures from below 228 K (−45 °C) to above 328 K (+55 °C); 
                            <E T="03">or</E>
                        </P>
                        <P>b. Designed as ruggedized or `radiation hardened'.</P>
                        <P>
                            <E T="04">Note:</E>
                              
                            <E T="03">
                                For the purposes of 4A101,`radiation hardened' means that the “part,” “component” or equipment is designed or rated to withstand radiation levels which meet or exceed a total irradiation dose of 5 × 10
                                <SU>5</SU>
                                 rads (Si).
                            </E>
                        </P>
                        <STARS/>
                        <FP SOURCE="FP-2">
                            <E T="04">5A001 Telecommunications systems, equipment, “components” and “accessories,” as follows (see List of Items Controlled).</E>
                        </FP>
                        <HD SOURCE="HD1">License Requirements</HD>
                        <FP SOURCE="FP-1">
                            <E T="03">Reason for Control:</E>
                             NS, SL, AT
                        </FP>
                        <GPOTABLE COLS="2" OPTS="L0,tp0,i1" CDEF="s10,r10">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1">
                                    <E T="03">Control(s)</E>
                                </CHED>
                                <CHED H="1">
                                    <E T="03">Country chart</E>
                                      
                                    <LI>
                                        <E T="03">(see Supp. No.1</E>
                                          
                                    </LI>
                                    <LI>
                                        <E T="03">to part 738)</E>
                                    </LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">NS applies to 5A001.a, b.5, .e, .f.3 and .h</ENT>
                                <ENT>NS Column 1.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">NS applies to 5A001.b (except .b.5), .c, .d, .f (except f.3), .g, and .j</ENT>
                                <ENT>NS Column 2.</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="18357"/>
                                <ENT I="01">SL applies to 5A001.f.1</ENT>
                                <ENT>
                                    A license is required for all destinations, as specified in § 742.13 of the EAR. Accordingly, a column specific to this control does not appear on the Commerce Country Chart (Supplement No. 1 to Part 738 of the EAR).
                                    <LI>
                                        <E T="02">Note to SL paragraph:</E>
                                          
                                        <E T="03">This licensing requirement does not supersede, nor does it implement, construe or limit the scope of any criminal statute, including, but not limited to the Omnibus Safe Streets Act of 1968, as amended</E>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">AT applies to entire entry</ENT>
                                <ENT>AT Column 1.</ENT>
                            </ROW>
                        </GPOTABLE>
                        <HD SOURCE="HD1">Reporting Requirements</HD>
                        <FP SOURCE="FP-1">See § 743.1 of the EAR for reporting requirements for exports under License Exceptions, and Validated End-User authorizations.</FP>
                        <HD SOURCE="HD1">List Based License Exceptions (See Part 740 for a Description of All License Exceptions)</HD>
                        <FP SOURCE="FP-1">
                            <E T="03">LVS:</E>
                             N/A for 5A001.a, b.5, .e, f.3 and .h; $5000 for 5A001.b.1, .b.2, .b.3, .b.6, .d, f.2, f.4, and .g; $3000 for 5A001.c.
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">GBS:</E>
                             Yes, except 5A001.a, b.5, e, and h.
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">ACE:</E>
                             Yes for 5A001.j, except to Country Group E:1 or E:2. See § 740.22 of the EAR for eligibility criteria.
                        </FP>
                        <HD SOURCE="HD1">Special Conditions for STA</HD>
                        <FP SOURCE="FP-1">
                            <E T="03">STA:</E>
                             License Exception STA may not be used to ship any commodity in 5A001.j to any of the destinations listed in Country Group A:5 or A:6 (See Supplement No. 1 to part 740 of the EAR), or any commodity in 5A001.b.3, .b.5 or .h to any of the destinations listed in Country Group A:6 (See Supplement No.1 to part 740 of the EAR).
                        </FP>
                        <HD SOURCE="HD1">List of Items Controlled</HD>
                        <FP SOURCE="FP-1">
                            <E T="03">Related Controls:</E>
                             (1) See USML Category XI for controls on direction-finding “equipment” including types of “equipment” in ECCN 5A001.e and any other military or intelligence electronic “equipment” that is “subject to the ITAR.” (2) See USML Category XI(a)(4)(iii) for controls on electronic attack and jamming “equipment” defined in 5A001.f and .h that are subject to the ITAR. (3) The act of incorporating a radiation hardened integrated circuit into telecommunications equipment that is specified under ECCN 5A991 or designated as EAR99 does not, in and of itself, cause the telecommunications equipment to meet the specifications of ECCN paragraph 5A001.a.2. (4) See also ECCNs 5A101, 5A980, and 5A991.
                        </FP>
                        <P>a. Any type of telecommunications equipment having any of the following characteristics, functions or features:</P>
                        <P>a.1. “Specially designed” to withstand transitory electronic effects or electromagnetic pulse effects, both arising from a nuclear explosion;</P>
                        <P>a.2. Specially hardened to withstand gamma, neutron or ion radiation;</P>
                        <P>
                            a.3. “Specially designed” to operate below 218 K (−55 °C); 
                            <E T="03">or</E>
                        </P>
                        <P>a.4. “Specially designed” to operate above 397 K (124 °C);</P>
                        <P>
                            <E T="04">Note:</E>
                              
                            <E T="03">5A001.a.3 and 5A001.a.4 apply only to electronic equipment.</E>
                        </P>
                        <P>b. Telecommunication systems and equipment, and “specially designed” “components” and “accessories” therefor, having any of the following characteristics, functions or features:</P>
                        <P>b.1 Being underwater untethered communications systems having any of the following:</P>
                        <P>b.1.a. An acoustic carrier frequency outside the range from 20 kHz to 60 kHz;</P>
                        <P>
                            b.1.b. Using an electromagnetic carrier frequency below 30 kHz; 
                            <E T="03">or</E>
                        </P>
                        <P>
                            b.1.c. Using electronic beam steering techniques; 
                            <E T="03">or</E>
                        </P>
                        <P>b.1.d. Using “lasers” or light-emitting diodes (LEDs), with an output wavelength greater than 400 nm and less than 700 nm, in a “local area network”;</P>
                        <P>b.2. Being radio equipment operating in the 1.5 MHz to 87.5 MHz band and having all of the following:</P>
                        <P>
                            b.2.a.. Automatically predicting and selecting frequencies and “total digital transfer rates” per channel to optimize the transmission; 
                            <E T="03">and</E>
                        </P>
                        <P>b.2.b. Incorporating a linear power amplifier configuration having a capability to support multiple signals simultaneously at an output power of 1 kW or more in the frequency range of 1.5 MHz or more but less than 30 MHz, or 250 W or more in the frequency range of 30 MHz or more but not exceeding 87.5 MHz, over an “instantaneous bandwidth” of one octave or more and with an output harmonic and distortion content of better than −80 dB;</P>
                        <P>b.3. Being radio equipment employing “spread spectrum” techniques, including “frequency hopping” techniques, not controlled in 5A001.b.4 and having any of the following:</P>
                        <P>
                            b.3.a. User programmable spreading codes; 
                            <E T="03">or</E>
                        </P>
                        <P>b.3.b. A total transmitted bandwidth which is 100 or more times the bandwidth of any one information channel and in excess of 50 kHz;</P>
                        <P>
                            <E T="04">Note:</E>
                              
                            <E T="03">5A001.b.3.b does not control radio equipment “specially designed” for use with any of the following:</E>
                        </P>
                        <P>
                            <E T="03">a. Civil cellular radio-communications systems; or</E>
                        </P>
                        <P>
                            <E T="03">b. Fixed or mobile satellite Earth stations for commercial civil telecommunications.</E>
                        </P>
                        <P>
                            <E T="04">Note:</E>
                              
                            <E T="03">5A001.b.3 does not control equipment operating at an output power of 1 W or less.</E>
                        </P>
                        <P>b.4. Being radio equipment employing ultra-wideband modulation techniques, having user programmable channelizing codes, scrambling codes, or network identification codes and having any of the following:</P>
                        <P>
                            b.4.a. A bandwidth exceeding 500 MHz; 
                            <E T="03">or</E>
                        </P>
                        <P>b.4.b. A “fractional bandwidth” of 20% or more;</P>
                        <P>b.5. Being digitally controlled radio receivers having all of the following:</P>
                        <P>b.5.a. More than 1,000 channels;</P>
                        <P>b.5.b. A `channel switching time' of less than 1 ms;</P>
                        <P>
                            b.5.c. Automatic searching or scanning of a part of the electromagnetic spectrum; 
                            <E T="03">and</E>
                        </P>
                        <P>
                            b.5.d. Identification of the received signals or the type of transmitter; 
                            <E T="03">or</E>
                        </P>
                        <P>
                            <E T="04">Note:</E>
                              
                            <E T="03">5A001.b.5 does not control radio equipment “specially designed” for use with civil cellular radio-communications systems.</E>
                        </P>
                        <P>
                            <E T="04">Technical Note:</E>
                              
                            <E T="03">For the purposes of 5A001.b.5.b, `channel switching time' means the time (i.e., delay) to change from one receiving frequency to another, to arrive at or within ±0.05% of the final specified receiving frequency. Items having a specified frequency range of less than ±0.05% around their center frequency are defined to be incapable of channel frequency switching.</E>
                        </P>
                        <P>b.6. Employing functions of digital “signal processing” to provide 'voice coding' output at rates of less than 700 bit/s.</P>
                        <P>
                            <E T="04">Technical Notes:</E>
                        </P>
                        <P>
                            <E T="03">1. For variable rate ‘voice coding', 5A001.b.6 applies to the ‘voice coding' output of continuous speech.</E>
                        </P>
                        <P>
                            <E T="03">2. For the purposes of 5A001.b.6, `voice coding' is defined as the technique to take samples of human voice and then convert these samples of human voice into a digital signal taking into account specific characteristics of human speech.</E>
                        </P>
                        <P>
                            c. Optical fibers of more than 500 m in length and specified by the manufacturer as being capable of withstanding a `proof test' tensile stress of 2 × 10
                            <SU>9</SU>
                             N/m
                            <SU>2</SU>
                             or more;
                        </P>
                        <P>
                            <E T="04">N.B.:</E>
                              
                            <E T="03">For underwater umbilical cables, see 8A002.a.3.</E>
                        </P>
                        <P>
                            <E T="04">Technical Note:</E>
                              
                            <E T="03">For the purposes of 5A001.c, `proof test' is the on-line or off-line production screen testing that dynamically applies a prescribed tensile stress over a 0.5 to 3 m length of fiber at a running rate of 2 to 5 m/s while passing between capstans approximately 150 mm in diameter. The ambient temperature is a nominal 293 K (20 °C) and relative humidity 40%. Equivalent national standards may be used for executing the proof test.</E>
                        </P>
                        <P>d. “Electronically steerable phased array antennae” as follows:</P>
                        <P>d.1. Rated for operation above 31.8 GHz, but not exceeding 57 GHz, and having an Effective Radiated Power (ERP) equal to or greater than +20 dBm (22.15 dBm Effective Isotropic Radiated Power (EIRP));</P>
                        <P>d.2. Rated for operation above 57 GHz, but not exceeding 66 GHz, and having an ERP equal to or greater than +24 dBm (26.15 dBm EIRP);</P>
                        <P>d.3. Rated for operation above 66 GHz, but not exceeding 90 GHz, and having an ERP equal to or greater than +20 dBm (22.15 dBm EIRP);</P>
                        <P>d.4. Rated for operation above 90 GHz;</P>
                        <P>
                            <E T="04">Note 1:</E>
                              
                            <E T="03">
                                5A001.d does not control `electronically steerable phased array 
                                <PRTPAGE P="18358"/>
                                antennae' for landing systems with instruments meeting ICAO standards covering Microwave Landing Systems (MLS).
                            </E>
                        </P>
                        <P>
                            <E T="04">Note 2:</E>
                              
                            <E T="03">5A001.d does not apply to antennae “specially designed” for any of the following:</E>
                        </P>
                        <P>
                            <E T="03">a. Civil cellular or WLAN radio-communications systems;</E>
                        </P>
                        <P>
                            <E T="03">b. IEEE 802.15 or wireless HDMI; or</E>
                        </P>
                        <P>
                            <E T="03">c. Fixed or mobile satellite earth stations for commercial civil telecommunications.</E>
                        </P>
                        <P>
                            <E T="04">Technical Note:</E>
                              
                            <E T="03">For the purposes of 5A001.d, `electronically steerable phased array antenna' is an antenna which forms a beam by means of phase coupling, (i.e., the beam direction is controlled by the complex excitation coefficients of the radiating elements) and the direction of that beam can be varied (both in transmission and reception) in azimuth or in elevation, or both, by application of an electrical signal.</E>
                        </P>
                        <P>e. Radio direction finding equipment operating at frequencies above 30 MHz and having all of the following, and “specially designed” “components” therefor:</P>
                        <P>e.1. “Instantaneous bandwidth” of 10 MHz or more; and</P>
                        <P>e.2. Capable of finding a Line Of Bearing (LOB) to non-cooperating radio transmitters with a signal duration of less than 1 ms;</P>
                        <P>f. Mobile telecommunications interception or jamming equipment, and monitoring equipment therefor, as follows, and “specially designed” “components” therefor:</P>
                        <P>f.1. Interception equipment designed for the extraction of voice or data, transmitted over the air interface;</P>
                        <P>
                            f.2. Interception equipment not specified in 5A001.f.1, designed for the extraction of client device or subscriber identifiers (
                            <E T="03">e.g.,</E>
                             IMSI, TIMSI or IMEI), signaling, or other metadata transmitted over the air interface;
                        </P>
                        <P>f.3. Jamming equipment “specially designed” or modified to intentionally and selectively interfere with, deny, inhibit, degrade or seduce mobile telecommunication services and performing any of the following:</P>
                        <P>f.3.a. Simulate the functions of Radio Access Network (RAN) equipment;</P>
                        <P>
                            f.3.b. Detect and exploit specific characteristics of the mobile telecommunications protocol employed (
                            <E T="03">e.g.,</E>
                             GSM); 
                            <E T="03">or</E>
                        </P>
                        <P>
                            f.3.c. Exploit specific characteristics of the mobile telecommunications protocol employed (
                            <E T="03">e.g.,</E>
                             GSM);
                        </P>
                        <P>f.4. Radio Frequency (RF) monitoring equipment designed or modified to identify the operation of items specified in 5A001.f.1, 5A001.f.2 or 5A001.f.3.</P>
                        <P>
                            <E T="04">Note:</E>
                              
                            <E T="03">5A001.f.1 and 5A001.f.2 do not apply to any of the following:</E>
                        </P>
                        <P>
                            <E T="03">a. Equipment “specially designed” for the interception of analog Private Mobile Radio (PMR), IEEE 802.11 WLAN;</E>
                        </P>
                        <P>
                            <E T="03">b. Equipment designed for mobile telecommunications network operators; or</E>
                        </P>
                        <P>
                            <E T="03">c. Equipment designed for the “development” or “production” of mobile telecommunications equipment or systems.</E>
                        </P>
                        <P>
                            <E T="04">N.B. 1:</E>
                              
                            <E T="03">See also the International Traffic in Arms Regulations (ITAR) (22 CFR parts 120-130). For items specified by 5A001.f.1 (including as previously specified by 5A001.i), see also 5A980 and the U.S. Munitions List (22 CFR part 121).</E>
                        </P>
                        <P>
                            <E T="04">N.B. 2:</E>
                              
                            <E T="03">For radio receivers see 5A001.b.5.</E>
                        </P>
                        <P>g. Passive Coherent Location (PCL) systems or equipment, “specially designed” for detecting and tracking moving objects by measuring reflections of ambient radio frequency emissions, supplied by non-radar transmitters.</P>
                        <P>
                            <E T="04">Technical Note:</E>
                              
                            <E T="03">For the purposes of 5A001.g, non-radar transmitters may include commercial radio, television or cellular telecommunications base stations.</E>
                        </P>
                        <P>
                            <E T="04">Note:</E>
                              
                            <E T="03">5A001.g. does not control:</E>
                        </P>
                        <P>
                            <E T="03">a. Radio-astronomical equipment; or</E>
                        </P>
                        <P>
                            <E T="03">b. Systems or equipment, that require any radio transmission from the target.</E>
                        </P>
                        <P>h. Counter Improvised Explosive Device (IED) equipment and related equipment, as follows:</P>
                        <P>h.1. Radio Frequency (RF) transmitting equipment, not specified by 5A001.f, designed or modified for prematurely activating or preventing the initiation of Improvised Explosive Devices (IEDs);</P>
                        <P>h.2. Equipment using techniques designed to enable radio communications in the same frequency channels on which co-located equipment specified by 5A001.h.1 is transmitting.</P>
                        <P>
                            <E T="04">N.B.:</E>
                              
                            <E T="03">See also Category XI of the International Traffic in Arms Regulations (ITAR) (22 CFR parts 120-130).</E>
                        </P>
                        <P>i. [Reserved]</P>
                        <P>
                            <E T="04">N.B.:</E>
                              
                            <E T="03">See 5A001.f.1 for items previously specified by 5A001.i.</E>
                        </P>
                        <P>j. IP network communications surveillance systems or equipment, and “specially designed” components therefor, having all of the following:</P>
                        <P>
                            j.1. Performing all of the following on a carrier class IP network (
                            <E T="03">e.g.,</E>
                             national grade IP backbone):
                        </P>
                        <P>
                            j.1.a. Analysis at the application layer (
                            <E T="03">e.g.,</E>
                             Layer 7 of Open Systems Interconnection (OSI) model (ISO/IEC 7498-1));
                        </P>
                        <P>
                            j.1.b. Extraction of selected metadata and application content (
                            <E T="03">e.g.,</E>
                             voice, video, messages, attachments); 
                            <E T="03">and</E>
                        </P>
                        <P>
                            j.1.c. Indexing of extracted data; 
                            <E T="03">and</E>
                        </P>
                        <P>j.2. Being “specially designed” to carry out all of the following:</P>
                        <P>
                            j.2.a. Execution of searches on the basis of “hard selectors”; 
                            <E T="03">and</E>
                        </P>
                        <P>j.2.b. Mapping of the relational network of an individual or of a group of people.</P>
                        <P>
                            <E T="04">Note:</E>
                              
                            <E T="03">5A001.j does not apply to “systems” or “equipment”, “specially designed” for any of the following:</E>
                        </P>
                        <P>
                            <E T="03">a. Marketing purpose;</E>
                        </P>
                        <P>
                            <E T="03">b. Network Quality of Service (QoS); or</E>
                        </P>
                        <P>
                            <E T="03">c. Quality of Experience (QoE).</E>
                        </P>
                        <P>
                            <E T="04">N.B.:</E>
                              
                            <E T="03">See also the International Traffic in Arms Regulations (ITAR) (22 CFR parts 120-130). Defense articles described in USML Category XI(b) are “subject to the ITAR.”</E>
                        </P>
                        <STARS/>
                        <FP SOURCE="FP-2">
                            <E T="04">6A203 High-speed cameras, imaging devices and “components” therefor, other than those controlled by 6A003 (see List of Items Controlled).</E>
                        </FP>
                        <HD SOURCE="HD1">License Requirements</HD>
                        <FP SOURCE="FP-1">
                            <E T="03">Reason for Control:</E>
                             NP, AT
                        </FP>
                        <GPOTABLE COLS="2" OPTS="L0,tp0,i1" CDEF="s10,r10">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1">
                                    <E T="03">Control(s)</E>
                                </CHED>
                                <CHED H="1">
                                    <E T="03">Country chart</E>
                                      
                                    <LI>
                                        <E T="03">(see Supp. No. 1</E>
                                          
                                    </LI>
                                    <LI>
                                        <E T="03">to part 738)</E>
                                    </LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">NP applies to entire entry </ENT>
                                <ENT>NP Column 1.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">AT applies to entire entry </ENT>
                                <ENT>AT Column 1.</ENT>
                            </ROW>
                        </GPOTABLE>
                        <HD SOURCE="HD1">List Based License Exceptions (See Part 740 for a Description of All License Exceptions)</HD>
                        <P>
                            <E T="03">LVS:</E>
                             N/A
                        </P>
                        <P>
                            <E T="03">GBS:</E>
                             N/A
                        </P>
                        <HD SOURCE="HD1">List of Items Controlled</HD>
                        <FP SOURCE="FP-1">
                            <E T="03">Related Controls:</E>
                             (1) See ECCNs 6E001 (“development”), 6E002 (“production”), and 6E201 (“use”) for technology for items controlled under this entry. (2) Also see ECCN 6A003.a.3 and a.4. (3) The act of incorporating a radiation hardened integrated circuit into a TV camera designated as EAR99 does not, in and of itself, cause the TV camera to meet the parameters of ECCN paragraph 6A203.d.
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">Related Definitions:</E>
                             N/A
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">Items:</E>
                        </FP>
                        <P>a. Streak cameras and “specially designed” components therefor, as follows:</P>
                        <P>a.1. Streak cameras with writing speeds greater than 0.5 mm/µs;</P>
                        <P>a.2. Electronic streak cameras capable of 50 ns or less time resolution;</P>
                        <P>a.3. Streak tubes for cameras described in 6A203.a.2;</P>
                        <P>a.4. Plug-ins, “specially designed” for use with streak cameras having modular structures, that enable the performance characteristics described in 6A203.a.1 or .a.2;</P>
                        <P>a.5. Synchronizing electronics units, and rotor assemblies consisting of turbines, mirrors and bearings, that are “specially designed” for cameras described in 6A203.a.1.</P>
                        <P>b. Framing cameras and “specially designed” components therefor, as follows:</P>
                        <P>b.1. Framing cameras with recording rates greater than 225,000 frames per second;</P>
                        <P>b.2. Framing cameras capable of 50 ns or less frame exposure time;</P>
                        <P>b.3. Framing tubes, and solid-state imaging devices, that have a fast image gating (shutter) time of 50 ns or less and are “specially designed” for cameras described in 6A203.b.1 or .b.2;</P>
                        <P>b.4. Plug-ins, “specially designed” for use with framing cameras having modular structures, that enable the performance characteristics described in 6A203.b.1 or .b.2;</P>
                        <P>b.5. Synchronizing electronic units, and rotor assemblies consisting of turbines, mirrors and bearings, that are “specially designed” for cameras described in 6A203.b.1 or .b.2.</P>
                        <P>c. Solid-state or electron tube cameras and “specially designed” components therefor, as follows:</P>
                        <P>c.1. Solid-state cameras, or electron tube cameras, with a fast image gating (shutter) time of 50 ns or less;</P>
                        <P>
                            c.2. Solid-state imaging devices, and image intensifiers tubes, that have a fast image gating (shutter) time of 50 ns or less and are “specially designed” for cameras described in 6A203.c.1;
                            <PRTPAGE P="18359"/>
                        </P>
                        <P>c.3. Electro-optical shuttering devices (Kerr or Pockels cells) with a fast image gating (shutter) time of 50 ns or less;</P>
                        <P>c.4. Plug-ins, “specially designed” for use with cameras having modular structures, that enable the performance characteristics described in 6A203.c.1.</P>
                        <P>
                            <E T="04">Technical Note:</E>
                              
                            <E T="03">High speed single frame cameras can be used alone to produce a single image of a dynamic event, or several such cameras can be combined in a sequentially-triggered system to produce multiple images of an event.</E>
                        </P>
                        <P>
                            d. Radiation-hardened TV cameras, or lenses therefor, “specially designed” or rated as radiation hardened to withstand a total radiation dose greater than 5 × 10 
                            <SU>4</SU>
                             Gy (silicon) without operational degradation.
                        </P>
                        <P>
                            <E T="04">Technical Note:</E>
                              
                            <E T="03">The term Gy (silicon) refers to the energy in Joules per kilogram absorbed by an unshielded silicon sample when exposed to ionizing radiation.</E>
                        </P>
                        <STARS/>
                        <FP SOURCE="FP-2">
                            <E T="04">6A999 Specific processing equipment, as follows (see List of Items Controlled).</E>
                        </FP>
                        <HD SOURCE="HD1">License Requirements</HD>
                        <FP SOURCE="FP-1">
                            <E T="03">Reason for Control:</E>
                             RS AT
                        </FP>
                        <GPOTABLE COLS="2" OPTS="L0,tp0,i1" CDEF="s10,r10">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1">
                                    <E T="03">Control(s)</E>
                                </CHED>
                                <CHED H="1">
                                    <E T="03">Country chart (see Supp. No. 1 to part 738)</E>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">RS applies to 6A999.c</ENT>
                                <ENT>RS Column 2.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">AT applies to entire entry</ENT>
                                <ENT>A license is required for items controlled by this entry to North Korea for anti-terrorism reasons. The Commerce Country Chart is not designed to determine AT licensing requirements for this entry. See § 742.19 of the EAR for additional information.</ENT>
                            </ROW>
                        </GPOTABLE>
                        <HD SOURCE="HD1">List Based License Exceptions (See Part 740 for a Description of All License Exceptions)</HD>
                        <FP SOURCE="FP-1">
                            <E T="03">LVS:</E>
                             N/A
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">GBS:</E>
                             N/A
                        </FP>
                        <HD SOURCE="HD1">List of Items Controlled</HD>
                        <FP SOURCE="FP-1">
                            <E T="03">Related Controls:</E>
                             (1) The act of incorporating a radiation hardened integrated circuit into a TV camera designated as EAR99 does not, in and of itself, cause the TV camera to meet the specifications of ECCN paragraph 6A999.b. (2) See also 6A203.
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">Related Definitions:</E>
                             N/A
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">Items:</E>
                        </FP>
                        <P>a. Seismic detection equipment not controlled in paragraph c.</P>
                        <P>b. Radiation hardened TV cameras, n.e.s.</P>
                        <P>c. Seismic intrusion detection systems that detect, classify and determine the bearing on the source of a detected signal.</P>
                        <STARS/>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <NAME>Thea D. Rozman Kendler,</NAME>
                    <TITLE>Assistant Secretary for Export Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05267 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-33-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Indian Affairs</SUBAGY>
                <CFR>25 CFR Parts 140, 141, 211, 213, 225, 226, 227, 243, 249, 273, and 700</CFR>
                <DEPDOC>[245A2100DD/AAKC001030/A0A501010.999900253G]</DEPDOC>
                <RIN>RIN 1076-AF75</RIN>
                <SUBJECT>Civil Penalties Inflation Adjustments; Annual Adjustments</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Indian Affairs, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This rule provides for annual adjustments to the level of civil monetary penalties contained in Bureau of Indian Affairs (Bureau) regulations to account for inflation under the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015 and Office of Management and Budget (OMB) guidance.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective on March 13, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         This rule may be found on the internet at 
                        <E T="03">https://www.regulations.gov</E>
                         by entering “RIN 1076-AF75” in the search box.
                    </P>
                    <P>
                        • 
                        <E T="03">Alternative Format:</E>
                         On request to the program contact person listed under 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        , individuals can obtain this document in an alternate format, usable by people with disabilities, at the Office of the Assistant Secretary—Indian Affairs, Room 4660, 1849 C Street NW, Washington, DC 20240.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Oliver Whaley, Director, Office of Regulatory Affairs and Collaborative Action (RACA), Office of the Assistant Secretary—Indian Affairs; Department of the Interior, 
                        <E T="03">RACA@bia.gov;</E>
                         telephone (202) 738-6065. 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.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. Background</FP>
                    <FP SOURCE="FP-2">II. Calculation of Annual Adjustments</FP>
                    <FP SOURCE="FP-2">III. Procedural Requirements</FP>
                    <FP SOURCE="FP1-2">A. Regulatory Planning and Review (E.O. 12866, 14094 and 13563)</FP>
                    <FP SOURCE="FP1-2">B. Reducing Regulation and Controlling Regulatory Costs (E.O. 13771)</FP>
                    <FP SOURCE="FP1-2">C. Regulatory Flexibility Act</FP>
                    <FP SOURCE="FP1-2">D. Congressional Review Act (CRA)</FP>
                    <FP SOURCE="FP1-2">E. Unfunded Mandates Reform Act</FP>
                    <FP SOURCE="FP1-2">F. Takings (E.O. 12630)</FP>
                    <FP SOURCE="FP1-2">G. Federalism (E.O. 13132)</FP>
                    <FP SOURCE="FP1-2">H. Civil Justice Reform (E.O. 12988)</FP>
                    <FP SOURCE="FP1-2">I. Consultation With Indian Tribes (E.O. 13175)</FP>
                    <FP SOURCE="FP1-2">J. Paperwork Reduction Act</FP>
                    <FP SOURCE="FP1-2">K. National Environmental Policy Act</FP>
                    <FP SOURCE="FP1-2">L. Effects on the Energy Supply (E.O. 13211)</FP>
                    <FP SOURCE="FP1-2">M. Clarity of This Regulation</FP>
                    <FP SOURCE="FP1-2">N. Administrative Procedure Act</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Background</HD>
                <P>On November 2, 2015, the President signed into law the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015 (sec. 701 of Pub. L. 114-74) (“the Act”). The Act requires Federal agencies to adjust the level of civil monetary penalties with an initial “catch-up” adjustment through rulemaking and then make subsequent annual adjustments for inflation. The purpose of these adjustments is to maintain the deterrent effect of civil penalties and to further the policy goals of the underlying statutes.</P>
                <P>
                    The Office of Management and Budget (OMB) issued guidance for Federal agencies on calculating the catch-up adjustment. 
                    <E T="03">See</E>
                     February 24, 2016, Memorandum for the Heads of Executive Departments and Agencies, from Shaun Donovan, Director, Office of Management and Budget, re: 
                    <E T="03">Implementation of the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015</E>
                     (M-16-06). Under the guidance, the Department identified applicable civil monetary penalties and calculated the catch-up adjustment. A civil monetary penalty is any assessment with a dollar amount that is levied for a violation of a Federal civil statute or regulation, and is assessed or enforceable through a civil action in Federal court or an administrative proceeding. A civil monetary penalty does not include a penalty levied for violation of a criminal statute, or fees for services, licenses, permits, or other regulatory review. The calculated catch-up adjustment is based on the percent change between the Consumer Price Index for all Urban Consumers (CPI-U) for the month of October in the year of the previous adjustment (or in the year of establishment, if no adjustment has been made) and the October 2015 CPI-U.
                    <PRTPAGE P="18360"/>
                </P>
                <P>The Bureau issued an interim final rule providing for calculated catch-up adjustments on June 30, 2016 (81 FR 42478), with an effective date of August 1, 2016, and requesting comments post-promulgation. The Bureau issued a final rule affirming the catch-up adjustments set forth in the interim final rule on December 2, 2016 (81 FR 86953). The Bureau then issued a final rule making the next scheduled annual inflation adjustment for 2017 on January 23, 2017 (82 FR 7649), for 2018 on February 6, 2018 (83 FR 5192), for 2019 on April 15, 2019 (84 FR 15098), for 2020 on February 19, 2020 (85 FR 9366), for 2021 on January 28, 2021 (86 FR 7344), for 2022 on March 9, 2022 (87 FR 13153), and for 2023 on March 2, 2023 (88 FR 13018).</P>
                <HD SOURCE="HD1">II. Calculation of 2024 Annual Adjustments</HD>
                <P>
                    OMB recently issued guidance to assist Federal agencies in implementing the annual adjustments required by the Act, which agencies must complete by January 15, 2024. 
                    <E T="03">See</E>
                     December 19, 2023, Memorandum for the Heads of Executive Departments and Agencies, from Shalanda D. Young, Director, Office of Management and Budget, re: 
                    <E T="03">Implementation of Penalty Inflation Adjustments for 2024, Pursuant to the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015</E>
                     (M-24-07). The guidance states that the cost-of-living adjustment multiplier for 2024, based on the CPI-U for the month of October 2023, not seasonally adjusted, is 1.03241. The annual inflation adjustments are based on the percent change between the October CPI-U preceding the date of the adjustment, and the prior year's October CPI-U. For 2024, OMB explains, October 2023 CPI-U (307.671)/October 2022 CPI-U (298.012) = 1.03241. The guidance instructs agencies to complete the 2024 annual adjustment by multiplying each applicable penalty by the multiplier 1.03241 and rounding to the nearest dollar. Further, agencies should apply the multiplier to the most recent penalty amount that includes the initial catch-up adjustment required by the Act.
                </P>
                <P>The annual adjustment applies to all civil monetary penalties with a dollar amount that are subject to the Act. This final rule adjusts the following civil monetary penalties contained in the Bureau's regulations for 2024 by multiplying 1.03241 by each penalty amount as updated by the adjustment made in the prior year (2023):</P>
                <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,r100,12,12,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">CFR citation</CHED>
                        <CHED H="1">
                            Description of 
                            <LI>penalty</LI>
                        </CHED>
                        <CHED H="1">
                            Current penalty including catchup 
                            <LI>adjustment</LI>
                        </CHED>
                        <CHED H="1">
                            Annual 
                            <LI>adjustment </LI>
                            <LI>(multiplier)</LI>
                        </CHED>
                        <CHED H="1">
                            Adjusted 
                            <LI>penalty for 2024</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">25 CFR 140.3</ENT>
                        <ENT>Penalty for trading in Indian country without a license</ENT>
                        <ENT>$1,566</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>$1,617</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 141.50</ENT>
                        <ENT>Penalty for trading on Navajo, Hopi, or Zuni reservations without a license</ENT>
                        <ENT>1,566</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>1,617</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 211.55</ENT>
                        <ENT>Penalty for violation of leases of tribal land for mineral development, violation of part 211, or failure to comply with a notice of noncompliance or cessation order</ENT>
                        <ENT>1,882</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>1,943</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 213.37</ENT>
                        <ENT>Penalty for failure of lessee to comply with lease of restricted lands of members of the Five Civilized Tribes in Oklahoma for mining, operating regulations at part 213, or orders</ENT>
                        <ENT>1,566</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>1,617</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 225.37</ENT>
                        <ENT>Penalty for violation of minerals agreement, regulations at part 225, other applicable laws or regulations, or failure to comply with a notice of noncompliance or cessation order</ENT>
                        <ENT>1,992</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>2,057</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 226.42</ENT>
                        <ENT>Penalty for violation of lease of Osage reservation lands for oil and gas mining or regulations at part 226, or noncompliance with the Superintendent's order</ENT>
                        <ENT>1,117</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>1,153</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 226.43(a)</ENT>
                        <ENT>Penalty per day for failure to obtain permission to start operations</ENT>
                        <ENT>111</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>115</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 226.43(b)</ENT>
                        <ENT>Penalty per day for failure to file records</ENT>
                        <ENT>111</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>115</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 226.43(c)</ENT>
                        <ENT>Penalty for each well and tank battery for failure to mark wells and tank batteries</ENT>
                        <ENT>111</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>115</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 226.43(d)</ENT>
                        <ENT>Penalty each day after operations are commenced for failure to construct and maintain pits</ENT>
                        <ENT>111</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>115</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 226.43(e)</ENT>
                        <ENT>Penalty for failure to comply with requirements regarding valve or other approved controlling device</ENT>
                        <ENT>223</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>230</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 226.43(f)</ENT>
                        <ENT>Penalty for failure to notify Superintendent before drilling, redrilling, deepening, plugging, or abandoning any well</ENT>
                        <ENT>446</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>460</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 226.43(g)</ENT>
                        <ENT>Penalty per day for failure to properly care for and dispose of deleterious fluids</ENT>
                        <ENT>1,117</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>1,153</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 226.43(h)</ENT>
                        <ENT>Penalty per day for failure to file plugging and other required reports</ENT>
                        <ENT>111</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>115</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 227.24</ENT>
                        <ENT>Penalty for failure of lessee of certain lands in Wind River Indian Reservation, Wyoming, for oil and gas mining to comply with lease provisions, operating regulations, regulations at part 227, or orders</ENT>
                        <ENT>1,566</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>1,617</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 243.8</ENT>
                        <ENT>Penalty for non-Native transferees of live Alaskan reindeer who violates part 243, takes reindeer without a permit, or fails to abide by permit terms</ENT>
                        <ENT>7,383</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>7,622</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 249.6(b)</ENT>
                        <ENT>Penalty for fishing in violation of regulations at part 249 (Off-Reservation Treaty Fishing)</ENT>
                        <ENT>1,566</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>1,617</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 273.182(a)</ENT>
                        <ENT>Penalty for misusing funds or property by officer, director, agent, or employee of, or connected with, any contractor or subcontractor</ENT>
                        <ENT>1,000</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>1,032</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="18361"/>
                        <ENT I="01">25 CFR 273.182(b)</ENT>
                        <ENT>Penalty for misusing funds or property by officer, director, agent, or employee of, or connected with, any contractor or subcontractor</ENT>
                        <ENT>10,000</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>10,324</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 700.725</ENT>
                        <ENT>Penalty per head per day for each cow, bull, horse, mule, or donkey in trespass</ENT>
                        <ENT>1</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>1 and 3¢</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 CFR 700.725</ENT>
                        <ENT>Penalty per head per day for each sheep or goat in trespass</ENT>
                        <ENT>25¢</ENT>
                        <ENT>1.03241</ENT>
                        <ENT>26¢</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Consistent with the Act, the adjusted penalty levels for 2024 will take effect immediately upon the effective date of the adjustment. The adjusted penalty levels for 2024 will apply to penalties assessed after that date including, if consistent with agency policy, assessments associated with violations that occurred on or after November 2, 2015 (the date of the Act). The Act does not, however, change previously assessed penalties that the Bureau is collecting or has collected. Nor does the Act change an agency's existing statutory authorities to adjust penalties.</P>
                <HD SOURCE="HD1">III. Procedural Requirements</HD>
                <HD SOURCE="HD2">A. Regulatory Planning and Review (E.O. 12866, 14094 and 13563)</HD>
                <P>Executive Order 12866, as amended by E.O. 14094, provides that the Office of Information and Regulatory Affairs in the Office of Management and Budget will review all significant rules. The Office of Information and Regulatory Affairs has determined that this rule is not significant.</P>
                <P>Executive Order 13563 reaffirms the principles of E.O. 12866 while calling for improvements in the Nation's regulatory system to promote predictability, to reduce uncertainty, and to use the best, most innovative, and least burdensome tools for achieving regulatory ends. The Executive order directs agencies to consider regulatory approaches that reduce burdens and maintain flexibility and freedom of choice for the public where these approaches are relevant, feasible, and consistent with regulatory objectives. E.O. 13563 emphasizes further that regulations must be based on the best available science and that the rulemaking process must allow for public participation and an open exchange of ideas. We have developed this rule in a manner consistent with these requirements.</P>
                <P>
                    In accordance with 5 U.S.C. 553(b)(4), a summary of this rule may be found at 
                    <E T="03">https://www.regulations.gov</E>
                     by searching for “RIN 1076-AF75.”
                </P>
                <HD SOURCE="HD2">B. Reducing Regulation and Controlling Regulatory Costs (Executive Order 13771)</HD>
                <P>This rule is not an E.O. 13771 regulatory action because this rule is not significant under Executive Order 12866.</P>
                <HD SOURCE="HD2">C. Regulatory Flexibility Act</HD>
                <P>
                    The Regulatory Flexibility Act (RFA) requires an agency to prepare a regulatory flexibility analysis for rules unless the agency certifies that the rule will not have a significant economic impact on a substantial number of small entities. The RFA applies only to rules for which an agency is required to first publish a proposed rule. 
                    <E T="03">See</E>
                     5 U.S.C. 603(a) and 604(a). The RFA does not apply to this final rule because the Bureau is not required to publish a proposed rule for the reasons explained below in section III.M below.
                </P>
                <HD SOURCE="HD2">D. Congressional Review Act (CRA)</HD>
                <P>This rule is not a major rule under 5 U.S.C. 804(2). This rule:</P>
                <P>(a) Does not have an annual effect on the economy of $100 million or more.</P>
                <P>(b) Will not cause a major increase in costs or prices for consumers, individual industries, Federal, State, or local government agencies, or geographic regions.</P>
                <P>(c) Does not have significant adverse effects on competition, employment, investment, productivity, innovation, or the ability of U.S.-based enterprises to compete with foreign-based enterprises.</P>
                <HD SOURCE="HD2">E. Unfunded Mandates Reform Act</HD>
                <P>
                    This rule does not impose an unfunded mandate on State, local, or tribal governments, or the private sector of more than $100 million per year. The rule does not have a significant or unique effect on State, local, or tribal governments or the private sector. A statement containing the information required by the Unfunded Mandates Reform Act (2 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ) is not required.
                </P>
                <HD SOURCE="HD2">F. Takings (E.O. 12630)</HD>
                <P>This rule does not affect a taking of private property or otherwise have taking implications under Executive Order 12630. A takings implication assessment is not required.</P>
                <HD SOURCE="HD2">G. Federalism (E.O. 13132)</HD>
                <P>Under the criteria in section 1 of Executive Order 13132, this rule does not have sufficient federalism implications to warrant the preparation of a federalism summary impact statement. A federalism summary impact statement is not required.</P>
                <HD SOURCE="HD2">H. Civil Justice Reform (E.O. 12988)</HD>
                <P>This rule complies with the requirements of Executive Order 12988. Specifically, this rule: (a) meets the criteria of section 3(a) requiring that all regulations be reviewed to eliminate errors and ambiguity and be written to minimize litigation; and (b) meets the criteria of section 3(b)(2) requiring that all regulations be written in clear language and contain clear legal standards.</P>
                <HD SOURCE="HD2">I. Consultation With Indian Tribes (E.O. 13175 and Departmental Policy)</HD>
                <P>The Department of the Interior strives to strengthen its government-to-government relationship with Indian tribes through a commitment to consultation with Indian Tribes and recognition of their right to self-governance and tribal sovereignty. We have evaluated this rule under the Department's consultation policy and under the criteria in Executive Order 13175 and have determined that it has no substantial direct effects on federally recognized Indian Tribes and that consultation under the Department's tribal consultation policy is not required.</P>
                <HD SOURCE="HD2">J. Paperwork Reduction Act</HD>
                <P>
                    This rule does not contain information collection requirements, and a submission to the Office of Management and Budget under the Paperwork Reduction Act (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.
                    <PRTPAGE P="18362"/>
                </P>
                <HD SOURCE="HD2">K. National Environmental Policy Act</HD>
                <P>This rule does not constitute a major Federal action significantly affecting the quality of the human environment. A detailed statement under the National Environmental Policy Act of 1969 (NEPA) is not required because the rule is covered by a categorical exclusion. This rule is excluded from the requirement to prepare a detailed statement because it is a regulation of an administrative nature. For further information see 43 CFR 46.210(i). We have also determined that the rule does not involve any of the extraordinary circumstances listed in 43 CFR 46.215 that would require further analysis under NEPA.</P>
                <HD SOURCE="HD2">L. Effects on the Energy Supply (E.O. 13211)</HD>
                <P>This rule is not a significant energy action under the definition in Executive Order 13211. A Statement of Energy Effects is not required.</P>
                <HD SOURCE="HD2">M. Clarity of This Regulation</HD>
                <P>We are required by E.O. 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>(a) Be logically organized;</P>
                <P>(b) Use the active voice to address readers directly;</P>
                <P>(c) Use clear language rather than jargon;</P>
                <P>(d) Be divided into short sections and sentences; and</P>
                <P>(e) 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 the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section. 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 you find unclear, which sections or sentences are too long, the sections where you believe lists or tables would be useful, etc.
                </P>
                <HD SOURCE="HD2">N. Administrative Procedure Act</HD>
                <P>
                    The Act requires agencies to publish annual inflation adjustments by no later than January 15, of each year, notwithstanding section 553 of the Administrative Procedure Act (APA) (5 U.S.C. 553). OMB has interpreted this direction to mean that the usual APA public procedure for rulemaking—which includes public notice of a proposed rule, an opportunity for public comment, and a delay in the effective date of a final rule—is not required when agencies issue regulations to implement the annual adjustments to civil penalties that the Act requires. Accordingly, we are issuing the annual adjustments as a final rule without prior notice or an opportunity for comment and with an effective date immediately upon publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>Section 553(b) of the APA provides that, when an agency for good cause finds that “notice and public procedure . . . are impracticable, unnecessary, or contrary to the public interest,” the agency may issue a rule without providing notice and an opportunity for prior public comment. Under section 553(b), the Bureau finds that there is good cause to promulgate this rule without first providing for public comment. It would not be possible to meet the deadlines imposed by the Act if we were to first publish a proposed rule, allow the public sufficient time to submit comments, analyze the comments, and publish a final rule. Also, the Bureau is promulgating this final rule to implement the statutory directive in the Act, which requires agencies to publish a final rule and to update the civil penalty amounts by applying a specified formula. The Bureau has no discretion to vary the amount of the adjustment to reflect any views or suggestions provided by commenters. Accordingly, it would serve no purpose to provide an opportunity for public comment on this rule prior to promulgation. Thus, providing for notice and public comment is impracticable and unnecessary.</P>
                <P>
                    Furthermore, the Bureau finds under section 553(d)(3) of the APA that good cause exists to make this final rule effective immediately upon publication in the 
                    <E T="04">Federal Register</E>
                    . In the Act, Congress expressly required Federal agencies to publish annual inflation adjustments to civil penalties in the 
                    <E T="04">Federal Register</E>
                     by January 15 of each year, notwithstanding section 553 of the APA. Under the statutory framework and OMB guidance, the new penalty levels take effect immediately upon the effective date of the adjustment. The statutory deadline does not allow time to delay this rule's effective date beyond publication. Moreover, an effective date after January 15 would delay application of the new penalty levels, contrary to Congress's intent.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>25 CFR Part 140</CFR>
                    <P>Business and industry, Indians, Penalties.</P>
                    <CFR>25 CFR Part 141</CFR>
                    <P>Business and industry, Credit, Indians—business and finance, Penalties.</P>
                    <CFR>25 CFR Part 211</CFR>
                    <P>Geothermal energy, Indians—lands, Mineral resources, Mines, Oil and gas exploration, Reporting and recordkeeping requirements.</P>
                    <CFR>25 CFR Part 213</CFR>
                    <P>Indians—lands, Mineral resources, Mines, Oil and gas exploration, Reporting and recordkeeping requirements.</P>
                    <CFR>25 CFR Part 225</CFR>
                    <P>Geothermal energy, Indians—lands, Mineral resources, Mines, Oil and gas exploration, Penalties, Reporting and recordkeeping requirements, Surety bonds.</P>
                    <CFR>25 CFR Part 226</CFR>
                    <P>Indians—lands.</P>
                    <CFR>25 CFR Part 227</CFR>
                    <P>Indians—lands, Mineral resources, Mines, Oil and gas exploration, Reporting and recordkeeping requirements.</P>
                    <CFR>25 CFR Part 243</CFR>
                    <P>Indians, Livestock.</P>
                    <CFR>25 CFR Part 249</CFR>
                    <P>Fishing, Indians.</P>
                    <CFR>25 CFR Part 273</CFR>
                    <P>Elementary and secondary education, Grant programs—Indians, Indians—education, Schools.</P>
                    <CFR>25 CFR Part 700</CFR>
                    <P>Indians, Indians—lands, Livestock.</P>
                </LSTSUB>
                <P>For the reasons given in the preamble, the Department of the Interior amends chapter I of title 25 Code of Federal Regulations as follows.</P>
                <HD SOURCE="HD1">Title 25—Indians</HD>
                <HD SOURCE="HD1">Chapter I—Bureau of Indian Affairs, Department of the Interior</HD>
                <PART>
                    <HD SOURCE="HED">PART 140—LICENSED INDIAN TRADERS</HD>
                </PART>
                <REGTEXT TITLE="25" PART="140">
                    <AMDPAR>1. The authority citation for part 140 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>5 U.S.C. 301; 18 U.S.C. 437; 25 U.S.C. 2, 9, 261, 262, 264; sec. 5, 19 Stat. 200, sec. 1, 31 Stat. 1066, as amended; and sec. 701, Pub. L. 114-74, 129 Stat. 599, unless otherwise noted.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 140.3</SECTNO>
                    <SUBJECT> [Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="25" PART="140">
                    <AMDPAR>
                        2. In § 140.3, remove “$1,566” and add in its place “$1,617” and remove 
                        <PRTPAGE P="18363"/>
                        the parenthetical authority citation at the end of the section.
                    </AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 141—BUSINESS PRACTICES ON THE NAVAJO, HOPI AND ZUNI RESERVATIONS</HD>
                </PART>
                <REGTEXT TITLE="25" PART="141">
                    <AMDPAR>3. The authority citation for part 141 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 5 U.S.C. 301; 25 U.S.C. 2 and 9; and Sec. 701, Pub. L. 114-74, 129 Stat. 599, unless otherwise noted.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 141.50 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="25" PART="141">
                    <AMDPAR>4. In § 141.50, remove “$1,566” and add in its place “$1,617”.</AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 211—LEASING OF TRIBAL LANDS FOR MINERAL DEVELOPMENT</HD>
                </PART>
                <REGTEXT TITLE="25" PART="211">
                    <AMDPAR>5. The authority citation for part 211 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>Sec. 4, Act of May 11, 1938 (52 Stat. 347); Act of August 1, 1956 (70 Stat. 744); 25 U.S.C. 396a-g; 25 U.S.C. 2 and 9; and Sec. 701, Pub. L. 114-74, 129 Stat. 599, unless otherwise noted.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 211.55</SECTNO>
                    <SUBJECT> [Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="25" PART="211">
                    <AMDPAR>6. In § 211.55(a), remove “$1,882” and add in its place “$1,943”. </AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 213—LEASING OF RESTRICTED LANDS FOR MEMBERS OF FIVE CIVILIZED TRIBES, OKLAHOMA, FOR MINING</HD>
                </PART>
                <REGTEXT TITLE="25" PART="213">
                    <AMDPAR>7. The authority citation for part 213 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>Sec. 2, 35 Stat. 312; sec. 18, 41 Stat. 426; sec. 1, 45 Stat. 495; sec. 1, 47 Stat. 777; 25 U.S.C. 356; and Sec. 701, Pub. L. 114-74, 129 Stat. 599. Interpret or apply secs. 3, 11, 35 Stat. 313, 316; sec. 8, 47 Stat. 779, unless otherwise noted.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 213.37</SECTNO>
                    <SUBJECT> [Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="25" PART="213">
                    <AMDPAR>8. In § 213.37, remove “$1,566” and add in its place “$1,617”. </AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 225—OIL AND GAS, GEOTHERMAL, AND SOLID MINERALS AGREEMENTS</HD>
                </PART>
                <REGTEXT TITLE="25" PART="225">
                    <AMDPAR>9. The authority citation for part 225 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>25 U.S.C. 2, 9, and 2101-2108; and Sec. 701, Pub. L. 114-74, 129 Stat. 599.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 225.37 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="25" PART="225">
                    <AMDPAR>10. In § 225.37(a), remove “$1,992” and add in its place “$2,057”. </AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 226—LEASING OF OSAGE RESERVATION LANDS FOR OIL AND GAS MINING</HD>
                </PART>
                <REGTEXT TITLE="25" PART="226">
                    <AMDPAR>11. The authority citation for part 226 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>Sec. 3, 34 Stat. 543; secs. 1, 2, 45 Stat. 1478; sec. 3, 52 Stat. 1034, 1035; sec. 2(a), 92 Stat. 1660; and Sec. 701, Pub. L. 114-74, 129 Stat. 599.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 226.42</SECTNO>
                    <SUBJECT> [Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="25" PART="226">
                    <AMDPAR>12. In § 226.42, remove “$1,117” and add in its place “$1,153”.</AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 226.43</SECTNO>
                    <SUBJECT> [Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="25" PART="226">
                    <AMDPAR>13. In § 226.43:</AMDPAR>
                    <AMDPAR>a. Remove “$111” wherever it appears and add “$115” in its place.</AMDPAR>
                    <AMDPAR>b. In paragraph (e), remove “$223” and add in its place “$230”.</AMDPAR>
                    <AMDPAR>c. In paragraph (f), remove “$446” and add in its place “$460”.</AMDPAR>
                    <AMDPAR>d. In paragraph (g), remove “$1,117” and add in its place “$1,153”.</AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 227—LEASING OF CERTAIN LANDS IN WIND RIVER INDIAN RESERVATION, WYOMING, FOR OIL AND GAS MINING</HD>
                </PART>
                <REGTEXT TITLE="25" PART="227">
                    <AMDPAR>14. The authority citation for part 227 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>Sec. 1, 39 Stat. 519; and Sec. 701, Pub. L. 114-74, 129 Stat. 599, unless otherwise noted.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 227.24</SECTNO>
                    <SUBJECT> [Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="25" PART="227">
                    <AMDPAR>15. In § 227.24, remove “$1,566” and add in its place “$1,617”.</AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 243—REINDEER IN ALASKA</HD>
                </PART>
                <REGTEXT TITLE="25" PART="243">
                    <AMDPAR>16. The authority citation for part 243 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>Sec. 12, 50 Stat. 902; 25 U.S.C. 500K; and Sec. 701, Pub. L. 114-74, 129 Stat. 599.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 243.8 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="25" PART="243">
                    <AMDPAR>17. In § 243.8(a) introductory text, remove “$7,383” and add in its place “$7,622”.</AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 249—OFF-RESERVATION TREATY FISHING</HD>
                </PART>
                <REGTEXT TITLE="25" PART="249">
                    <AMDPAR>18. The authority citation for part 249 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>25 U.S.C. 2, and 9; 5 U.S.C. 301; and Sec. 701, Pub. L. 114-74, 129 Stat. 599, unless otherwise noted.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 249.6</SECTNO>
                    <SUBJECT> [Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="25" PART="249">
                    <AMDPAR>19. In § 249.6(b), remove “$1,566” and add in its place “$1,617”.</AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 273—EDUCATION CONTRACTS UNDER JOHNSON-O'MALLEY ACT</HD>
                </PART>
                <REGTEXT TITLE="25" PART="273">
                    <AMDPAR>20. The authority citation for part 273 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>Secs. 201-203, Pub. L. 93-638, 88 Stat. 2203, 2213-2214 (25 U.S.C. 455-457), unless otherwise noted.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 273.182 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="25" PART="273">
                    <AMDPAR>21. In § 273.182(a) remove “$1,000” and add in its place “$1,032”.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="25" PART="273">
                    <AMDPAR>22. In § 273.182(b) remove “$10,000” and add in its place “$10,324”.</AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 700—COMMISSION OPERATIONS AND RELOCATION PROCEDURES</HD>
                </PART>
                <REGTEXT TITLE="25" PART="700">
                    <AMDPAR>23. The authority citation for part 700 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P> Pub. L. 99-590; Pub. L. 93-531, 88 Stat. 1712 as amended by Pub. L. 96-305, 94 Stat. 929, Pub. L. 100-666, 102 Stat. 3929 (25 U.S.C. 640d).</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 700.725</SECTNO>
                    <SUBJECT> [Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="25" PART="700">
                    <AMDPAR>24. In § 700.725, remove “$1” and add in its place “$1 and 3¢”.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="25" PART="700">
                    <AMDPAR>25. In § 700.725, remove “25¢” and add in its place “26¢”.</AMDPAR>
                </REGTEXT>
                <SIG>
                    <NAME>Bryan Newland,</NAME>
                    <TITLE>Assistant Secretary—Indian Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05275 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4337-15-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">PENSION BENEFIT GUARANTY CORPORATION</AGENCY>
                <CFR>29 CFR Part 4044</CFR>
                <SUBJECT>Allocation of Assets in Single-Employer Plans; Interest Assumptions for Valuing Benefits</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Pension Benefit Guaranty Corporation.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This final rule amends the Pension Benefit Guaranty Corporation's regulation on Allocation of Assets in Single-Employer Plans to prescribe interest assumptions under the asset allocation regulation for plans with valuation dates in the second quarter of 2024. These interest assumptions are used for valuing benefits under terminating single-employer plans and for other purposes.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective April 1, 2024.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Monica O'Donnell (
                        <E T="03">odonnell.monica@pbgc.gov</E>
                        ), Attorney, Office of the General Counsel, Pension Benefit Guaranty Corporation, 445 12th Street SW, Washington, DC 20024-2101, 202-229-8706. 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>
                    PBGC's regulation on Allocation of Assets in Single-Employer Plans (29 CFR part 4044) prescribes actuarial assumptions—including interest assumptions—for valuing benefits under terminating single-employer plans covered by title IV of the Employee 
                    <PRTPAGE P="18364"/>
                    Retirement Income Security Act of 1974 (ERISA). The interest assumptions in the regulation are also published on PBGC's website (
                    <E T="03">www.pbgc.gov</E>
                    ).
                </P>
                <P>PBGC uses the interest assumptions in appendix B to part 4044 (“Interest Rates Used to Value Benefits”) to determine the present value of annuities in an involuntary or distress termination of a single-employer plan under the asset allocation regulation. The assumptions are also used to determine the value of multiemployer plan benefits and certain assets when a plan terminates by mass withdrawal in accordance with PBGC's regulation on Duties of Plan Sponsor Following Mass Withdrawal (29 CFR part 4281).</P>
                <P>The second quarter 2024 interest assumptions will be 5.50 percent for the first 20 years following the valuation date and 4.83 percent thereafter. In comparison with the interest assumptions in effect for the first quarter of 2024, these interest assumptions represent no change in the select period (the period during which the select rate (the initial rate) applies), an increase of 0.05 percent in the select rate, and a decrease of 0.39 percent in the ultimate rate (the final rate).</P>
                <HD SOURCE="HD1">Need for Immediate Guidance</HD>
                <P>PBGC has determined that notice of, and public comment on, this rule are impracticable, unnecessary, and contrary to the public interest. PBGC routinely updates the interest assumptions in appendix B of the asset allocation regulation each quarter so that they are available to value benefits. Accordingly, PBGC finds that the public interest is best served by issuing this rule expeditiously, without an opportunity for notice and comment, and that good cause exists for making the assumptions set forth in this amendment effective less than 30 days after publication to allow the use of the proper assumptions to estimate the value of plan benefits for plans with valuation dates early in the second quarter of 2024.</P>
                <P>PBGC has determined that this action is not a “significant regulatory action” under the criteria set forth in Executive Order 12866.</P>
                <P>Because no general notice of proposed rulemaking is required for this amendment, the Regulatory Flexibility Act of 1980 does not apply. See 5 U.S.C. 601(2).</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 29 CFR Part 4044</HD>
                    <P>Employee benefit plans, Pension insurance, Pensions.</P>
                </LSTSUB>
                <P>In consideration of the foregoing, 29 CFR part 4044 is amended as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 4044—ALLOCATION OF ASSETS IN SINGLE-EMPLOYER PLANS</HD>
                </PART>
                <REGTEXT TITLE="29" PART="4044">
                    <AMDPAR>1. The authority citation for part 4044 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>29 U.S.C. 1301(a), 1302(b)(3), 1341, 1344, 1362.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="29" PART="4044">
                    <AMDPAR>2. In appendix B to part 4044, an entry for “April-June 2024” is added at the end of the table to read as follows:</AMDPAR>
                    <HD SOURCE="HD1">Appendix B to Part 4044—Interest Rates Used To Value Benefits</HD>
                    <STARS/>
                    <GPOTABLE COLS="7" OPTS="L1,tp0,i1" CDEF="s75,12,12,12,12,12,12">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1" O="L">For valuation dates occurring in the month—</CHED>
                            <CHED H="1" O="L">
                                The values of 
                                <E T="03">i</E>
                                <E T="8145">t</E>
                                 are:
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="8145">t</E>
                            </CHED>
                            <CHED H="2">
                                for 
                                <E T="03">t</E>
                                 =
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="8145">t</E>
                            </CHED>
                            <CHED H="2">
                                for 
                                <E T="03">t</E>
                                 =
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="8145">t</E>
                            </CHED>
                            <CHED H="2">
                                for 
                                <E T="03">t</E>
                                 =
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22"> </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="28">*         *         *         *         *         *         *</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">April-June 2024</ENT>
                            <ENT>0.0550</ENT>
                            <ENT>1-20</ENT>
                            <ENT>0.0483</ENT>
                            <ENT>&gt;20</ENT>
                            <ENT>N/A</ENT>
                            <ENT>N/A</ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <SIG>
                    <P>Issued in Washington, DC, by</P>
                    <NAME>Hilary Duke,</NAME>
                    <TITLE>Assistant General Counsel for Regulatory Affairs, Pension Benefit Guaranty Corporation.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05249 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7709-02-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <CFR>47 CFR Part 73</CFR>
                <DEPDOC>[MB Docket No. 23-406; RM-11969; DA 24-199; FR ID 207515]</DEPDOC>
                <SUBJECT>Television Broadcasting Services Greenville, South Carolina</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On November 27, 2023, the Media Bureau, Video Division (Bureau) issued a Notice of Proposed Rulemaking (NPRM) in response to a petition for rulemaking filed by Carolina Christian Broadcasting, Inc. (Petitioner), the licensee of WGGS-TV (Station or WGGS), channel 2, Greenville, South Carolina (Greenville), requesting the substitution of channel 29 for channel 2 at Greenville in the Table of TV Allotments. For the reasons set forth in the 
                        <E T="03">Report and Order</E>
                         referenced below, the Bureau amends FCC regulations to substitute channel 29 for channel 2 at Greenville.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective April 12, 2024.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Joyce Bernstein, Media Bureau, at (202) 418-1647 or 
                        <E T="03">Joyce.Bernstein@fcc.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The proposed rule was published at 88 FR 84771 on December 6, 2023. The Petitioner filed comments in support of the petition reaffirming its commitment to apply for channel 29. No other comments were filed.</P>
                <P>
                    The Bureau believes the public interest would be served by substituting channel 29 for channel 2 at Greenville. Petitioner states that its proposed channel substitution would serve the public interest by resolving reception challenges currently experienced by viewers in the WGGS service area, and substantially improving access to the Station's programming. The Petitioner notes that the Commission has recognized that VHF channels have certain characteristics that pose challenges for their use in providing digital television service, including a large variability in the performance of indoor antennas available to viewers, with most antennas performing very poorly on VHF channels. The Petitioner proposes to operate the Station on channel 29 with a 3-node Distributed Transmission System (DTS) facility, and all viewers within the Station's community of license will continue to be served by the Station. An analysis using the Commission's TVStudy software indicates that the Station's move to channel 29 would result in a loss of service to 946,964 persons, mostly located around the edge of the channel 2 noise limited service contour (NLSC). All but 417 persons of those persons, however, would remain well-served by continuing to receive at least five full power or Class A stations, and those 417 persons would continue to receive service from at least four such stations, a number of persons that the Commission has found to be de minimis.
                    <PRTPAGE P="18365"/>
                </P>
                <P>As proposed, channel 29 can be substituted for channel 2 at Greenville in compliance with the principal community coverage requirements of section 73.625(a) of the rules, at coordinates 34°56′26.4″ N and 82°24′40.4″ W. Although the Petitioner's proposal would result in a loss of programming to a number of viewers on the fringes of the Station's NLSC, all but a de minimis number of viewers will remain well-served and we conclude that the overall benefits of the proposed channel change in resolving reception issues outweighs any possible harm to the public interest.</P>
                <P>
                    This is a synopsis of the Commission's 
                    <E T="03">Report and Order,</E>
                     MB Docket No. 23-406; RM-11969; DA 24-199, adopted March 4, 2024, and released March 4, 2024. The full text of this document is available for download at 
                    <E T="03">https://www.fcc.gov/edocs.</E>
                     To request materials in accessible formats for people with disabilities (braille, large print, electronic files, audio format), send an email to 
                    <E T="03">fcc504@fcc.gov</E>
                     or call the Consumer &amp; Governmental Affairs Bureau at 202-418-0530 (voice), 202-418-0432 (tty).
                </P>
                <P>
                    This document does not contain information collection requirements subject to the Paperwork Reduction Act of 1995, Public Law 104-13. In addition, therefore, it does not contain any proposed information collection burden “for small business concerns with fewer than 25 employees,” pursuant to the Small Business Paperwork Relief Act of 2002, Public Law 107-198, 
                    <E T="03">see</E>
                     44 U.S.C. 3506(c)(4). Provisions of the Regulatory Flexibility Act of 1980, 5 U.S.C. 601-612, do not apply to this proceeding.
                </P>
                <P>
                    The Commission will send a copy of this 
                    <E T="03">Report and Order</E>
                     in a report to be sent to Congress and the Government Accountability Office pursuant to the Congressional Review Act, 
                    <E T="03">see</E>
                     5 U.S.C. 801(a)(1)(A).
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 47 CFR Part 73</HD>
                    <P>Television.</P>
                </LSTSUB>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Thomas Horan,</NAME>
                    <TITLE>Chief of Staff, Media Bureau.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Final Rule</HD>
                <P>For the reasons discussed in the preamble, the Federal Communications Commission amends 47 CFR part 73 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 73—RADIO BROADCAST SERVICE</HD>
                </PART>
                <REGTEXT TITLE="47" PART="73">
                    <AMDPAR>1. The authority citation for part 73 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 47 U.S.C. 154, 155, 301, 303, 307, 309, 310, 334, 336, 339.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="73">
                    <AMDPAR>2. In § 73.622, in paragraph (j), amend the Table of TV Allotments, under South Carolina, by revising the entry for Greenville to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 73.622 </SECTNO>
                        <SUBJECT>Digital television table of allotments.</SUBJECT>
                        <STARS/>
                        <P>(j) * * *</P>
                        <GPOTABLE COLS="2" OPTS="L1,tp0,i1" CDEF="s50,12C">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1">Community</CHED>
                                <CHED H="1">Channel No.</CHED>
                            </BOXHD>
                            <ROW RUL="s">
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*    *    *    *    *    </ENT>
                            </ROW>
                            <ROW EXPSTB="01" RUL="s">
                                <ENT I="21">
                                    <E T="02">South Carolina</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*    *    *    *    *    </ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="01">Greenville</ENT>
                                <ENT>*8, 17, 29, 30</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*    *    *    *    *    </ENT>
                            </ROW>
                        </GPOTABLE>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05307 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </RULE>
    </RULES>
    <VOL>89</VOL>
    <NO>50</NO>
    <DATE>Wednesday, March 13, 2024</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <PRORULES>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="18366"/>
                <AGENCY TYPE="F">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 165</CFR>
                <DEPDOC>[Docket Number USCG-2024-0191]</DEPDOC>
                <RIN>RIN 1625-AA00</RIN>
                <SUBJECT>Safety Zone; Inner Harbor, Baltimore MD</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, Department of Homeland Security (DHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is proposing a temporary safety zone for certain waters of the Inner Harbor of Baltimore, MD, where Maryland Fleet Week and Flyover Baltimore 2024 will take place from June 12 to 18, 2024. The safety zone would protect personnel, vessels, and the marine environment from potential hazards during multi-agency helicopter rescue demonstration. It would be enforced thirty minutes prior to a demonstration and lifted at its conclusion. Entry of vessels or persons into this zone is prohibited unless specifically authorized by the Captain of the Port, Maryland-National Capital Region, or a designated representative.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by the Coast Guard on or before April 7, 2024.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments identified by docket number USCG-2024-0191 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. This notice of proposed rulemaking with its plain-language, 100-word-or-less proposed rule summary will be available in this same docket.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions about this proposed rulemaking, call or email Mr. Charles Bullock, Sector Maryland-National Capital Region Waterways Management Division, U.S. Coast Guard; telephone 410-576-2674, email 
                        <E T="03">Charles.d.bullock@uscg.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <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, Sector Maryland-National Capital Region</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, Purpose, and Legal Basis</HD>
                <P>The Coast Guard is proposing to establish a safety zone from 8 a.m. on June 12, 2024, through 6 p.m. on June 18, 2024. The zone would be intended to protect personnel, vessels, and the marine environment in these navigable waters before, during, and after the air and rescue swimmer demonstrations. No vessel or person would be permitted to enter the safety zone without obtaining permission from the COTP or a designated representative. We invite your comments on this proposed rulemaking.</P>
                <HD SOURCE="HD1">III. Discussion of Proposed Rule</HD>
                <P>The zone would be enforced beginning thirty minutes prior to a demonstration and ending at the conclusion of that demonstration. It would cover all navigable waters of the Inner Harbor, encompassed by a line connecting the following points: beginning at Inner Harbor Pier 6 at position latitude 39°16′59″ N, longitude 076°36′12″ W, thence south to the Harborview Towers pier at latitude 39°16′41″ N, longitude 076°36′12″ W, thence northerly and easterly along the shoreline to and terminating at the point of origin located in Baltimore, MD. The dimensions of the safety zone are approximately 2,000 yards in length and 500 yards in width.</P>
                <HD SOURCE="HD1">IV. Regulatory Analyses</HD>
                <P>We developed this proposed rule after considering numerous statutes and Executive orders related to rulemaking. Below we summarize our analyses based on 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 NPRM has not been designated a “significant regulatory action,” under section 3(f) of Executive Order 12866, as amended by Executive Order 14094 (Modernizing Regulatory Review). Accordingly, the NPRM has not been reviewed by the Office of Management and Budget (OMB).</P>
                <P>This regulatory action determination is based on the location and duration of the safety zone. This safety zone will be enforced 30 minutes prior to a demonstration and will be lifted at the conclusion of each demonstration. We anticipate that there will be no vessels that are unable to conduct business. Commercial fishing vessels and towing vessels do not operate in the Inner Harbor and would not be impacted by this rulemaking. Although excursion vessels and water taxis do operate there, the impact to these waterway users is minimized because of the extensive outreach that has been conducted for the Maryland Fleet Week and Flyover Baltimore 2024 and the involvement of these vessel managers in the event planning process. 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 proposed rule would 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 IV.A above, this proposed rule would not have a significant economic impact on any vessel owner or operator. We have 
                    <PRTPAGE P="18367"/>
                    deconflicted ferry boat schedules and other commercial vessels during the planning process for these events.
                </P>
                <P>
                    If you think that your business, organization, or governmental jurisdiction qualifies as a small entity and that this proposed rule would have a significant economic impact on it, please submit a comment (see 
                    <E T="02">ADDRESSES</E>
                    ) explaining why you think it qualifies and how and to what degree this rule would economically affect it.
                </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 proposed rule. If the proposed 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. The Coast Guard will not retaliate against small entities that question or complain about this proposed rule or any policy or action of the Coast Guard.
                </P>
                <HD SOURCE="HD2">C. Collection of Information</HD>
                <P>This proposed rule would 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 proposed 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 proposed rule does not have tribal implications under Executive Order 13175 (Consultation and Coordination with Indian Tribal Governments) because it would not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes. If you believe this proposed rule has implications for federalism or Indian tribes, please call or email the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section.
                </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 proposed rule would not result in such an expenditure, we do discuss the potential effects of this proposed rule elsewhere in this preamble.</P>
                <HD SOURCE="HD2">F. Environment</HD>
                <P>
                    We have analyzed this proposed 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 made a preliminary determination 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 proposed rule involves an intermittent safety zone lasting 30 minutes at a time, that would prohibit entry the above-mentioned safety zone. 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. 01. A preliminary 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. We seek any comments or information that may lead to the discovery of a significant environmental impact from promulgation of this proposed rule.
                </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>
                <HD SOURCE="HD1">V. Public Participation and Request for Comments</HD>
                <P>We view public participation as essential to effective rulemaking and will consider all comments and material received during the comment period. Your comment can help shape the outcome of this rulemaking. If you submit a comment, please include the docket number for this rulemaking, indicate the specific section of this document to which each comment applies, and provide a reason for each suggestion or recommendation.</P>
                <P>
                    <E T="03">Submitting comments.</E>
                     We encourage you to submit comments through the Federal Decision-Making Portal at 
                    <E T="03">https://www.regulations.gov.</E>
                     To do so, go to 
                    <E T="03">https://www.regulations.gov,</E>
                     type USCG-2024-0191 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 you cannot submit your material by using 
                    <E T="03">https://www.regulations.gov,</E>
                     call or email the person in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this proposed rule for alternate instructions.
                </P>
                <P>
                    <E T="03">Viewing material in docket.</E>
                     To view documents mentioned in this proposed rule 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. Also, if you click on the Dockets tab and then the proposed rule, you should see a “Subscribe” option for email alerts. That option will notify you when comments are posted, or a final rule is published.
                </P>
                <P>We review all comments received, but we will only post comments that address the topic of the proposed rule. 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 to the docket in response to this document, see DHS's eRulemaking System of Records notice (85 FR 14226, March 11, 2020).
                </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>
                <AMDPAR>1. The authority citation for part 165 continues to read as follows:</AMDPAR>
                <AUTH>
                    <PRTPAGE P="18368"/>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> 46 U.S.C. 70034, 70051, 70124; 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.3.</P>
                </AUTH>
                <AMDPAR>2. Add § 165.T05-0712 to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 165.T05-0712</SECTNO>
                    <SUBJECT> Safety Zone; Inner Harbor, Baltimore, MD.</SUBJECT>
                    <P>
                        (a) 
                        <E T="03">Location.</E>
                         The following area is a safety zone: All navigable waters of the Inner Harbor, encompassed by a line connecting the following points: beginning at Inner Harbor Pier 6 at position latitude 39°16′59″ N, longitude 076°36′12″ W, thence south to the Harborview Towers pier at latitude 39°16′41″ N, longitude 076°36′12″ W, thence northerly and easterly along the shoreline to and terminating at the point of origin, located in Baltimore, MD. These coordinates are based on datum NAD 1983.
                    </P>
                    <P>
                        (b) 
                        <E T="03">Definitions.</E>
                         As used in this section—
                    </P>
                    <P>
                        <E T="03">Captain of the Port (COTP)</E>
                         means the Commander, U.S. Coast Guard Sector Maryland-National Capital Region.
                    </P>
                    <P>
                        <E T="03">Designated representative</E>
                         means any Coast Guard commissioned, warrant, or petty officer who has been authorized by the Captain of the Port Maryland-National Capital Region to assist in enforcing the safety zone described in paragraph (a) of this section.
                    </P>
                    <P>
                        (c) 
                        <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 telephone at 410-576-2693 or on Marine Band Radio VHF-FM channel 16 (156.8 MHz). The Coast Guard vessels enforcing this section can be contacted on Marine Band Radio VHF-FM channel 16 (156.8 MHz).</P>
                    <P>(3) 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>
                        (d) 
                        <E T="03">Enforcement officials.</E>
                         The U.S. Coast Guard may be assisted in the patrol and enforcement of the safety zone by Federal, State, and local agencies.
                    </P>
                    <P>
                        (e) 
                        <E T="03">Enforcement period.</E>
                         This section will be enforced as needed from June 12, 2024, to June 18, 2024.
                    </P>
                </SECTION>
                <SIG>
                    <DATED>Dated: March 8, 2024.</DATED>
                    <NAME>David E. O'Connell,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port Maryland-National Capital Region.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05339 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <CFR>50 CFR Part 300</CFR>
                <DEPDOC>[Docket No. 240307-0074]</DEPDOC>
                <RIN>RTID 0648-XD634</RIN>
                <SUBJECT>Pacific Halibut Fisheries of the West Coast; Management Measures for the 2024 Area 2A Pacific Halibut Directed Commercial Fishery</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        NMFS proposes to implement fishing periods and fishing period limits for the 2024 non-tribal directed commercial Pacific halibut fishery that operates south of Point Chehalis, WA, (lat. 46°53.30′ N) in the International Pacific Halibut Commission's regulatory Area 2A off Washington, Oregon, and California. The proposed action includes two 58-hour fishing periods. The first fishing period would begin at 8 a.m. Pacific Daylight Time (PDT) on June 25, 2024, and close at 6 p.m. PDT on June 27, 2024. The second fishing period would start at 8 a.m. PDT on July 9, 2024, and close at 6 p.m. PDT on July 11, 2024. NMFS is also proposing four fishing period limits (
                        <E T="03">i.e.,</E>
                         vessel catch limits) across eight vessel size classes for both fishing periods. These actions are intended to conserve Pacific halibut and provide fishing opportunity where available.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by April 12, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        A plain language summary of this proposed rule is available at 
                        <E T="03">https://www.regulations.gov/docket/NOAA-NMFS-2024-0031.</E>
                         You may submit comments on this document, identified by NOAA-NMFS-2024-0031, 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 type NOAA-NMFS-2024-0031 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 or received after the end of the comment period, may not be considered by NMFS. All comments received are a part of the public record and will generally be posted for public viewing on 
                        <E T="03">https://www.regulations.gov</E>
                         without change. All personal identifying information (
                        <E T="03">e.g.,</E>
                         name, address, 
                        <E T="03">etc.</E>
                        ), confidential business information, or otherwise sensitive information submitted voluntarily by the sender will be publicly accessible. NMFS will accept anonymous comments (enter “N/A” in the required fields if you wish to remain anonymous).
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         This proposed rule is accessible at the Office of the Federal Register website at 
                        <E T="03">https://www.federalregister.gov.</E>
                         Background information and documents are available at the NMFS West Coast Region Pacific Halibut Directed Commercial Fishery website at 
                        <E T="03">https://www.fisheries.noaa.gov/action/2024-pacific-halibut-directed-commercial-fishery</E>
                         and at the Council's website at 
                        <E T="03">https://www.pcouncil.org.</E>
                         Other comments received may be accessed through 
                        <E T="03">https://www.regulations.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Heather Fitch, West Coast Region, NMFS, (360) 320-6549, 
                        <E T="03">heather.fitch@noaa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>The Northern Pacific Halibut Act of 1982 (16 U.S.C. 773-773k) (Halibut Act) gives the Secretary of Commerce the responsibility of 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 (Convention), signed at Ottawa, Ontario, on March 2, 1953, as amended by a Protocol Amending the Convention (March 29, 1979).</P>
                <P>
                    As provided in the Halibut Act at 16 U.S.C. 773b, the Secretary of State, with the concurrence of the Secretary of Commerce, may accept or reject, on behalf of the United States, regulations recommended by the International Pacific Halibut Commission (IPHC) in accordance with the Convention. Following acceptance by the Secretary of State, the annual management measures promulgated by the IPHC are published in the 
                    <E T="04">Federal Register</E>
                     to provide notice of their immediate regulatory effectiveness and to inform persons subject to the regulations of their restrictions and requirements (50 CFR 300.62).
                </P>
                <P>
                    The Halibut Act also provides that Regional Fishery Management Councils may develop, and the Secretary of Commerce may implement, regulations governing Pacific halibut fishing in U.S. waters that are in addition to, and not in conflict with, approved IPHC regulations (16 U.S.C. 773c(c)). The Pacific Fishery Management Council 
                    <PRTPAGE P="18369"/>
                    (Council) developed a catch sharing plan guiding the allocation of halibut across the various sectors for the IPHC's regulatory Area 2A.
                </P>
                <HD SOURCE="HD1">Fishery Allocation</HD>
                <P>
                    At its annual meeting held January 22-26, 2024, the IPHC adopted an Area 2A catch limit, called a fishery constant exploitation yield (FCEY), of 1.47 million pounds (667 metric tons (mt)), net weight (
                    <E T="03">i.e.,</E>
                     the weight of Pacific halibut that is without gills and entrails, head-off, washed, and without ice and slime) of Pacific halibut. Upon acceptance by the Secretary of State, with concurrence from the Secretary of Commerce, the fishery allocations adopted by the IPHC will be published in the 
                    <E T="04">Federal Register</E>
                    , in accordance with 50 CFR 300.62. The FCEY was derived from the total constant exploitation yield (TCEY) of 1.65 million pounds (748 mt), net weight, for Area 2A, which includes commercial discards and bycatch projections calculated using a formula developed by the IPHC. Based on the FCEY for Area 2A and the allocation framework in the Council's catch sharing plan, the non-tribal directed commercial fishing allocation is 249,338 pounds (113 mt), net weight.
                </P>
                <HD SOURCE="HD1">Fishing Periods</HD>
                <P>Fishing periods, often referred to as fishery openers, are the time during the annual commercial halibut season when fishing for non-tribal directed commercial Pacific halibut in Area 2A is allowed. At its November 2023 meeting, the Council discussed the 2024 directed commercial season structure and recommended that NMFS establish fishing periods similar to those in the previous year. Specifically, the Council recommended that the directed commercial fishery operate as a series of 3-day openings, with the first fishing period beginning at 8 a.m. Pacific Daylight Time (PDT) on the fourth Tuesday in June and ending at 6 p.m. PDT on Thursday of that week, and the second fishing period occurring 2 weeks later. The Council also recommended that if there is a third fishing period, it should occur no earlier than 3 weeks after the second fishing period, and that any subsequent fishing periods would occur as soon as possible. Based on the Council's recommendations, NMFS is proposing to open the 2024 directed commercial fishery for 58 hours, beginning on June 25, 2024, at 8 a.m. PDT and closing on June 27, 2024, at 6 p.m. PDT. The second fishing period would occur 2 weeks later, beginning on July 9, 2024, at 8 a.m. PDT and closing on July 11, 2024, at 6 p.m. PDT.</P>
                <P>
                    Following the initial two fishing periods, NMFS will assess fishery harvest to date and determine if the fishery has attained the directed commercial allocation. If harvest estimates indicate the allocation has not been reached, NMFS may determine that subsequent fishing period(s) are necessary to attain the allocation. If a third fishing period occurs, it would occur no sooner than 3 weeks after the second fishing period. A third fishing period, and any subsequent fishing periods would be announced in the 
                    <E T="04">Federal Register</E>
                     through inseason action.
                </P>
                <HD SOURCE="HD1">Fishing Period Limits</HD>
                <P>A fishing period limit, also called a vessel catch limit, is the maximum amount of Pacific halibut that may be retained and landed by a vessel during one fishing period. Each vessel may retain no more than the current fishing period limit of Pacific halibut for its vessel class, which is determined by vessel length. NMFS is proposing directed commercial fishing period limits, shown in table 1 below, based on the 2024 directed fishery allocation, the number of permits issued by vessel size class, and participation and catch rates from prior years.</P>
                <P>For the 2024 fishing season, NMFS received 185 applications across 8 vessel size classes (A-H). Based on this number of permits and past fishery participation, NMFS anticipates similar vessel participation as has occurred in previous years. Therefore, NMFS is proposing that fishing period limits be grouped the same way as was done in previous years.</P>
                <P>Although the directed commercial allocation for 2024 is similar to the allocations for the previous 3 years, the average catch per vessel increased in 2023. Therefore, NMFS is proposing reduced fishing period limits compared to the previous 3 years. These fishing period catch limits are intended to ensure that the Area 2A directed commercial fishery does not exceed its allocation, while also providing fair and equitable access across participants to an attainable amount of harvest.</P>
                <P>If NMFS determines that more than two fishing periods are warranted, NMFS will set new fishing period limits and will set the fishing period limits for subsequent fishing periods equal across all vessel classes through inseason action.</P>
                <HD SOURCE="HD1">2024 Non-Tribal Directed Commercial Fishery Fishing Periods and Fishing Period Limits</HD>
                <P>The Area 2A non-tribal directed commercial fishery, which occurs south of Point Chehalis, WA, (lat. 46°53.30′ N) would open on June 25, 2024, at 8 a.m. PDT and close on June 27, 2024, at 6 p.m. PDT and would re-open July 9, 2024, at 8 a.m. PDT and close on July 11, 2024, at 6 p.m. PDT. The fishery may be adjusted inseason consistent with 50 CFR 300.63.</P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s25,20,20">
                    <TTITLE>Table 1—Fishing Period Limits by Size Class for the 2024 First and Second Fishing Periods of the Area 2A Pacific Halibut Non-Tribal Directed Commercial Fishery</TTITLE>
                    <BOXHD>
                        <CHED H="1">Vessel class</CHED>
                        <CHED H="1">
                            Length range
                            <LI>in feet</LI>
                            <LI>(meters)</LI>
                        </CHED>
                        <CHED H="1">
                            Fishing period
                            <LI>limit in pounds</LI>
                            <LI>(mt)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">A</ENT>
                        <ENT>1-25 (0.3-7.8)</ENT>
                        <ENT>1,800 (0.8164)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">B</ENT>
                        <ENT>26-30 (7.9-9.3)</ENT>
                        <ENT>1,800 (0.8164)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">C</ENT>
                        <ENT>31-35 (9.4-10.9)</ENT>
                        <ENT>1,800 (0.8164)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">D</ENT>
                        <ENT>36-40 (11.0-12.4)</ENT>
                        <ENT>3,000 (1.361)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">E</ENT>
                        <ENT>41-45 (12.5-13.9)</ENT>
                        <ENT>3,000 (1.361)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">F</ENT>
                        <ENT>46-50 (14.0-15.4)</ENT>
                        <ENT>3,800 (1.724)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">G</ENT>
                        <ENT>51-55 (15.5-16.9)</ENT>
                        <ENT>3,800 (1.724)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">H</ENT>
                        <ENT>56+ (17.0+)</ENT>
                        <ENT>4,500 (2.041)</ENT>
                    </ROW>
                    <TNOTE>
                        <E T="02">Note:</E>
                         Fishing period limits are in dressed weight (head-on, with ice and slime).
                    </TNOTE>
                </GPOTABLE>
                <PRTPAGE P="18370"/>
                <HD SOURCE="HD1">Classification</HD>
                <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 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. Such regulations shall only be implemented with the approval of the Secretary.</P>
                <P>This proposed rule is exempt from the procedures of E.O. 12866 because this action contains no implementing regulations.</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.</P>
                <P>For Regulatory Flexibility Act (RFA) purposes only, NMFS has established a small business size standard for businesses, including their affiliates, whose primary industry is commercial fishing (see 50 CFR 200.2). A business primarily engaged in commercial fishing (North American Industry Classification System code 114111) is classified as a small business if it is independently owned and operated, is not dominant in its field of operation (including its affiliates), and has combined annual receipts not in excess of $11 million for all its affiliated operations worldwide. The entities that would be affected by the proposed action are those vessels that harvest Pacific halibut as part of the non-tribal directed commercial fishery and are all considered small businesses under the above size standards.</P>
                <P>This proposed rule, if adopted, would establish the 2024 Area 2A non-tribal directed commercial fishery fishing periods and fishing period limits.</P>
                <P>There are no large entities involved in Pacific halibut fisheries off the West Coast. In 2023, NMFS issued 148 licenses to the commercial fishing fleet for the Area 2A non-tribal directed commercial fishery. Of those 148 vessels that obtained licenses, 50 percent (74 vessels) participated in the fishery. NMFS expects that a similar proportion of vessels will participate in the fishery this year and may be affected by these regulations. Cost data for the harvesting operations of non-tribal commercial halibut vessels is limited or unavailable. However, for 2023, the non-tribal directed allocation was 257,819 pounds (117 mt), of which approximately 259,226 pounds (118 mt) of Pacific halibut were harvested and resulted in a total fishery ex-vessel value of approximately $2.36 million. Therefore, NMFS considers all vessels affected by this action to be small entities.</P>
                <P>Since this action will only impact commercial fishing vessels, which in the Pacific halibut fishery are small entities, none of these changes will have a disproportionately negative effect on small entities versus large entities. Because each affected vessel is a small business, this proposed rule is considered to equally affect all of these small entities in the same manner. Therefore, this rule, if adopted, would not create disproportionate costs between small and large vessels/businesses.</P>
                <P>The major effect of Pacific halibut management on small entities is from the Area 2A allocation decided by the IPHC; a decision independent from this proposed action. This action proposes fishing periods and fishing period limits for the 2024 non-tribal directed commercial fishery consistent with recommendations from the Council to provide commercial harvest opportunities under the allocations that result from the Area 2A catch limit determined by the IPHC. Profitability is largely based on the total Area 2A allocation decided by the IPHC, with subarea allocations determined based on the allocation formulae in the Council's catch sharing plan. Therefore, the proposed rule, if adopted, is unlikely to affect the profitability of the commercial fishery.</P>
                <P>The Area 2A non-tribal directed commercial fishery allocation for 2024 is 249,338 pounds (113 mt), net weight, which is 3 percent lower than in 2023. This proposed rule, if adopted, is unlikely to affect overall participation in the directed commercial fishery since this action maintains an allocation similar to previous years. Profitability is dependent on the total amount of allocation available and market forces independent of this action. It is therefore highly unlikely that this proposed action would limit the fleet's potential profitability from catching halibut compared to last season or recent catch levels, as fishing periods and fishing period catch limits for 2024 are set using similar considerations as in previous years. Accordingly, vessel income from fishing is not expected to be altered as a result of this rule as it compares to recent catches in the fishery, including under the previous season's regulations.</P>
                <P>Based on the disproportionality and profitability analysis above, the proposed action, if adopted, will not have adverse or disproportional economic impact on these small business entities. As a result, an Initial Regulatory Flexibility Analysis is not required, and none has been prepared.</P>
                <P>This proposed rule contains no information collection requirements under the Paperwork Reduction Act of 1995.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> 16 U.S.C. 773-773k.</P>
                </AUTH>
                <SIG>
                    <DATED>Dated: March 7, 2024.</DATED>
                    <NAME>Samuel D. Rauch, III,</NAME>
                    <TITLE>Deputy Assistant Administrator for Regulatory Programs, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05289 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </PRORULE>
    </PRORULES>
    <VOL>89</VOL>
    <NO>50</NO>
    <DATE>Wednesday, March 13, 2024</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NOTICES>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18371"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <P>The Department of Agriculture has submitted the following information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13. Comments are requested regarding: 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; the accuracy of the agency's estimate of burden including the validity of the methodology and assumptions used; ways to enhance the quality, utility and clarity 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 appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology.</P>
                <P>
                    Comments regarding this information collection received by April 12, 2024 will be considered. 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.
                </P>
                <P>An agency may not conduct or sponsor a collection of information unless the collection of information displays a currently valid OMB control number and the agency informs potential persons who are to respond to the collection of information that such persons are not required to respond to the collection of information unless it displays a currently valid OMB control number.</P>
                <HD SOURCE="HD1">National Institute of Food and Agriculture</HD>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0524-0048.
                </P>
                <P>
                    <E T="03">Summary of Collection:</E>
                     The United States Department of Agriculture (USDA), National Institute of Food and Agriculture (NIFA) administer several competitive, peer-reviewed research, education, and extension programs, under which awards of high-priority are made. These programs are authorized pursuant to the authorities contained in the National Agricultural Research, Extension, and Teaching Policy Act of 1977, as amended (
                    <E T="03">7 U.S.C. 3101</E>
                    ), the Smith-Lever Act of 1914, as amended (
                    <E T="03">Pub. L. 107-293,</E>
                     2002) and other legislative authorities. NIFA also administers several formula funded research programs. The programs are authorized pursuant to the authorities contained in the McIntire-Stennis Cooperative Forestry Research Act of October 10, 1962 (
                    <E T="03">16 U.S.C. 582a-582a-7</E>
                    ) (McIntire-Stennis Act); the Hatch Act of 1887, as amended (
                    <E T="03">7 U.S.C. 361a-i</E>
                    ) (Hatch Act); Section 1445 of Public Law 95-113, the Food and Agriculture Act of 1977, as amended (
                    <E T="03">7 U.S.C. 3222</E>
                    ) (Pub. L. 95-113); Section 1433 of Subtitle E (Sections 1429-1439); Title XIV of Public Law 95-113, as amended (
                    <E T="03">7 U.S.C. 3191-3201</E>
                    ) (Pub. L. 95-113); the Smith-Lever Act; and the Renewable Resources Extension Act. Each formula funded program is also subject to requirements, which were revised in March 2000, and set forth in the Administrative Manual for the McIntire-Stennis Cooperative Forestry Research Program, the Administrative Manual for the Hatch Research Program, the Administrative Manual for the Evans-Allen Cooperative Agricultural Research Program, and the Administrative Manual for the Continuing Animal Health and Disease Research Program.
                </P>
                <P>
                    <E T="03">Need and Use of the Information:</E>
                     The collection of information is necessary in order to provide descriptive information regarding individual research, education, and integrated activities, to document expenditures and staff support for the activities, and to monitor the progress and impact of such activities. The information is collected primarily via the internet through a website that may be accessed via the NIFS Reporting Portal. The information provided helps users to keep abreast of the latest developments in utilization in specific target areas, plan for future activities; plan for resource allocation to research and education programs; avoid costly duplication of effort; aid in coordination of research and education efforts addressing similar problems in different location; and aid researchers and project directors in establishing valuable contacts with the agricultural community.
                </P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     Not-for-profit institutions; Business or other for-profit; Individuals or household; Federal Government; State, Local or Tribal Government.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     740.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     Reporting: Once per request.
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     62,415.
                </P>
                <SIG>
                    <NAME>Rachelle Ragland-Greene,</NAME>
                    <TITLE>Acting Departmental Information Collection Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05314 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">COMMISSION ON CIVIL RIGHTS</AGENCY>
                <SUBJECT>Notice of Public Meeting of the Arizona Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Commission on Civil Rights.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Announcement of virtual web briefing.</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 (FACA) that a web briefing of the Arizona Advisory Committee (Committee) to the U.S. Commission on Civil Right will convene via 
                        <E T="03">ZoomGov</E>
                         on Tuesday, March 26, 2024, from 12:00 p.m.-2:00 p.m. Arizona Time. The purpose of the web briefing is to collect testimony related to racial and ethnic disparities in pediatric healthcare in the state.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The web briefing will take place on:</P>
                    <P>Tuesday, March 26, 2024, from 12:00 p.m.-2:00 p.m. Arizona Time.</P>
                    <P>
                        <E T="03">Webinar Zoom Link to Join (Audio/Visual): https://www.zoomgov.com/webinar/register/WN_DH7gnikLTia44fWccVrg7g.</E>
                    </P>
                    <P>
                        <E T="03">Telephone (Audio Only) Dial:</E>
                         1-833-435-1820 (US Toll-free); Meeting ID: 160 401 9531.
                    </P>
                </DATES>
                <FURINF>
                    <PRTPAGE P="18372"/>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ana Fortes, DFO, at 
                        <E T="03">afortes@usccr.gov</E>
                         or (202) 681-0857.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Committee meetings are available to the public through the videoconference 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. Per the Federal Advisory Committee Act, public minutes of the meeting will include a list of persons who are present at the meeting. 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. Closed captioning will be available for individuals who are deaf, hard of hearing, or who have certain cognitive or learning impairments. To request additional accommodations, please email Angelica Trevino, Support Services Specialist, at 
                    <E T="03">atrevino@usccr.gov</E>
                     at least 10 business days prior to the meeting. Members of the public are entitled to make comments during the open period at the end of the meeting. Members of the public may also submit written comments; the comments must be received in the Regional Programs Unit within 30 days following the meeting. Written comments can be sent via email to Ana Fortes (DFO) at 
                    <E T="03">afortes@usccr.gov.</E>
                </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 meetings will be available via 
                    <E T="03">www.facadatabase.gov</E>
                     under the Commission on Civil Rights, Arizona 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 
                    <E T="03">atrevino@usccr.gov.</E>
                </P>
                <HD SOURCE="HD1">Agenda</HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. Introductory Remarks (12:00-12:10 p.m.)</FP>
                    <FP SOURCE="FP-2">II. Presentation (12:10-1:10 p.m.)</FP>
                    <FP SOURCE="FP-2">III. Q &amp; A (1:10-1:35 p.m.)</FP>
                    <FP SOURCE="FP-2">IV. Public Comment (1:35-1:50 p.m.)</FP>
                    <FP SOURCE="FP-2">V. Business Meeting (Tentative)</FP>
                    <FP SOURCE="FP-2">VI. Adjournment (2:00 p.m.)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: March 8, 2024.</DATED>
                    <NAME>David Mussatt,</NAME>
                    <TITLE>Supervisory Chief, Regional Programs Unit.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05324 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6335-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Foreign-Trade Zones Board</SUBAGY>
                <DEPDOC>[B-10-2024]</DEPDOC>
                <SUBJECT>Foreign-Trade Zone (FTZ) 183, Notification of Proposed Production Activity; Flextronics America, LLC; (Radio Frequency (RF) Communication Device Testers), Austin, Texas</SUBJECT>
                <P>Flextronics America, LLC submitted a notification of proposed production activity to the FTZ Board (the Board) for its facility in Austin, Texas within Subzone 183C. The notification conforming to the requirements of the Board's regulations (15 CFR 400.22) was received on March 7, 2024.</P>
                <P>
                    Pursuant to 15 CFR 400.14(b), FTZ production activity would be limited to the specific foreign-status material(s)/component(s) and specific finished product(s) described in the submitted notification (summarized below) and subsequently authorized by the Board. The benefits that may stem from conducting production activity under FTZ procedures are explained in the background section of the Board's website—accessible via 
                    <E T="03">www.trade.gov/ftz.</E>
                     The proposed finished product(s) and material(s)/component(s) would be added to the production authority that the Board previously approved for the operation, as reflected on the Board's website.
                </P>
                <P>The proposed finished product is a modular RF communication device tester (duty-free).</P>
                <P>The proposed foreign-status materials and components include: rubber seals; rubber bumpers; steel bolts; steel nuts; copper washers; copper cotters and cotter pins; copper screws and bolts; aluminum p-clamps; steel brackets; flat planel display monitors; indicator panels incorporating liquid crystal devices (LCDs); tantalum capacitors; thermistors; flexible printed circuit boards; slide switches; coaxial cable connectors; rack and panel cable connectors; mounted piezoelectric crystal oscillators; dynamic read-write random access (DRAM) integrated circuits; amplifier integrated circuits; modular RF communication device testers; printed circuit assemblies of modular RF communication device testers; and, chassis assemblies of modular RF communication device testers (plastic, steel, and aluminum) (duty rate ranges from duty-free to 3%).</P>
                <P>
                    Public comment is invited from interested parties. Submissions shall be addressed to the Board's Executive Secretary and sent to: 
                    <E T="03">ftz@trade.gov.</E>
                     The closing period for their receipt is April 22, 2024.
                </P>
                <P>A copy of the notification will be available for public inspection in the “Online FTZ Information System” section of the Board's website.</P>
                <P>
                    For further information, contact Kolade Osho at 
                    <E T="03">Kolade.Osho@trade.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 7, 2024.</DATED>
                    <NAME>Elizabeth Whiteman,</NAME>
                    <TITLE>Executive Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05264 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-588-880]</DEPDOC>
                <SUBJECT>Lightweight Thermal Paper From Japan: Rescission of Antidumping Duty Administrative Review; 2022-2023</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Department of Commerce (Commerce) is rescinding the administrative review of the antidumping duty (AD) order on lightweight thermal paper (thermal paper) from Japan for the period of review (POR) November 1, 2022, through October 31, 2023.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable March 13, 2024.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Rebecca Janz, AD/CVD Operations, Office II, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: (202) 482-2972.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On November 22, 2021, Commerce published in the 
                    <E T="04">Federal Register</E>
                     the AD order on thermal paper from Japan.
                    <SU>1</SU>
                    <FTREF/>
                     On November 2, 2023, Commerce published in the 
                    <E T="04">Federal Register</E>
                     a notice of opportunity to request an administrative review of the 
                    <E T="03">Order.</E>
                    <SU>2</SU>
                    <FTREF/>
                     On November 30, 2023, Lollicup USA Incorporated (Lollicup USA), a U.S. importer, submitted a timely request that Commerce conduct an administrative review of the 
                    <E T="03">Order</E>
                     with respect to Nippon Paper Industries Co., Ltd. and Nippon Paper Papylia Co., Ltd. (collectively, Nippon Paper), the 
                    <PRTPAGE P="18373"/>
                    producer and exporter of Lollicup USA's imports of subject merchandise.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Thermal Paper from Germany, Japan, the Republic of Korea, and Spain: Antidumping Duty Orders,</E>
                         86 FR 66284 (November 22, 2021) (
                        <E T="03">Order</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See Antidumping or Countervailing Duty Order, Finding, or Suspended Investigation; Opportunity to Request Administrative Review and Join Annual Inquiry Service List,</E>
                         88 FR 75270 (November 2, 2023).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Lollicup USA's Letter, “Administrative Review Request,” dated November 30, 2023. In the underlying investigation, Commerce determined it was appropriate to treat Nippon Paper Industries Co., Ltd. and Nippon Paper Papylia Co. Ltd. as a single entity. 
                        <E T="03">See Thermal Paper from Japan: Preliminary Affirmative Determination of Sales at Less Than Fair Value, Postponement of the Final Determination, and Extension of Provisional Measures,</E>
                         86 FR 26011 (May 12, 2021), and accompanying Preliminary Decision Memorandum at 7 n.2, unchanged in 
                        <E T="03">Thermal Paper from Japan: Final Affirmative Determination of Sales at Less Than Fair Value,</E>
                         86 FR 54157 (September 30, 2021). Given the lack of any information to the contrary on the record of this review, we continue to find it is appropriate to treat these companies as a single entity.
                    </P>
                </FTNT>
                <P>
                    On December 29, 2023, Commerce published in the 
                    <E T="04">Federal Register</E>
                     a notice of initiation of administrative review with respect to imports of thermal paper exported and/or produced by Nippon Paper, in accordance with section 751(a) of the Tariff Act of 1930, as amended (the Act), and 19 CFR 351.221(c)(1)(i).
                    <SU>4</SU>
                    <FTREF/>
                     On January 4, 2024, we placed on the record U.S. Customs and Border Protection (CBP) data for entries of thermal paper from Japan during the POR, showing no reviewable POR entries and invited interested parties to comment.
                    <SU>5</SU>
                    <FTREF/>
                     No interested party submitted comments to Commerce regarding the CBP data.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See Initiation of Antidumping and Countervailing Duty Administrative Reviews,</E>
                         88 FR 90168 (December 29, 2023).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Customs Entry Data from U.S. Customs and Border Protection,” dated January 4, 2024.
                    </P>
                </FTNT>
                <P>
                    Additionally, on February 9, 2024, Commerce notified all interested parties of its intent to rescind the instant review in full because there were no reviewable, suspended entries of subject merchandise by Nippon Paper during the POR and invited interested parties to comment.
                    <SU>6</SU>
                    <FTREF/>
                     No interested party submitted comments to Commerce in response to this notice.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Commerce's Letter, “Notice of Intent to Rescind Review,” dated February 9, 2024.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Rescission of Review</HD>
                <P>
                    Pursuant to 19 CFR 351.213(d)(3), it is Commerce's practice to rescind an administrative review of an AD order when there are no reviewable entries of subject merchandise during the POR for which liquidation is suspended.
                    <SU>7</SU>
                    <FTREF/>
                     Normally, upon completion of an administrative review, the suspended entries are liquidated at the AD assessment rate calculated for the review period.
                    <SU>8</SU>
                    <FTREF/>
                     Therefore, for an administrative review to be conducted, there must be a reviewable, suspended entry that Commerce can instruct CBP to liquidate at the AD assessment rate calculated for the review period.
                    <SU>9</SU>
                    <FTREF/>
                     As noted above, there were no entries of subject merchandise for Nippon Paper during the POR. Accordingly, in the absence of suspended entries of subject merchandise during the POR, we are hereby rescinding this administrative review, in its entirety, in accordance with 19 CFR 351.213(d)(3).
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See, e.g., Dioctyl Terephthalate from the Republic of Korea: Rescission of Antidumping Administrative Review; 2021-2022,</E>
                         88 FR 24758 (April 24, 2023); 
                        <E T="03">see also Certain Carbon and Alloy Steel Cut- to Length Plate from the Federal Republic of Germany: Recission of Antidumping Administrative Review; 2020-2021,</E>
                         88 FR 4157 (January 24, 2023).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         19 CFR 351.212(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         19 CFR 351.213(d)(3).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Assessment</HD>
                <P>
                    Commerce will instruct CBP to assess antidumping duties on all appropriate entries. Antidumping duties shall be assessed at rates equal to the cash deposit of estimated antidumping duties required at the time of entry, or withdrawal from warehouse, for consumption, in accordance with 19 CFR 351.212(c)(1)(i). Commerce intends to issue assessment instructions to CBP no earlier than 35 days after the date of publication of this rescission notice in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <HD SOURCE="HD1">Notification Regarding Administrative Protective Order</HD>
                <P>This notice serves as the only reminder to parties subject to administrative protective order (APO) of their responsibility concerning the disposition of proprietary information disclosed under APO in accordance with 19 CFR 351.305(a)(3). Timely written notification of the return or destruction of APO materials or conversion to judicial protective order is hereby requested. Failure to comply with the regulations and terms of an APO is a violation subject to sanction.</P>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>This notice is issued and published in accordance with sections 751(a)(1) and 777(i)(1) of the Act, and 19 CFR 351.213(d)(4).</P>
                <SIG>
                    <DATED>Dated: March 7, 2024.</DATED>
                    <NAME>James Maeder,</NAME>
                    <TITLE>Deputy Assistant Secretary for Antidumping and Countervailing Duty Operations.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05265 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Institute of Standards and Technology</SUBAGY>
                <DEPDOC>[Docket Number: 240305-0070]</DEPDOC>
                <SUBJECT>Manufacturing USA Institute Competition: AI for Resilient Manufacturing</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Institute of Standards and Technology, Department of Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Intent (NOI).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Office of Advanced Manufacturing within the National Institute of Standards and Technology, an agency of the U.S. Department of Commerce, intends to announce an open competition for a new Manufacturing USA institute. The expected competition will seek to establish a Manufacturing USA institute focused on the use of Artificial Intelligence to improve resilience of U.S. manufacturing. This NOI is provided to allow potential applicants sufficient time to develop meaningful collaborations among industry, academia, Federal laboratories and state/local government.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        All inquiries may be directed to Ms. Cheryl Leonard via email to 
                        <E T="03">ManufacturingUSA@nist.gov</E>
                         or by phone at (301) 975-4350, with a subject line stating: `AI for Manufacturing Resilience.' NIST will respond to questions received with answers to Frequently Asked Questions (FAQs) posted on the NIST competition website at 
                        <E T="03">https://www.nist.gov/oam/funding-opportunities.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Purpose.</E>
                     This Notice serves to announce the U.S. Department of Commerce's intention to initiate a competition to establish a new Manufacturing USA institute to strengthen U.S. industrial capabilities in advanced manufacturing sectors. The new institute will be sponsored by the Department of Commerce (DOC), through the National Institute of Standards and Technology (NIST). For this competition, NIST will solicit proposals for a Manufacturing USA institute to accelerate the use of 
                    <E T="03">artificial intelligence (AI) for resilient manufacturing.</E>
                </P>
                <P>
                    NIST will broadly compete the new institute, allowing applicants to focus on the use of AI to improve resilience of manufacturing within industries and sectors of national interest. The Manufacturing USA authorizing statute includes in the definition of a 
                    <PRTPAGE P="18374"/>
                    Manufacturing USA institute that an institute has a predominant focus on a manufacturing process, novel, material, enabling technology, supply chain integration methodology or another relevant aspect of advanced manufacturing such as nanotechnology applications, advanced ceramics, photonics and optics, composites, biobased and advanced materials, flexible hybrid technologies, tool development for microelectronics, food manufacturing, superconductors, advanced battery technologies, robotics, advanced sensors, quantum information science, supply chain water optimization, aeronautics and advanced materials, and graphene and graphene commercialization.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 278s(d)(1)(B), as amended. 
                        <E T="03">https://uscode.house.gov/view.xhtml?req=(title:15%20section:278s%20edition:prelim).</E>
                    </P>
                </FTNT>
                <P>
                    The newly awarded AI institute will join a network of 17 existing Manufacturing USA institutes sponsored by the U.S. Departments of Defense, Energy, and Commerce.
                    <SU>2</SU>
                    <FTREF/>
                     NIST intends that the new institute will both contribute to and benefit from the expertise within the existing network of institutes. As required by the Manufacturing USA authorizing statute, NIST will ensure that the AI institute to be established will not substantially duplicate the work of the existing network of institutes.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">www.manufacturingusa.com.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         15 U.S.C. 278s(e)(4)(A), as amended. 
                        <E T="03">https://uscode.house.gov/view.xhtml?req=(title:15%20section:278s%20edition:prelim).</E>
                    </P>
                </FTNT>
                <P>
                    The competition is expected to be announced in early Spring 2024 with a formal announcement on 
                    <E T="03">Grants.gov</E>
                     as well as on the NIST Office of Advanced Manufacturing website (
                    <E T="03">www.nist.gov/oam</E>
                    ) and Manufacturing USA website (
                    <E T="03">https://www.manufacturingusa.com/</E>
                    ).
                </P>
                <P>
                    <E T="03">Note that this NOI for an AI Manufacturing USA institute is separate from any planned solicitations for the Manufacturing USA semiconductor institute funded through the CHIPS Act</E>
                     
                    <SU>4</SU>
                    <FTREF/>
                      
                    <E T="03">and is separate from NIST's U.S. AI Safety Institute (USAISI). Interested parties should monitor https://www.nist.gov/chips/chips-rd-funding-opportunities</E>
                     for information regarding CHIPS-funded semiconductor institutes, and 
                    <E T="03">https://www.nist.gov/artificial-intelligence/artificial-intelligence-safety-institute</E>
                     for updates on the USAISI.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Title XCIX—Creating Helpful Incentives to Produce Semiconductors for America of the William M. (Mac) Thornberry National Defense Authorization Act for Fiscal Year 2021 (Pub. L. 116-283, often referred to as the CHIPS Act).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    <E T="03">Program Background:</E>
                     The Manufacturing USA Program: Manufacturing USA exists to secure U.S. global leadership in advanced manufacturing. The nine federal agencies 
                    <SU>5</SU>
                    <FTREF/>
                     participating in Manufacturing USA bring a whole-of-government approach to innovation, one that springboards U.S.-based inventions to the forefront of advanced manufacturing technologies, created and utilized by a skilled American workforce.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The federal agencies engaged in Manufacturing USA are the three sponsoring agencies, U.S. Departments of Commerce, Energy, and Defense, plus the Departments of Agriculture, Education, Health and Human Services, and Labor, NASA, and the National Science Foundation.
                    </P>
                </FTNT>
                <P>Each Manufacturing USA institute is a public-private partnership that brings together industry of all sizes, universities and community colleges, federal agencies, and state organizations to accelerate innovation by investing in industrially relevant pre-competitive advanced manufacturing technologies to advance specific technology sectors and develop the current and future workforce in those technologies. Manufacturing USA institutes are tasked to mature advanced manufacturing technologies from laboratory prototypes to industrial readiness, focusing on major industry challenges that can be addressed collaboratively but are generally beyond the reach of individual organizations. Institutes bridge the gap between basic research and commercial product development, provide shared assets allowing access to cutting-edge capabilities and equipment, and create accessible training resources to ensure that students and workers, including rural and underserved populations, have skills needed for careers in advanced manufacturing. Each Manufacturing USA institute also serves as a regional hub of manufacturing innovation, providing the innovation infrastructure to reinforce the competitiveness of the U.S. industrial base while strengthening our national and economic security.</P>
                <P>Manufacturing USA institutes may address the full spectrum of advanced manufacturing challenges, such as innovation for manufacturing processes, novel materials, cross cutting enabling technology, supply chain integration methodology and education and workforce development. Manufacturing USA institutes' federal funding catalyzes co-investment from non-federal sources for institute projects, promoting stable and sustainable business models.</P>
                <HD SOURCE="HD1">Competition Information</HD>
                <P>
                    <E T="03">Upcoming Manufacturing USA AI Institute Competition:</E>
                     Adoption of AI in manufacturing has the potential to increase productivity and efficiency, increase worker safety, allow for predictive maintenance to reduce or eliminate factory floor downtime, improve quality control and reduce waste and defects. AI adoption has the potential for efficient utilization of other digital technologies in optimizing product design and process flow, and energy management. Furthermore, adoption of AI technologies will also positively impact manufacturing supply chain management and resilience and has potential for scalable implementation of workforce development for all. Through the planned competition, NIST expects to select an applicant team most capable of establishing and leading a Manufacturing USA institute to accelerate the use of AI for strengthening resilience of manufacturing processes for the nation's manufacturers. The resulting institute is expected to integrate expertise in AI, manufacturing and optimization of supply chain networks to strengthen the resilience of domestic manufacturing. The institute will conduct applied R&amp;D projects and establish employer-led sectoral partnerships to develop accessible, effective, scalable training resources and credentialling pathways for the skilled workforce needed to move innovation into industrial practice. The work of the institute will also support the growth of an AI service provision infrastructure that will provide focused AI solutions to manufacturers by leveraging manufacturing data at national scale. Through these initiatives, the work of the institute will boost resilience to the benefit of individual companies and the overall U.S. manufacturing base. NIST anticipates that applicants for this upcoming funding opportunity will be permitted to choose an industrial sector of focus for the proposed institute, or to focus on cross-cutting tools that may be tailored for more than one industrial sector. Regardless of the applicant's choice, applicants will be required to define clear time-bounded deliverables and identify key partners needed to accomplish the work proposed and provide the non-federal co-investment that will be required to match the federal award (see Section 3 below). 
                    <E T="03">Applicants must also define the scope of the new institute to avoid substantive duplication with the existing network of Manufacturing USA institutes.</E>
                </P>
                <P>
                    It is anticipated that the awardee selected from the upcoming competition will lead the institute partners in activities such as establishing a trusted 
                    <PRTPAGE P="18375"/>
                    manufacturing-centric AI data commons, developing standards for AI risk assessment tools, creating validated and interoperable AI manufacturing and/or supply chain network models, and building shared testbeds to support the integration between software and hardware needed for deployment by U.S manufacturers. The institute will also be expected to support market transition of institute-developed technologies, ultimately supporting technology maturation into scale-up and industry use and to facilitate AI-related education and workforce development partnerships and programs.
                </P>
                <P>NIST expects the institute to achieve time-bound outcomes for technical applications that support manufacturing resilience, such as, but not limited to:</P>
                <P>• Accelerating qualification of new production technologies, facilities, or processes;</P>
                <P>• Performing predictive maintenance of structures and equipment to eliminate down-time due to equipment failure;</P>
                <P>• Optimizing manufacturing processes to reduce resource inputs and quality failures;</P>
                <P>• Optimizing working capital to predict inventory needs; and/or;</P>
                <P>• Predicting and mitigating risks from manufacturing supply chain network disruptions stemming from factors such as extreme climate events, while increasing visibility of potential domestic suppliers.</P>
                <P>
                    NIST intends that applications will be evaluated for merit and for alignment with program purposes and statutory requirements according to the authorizing legislation for Manufacturing USA, 15 U.S.C. 278s, and in 42 U.S.C. 18971, 
                    <E T="03">Expanding opportunities through the Manufacturing USA Program and</E>
                     42 U.S.C. 18972, 
                    <E T="03">Promoting domestic production of technologies developed under Manufacturing USA Program.</E>
                </P>
                <P>
                    <E T="03">Award Information:</E>
                     The U.S. Government intends to enter into a five-year agreement with the possibility of a non-competitive extension for up to an additional two (2) years and provide federal funding of up to $70 million. This funding is to be matched or exceeded by funding from private industry and other non-federal sources, with a required minimum 1:1 cost share. To provide the public with an opportunity to learn more about the solicitation before submitting a proposal, NIST will host a webinar and at least one in-person Proposer's Day. The exact date and location for the webinar and Proposer's Day(s) will be confirmed upon the release of the solicitation, anticipated to occur in early Spring 2024. In addition, a preliminary high-level webinar following the release of this Notice of Intent is planned. NIST also expects to post and update answers to Frequently Asked Questions in support of this NOI and the future competition. Interested applicants should monitor 
                    <E T="03">https://NIST.gov/oam</E>
                     for updates.
                </P>
                <P>
                    <E T="03">Application Process:</E>
                     NIST plans to use a two-stage process for soliciting applications for this directed-topic Manufacturing USA institute. Concept Papers will be considered in the first stage of competition, and applicants submitting the most meritorious concepts will be invited to submit full proposals in the second stage of the competition. To limit burden on applicants and the Federal Government, only a single concept paper may be submitted from a lead applicant entity. However, entities may be partners on multiple proposals submitted. NIST anticipates that the due date for submission of concept papers will be a minimum of 45 days from the publication of the funding opportunity announcement.
                </P>
                <P>In anticipation of the release of the funding opportunity, potential applicants are encouraged to complete the following preparations required for application submission:</P>
                <P>
                    • Ensure that your organization has a Unique Entity Identifier (UIE) with 
                    <E T="03">SAM.gov</E>
                    . The UIE has replaced the previous Dun and Bradstreet Data Universal Numbering System (DUNS) number. More information may be found at: 
                    <E T="03">https://sam.gov/content/entity-information.</E>
                </P>
                <P>
                    • Register with the System for Award Management (SAM) at 
                    <E T="03">https://www.sam.gov.</E>
                     Designating an Electronic Business Point of Contact (EBiz POC) and obtaining a special password called an MPIN are important steps in SAM registration. Please update your SAM registration annually.
                </P>
                <P>
                    • Register for a 
                    <E T="03">Grants.gov</E>
                     (
                    <E T="03">http://www.grants.gov/</E>
                    ) account. It is advisable also to go to “manage subscriptions” on 
                    <E T="03">Grants.gov</E>
                     and sign up to receive automatic updates when Amendments to a NOFO are posted.
                </P>
                <P>
                    <E T="03">Disclaimer. This NOI does not constitute a solicitation. No applications may be submitted in response to this NOI. NIST will post a future announcement to Grants.gov that will provide the full requirements for applying for an assistance award. When published, information within the Notice of Funding Opportunity will supersede in its entirety any information provided by this Notice. Any inconsistency between information within this Notice and the expected Notice of Funding Opportunity announcing NIST's AI for Manufacturing Resilience award competition shall be resolved in favor of the Notice of Funding Opportunity.</E>
                </P>
                <P>
                    <E T="03">Authority.</E>
                     Consolidated and Further Continuing Appropriations Act, 2015, Public Law 113-235, Title VII—Revitalize America Manufacturing Innovation Act of 2014, codified at 15 U.S.C. 278s, as amended.
                </P>
                <SIG>
                    <NAME>Alicia Chambers,</NAME>
                    <TITLE>NIST Executive Secretariat.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05228 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <DEPDOC>[RTID 0648-XD768]</DEPDOC>
                <SUBJECT>Atlantic Highly Migratory Species; Atlantic Bluefin Tuna Fishery Public Listening Session Regarding the Harpoon Category</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 meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NMFS will hold a public meeting to listen to concerns and gather input regarding the Atlantic Tunas Harpoon category fishery. During the meeting, stakeholders and the public may express their thoughts about harpooning practices, including concerns related to fishing activities in proximity to mobile-gear vessels and harpooning during nighttime hours.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The public meeting will be held on March 28, 2024, from 10 a.m. to 12 p.m. ET.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The meeting will be accessible via WebEx webinar/conference call. Webinar access information will be available at: 
                        <E T="03">https://www.fisheries.noaa.gov/event/public-listening-session-atlantic-tunas-harpoon-category-fishery.</E>
                    </P>
                    <P>
                        Participants accessing the webinar are strongly encouraged to log/dial in 15 minutes prior to the meeting. Requests for sign language interpretation or other auxiliary aids should be directed to Anna Quintrell (see 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section) at least 7 days prior to the meeting.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Anna Quintrell, 
                        <E T="03">anna.quintrell@noaa.gov,</E>
                         or Larry Redd, 
                        <E T="03">larry.redd@noaa.gov,</E>
                         at 301-427-8503.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Atlantic highly migratory species (HMS) 
                    <PRTPAGE P="18376"/>
                    fisheries, including the bluefin tuna (BFT) fisheries, are managed under the 2006 Consolidated HMS Fishery Management Plan and its amendments pursuant to the Magnuson-Stevens Fishery Conservation and Management Act (16 U.S.C. 1801 
                    <E T="03">et seq.</E>
                    ) and consistent with the Atlantic Tunas Convention Act (16 U.S.C. 971 
                    <E T="03">et seq.</E>
                    ). HMS implementing regulations are at 50 CFR part 635.
                </P>
                <P>In response to petitions for rulemaking submitted in 2021 and 2023, NMFS has engaged in deliberations regarding the management of the Harpoon category fishery for BFT. The petitioners advocated for regulatory measures to limit harpoon fishing near vessels using mobile gear that is used to fish for groundfish, scallops, or clams and to restrict the deployment of floating bait for the purpose of attracting BFT to the surface for harpooning. The petitioners felt the practices were contrary to the traditional method of fishing with harpoon gear, would cause the Harpoon category quota to be filled too quickly, and would cause safety issues. The petitioners also advocated for fishing with harpoon gear only during the day and prohibiting nighttime fishing due to safety concerns.</P>
                <P>During the September 2023 HMS Advisory Panel meeting, stakeholders were invited to provide public comment on the aforementioned petitions. NMFS recognized the significance of ongoing dialogue and indicated the possibility of further discussions on the matter in the future.</P>
                <P>The upcoming listening session allows NMFS to hear from stakeholders and the public regarding any insights, concerns, and recommendations pertaining to the Harpoon category in general and the aforementioned petitions.</P>
                <P>For this meeting, we anticipate hearing from the public about the following topics:</P>
                <P>• Recent harpooning practices and techniques in the BFT fishery;</P>
                <P>• Recent harpooning activities in the BFT fishery in proximity to mobile-gear vessels;</P>
                <P>• The impact of nighttime harpooning; and,</P>
                <P>• Thoughts about the potential regulatory changes regarding the Harpoon category fishery.</P>
                <P>The public is reminded that NMFS expects participants of the meeting to conduct themselves appropriately. At the beginning of the meeting, the moderator will explain how the meeting will be conducted and how and when participants can provide comments. NMFS will structure the meeting so that all members of the public will be able to comment. Participants are expected to respect the ground rules, and those that do not may be asked to leave.</P>
                <SIG>
                    <DATED>Dated: March 7, 2024.  </DATED>
                    <NAME>Everett Wayne Baxter,</NAME>
                    <TITLE>Acting Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05299 Filed 3-12-24; 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-XD656]</DEPDOC>
                <SUBJECT>Magnuson-Stevens Act Provisions; General Provisions for Domestic Fisheries; Application for Exempted Fishing Permits</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; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Assistant Regional Administrator for Sustainable Fisheries, Greater Atlantic Region, NMFS, has made a preliminary determination that an Exempted Fishing Permit (EFP) application contains all of the required information and warrants further consideration. The EFP would allow federally permitted fishing vessels to fish outside fishery regulations in support of exempted fishing activities proposed by Coonamessett Farm Foundation. Regulations under the Magnuson-Stevens Fishery Conservation and Management Act require publication of this notification to provide interested parties the opportunity to comment on applications for proposed EFPs.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before April 12, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit written comments by email at 
                        <E T="03">nmfs.gar.efp@noaa.gov.</E>
                         Include in the subject line “CFF Great South Channel HMA Clam EFP.”
                    </P>
                    <P>
                        All comments received are a part of the public record and will generally be posted for public viewing in 
                        <E T="03">https://www.noaa.gov/organization/information-technology/foia-reading-room</E>
                         without change. All personal identifying information (
                        <E T="03">e.g.,</E>
                         name, address), confidential business information, or otherwise sensitive information submitted voluntarily by the sender will be publicly accessible. NMFS will accept anonymous comments (enter “anonymous” as the signature if you wish to remain anonymous).
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Douglas Potts, Fishery Policy Analyst, 
                        <E T="03">douglas.potts@noaa.gov,</E>
                         978-281-9341.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The applicant submitted a complete application for an EFP to conduct commercial fishing activities that the regulations would otherwise restrict. This EFP would exempt the participating vessels from the following Federal regulations:</P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s45,r50,r50">
                    <TTITLE>Table 1—Requested Exemptions</TTITLE>
                    <BOXHD>
                        <CHED H="1">CFR citation</CHED>
                        <CHED H="1">Regulation</CHED>
                        <CHED H="1">
                            Need for
                            <LI>exemption</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">50 CFR 648.370(h)</ENT>
                        <ENT>Habitat Management Areas—prohibition on using bottom-tending mobile gear</ENT>
                        <ENT>To conduct compensation fishing with hydraulic clam dredges.</ENT>
                    </ROW>
                </GPOTABLE>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s50,r150">
                    <TTITLE>Table 2—Project Summary</TTITLE>
                    <BOXHD>
                        <CHED H="1">Project title</CHED>
                        <CHED H="1">Compensation fishing in support of a Great South Channel Habitat Management Area study phase II: an acoustic mapping survey of Davis Bank East</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Division action number</ENT>
                        <ENT>DA23-073.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Principal Investigator</ENT>
                        <ENT>Natalie Jennings.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Institution</ENT>
                        <ENT>Coonamessett Farm Foundation (CFF).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Continuing project (yes/no)</ENT>
                        <ENT>Yes.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Initial application date</ENT>
                        <ENT>September 26, 2023.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Complete application date</ENT>
                        <ENT>December 5, 2023.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Funding source</ENT>
                        <ENT>Compensation fishing.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Project Start</ENT>
                        <ENT>Upon issue.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Project End</ENT>
                        <ENT>1 year from issue.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="18377"/>
                        <ENT I="01">Project objectives</ENT>
                        <ENT>Compensation surfclam fishing to fund a habitat mapping project using multibeam sonar and drop cameras.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Project location</ENT>
                        <ENT>Great South Channel Habitat Management Area, Davis Bank East.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Number of vessels</ENT>
                        <ENT>3 (2 active with 1 in reserve).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Number of trips</ENT>
                        <ENT>260.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Trip duration (days)</ENT>
                        <ENT>1.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Total number of days</ENT>
                        <ENT>260.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Gear type(s)</ENT>
                        <ENT>Hydraulic clam dredge.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Number of tows or sets</ENT>
                        <ENT>30 per trip.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Duration of tows or sets</ENT>
                        <ENT>0.16 hrs.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Project Narrative</HD>
                <HD SOURCE="HD2">Acoustic Survey Trips</HD>
                <P>An initial survey of the full Davis Bank East area (approximately 60 square kilometers) would be conducted using multibeam sonar and a drop camera array, lasting approximately 8 and 6 days, respectively. This would establish a baseline to monitor changes in fished and unfished portions of the area. Following the initial survey, research trips would consist of one 4-day trip per season (16 total days) in the northern half of the area. The survey would be conducted with a 25-percent overlap between adjacent multibeam lines. Sonar imagery would be processed for bathymetry and backscatter. In addition, a 2-day research trip would occur seasonally (8 total days) using a drop camera array to ground-truth the sonar imagery and provide benthic community biological information. Drop camera survey trips would be conducted concurrent with the sonar survey trips. Four drops per hour would be accomplished for 12 hours for 2 days, with a goal of approximately 96 stations sampled per trip. Time of day, sea state and weather conditions, GPS coordinates, depth, and time on bottom will be recorded at each drop camera station. The drop camera is a 4-foot-tall, four-sided pyramid outfitted with lights and a high-resolution Sony camera with a 1-meter-squared field of view. A final multibeam sonar and drop camera survey of the full Davis Bank East area would be conducted again lasting approximately 8 and 6 days, respectively. All survey trips would be directed by two CFF scientists onboard the vessel. No fishing gear will be deployed during survey trips. CFF will submit a separate application for a letter of acknowledgment of scientific research for these survey cruises.</P>
                <HD SOURCE="HD2">Compensation Fishing Trips</HD>
                <P>The EFP would authorize the harvest of surfclams from an area closed to hydraulic clam dredges for the purpose of generating funds for the acoustic survey. After the initial acoustic survey is completed, two commercial surfclam vessels would take up to 130 trips (260 total trips) into the southern portion of the Davis Bank East area defined by these coordinates:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s25,r25">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Latitude</CHED>
                        <CHED H="1">Longitude</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">41.268° N</ENT>
                        <ENT>69.58° W.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">41.268° N</ENT>
                        <ENT>69.508° W.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">41.223° N</ENT>
                        <ENT>69.566° W.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">41.223° N</ENT>
                        <ENT>69.508° W.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Both vessels would use a 48-inch-wide hydraulic surfclam dredge, towed between 2 and 3 knots for 10 minutes per tow, with a trip limit of 14 cages. Approximately 30 tows would be conducted per trip. A CFF scientist would be onboard 25 percent of compensation fishing trips to collect surfclam catch per unit effort and catch composition data. The vessel owners have committed 15 percent of the value of each trip to cover the full cost of the research trips and data analysis. At an estimated $30 per bushel ex-vessel value, this would just cover the total research budget of roughly $505,000. The participating vessel owners have agreed to make up the difference if the price falls below $30 per bushel.</P>
                <P>If approved, the applicant may request minor modifications and extensions to the EFP throughout the year. EFP modifications and extensions may be granted without further notice if they are deemed essential to facilitate completion of the proposed research and have minimal impacts that do not change the scope or impact of the initially approved EFP request. Any fishing activity conducted outside the scope of the exempted fishing activity would be prohibited.</P>
                <P>
                    <E T="03">Authority:</E>
                     16 U.S.C. 1801 
                    <E T="03">et seq.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 7, 2024.</DATED>
                    <NAME>Everett Wayne Baxter,</NAME>
                    <TITLE>Acting Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05271 Filed 3-12-24; 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-XD753]</DEPDOC>
                <SUBJECT>New England 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 New England Fishery Management Council's is convening its Scientific and Statistical Committee (SSC) sub-panel to consider actions affecting New England fisheries in the exclusive economic zone (EEZ). Recommendations from this group will be brought to the full Council for formal consideration and action, if appropriate.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This webinar will be held on Wednesday, March 27, 2024, at 1 p.m.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        <E T="03">Webinar registration information: https://attendee.gotowebinar.com/register/6027689206954658393.</E>
                         Call in information: +1 (415) 930-5321, Access Code: 210-165-122.
                    </P>
                    <P>
                        <E T="03">Council address:</E>
                         New England Fishery Management Council, 50 Water Street, Mill 2, Newburyport, MA 01950.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Cate O'Keefe, Executive Director, New England Fishery Management Council; telephone: (978) 465-0492.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Agenda</HD>
                <P>
                    A Scientific and Statistical Committee sub-panel will meet to review the 
                    <PRTPAGE P="18378"/>
                    methods of a management strategy evaluation (MSE) for Atlantic cod and give input on possible scenarios to simulate through the MSE. This MSE aims to support the Council's ongoing decision-making process for how to manage Atlantic cod given the recent review of cod stock structure that resulted in shifting from two biological units (Gulf of Maine and Georges Bank) to five units. This MSE aims to quantify the relative performance of candidate spatial management procedures. The sub-panel will formulate suggestions for the MSE team to consider and may reconvene later in 2024 to review progress. Other business will be discussed as necessary.
                </P>
                <P>Although non-emergency issues not contained on the agenda may come before this Council for discussion, those issues may not be the subject of formal action during this meeting. Council action will be restricted to those issues specifically listed in this notice and any issues arising after publication of this notice that require emergency action under section 305(c) of the Magnuson-Stevens Act, provided the public has been notified of the Council's intent to take final action to address the emergency. The public also should be aware that the meeting will be recorded. Consistent with 16 U.S.C. 1852, a copy of the recording is available upon request.</P>
                <HD SOURCE="HD1">Special Accommodations</HD>
                <P>This meeting is physically accessible to people with disabilities. Requests for sign language interpretation or other auxiliary aids should be directed to Cate O'Keefe, Executive Director, at (978) 465-0492, at least 5 days prior to the meeting date.</P>
                <P>
                    <E T="03">Authority:</E>
                     16 U.S.C. 1801 
                    <E T="03">et seq.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 6, 2024.</DATED>
                    <NAME>Rey Israel Marquez,</NAME>
                    <TITLE>Acting Deputy Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05460 Filed 3-12-24; 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-XD793]</DEPDOC>
                <SUBJECT>Marine Mammals; File No. 27938</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; receipt of application.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given that BBC Studios, Ltd., Whiteladies Road, Bristol, BS8 2LR, UK (Emily-Kate Moorhead, Responsible Party) has applied in due form for a permit to conduct commercial and educational photography on marine mammals.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments must be received on or before April 12, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        These documents are available upon written request via email to 
                        <E T="03">NMFS.Pr1Comments@noaa.gov.</E>
                    </P>
                    <P>
                        Written comments on this application should be submitted via email to 
                        <E T="03">NMFS.Pr1Comments@noaa.gov.</E>
                         Please include File No. 27938 in the subject line of the email comment.
                    </P>
                    <P>
                        Those individuals requesting a public hearing should submit a written request via email to 
                        <E T="03">NMFS.Pr1Comments@noaa.gov.</E>
                         The request should set forth the specific reasons why a hearing on this application would be appropriate.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Shasta McClenahan, Ph.D., or Amy Hapeman, (301) 427-8401.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The subject permit is requested under the authority of the Marine Mammal Protection Act of 1972, as amended (MMPA; 16 U.S.C. 1361 
                    <E T="03">et seq.</E>
                    ), the regulations governing the taking and importing of marine mammals (50 CFR part 216).
                </P>
                <P>The applicant proposes to film up to 13 species of non-listed marine mammals in the New York Bight for a wildlife documentary series. Filming may occur from land, vessel, underwater (pole or drop-in camera), and unmanned aircraft system platform. See the application for species, life stages, and numbers of animals by filming platform. The permit is requested for 2 years.</P>
                <P>
                    In compliance with the National Environmental Policy Act of 1969 (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), an initial determination has been made that the activity proposed is categorically excluded from the requirement to prepare an environmental assessment or environmental impact statement.
                </P>
                <P>
                    Concurrent with the publication of this notice in the 
                    <E T="04">Federal Register</E>
                    , NMFS is forwarding copies of the application to the Marine Mammal Commission and its Committee of Scientific Advisors.
                </P>
                <SIG>
                    <DATED>Dated: March 7, 2024.</DATED>
                    <NAME>Julia M. Harrison,</NAME>
                    <TITLE>Chief, Permits and Conservation Division, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05263 Filed 3-12-24; 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-XD721]</DEPDOC>
                <SUBJECT>Takes of Marine Mammals Incidental to Specified Activities; Taking Marine Mammals Incidental to the Parallel Thimble Shoal Tunnel Project, Virginia Beach, Virginia</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Issuance of an incidental harassment authorization.</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 an incidental harassment authorization (IHA) to the Chesapeake Tunnel Joint Venture (CTJV) to incidentally harass marine mammals during construction associated with the Parallel Thimble Shoal Tunnel Project (PTST) in Virginia Beach, Virginia.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This authorization is effective from February 15, 2024, through February 14, 2025.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        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/national/marine-mammal-protection/incidental-take-authorizations-construction-activities.</E>
                         In case of problems accessing these documents, please call the contact listed below.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Robert Pauline, Office of Protected Resources, NMFS, (301) 427-8401.</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 IHA is provided to the public for review.
                </P>
                <P>
                    Authorization for incidental takings shall be granted if NMFS finds that the 
                    <PRTPAGE P="18379"/>
                    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>On July 28, 2023, NMFS received a request from CTJV for an IHA to take marine mammals incidental to in-water construction activities associated with the PTST project near Virginia Beach, VA. Following NMFS' review of the initial application, CTJV submitted several revised versions of the application based on NMFS' comments. The final version was submitted on November 7, 2023, and was deemed adequate and complete on November 13, 2023. CTJV's request is for take of 5 species by Level B harassment and, for a subset of three of these species, by Level A harassment. Neither CTJV nor NMFS expect serious injury or mortality to result from this activity and, therefore, an IHA is appropriate.</P>
                <P>
                    NMFS most recently issued an IHA to CTJV for similar work on November 8, 2022, (87 FR 68462; November 15, 2022). CTJV complied with all the requirements (
                    <E T="03">e.g.,</E>
                     mitigation, monitoring, and reporting) of the previous IHA, and information regarding their monitoring results may be found in the Estimated Take section.
                </P>
                <P>This final IHA will cover 1 year of a larger project for which CTJV obtained IHAs for similar work (83 FR 36522, July 30, 2018; 85 FR 16061, March 20, 2020; 86 FR 14606, March 17, 2021; 86 FR 67024, November 24, 2021; and 87 FR 68462, November 15, 2022). The larger multi-year PTST project consists of the construction of a two-lane parallel tunnel to the west of the existing Thimble Shoal Tunnel, connecting Portal Island Nos. 1 and 2 as part of the 23-mile Chesapeake Bay Bridge-Tunnel (CBBT) facility.</P>
                <HD SOURCE="HD1">Description of Activity</HD>
                <HD SOURCE="HD2">Overview</HD>
                <P>The purpose of the project is to build an additional two lane vehicle tunnel under the navigation channel as part of the CBBT. The PTST project will address existing constraints to regional mobility based on current traffic volume, improve safety, improve the ability to conduct necessary maintenance with minimal impact to traffic flow, and ensure reliable hurricane evacuation routes. In-water construction work will include the removal of a total of 158 36-inch steel piles on the temporary dock and trestle on Portal Islands Nos. 1 and 2 as well as the removal of steel mooring piles on both Portal Islands (97 total on Portal Island No.1); the removal of 36″ steel piles on the trestle (34 total on Portal Island No. 2); and the removal of 36″ steel mooring piles on both Island 1 (9 piles) and Island No. 2 (18 piles). All steel piles are hollow pipe piles. The planned impact and vibratory pile removal activities can introduce sound into the water environment which can result in take of marine mammals by behavioral harassment and, for some species, by auditory injury. Planned construction activities are expected to be completed from January-April as well as in December 2024. Note that the term “pile driving” is only used to refer to pile removal activities. No pile installation activities are planned by CTJV.</P>
                <P>The in-water removal of a total of 158 piles will occur over 80 days. Removal will begin on Portal Island No. 1 in January through April 2024 for 54 days then will resume on Portal Island No. 2 in December 2024 for 26 days. No pile removal work will take place in the interim. The project schedule is shown in table 1. The IHA is effective from February 15, 2024, through February 14, 2025.</P>
                <BILCOD>BILLING CODE 3510-22-P</BILCOD>
                <GPH SPAN="3" DEEP="488">
                    <PRTPAGE P="18380"/>
                    <GID>EN13MR24.004</GID>
                </GPH>
                <BILCOD>BILLING CODE 3510-22-C</BILCOD>
                <GPOTABLE COLS="9" OPTS="L2,nj,p7,7/8,i1" CDEF="s50,r50,r50,r55,r25,7,9,r35,r55">
                    <TTITLE>Table 1—Anticipated Pile Installation Schedule (January 2024-December 2024)</TTITLE>
                    <BOXHD>
                        <CHED H="1">Pile location</CHED>
                        <CHED H="1">Pile function</CHED>
                        <CHED H="1">Pile type</CHED>
                        <CHED H="1">
                            Installation/
                            <LI>removal method</LI>
                        </CHED>
                        <CHED H="1">
                            Bubble
                            <LI>curtain</LI>
                            <LI>yes/no</LI>
                        </CHED>
                        <CHED H="1">Number of piles</CHED>
                        <CHED H="1">
                            Number of days per activity
                            <LI>(total)</LI>
                        </CHED>
                        <CHED H="1">
                            Number of piles/days per activity
                            <LI>(per hammer type)</LI>
                        </CHED>
                        <CHED H="1">
                            Anticipated
                            <LI>installation date</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Portal Island No. 1</ENT>
                        <ENT>Mooring dolphins</ENT>
                        <ENT>36-inch Diameter Steel Pipe Pile</ENT>
                        <ENT>
                            Impact (if needed)
                            <LI>Vibratory (Removal)</LI>
                        </ENT>
                        <ENT>
                            Yes
                            <LI>Yes</LI>
                        </ENT>
                        <ENT>9</ENT>
                        <ENT>
                            5
                            <LI>5</LI>
                        </ENT>
                        <ENT>
                            (2 Piles/Day)
                            <LI>(2 Piles/Day)</LI>
                        </ENT>
                        <ENT>1 January through 28 February 2024.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Portal Island No. 1</ENT>
                        <ENT>Temporary Dock/Trestle</ENT>
                        <ENT>36-inch Diameter Steel Interlocked Pipe Piles</ENT>
                        <ENT>
                            Impact (if needed)
                            <LI>Vibratory (Removal)</LI>
                        </ENT>
                        <ENT>
                            Yes
                            <LI>Yes</LI>
                        </ENT>
                        <ENT>97</ENT>
                        <ENT>
                            49
                            <LI>49</LI>
                        </ENT>
                        <ENT>
                            (2 Piles/Day)
                            <LI>(2 Piles/Day)</LI>
                        </ENT>
                        <ENT>1 January through 30 April 2024.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Portal Island No. 2</ENT>
                        <ENT>Mooring dolphins</ENT>
                        <ENT>36-inch Diameter Steel Pipe Pile</ENT>
                        <ENT>
                            Impact (if needed)
                            <LI>Vibratory (Removal)</LI>
                        </ENT>
                        <ENT>
                            Yes
                            <LI>Yes</LI>
                        </ENT>
                        <ENT>18</ENT>
                        <ENT>
                            9
                            <LI>9</LI>
                        </ENT>
                        <ENT>
                            (2 Piles/Day)
                            <LI>(2 Piles/Day)</LI>
                        </ENT>
                        <ENT>December 1-31, 2024.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Portal Island No. 2</ENT>
                        <ENT>Omega Trestle</ENT>
                        <ENT>36-inch Diameter Steel Interlocked Pipe Piles</ENT>
                        <ENT>
                            Impact (if needed)
                            <LI>Vibratory (Removal)</LI>
                        </ENT>
                        <ENT>
                            Yes
                            <LI>Yes</LI>
                        </ENT>
                        <ENT>34</ENT>
                        <ENT>
                            17
                            <LI>17</LI>
                        </ENT>
                        <ENT>
                            (2 Piles/Day)
                            <LI>(2 Piles/Day)</LI>
                        </ENT>
                        <ENT>December 1-31, 2024</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="18381"/>
                <P>
                    A detailed description of the planned construction project is provided in the 
                    <E T="04">Federal Register</E>
                     notice for the proposed IHA (88 FR 89385, December 27, 2023). Since that time, no changes have been made to the planned activities. Therefore, a detailed description is not provided here. Please refer to that 
                    <E T="04">Federal Register</E>
                     notice for the description of the specific activity.
                </P>
                <P>Mitigation, monitoring, and reporting measures are described in detail later in this document (please see Mitigation and Monitoring and Reporting).</P>
                <HD SOURCE="HD1">Comments and Responses</HD>
                <P>
                    A notice of NMFS' proposal to issue an IHA to CTJV was published in the 
                    <E T="04">Federal Register</E>
                     on December 27, 2023 (88 FR 89385). That notice described, in detail, CTJV's activities, the marine mammal species that may be affected by the activities, and the anticipated effects on marine mammals. In that notice, we requested public input on the request for authorization described therein, our analyses, the proposed authorization, and any other aspect of the notice of proposed IHA, and requested that interested persons submit relevant information, suggestions, and comments. This proposed notice was available for a 30-day public comment period. No comments were submitted during the 30-day public comment period,
                </P>
                <HD SOURCE="HD1">Changes From the Proposed IHA to Final IHA</HD>
                <P>
                    Since the 
                    <E T="04">Federal Register</E>
                     notice of the proposed IHA was published (88 FR 89385, December 27, 2023), NMFS published the 2023 Draft Atlantic Marine Mammal Stock Assessment Report, which provide updates to the harbor porpoise Gulf of Maine/Bay of Fundy stock and the gray seal Western North Atlantic stock abundances, Potential Biological Removal values (PBRs), and Annual Mortality/Serious Injury values (Annual M/SI). Updates have been made to Table 2 Species Likely Impacted by the Specified Activities as well as to our analysis of take (see Estimated Take) and small numbers determinations (see Small Numbers).
                </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. NMFS fully considered all of this information, and we refer the reader to these descriptions, instead of reprinting the information. Additional information regarding population trends and threats may be found in NMFS' Stock Assessment Reports (SARs; 
                    <E T="03">https://www.fisheries.noaa.gov/national/marine-mammal-protection/marine-mammal-stock-assessments</E>
                     and 2023 Draft SARS; 
                    <E T="03"> https://www.federalregister.gov/documents/2024/01/29/2024-01653/draft-2023-marine-mammal-stock-assessment-reports</E>
                    ) and more general information about these species (
                    <E T="03">e.g.,</E>
                     physical and behavioral descriptions) may be found on NMFS' website (
                    <E T="03">https://www.fisheries.noaa.gov/find-species).</E>
                </P>
                <P>Table 2 lists all species or stocks for which take is expected and authorized for this activity 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. 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' SARs). While no serious injury or 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 or stocks 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' 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' U.S. Atlantic and Gulf of Mexico SARs (Hayes 
                    <E T="03">et al.</E>
                     2023) and 2023 Draft SARS; 
                    <E T="03"> https://www.federalregister.gov/documents/2024/01/29/2024-01653/draft-2023-marine-mammal-stock-assessment-reports.</E>
                     All values presented in table 2 are the most recent available at the time of publication and are available online at: 
                    <E T="03">https://www.fisheries.noaa.gov/national/marine-mammal-protection/marine-mammal-stock-assessments.</E>
                </P>
                <GPOTABLE COLS="7" OPTS="L2,p7,7/8,i1" CDEF="s50,r50,r50,xls30,r40,8,9">
                    <TTITLE>Table 2—Species Likely Impacted by the Specified Activities</TTITLE>
                    <BOXHD>
                        <CHED H="1">Common name</CHED>
                        <CHED H="1">Scientific name</CHED>
                        <CHED H="1">Stock</CHED>
                        <CHED H="1">
                            ESA/
                            <LI>MMPA</LI>
                            <LI>status;</LI>
                            <LI>strategic</LI>
                            <LI>
                                (Y/N) 
                                <SU>1</SU>
                            </LI>
                        </CHED>
                        <CHED H="1">
                            Stock abundance
                            <LI>
                                (CV, N
                                <E T="0732">min</E>
                                , most recent
                            </LI>
                            <LI>
                                abundance survey) 
                                <SU>2</SU>
                            </LI>
                        </CHED>
                        <CHED H="1">PBR</CHED>
                        <CHED H="1">
                            Annual
                            <LI>
                                M/SI 
                                <SU>3</SU>
                            </LI>
                        </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 Balaenopteridae (rorquals):</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">Humpback whale</ENT>
                        <ENT>
                            <E T="03">Megaptera novaeangliae</E>
                        </ENT>
                        <ENT>Gulf of Maine</ENT>
                        <ENT>-,-; N</ENT>
                        <ENT>1,393 (0; 1,375, 2016)</ENT>
                        <ENT>22</ENT>
                        <ENT>12.15</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <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">Bottlenose dolphin</ENT>
                        <ENT>
                            <E T="03">Tursiops truncatus</E>
                        </ENT>
                        <ENT>WNA Coastal, Northern Migratory</ENT>
                        <ENT>-,-; Y</ENT>
                        <ENT>6,639 (0.41; 4,759; 2016)</ENT>
                        <ENT>48</ENT>
                        <ENT>12.2-21.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>WNA Coastal, Southern Migratory</ENT>
                        <ENT>-,-; Y</ENT>
                        <ENT>3,751 (0.06; 2,353; 2016)</ENT>
                        <ENT>24</ENT>
                        <ENT>0-18.3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>Northern North Carolina Estuarine System</ENT>
                        <ENT>-,-; Y</ENT>
                        <ENT>823 (0.06; 782; 2017)</ENT>
                        <ENT>7.8</ENT>
                        <ENT>7.2-30</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Family Phocoenidae (porpoises):</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">Harbor porpoise</ENT>
                        <ENT>
                            <E T="03">Phocoena phocoena</E>
                        </ENT>
                        <ENT>Gulf of Maine/Bay of Fundy</ENT>
                        <ENT>-, -; N</ENT>
                        <ENT>85,765 (0.53, 56,420, 2021)</ENT>
                        <ENT>649</ENT>
                        <ENT>145</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <PRTPAGE P="18382"/>
                        <ENT I="21">
                            <E T="02">Order Carnivora—Superfamily Pinnipedia</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <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>WNA</ENT>
                        <ENT>-, -; N</ENT>
                        <ENT>61,336 (0.08, 57,637, 2018)</ENT>
                        <ENT>1,729</ENT>
                        <ENT>339</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">
                            Gray seal 
                            <SU>4</SU>
                        </ENT>
                        <ENT>
                            <E T="03">Halichoerus grypus</E>
                        </ENT>
                        <ENT>WNA</ENT>
                        <ENT>-, -; N</ENT>
                        <ENT>27,911 (0.0, 23,624, 2021)</ENT>
                        <ENT>1,512</ENT>
                        <ENT>4,570</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">https://www.fisheries.noaa.gov/national/marine-mammal-protection/marine-mammal-stock-assessment-reports.</E>
                         CV is coefficient of variation; N
                        <E T="0732">min</E>
                         is the minimum estimate of stock abundance.
                    </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/Serious Injury (M/SI) often cannot be determined precisely and is in some cases presented as a minimum value or range.
                    </TNOTE>
                    <TNOTE>
                        <SU>4</SU>
                         The NMFS stock abundance estimate applies to U.S. population only, however the actual stock abundance is approximately 505,000. The PBR value is estimated for the U.S. population, while the M/SI estimate is provided for the entire gray seal stock (including animals in Canada).
                    </TNOTE>
                </GPOTABLE>
                <P>
                    A detailed description of the species likely to be affected by the construction project, including a brief introduction to the affected stock 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 (88 FR 89385, December 27, 2023). Please refer to the 
                    <E T="04">Federal Register</E>
                     notice of the proposed IHA for the full description for all species. 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 3.
                </P>
                <GPOTABLE COLS="2" OPTS="L2,nj,i1" CDEF="s150,r50">
                    <TTITLE>Table 3—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 
                    <E T="03">et al.</E>
                     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 produced by CTJV's construction activities has the potential to result in behavioral harassment of marine mammals in the vicinity of the survey area. The 
                    <E T="04">Federal Register</E>
                     notice of the proposed IHA (88 FR 89385, December 27, 2023) included a discussion of the effects of anthropogenic noise on marine mammals and the potential effects of underwater noise from CTJV's construction activities on marine mammals and their habitat. That information and analysis is incorporated by reference into this final IHA determination and is not repeated here; please refer to the notice of the 
                    <PRTPAGE P="18383"/>
                    proposed IHA (88 FR 89385, December 27, 2023).
                </P>
                <HD SOURCE="HD1">Estimated Take</HD>
                <P>This section provides an estimate of the number of incidental takes authorized through the IHA, which will inform both NMFS' consideration of “small numbers,” and the negligible impact determinations.</P>
                <P>Harassment is the only type of take 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 will primarily be by Level B harassment, as use of the acoustic sources (
                    <E T="03">i.e.,</E>
                     impact and vibratory driving) has the potential to result in disruption of behavioral patterns for individual marine mammals. There is also some potential for auditory injury (Level A harassment) to result, primarily for high frequency species and phocids because predicted auditory injury zones are larger than for mid-frequency species. Auditory injury is unlikely to occur for mid-frequency species. The required mitigation and monitoring measures are expected to minimize the severity of the taking to the extent practicable.
                </P>
                <P>As described previously, no serious injury or mortality is anticipated or authorized for this activity. Below we describe how the 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 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 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). 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 estimate the onset of behavioral harassment. NMFS generally predicts that marine mammals are likely to be behaviorally harassed 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 for non-explosive impulsive (
                    <E T="03">e.g.,</E>
                     seismic airguns) or intermittent (
                    <E T="03">e.g.,</E>
                     scientific sonar) sources. Generally speaking, Level B harassment take estimates based on these behavioral harassment thresholds are expected to include any likely takes by TTS as, in most cases, the likelihood of TTS occurs at distances from the source less than those at which behavioral harassment is likely. TTS of a sufficient degree can manifest as behavioral harassment, as reduced hearing sensitivity and the potential reduced opportunities to detect important signals (conspecific communication, predators, prey) may result in changes in behavior patterns that would not otherwise occur. CTJV's planned activities include the use of continuous (vibratory pile driving) and impulsive (impact pile driving) sources, and therefore the RMS SPL thresholds of 120 and 160 dB re 1 μPa are applicable.
                </P>
                <P>
                    <E T="03">Level A Harassment</E>
                    —NMFS' Technical Guidance for Assessing the Effects of Anthropogenic Sound on Marine 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). CTJV's planned pile driving activities includes the use of impulsive (impact pile driving) and non-impulsive (vibratory pile driving) sources.
                </P>
                <P>
                    These thresholds are provided in table 4 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 4—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>
                            <E T="03">:</E>
                             219 dB; 
                            <E T="03">L</E>
                            <E T="0732">E,LF,24h</E>
                            <E T="03">:</E>
                             183 dB
                        </ENT>
                        <ENT>
                            <E T="03">Cell 2: L</E>
                            <E T="0732">E,LF,24h</E>
                            <E T="03">:</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>
                            <E T="03">:</E>
                             230 dB; 
                            <E T="03">L</E>
                            <E T="0732">E,MF,24h</E>
                            <E T="03">:</E>
                             185 dB
                        </ENT>
                        <ENT>
                            <E T="03">Cell 4: L</E>
                            <E T="0732">E,MF,24h</E>
                            <E T="03">:</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>
                            <E T="03">:</E>
                             202 dB; 
                            <E T="03">L</E>
                            <E T="0732">E,HF,24h</E>
                            <E T="03">:</E>
                             155 dB
                        </ENT>
                        <ENT>
                            <E T="03">Cell 6: L</E>
                            <E T="0732">E,HF,24h</E>
                            <E T="03">:</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>
                            <E T="03">:</E>
                             218 dB; 
                            <E T="03">L</E>
                            <E T="0732">E,PW,24h</E>
                            <E T="03">:</E>
                             185 dB
                        </ENT>
                        <ENT>
                            <E T="03">Cell 8: L</E>
                            <E T="0732">E,PW,24h</E>
                            <E T="03">:</E>
                             201 dB.
                        </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="18384"/>
                        <ENT I="01">Otariid Pinnipeds (OW) (Underwater)</ENT>
                        <ENT>
                            <E T="03">Cell 9: L</E>
                            <E T="0732">pk,flat</E>
                            <E T="03">:</E>
                             232 dB; 
                            <E T="03">L</E>
                            <E T="0732">E,OW,24h</E>
                            <E T="03">:</E>
                             203 dB
                        </ENT>
                        <ENT>
                            <E T="03">Cell 10: L</E>
                            <E T="0732">E,OW,24h</E>
                            <E T="03">:</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 are used in estimating the area ensonified above the acoustic thresholds, including source levels and transmission loss coefficient.</P>
                <P>
                    The sound field in the project area is the existing background noise plus additional construction noise from the planned project. Marine mammals are expected to be affected via sound generated by the primary components of the project (
                    <E T="03">i.e.,</E>
                     pile driving).
                </P>
                <P>The project includes vibratory and impact pile driving. Source levels for these activities are based on reviews of measurements of the same or similar types and dimensions of piles available in the literature. Source levels for each pile size and activity are presented in table 5. Source levels for vibratory removal of piles of the same diameter are assumed to be the same. Note that CTJV will employ a bubble curtain during all impact and vibratory driving activities which NMFS assumes will reduce source levels by 5 dB.</P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,r50,12,12,12,r50">
                    <TTITLE>Table 5—Estimates of Mean Underwater Sound Levels Generated During Vibratory and Impact Pile Driving</TTITLE>
                    <BOXHD>
                        <CHED H="1">Pile type</CHED>
                        <CHED H="1">Hammer type</CHED>
                        <CHED H="1">Peak</CHED>
                        <CHED H="1">RMS</CHED>
                        <CHED H="1">SSsel</CHED>
                        <CHED H="1">Source</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">36-in steel pipe</ENT>
                        <ENT>Impact/(with −5 dB bubble curtain)</ENT>
                        <ENT>210/(205)</ENT>
                        <ENT>193/(188)</ENT>
                        <ENT>183/(178)</ENT>
                        <ENT>Caltrans 2015, 2020.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Vibratory/(with −5 dB bubble curtain)</ENT>
                        <ENT>180/(175)</ENT>
                        <ENT>170/(165)</ENT>
                        <ENT/>
                        <ENT>Caltrans 2015.</ENT>
                    </ROW>
                    <TNOTE>
                        <E T="02">Note:</E>
                         CTJV will incorporate bubble curtain with a 5 dB reduction for all pile driving activities.
                    </TNOTE>
                </GPOTABLE>
                <P>
                    Transmission loss (
                    <E T="03">TL</E>
                    ) is the decrease in acoustic intensity as an acoustic pressure wave propagates out from a source. 
                    <E T="03">TL</E>
                     parameters vary with frequency, temperature, sea conditions, current, source and receiver depth, water depth, water chemistry, and bottom composition and topography. The general formula for underwater 
                    <E T="03">TL</E>
                     is:
                </P>
                <FP SOURCE="FP-2">
                    <E T="03">TL</E>
                     = 
                    <E T="03">B</E>
                     * Log10 (
                    <E T="03">R</E>
                    1/
                    <E T="03">R</E>
                    2),
                </FP>
                <EXTRACT>
                    <FP SOURCE="FP-2">where</FP>
                    <FP SOURCE="FP-2">
                        <E T="03">TL</E>
                         = transmission loss in dB 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">B</E>
                         = transmission loss coefficient 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">R</E>
                        1 = the distance of the modeled SPL from the driven pile, and 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">R</E>
                        2 = the distance from the driven pile of the initial measurement
                    </FP>
                </EXTRACT>
                <P>Absent site-specific acoustical monitoring with differing measured transmission loss, a practical spreading value of 15 is used as the transmission loss coefficient in the above formula. Site-specific transmission loss data for the PTST project area are not available; therefore, the default coefficient of 15 is used to determine the distances to the Level A harassment and Level B harassment thresholds.</P>
                <P>The ensonified area associated with Level A harassment is more technically challenging to predict due to the need to account for a duration component. Therefore, NMFS developed an optional User Spreadsheet tool to accompany the Technical Guidance that can be used to relatively simply predict an isopleth distance for use in conjunction with marine mammal density or occurrence to help predict potential takes. We note that because of some of the assumptions included in the methods underlying this optional tool, we anticipate that the resulting isopleth estimates are typically going to be overestimates of some degree, which may result in an overestimate of potential take by Level A harassment. However, this optional tool offers the best way to estimate isopleth distances when more sophisticated modeling methods are not available or practical. For stationary sources, such as pile driving, the optional User Spreadsheet tool predicts the distance at which, if a marine mammal remained at that distance for the duration of the activity, it would be expected to incur PTS. Inputs used in the optional User Spreadsheet tool are shown in table 6, and the resulting estimated isopleths are shown in table 7, as reported below.</P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s50,12,12">
                    <TTITLE>Table 6—User Spreadsheet Inputs</TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">36-inch steel piles</CHED>
                        <CHED H="2">Vibratory</CHED>
                        <CHED H="2">Impact</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Source Level (SPL)</ENT>
                        <ENT>170 RMS</ENT>
                        <ENT>183 SEL</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="18385"/>
                        <ENT I="01">Transmission Loss Coefficient</ENT>
                        <ENT>15</ENT>
                        <ENT>15</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Weighting Factor Adjustment (kHz)</ENT>
                        <ENT>2.5</ENT>
                        <ENT>2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Activity Duration per day (minutes)</ENT>
                        <ENT>30</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Number of strikes per pile</ENT>
                        <ENT/>
                        <ENT>240</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Number of piles per day</ENT>
                        <ENT>2</ENT>
                        <ENT>2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Distance of sound pressure level measurement</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                    </ROW>
                </GPOTABLE>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,r25,r25,r25,r25,r25">
                    <TTITLE>Table 7—Calculated Level A and Level B Harassment Isopleths </TTITLE>
                    <TDESC>[Meters]</TDESC>
                    <BOXHD>
                        <CHED H="1">Scenario</CHED>
                        <CHED H="1">Level A harassment zones</CHED>
                        <CHED H="2">LF</CHED>
                        <CHED H="2">MF</CHED>
                        <CHED H="2">HF</CHED>
                        <CHED H="2">Phocid pinnipeds</CHED>
                        <CHED H="1">
                            Level B 
                            <LI>harassment zones</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">Driving Type:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Pile Type</ENT>
                        <ENT>Island 1 &amp; 2</ENT>
                        <ENT>Island 1 &amp; 2</ENT>
                        <ENT>Island 1 &amp; 2</ENT>
                        <ENT>Island 1 &amp; 2</ENT>
                        <ENT>Island 1 &amp; 2.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">36-in Impact (with Bubble Curtain):</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">36-in. Steel</ENT>
                        <ENT>285</ENT>
                        <ENT>10</ENT>
                        <ENT>338</ENT>
                        <ENT>152</ENT>
                        <ENT>736.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">36-in Vibratory (with Bubble Curtain):</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">36-in. Steel</ENT>
                        <ENT>8</ENT>
                        <ENT>1</ENT>
                        <ENT>12</ENT>
                        <ENT>5</ENT>
                        <ENT>10,000.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD2">Marine Mammal Occurrence and Take Estimation</HD>
                <P>
                    In this section we provide information about the occurrence of marine mammals, including density or other relevant information which will inform the take calculations as well as how the information provided is synthesized to produce a quantitative estimate of the take that is reasonably likely to occur and authorized for take. Several approaches were utilized to estimate take for affected species depending on the best data that was available. For some species, survey or observational data was used to estimate take (
                    <E T="03">e.g.</E>
                     harbor seal, gray seal). If density data was available, it was employed to develop the take estimate (
                    <E T="03">i.e.,</E>
                     bottlenose dolphin). In cases where the best available information consisted only of very low density values, NMFS assumed the average group to arrive at an estimate (
                    <E T="03">i.e.,</E>
                     humpback whale, harbor porpoise).
                </P>
                <HD SOURCE="HD2">Humpback Whale</HD>
                <P>
                    Humpback whales are rare in the Chesapeake Bay. Density data for this species within the project vicinity were not available. Habitat-based density models produced by the Duke University Marine Geospatial Ecology Laboratory (Roberts 
                    <E T="03">et al.</E>
                     2016) represent the best available information regarding marine mammal densities offshore near the mouth of the Chesapeake Bay. At the closest point to the PTST project area, humpback densities showed a maximum monthly density of 0.107/100 km
                    <SU>2</SU>
                     in March. Because humpback whale occurrence is low, as mentioned above, the CTJV estimated, and NMFS concurred, that there will be a single humpback sighting every two months for the duration of in-water pile driving activities. There are 5 months of planned in-water construction. Using an average group size of two animals Kraus 
                    <E T="03">et al.</E>
                     (2016) and 5 months of active in-water pile driving work (Jan, Feb, Mar, Apr, Dec) provides an estimate of four takes during the January-April period. NMFS conservatively assumed that there will be an additional sighting of 2 humpback whales in December. Because it is expected that a full shutdown can occur before the mammal can reach the full extent of the Level A harassment zone, no takes by Level A harassment were requested or are authorized. Therefore, NMFS has authorized six takes of humpback whale by Level B harassment.
                </P>
                <HD SOURCE="HD2">Bottlenose Dolphin</HD>
                <P>
                    There was insufficient monitoring data available from previous PTST IHAs to estimate dolphin take. Therefore, the expected number of bottlenose dolphins was estimated using a 2016 report on the occurrence, distribution, and density of marine mammals near Naval Station Norfolk and Virginia Beach, Virginia (Engelhaupt 
                    <E T="03">et al.</E>
                     2016). This report provides seasonal densities of bottlenose dolphins for inshore areas in the vicinity of the project and along the coast of Virginia Beach. Like most wildlife, bottlenose dolphins do not use habitat uniformly. The heterogeneity in available habitat, dietary items and protection likely results in some individuals preferring ocean and others estuary (Ballance 1992; Gannon and Waples 2004). Dolphins clearly have the ability to move between these habitat types. Gannon and Waples (2004) suggest individuals prefer one habitat over the other based on gut contents of dietary items. Therefore, a subset of survey data from Engelhaupt 
                    <E T="03">et al.</E>
                     (2016) was used to determine seasonal dolphin densities within the project area. A spatially refined approach was used by plotting dolphin sightings within a 12 km radius of the planned project location. Densities were determined following methodology outlined in Engelhaupt 
                    <E T="03">et al.</E>
                     2016 and Miller 
                    <E T="03">et al.</E>
                     2019 using the package DISTANCE in R statistical software (R. Core Team 2018). Calculated densities by season are provided in table 8.
                </P>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s50,15">
                    <TTITLE>
                        Table 8—Densities (Individual/
                        <E T="01">km</E>
                        <SU>2</SU>
                        ) of Bottlenose Dolphin From Inshore Areas of Virginia
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">Season</CHED>
                        <CHED H="1">
                            12 km 
                            <LI>distance </LI>
                            <LI>around </LI>
                            <LI>PTST project area</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Spring</ENT>
                        <ENT>1.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Winter</ENT>
                        <ENT>0.63</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    This information was then used to calculate the monthly takes based on the number of pile driving days per month. These were broken out by month as shown in table 9. The Level B harassment area for each pile and driving type was multiplied by the 
                    <PRTPAGE P="18386"/>
                    appropriate seasonal density and the anticipated number of days per activity per month to derive the total number of takes for each activity. Given this information, NMFS is authorizing 12,256 Level B harassment exposures for bottlenose dolphins. No take by Level A harassment has been authorized by NMFS since the shutdown zone is 20 m and should be readily visible to PSOs.
                </P>
                <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="s50,12,12,12,12,12,12">
                    <TTITLE>Table 9—Estimated Takes of Bottlenose Dolphin by Level B Harassment by Month, Location, and Driving Activity</TTITLE>
                    <BOXHD>
                        <CHED H="1">Month</CHED>
                        <CHED H="1">Jan</CHED>
                        <CHED H="1">Feb</CHED>
                        <CHED H="1">Mar</CHED>
                        <CHED H="1">Apr</CHED>
                        <CHED H="1">Dec</CHED>
                        <CHED H="1">Totals</CHED>
                    </BOXHD>
                    <ROW RUL="s">
                        <ENT I="01">
                            Dolphin Density (/km
                            <SU>2</SU>
                            )
                        </ENT>
                        <ENT>0.63</ENT>
                        <ENT>0.63</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>0.63</ENT>
                        <ENT/>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Impact: Portal Island 1 Mooring Dolphins (9 Piles)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">
                            Refined Area(/km
                            <SU>2</SU>
                            )
                        </ENT>
                        <ENT>1.38</ENT>
                        <ENT>1.38</ENT>
                        <ENT>1.38</ENT>
                        <ENT>1.38</ENT>
                        <ENT>1.38</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Driving Days</ENT>
                        <ENT>2</ENT>
                        <ENT>3</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Dolphin Harassments</ENT>
                        <ENT>2</ENT>
                        <ENT>3</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>5</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Vibratory: Portal Island 1 Mooring Dolphins (9 Piles)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">
                            Refined Area(/km
                            <SU>2</SU>
                            )
                        </ENT>
                        <ENT>212</ENT>
                        <ENT>212</ENT>
                        <ENT>212</ENT>
                        <ENT>212</ENT>
                        <ENT>212</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Driving Days</ENT>
                        <ENT>2</ENT>
                        <ENT>3</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Dolphin Harassments</ENT>
                        <ENT>268</ENT>
                        <ENT>401</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>669</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Impact: Portal Island 2 Mooring Dolphins (18 Piles)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">
                            Refined Area(/km
                            <SU>2</SU>
                            )
                        </ENT>
                        <ENT>1.32</ENT>
                        <ENT>1.32</ENT>
                        <ENT>1.32</ENT>
                        <ENT>1.32</ENT>
                        <ENT>1.32</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Driving Days</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>9</ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Dolphin Harassments</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>8</ENT>
                        <ENT>8</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Vibratory: Portal Island 2 Mooring Dolphins (18 Piles)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">
                            Refined Area(/km
                            <SU>2</SU>
                            )
                        </ENT>
                        <ENT>202</ENT>
                        <ENT>202</ENT>
                        <ENT>202</ENT>
                        <ENT>202</ENT>
                        <ENT>202</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Driving Days</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>9</ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Dolphin Harassments</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>1,146</ENT>
                        <ENT>1,146</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Impact: Portal Island 1 Trestle/Dock Removal (97 Piles)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">
                            Refined Area(/km
                            <SU>2</SU>
                            )
                        </ENT>
                        <ENT>1.38</ENT>
                        <ENT>1.38</ENT>
                        <ENT>1.38</ENT>
                        <ENT>1.38</ENT>
                        <ENT>1.38</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Driving Days</ENT>
                        <ENT>13</ENT>
                        <ENT>15</ENT>
                        <ENT>13</ENT>
                        <ENT>8</ENT>
                        <ENT>0</ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Dolphin Harassments</ENT>
                        <ENT>12</ENT>
                        <ENT>14</ENT>
                        <ENT>18</ENT>
                        <ENT>12</ENT>
                        <ENT>0</ENT>
                        <ENT>56</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Vibratory: Portal Island 1 Trestle/Dock Removal (97 Piles)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">
                            Refined Area(/km
                            <SU>2</SU>
                            )
                        </ENT>
                        <ENT>212</ENT>
                        <ENT>212</ENT>
                        <ENT>212</ENT>
                        <ENT>212</ENT>
                        <ENT>212</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Driving Days</ENT>
                        <ENT>13</ENT>
                        <ENT>15</ENT>
                        <ENT>13</ENT>
                        <ENT>8</ENT>
                        <ENT>0</ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Dolphin Harassments</ENT>
                        <ENT>1,737</ENT>
                        <ENT>2,004</ENT>
                        <ENT>2,756</ENT>
                        <ENT>1,696</ENT>
                        <ENT>0</ENT>
                        <ENT>8,193</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Impact: Portal Island 2 Trestle Removal (34 Piles)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">
                            Refined Area(/km
                            <SU>2</SU>
                            )
                        </ENT>
                        <ENT>1.32</ENT>
                        <ENT>1.32</ENT>
                        <ENT>1.32</ENT>
                        <ENT>1.32</ENT>
                        <ENT>1.32</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Driving Days</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>17</ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Dolphin Harassments</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>15</ENT>
                        <ENT>15</ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">Vibratory: Portal Island 2 Trestle Removal (34 Piles)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">
                            Refined Area(/km
                            <SU>2</SU>
                            )
                        </ENT>
                        <ENT>202</ENT>
                        <ENT>202</ENT>
                        <ENT>202</ENT>
                        <ENT>202</ENT>
                        <ENT>202</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Driving Days</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>17</ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Dolphin Harassments</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>2,164</ENT>
                        <ENT>2,164</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>12,256</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The total number of bottlenose dolphin Level B harassment events will be split between three bottlenose dolphin stocks: Western North Atlantic Southern Migratory Coastal; Western North Atlantic Northern Migratory Coastal; and NNCES. There is insufficient information to apportion the requested takes precisely to each of these three stocks present in the project area. Given that most of the NNCES stock are found in the Pamlico Sound estuarine system, it is assumed that no greater than 200 of the takes will be from this stock. Since members of the Western North Atlantic Northern Migratory Coastal and Western North Atlantic Southern Migratory Coastal stocks are thought to occur in or near the project area in greater numbers, we conservatively assume that no more than half of the remaining animals will belong to either of these stocks.</P>
                <P>
                    Additionally, a subset of these takes will likely be comprised of Chesapeake Bay resident dolphins, although the size of that population is unknown. It is assumed that an animal will be taken once over a 24-hour period; however, the same individual may be taken multiple times over the duration of the project. Therefore, the number of takes 
                    <PRTPAGE P="18387"/>
                    for each stock is assumed to overestimate the actual number of individuals that may be affected.
                </P>
                <HD SOURCE="HD2">Harbor Porpoise</HD>
                <P>
                    Harbor porpoises are known to occur in the coastal waters near Virginia Beach (Hayes 
                    <E T="03">et al.</E>
                     2019), and although they have been reported on rare occasions in the Chesapeake Bay near the project area, they have not been seen by the Protected Species Observers in the PTST project area during the construction. Density data for this species within the project vicinity do not exist or were not calculated because sample sizes were too small to produce reliable estimates of density. Additionally, harbor porpoise sighting data collected by the U.S. Navy near Naval Station Norfolk and Virginia Beach from 2012 to 2015 (Engelhaupt 
                    <E T="03">et al.</E>
                     2014, 2015, 2016) did not produce high enough sample sizes to calculate densities.
                </P>
                <P>
                    One group of two harbor porpoises was seen during spring 2015 (Engelhaupt 
                    <E T="03">et al.</E>
                     2016). Therefore, it is assumed that there are two harbor porpoises exposed to noise exceeding harassment levels each month during the spring (March-April) for a total of four harbor porpoises (
                    <E T="03">i.e.,</E>
                     1 group of 2 individuals per month × 2 months per year = 4 harbor porpoises). Harbor porpoises are not expected to be present in the summer, fall or winter. Harbor porpoises are members of the high-frequency hearing group which will have Level A harassment isopleths as large as 338 m during impact driving of 36″ steel pile, while the Level B harassment zone is 736 m. Given the relatively large Level A harassment zones for HF cetaceans during impact driving and a required shutdown zone of 200 m, NMFS will assume that 30 percent of porpoises are taken by Level A harassment. Therefore, NMFS is authorizing take of three porpoises by Level B harassment and one porpoise by Level A harassment.
                </P>
                <HD SOURCE="HD2">Harbor Seal</HD>
                <P>
                    The expected number of harbor seals in the project area was estimated using systematic, land and vessel-based survey data for in-water and hauled-out seals collected by the U.S. Navy at the CBBT rock armor and Portal Islands from November 2014 through April 2022 (Rees 
                    <E T="03">et al.</E>
                     2016; Jones 
                    <E T="03">et al.</E>
                     2018; Jones and Rees 2020; Jones and Rees 2021; Jones and Rees 2022; Jones and Rees 2023) and shown in table 10. The number of harbor seals sighted by month ranged from 0 to 170 individuals.
                </P>
                <GPOTABLE COLS="11" OPTS="L2,p7,7/8,i1" CDEF="s25,10,10,10,10,10,10,10,10,10,10">
                    <TTITLE>Table 10—Summary of Historical Harbor Seal Sightings by Month From 2014 to 2022 at the Chesapeake Bay Bridge Tunnel</TTITLE>
                    <BOXHD>
                        <CHED H="1">Month</CHED>
                        <CHED H="1">2014</CHED>
                        <CHED H="1">2015</CHED>
                        <CHED H="1">2016</CHED>
                        <CHED H="1">2017</CHED>
                        <CHED H="1">2018</CHED>
                        <CHED H="1">2019</CHED>
                        <CHED H="1">2020</CHED>
                        <CHED H="1">2021</CHED>
                        <CHED H="1">2022</CHED>
                        <CHED H="1">
                            Monthly 
                            <LI>average</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">January</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>33</ENT>
                        <ENT>120</ENT>
                        <ENT>170</ENT>
                        <ENT>7</ENT>
                        <ENT>18</ENT>
                        <ENT>49</ENT>
                        <ENT>34</ENT>
                        <ENT>61.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">February</ENT>
                        <ENT/>
                        <ENT>39</ENT>
                        <ENT>80</ENT>
                        <ENT>106</ENT>
                        <ENT>159</ENT>
                        <ENT>21</ENT>
                        <ENT>0</ENT>
                        <ENT>43</ENT>
                        <ENT>14</ENT>
                        <ENT>57.7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">March</ENT>
                        <ENT/>
                        <ENT>55</ENT>
                        <ENT>61</ENT>
                        <ENT>41</ENT>
                        <ENT>0</ENT>
                        <ENT>18</ENT>
                        <ENT>6</ENT>
                        <ENT>26</ENT>
                        <ENT>37</ENT>
                        <ENT>30.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">April</ENT>
                        <ENT/>
                        <ENT>10</ENT>
                        <ENT>1</ENT>
                        <ENT>3</ENT>
                        <ENT>3</ENT>
                        <ENT>4</ENT>
                        <ENT>0</ENT>
                        <ENT>6</ENT>
                        <ENT>1</ENT>
                        <ENT>3.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">December</ENT>
                        <ENT>4</ENT>
                        <ENT>9</ENT>
                        <ENT>24</ENT>
                        <ENT>8</ENT>
                        <ENT>29</ENT>
                        <ENT>0</ENT>
                        <ENT>4</ENT>
                        <ENT>11</ENT>
                        <ENT>11</ENT>
                        <ENT>12.5</ENT>
                    </ROW>
                    <TNOTE>
                        <E T="02">Note:</E>
                         Seal counts began in November 2014 and were collected for 9 field seasons (2014/2015, 2015/2016, 2016/2017, 2017/2018, 2018/2019, 2019/2020, 2020/2021, 2021/2022) ending in 2022. In January 2015, no surveys were conducted.
                    </TNOTE>
                </GPOTABLE>
                <P>Seal density data are in the format of seal per unit time; therefore, seal take requests were calculated as total number of potential seals per pile driving day (8 hours) multiplied by the number of driving days per month. For example, in December seal density data is reported at 14.3 seals per day × 26 workdays in December, resulting in the potential of 372 instances of take for that month (table 11). The anticipated number of take events were summed across the months during which in-water pile driving is planned. The largest Level A harassment isopleth for phocid species is 153 m which will occur when piles are being removed via impact hammer with a bubble curtain. The smallest Level A harassment zone is 1 m which will occur when piles are removed via vibratory hammer with a bubble curtain. NMFS is requiring a shutdown zone for harbor seals of 100 m during impact driving which will theoretically result in no take by Level A harassment. However, a small number of harbor seals could enter into the shutdown zone unseen by a PSO and remain for sufficient duration to incur PTS. Given that harbor seals are common in the project area, NMFS assumed that a single harbor seal will experience Level A harassment during each in-water work day (80). Therefore, NMFS is authorizing the take of 80 harbor seals by Level A harassment and 2,634 harbor seals by Level B harassment for a total of 2,714 takes (table 11).</P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,12,12,12">
                    <TTITLE>Table 11—Calculation of the Number of Harbor Seal Takes</TTITLE>
                    <BOXHD>
                        <CHED H="1">Month</CHED>
                        <CHED H="1">Estimated seals per work day</CHED>
                        <CHED H="1">
                            Total pile 
                            <LI>driving days </LI>
                            <LI>per month</LI>
                        </CHED>
                        <CHED H="1">Total number of requested takes</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">January 2024</ENT>
                        <ENT>61.6</ENT>
                        <ENT>15</ENT>
                        <ENT>924</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">February 2024</ENT>
                        <ENT>57.8</ENT>
                        <ENT>18</ENT>
                        <ENT>1,040</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">March 2024</ENT>
                        <ENT>30.5</ENT>
                        <ENT>13</ENT>
                        <ENT>396.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">April 2024</ENT>
                        <ENT>3.5</ENT>
                        <ENT>8</ENT>
                        <ENT>28</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">December 2024</ENT>
                        <ENT>12.5</ENT>
                        <ENT>26</ENT>
                        <ENT>325</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT O="xl"/>
                        <ENT>2,714</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD2">Gray Seal</HD>
                <P>
                    The number of gray seals expected to be present at the PTST project area was estimated using the same methodology as was used for the harbor seal. Survey data collected by the U.S. Navy at the portal islands from 2015 through 2022 was utilized (Rees 
                    <E T="03">et al.</E>
                     2016; Jones 
                    <E T="03">et al.</E>
                     2018; Jones and Rees 2023). A maximum of 1 gray seal was seen during the months of February 2015, 2016, and 2022. Given this information NMFS 
                    <PRTPAGE P="18388"/>
                    assumed that a single gray seal will be taken per work day in February 2024. The anticipated numbers of monthly takes were calculated following the same approach as for harbor seals, and the monthly takes were then summed (table 12). Although the project has not recorded any gray seal sightings to date, NMFS assumed that, over the duration of the project, a single gray seal could enter into the Level A harassment zone unseen by a PSO and remain for sufficient duration to incur PTS. Therefore, NMFS is authorizing the take of 1 gray seal by Level A harassment and 17 gray seals by Level B harassment for a total of 18 authorized takes.
                </P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,12,12,12">
                    <TTITLE>Table 12—Calculation of the Number of Gray Seal Takes</TTITLE>
                    <BOXHD>
                        <CHED H="1">Month</CHED>
                        <CHED H="1">Estimated seals per work day</CHED>
                        <CHED H="1">
                            Total pile 
                            <LI>driving days </LI>
                            <LI>per month</LI>
                        </CHED>
                        <CHED H="1">Total number of requested takes</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">January 2024</ENT>
                        <ENT>0</ENT>
                        <ENT>15</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">February 2024</ENT>
                        <ENT>1</ENT>
                        <ENT>18</ENT>
                        <ENT>18</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">March 2024</ENT>
                        <ENT>0</ENT>
                        <ENT>13</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">April 2024</ENT>
                        <ENT>0</ENT>
                        <ENT>8</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">December 2024</ENT>
                        <ENT>0</ENT>
                        <ENT>26</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>18</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Table 13 shows the take numbers authorized by NMFS as well as the percentage of each stock affected.</P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,r50,12,12,12,12">
                    <TTITLE>Table 13—Authorized Take by Stock and Harassment Type as a Percentage of Stock Abundance</TTITLE>
                    <BOXHD>
                        <CHED H="1">Species</CHED>
                        <CHED H="1">Stock</CHED>
                        <CHED H="1">
                            Level A
                            <LI>harassment</LI>
                        </CHED>
                        <CHED H="1">
                            Level B
                            <LI>harassment</LI>
                        </CHED>
                        <CHED H="1">Total</CHED>
                        <CHED H="1">Percent of stock</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Humpback Whale</ENT>
                        <ENT>Gulf of Maine</ENT>
                        <ENT>0</ENT>
                        <ENT>6</ENT>
                        <ENT>6</ENT>
                        <ENT>0.4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Harbor Porpoise</ENT>
                        <ENT>Gulf of Maine/Bay of Fundy</ENT>
                        <ENT>1</ENT>
                        <ENT>3</ENT>
                        <ENT>4</ENT>
                        <ENT>&lt;0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bottlenose Dolphin</ENT>
                        <ENT>WNA Coastal, Northern Migratory</ENT>
                        <ENT>0</ENT>
                        <ENT>6,028</ENT>
                        <ENT>6,028</ENT>
                        <ENT>90.8</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>WNA Coastal, Southern Migratory</ENT>
                        <ENT>0</ENT>
                        <ENT>6,028</ENT>
                        <ENT>6,028</ENT>
                        <ENT>160.7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>NNCES</ENT>
                        <ENT>0</ENT>
                        <ENT>200</ENT>
                        <ENT>200</ENT>
                        <ENT>24.3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Harbor Seal</ENT>
                        <ENT>Western North Atlantic</ENT>
                        <ENT>80</ENT>
                        <ENT>2,634</ENT>
                        <ENT>2,714</ENT>
                        <ENT>4.4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Gray Seal</ENT>
                        <ENT>Western North Atlantic</ENT>
                        <ENT>1</ENT>
                        <ENT>17</ENT>
                        <ENT>18</ENT>
                        <ENT>&lt;0.01</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The monitoring results from work conducted in 2020 and 2021 are found in table 14. The results demonstrate significantly fewer takes by harassment than were authorized, and it is important to note that estimates in the previous IHAs as well as in this IHA are based on conservative assumptions, including the size of identified harassment zones and the abundance of marine mammals. However, we note that these assumptions represent the best available information in this case.</P>
                <GPOTABLE COLS="10" OPTS="L2,p7,7/8,i1" CDEF="s50,r50,11,11,11,11,11,11,11,11">
                    <TTITLE>Table 14—Marine Mammal Monitoring Results From IHAs Issued in 2020 and 2021</TTITLE>
                    <BOXHD>
                        <CHED H="1">Species</CHED>
                        <CHED H="1">Stock</CHED>
                        <CHED H="1">
                            Level A
                            <LI>harassments</LI>
                            <LI>authorized</LI>
                            <LI>in 2020 IHA</LI>
                        </CHED>
                        <CHED H="1">
                            Level B
                            <LI>harassments</LI>
                            <LI>authorized</LI>
                            <LI>in 2020 IHA</LI>
                        </CHED>
                        <CHED H="1">
                            Observations
                            <LI>in level A</LI>
                            <LI>harassment</LI>
                            <LI>zones under</LI>
                            <LI>2020 IHA</LI>
                        </CHED>
                        <CHED H="1">
                            Observations
                            <LI>in level B</LI>
                            <LI>harassment</LI>
                            <LI>zones under</LI>
                            <LI>2020 IHA</LI>
                        </CHED>
                        <CHED H="1">
                            Level A
                            <LI>harassments</LI>
                            <LI>authorized</LI>
                            <LI>in 2021 IHA</LI>
                        </CHED>
                        <CHED H="1">
                            Level B
                            <LI>harassments</LI>
                            <LI>authorized</LI>
                            <LI>in 2021 IHA</LI>
                        </CHED>
                        <CHED H="1">
                            Observations
                            <LI>in level A</LI>
                            <LI>harassment</LI>
                            <LI>zones under</LI>
                            <LI>2021 IHA</LI>
                        </CHED>
                        <CHED H="1">
                            Observations
                            <LI>in level B</LI>
                            <LI>harassment</LI>
                            <LI>zones under</LI>
                            <LI>2021 IHA</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Humpback Whale</ENT>
                        <ENT>Gulf of Maine</ENT>
                        <ENT/>
                        <ENT>12</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>12</ENT>
                        <ENT/>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Harbor Porpoise</ENT>
                        <ENT>Gulf of Maine/Bay of Fundy</ENT>
                        <ENT>5</ENT>
                        <ENT>7</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>5</ENT>
                        <ENT>7</ENT>
                        <ENT/>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bottlenose Dolphin</ENT>
                        <ENT>WNA Coastal, Northern Migratory</ENT>
                        <ENT>142</ENT>
                        <ENT>14,095</ENT>
                        <ENT/>
                        <ENT>5</ENT>
                        <ENT/>
                        <ENT>43,203</ENT>
                        <ENT/>
                        <ENT>394</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>WNA Coastal, Southern Migratory</ENT>
                        <ENT>142</ENT>
                        <ENT>14,095</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>43,203</ENT>
                        <ENT/>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>NNCES</ENT>
                        <ENT>2</ENT>
                        <ENT>198</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>250</ENT>
                        <ENT/>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Harbor Seal</ENT>
                        <ENT>Western North Atlantic</ENT>
                        <ENT>1,296</ENT>
                        <ENT>2,124</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>1,154</ENT>
                        <ENT>1,730</ENT>
                        <ENT/>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Gray Seal</ENT>
                        <ENT>Western North Atlantic</ENT>
                        <ENT>1</ENT>
                        <ENT>3</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>16</ENT>
                        <ENT>24</ENT>
                        <ENT/>
                        <ENT/>
                    </ROW>
                </GPOTABLE>
                <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 
                    <PRTPAGE P="18389"/>
                    (latter not applicable for this action). 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, NMFS considers 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. 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 and impact on operations.</P>
                <P>CTJV must conduct training between construction supervisors, crews, marine mammal monitoring team, and relevant CTJV staff prior to the start of all pile driving activities and when new personnel join the work, so that responsibilities, communication procedures, monitoring protocols, and operational procedures are clearly understood.</P>
                <P>Construction supervisors and crews, PSOs, and relevant CTJV staff must avoid direct physical interaction with marine mammals during construction activity. If a marine mammal comes within 10 m of such activity, operations must cease and vessels must reduce speed to the minimum level required to maintain steerage and safe working conditions, as necessary to avoid direct physical interaction. If an activity is delayed or halted due to the presence of a marine mammal, the activity may not commence or resume until either the animal has voluntarily exited and been visually confirmed beyond the shutdown zone indicated in table 15 or 15 minutes have passed without re-detection of the animal.</P>
                <P>Construction activities must be halted upon observation of a species for which incidental take is not authorized or a species for which incidental take has been authorized but the authorized number of takes has been met entering or within the harassment zone.</P>
                <P>
                    <E T="03">Shutdown Zones</E>
                    —For all pile driving activities, CTJV will implement shutdowns within designated zones. The purpose of a shutdown zone is generally to define an area within which shutdown of the activity will occur upon sighting of a marine mammal (or in anticipation of an animal entering the defined area). Shutdown zones vary based on the activity type and marine mammal hearing group (table 7). In most cases, the shutdown zones are based on the estimated Level A harassment isopleth distances for each hearing group. However, in cases where it would be challenging to detect marine mammals at the Level A harassment isopleth, (
                    <E T="03">e.g.,</E>
                     for high frequency cetaceans and phocids during impact driving activities), smaller shutdown zones have been established (table 15).
                </P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12,12,12,12,12">
                    <TTITLE>Table 15—Shutdown and Monitoring Zones</TTITLE>
                    <TDESC>[Meters]</TDESC>
                    <BOXHD>
                        <CHED H="1">Method and piles</CHED>
                        <CHED H="1">LF cetaceans</CHED>
                        <CHED H="1">MF cetaceans</CHED>
                        <CHED H="1">HF cetaceans</CHED>
                        <CHED H="1">Phocids</CHED>
                        <CHED H="1">Monitoring zone</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">36-in Impact (with bubble Curtain)</ENT>
                        <ENT>285</ENT>
                        <ENT>20</ENT>
                        <ENT>200</ENT>
                        <ENT>160</ENT>
                        <ENT>736</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">36-in Vibratory (with bubble curtain)</ENT>
                        <ENT>10</ENT>
                        <ENT>10</ENT>
                        <ENT>15</ENT>
                        <ENT>10</ENT>
                        <ENT>10,000</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Protected Species Observers</E>
                    —The number and placement of PSOs during all construction activities (described in the Monitoring and Reporting section as well as the Marine Mammal Monitoring Plan) will ensure that the entire shutdown zone is visible. A minimum of one PSO must be employed for all driving activities and placed at a location providing, at a minimum, adequate views of the established shutdown zones.
                </P>
                <P>
                    <E T="03">Monitoring for Level B Harassment</E>
                    —PSOs will monitor the shutdown zones and beyond to the extent that PSOs can see. Monitoring beyond the shutdown zones enables observers to be aware of and communicate the presence of marine mammals in the project areas outside the shutdown zones and thus prepare for a potential cessation of activity should the animal enter the shutdown zone. If a marine mammal enters the Level B harassment zone (or Level A harassment zone if larger than the Level B harassment zone), PSOs will document the marine mammal's presence and behavior.
                </P>
                <P>
                    <E T="03">Pre and Post-Activity Monitoring</E>
                    —Prior to the start of daily in-water construction activity, or whenever a break in pile driving of 30 minutes or longer occurs, PSOs will observe the shutdown, Level A harassment, and Level B harassment zones for a period of 30 minutes. Pre-start clearance monitoring must be conducted during periods of visibility sufficient for the lead PSO to determine that the shutdown zones are clear of marine mammals. If the shutdown zone is obscured by fog or poor lighting conditions, in-water construction activity will not be initiated until the entire shutdown zone is visible. Pile driving activities may commence following 30 minutes of observation when the determination is made that the shutdown zones are clear of marine mammals. If a marine mammal is observed entering or within shutdown zones, pile driving activities must be delayed or halted. If pile driving is delayed or halted due to the presence of a marine mammal, the activity may not commence or resume until either the animal has voluntarily exited and been visually confirmed beyond the shutdown zone or 15 minutes have passed for all other species without re-detection of the animal.
                </P>
                <P>
                    <E T="03">Soft Start</E>
                    —The use of soft-start procedures are believed to provide additional protection to marine mammals by providing warning and/or giving marine mammals a chance to leave the area prior to the hammer operating at full capacity. For impact pile driving, contractors will be required to provide an initial set of three strikes from the hammer at reduced energy, with each strike followed by a 30-second waiting period. This procedure will be conducted a total of three times before impact pile driving begins. Soft start will be implemented at the start of each day's impact pile driving activities and at any time following cessation of 
                    <PRTPAGE P="18390"/>
                    impact pile driving activities for a period of 30 minutes or longer. Soft start is not required during vibratory pile driving activities.
                </P>
                <P>
                    <E T="03">Bubble Curtain</E>
                    —Use of a bubble curtain during impact and vibratory pile driving in water depths greater than 3 m (10 ft) will be required. It must be operated as necessary to achieve optimal performance, and there can be no reduction in performance attributable to faulty deployment. At a minimum, CTJV must adhere to the following performance standards: The bubble curtain must distribute air bubbles around 100 percent of the piling circumference for the full depth of the water column. The lowest bubble ring must be in contact with the substrate for the full circumference of the ring, and the weights attached to the bottom ring shall ensure 100 percent substrate contact. No parts of the ring or other objects shall prevent full substrate contact. Air flow to the bubblers must be balanced around the circumference of the pile.
                </P>
                <P>Based on our evaluation of the applicant's planned measures, 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.</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 present while conducting the activities. 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 activity; 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); and,
                </P>
                <P>• Mitigation and monitoring effectiveness.</P>
                <P>
                    <E T="03">Visual Monitoring</E>
                    —Marine mammal monitoring must be conducted in accordance with the Marine Mammal Monitoring and Mitigation Plan. Marine mammal monitoring during pile driving activities must be conducted by NMFS-approved PSOs in a manner consistent with the following:
                </P>
                <P>• PSOs must be independent of the activity contractor (for example, employed by a subcontractor), and have no other assigned tasks during monitoring periods;</P>
                <P>• At least one PSO must have prior experience performing the duties of a PSO during construction activity pursuant to a NMFS-issued incidental take authorization;</P>
                <P>• Other PSOs may substitute other relevant experience, education (degree in biological science or related field) or training for experience performing the duties of a PSO during construction activities pursuant to a NMFS-issued incidental take authorization.</P>
                <P>• PSOs must be approved by NMFS prior to beginning any activity subject to this IHA.</P>
                <P>PSOs should also have the following additional qualifications:</P>
                <P>• Ability to conduct field observations and collect data according to assigned protocols;</P>
                <P>• Experience or training in the field identification of marine mammals, including identification of behaviors;</P>
                <P>• Sufficient training, orientation, or experience with the construction operation to provide for personal safety during observations;</P>
                <P>• 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 in-water construction activities were conducted; dates, times, and reason for implementation of mitigation (or why mitigation was note implemented when required); and marine mammal behavior; and</P>
                <P>• 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>
                    Visual monitoring will be conducted by a minimum of one trained PSO positioned at a suitable vantage point that will allow coverage of the identified harassment zones. The Portal Islands and associated berms will constrain the ensonified area to only one side (
                    <E T="03">i.e.</E>
                     east or west) of the bridge tunnel structure. Additionally, CTJV expressed concern that since they will only be using one drill for about two hours per week, it will be difficult to secure multiple observers willing to commit to the PTST project.
                </P>
                <P>Monitoring will be conducted 30 minutes before, during, and 30 minutes after all in water construction activities. In addition, PSOs will record all incidents of marine mammal occurrence, regardless of distance from activity, and will document any behavioral reactions in concert with distance from piles being removed. Pile driving activities include the time to remove a single pile or series of piles, as long as the time elapsed between uses of the pile driving equipment is no more than 30 minutes.</P>
                <HD SOURCE="HD2">Reporting</HD>
                <P>CTJV will submit a draft marine mammal monitoring report to NMFS within 90 days after the completion of pile driving activities, or 60 days prior to a requested date of issuance of any future IHAs for the project, or other projects at the same location, whichever comes first. The marine mammal monitoring report will include an overall description of work completed, a narrative regarding marine mammal sightings, and associated PSO data sheets. Specifically, the report will include:</P>
                <P>• Dates and times (begin and end) of all marine mammal monitoring;</P>
                <P>
                    • Construction activities occurring during each daily observation period, including: (1) The number and type of piles that were removed (
                    <E T="03">e.g.,</E>
                     impact, vibratory); and (2) Total duration of driving time for each pile (vibratory) and number of strikes for each pile (impact);
                    <PRTPAGE P="18391"/>
                </P>
                <P>• PSO locations during marine mammal monitoring;</P>
                <P>• Environmental conditions during monitoring periods (at beginning and end of PSO shift and whenever conditions change significantly), including Beaufort sea state and any other relevant weather conditions including cloud cover, fog, sun glare, and overall visibility to the horizon, and estimated observable distance;</P>
                <P>
                    • Upon observation of a marine mammal, the following information: (1) Name of PSO who sighted the animal(s) and PSO location and activity at time of sighting; (2) Time of sighting; (3) Identification of the animal(s) (
                    <E T="03">e.g.,</E>
                     genus/species, lowest possible taxonomic level, or unidentified), PSO confidence in identification, and the composition of the group if there is a mix of species; (4) Distance and location of each observed marine mammal relative to the pile being removed for each sighting; (5) Estimated number of animals (min/max/best estimate); (6) Estimated number of animals by cohort (adults, juveniles, neonates, group composition, 
                    <E T="03">etc.</E>
                    ); (7) Animal's closest point of approach and estimated time spent within the harassment zone; (8) Description of any marine mammal behavioral observations (
                    <E T="03">e.g.,</E>
                     observed behaviors such as feeding or traveling), including an assessment of behavioral responses thought to have resulted from the activity (
                    <E T="03">e.g.,</E>
                     no response or changes in behavioral state such as ceasing feeding, changing direction, flushing, or breaching);
                </P>
                <P>• Number of marine mammals detected within the harassment zones, by species; and,</P>
                <P>
                    • Detailed information about implementation of any mitigation (
                    <E T="03">e.g.,</E>
                     shutdowns and delays), a description of specific actions that ensued, and resulting changes in behavior of the animal(s), if any.
                </P>
                <P>
                    If no comments are received from NMFS within 30 days, the draft final report will constitute the final report. If comments are received, a final report addressing NMFS comments must be submitted within 30 days after receipt of comments. The Holder must submit all PSO data electronically in a format that can be queried such as a spreadsheet or database (
                    <E T="03">i.e.,</E>
                     digital images of data sheets are not sufficient).
                </P>
                <P>
                    In the event that personnel involved in the construction activities discover an injured or dead marine mammal, the Holder must report the incident to the Office of Protected Resources (OPR), NMFS (
                    <E T="03">PR.ITP.MonitoringReports@noaa.gov</E>
                     and 
                    <E T="03">ITP.pauline@noaa.gov</E>
                    ) and to the Greater Atlantic Regional Stranding Coordinator (978-282-8478) as soon as feasible. If the death or injury was clearly caused by the specified activity, the Holder must immediately cease the activities until NMFS OPR is able to review the circumstances of the incident and determine what, if any, additional measures are appropriate to ensure compliance with the terms of this IHA. The Holder must not resume their activities until notified by NMFS. The report must include the following information:
                </P>
                <P>• Time, date, and location (latitude/longitude) of the first discovery (and updated location information if known and applicable);</P>
                <P>• Species identification (if known) or description of the animal(s) involved;</P>
                <P>• Condition of the animal(s) (including carcass condition if the animal is dead);</P>
                <P>• Observed behaviors of the animal(s), if alive;</P>
                <P>• If available, photographs or video footage of the animal(s); and</P>
                <P>• General circumstances under which the animal was discovered.</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 majority of our analysis applies to all the species listed in table 13, given that many of the anticipated effects of this project on different marine mammal stocks are expected to be relatively similar in nature. 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>Impact and vibratory pile driving have the potential to disturb or displace marine mammals. Specifically, the project activities may result in take, in the form of Level A and Level B harassment from underwater sounds generated from pile driving.</P>
                <P>The takes from Level A and Level B harassment would be due to potential behavioral disturbance, TTS, and PTS. No serious injury or mortality is anticipated given the nature of the activity and measures designed to minimize the possibility of injury to marine mammals. The potential for harassment is minimized through the construction method and the implementation of the planned mitigation measures (see Mitigation section).</P>
                <P>
                    We anticipate that harbor porpoises, harbor seals and gray seals may sustain some limited Level A harassment in the form of auditory injury. However, animals in these locations that experience PTS will likely only receive slight PTS, 
                    <E T="03">i.e.,</E>
                     minor degradation of hearing capabilities within regions of hearing that align most completely with the energy produced by pile driving, 
                    <E T="03">i.e.,</E>
                     the low-frequency region below 2 kHz, not severe hearing impairment or impairment in the regions of greatest hearing sensitivity. If hearing impairment occurs, it is most likely that the affected animal will lose a few decibels in its hearing sensitivity, which in most cases is not likely to meaningfully affect its ability to forage and communicate with conspecifics. Impacts to individual fitness, reproduction, or survival are unlikely. As described above, we expect that marine mammals will be likely to move away from a sound source that represents an aversive stimulus, especially at levels that would be expected to result in PTS, given sufficient notice through use of soft start.
                </P>
                <P>
                    Behavioral responses of marine mammals to pile driving at the project 
                    <PRTPAGE P="18392"/>
                    site, if any, are expected to be mild and temporary. Marine mammals within the Level B harassment zone may not show any visual cues they are disturbed by activities or could become alert, avoid the area, leave the area, or display other mild responses that are not observable such as changes in vocalization patterns. Given the short duration of noise-generating activities per day, any harassment would be temporary. There are no other areas or times of known biological importance for any of the affected species.
                </P>
                <P>We acknowledge the existence and concern about the ongoing humpback whale UME. We have no evidence that this project is likely to result in vessel strikes (a major correlate of the UME) and marine construction projects in general involve the use of slow-moving vessels, such as tugs towing or pushing barges, or smaller work boats maneuvering in the vicinity of the construction project. These vessel types are not typically associated with vessel strikes resulting in injury or mortality. More generally, the UME does not yet provide cause for concern regarding population-level impacts for humpback whales. Despite the UME, the West Indies breeding population or DPS, remains healthy.</P>
                <P>For all species and stocks, take will occur within a limited, confined area (adjacent to the CBBT) of the stock's range and the amount of take authorized is extremely small when compared to stock abundance. In addition, it is unlikely that minor noise effects in a small, localized area of habitat will have any effect on the stocks' ability to recover. In combination, we believe that these factors, as well as the available body of evidence from other similar activities, demonstrate that the potential effects of the specified activities will have only minor, short-term effects on individuals. The specified activities are not expected to impact rates of recruitment or survival and will therefore not result in population-level impacts.</P>
                <P>In summary and as described above, the following factors primarily support our determination that the impacts resulting from this activity are not expected to adversely affect the species or stock through effects on annual rates of recruitment or survival:</P>
                <P>• No serious injury or mortality is anticipated or authorized;</P>
                <P>• Authorized Level A harassment will be very small amounts and of low degree;</P>
                <P>• No important habitat areas have been identified within the project area;</P>
                <P>• For all species, the specified project area in Chesapeake Bay is a very small and peripheral part of their range;</P>
                <P>• CTJV will implement mitigation measures such as bubble curtains, soft-starts, and shut downs; and</P>
                <P>• Monitoring reports from similar work in Chesapeake Bay have documented little to no effect on individuals of the same species impacted by the specified 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 required monitoring and mitigation measures, NMFS finds that the total marine mammal take from the planned activity will have a negligible impact on all affected marine mammal species or stocks.</P>
                <HD SOURCE="HD1">Small Numbers</HD>
                <P>As noted previously, only take of small numbers of marine mammals 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 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 less than one-third of the species or stock abundance, 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>The amount of take NMFS is authorizing is below one-third of the estimated stock abundance for humpback whale, harbor porpoise, gray seal, and harbor seal (in fact, take is no more than 6 percent of the abundance of the affected stocks, see table 13). This is likely a conservative estimate because they assume all takes are of different individual animals which is likely not the case. Some individuals may return multiple times in a day, but PSOs will count them as separate takes if they cannot be individually identified.</P>
                <P>There are three bottlenose dolphin stocks that could occur in the project area. Therefore, the estimated 12,256 dolphin takes by Level B harassment will likely be split among the western North Atlantic northern migratory coastal stock, western North Atlantic southern migratory coastal stock, and NNCES stock. Based on the stocks' respective occurrence in the area, NMFS estimated that there will be no more than 200 takes from the NNCES stock, representing 24.3 percent of that population, with the remaining takes split evenly between the northern (90.8 percent) and southern migratory coastal stocks (160.7 percent). Based on consideration of various factors described below, we have determined the numbers of individuals taken will comprise less than one-third of the best available population abundance estimate of either coastal migratory stock. Detailed descriptions of the stocks' ranges have been provided in Description of Marine Mammals in the Area of Specified Activities.</P>
                <P>Both the northern migratory coastal and southern migratory coastal stocks have expansive ranges and they are the only dolphin stocks thought to make broad-scale, seasonal migrations in coastal waters of the western North Atlantic. Given the large ranges associated with these two stocks it is unlikely that large segments of either stock will approach the project area and enter into the Chesapeake Bay. The majority of both stocks are likely to be found widely dispersed across their respective habitat ranges and unlikely to be concentrated in or near the Chesapeake Bay.</P>
                <P>Furthermore, the Chesapeake Bay and nearby offshore waters represent the boundaries of the ranges of each of the two coastal stocks during migration. The northern migratory coastal stock is found during warm water months from coastal Virginia, including the Chesapeake Bay and Long Island, New York. The stock migrates south in late summer and fall. During cold water months dolphins may be found in coastal waters from Cape Lookout, North Carolina, to the North Carolina/Virginia. During January-March, the southern migratory coastal stock appears to move as far south as northern Florida. From April to June, the stock moves back north to North Carolina. During the warm water months of July-August, the stock is presumed to occupy coastal waters north of Cape Lookout, North Carolina, to Assateague, Virginia, including the Chesapeake Bay. There is likely some overlap between the northern and southern migratory stocks during spring and fall migrations, but the extent of overlap is unknown.</P>
                <P>
                    The Bay and waters offshore of the mouth are located on the periphery of the migratory ranges of both coastal stocks (although during different seasons). Additionally, each of the migratory coastal stocks are likely to be located in the vicinity of the Bay for 
                    <PRTPAGE P="18393"/>
                    relatively short timeframes. Given the limited number of animals from each migratory coastal stock likely to be found at the seasonal migratory boundaries of their respective ranges, in combination with the short time periods (~2 months) animals might remain at these boundaries, it is reasonable to assume that takes are likely to occur only within some small portion of either of the migratory coastal stocks.
                </P>
                <P>
                    Both migratory coastal stocks likely overlap with the NNCES stock at various times during their seasonal migrations. The NNCES stock is defined as animals that primarily occupy waters of the Pamlico Sound estuarine system (which also includes Core, Roanoke, and Albemarle sounds, and the Neuse River) during warm water months (July-August). Members of this stock also use coastal waters (≤1 km from shore) of North Carolina from Beaufort north to Virginia Beach, Virginia, including the lower Chesapeake Bay. Comparison of dolphin photo-identification data confirmed that limited numbers of individual dolphins observed in Roanoke Sound have also been sighted in the Chesapeake Bay (Young, 2018). Like the migratory coastal dolphin stocks, the NNCES stock covers a large range. The spatial extent of most small and resident bottlenose dolphin populations is on the order of 500 km
                    <SU>2</SU>
                    , while the NNCES stock occupies over 8,000 km
                    <SU>2</SU>
                     (LeBrecque 
                    <E T="03">et al.,</E>
                     2015). Given this large range, it is again unlikely that a preponderance of animals from the NNCES stock will depart the North Carolina estuarine system and travel to the northern extent of the stock's range and enter into the Bay. However, recent evidence suggests that there is likely a small resident community of NNCES dolphins of indeterminate size that inhabits the Chesapeake Bay year-round (Eric Patterson, Personal Communication).
                </P>
                <P>
                    Many of the dolphin observations in the Bay are likely repeated sightings of the same individuals. The Potomac-Chesapeake Dolphin Project has observed over 1,200 unique animals since observations began in 2015. Re-sightings of the same individual can be highly variable. Some dolphins are observed once per year, while others are highly regular with greater than 10 sightings per year (Mann, Personal Communication). Similarly, using available photo-identification data, Engelhaupt 
                    <E T="03">et al.</E>
                     (2016) determined that specific individuals were often observed in close proximity to their original sighting locations and were observed multiple times in the same season or same year. Ninety-one percent of re-sighted individuals (100 of 110) in the study area were recorded less than 30 km from the initial sighting location. Multiple sightings of the same individual will considerably reduce the number of individual animals that are taken by harassment. Furthermore, the existence of a resident dolphin population in the Bay will increase the percentage of dolphin takes that are actually re-sightings of the same individuals.
                </P>
                <P>In summary and as described above, the following factors primarily support our determination regarding the incidental take of small numbers of a species or stock:</P>
                <P>• The take of marine mammal stocks authorized for take comprises less than 10 percent of any stock abundance (with the exception of bottlenose dolphin stocks);</P>
                <P>• Potential bottlenose dolphin takes in the project area are likely to be allocated among three distinct stocks;</P>
                <P>• Bottlenose dolphin stocks in the project area have extensive ranges and it will be unlikely to find a high percentage of any one stock concentrated in a relatively small area such as the project area or the Bay;</P>
                <P>• The Bay represents the migratory boundary for each of the specified dolphin stocks and it will be unlikely to find a high percentage of any stock concentrated at such boundaries;</P>
                <P>• Many of the takes will be repeats of the same animal and it is likely that a number of individual animals could be taken 10 or more times.</P>
                <P>Based on the analysis contained herein of the planned activity (including the required 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.</P>
                <HD SOURCE="HD1">Unmitigable Adverse Impact Analysis and Determination</HD>
                <P>There are no relevant subsistence uses of the affected marine mammal stocks or species implicated by this action. Therefore, NMFS has determined that the total taking of affected species or stocks will not have an unmitigable adverse impact on the availability of such species or stocks for taking for subsistence purposes.</P>
                <HD SOURCE="HD1">Endangered Species Act</HD>
                <P>
                    Section 7(a)(2) of the Endangered Species Act of 1973 (ESA; 16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ) requires that each Federal agency insure that any action it authorizes, funds, or carries out is not likely to jeopardize the continued existence of any endangered or threatened species or result in the destruction or adverse modification of designated critical habitat. To ensure ESA compliance for the issuance of IHAs, NMFS consults internally whenever we propose to authorize take for endangered or threatened species.
                </P>
                <P>No incidental take of ESA-listed species is expected to result from this activity or been authorized by NMFS. Therefore, NMFS has determined that formal consultation under section 7 of the ESA is not required for this action.</P>
                <HD SOURCE="HD1">National Environmental Policy Act</HD>
                <P>
                    To comply with the National Environmental Policy Act of 1969 (NEPA; 42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ) and NOAA Administrative Order (NAO) 216-6A, NMFS must review our action (
                    <E T="03">i.e.,</E>
                     the issuance of an IHA) with respect to potential impacts on the human environment.
                </P>
                <P>This action is consistent with categories of activities identified in Categorical Exclusion B4 (IHAs with no anticipated serious injury or mortality) of the Companion Manual for NAO 216-6A, which do not individually or cumulatively have the potential for significant impacts on the quality of the human environment and for which we have not identified any extraordinary circumstances that will preclude this categorical exclusion. Accordingly, NMFS has determined that the issuance of the IHA qualifies to be categorically excluded from further NEPA review.</P>
                <HD SOURCE="HD1">Authorization</HD>
                <P>NMFS has issued an IHA to CTJV for the potential harassment of small numbers of five marine mammal species incidental to the Parallel Thimble Shoal Tunnel Project, In Virginia Beach, Virginia that includes the previously explained mitigation, monitoring and reporting requirements.</P>
                <SIG>
                    <DATED>Dated: March 4, 2024.</DATED>
                    <NAME>Kimberly Damon-Randall,</NAME>
                    <TITLE>Director, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05321 Filed 3-12-24; 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-XD783]</DEPDOC>
                <SUBJECT>North Pacific 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>
                    <PRTPAGE P="18394"/>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of hybrid conference meetings.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The North Pacific Fishery Management Council (Council) and its advisory committees will meet April 1, 2024 through April 9, 2024.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The Council's Scientific and Statistical Committee (SSC) will begin at 8 a.m. in the Aleutian room on Monday, April 1, 2024, and continue through Wednesday, April 3, 2024. The Council's Advisory Panel (AP) will begin at 8 a.m. in the Denali room on Tuesday, April 2, 2024, and continue through Saturday, April 6, 2024. The closed Executive/Finance Committee will meet Wednesday April 3, 2024, from 1 p.m. to 5 p.m. at the Council's offices. The Council will begin at 8 a.m. in the Aleutian room on Thursday, April 4, 2024, and continue through Tuesday, April 9, 2024. All times listed are Alaska Time.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The meetings will be a hybrid conference. The in-person component of the meeting will be held at the Hilton Hotel, 500 W 3rd Ave., Suite 400, Anchorage, AK 99501, or join the meeting online through the links at 
                        <E T="03">https://www.npfmc.org/upcoming-council-meetings.</E>
                    </P>
                    <P>
                        <E T="03">Council address:</E>
                         North Pacific Fishery Management Council, 1007 W 3rd Ave., Anchorage, AK 99501-2252; telephone: (907) 271-2809. Instructions for attending the meeting via webconference are given under Connection Information, below.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Diana Evans, Council staff; email: 
                        <E T="03">diana.evans@noaa.gov;</E>
                         telephone: (907) 271-2809. For technical support, please contact our Council administrative staff, email: 
                        <E T="03">npfmc.admin@noaa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Agenda</HD>
                <HD SOURCE="HD2">Monday, April 1, 2024, Through Wednesday, April 3, 2024</HD>
                <P>The SSC agenda will include the following issues:</P>
                <P>(1) Scallops—Stock Assessment and Fishery Evaluation (SAFE) report, Acceptable biological catch (ABC)/Over Fishing Limit (OFL), Plan Team report.</P>
                <P>(2) Salmon bycatch—review (a) Chinook/chum genetics reports for Bering Sea (BS), Gulf of Alaska (GOA); and (c) Chum Salmon Bycatch initial review analysis.</P>
                <P>(3) Amendment 80 Program Review—review report.</P>
                <P>(4) Research Priorities—set 5-year priorities.</P>
                <P>(5) Sablefish study for IRA funding—discuss for potential analysis.</P>
                <P>
                    The agenda is subject to change, and the latest version will be posted at 
                    <E T="03">https://meetings.npfmc.org/Meeting/Details/3040</E>
                     prior to the meeting, along with meeting materials.
                </P>
                <P>In addition to providing ongoing scientific advice for fishery management decisions, the SSC functions as the Council's primary peer review panel for scientific information, as described by the Magnuson-Stevens Act section 302(g)(1)(e), and the National Standard 2 guidelines (78 FR 43066). The peer-review process is also deemed to satisfy the requirements of the Information Quality Act, including the OMB Peer Review Bulletin guidelines.</P>
                <HD SOURCE="HD2">Tuesday, April 2, 2024, Through Saturday, April 6, 2024</HD>
                <P>The Advisory Panel agenda will include the following issues:</P>
                <P>(1) Scallops—SAFE report, ABC/OFL, Plan Team report.</P>
                <P>(2) Salmon bycatch—review (a) Chinook/chum genetics reports BS and GOA, and (c) Chum Salmon Bycatch initial review analysis.</P>
                <P>(3) Area 4 Vessel Caps—Initial Review.</P>
                <P>(4) Amendment 80 Program Review—review report.</P>
                <P>(5) Maximum retention amount adjustments—review discussion paper.</P>
                <P>(6) Research Priorities set 5-year priorities.</P>
                <P>(7) Staff Tasking.</P>
                <HD SOURCE="HD2">Wednesday, April 3, 2024</HD>
                <P>The Executive/Finance Committee will meet in closed session to discuss Council finances and internal administrative matters.</P>
                <HD SOURCE="HD2">Thursday, April 4, 2024, Through Tuesday, April 9, 2024</HD>
                <P>The Council agenda will include the following issues. The Council may take appropriate action on any of the issues identified.</P>
                <P>(1) B Reports (Executive Director, NMFS Management, NOAA General Counsel (GC), Alaska Fishery Science Center (AFSC), Alaska Department of Fish and Game (ADF&amp;G), United States Coast Guard (USCG), United States Fish and Wildlife Service (USFWS), National Institute for Occupational Safety &amp; Health (NIOSH) report, Cooperative reports, Advisory Panel, SSC report).</P>
                <P>(2) Scallops—SAFE report, ABC/OFL, Plan Team report.</P>
                <P>(3) Salmon bycatch—review (a) Chinook/chum genetics reports BS and GOA; (b) pollock IPA reports, Sea Share, and (c) Chum Salmon Bycatch initial review analysis.</P>
                <P>(4) Area 4 Vessel Caps—Initial Review.</P>
                <P>(5) Amendment 80 Program Review—review report.</P>
                <P>(6) Maximum retention amount adjustments—review discussion paper.</P>
                <P>(7) Research Priorities set 5-year priorities.</P>
                <P>(8) Staff Tasking.</P>
                <HD SOURCE="HD1">Connection Information</HD>
                <P>
                    You can attend the meeting online using a computer, tablet, or smart phone; or by phone only. Connection information will be posted online at: 
                    <E T="03">https://www.npfmc.org/upcoming-council-meetings.</E>
                     For technical support, please contact our administrative staff, email: 
                    <E T="03">npfmc.admin@noaa.gov.</E>
                </P>
                <P>
                    If you are attending the meeting in-person, please refer to the COVID avoidance protocols on our website, 
                    <E T="03">https://www.npfmc.org/upcoming-council-meetings/.</E>
                </P>
                <HD SOURCE="HD1">Public Comment</HD>
                <P>
                    Public comment letters will be accepted and should be submitted electronically through the links at 
                    <E T="03">https://www.npfmc.org/upcoming-council-meetings.</E>
                     The Council strongly encourages written public comment for this meeting, to avoid any potential for technical difficulties to compromise oral testimony. The written comment period is open from March 8, 2024, to March 29, 2024, and closes at 12 p.m., Alaska Time on Friday, March 29, 2024.
                </P>
                <P>
                    <E T="03">Authority:</E>
                     16 U.S.C. 1801 
                    <E T="03">et seq.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 8, 2024.</DATED>
                    <NAME>Rey Israel Marquez,</NAME>
                    <TITLE>Acting Deputy Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05325 Filed 3-12-24; 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>
                <SUBJECT>Renewal of the Advisory Committee on Excellence in Space, Formerly the Advisory Committee on Commercial Remote Sensing</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with the provisions of the Federal Advisory Committee Act, as amended (FACA), the Department of Commerce has renewed and renamed the Advisory Committee on Commercial Remote Sensing (ACCRES) as the Advisory Committee on Excellence in Space (ACES), determining this action to be in the public interest in connection with the performance of duties imposed on the Department by law. ACCRES was 
                        <PRTPAGE P="18395"/>
                        renewed and renamed as ACES on March 4, 2024.
                    </P>
                </SUM>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Committee was first established in May 2002 to advise the Under Secretary of Commerce for Oceans and Atmosphere on matters relating to the U.S. commercial remote sensing industry and NOAA's activities to carry out the responsibilities of the Department of Commerce set forth in the National and Commercial Space Programs Act of 2010 (the Act), title 51 U.S.C. 60101 
                    <E T="03">et seq.</E>
                     (formerly the Land Remote Sensing Policy Act of 1992, 15 U.S.C. 5621-5625).
                </P>
                <P>ACES will have a fairly balanced membership consisting of no more than 25 members serving in a representative or Special Government Employee capacity. The members should represent a variety of space policy, engineering, technical, science, legal, and finance professionals with significant expertise in the commercial space industry. Each candidate member shall be recommended by the Director of NOAA's Office of Space Commerce (OSC) and shall be appointed by the Under Secretary or the OSC Director, generally for a term of two years and serve at the discretion of the Under Secretary or OSC Director.</P>
                <P>The Committee will function solely as an advisory body, and in compliance with provisions of the Federal Advisory Committee Act. Copies of the Committee's revised Charter have been filed with the appropriate committees of the Congress and with the Library of Congress.</P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jason Y. Kim, Chief of Staff, NOAA Office of Space Commerce, 1401 Constitution Ave. NW, Room 68015, Washington, DC 20230; telephone 202-482-6125; email 
                        <E T="03">space.commerce@noaa.gov.</E>
                    </P>
                    <SIG>
                        <NAME>Michael C. Morgan,</NAME>
                        <TITLE>Assistant Secretary for Environmental Observation and Prediction.</TITLE>
                    </SIG>
                </FURINF>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05284 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <DEPDOC>[RTID 0648-XD786]</DEPDOC>
                <SUBJECT>Magnuson-Stevens Fishery Conservation and Management Act Provisions; Atlantic Coastal Fisheries Cooperative Management Act Provisions; General Provisions for Domestic Fisheries; Application for Exempted Fishing Permits</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; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Assistant Regional Administrator for Sustainable Fisheries, Greater Atlantic Region, NMFS, has made a preliminary determination that an Exempted Fishing Permit application contains all of the required information and warrants further consideration. The exempted fishing permit would allow federally permitted fishing vessels to fish outside fishery regulations in support of exempted fishing activities proposed by the Maine Department of Marine Resources. Regulations under the Magnuson-Stevens Fishery Conservation and Management Act and the Atlantic Coastal Fisheries Cooperative Management Act require publication of this notification to provide interested parties the opportunity to comment on applications for proposed exempted fishing permits (EFP).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before March 28, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit written comments by the following method:</P>
                    <P>
                        • 
                        <E T="03">Email: nmfs.gar.efp@noaa.gov.</E>
                         Include in the subject line “MDMR 2024 On-demand EFP”
                    </P>
                    <P>
                        All comments received are a part of the public record and will generally be posted for public viewing in 
                        <E T="03">https://www.noaa.gov/organization/information-technology/foia-reading-room</E>
                         without change. All personal identifying information (
                        <E T="03">e.g.,</E>
                         name, address), confidential business information, or otherwise sensitive information submitted voluntarily by the sender will be publicly accessible. NMFS will accept anonymous comments (enter “anonymous” as the signature if you wish to remain anonymous).
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Christine Ford, Fishery Management Specialist, 
                        <E T="03">Christine.Ford@noaa.gov,</E>
                         (978) 281-9185.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Maine Department of Marine Resources (MDMR) submitted a complete application for an EFP to conduct commercial fishing activities that the regulations would otherwise restrict to test alternative gear retrieval systems that only use one traditional surface buoy. This EFP would exempt the participating vessels from the following Federal regulations:</P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s50,r50,r100">
                    <TTITLE>Table 1—Requested Exemptions</TTITLE>
                    <BOXHD>
                        <CHED H="1">CFR citation</CHED>
                        <CHED H="1">Regulation</CHED>
                        <CHED H="1">Need for exemption</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">50 CFR 697.21(b)(2)</ENT>
                        <ENT>Gear marking requirements</ENT>
                        <ENT>For trial of trap/pot gear with no more than one surface marking on trawls of more than three traps.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">50 CFR 648.84(b)</ENT>
                        <ENT>Gear marking requirements</ENT>
                        <ENT>For trial of gillnet gear with no more than one surface marking.</ENT>
                    </ROW>
                </GPOTABLE>
                <GPOTABLE COLS="2" OPTS="L2,p1,8/9,i1" CDEF="s50,r150">
                    <TTITLE>Table 2—Project Summary</TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Project title</ENT>
                        <ENT>Testing various acoustic on-demand fishing technologies that help minimize the risk of large whale entanglements in trap/pot and gillnet fishing gear in the Gulf of Maine.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Project Start</ENT>
                        <ENT>Upon Issuance.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Project End</ENT>
                        <ENT>One year from the date of issuance.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Project objectives</ENT>
                        <ENT>Provide access, training, and support to fishers in the Gulf of Maine to test acoustic on-demand fishing and gear geolocation technology. Data collected will help provide feedback to manufacturers to adapt to the specific needs of Maine fishers involved in fixed gear fleets. This work is important to reduce the risk associated with vertical lines to the endangered North Atlantic right whale in the Gulf of Maine.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Project location</ENT>
                        <ENT>
                            Trap/pot: Lobster Management Area 1 and all Maine Lobster Conservation Zones (A, B, C, D, E, F, G).
                            <LI>Gillnet: Statistical Areas 513, 514, 515.</LI>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Number of vessels</ENT>
                        <ENT>50 (up to 45 trap/pot; up to 5 gillnet).</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="18396"/>
                        <ENT I="01">Number of trips, trip duration (days), total number of days, number of tows or sets, and duration of tows or sets</ENT>
                        <ENT>See project narrative.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Gear type(s)</ENT>
                        <ENT>Trap/pot and anchored gillnet.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Project Narrative</HD>
                <P>This EFP would allow federally permitted vessels to test alternative gears to reduce entanglement risk to protected species, mainly the North Atlantic right whale, in trap/pot and sink gillnet fisheries. There are two components to this EFP, a gear library component, which is an assortment of devices and technologies to retrieve gear, and a gear geolocation component.</P>
                <P>
                    For the gear library component, participating vessels would replace one traditional surface marking with a spring-tag or timed-release retrieval system, a buoy and stowed-rope system, or a lift-bag system. A spring-tag retrieval system uses a low breaking strength (&lt;1,700 pounds (lb) (&lt;771 kilograms (kg))) buoy line that releases a stowed retrieval line of greater breaking strength when subjected to tension (&gt;75 lb (&gt;34 kg)). A timed-release retrieval system releases a stowed line after a programmed pre-set soak time. A buoy and stowed-rope system or a lift-bag system uses an acoustic trigger sent from the vessel to release the retrieval system, once the vessel is in close proximity to the gear. Each vessel would modify two trawls or strings by replacing one of the traditional vertical lines with one of the available on-demand retrieval systems, resulting in no additional vertical lines in the water. Vessels would be required to use one traditional surface marking on the other end of trap trawls of more than three traps and on all gillnet gear. For trap trawls of fewer than three traps, vessels would still use one traditional surface marking, in addition to the on-demand retrieval system; therefore, there would be no fully ropeless trawls. Other than gear markings, all trap trawls and gillnet strings would be consistent with the regulations of the management area where the vessel is fishing and would be fished in accordance with the participating vessels' standard operations (
                    <E T="03">i.e.,</E>
                     number and length of trips, soak times, trap limits, etc.).
                </P>
                <P>The gear geolocation component of this project will include a subset (up to 10) of the trap/pot vessels participating in the gear library component. Vessels would use acoustic positioning systems from any of the five available manufacturers (Teledyne Benthos, Ropeless Systems, Ashored, Nova Robotics, and Advanced Navigation), and would modify up to three trawls by replacing one of the traditional vertical lines with either a buoy and stowed-rope system or a lift-bag system to communicate with the acoustic positioning systems. The trawls would be set at different distances apart, within a density slightly greater than common gear densities, allowed to soak no longer than one hour each, and then be retrieved in rapid succession. The focus of this component would be testing the acoustic positioning systems to determine the extent of difference between acoustic geolocation and surface buoy or surface GPS geolocation, as well as testing the performance of the different acoustic positioning systems in an environment where multiple acoustic signals are being transmitted simultaneously. Up to 10 discrete single-day gear geolocation trials would be conducted within the fishing year. These trials would increase trap/pot effort via short soaks and high rate of retrieval. However, catch per unit effort would be reduced. Any legal catch would be kept for sale.</P>
                <P>MDMR researchers anticipate up to 5,200 total hauls of hybrid trap/pot trawls or gillnet strings for the gear library component, and up to an additional 150 retrievals of hybrid trap/pot trawls for the gear geolocation component. Trap trawls would be consistent with Atlantic Large Whale Take Reduction Plan (ALWTRP) regulations. Trawls would not exceed 50 traps per trawl and the gear library component trawls would soak for approximately 3 days (and not more than 30 days). Gillnets would be consistent with ALWTRP and Harbor Porpoise Take Reduction Plan (HPTRP) regulations. Gillnets would use 15-30.5 centimeters (cm) mesh, would not exceed 3,200 meters (m), and would soak for a period of approximately 24 hours (and not more than 30 days).</P>
                <P>To ensure broad participation and target areas where data is needed, MDMR has requested the flexibility to modify the participant vessel list and would submit modifications to the active participants list one month in advance. MDMR and the gear manufacturers will distribute gear and train all participants on its use. Scientific observers may accompany the participants on up to two trips per vessel, within budget and safety limitations. MDMR would provide standardized data collection sheets to all participants, but individually identifiable data will only be made public with the express permission of the vessel owner. Additionally, MDMR has requested an EFP Interactive Voice Response (IVR) reporting waiver for those trap/pot vessels not typically subject to IVR reporting; the applicant states that this requirement is a barrier to fishermen recruitment to this project, and is duplicative of the required eVTR reporting.</P>
                <P>The project objectives are to: (1) Collect data on deployments and retrievals of various acoustic on-demand fishing gears within the trap/pot and gillnet fisheries in the Gulf of Maine; (2) provide support and training to fishers on various on-demand technologies; (3) assess fishing areas that may be best suited for adopting the tested retrieval systems; (4) increase familiarity within the trap/pot and gillnet fisheries with on-demand gear; (5) provide feedback to on-demand fishing gear manufacturers to increase performance under commercial fishery conditions; (6) trial gear geolocation and marking systems that promote interoperability for fishers and management; and (7) compare the relative precision of various gear geolocation technologies to improve understanding of how transitioning to acoustic technologies may impact fishing behavior.</P>
                <P>MDMR has proposed the following best management and risk reduction practices:</P>
                <P>• Experimental buoy lines would be marked with unique white and blue markings above the required regional markings;</P>
                <P>• All vessels would provide mandatory, weekly gear loss and conflict reports to the Principal Investigator (PI), and the PI would provide monthly gear loss and conflict reports to the NOAA Greater Atlantic Regional Fisheries Office;</P>
                <P>• After release, the on-demand vertical lines would be retrieved as quickly as possible to minimize time in the water column;</P>
                <P>
                    • All vessels would record right whale sightings on data sheets, and would notify NMFS via email 
                    <PRTPAGE P="18397"/>
                    (
                    <E T="03">ne.rw.survey@noaa.gov</E>
                    ), or NOAA via phone (866-755-6622), or the U.S. Coast Guard (Channel 16);
                </P>
                <P>• All vessels would adhere to a 10-knot speed limit when transiting dynamic management areas, transiting areas closed to vertical lines, and/or when whales are observed;</P>
                <P>• All vessels would adhere to current approach regulations that create a 500-yard (1,500-feet (ft)) buffer zone in the presence of a surfacing right whale and would depart immediately at a safe and slow speed. Hauling any fishing gear would cease once the entire string or trawl was aboard the vessel, to accommodate the regulation, and be redeployed only after it was reasonable to assume the whale left the area; and</P>
                <P>• Law enforcement would be able to inspect gear at any time because one traditional surface-marking would be present at all times. The PI would notify law enforcement agencies (NOAA Office of Law Enforcement (OLE) and Maine Marine Patrol) of project participants and activities in advance of the project start date, including:</P>
                <P>○ Materials related to the redeployment of alternative gear-retrieval systems, most relevant to the spring-tagline retrieval system; and</P>
                <P>○ Information necessary to continue relevant enforcement operations with participant gear.</P>
                <P>If approved, the applicant may request minor modifications and extensions to the EFP throughout the year. EFP modifications and extensions may be granted without further notice if they are deemed essential to facilitate completion of the proposed research and have minimal impacts that do not change the scope or impact of the initially approved EFP request. Any fishing activity conducted outside the scope of the exempted fishing activity would be prohibited.</P>
                <P>
                    <E T="03">Authority:</E>
                     16 U.S.C. 1801 
                    <E T="03">et seq.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 7, 2024.</DATED>
                    <NAME>Everett Wayne Baxter,</NAME>
                    <TITLE>Acting Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05262 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <RIN>RTID 0648-XD796</RIN>
                <SUBJECT>Marine Mammals and Endangered Species; File No. 27671</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; receipt of application.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given that the Northwest Fisheries Science Center, Marine Forensic Laboratory, 2725 Montlake Blvd. East, Seattle, WA 98112 (Kevin Werner, Ph.D., Responsible Party), has applied in due form for a permit to receive, import, and export marine mammal and protected species parts for scientific research.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written, telefaxed, or email comments must be received on or before April 12, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The application and related documents are available for review by selecting “Records Open for Public Comment” from the “Features” box on the Applications and Permits for Protected Species (APPS) home page, 
                        <E T="03">https://apps.nmfs.noaa.gov,</E>
                         and then selecting File No. 27671 from the list of available applications. These documents are also available upon written request via email to 
                        <E T="03">NMFS.Pr1Comments@noaa.gov.</E>
                    </P>
                    <P>
                        Written comments on this application should be submitted via email to 
                        <E T="03">NMFS.Pr1Comments@noaa.gov.</E>
                         Please include File No. 27671 in the subject line of the email comment.
                    </P>
                    <P>
                        Those individuals requesting a public hearing should submit a written request via email to 
                        <E T="03">NMFS.Pr1Comments@noaa.gov.</E>
                         The request should set forth the specific reasons why a hearing on this application would be appropriate.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Malcolm Mohead or Jennifer Skidmore, (301) 427-8401.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The subject permit is requested under the authority of the Marine Mammal Protection Act of 1972, as amended (MMPA; 16 U.S.C. 1361 
                    <E T="03">et seq.</E>
                    ), the regulations governing the taking and importing of marine mammals (50 CFR part 216), the Endangered Species Act of 1973, as amended (ESA; 16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ), the regulations governing the taking, importing, and exporting of endangered and threatened species (50 CFR parts 222-226), and the Fur Seal Act of 1966, as amended (16 U.S.C. 1151 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <P>The applicant proposes to receive, import, and export samples from up to 100 individual animals from each species of all cetaceans, pinnipeds (excluding walrus), sea turtles (in water), coral, and individual species of fish and abalone listed under the ESA including: black and white abalone, Pacific and Atlantic salmonids, sawfish, sturgeon, sharks, grouper, rockfish, guitarfish, and totoaba. Receipt, import, and export is requested worldwide. Sources of samples may include animal strandings in foreign countries, foreign and domestic subsistence harvests, captive animals, other authorized persons or collections, incidentally bycaught animals, transfers from law enforcement, and marine mammals that died incidental to commercial fishing operations in the U.S. and foreign countries, where such take is legal. Samples would be archived at the Marine Forensics Laboratories in either Charleston, South Carolina, Seattle, Washington, and Ashland, Oregon. Samples would be used for research, supporting law enforcement actions, and outreach and education. No live takes from the wild would be authorized. The requested duration of the permit is 5 years.</P>
                <P>
                    In compliance with the National Environmental Policy Act of 1969 (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), an initial determination has been made that the activity proposed is categorically excluded from the requirement to prepare an environmental assessment or environmental impact statement.
                </P>
                <P>
                    Concurrent with the publication of this notice in the 
                    <E T="04">Federal Register</E>
                    , NMFS is forwarding copies of the application to the Marine Mammal Commission and its Committee of Scientific Advisors.
                </P>
                <SIG>
                    <DATED>Dated: March 7, 2024.</DATED>
                    <NAME>Julia Marie Harrison,</NAME>
                    <TITLE>Chief, Permits and Conservation Division, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05261 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <SUBJECT>Board of Visitors, National Defense University; Notice of Federal Advisory Committee Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P> Office of the Chairman Joint Chiefs of Staff, 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 Board of Visitors, National Defense University (BoV NDU) will take place.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P> Thursday, April 18, 2024 from 9:00 a.m. to 3:15 p.m. Eastern Time (ET).</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Marshall Hall, Building 62, Room 155, the National Defense 
                        <PRTPAGE P="18398"/>
                        University, 300 5th Avenue SW, Fort McNair, Washington, DC 20319-5066. Visitors should report to the Front Security Desk in the lobby of Marshall Hall and from there, they will be directed to the meeting room.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                         Ms. Joycelyn Stevens, (202) 685-0079 (Voice) 
                        <E T="03">joycelyn.a.stevens.civ@mail.mil; stevensj7@ndu.edu</E>
                         (Email). Mailing address is National Defense University, Fort McNair, Washington, DC 20319-5066. Website: 
                        <E T="03">http://www.ndu.edu/About/Board-of-Visitors/.</E>
                         The most up-to-date changes to the meeting agenda can be found at 
                        <E T="03">https://www.ndu.edu/About/Board-of-Visitors/BOV-Apr-18-2024.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> This meeting is being held in accordance with chapter 10 of title 5 United States Code (U.S.C.) (formerly known as the Federal Advisory Committee Act (FACA) (5 U.S.C., App.)) and under the provisions of the Government in the Sunshine Act of 1976 (5 U.S.C. 552b, as amended) and 41 CFR 102-3.140 and 102-3.150. Pursuant to 5 U.S.C. 552b and 41 CFR 102-3.140 through 102-3.165, this meeting is open to the public.</P>
                <P>
                    <E T="03">Purpose of the Meeting:</E>
                     The purpose of the meeting will include discussion on accreditation compliance, organizational management, resource management, and other matters of interest to the NDU.
                </P>
                <P>
                    <E T="03">Agenda:</E>
                     Thursday, April 18, 2024 from 9:00 a.m. to 3:15 p.m. Call to Order and Administrative Notes; State of the University Address; Reaffirmation of Middle States Commission on Higher Education Accreditation Update; Cybersecurity Update and Path Forward; Budget Outlook; National Defense Authorization Act Facilities Report Summary and Cost Model Findings; Realizing the Vision 2022-2027: NDU Implementation Plan; Command Climate; NATO Conference of Commandants; Discussion of Public Written Comments; Board of Visitors Member Deliberation and Feedback; Wrap-up and Closing Remarks.
                </P>
                <P>
                    <E T="03">Meeting Accessibility:</E>
                     Limited space is available for observers and will be allocated on a first come, first served basis. Meeting location is handicap accessible. The Main Gate/Visitor's Gate on 2nd Street SW is open 24/7. All Non-DoD, Non-federally-affiliated visitors must use this gate to access Fort McNair.
                </P>
                <P>
                    <E T="03">Base Access Requirements:</E>
                     All visitors without a DoD Common Access Card or U.S. military ID must be vetted in advance to gain entry onto the base. Per the U.S. Army, all non-DoD civilians are required to have a background check before being allowed on a military installation; better known as vetting. It is highly recommended that visitors undergo the pre-vetting process and apply online as detailed below.
                </P>
                <P>
                    <E T="03">For Pre-vetting:</E>
                     To allow sufficient time for processing, access requests should be submitted no more than 14 days ahead or less than three days before the event. The visitor will receive notification via email, and, if approved, a one-day visitor's pass for entry onto the base. The visitor must print the pass and present it to the guard at the gate to enter Fort McNair.
                </P>
                <P>(a) If the visitor has a valid U.S. driver's license:</P>
                <P>
                    (i) The visitor can apply for access online at 
                    <E T="03">https://pass.aie.army.mil/jbmhh/.</E>
                     Under Reason for Visit, select “Other.” Alternatively, the visitor can apply in person at the Fort McNair Visitor Control Center (VCC)/Police Substation (Building 65) from 8:00 a.m. to 4:00 p.m. Monday through Friday.
                </P>
                <P>(b) If the visitor does not have a U.S. driver's license:</P>
                <P>(i) The visitor must fill out a paper application in person at the Fort McNair Visitor Control Center VCC/Police Substation (Building 65) from 8:00 a.m. to 4:00 p.m. Monday through Friday.</P>
                <P>
                    <E T="03">For Vetting the Day of the Event:</E>
                </P>
                <P>The visitor must apply in person at the Fort McNair VCC/Police Substation (Building 65) from 8:00 a.m. to 4:00 p.m. Monday through Friday. The visitor should plan to arrive early, as the procedure for running background checks and issuing passes can take much longer than expected.</P>
                <P>
                    For additional information, please go to 
                    <E T="03">https://home.army.mil/jbmhh/index.php/my-fort/all-services/access-gate-info.</E>
                </P>
                <P>
                    <E T="03">Vehicle Search:</E>
                     Non-DoD, Non-federally-affiliated visitors' vehicles are subject to search.
                </P>
                <P>
                    <E T="03">Written Statements:</E>
                     Pursuant to 41 CFR 102-3.105(j) and 102-3.140, and section 10(a)(3) of the Federal Advisory Committee Act of 1972, written statements to the committee may be submitted to the committee at any time or in response to a stated planned meeting agenda by email or fax to Ms. Joycelyn Stevens at 
                    <E T="03">bov@ndu.edu</E>
                     or Fax (202) 685-3920. Any written statements received by 5:00 p.m. on Wednesday, April 17 will be distributed to the BoV NDU in the order received. Comments pertaining to the agenda items will be discussed during the public meeting. Any written statements received after the deadline will be provided to the members of the BoV NDU prior to the next scheduled meeting and posted on the website.
                </P>
                <SIG>
                    <DATED>Dated: March 7, 2024.</DATED>
                    <NAME>Aaron T. Siegel,</NAME>
                    <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05347 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6001-FR-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF EDUCATION</AGENCY>
                <SUBJECT>Applications for New Awards; Braille Training Program</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Special Education and Rehabilitative Services, Department of Education.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Education (Department) is issuing a notice inviting applications for fiscal year (FY) 2024 for the Braille Training program, Assistance Listing Number 84.235E. This notice relates to the approved information collection under OMB control number 1894-0006.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P/>
                    <P>
                        <E T="03">Applications Available:</E>
                         March 13, 2024.
                    </P>
                    <P>
                        <E T="03">Deadline for Transmittal of Applications:</E>
                         May 13, 2024.
                    </P>
                    <P>
                        <E T="03">Date of Pre-Application Meeting:</E>
                         No later than March 18, 2024, the Office of Special Education and Rehabilitative Services (OSERS) will post a PowerPoint Presentation specifically about the Braille Training program at 
                        <E T="03">https://ncrtm.ed.gov/grant-info.</E>
                         In addition to posting the PowerPoint, OSERS will conduct a pre-application meeting specific to this competition via conference call to respond to questions. Information about the pre-application meeting will be available at 
                        <E T="03">https://ncrtm.ed.gov/grant-info</E>
                         prior to the date of the call. OSERS invites you to send questions to 
                        <E T="03">84.235E@ed.gov</E>
                         in advance of the pre-application conference call. A summary of questions and responses will be available at 
                        <E T="03">https://ncrtm.ed.gov/grant-info</E>
                         within six business days after the pre-application conference call.
                    </P>
                    <P>
                        <E T="03">Deadline for Intergovernmental Review:</E>
                         July 11, 2024.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        For the addresses for obtaining and submitting an application, please refer to our Common Instructions for Applicants to Department of Education Discretionary Grant Programs, published in the 
                        <E T="04">Federal Register</E>
                         on December 7, 2022 (87 FR 75045), and available at 
                        <E T="03">www.federalregister.gov/d/2022-26554.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Theresa DeVaughn, U.S. Department of Education, 400 Maryland Avenue SW, Room 4A110, Washington, DC 20202-5076. Telephone: (202) 987-0144. Email: 
                        <E T="03">84.235E@ed.gov.</E>
                        <PRTPAGE P="18399"/>
                    </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/>
                <HD SOURCE="HD1">Full Text of Announcement</HD>
                <HD SOURCE="HD1">I. Funding Opportunity Description</HD>
                <P>
                    <E T="03">Purpose of Program:</E>
                     The Braille Training program offers financial assistance to projects that will (1) provide training in the use of braille for personnel providing vocational rehabilitation (VR) services or educational services to youth and adults who are blind; (2) develop braille training materials; (3) develop methods used to teach braille; and (4) develop activities used to promote the knowledge and use of braille and nonvisual access technology for youth and adults who are blind.
                </P>
                <P>
                    <E T="03">Background:</E>
                     The Braille Training program partners with States and public nonprofit agencies and organizations, including institutions of higher education, to provide information, material, equipment, and training in braille instruction. The support provided by the program will increase the knowledge and skills of personnel providing VR services or educational services to youth and adults who are blind.
                </P>
                <P>
                    The Department's invitational priorities align with the Secretary's Supplemental Priorities published in the 
                    <E T="04">Federal Register</E>
                     on December 10, 2021 (86 FR 70612) to encourage applicants to promote educational equity and adequacy in resources and opportunities for underserved students, increase the proportion of well-prepared, diverse, and effective educators serving students, with a focus on underserved students, and to encourage applicants to incorporate innovative technology into the project design and delivery of services.
                </P>
                <P>
                    <E T="03">Priorities:</E>
                     This notice includes one absolute priority and three invitational priorities. In accordance with 34 CFR 75.105(b)(2)(v), the absolute priority is from section 303(d) of the Rehabilitation Act of 1973, as amended (29 U.S.C. 773(d)).
                </P>
                <P>
                    <E T="03">Absolute Priority:</E>
                     For FY 2024 and any subsequent year in which we make awards from the list of unfunded applications from this competition, this priority is an absolute priority. Under 34 CFR 75.105(c)(3), we consider only applications that meet this priority.
                </P>
                <P>The priority is:</P>
                <HD SOURCE="HD2">Braille Training Program</HD>
                <P>Under this priority, we provide grants for the establishment or continuation of projects that provide—</P>
                <P>(1) Development of braille training materials;</P>
                <P>(2) In-service or pre-service training in the use of braille, the importance of braille literacy, and methods of teaching braille to youth and adults who are blind; and</P>
                <P>(3) Activities to promote knowledge and use of braille and nonvisual access technology for blind youth and adults through a program of training, demonstration, and evaluation conducted with leadership of experienced blind individuals, including the use of comprehensive, state-of-the-art technology.</P>
                <P>
                    <E T="03">Invitational Priorities:</E>
                     For FY 2024 and any subsequent year in which we make awards from the list of unfunded applications from this competition, these priorities are invitational priorities. Under 34 CFR 75.105(c)(1) we do not give an application that meets one or more of these invitational priorities a competitive or absolute preference over other applications.
                </P>
                <P>These priorities are:</P>
                <HD SOURCE="HD2">Invitational Priority 1</HD>
                <P>Projects designed to promote educational equity and adequacy in resources for underserved students and adults who are blind, especially those located in rural areas, in one of more of the following educational settings: (1) Early learning programs, (2) Elementary school, (3) Middle school, (4) High school, (5) Career and technical education programs, (6) Out-of-school-time settings, (7) Alternative schools and programs, (8) Juvenile justice-system or correctional facilities, and (9) Adult learning. Projects will expand access to high-quality braille training, including in school-based and community-based settings, by providing braille instruction in the areas of literacy and Science, Technology, Engineering, and Math (STEM), including mathematical and scientific notations, and by removing barriers through implementation of programs that are inclusive with regard to race, ethnicity, culture, language, and disability status.</P>
                <HD SOURCE="HD2">Invitational Priority 2</HD>
                <P>Projects designed to increase the number and proportion of experienced and effective braille educators and instructors from traditionally underrepresented backgrounds or the communities they serve, including rural areas, to ensure that underserved students and adults, including those in rural areas, have educators from those backgrounds and communities, and are not taught at disproportionately higher rates by out-of-field and novice teachers compared to their peers. Projects will also identify and disseminate pedagogical practices in braille training that are inclusive with regard to race, ethnicity, culture, language, and disability status so that braille educators and instructors are better prepared to create inclusive, supportive, equitable, unbiased, and identity-safe learning environments for underserved students and adults who are blind.</P>
                <HD SOURCE="HD2">Invitational Priority 3</HD>
                <P>Projects that design and deliver instruction to individuals who are blind that effectively integrate innovative technology and provide opportunities for individuals who are blind to apply braille technology in authentic and real-world settings, such as project-based, work-based, or other relevant experiential learning opportunities that will allow individuals with disabilities who are blind to think critically, solve complex problems, communicate and collaborate with others, and support their educational and career goals.</P>
                <P>
                    Under this invitational priority, innovative technology that could be integrated into the project design includes, but is not limited to: (1) Braille translation, such as software that converts text from digital formats (
                    <E T="03">i.e.,</E>
                     websites, e-books) into braille; (2) Braille displays, such as converting digital text into braille characters; (3) Voice assistants that can provide audio feedback to braille users, helping them navigate and interact with digital interfaces more efficiently; (4) Language driven translation tools that can be adapted to translate content from one language to another and provide the output in braille, making it easier for braille users to access information in multiple languages; (5) Braille notation to assist in creating braille notation in STEM and art, making these fields more accessible to braille users; (6) Descriptive media to explain visual information needed to understand content; (7) Technology that generates braille controlled (
                    <E T="03">i.e.,</E>
                     limited use of certain syllable types, such as phonemes, and braille contractions) specific passages and stories for individuals who are blind based on their abilities and skill sets; and (8) Other relevant innovative technology to promote knowledge and use of braille and nonvisual access technology for individuals who are blind. The use of any technology in this list is not required, and the use of any example does not provide an applicant any advantage in this competition. The list is included to assist the applicant in understanding the invitational priority.
                    <PRTPAGE P="18400"/>
                </P>
                <HD SOURCE="HD2">Definitions</HD>
                <P>For purposes of the invitational priorities, the following definitions apply:</P>
                <P>
                    <E T="03">Children or students with disabilities</E>
                     means children with disabilities as defined in section 602(3) of the Individuals with Disabilities Education Act (IDEA) (20 U.S.C. 1401(3)) and 34 CFR 300.8, or students with disabilities, as defined in the Rehabilitation Act of 1973 (29 U.S.C. 705(37)).
                </P>
                <P>
                    <E T="03">Educator</E>
                     means an individual who is an early learning educator, teacher, principal, or other school leader, specialized instructional support personnel (
                    <E T="03">e.g.,</E>
                     school psychologist, counselor, school social worker, early intervention service personnel), paraprofessional, or faculty.
                </P>
                <P>
                    <E T="03">English learner</E>
                     means an individual who is an English learner as defined in section 8101(20) of the Elementary and Secondary Education Act of 1965, as amended, or an individual who is an English language learner as defined in section 203(7) of the Workforce Innovation and Opportunity Act.
                </P>
                <P>
                    <E T="03">Underserved student</E>
                     means a student (which may include children in early learning environments, students in K-12 programs, students in postsecondary education or career and technical education, and adult learners, as appropriate) in one or more of the following subgroups:
                </P>
                <P>(a) A student who is living in poverty or is served by schools with high concentrations of students living in poverty.</P>
                <P>(b) A student of color.</P>
                <P>(c) A student who is a member of a federally recognized Indian Tribe.</P>
                <P>(d) An English learner.</P>
                <P>(e) A child or student with a disability.</P>
                <P>(f) A disconnected youth.</P>
                <P>(g) A technologically unconnected youth.</P>
                <P>(h) A migrant student.</P>
                <P>(i) A student experiencing homelessness or housing insecurity.</P>
                <P>(j) A lesbian, gay, bisexual, transgender, queer or questioning, or intersex (LGBTQI+) student.</P>
                <P>(k) A student who is in foster care.</P>
                <P>(l) A student without documentation of immigration status.</P>
                <P>(m) A pregnant, parenting, or caregiving student.</P>
                <P>(n) A student impacted by the justice system, including a formerly incarcerated student.</P>
                <P>(o) A student who is the first in their family to attend postsecondary education.</P>
                <P>(p) A student enrolling in or seeking to enroll in postsecondary education for the first time at the age of 20 or older.</P>
                <P>(q) A student who is working full-time while enrolled in postsecondary education.</P>
                <P>(r) A student who is enrolled in or is seeking to enroll in postsecondary education who is eligible for a Pell Grant.</P>
                <P>(s) An adult student in need of improving their basic skills or an adult student with limited English proficiency.</P>
                <P>(t) A student performing significantly below grade level.</P>
                <P>(u) A military- or veteran-connected student.</P>
                <P>
                    <E T="03">Program Authority:</E>
                     29 U.S.C. 773(d).
                </P>
                <P>
                    <E T="03">Note:</E>
                     Projects will be awarded and must be operated in a manner consistent with the nondiscrimination requirements contained in Federal civil rights laws.
                </P>
                <P>
                    <E T="03">Applicable Regulations:</E>
                     (a) The Education Department General Administrative Regulations in 34 CFR parts 75, 77, 79, 81, 82, 84, 86, 97, and 99. (b) The Office of Management and Budget Guidelines to Agencies on Governmentwide Debarment and Suspension (Nonprocurement) in 2 CFR part 180, as adopted and amended as regulations of the Department in 2 CFR part 3485. (c) The Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards in 2 CFR part 200, as adopted and amended as regulations of the Department in 2 CFR part 3474.
                </P>
                <P>
                    <E T="03">Note:</E>
                     The regulations in 34 CFR part 79 apply to all applicants except federally recognized Indian Tribes.
                </P>
                <P>
                    <E T="03">Note:</E>
                     The regulations in 34 CFR part 86 apply to institutions of higher education only.
                </P>
                <HD SOURCE="HD1">II. Award Information</HD>
                <P>
                    <E T="03">Type of Award:</E>
                     Grant.
                </P>
                <P>
                    <E T="03">Estimated Available Funds:</E>
                     $342,000.
                </P>
                <P>The Administration has requested $7.3 million for the Training and Demonstration Programs for FY 2024, of which we intend to use $342,000 for this competition. The actual level of funding, if any, depends on final congressional action. However, we are inviting applications to allow enough time to complete the grant process if Congress appropriates funds for this program.</P>
                <P>Contingent upon the availability of funds and the quality of applications, we may make additional awards in subsequent years from the list of unfunded applications from this competition.</P>
                <P>
                    <E T="03">Estimated Average Size of Awards:</E>
                     Year 1: $115,000; Years 2-5: $230,000.
                </P>
                <P>
                    <E T="03">Maximum Award:</E>
                     Year 1: We will not make an award exceeding $115,000 for the first budget period of 12 months; Years 2-5: We will not make an award exceeding $230,000 for each budget period of 12 months.
                </P>
                <P>
                    <E T="03">Note:</E>
                     Applicants must describe, in their applications, the amount of funding being requested for each 12-month budget period.
                </P>
                <P>
                    <E T="03">Estimated Number of Awards:</E>
                     3.
                </P>
                <P>
                    <E T="03">Project Period:</E>
                     Up to 60 months.
                </P>
                <P>
                    <E T="03">Note:</E>
                     The Department is not bound by any estimates in this notice.
                </P>
                <HD SOURCE="HD1">III. Eligibility Information</HD>
                <P>
                    1. 
                    <E T="03">Eligible Applicants:</E>
                     States and public or nonprofit agencies and organizations, including institutions of higher education.
                </P>
                <P>
                    2. a. 
                    <E T="03">Cost Sharing or Matching:</E>
                     This competition does not require cost sharing or matching.
                </P>
                <P>
                    b. 
                    <E T="03">Indirect Cost Rate Information:</E>
                     This program uses an unrestricted indirect cost rate. For more information regarding indirect costs, or to obtain a negotiated indirect cost rate, please see 
                    <E T="03">www2.ed.gov/about/offices/list/ocfo/intro.html.</E>
                </P>
                <P>
                    c. 
                    <E T="03">Administrative Cost Limitation:</E>
                     This program does not include any program-specific limitation on administrative expenses. All administrative expenses must be reasonable and necessary and conform to Cost Principles described in 2 CFR part 200 subpart E of the Uniform Guidance.
                </P>
                <P>
                    3. 
                    <E T="03">Subgrantees:</E>
                     Under 34 CFR 75.708(b) and (c), a grantee under this competition may not award subgrants to directly carry out project activities described in its application. Under 34 CFR 75.708(e), a grantee may contract for supplies, equipment, and other services in accordance with 2 CFR 200.317-200.326, Procurement Standards.
                </P>
                <HD SOURCE="HD1">IV. Application and Submission Information</HD>
                <P>
                    1. 
                    <E T="03">Application Submission Instructions:</E>
                     Applicants are required to follow the Common Instructions for Applicants to Department of Education Discretionary Grant Programs, published in the 
                    <E T="04">Federal Register</E>
                     on December 7, 2022 (87 FR 75045), and available at 
                    <E T="03">www.federalregister.gov/d/2022-26554,</E>
                     which contain requirements and information on how to submit an application.
                </P>
                <P>
                    2. 
                    <E T="03">Intergovernmental Review:</E>
                     This competition is subject to Executive Order 12372 and the regulations in 34 CFR part 79. Information about Intergovernmental Review of Federal Programs under Executive Order 12372 is in the application package for this competition.
                    <PRTPAGE P="18401"/>
                </P>
                <P>
                    3. 
                    <E T="03">Funding Restrictions:</E>
                     We reference regulations outlining funding restrictions in the 
                    <E T="03">Applicable Regulations</E>
                     section of this notice.
                </P>
                <P>
                    4. 
                    <E T="03">Recommended Page Limit:</E>
                     The application narrative is where you, the applicant, address the selection criteria that reviewers use to evaluate your application. We recommend that you (1) limit the application narrative to no more than 50 pages and (2) use the following standards:
                </P>
                <P>• A “page” is 8.5″ x 11″, on one side only, with 1″ margins at the top, bottom, and both sides.</P>
                <P>• Double space (no more than three lines per vertical inch) all text in the application narrative, including titles, headings, footnotes, quotations, reference citations, and captions, as well as all text in charts, tables, figures, graphs, and screen shots.</P>
                <P>• Use a font that is 12 point or larger.</P>
                <P>• Use one of the following fonts: Times New Roman, Courier, Courier New, or Arial.</P>
                <P>
                    The recommended page limit does not apply to the cover sheet; the budget section, including the narrative budget justification; the assurances and certifications; or the abstract (follow the guidance provided in the application package for completing the abstract), the table of contents, the resumes, the reference list, the letters of support, or the appendices. However, the recommended page limit does apply to all of the application narrative, including all text in charts, tables, figures, graphs, and screen shots. Applicants are expected to make the contents of their application accessible for individuals with disabilities to the maximum extent possible. Tutorials and resources for making documents accessible are available for free on RSA's National Clearinghouse for Rehabilitation Training Materials at 
                    <E T="03">https://ncrtm.ed.gov/accessibility-resources.</E>
                </P>
                <HD SOURCE="HD1">V. Application Review Information</HD>
                <P>
                    1. 
                    <E T="03">Selection Criteria:</E>
                     The selection criteria for this competition are from 34 CFR 75.210, have a maximum score of 100 points, and are as follows:
                </P>
                <P>(a) Need for project. (10 points)</P>
                <P>(1) The Secretary considers the need for the proposed project.</P>
                <P>(2) In determining the need for the proposed project, the Secretary considers the following factors:</P>
                <P>(i) The magnitude of the need for the services to be provided or the activities to be carried out by the proposed project;</P>
                <P>(ii) The extent to which the proposed project will prepare personnel for fields in which shortages have been demonstrated; and</P>
                <P>(iii) The potential replicability of the proposed project or strategies, including, as appropriate, the potential for implementation in a variety of settings.</P>
                <P>(b) Quality of the project design. (20 points)</P>
                <P>(1) The Secretary considers the quality of the design of the proposed project.</P>
                <P>(2) In determining the quality of the design of the proposed project, the Secretary considers the following factors:</P>
                <P>(i) The extent to which the goals, objectives, and outcomes to be achieved by the proposed project are clearly specified and measurable;</P>
                <P>(ii) The extent to which the design for implementing and evaluating the proposed project will result in information to guide possible replication of project activities or strategies, including information about the effectiveness of the approach or strategies employed by the project;</P>
                <P>(iii) The extent to which the proposed project is designed to build capacity and yield results that will extend beyond the period of Federal financial assistance;</P>
                <P>(iv) The extent to which the design of the proposed project reflects up-to-date knowledge from research and effective practice; and</P>
                <P>(v) The extent to which performance feedback and continuous improvement are integral to the design of the proposed project.</P>
                <P>(c) Quality of project services. (25 points)</P>
                <P>(1) The Secretary considers the quality of the services to be provided by the proposed project.</P>
                <P>(2) In determining the quality of the services to be provided by the proposed project, the Secretary considers the quality and sufficiency of strategies for ensuring equal access and treatment for eligible project participants who are members of groups that have traditionally been underrepresented based on race, color, national origin, gender, age, or disability.</P>
                <P>(3) In addition, the Secretary considers the following factors:</P>
                <P>(i) The likely impact of the services to be provided by the proposed project on the intended recipients of those services;</P>
                <P>(ii) The extent to which the services to be provided by the proposed project involve the collaboration of appropriate partners for maximizing the effectiveness of project services;</P>
                <P>(iii) The extent to which the training or professional development services to be provided by the proposed project are of sufficient quality, intensity, and duration to lead to improvements in practice among the recipients of those services; and</P>
                <P>(iv) The extent to which the results of the proposed project are to be disseminated in ways that will enable others to use the information or strategies.</P>
                <P>(d) Quality of the project evaluation. (25 points)</P>
                <P>(1) The Secretary considers the quality of the evaluation to be conducted of the proposed project.</P>
                <P>(2) In determining the quality of the evaluation, the Secretary considers the following factors:</P>
                <P>(i) The extent to which the methods of evaluation are thorough, feasible, and appropriate to the goals, objectives, and outcomes of the proposed project;</P>
                <P>(ii) The extent to which the methods of evaluation will provide valid and reliable performance data on relevant outcomes (as defined in 34 CFR 77.1(c));</P>
                <P>(iii) The extent to which the methods of evaluation will, if well implemented, produce promising evidence (as defined in 34 CFR 77.1(c)) about the project's effectiveness;</P>
                <P>(iv) The extent to which the methods of evaluation include the use of objective performance measures that are clearly related to the intended outcomes of the project and will produce quantitative and qualitative data to the extent possible;</P>
                <P>(v) The qualifications, including relevant training, experience, and independence, of the evaluator;</P>
                <P>(vi) The extent to which the methods of evaluation provide for examining the effectiveness of project implementation strategies; and</P>
                <P>(vii) The extent to which the methods of evaluation will provide performance feedback and permit periodic assessment of progress toward achieving intended outcomes.</P>
                <P>(e) Quality of the management plan. (20 points)</P>
                <P>(1) The Secretary considers the quality of the management plan for the proposed project.</P>
                <P>(2) In determining the quality of the management plan for the proposed project, the Secretary considers the following factors:</P>
                <P>(i) The adequacy of the management plan to achieve the objectives of the proposed project on time and within budget, including clearly defined responsibilities, timelines, and milestone for accomplishing project tasks;</P>
                <P>
                    (ii) The extent to which the time commitments of the project director and principal investigator and other key project personnel are appropriate and 
                    <PRTPAGE P="18402"/>
                    adequate to meet the objectives of the proposed project;
                </P>
                <P>(iii) The adequacy of procedures for ensuring feedback and continuous improvement in the operation of the proposed project; and</P>
                <P>(iv) How the applicant will ensure that a diversity of perspectives are brought to bear in the operation of the proposed project, including those of parents, teachers, the business community, a variety of disciplinary and professional fields, recipients or beneficiaries of services, or others, as appropriate.</P>
                <P>
                    2. 
                    <E T="03">Review and Selection Process:</E>
                     We remind potential applicants that in reviewing applications in any discretionary grant competition, the Secretary may consider, under 34 CFR 75.217(d)(3), the past performance of the applicant in carrying out a previous award, such as the applicant's use of funds, achievement of project objectives, and compliance with grant conditions. The Secretary may also consider whether the applicant failed to submit a timely performance report or submitted a report of unacceptable quality.
                </P>
                <P>In addition, in making a competitive grant award, the Secretary requires various assurances, including those applicable to Federal civil rights laws that prohibit discrimination in programs or activities receiving Federal financial assistance from the Department (34 CFR 100.4, 104.5, 106.4, 108.8, and 110.23).</P>
                <P>
                    3. 
                    <E T="03">Risk Assessment and Specific Conditions:</E>
                     Consistent with 2 CFR 200.206, before awarding grants under this competition the Department conducts a review of the risks posed by applicants. Under 2 CFR 200.208, the Secretary may impose specific conditions and, under 2 CFR 3474.10, in appropriate circumstances, high-risk conditions on a grant if the applicant or grantee is not financially stable; has a history of unsatisfactory performance; has a financial or other management system that does not meet the standards in 2 CFR part 200, subpart D; has not fulfilled the conditions of a prior grant; or is otherwise not responsible.
                </P>
                <P>
                    4. 
                    <E T="03">Integrity and Performance System:</E>
                     If you are selected under this competition to receive an award that over the course of the project period may exceed the simplified acquisition threshold (currently $250,000), under 2 CFR 200.206(a)(2) we must make a judgment about your integrity, business ethics, and record of performance under Federal awards—that is, the risk posed by you as an applicant—before we make an award. In doing so, we must consider any information about you that is in the integrity and performance system (currently referred to as the Federal Awardee Performance and Integrity Information System (FAPIIS)), accessible through the System for Award Management. You may review and comment on any information about yourself that a Federal agency previously entered and that is currently in FAPIIS.
                </P>
                <P>Please note that, if the total value of your currently active grants, cooperative agreements, and procurement contracts from the Federal Government exceeds $10,000,000, the reporting requirements in 2 CFR part 200, Appendix XII, require you to report certain integrity information to FAPIIS semiannually. Please review the requirements in 2 CFR part 200, Appendix XII, if this grant plus all the other Federal funds you receive exceed $10,000,000.</P>
                <P>
                    5. 
                    <E T="03">In General:</E>
                     In accordance with the Office of Management and Budget's guidance located at 2 CFR part 200, all applicable Federal laws, and relevant Executive guidance, the Department will review and consider applications for funding pursuant to this notice inviting applications in accordance with:
                </P>
                <P>(a) Selecting recipients most likely to be successful in delivering results based on the program objectives through an objective process of evaluating Federal award applications (2 CFR 200.205);</P>
                <P>(b) Prohibiting the purchase of certain telecommunication and video surveillance services or equipment in alignment with section 889 of the National Defense Authorization Act of 2019 (Pub. L. 115-232) (2 CFR 200.216);</P>
                <P>(c) Providing a preference, to the extent permitted by law, to maximize use of goods, products, and materials produced in the United States (2 CFR 200.322); and</P>
                <P>(d) Terminating agreements in whole or in part to the greatest extent authorized by law if an award no longer effectuates the program goals or agency priorities (2 CFR 200.340).</P>
                <HD SOURCE="HD1">VI. Award Administration Information</HD>
                <P>
                    1. 
                    <E T="03">Award Notices:</E>
                     If your application is successful, we notify your U.S. Representative and U.S. Senators and send you a Grant Award Notification (GAN); or we may send you an email containing a link to access an electronic version of your GAN. We may notify you informally, also.
                </P>
                <P>If your application is not evaluated or not selected for funding, we notify you.</P>
                <P>
                    2. 
                    <E T="03">Administrative and National Policy Requirements:</E>
                     We identify administrative and national policy requirements in the application package and reference these and other requirements in the 
                    <E T="03">Applicable Regulations</E>
                     section of this notice.
                </P>
                <P>
                    We reference the regulations outlining the terms and conditions of an award in the 
                    <E T="03">Applicable Regulations</E>
                     section of this notice and include these and other specific conditions in the GAN. The GAN also incorporates your approved application as part of your binding commitments under the grant.
                </P>
                <P>
                    3. 
                    <E T="03">Open Licensing Requirements:</E>
                     Unless an exception applies, if you are awarded a grant under this competition, you will be required to openly license to the public grant deliverables created in whole, or in part, with Department grant funds. When the deliverable consists of modifications to pre-existing works, the license extends only to those modifications that can be separately identified and only to the extent that open licensing is permitted under the terms of any licenses or other legal restrictions on the use of pre-existing works. Additionally, a grantee or subgrantee that is awarded competitive grant funds must have a plan to disseminate these public grant deliverables. This dissemination plan can be developed and submitted after your application has been reviewed and selected for funding. For additional information on the open licensing requirements please refer to 2 CFR 3474.20.
                </P>
                <P>
                    4. 
                    <E T="03">Reporting:</E>
                     (a) If you apply for a grant under this competition, you must ensure that you have in place the necessary processes and systems to comply with the reporting requirements in 2 CFR part 170 should you receive funding under the competition. This does not apply if you have an exception under 2 CFR 170.110(b).
                </P>
                <P>
                    (b) At the end of your project period, you must submit a final performance report, including financial information, as directed by the Secretary. If you receive a multiyear award, you must submit an annual performance report that provides the most current performance and financial expenditure information as directed by the Secretary under 34 CFR 75.118. The Secretary may also require more frequent performance reports under 34 CFR 75.720(c). For specific requirements on reporting, please go to 
                    <E T="03">www.ed.gov/fund/grant/apply/appforms/appforms.html.</E>
                </P>
                <P>
                    (c) Under 34 CFR 75.250(b), the Secretary may approve a data collection period for a grant for a period of up to 72 months after the end of the project period and provide funding, separate from this funding opportunity, for the data collection period for the sole purpose of collecting, analyzing, and 
                    <PRTPAGE P="18403"/>
                    reporting performance measurement data regarding the project.
                </P>
                <P>
                    5. 
                    <E T="03">Performance Measures:</E>
                     For the purposes of Department reporting under 34 CFR 75.110, grantees must submit information to allow measurement of project outcomes and performance consistent with its approved application. For the Braille Training program, a grantee must collect and report information on:
                </P>
                <P>(a) The number of participants who attend the program disaggregated by adults and youth.</P>
                <P>(b) The number of participants who successfully complete the program disaggregated by adults and youth.</P>
                <P>(c) The number of personnel who attend the program.</P>
                <P>(d) The number of personnel who successfully complete the program.</P>
                <P>(e) The number of trained personnel who subsequently report obtaining or advancing in positions where they provide braille instruction to blind youth and adults following completion of the program.</P>
                <P>Grantees are required to report annually to the Rehabilitation Services Administration (RSA) on these data.</P>
                <P>
                    6. 
                    <E T="03">Continuation Awards:</E>
                     In making a continuation award under 34 CFR 75.253, the Secretary considers, among other things: whether a grantee has made substantial progress in achieving the goals and objectives of the project; whether the grantee has expended funds in a manner that is consistent with its approved application and budget; and, if the Secretary has established performance measurement requirements, whether the grantee has made substantial progress in achieving the performance targets in the grantee's approved application.
                </P>
                <P>In making a continuation award, the Secretary also considers whether the grantee is operating in compliance with the assurances in its approved application, including those applicable to Federal civil rights laws that prohibit discrimination in programs or activities receiving Federal financial assistance from the Department (34 CFR 100.4, 104.5, 106.4, 108.8, and 110.23).</P>
                <HD SOURCE="HD1">VII. Other Information</HD>
                <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>Glenna Wright-Gallo,</NAME>
                    <TITLE>Assistant Secretary for Special Education and Rehabilitative Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05290 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4000-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">ELECTION ASSISTANCE COMMISSION</AGENCY>
                <SUBAGY>Agency Information Collection Activities</SUBAGY>
                <SUBJECT>Election Supporting Technology Evaluation Program Anomaly Reporting Forms</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Election Assistance Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; request for comment.</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 U.S. Election Assistance Commission (EAC) gives notice that it is requesting from the Office of Management and Budget (OMB) approval for the information collection of one Election Supporting Technology Evaluation form. The information collected is to be used to improve the quality of election-supporting technology used in federal elections, and to collect necessary key information on election-supporting technology anomalies. Participation in this program is voluntary.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by 5 p.m. Eastern on Monday, May 13, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES: </HD>
                    <P>
                        Comments on the proposed form should be submitted electronically via 
                        <E T="03">https://www.regulations.gov</E>
                         (docket ID: EAC-2024-0001).
                    </P>
                    <P>Written comments on the proposed information collection can also be sent to the U.S. Election Assistance Commission, 633 3rd Street NW, Suite 200, Washington, DC 20001, Attn: Election Supporting Technology Evaluation Program.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jenniffer Day, Election Technology Specialist, Election Supporting Technology Evaluation Program, Washington, DC, (202) 578-6641. Email: 
                        <E T="03">ESTEP@eac.gov.</E>
                    </P>
                    <P>All requests and submissions should be identified by the title of the information collection.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title and OMB Number:</E>
                     Election Supporting Technology Evaluation Anomaly Reporting Forms
                </P>
                <P>OMB Number Pending.</P>
                <HD SOURCE="HD1">Purpose</HD>
                <P>In compliance with Section 3507(a)(1)(D) of the Paperwork Reduction Act (PRA) of 1995, EAC is submitting to the Office of Management and Budget (OMB) a request for review and approval of the information collection described. The purpose of this notice is to allow 60 days for public comment from all interested individuals and organizations.</P>
                <P>The EAC Election Supporting Technology Evaluation Program evaluates the security and accessibility of election-supporting technologies, including electronic poll books, voter registration systems, electronic ballot delivery systems, and election night reporting databases. The program is to publish two forms. These forms are to be used to collect initial anomaly information and anomaly root cause analysis as reported by election officials and election-supporting technology manufacturers. The information collected will be used to improve the quality of election-supporting technology used in federal elections.</P>
                <HD SOURCE="HD1">Public Comments</HD>
                <P>We are soliciting public comments to permit the EAC to:</P>
                <P>• Evaluate whether the proposed information collection is necessary and sufficient for the proper functions of the Election Supporting Technology Evaluation Program.</P>
                <P>• Evaluate the accuracy of our estimate of burden for this proposed collection, including the validity of the methodology and assumptions used.</P>
                <P>• Enhance the quality, utility, and clarity of the information to be collected.</P>
                <P>• Minimize the reporting burden on those who are to respond, including the use of information technology.</P>
                <P>
                    Please note that comments submitted in response to this Notice are public 
                    <PRTPAGE P="18404"/>
                    record. Before including any detailed personal information, you should be aware that your comments as submitted, including your personal information, will be available for public review. Respondents: Election Supporting Technology Manufacturers, State and Local Election Officials.
                </P>
                <HD SOURCE="HD1">Annual Reporting Burden</HD>
                <P>OMB approval is requested for 3 years.</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,12,12,12,12">
                    <TTITLE>Annual Burden Estimates</TTITLE>
                    <BOXHD>
                        <CHED H="1">Instrument</CHED>
                        <CHED H="1">
                            Estimated number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">Total number of responses per year</CHED>
                        <CHED H="1">
                            Average
                            <LI>burden hours</LI>
                            <LI>per response</LI>
                        </CHED>
                        <CHED H="1">Annual burden hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">ESTEP Anomaly Reporting Form</ENT>
                        <ENT>5</ENT>
                        <ENT>5</ENT>
                        <ENT>2</ENT>
                        <ENT>50</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">ESTEP Root Cause Anomaly Form</ENT>
                        <ENT>5</ENT>
                        <ENT>5</ENT>
                        <ENT>16</ENT>
                        <ENT>400</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT>10</ENT>
                        <ENT/>
                        <ENT>450</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The estimated cost of the annualized cost of this burden is: $37,800.</P>
                <SIG>
                    <NAME>Camden Kelliher,</NAME>
                    <TITLE>Acting General Counsel, U.S. Election Assistance Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05302 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-71-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <SUBJECT>Combined Notice of Filings</SUBJECT>
                <P>Take notice that the Commission has received the following Natural Gas Pipeline Rate and Refund Report filings:</P>
                <P>
                    <E T="03">Filings Instituting Proceedings</E>
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP24-514-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Great Basin Gas Transmission Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: 2024 Section 4 Rate Case to be effective 4/6/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/6/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240306-5144.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/18/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP24-515-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Transcontinental Gas Pipe Line Company, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: Transcontinental Gas Pipeline Company, LLC submits tariff filing per 154.403: LSS, SS-2, and Firm and Interruptible Transportation Fuel Percentages Tracker to be effective 4/1/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/7/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240307-5035.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/19/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP24-516-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Enable Mississippi River Transmission, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: Update GT&amp;C Section 8 to be effective 4/7/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/7/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240307-5050.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/19/24.
                </P>
                <P>Any person desiring to intervene, to protest, or to answer a complaint in any of the above proceedings must file in accordance with Rules 211, 214, or 206 of the Commission's Regulations (18 CFR 385.211, 385.214, or 385.206) 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>
                    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>
                    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>
                <P>
                    The Commission's Office of Public Participation (OPP) supports meaningful public engagement and participation in Commission proceedings. OPP can help members of the public, including landowners, environmental justice communities, Tribal members and others, access publicly available information and navigate Commission processes. For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, the public is encouraged to contact OPP at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 7, 2024.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05329 Filed 3-12-24; 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. ER24-1420-000</DEPDOC>
                <SUBJECT>Sierra Estrella Energy Storage LLC; Supplemental Notice That Initial Market-Based Rate Filing Includes Request for Blanket Section 204 Authorization</SUBJECT>
                <P>This is a supplemental notice in the above-referenced proceeding of Sierra Estrella Energy Storage LLC's application for market-based rate authority, with an accompanying rate tariff, noting that such application includes a request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability.</P>
                <P>Any person desiring to intervene or to protest should file with the Federal Energy Regulatory Commission, 888 First Street, NE, Washington, DC 20426, in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214). Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant.</P>
                <P>Notice is hereby given that the deadline for filing protests with regard to the applicant's request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability, is March 27, 2024.</P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at 
                    <E T="03">http://www.ferc.gov.</E>
                     To facilitate electronic service, persons with internet access who will eFile a document and/or be listed as a contact for an intervenor must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests.
                    <PRTPAGE P="18405"/>
                </P>
                <P>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>
                    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://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. 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 the Federal Energy Regulatory Commission at 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                     or call toll-free, (886) 208-3676 or TYY, (202) 502-8659.
                </P>
                <P>
                    The Commission's Office of Public Participation (OPP) supports meaningful public engagement and participation in Commission proceedings. OPP can help members of the public, including landowners, environmental justice communities, Tribal members and others, access publicly available information and navigate Commission processes. For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, the public is encouraged to contact OPP at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 7, 2024.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05327 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <SUBJECT>Combined Notice of Filings</SUBJECT>
                <P>Take notice that the Commission has received the following Natural Gas Pipeline Rate and Refund Report filings:</P>
                <HD SOURCE="HD1">Filings Instituting Proceedings</HD>
                <P>
                    <E T="03">Docket Numbers:</E>
                     CP24-76-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Cardinal States Gathering Company LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Cardinal States Gathering Company LLC submits Application for a limited jurisdiction Certificate of Public Convenience and Necessity to provide the limited receipt and transportation of pipeline-quality gas service etc.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/1/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240301-5166.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/22/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP24-510-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Adelphia Gateway, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Adelphia Gateway OPS Report Filing to be effective N/A.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/6/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240306-5019.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/18/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP24-511-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Empire Pipeline, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     4(d) Rate Filing: Fuel Tracker (Empire Tracking Supply Storage 2024) to be effective 4/1/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/6/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240306-5041.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/18/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP24-512-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Express Pipeline LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     4(d) Rate Filing: Non-Conforming Agreement (Trafigura) April 2024 to be effective 4/1/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/6/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240306-5048.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/18/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP24-513-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Algonquin Gas Transmission, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     4(d) Rate Filing: Negotiated Rates—Yankee Gas to Emera Energy to be effective 3/6/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/6/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240306-5077.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/18/24.
                </P>
                <P>Any person desiring to intervene, to protest, or to answer a complaint in any of the above proceedings must file in accordance with Rules 211, 214, or 206 of the Commission's Regulations (18 CFR 385.211, 385.214, or 385.206) on or before 5:00 p.m. Eastern time on the specified comment date. Protests may be considered, but intervention is necessary to become a party to the proceeding.</P>
                <HD SOURCE="HD1">Filings in Existing Proceedings</HD>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP18-75-008.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Algonquin Gas Transmission, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: AGT FRQ Settlement Extension 2024 to be effective N/A.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/6/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240306-5055.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/18/24.
                </P>
                <P>Any person desiring to protest in any the above proceedings must file in accordance with Rule 211 of the Commission's Regulations (18 CFR 385.211) on or before 5:00 p.m. Eastern time on the specified comment date.</P>
                <P>
                    The filings are accessible in the Commission's eLibrary system (
                    <E T="03">https://elibrary.ferc.gov/idmws/search/fercgensearch.asp</E>
                    ) by querying the docket number.
                </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>
                <P>
                    The Commission's Office of Public Participation (OPP) supports meaningful public engagement and participation in Commission proceedings. OPP can help members of the public, including landowners, environmental justice communities, Tribal members and others, access publicly available information and navigate Commission processes. For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, the public is encouraged to contact OPP at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 6, 2024.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05230 Filed 3-12-24; 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. ER24-1421-000]</DEPDOC>
                <SUBJECT>Superstition Energy Storage LLC; Supplemental Notice That Initial Market-Based Rate Filing Includes Request for Blanket Section 204 Authorization</SUBJECT>
                <P>This is a supplemental notice in the above-referenced proceeding of Superstition Energy Storage LLC's application for market-based rate authority, with an accompanying rate tariff, noting that such application includes a request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability.</P>
                <P>
                    Any person desiring to intervene or to protest should file with the Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426, in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214). Anyone filing a motion to 
                    <PRTPAGE P="18406"/>
                    intervene or protest must serve a copy of that document on the Applicant.
                </P>
                <P>Notice is hereby given that the deadline for filing protests with regard to the applicant's request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability, is March 27, 2024.</P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at 
                    <E T="03">http://www.ferc.gov.</E>
                     To facilitate electronic service, persons with internet access who will eFile a document and/or be listed as a contact for an intervenor must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests.
                </P>
                <P>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>
                    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://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. 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 the Federal Energy Regulatory Commission at 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                     or call toll-free, (886) 208-3676 or TYY, (202) 502-8659.
                </P>
                <P>
                    The Commission's Office of Public Participation (OPP) supports meaningful public engagement and participation in Commission proceedings. OPP can help members of the public, including landowners, environmental justice communities, Tribal members and others, access publicly available information and navigate Commission processes. For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, the public is encouraged to contact OPP at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 7, 2024.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05326 Filed 3-12-24; 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. CP24-27-000]</DEPDOC>
                <SUBJECT>Kern River Gas Transmission Company; Notice of Withdrawal of Staff Protest</SUBJECT>
                <P>Federal Energy Regulatory Commission (FERC or Commission) staff hereby withdraws its February 26, 2024 protest of the prior notice request filed under the provisions of the Commission's regulations at Part 157, subpart F, by Kern River Gas Transmission Company (Kern River) on December 15, 2023, for its proposed construction and operation of the Lanes Crossing Meter Station (Project). Staff's protest noted that Kern River did not provide a copy of a finding by the California State Historic Preservation Office (SHPO) of “no historic properties” or “no historic properties effected.”</P>
                <P>On March 6, 2024, at the request of Kern River, the California SHPO filed a letter noting its consultation with Kern River regarding the Project, and that no historic properties were identified within the area of potential effect. The SHPO stated that it did “not object to a finding of no historic properties affected.” Therefore, the application now meets the standards outlined in Appendix II of subpart F of section 157 of the Commission's regulations. This issue was resolved within 30 days of the protest as required by section 157.205(g) of the Commission's regulations. Based on the submission of the SHPO's findings for this Project, Commission staff withdraws its protest.</P>
                <SIG>
                    <DATED>Dated: March 7, 2024.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05328 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <SUBJECT>Combined Notice of Filings #1</SUBJECT>
                <P>Take notice that the Commission received the following electric rate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER18-533-005; ER22-48-002; ER18-538-006; ER18-537-005; ER18-535-005; ER18-280-007; ER18-536-005; ER12-1436-018; ER18-534-005.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Montpelier Generating Station, LLC, Eagle Point Power Generation LLC, O.H. Hutchings CT, LLC, Lee County Generating Station, LLC, Yankee Street, LLC, Monument Generating Station, LLC, Sidney, LLC, Gridflex Generation, LLC, Tait Electric Generating Station, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Supplement to June 30, 2023, Triennial Market Power Analysis for Northeast Region of Eagle Point Power Generation LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/6/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240306-5189.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/27/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER22-2230-000; ER13-1562-011; ER22-2233-000; ER22-2234-000; ER22-2235-000; ER22-2236-000; ER22-2231-000; ER22-2232-000; ER12-1931-012; ER10-2504-013; ER12-610-013; ER13-338-011; ER19-2260-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Valentine Solar, LLC, Shiloh IV Lessee, LLC, Shiloh III Lessee, LLC, Shiloh Wind Project 2, LLC, Pacific Wind Lessee, LLC, Maverick Solar 7, LLC, Maverick Solar 6, LLC, Maverick Solar 4, LLC, Maverick Solar, LLC, Desert Harvest II LLC, Desert Harvest, LLC, Catalina Solar Lessee, LLC, BigBeau Solar, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Supplement to June 29, 2022, Triennial Market Power Analysis BigBeau Solar, LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/6/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240306-5195.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/27/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER23-2935-002.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc., Northern Indiana Public Service Company LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: Midcontinent Independent System Operator, Inc. submits tariff filing per 35.17(b): 2024-03-07_Amendment NIPSCO Request for Depreciation Rates-Supplemental to be effective 8/1/2023.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/7/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240307-5025.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/28/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER24-1007-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Black Hills Colorado Electric, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: Amendment to Unreserved Use Penalty and Transmission Planning Updates to be effective 5/7/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/7/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240307-5123.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/28/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER24-1421-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Superstition Energy Storage LLC.
                    <PRTPAGE P="18407"/>
                </P>
                <P>
                    <E T="03">Description:</E>
                     Baseline eTariff Filing: Application for MBR Authorization and Request for Waivers to be effective 3/18/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/6/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240306-5156.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/27/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER24-1422-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PJM Interconnection, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Amendment to AE2-226 ISA No. 6736 (amend_mcd) to be effective 5/7/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/7/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240307-5067.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/28/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER24-1423-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 2024-03-07_MEAN Integration Revisions to Schedules 7, 8, and 9 to be effective 6/1/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/7/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240307-5133.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/28/24.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER24-1424-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     MidAmerican Energy Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Joint Pricing Zone Revenue Allocation Agreement (4th Rev) to be effective 6/1/2024.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/7/24.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20240307-5167.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/28/24.
                </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, to protest, or to answer a complaint in any of the above proceedings must file in accordance with Rules 211, 214, or 206 of the Commission's Regulations (18 CFR 385.211, 385.214, or 385.206) 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>
                <P>
                    The Commission's Office of Public Participation (OPP) supports meaningful public engagement and participation in Commission proceedings. OPP can help members of the public, including landowners, environmental justice communities, Tribal members and others, access publicly available information and navigate Commission processes. For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, the public is encouraged to contact OPP at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 7, 2024.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05330 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[EPA-HQ-OECA-2020-0020; FRL-11769-01-OECA]</DEPDOC>
                <SUBJECT>Proposed Information Collection Request; Comment Request; Annual Public Water Systems Compliance Report</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Environmental Protection Agency is planning to submit an information collection request (ICR), “Annual Public Water System Compliance Report” (EPA ICR No. 1812.08, OMB Control No. 2020-0020) to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act. Before doing so, the EPA is soliciting public comments on specific aspects of the proposed information collection as described below. This is a proposed extension of the ICR, which is currently approved through November 30, 2024. 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>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before May 13, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit your comments, referencing Docket ID No. EPA-HQ-OECA-2020-0020 online using 
                        <E T="03">www.regulations.gov</E>
                         (our preferred method), by email to 
                        <E T="03">docket.oeca@epa.gov,</E>
                         or by mail to: EPA Docket Center, Environmental Protection Agency, Mail Code 28221T, 1200 Pennsylvania Ave. NW, Washington, DC 20460. The EPA's policy is that all comments received will be included in the public docket without change, including any personal information provided, unless the comment includes profanity, threats, information claimed to be Confidential Business Information or other information whose disclosure is restricted by statute.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Raquel Taveras, Monitoring, Assistance and Media Programs Division, Office of Compliance, MC-2227A, Environmental Protection Agency, 1200 Pennsylvania Ave. NW, Washington, DC 20460; telephone number: (202) 564-9651; email address: 
                        <E T="03">taveras.raquel@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This is a proposed extension of the ICR, which is currently approved through November 30, 2024. 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>
                    This notice allows 60 days for public comments. Supporting documents, which explain in detail the information that the EPA will be collecting, are available in the public docket for this ICR. The docket can be viewed online at 
                    <E T="03">www.regulations.gov</E>
                     or in person at the EPA Docket Center, WJC West, Room 3334, 1301 Constitution Ave. NW, Washington, DC. The telephone number for the Docket Center is 202-566-1744. For additional information about EPA's public docket, visit 
                    <E T="03">http://www.epa.gov/dockets.</E>
                </P>
                <P>
                    Pursuant to section 3506(c)(2)(A) of the Paper Reduction Act, the EPA is soliciting comments and information to enable it to: (i) 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; (ii) 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; (iii) enhance the quality, utility, and clarity of the information to be collected; and (iv) minimize the burden of the collection of information on those who are to respond, including through the use of appropriate forms of information technology. The EPA will consider the comments received and amend the ICR as appropriate. The final ICR package will then be submitted to OMB for review and approval. At that time, the EPA will issue another 
                    <E T="04">Federal Register</E>
                     notice to announce the submission of the ICR to OMB and the opportunity to submit additional comments to OMB.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Section 1414(c)(3)(A) of the Safe Drinking Water Act (SDWA) provides that each state (a term that includes states, commonwealths, tribes and territories) that has primary enforcement authority under the SDWA shall prepare, make readily available to 
                    <PRTPAGE P="18408"/>
                    the public, and submit to the Administrator of EPA, an annual report of violations of national primary drinking water regulations in the state. These Annual State Public Water System Compliance Reports are to include violations of maximum contaminant levels, treatment requirements, variances and exemptions, and monitoring requirements determined to be significant by the Administrator after consultation with the states. To minimize a state's burden in preparing its annual statutorily required report, the EPA issued guidance that explains what section 1414(c)(3)(A) requires and provides model language and reporting templates. The EPA also annually makes available to the states a computer query that generates for each state (from information states are already separately required to submit to EPA's national database on a quarterly basis) the required violations information in a table consistent with the reporting template in the EPA's guidance.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     None.
                </P>
                <P>
                    <E T="03">Respondents/affected entities:</E>
                     Entities that are potentially affected by this action are states that have primacy enforcement authority and meet the definition of “state” under the SDWA.
                </P>
                <P>
                    <E T="03">Respondent's obligation to respond:</E>
                     Mandatory under section 1414 (c)(3)(A) of SDWA.
                </P>
                <P>
                    <E T="03">Estimated number of respondents:</E>
                     55 (total).
                </P>
                <P>
                    <E T="03">Frequency of response:</E>
                     Annually.
                </P>
                <P>
                    <E T="03">Total estimated burden:</E>
                     4,400 hours (per year). Burden is defined at 5 CFR 1320.03(b).
                </P>
                <P>
                    <E T="03">Total estimated cost:</E>
                     $730,000 (per year), includes $0 annualized capital or operation &amp; maintenance costs.
                </P>
                <P>
                    <E T="03">Changes in Estimates:</E>
                     There is no change in burden from the most recently approved ICR as currently identified in the OMB Inventory of Approved Burdens. This is due to two considerations. First, the regulations have not changed over the past three years and are not anticipated to change over the next three years. Second, the growth rate for this industry is very low or non-existent, so there is no significant change in the overall burden. Since there are no changes in the regulatory requirements and there is no significant industry growth, there are also no changes in the capital/startup or operation and maintenance (O&amp;M) costs. There is a slight increase in costs, which is wholly due to the use of updated labor rates. This ICR uses labor rates from the most recent Bureau of Labor Statistics report (December 2023) to calculate respondent burden costs.
                </P>
                <SIG>
                    <NAME>Loren Denton,</NAME>
                    <TITLE>Director, Monitoring Assistance and Media Programs Division, Office of Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05285 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[EPA-HQ-OGC-2024-0112; FRL-11804-01-OGC]</DEPDOC>
                <SUBJECT>Proposed Settlement Agreement, Petition for Writ of Mandamus</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed settlement agreement; request for public comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Notice is given of a proposed settlement agreement to address a petition for writ of mandamus filed by the Ecology Center, the Center for Environmental Health, United Parents Against Lead &amp; Other Environmental Hazards, and the Sierra Club (collectively, “Petitioners”) in the United States Court of Appeals for the Ninth Circuit: 
                        <E T="03">Ecology Center, et al.</E>
                         v. 
                        <E T="03">U.S. EPA,</E>
                         No. 23-70158 (9th Cir.). Petitioners filed a petition for writ of mandamus on August 22, 2023, requesting that the Ninth Circuit direct the Environmental Protection Agency (EPA) to “conclude a rulemaking under [TSCA] regulating lead wheel weights within six months.” The mandamus petition alleges that EPA's 14-year delay violated the APA's requirement that a Federal agency “conclude a matter presented to it . . . within a reasonable time,” and that the court has the authority to “compel agency action unlawfully withheld or unreasonably delayed.” EPA is providing notice of this proposed settlement agreement, which would resolve all claims in the case by establishing deadlines for EPA to take final action.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments on the proposed settlement agreement must be received by April 12, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit your comments, identified by Docket ID No. EPA-HQ-OGC-2024-0112, online at
                        <E T="03"> https://www.regulations.gov</E>
                         (EPA's preferred method). Follow the online instructions for submitting comments.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the Docket ID number for this action. 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 “Additional Information about Commenting on the Proposed Settlement Agreement” heading under the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Alyssa Gsell, Pesticides and Toxic Substances Law Office, Office of General Counsel, U.S. Environmental Protection Agency; telephone (202) 564-7413; email address 
                        <E T="03">Gsell.Alyssa@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Obtaining a Copy of the Proposed Settlement Agreement</HD>
                <P>The official public docket for this action (Docket ID No. EPA-HQ-OGC-2024-0112) contains a copy of the proposed settlement agreement. The official public docket is available for public viewing at the Office of Environmental Information (OEI) Docket in the EPA Docket Center, EPA West, Room 3334, 1301 Constitution Ave. NW, Washington, DC. The EPA Docket Center Public Reading Room is open from 8:30 a.m. to 4:30 p.m., Monday through Friday, excluding legal holidays. The telephone number for the Public Reading Room is (202) 566-1744 and the telephone number for the OEI Docket is (202) 566-1752.</P>
                <P>
                    The electronic version of the public docket for this action contains a copy of the proposed settlement agreement and is available through 
                    <E T="03">https://www.regulations.gov.</E>
                     You may use 
                    <E T="03">https://www.regulations.gov</E>
                     to submit or view public comments, access the index listing of the contents of the official public docket, and access those documents in the public docket that are available electronically. Once in the system, key in the appropriate docket identification number then select “search.”
                </P>
                <HD SOURCE="HD1">II. Additional Information About the Proposed Settlement Agreement</HD>
                <P>In 2009, Petitioners petitioned EPA under the Toxic Substances Control Act (“TSCA”) section 21, requesting that EPA regulate lead wheel weights. EPA granted the 2009 Petition but did not issue either an Advanced Notice of Proposed Rulemaking or a Proposed Rule.</P>
                <P>
                    On August 22, 2023, Petitioners filed a petition for writ of mandamus requesting that the Ninth Circuit direct EPA to “conclude a rulemaking under [TSCA] regulating lead wheel weights within six months.” The mandamus petition alleged that EPA's 14-year delay violated the APA's requirement that a 
                    <PRTPAGE P="18409"/>
                    Federal agency “conclude a matter presented to it . . . within a reasonable time,” 5 U.S.C. 555(b), and that the court had authority to “compel agency action unlawfully withheld or unreasonably delayed.” 
                    <E T="03">Id.</E>
                     sec. 706.
                </P>
                <P>In accordance with the EPA's “Consent Decrees and Settlement Agreements to Resolve Environmental Claims Against the Agency” (March 18, 2022), for a period of thirty (30) days following the date of publication of this document, the Agency will accept written comments relating to a proposed settlement agreement for these claims. EPA or the Department of Justice may withdraw or withhold consent to the proposed settlement agreement if the comments disclose facts or considerations that indicate that such consent is inappropriate, improper, or inadequate.</P>
                <HD SOURCE="HD1">III. Additional Information About Commenting on the Proposed Settlement Agreement</HD>
                <P>
                    Submit your comments, identified by Docket ID No. EPA-HQ-OGC-2024-0112, via 
                    <E T="03">https://www.regulations.gov.</E>
                     Once submitted, comments cannot be edited or removed from this docket. 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 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. 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 additional information about submitting information identified as CBI, please contact the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this document. Note that written comments containing CBI and submitted by mail may be delayed and deliveries or couriers will be received by scheduled appointment only.
                </P>
                <P>If you submit an electronic comment, EPA recommends that you include your name, mailing address, and an email address or other contact information in the body of your comment. This ensures that you can be identified as the submitter of the comment and allows EPA to contact you in case EPA cannot read your comment due to technical difficulties or needs further information on the substance of your comment. Any identifying or contact information provided in the body of a comment will be included as part of the comment that is placed in the official public docket and made available in EPA's electronic public docket. If EPA cannot read your comment due to technical difficulties and cannot contact you for clarification, EPA may not be able to consider your comment.</P>
                <P>
                    Use of the 
                    <E T="03">https://www.regulations.gov</E>
                     website to submit comments to EPA electronically is EPA's preferred method for receiving comments. The electronic public docket system is an “anonymous access” system, which means EPA will not know your identity, email address, or other contact information unless you provide it in the body of your comment.
                </P>
                <P>Please ensure that your comments are submitted within the specified comment period. Comments received after the close of the comment period will be marked “late.” EPA is not required to consider these late comments.</P>
                <SIG>
                    <NAME>Randolph L. Hill,</NAME>
                    <TITLE>Associate General Counsel.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05287 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <DEPDOC>[FR ID 207973]</DEPDOC>
                <SUBJECT>Open Commission Meeting Thursday, March 14, 2024</SUBJECT>
                <DATE>March 7, 2024.</DATE>
                <P>The Federal Communications Commission will hold an Open Meeting on the subjects listed below on Thursday, March 14, 2024, which is scheduled to commence at 10:30 a.m. in the Commission Meeting Room of the Federal Communications Commission, 45 L Street NE, Washington, DC.</P>
                <P>
                    While attendance at the Open Meeting is available to the public, the FCC headquarters building is not open access and all guests must check in with and be screened by FCC security at the main entrance on L Street. Attendees at the Open Meeting will not be required to have an appointment but must otherwise comply with protocols outlined at: 
                    <E T="03">www.fcc.gov/visit.</E>
                     Open Meetings are streamed live at: 
                    <E T="03">www.fcc.gov/live</E>
                     and on the FCC's YouTube channel.
                </P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="xs36,r50,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Item No.</CHED>
                        <CHED H="1">Bureau</CHED>
                        <CHED H="1">Subject</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">1</ENT>
                        <ENT>Public Safety &amp; Homeland Security</ENT>
                        <ENT>
                            <E T="03">Title:</E>
                             Cybersecurity Labeling for Internet of Things (PS Docket No. 23-239).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>
                            <E T="03">Summary:</E>
                             The Commission will consider a Report and Order to create a voluntary cybersecurity labeling program for wireless consumer Internet of Things (IoT) products, which would help consumers make informed purchasing decisions, differentiate trustworthy products in the marketplace, and create incentives for manufacturers to meet higher cybersecurity standards.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2</ENT>
                        <ENT>Wireline Competition</ENT>
                        <ENT>
                            <E T="03">Title:</E>
                             Inquiry Concerning Deployment of Advanced Telecommunications Capability to All Americans in a Reasonable and Timely Fashion (GN Docket No. 22-270).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>
                            <E T="03">Summary:</E>
                             The Commission will consider the draft 2024 Section 706 Report, which, if adopted, would fulfill the Commission's statutory responsibility under section 706 of the Telecommunications Act of 1996 and raise the fixed speed benchmark for advanced telecommunications capability to 100/20 Mbps.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3</ENT>
                        <ENT>Wireless Telecommunications and Space</ENT>
                        <ENT>
                            <E T="03">Title:</E>
                             Single Network Future: Supplemental Coverage from Space (GN Docket No. 23-65); Space Innovation (IB Docket No. 22-271).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>
                            <E T="03">Summary:</E>
                             The Commission will consider a Report and Order and Further Notice of Proposed Rulemaking that would advance the Commission's vision for a single network future in which satellite and terrestrial networks work seamlessly together to provide coverage for consumer handsets that neither network can achieve on its own.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4</ENT>
                        <ENT>Media</ENT>
                        <ENT>
                            <E T="03">Title:</E>
                             All-In Cable and Satellite TV Pricing (MB Docket No. 23-203).
                        </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="18410"/>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>
                            <E T="03">Summary:</E>
                             The Commission will consider a Report and Order to require cable and satellite TV providers to specify the “all-in” price for video programming services in promotional materials and on subscribers' bills in order to allow consumers to make informed choices.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">5</ENT>
                        <ENT>Consumer &amp; Governmental Affairs</ENT>
                        <ENT>
                            <E T="03">Title:</E>
                             Wireless Emergency Alerts (PS Docket No. 15-91); Amendments to Part 11 of the Commission's Rules Regarding the Emergency Alert System (PS Docket No. 15-94).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>
                            <E T="03">Summary:</E>
                             The Commission will consider a Notice of Proposed Rulemaking that would propose to facilitate the more efficient and widespread dissemination of alerts and coordinated responses to incidents involving missing and endangered persons, an issue that is particularly prevalent in Tribal communities.
                        </ENT>
                    </ROW>
                </GPOTABLE>
                <STARS/>
                <P>
                    The meeting will be webcast at: 
                    <E T="03">www.fcc.gov/live.</E>
                     Open captioning will be provided as well as a text only version on the FCC website. Other reasonable accommodations for people with disabilities are available upon request. In your request, include a description of the accommodation you will need and a way we can contact you if we need more information. Last minute requests will be accepted but may be impossible to fill. Send an email to: 
                    <E T="03">fcc504@fcc.gov</E>
                     or call the Consumer &amp; Governmental Affairs Bureau at 202-418-0530.
                </P>
                <P>
                    <E T="03">Press Access</E>
                    —Members of the news media are welcome to attend the meeting and will be provided reserved seating on a first-come, first-served basis. Following the meeting, the Chairwoman may hold a news conference in which she will take questions from credentialed members of the press in attendance. Also, senior policy and legal staff will be made available to the press in attendance for questions related to the items on the meeting agenda. Commissioners may also choose to hold press conferences. Press may also direct questions to the Office of Media Relations (OMR): 
                    <E T="03">MediaRelations@fcc.gov.</E>
                     Questions about credentialing should be directed to OMR.
                </P>
                <P>
                    Additional information concerning this meeting may be obtained from the Office of Media Relations, (202) 418-0500. Audio/Video coverage of the meeting will be broadcast live with open captioning over the internet from the FCC Live web page at 
                    <E T="03">www.fcc.gov/live.</E>
                </P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Katura Jackson,</NAME>
                    <TITLE>Federal Register Liaison Officer, Office of the Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05313 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL MARITIME COMMISSION</AGENCY>
                <SUBJECT>Notice of Agreements Filed</SUBJECT>
                <P>
                    The Commission hereby gives notice of filing of the following agreements under the Shipping Act of 1984. Interested parties may submit comments, relevant information, or documents regarding the agreements to the Secretary by email at 
                    <E T="03">Secretary@fmc.gov,</E>
                     or by mail, Federal Maritime Commission, 800 North Capitol Street, Washington, DC 20573. Comments will be most helpful to the Commission if received within 12 days of the date this notice appears in the 
                    <E T="04">Federal Register</E>
                    , and the Commission requests that comments be submitted within 7 days on agreements that request expedited review. Copies of agreements are available through the Commission's website (
                    <E T="03">www.fmc.gov</E>
                    ) or by contacting the Office of Agreements at (202)-523-5793 or 
                    <E T="03">tradeanalysis@fmc.gov.</E>
                </P>
                <P>
                    <E T="03">Agreement No.:</E>
                     012307-008.
                </P>
                <P>
                    <E T="03">Agreement Name:</E>
                     Maersk/APL Slot Exchange Agreement.
                </P>
                <P>
                    <E T="03">Parties:</E>
                     American President Lines, LLC; Maersk A/S.
                </P>
                <P>
                    <E T="03">Filing Party:</E>
                     Wayne Rohde; Cozen O'Connor.
                </P>
                <P>
                    <E T="03">Synopsis:</E>
                     The amendment removes Maersk A/S as a party and replaces it with Maersk Line, Limited.
                </P>
                <P>
                    <E T="03">Proposed Effective Date:</E>
                     04/18/2024.
                </P>
                <P>
                    <E T="03">Location: https://www2.fmc.gov/FMC.Agreements.Web/Public/AgreementHistory/176.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 8, 2024.</DATED>
                    <NAME>Carl Savoy,</NAME>
                    <TITLE>Federal Register Alternate Liaison Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05344 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6730-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Change in Bank Control Notices; Acquisitions of Shares of a Bank or Bank Holding Company</SUBJECT>
                <P>The notificants listed below have applied under the Change in Bank Control Act (Act) (12 U.S.C. 1817(j)) and § 225.41 of the Board's Regulation Y (12 CFR 225.41) to acquire shares of a bank or bank holding company. The factors that are considered in acting on the applications are set forth in paragraph 7 of the Act (12 U.S.C. 1817(j)(7)).</P>
                <P>
                    The public portions of the applications listed below, as well as other related filings required by the Board, if any, are available for immediate inspection at the Federal Reserve Bank(s) indicated below and at the offices of the Board of Governors. This information may also be obtained on an expedited basis, upon request, by contacting the appropriate Federal Reserve Bank and from the Board's Freedom of Information Office at 
                    <E T="03">https://www.federalreserve.gov/foia/request.htm.</E>
                     Interested persons may express their views in writing on the standards enumerated in paragraph 7 of the Act.
                </P>
                <P>Comments regarding each of these applications must be received at the Reserve Bank indicated or the offices of the Board of Governors, Ann E. Misback, Secretary of the Board, 20th Street and Constitution Avenue NW, Washington, DC 20551-0001, not later than March 27, 2024.</P>
                <P>
                    <E T="03">A. Federal Reserve Bank of Kansas City</E>
                     (Jeffrey Imgarten, Assistant Vice President) 1 Memorial Drive, Kansas City, Missouri 64198-0001. Comments can also be sent electronically to 
                    <E T="03">KCApplicationComments@kc.frb.org:</E>
                </P>
                <P>
                    1. 
                    <E T="03">Ashlie D. Hadden, Kearney, Nebraska;</E>
                     to join the Stull Family Control Group, a group acting in concert, to acquire voting shares of Farmers State Bancshares, Inc., and thereby indirectly acquire voting shares of Nebraska Bank, both of Dodge, Nebraska.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System.</P>
                    <NAME>Michele Taylor Fennell,</NAME>
                    <TITLE>Deputy Associate Secretary of the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05235 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18411"/>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Formations of, Acquisitions by, and Mergers of Bank Holding Companies</SUBJECT>
                <P>
                    The companies listed in this notice have applied to the Board for approval, pursuant to the Bank Holding Company Act of 1956 (12 U.S.C. 1841 
                    <E T="03">et seq.</E>
                    ) (BHC Act), Regulation Y (12 CFR part 225), and all other applicable statutes and regulations to become a bank holding company and/or to acquire the assets or the ownership of, control of, or the power to vote shares of a bank or bank holding company and all of the banks and nonbanking companies owned by the bank holding company, including the companies listed below.
                </P>
                <P>
                    The public portions of the applications listed below, as well as other related filings required by the Board, if any, are available for immediate inspection at the Federal Reserve Bank(s) indicated below and at the offices of the Board of Governors. This information may also be obtained on an expedited basis, upon request, by contacting the appropriate Federal Reserve Bank and from the Board's Freedom of Information Office at 
                    <E T="03">https://www.federalreserve.gov/foia/request.htm.</E>
                     Interested persons may express their views in writing on the standards enumerated in the BHC Act (12 U.S.C. 1842(c)).
                </P>
                <P>Comments regarding each of these applications must be received at the Reserve Bank indicated or the offices of the Board of Governors, Ann E. Misback, Secretary of the Board, 20th Street and Constitution Avenue NW, Washington, DC 20551-0001, not later than April 12, 2024.</P>
                <P>
                    <E T="03">A. Federal Reserve Bank of Chicago</E>
                     (Colette A. Fried, Assistant Vice President) 230 South LaSalle Street, Chicago, Illinois 60690-1414. Comments can also be sent electronically to 
                    <E T="03">Comments.applications@chi.frb.org:</E>
                </P>
                <P>
                    1. 
                    <E T="03">Billfloat, Inc., dba SmartBiz Loans, San Francisco, California;</E>
                     to become a bank holding company by acquiring United Community Bancshares, Inc., and thereby indirectly acquiring Centrust Bank, N.A., both of Northbrook, Illinois.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System.</P>
                    <NAME>Michele Taylor Fennell,</NAME>
                    <TITLE>Deputy Associate Secretary of the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05323 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
                <DEPDOC>[Document Identifiers: CMS-10279, CMS-10316 and CMS-10008]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services, 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 Medicare &amp; Medicaid Services (CMS) is announcing an opportunity for the public to comment on CMS' intention to collect information from the public. 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 or reinstatement of an existing collection of information) and to allow 60 days for public comment on the proposed action. Interested persons are invited to send comments regarding our burden estimates or any other aspect of this collection of information, including the necessity and utility of the proposed information collection for the proper performance of the agency's functions, the accuracy of the estimated burden, ways to enhance the quality, utility, and clarity of the information to be collected, and the use of automated collection techniques or other forms of information technology to minimize the information collection burden.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by May 13, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>When commenting, please reference the document identifier or OMB control number. To be assured consideration, comments and recommendations must be submitted in any one of the following ways:</P>
                    <P>
                        1. 
                        <E T="03">Electronically.</E>
                         You may send your comments electronically to 
                        <E T="03">http://www.regulations.gov.</E>
                         Follow the instructions for “Comment or Submission” or “More Search Options” to find the information collection document(s) that are accepting comments.
                    </P>
                    <P>
                        2. 
                        <E T="03">By regular mail.</E>
                         You may mail written comments to the following address: CMS, Office of Strategic Operations and Regulatory Affairs, Division of Regulations Development, Attention: Document Identifier/OMB Control Number: __, Room C4-26-05, 7500 Security Boulevard, Baltimore, Maryland 21244-1850.
                    </P>
                    <P>
                        To obtain copies of a supporting statement and any related forms for the proposed collection(s) summarized in this notice, please access the CMS PRA website by copying and pasting the following web address into your web browser: 
                        <E T="03">https://www.cms.gov/Regulations-and-Guidance/Legislation/PaperworkReductionActof1995/PRA-Listing.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>William N. Parham at (410) 786-4669.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Contents</HD>
                <P>
                    This notice sets out a summary of the use and burden associated with the following information collections. More detailed information can be found in each collection's supporting statement and associated materials (see 
                    <E T="02">ADDRESSES</E>
                    ).
                </P>
                <FP SOURCE="FP-2">CMS-10279 Ambulatory Surgical Center Conditions for Coverage </FP>
                <FP SOURCE="FP-2">CMS-10316 Implementation of the Medicare Prescription Drug Plan (PDP) and Medicare Advantage (MA) Plan Disenrollment Reasons Survey</FP>
                <FP SOURCE="FP-2">CMS-10008 Transitional Pass-through payments related to Drugs, Biologicals, and Radiopharmaceuticals to determine eligibility under the Outpatient Prospective Payment System</FP>
                <P>
                    Under the PRA (44 U.S.C. 3501-3520), federal agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. The term “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 requires federal agencies to publish a 60-day notice in the 
                    <E T="04">Federal Register</E>
                     concerning each proposed collection of information, including each proposed extension or reinstatement of an existing collection of information, before submitting the collection to OMB for approval. To comply with this requirement, CMS is publishing this notice.
                </P>
                <HD SOURCE="HD1">Information Collection</HD>
                <P>
                    1. 
                    <E T="03">Type of Information Collection Request:</E>
                     Reinstatement with changes to a previously approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     Ambulatory Surgical Center Conditions for Coverage; 
                    <E T="03">Use:</E>
                     The purpose of this package is to request from the Office of Management and Budget (OMB) the approval to reinstate, with changes, the collection of 
                    <PRTPAGE P="18412"/>
                    information. The Cfc for ASCs are regulation based on criteria described and codified at § 42 CFR 416. The Cfc establish standards designed to ensure that each ASC has properly trained staff to provide the appropriate type and level of care for the environment of ASC patients.
                </P>
                <P>To determine ASC compliance with CMS standards, CMS, via the Secretary, authorizes States, through contracts, to survey ASC facilities. For Medicare purposes, certification is based on the State survey agency's recording of an ASC provider's compliance or non-compliance with the health and safety Cfc as published and codified in 42 CFR 416.40 to 485.54. The information collections aid surveyors as they assess ASC compliance or non-compliance.</P>
                <P>
                    The previous iteration of this information collection request had a burden of 262,946 annual hours at an annual cost of $28,144,370. For this requested reinstatement, with changes, the adjusted annual hourly burden is 97,527 hours at a cost of $11,089,427. The reasons for this change, is the previous iteration of this IC assumed the development associated with IC-1 and IC-2 occurred frequently. We have revised this as development of drafts only occur on a one-time basis. 
                    <E T="03">Form Number:</E>
                     CMS-10279 (OMB control number: 0938-1071); 
                    <E T="03">Frequency:</E>
                     Annual; 
                    <E T="03">Affected Public:</E>
                     Business or other for-profit and Not-for-profit institutions; 
                    <E T="03">Number of Respondents:</E>
                     6,257; 
                    <E T="03">Total Annual Responses:</E>
                     6,257; 
                    <E T="03">Total Annual Hours:</E>
                     97,527. (For policy questions regarding this collection contact Claudia Molinar at 410-786-8445.)
                </P>
                <P>
                    2. 
                    <E T="03">Type of Information Collection Request:</E>
                     Revision of a currently approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     Implementation of the Medicare Prescription Drug Plan (PDP) and Medicare Advantage (MA) Plan Disenrollment Reasons Survey; 
                    <E T="03">Use:</E>
                     Medicare Prescription Drug, Improvement, and Modernization Act of 2003 (MMA) provides a requirement to collect and report performance data for Part D prescription drug plans. Specifically, the MMA under Sec. 1860D-4 (Information to Facilitate Enrollment) requires CMS to conduct consumer satisfaction surveys regarding the PDP and MA contracts pursuant to section 1860D-4(d). Plan disenrollment is generally believed to be a broad indicator of beneficiary dissatisfaction with some aspect of plan services, such as access to care, customer service, cost of the plan, services, benefits provided, or quality of care.
                </P>
                <P>This data collection complements the enrollee beneficiary experience data collected through the Medicare Consumer Assessment of Healthcare Providers and Systems (Medicare CAHPS) survey by providing information on the reasons for disenrollment from a Medicare Advantage (with or without prescription drug coverage) or Prescription Drug Plan.</P>
                <P>
                    The Disenrollment Survey results are an important source of information used by CMS to monitor contract performance and to identify potential problems (
                    <E T="03">e.g.,</E>
                     plans providing incorrect information to beneficiaries or creating access problems). CMS uses the results to monitor the quality of service that Medicare beneficiaries get from contracted plans and their providers and to understand beneficiaries' expectations relative to provided benefits and services for MA and PDPs. CMS uses information from the Disenrollment Survey to support quality improvement efforts of individual contracts. 
                    <E T="03">Form Number:</E>
                     CMS-10316 (OMB control number: 0938-1113); 
                    <E T="03">Frequency:</E>
                     Yearly; 
                    <E T="03">Affected Public:</E>
                     Individuals and Households; 
                    <E T="03">Number of Respondents:</E>
                     36,050; 
                    <E T="03">Total Annual Responses:</E>
                     36,050; 
                    <E T="03">Total Annual Hours:</E>
                     6,730. (For policy questions regarding this collection contact Beth Simon at 415-744-3780.)
                </P>
                <P>
                    3. 
                    <E T="03">Type of Information Collection Request:</E>
                     Extension currently approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     Transitional Pass through payments related to Drugs, Biologicals, and Radiopharmaceuticals to determine eligibility under the Outpatient Prospective Payment System; 
                    <E T="03">Use:</E>
                     Section 1833(t)(6)(D)(i) of the Act sets the payment rate for pass-through eligible drugs and biologicals (assuming that no pro rata reduction in pass-through payment is necessary) as the amount determined under section 1842(o) of the Act. Section 303(c) of Public Law 108-173 amended Title XVIII of the Act by adding new section 1847A. This new section establishes the use of the average sales price (ASP) methodology for payment for drugs and biologicals described in section 1842(o)(1)(C) of the Act furnished on or after January 1, 2005. Therefore, as we stated in the November 15, 2004 
                    <E T="04">Federal Register</E>
                     (69 FR 65776), in CY 2005, we will pay under the OPPS for drugs, biologicals and radiopharmaceuticals with pass-through status consistent with the provisions of section 1842(o) of the Act as amended by Public Law 108-173 at a rate that is equivalent to the payment these drugs and biologicals will receive in the physician office setting, and established in accordance with the methodology described in the CY 2005 Physician Fee Schedule final rule.
                </P>
                <P>
                    Interested parties such as hospitals, pharmaceutical companies, and physicians will apply for transitional pass-through payment for drugs, biologicals, and radiopharmaceuticals used with services covered under the hospital OPPS. After we receive all requested information, we will evaluate the information to determine if the criteria for making a transitional pass-through payment are met and if an interim healthcare common procedure coding system (HCPCS) code for a new drug, biological, or radiopharmaceutical is necessary. We will advise the applicant of our decision, and update the hospital OPPS during its next scheduled quarterly update to reflect any newly approved drug, biological, or radiopharmaceutical. Based on experience gained in processing transitional pass-through and new technology applications, we have reworded some of the statements for clarity and have more clearly requested information in a format that will allow us to determine if the drug, biological, or radiopharmaceutical meets the cost significance test, as well as to estimate the associated pass-through payment amount. In addition, we have also eliminated the requirement for applicants to obtain a national Level II HCPCS code prior to seeking transitional pass-through payment eligibility, or provide us with a copy of their application for a national HCPCS code, as we had originally required in the April 7, 2000 final rule. 
                    <E T="03">Form Number:</E>
                     CMS-10008 (OMB control number: 0938-0802); 
                    <E T="03">Frequency:</E>
                     Once; 
                    <E T="03">Affected Public:</E>
                     Private Sector, Business or other for-profit and Not-for-profit institutions; 
                    <E T="03">Number of Respondents:</E>
                     35; 
                    <E T="03">Total Annual Responses:</E>
                     35; 
                    <E T="03">Total Annual Hours:</E>
                     560. (For policy questions regarding this collection contact Andrew Wang at 410-786-8233.)
                </P>
                <SIG>
                    <NAME>William N. Parham, III,</NAME>
                    <TITLE>Director, Division of Information Collections and Regulatory Impacts, Office of Strategic Operations and Regulatory Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05291 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4120-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18413"/>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
                <DEPDOC>[Document Identifiers: CMS-10454]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services, 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 Medicare &amp; Medicaid Services (CMS) is announcing an opportunity for the public to comment on CMS' intention to collect information from the public. 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 or reinstatement of an existing collection of information) and to allow 60 days for public comment on the proposed action. Interested persons are invited to send comments regarding our burden estimates or any other aspect of this collection of information, including the necessity and utility of the proposed information collection for the proper performance of the agency's functions, the accuracy of the estimated burden, ways to enhance the quality, utility, and clarity of the information to be collected, and the use of automated collection techniques or other forms of information technology to minimize the information collection burden.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by May 13, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>When commenting, please reference the document identifier or OMB control number. To be assured consideration, comments and recommendations must be submitted in any one of the following ways:</P>
                    <P>
                        1. 
                        <E T="03">Electronically.</E>
                         You may send your comments electronically to 
                        <E T="03">http://www.regulations.gov.</E>
                         Follow the instructions for “Comment or Submission” or “More Search Options” to find the information collection document(s) that are accepting comments.
                    </P>
                    <P>
                        2. 
                        <E T="03">By regular mail.</E>
                         You may mail written comments to the following address: CMS, Office of Strategic Operations and Regulatory Affairs, Division of Regulations Development, Attention: Document Identifier/OMB Control Number: ___, Room C4-26-05, 7500 Security Boulevard, Baltimore, Maryland 21244-1850.
                    </P>
                    <P>
                        To obtain copies of a supporting statement and any related forms for the proposed collection(s) summarized in this notice, please access the CMS PRA website by copying and pasting the following web address into your web browser: 
                        <E T="03">https://www.cms.gov/Regulations-and-Guidance/Legislation/PaperworkReductionActof1995/PRA-Listing.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>William N. Parham at (410) 786-4669.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Contents</HD>
                <P>
                    This notice sets out a summary of the use and burden associated with the following information collections. More detailed information can be found in each collection's supporting statement and associated materials (see 
                    <E T="02">ADDRESSES</E>
                    ).
                </P>
                <HD SOURCE="HD2">CMS-10454 Disclosure of State Rating Requirements</HD>
                <P>
                    Under the PRA (44 U.S.C. 3501-3520), federal agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. The term “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 requires federal agencies to publish a 60-day notice in the 
                    <E T="04">Federal Register</E>
                     concerning each proposed collection of information, including each proposed extension or reinstatement of an existing collection of information, before submitting the collection to OMB for approval. To comply with this requirement, CMS is publishing this notice.
                </P>
                <HD SOURCE="HD1">Information Collection</HD>
                <P>
                    1. 
                    <E T="03">Type of Information Collection Request:</E>
                     Extension; 
                    <E T="03">Title of Information Collection:</E>
                     Disclosure of State Rating Requirements; 
                    <E T="03">Use:</E>
                     The final rule “Patient Protection and Affordable Care Act; Health Insurance Market Rules; Rate Review” implements sections 2701, 2702, and 2703 of the Public Health Service Act (PHS Act), as added and amended by the Affordable Care Act, and sections 1302(e) and 1312(c) of the Affordable Care Act. The rule directs that states submit to CMS certain information about state rating and risk pooling requirements for their individual, small group, and large group markets, as applicable. Specifically, states will inform CMS of age rating ratios that are narrower than 3:1 for adults; tobacco use rating ratios that are narrower than 1.5:1; a state-established uniform age curve; geographic rating areas; whether premiums in the small and large group market are required to be based on average enrollee amounts (also known as composite premiums); and, in states that do not permit any rating variation based on age or tobacco use, uniform family tier structures and corresponding multipliers. In addition, states that elect to merge their individual and small group market risk pools into a combined pool will notify CMS of such election. This information will allow CMS to determine whether state-specific rules apply or Federal default rules apply. It will also support the accuracy of the federal risk adjustment methodology. 
                    <E T="03">Form Number:</E>
                     CMS-10454 (OMB control number 0938-1258); 
                    <E T="03">Frequency:</E>
                     Occasionally; 
                    <E T="03">Affected Public:</E>
                     State, Local, or Tribal Governments; 
                    <E T="03">Number of Respondents:</E>
                     3; 
                    <E T="03">Total Annual Responses:</E>
                     3; 
                    <E T="03">Total Annual Hours:</E>
                     7.3. For policy questions regarding this collection contact Russell Tipps at 301-869-3502.
                </P>
                <SIG>
                    <NAME>William N. Parham, III,</NAME>
                    <TITLE>Director, Division of Information Collections and Regulatory Impacts, Office of Strategic Operations and Regulatory Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05332 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4120-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Administration for Community Living</SUBAGY>
                <SUBJECT>Agency Information Collection Activities; Submission for OMB Review; Public Comment Request; National Survey of Older Americans Act Participants [OMB 0985-0023]</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Administration for Community Living, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Administration for Community Living is announcing that the proposed collection of information listed above has been submitted to the Office of Management and Budget (OMB) for review and clearance as required under the Paperwork Reduction Act of 1995. This 30-day notice collects comments on the information collection requirements related to the proposed revision for the information collection requirements related to the National Survey of Older Americans Act Participants.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on the collection of information must be submitted electronically by 11:59 p.m. (EST) or postmarked by April 12, 2024.</P>
                </DATES>
                <ADD>
                    <PRTPAGE P="18414"/>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit written comments and recommendations for the proposed information collection within 30 days of publication of this notice to 
                        <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                         Find the information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function. By mail to the Office of Information and Regulatory Affairs, OMB, New Executive Office Bldg., 725 17th St. NW, Rm. 10235, Washington, DC 20503, Attn: OMB Desk Officer for ACL.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kristen Robinson, Administration for Community Living, Washington, DC 20201, by email at 
                        <E T="03">Kristen.Robinson@acl.hhs.gov,</E>
                         or by telephone at 202-795-7428.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In compliance with the Paperwork Reduction Act (44 U.S.C. 3506), the Administration for Community Living (ACL) has submitted the following proposed collection of information to OMB for review and clearance. The National Survey of Older Americans Act (OAA Section 202(f),) Participants information collection includes consumer assessment surveys for the Congregate and Home-delivered meal nutrition programs; Case Management, Homemaker, and Transportation Services; and the National Family Caregiver Support Program. This survey builds on earlier national pilot studies and surveys, as well as performance measurement tools developed by ACL grantees in the Performance Outcomes Measures Project (POMP). Changes identified as a result of these initiatives were incorporated into the last data collection package that was approved by OMB and are included in this proposed extension of a currently approved collection.</P>
                <P>This information will be used by ACL to track performance outcome measures; support budget requests; comply with the GPRA Modernization Act of 2010 (Pub. L. 111-352) reporting requirements; provide national benchmark information; and inform program development and management initiatives.</P>
                <P>In addition to the proposed extension of a currently approved collection of information, ACL is requesting approval for a one-time module on `Preferences and Needs Related to Community Living' to be added to the currently approved NSOAAP data collection effort. The module will be added to the 2024 collection instrument.</P>
                <P>Most older adults want to remain living in their homes and communities as they age. According to a 2022 National Poll on Healthy Aging conducted by the University of Michigan, 88 percent of older adults reported it was important to them to be able to stay living safely in their homes for as long as possible. Unexpected medical events and declines in health, however, can sometimes make that difficult. The purpose of the one-time module on `Preferences and Needs Related to Community Living' is to better understand how prepared OAA recipients are to remain living in their homes as they age, so that the Aging Network can better tailor their programs and services to meet their clients' needs.</P>
                <P>The results of this information collection will be used by ACL to:</P>
                <P>• Provide refined national benchmarks for use by State agencies and area agencies on aging (AAAs).</P>
                <P>• Provide secondary data for analysis of various Title III program evaluations.</P>
                <P>• Provide performance information for key demographic subgroups which will enable ACL to identify variations in performance and examine the need for additional targeted technical assistance.</P>
                <P>• Provide secondary data for analysis of `Preferences and Needs Related to Community Living' on access to and use of OAA programs and services among older adults that will be shared with states and AAAs to help them better structure their programs and services to help older adults remain safely in their homes and communities as long as possible.</P>
                <P>
                    The data will be used by the Senior official performing the duties of the Administrator and the Assistant Secretary for Aging for the Administration for Community Living, in testimony and presentations; it will be incorporated into the agency's Annual Report; and it will be used by program staff to identify areas that may need attention at the national level. Copies of the survey instruments and data from previous National Surveys of OAA Participants can be found on the Aging, Independence, and Disability (AGID) Program Data Portal at 
                    <E T="03">https://agid.acl.gov/.</E>
                     This IC collects demographic data from grantees receiving programs and services funded by HHS. ACL will adhere to best practices for collection of all demographic information when this information is collected for the programs listed in accordance with OMB guidance.
                </P>
                <P>This includes, but is not limited to, guidance specific to the collection of sexual orientation and gender identity (SOGI) items that align with Executive Order 13985 on Advancing Racial Equity and Support for Underserved Communities Through the Federal Government, Executive Order 14075 on Advancing Equality for Lesbian, Gay, Bisexual, Transgender, Queer, and Intersex Individuals, and Executive Order 13988 on Preventing and Combating Discrimination on the Basis of Gender Identity and Sexual Orientation. Understanding these disparities can and should lead to improved service delivery for ACL's programs and populations served.</P>
                <HD SOURCE="HD1">Comments in Response to the 60-Day Federal Register Notice</HD>
                <P>A 60-day FRN published in the FR on August 2, 2023, at 88 FR 50869. One public comment was received.</P>
                <GPOTABLE COLS="3" OPTS="L2,nj,tp0,i1" CDEF="s50,r100,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Data collection form</CHED>
                        <CHED H="1">Comment</CHED>
                        <CHED H="1">ACL response</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">
                            <E T="03">NSOAAP Demographic Characteristics</E>
                        </ENT>
                        <ENT>The undersigned write to provide support for the Administration's efforts to retain a question assessing sexual orientation and add in a two-step question assessing gender identity amongst respondents to the NSOAAP. Questions measuring SOGI among respondents to the NSOAAP will serve a practical utility for the Administration as it will increase the Administration's ability to assess the needs of LGBTQ older Americans</ENT>
                        <ENT>ACL concurs and plans to maintain the sexual orientation question and two-step gender identity question for the foreseeable future.</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="18415"/>
                <P>
                    <E T="03">Estimated Program Burden:</E>
                </P>
                <P>ACL estimates the annual burden associated with this collection of information as follows:</P>
                <GPOTABLE COLS="5" OPTS="L2,nj,tp0,i1" CDEF="s50,12,12,12,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Respondent/data collection activity</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Responses
                            <LI>per</LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Hours
                            <LI>per</LI>
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">
                            Annual
                            <LI>burden</LI>
                            <LI>hours</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Area Agency on Aging: Respondent selection process</ENT>
                        <ENT>300</ENT>
                        <ENT>1</ENT>
                        <ENT>4.0</ENT>
                        <ENT>1,200</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Service recipients (
                            <E T="03">i.e.,</E>
                             Congregate and Home-Delivered Meal nutrition programs, Case Management, Homemaker, Transportation services) + Rotating Module
                        </ENT>
                        <ENT>4,000</ENT>
                        <ENT>1</ENT>
                        <ENT>0.75</ENT>
                        <ENT>3,000</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">National Family Caregiver Support Program clients + Rotating Module</ENT>
                        <ENT>2,000</ENT>
                        <ENT>1</ENT>
                        <ENT>0.75</ENT>
                        <ENT>1,500</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT>6,300</ENT>
                        <ENT>1</ENT>
                        <ENT>* 0.90</ENT>
                        <ENT>5,700</ENT>
                    </ROW>
                    <TNOTE>* Weighted mean.</TNOTE>
                </GPOTABLE>
                <SIG>
                    <DATED>Dated: March 7, 2024.</DATED>
                    <NAME>Alison Barkoff,</NAME>
                    <TITLE>Principal Deputy Administrator for the Administration for Community Living, performing the delegable duties of the Administrator and the Assistant Secretary for Aging.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05310 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4154-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-2024-N-0668]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Proposed Collection; Comment Request; Proposed Small Dispensers Assessment Under the Drug Supply Chain Security 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 or Agency) 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 and to allow 60 days for public comment in response to the notice. This notice solicits comments on the Proposed Small Dispensers Assessment under the Drug Supply Chain Security Act (DSCSA).
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Either electronic or written comments on the collection of information must be submitted by May 13, 2024.</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 May 13, 2024. 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-2024-N-0668 for “Agency Information Collection Activities; Proposed Collection; Comment Request; Proposed Small Dispensers Assessment under the Drug Supply Chain Security Act (DSCSA).” 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 
                    <PRTPAGE P="18416"/>
                    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>
                        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>
                </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 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">Proposed Small Dispensers Assessment Under the Drug Supply Chain Security Act</HD>
                <HD SOURCE="HD1">OMB Control Number 0910-NEW</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    On November 27, 2013, the DSCSA (Title II of Pub. L. 113-54) was signed into law. The DSCSA outlines steps to achieve interoperable, electronic tracing of products at the package level 
                    <SU>1</SU>
                    <FTREF/>
                     to identify and trace certain prescription drugs as they are distributed in the United States. Section 202 of the DSCSA added the new sections 581 and 582 to the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) (21 U.S.C. 360eee and 360eee-1). Under section 582(g)(3), FDA is required to enter into a contract with a private, independent consulting firm with expertise to conduct a technology and software assessment that looks at the feasibility of dispensers with 25 or fewer full-time employees (FTEs) conducting interoperable, electronic tracing of products at the package level.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         As defined by section 581(11) of the FD&amp;C Act, generally, the term “package” means the smallest individual saleable unit or smallest container of product for distribution by a manufacturer or repackager that is intended by the manufacturer for ultimate sale to the dispenser of such product.
                    </P>
                </FTNT>
                <P>As described in section 582(g)(3)(C), issues to be addressed in the assessment questions are related to the accessibility of the necessary software and hardware to such dispensers; whether the necessary software and hardware is prohibitively expensive to obtain, install, and maintain for such dispensers; and if the necessary hardware and software can be integrated into business practices. Respondents will submit information by answering the assessment questions. Under enhanced drug distribution security requirements in section 582(g)(1), dispensers and other trading partners will be required to, among other requirements, exchange transaction information and transaction statements in a secure, interoperable, electronic manner for each package; implement systems and processes for package level verification, including the standardized numerical identifier; and implement systems and processes to facilitate gathering the information necessary to produce the transaction information and statement for each transaction going back to the manufacturer if FDA or a trading partner requests an investigation in the event of a recall or a suspect or illegitimate product. These enhanced drug distribution security requirements are also referred to as “enhanced product tracing or enhanced verification.”</P>
                <HD SOURCE="HD1">II. Proposed DSCSA Small Dispensers Assessment</HD>
                <HD SOURCE="HD2">A. Eligibility Requirements</HD>
                <P>
                    Assessment participants will include self-identified individuals representing dispensers with a total of 25 or fewer FTEs (small dispenser) and individuals representing small dispensers' third-party entities (
                    <E T="03">e.g.,</E>
                     solution providers, wholesale distributors, consultants).
                </P>
                <HD SOURCE="HD2">B. Potential Issues To Examine and Evaluation Methods</HD>
                <P>
                    The proposed DSCSA Small Dispensers Assessment will look at the feasibility of dispensers with a total of 25 or fewer FTEs of conducting interoperable, electronic tracing of products at the package level. As part of the qualitative data analysis, respondents will submit information by answering specific questions for the assessment. Evaluation methods and analyses are expected to include qualitative analyses (for example, content analysis for responses), and quantitative analyses using descriptive statistics. In cases where quantitative data are collected, descriptive statistics—including percentages and tabulations—will be calculated and presented, along with demographic descriptions of respondents. For example, quantitative analysis could include percentages or tabulations of small dispensers with access to the necessary software and hardware to meet the requirements in section 582(g)(1) of the FD&amp;C Act. We have developed a web page to further assist industry regarding the proposed DSCSA Small Dispensers Assessment, available at 
                    <E T="03">https://www.fda.gov/drugs/drug-supply-chain-security-act-dscsa/drug-supply-chain-security-act-dscsa-assessment-small-dispensers.</E>
                </P>
                <HD SOURCE="HD2">C. Proposed Instructions for Enrollment for the Proposed DSCSA Small Dispensers Assessment</HD>
                <P>
                    After the proposed DSCSA Small Dispensers Assessment is established, volunteers interested in participating will enroll by submitting participant information using a link to be provided on the same web page mentioned above, 
                    <E T="03">https://www.fda.gov/drugs/drug-supply-chain-security-act-dscsa/drug-supply-chain-security-act-dscsa-assessment-small-dispensers.</E>
                     Only one point-of-contact per company should be provided for the enrollment.
                </P>
                <HD SOURCE="HD2">D. Proposed Content of the Enrollment for the Proposed DSCSA Small Dispensers Assessment</HD>
                <P>
                    The following information should be included:
                    <PRTPAGE P="18417"/>
                </P>
                <P>• Contact information (name, email address, phone number, mailing address)</P>
                <P>
                    • Confirm you are a dispenser that has 25 or fewer FTEs or you are an individual representing a small dispensers' third-party entity (
                    <E T="03">e.g.,</E>
                     solution providers, wholesale distributors, consultants)
                </P>
                <P>• Commitment to answer the questions contained in the assessment within 45 days of receiving</P>
                <P>• Applicable state license number</P>
                <HD SOURCE="HD2">E. Participation</HD>
                <P>Assessment participants will include those who have met eligibility requirements and completed enrollment. The assessment is expected to be completed within the proposed duration of 45 days of receiving, and participants will be expected to provide responses to FDA via the designated FDA online tool/platform.</P>
                <HD SOURCE="HD2">F. Proposed Recordkeeping</HD>
                <P>Any records generated by a participant in the assessment should be maintained as an entity would in a normal course of business. FDA recommends that the responses that participants create and submit to FDA for the assessment be maintained for at least 1 year after FDA publishes its final report of the assessment.</P>
                <HD SOURCE="HD2">G. Initiation of FDA's Proposed DSCSA Small Dispensers Assessment</HD>
                <P>FDA does not intend to begin the proposed DSCSA Small Dispensers Assessment or accept enrollment to participate in the assessment until OMB has approved the proposed collection of information described in this notice.</P>
                <P>FDA estimates the burden of this one-time collection of information as follows:</P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12,12,12,12,12">
                    <TTITLE>
                        Table 1—Estimated Annual Reporting Burden 
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">DSCSA small dispensers assessment</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 per</LI>
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">Total hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Enrollment</ENT>
                        <ENT>200</ENT>
                        <ENT>1</ENT>
                        <ENT>200</ENT>
                        <ENT>0.5</ENT>
                        <ENT>100</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Assessment Questions Response</ENT>
                        <ENT>100</ENT>
                        <ENT>1</ENT>
                        <ENT>100</ENT>
                        <ENT>2</ENT>
                        <ENT>200</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT>300</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>300</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>
                    <E T="03">Submitting an enrollment and reporting activities.</E>
                     FDA estimates that no more than 200 respondents (
                    <E T="03">i.e.,</E>
                     the submitter or point of contact) will submit an enrollment, and that it will take, based on the various levels of resources by company, an average of 0.5 hours to complete an enrollment to FDA. FDA estimates that it will receive no more than 100 participants for the assessment. The estimated total time for respondents to submit an enrollment to participate in the assessment is 100 hours. FDA estimates that it will take, based on the various levels of resources by company, an average of 2 hours to compile and submit a response to the assessment. The estimated total number of hours for submitting a response to the assessment would be 200 hours. The total hours for the estimated reporting burden are 300 hours (table 1).
                </P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12,12,12,12,12">
                    <TTITLE>
                        Table 2—Estimated Annual Recordkeeping Burden 
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">DSCSA small dispensers assessment</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
                            <LI>burden per</LI>
                            <LI>recordkeeping</LI>
                        </CHED>
                        <CHED H="1">Total hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Records related to enrollment</ENT>
                        <ENT>200</ENT>
                        <ENT>1</ENT>
                        <ENT>200</ENT>
                        <ENT>0.5</ENT>
                        <ENT>100</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Records related to Assessment Questions Response</ENT>
                        <ENT>100</ENT>
                        <ENT>1</ENT>
                        <ENT>100</ENT>
                        <ENT>0.5</ENT>
                        <ENT>50</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT>300</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>150</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>
                    <E T="03">Recordkeeping activities.</E>
                     Recordkeeping activities include storing and maintaining records related to submitting to enroll to participate in the assessment and compiling reports. Respondents can use current record retention capabilities for electronic or paper storage to achieve these activities. FDA estimates that no more than 200 respondents will have recordkeeping activities related to assessment participation. FDA believes that it will take 0.5 hour to ensure that the documents related to enrollment to participate in the assessment are retained properly for a minimum of 1 year after the assessment is completed (as recommended by FDA). The resulting total to maintain the records related to submitting a request is 100 hours annually.
                </P>
                <P>
                    For retaining records related to the response to the assessment properly for a minimum of 1 year after the assessment is completed (as recommended by FDA), FDA estimates that it will take approximately 0.5 hour. As noted above, FDA estimates that the 100 respondents will submit one response for the assessment. The estimated total for maintaining records related to the assessment is 50 hours respectively. The total recordkeeping burden is estimated to be 150 hours (table 2).
                    <PRTPAGE P="18418"/>
                </P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12,12,12,12,12">
                    <TTITLE>
                        Table 3—Estimated Annual Third-Party Disclosure Burden 
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">DSCSA small dispensers assessment</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>disclosures per</LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual
                            <LI>disclosures</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>burden per</LI>
                            <LI>disclosure</LI>
                        </CHED>
                        <CHED H="1">Total hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Coordination with third-party entities related to enrollment</ENT>
                        <ENT>75</ENT>
                        <ENT>2</ENT>
                        <ENT>150</ENT>
                        <ENT>0.5</ENT>
                        <ENT>75</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Coordination with third-party entities related to assessment questions response</ENT>
                        <ENT>50</ENT>
                        <ENT>2</ENT>
                        <ENT>100</ENT>
                        <ENT>2</ENT>
                        <ENT>200</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT>125</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>275</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>
                    <E T="03">Third-party disclosure activities.</E>
                     For those assessment participants that involve third-party activities, FDA is taking into consideration the time that participants will spend coordinating with third-party entities (
                    <E T="03">e.g.,</E>
                     solution providers, wholesale distributors, consultants). For the enrollment, FDA estimates that 75 respondents will work with their respective partnering entities and the average number of partnering entities will be 2. FDA estimates that each respondent will spend 2 hours coordinating with each third-party entity. Thus, for 150 respondents with an average of 2 partnering entities, the estimated total burden for coordinating with partnering entities related to the enrollment is 75 hours. FDA estimates that for each of the 100 lists of assessment responses, it will take approximately 2 hours to coordinate with each partner, resulting in a total of 200 hours. The total estimation for third-party disclosure burden is 275 hours (table 3).
                </P>
                <SIG>
                    <DATED>Dated: March 8, 2024.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05294 Filed 3-12-24; 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-2023-D-5616]</DEPDOC>
                <SUBJECT>Annual Reportable Labeling Changes for New Drug Applications and Abbreviated New Drug Applications for Nonprescription Drug Products; Draft 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, Agency, or we) is announcing the availability of a draft guidance for industry entitled “Annual Reportable Labeling Changes for NDAs and ANDAs for Nonprescription Drug Products.” This draft guidance provides recommendations to applicants of approved new drug applications (NDAs) and abbreviated new drug applications (ANDAs) for nonprescription drug products on documenting minor labeling changes in the next annual report and provides examples of minor labeling changes that may be submitted in an annual report. The recommendations in this draft guidance address the types of minor labeling changes that may be appropriate to submit in an annual report to ensure that consumers have timely access to the most current labeling for a nonprescription drug product to ensure the product's safe and effective use. We anticipate that these recommendations may assist industry in understanding the circumstances in which it would be appropriate to document minor changes in the applicant's next annual report rather than submitting a prior approval supplement or “changes being effected” supplement, thereby reducing burden on industry and FDA.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit either electronic or written comments on the draft guidance by May 13, 2024 to ensure that the Agency considers your comment on this draft guidance before it begins work on the final version of the guidance.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments on any guidance 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-2023-D-5616 for “Annual Reportable Labeling Changes for NDAs and ANDAs for Nonprescription Drug Products.” 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 
                    <PRTPAGE P="18419"/>
                    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>
                <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 the draft 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. 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 draft guidance document.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Trang Tran, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 22, Rm. 4139, Silver Spring, MD 20993-0002, 240-402-7945.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>FDA is announcing the availability of a draft guidance for industry entitled “Annual Reportable Labeling Changes for NDAs and ANDAs for Nonprescription Drug Products.” This draft guidance provides recommendations to applicants of approved NDAs and ANDAs for nonprescription drug products on documenting minor labeling changes in the next annual report. The draft guidance also provides examples of minor labeling changes that may be submitted in an annual report.</P>
                <P>
                    FDA evaluates whether the data and information submitted as part of an NDA or ANDA for a nonprescription drug product demonstrate that the drug product is safe and effective for nonprescription use under the conditions prescribed, recommended, or suggested in its proposed labeling.
                    <SU>1</SU>
                    <FTREF/>
                     A nonprescription drug must be labeled with adequate directions for use.
                    <SU>2</SU>
                    <FTREF/>
                     Adequate directions for use are the directions under which the consumer can use the drug safely and for the purposes for which it is intended.
                    <SU>3</SU>
                    <FTREF/>
                     Therefore, labeling for a nonprescription drug product enables consumers to appropriately self-select and use the nonprescription drug product safely and effectively without the supervision of a healthcare practitioner.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         See sections 505(d) and 503(b)(1) of the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) (21 U.S.C. 355(d) and 353(b)(1)).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         See section 502(f)(1) of the FD&amp;C Act (21 U.S.C. 352(f)(1)).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         See 21 CFR 201.5.
                    </P>
                </FTNT>
                <P>
                    After FDA approves an NDA or ANDA, an applicant may make, or in certain cases propose to FDA, changes to the approved application. Section 506A of the FD&amp;C Act (21 U.S.C. 356a) and FDA regulations under §§ 314.70, 314.71, and 314.97 (21 CFR 314.70, 314.71, and 314.97) provide certain requirements for making and reporting to FDA changes to an approved NDA or ANDA, including an NDA or ANDA for a nonprescription drug product. Changes to an approved NDA or ANDA, including labeling changes, are categorized into one of three reporting categories: major, moderate, or minor.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         See §§ 314.70 and 314.97; see also the guidance for industry entitled “Changes to an Approved NDA or ANDA,” available at 
                        <E T="03">https://www.fda.gov/media/71846/download.</E>
                    </P>
                </FTNT>
                <P>
                    “Minor changes” include certain changes that have a minimal potential to have an adverse effect on the identity, strength, quality, purity, or potency of a drug product as these factors may relate to the safety or effectiveness of the drug product.
                    <SU>5</SU>
                    <FTREF/>
                     Minor changes with an approved NDA or ANDA may be implemented immediately by the applicant without the applicant submitting a supplement to FDA. The applicant must document minor changes, including minor labeling changes, in its next annual report in accordance with § 314.81(b)(2) (21 CFR 314.81(b)(2)) (
                    <E T="03">i.e.,</E>
                     the annual report covering the period when the change or changes occurred) submitted to FDA.
                    <SU>6</SU>
                    <FTREF/>
                     The annual report must include a summary of any changes in labeling, including minor changes, that have been made since the last report listed by date in the order in which they were implemented, or if no changes have been made, a statement of that fact.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         See § 314.70(d).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         See §§ 314.70(d) and 314.81(b)(2). Additionally, a representative sample of, among other things, the package labels must be submitted in the annual report (§ 314.81(b)(2)(iii)(
                        <E T="03">a</E>
                        )).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         See § 314.81(b)(2)(iii)(
                        <E T="03">c</E>
                        ).
                    </P>
                </FTNT>
                <P>
                    Determining the reporting category for a change to nonprescription drug labeling may present certain considerations that differ from changes to prescription drug labeling. Changes to the approved labeling for a nonprescription drug product may affect consumers' ability to appropriately self-select and use the nonprescription drug product safely and effectively without the supervision of a healthcare practitioner. Thus, changes to nonprescription labeling may not be considered minor even though similar changes may be considered minor when applied to the labeling of a prescription drug product. For example, certain changes in the layout of the package or container label for a prescription drug product that are consistent with FDA regulations (
                    <E T="03">e.g.,</E>
                     21 CFR part 201), without a change in the content of the labeling, might not affect the safe and effective use of the prescription drug product because it is used under the supervision of a healthcare practitioner. In contrast, changes in the layout of the package or container label and other changes to nonprescription drug labeling could affect consumers' ability to comprehend the nonprescription drug labeling and to appropriately self-select and use the nonprescription drug product such that the change would not be a minor change under § 314.70(d).
                </P>
                <P>FDA generally does not expect that editorial and similar minor labeling changes to nonprescription drug labeling would affect consumers' ability to appropriately self-select and use the nonprescription drug product without the supervision of a healthcare practitioner. Based on FDA's experience approving nonprescription drug labeling, FDA is providing specific examples of such editorial or similar minor labeling changes for nonprescription drug products that may be appropriate to include in an annual report.</P>
                <P>
                    This draft guidance is being issued consistent with FDA's good guidance practices regulation (21 CFR 10.115). The draft guidance, when finalized, will represent the current thinking of FDA 
                    <PRTPAGE P="18420"/>
                    on “Annual Reportable Labeling Changes for NDAs and ANDAs for Nonprescription Drug Products.” It does not establish any rights for any person and 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>
                <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. The previously approved collections of information are subject to review by the Office of Management and Budget (OMB) under the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501-3521). The collections of information in 21 CFR part 314 relating to the submissions of NDAs and ANDAs, supplemental applications, and annual reports have been approved under OMB control number 0910-0001. The collections of information in 21 CFR part 201 for the format and content requirements for nonprescription drug product labeling have been approved under OMB control number 0910-0340. The collections of information in 21 CFR part 211 have been approved under OMB control number 0910-0139.</P>
                <HD SOURCE="HD1">III. Electronic Access</HD>
                <P>
                    Persons with access to the internet may obtain the draft guidance at 
                    <E T="03">https://www.fda.gov/drugs/guidance-compliance-regulatory-information/guidances-drugs</E>
                    , 
                    <E T="03">https://www.fda.gov/regulatory-information/search-fda-guidance-documents</E>
                    , or 
                    <E T="03">https://www.regulations.gov</E>
                    .
                </P>
                <SIG>
                    <DATED>Dated: March 8, 2024.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05293 Filed 3-12-24; 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-2023-P-2874]</DEPDOC>
                <SUBJECT>Determination That Romidepsin Injection, 10 Milligrams/2 Milliliters (5 Milligrams/Milliliter) and 27.5 Milligrams/5.5 Milliliters (5 Milligrams/Milliliter), Were Not Withdrawn From Sale for Reasons of Safety or Effectiveness</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) has determined that Romidepsin Injection, 10 milligrams (mg)/2 milliliters (mL) (5 mg/mL) and 27.5 mg/5.5 mL (5 mg/mL), were not withdrawn from sale for reasons of safety or effectiveness. This determination will allow FDA to approve abbreviated new drug applications (ANDAs) for romidepsin solution, 10 mg/2 mL (5 mg/mL) and 27.5 mg/5.5 mL (5 mg/mL), that refer to these drugs as long as they meet relevant legal and regulatory requirements.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Veniqua Stewart, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, Rm. 6219, Silver Spring, MD 20993-0002, 301-796-3267, 
                        <E T="03">Veniqua.Stewart@fda.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Section 505(j) of the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) (21 U.S.C. 355(j)) allows the submission of an ANDA to market a generic version of a previously approved drug product. To obtain approval, the ANDA applicant must show, among other things, that the generic drug product: (1) has the same active ingredient(s), dosage form, route of administration, strength, conditions of use, and (with certain exceptions) labeling as the listed drug, which is a version of the drug that was previously approved, and (2) is bioequivalent to the listed drug. ANDA applicants do not have to repeat the extensive clinical testing otherwise necessary to gain approval of a new drug application (NDA).</P>
                <P>Section 505(j)(7) of the FD&amp;C Act requires FDA to publish a list of all approved drugs. FDA publishes this list as part of the “Approved Drug Products With Therapeutic Equivalence Evaluations,” which is known generally as the “Orange Book.” Under FDA regulations, drugs are removed from the list if the Agency withdraws or suspends approval of the drug's NDA or ANDA for reasons of safety or effectiveness or if FDA determines that the listed drug was withdrawn from sale for reasons of safety or effectiveness (21 CFR 314.162).</P>
                <P>A person may petition the Agency to determine, or the Agency may determine on its own initiative, whether a listed drug was withdrawn from sale for reasons of safety or effectiveness. This determination may be made at any time after the drug has been withdrawn from sale, but must be made prior to approving an ANDA that refers to the listed drug (§ 314.161 (21 CFR 314.161)). FDA may not approve an ANDA that does not refer to a listed drug.</P>
                <P>Romidepsin Injection, 10 mg/2 mL (5 mg/mL) and 27.5 mg/5.5 mL (5 mg/mL), are the subject of NDA 208574, held by Teva Pharmaceuticals USA, Inc. (Teva), and initially approved on March 13, 2020. Romidepsin Injection is currently indicated only for the treatment of cutaneous T-cell lymphoma (CTCL) in adult patients who have received at least one prior systemic therapy.</P>
                <P>Romidepsin Injection, 10 mg/2 mL (5 mg/mL) and 27.5 mg/5.5 mL (5 mg/mL), are currently listed in the “Discontinued Drug Product List” section of the Orange Book.</P>
                <P>E. Rust Consulting, LLC submitted a citizen petition dated July 11, 2023 (Docket No. FDA-2023-P-2874), under 21 CFR 10.30, requesting that the Agency determine whether Romidepsin Injection, 10 mg/2 mL (5 mg/mL) and 27.5 mg/5.5 mL (5 mg/mL), were withdrawn from sale for reasons of safety or effectiveness.</P>
                <P>After considering the citizen petition and reviewing Agency records and based on the information we have at this time, FDA has determined under § 314.161 that Romidepsin Injection, 10 mg/2 mL (5 mg/mL) and 27.5 mg/5.5 mL (5 mg/mL), were not withdrawn for reasons of safety or effectiveness. The petitioner has identified no data or other information suggesting that Romidepsin Injection, 10 mg/2 mL (5 mg/mL) and 27.5 mg/5.5 mL (5 mg/mL), were withdrawn for reasons of safety or effectiveness. We have carefully reviewed our files for records concerning the withdrawal of Romidepsin Injection, 10 mg/2 mL (5 mg/mL) and 27.5 mg/5.5 mL (5 mg/mL), from sale. We have also independently evaluated relevant literature and data for possible postmarketing adverse events.</P>
                <P>
                    We note that Romidepsin Injection, 10 mg/2 mL (5 mg/mL) and 27.5 mg/5.5 mL (5 mg/mL), previously were approved with an indication for treatment of peripheral T-cell lymphoma (PTCL) in adult patients who have received at least one prior therapy, under the Agency's accelerated approval regulations, 21 CFR part 314, subpart H. The accelerated approval of Teva's Romidepsin Injection for PTCL included a required postmarketing clinical trial intended to verify the clinical benefit of romidepsin (the Ro-CHOP study) for PTCL. Teva's Romidepsin Injection product was approved under the 505(b)(2) approval pathway, and the listed drug relied upon is Celgene Corp.'s (Celgene) NDA 022393, ISTODAX (romidepsin) for injection, 10 mg/vial. Celgene was acquired by Bristol-Meyers Squib Co. which is 
                    <PRTPAGE P="18421"/>
                    currently listed as the NDA holder in the Orange Book.
                </P>
                <P>On August 6, 2020, Celgene submitted high level results from the Ro-CHOP study to FDA, which indicated the study failed to meet its primary endpoint of progression-free survival. On May 14, 2021, Celgene informed FDA that after careful consideration, Celgene decided to voluntarily withdraw the PTCL indication from ISTODAX (romidepsin) for injection, 10 mg/vial. On June 17, 2021, Celgene submitted a supplemental NDA proposing to remove the PTCL indication. On July 14, 2021, Celgene submitted a letter asking FDA to withdraw approval of the PTCL indication pursuant to § 314.150(d) (21 CFR 314.150(d)) and waiving its opportunity for a hearing.</P>
                <P>
                    On August 27, 2021, Teva submitted a labeling supplement proposing to remove the PTCL indication. On September 12, 2021, the Agency requested Teva voluntarily request withdrawal of the PTCL indication pursuant to § 314.150(d) and waive its opportunity for a hearing. On September 14, 2021, Teva amended its supplement by submitting a cover letter requesting withdrawal of approval of the PTCL indication pursuant to § 314.150(d) and waiving its opportunity for a hearing. On December 8, 2021, FDA approved the supplemental NDA to revise the labeling to remove the PTCL indication. In the 
                    <E T="04">Federal Register</E>
                     of May 9, 2022 (87 FR 27644), FDA announced that it was withdrawing approval of the PTCL indications for ISTODAX (romidepsin) for injection, 10 mg/vial, and Romidepsin Injection. Therefore, Romidepsin Injection is only indicated for the treatment of CTCL in adult patients who have received at least one prior systemic therapy.
                </P>
                <P>
                    The Agency will continue to list Teva's Romidepsin Injection, 10 mg/2 mL (5 mg/mL) and 27.5 mg/5.5 mL (5 mg/mL), in the “Discontinued Drug Product List” section of the Orange Book. The “Discontinued Drug Product List” delineates, among other items, drug products that have been discontinued from marketing for reasons other than safety or effectiveness. FDA will accept and, where appropriate, approve ANDAs that refer to these drug products, but does not intend to do so if they propose to include the PTCL indication (see, 
                    <E T="03">e.g.,</E>
                     section 505(j)(2)(A)(v) and (j)(4)(G) of the FD&amp;C Act and 21 CFR 314.94(a)(8)(iv) and 314.127(a)(7)). If FDA determines that labeling for these drug products should be revised to meet current standards, the Agency will advise ANDA applicants to submit such labeling.
                </P>
                <SIG>
                    <DATED>Dated: March 8, 2024.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05298 Filed 3-12-24; 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-D-1158]</DEPDOC>
                <SUBJECT>Select Updates for the Premarket Cybersecurity Guidance: Section 524B of the Federal Food, Drug, and Cosmetic Act; Draft Guidance for Industry and Food and Drug Administration Staff; 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 the draft guidance entitled “Select Updates for the Premarket Cybersecurity Guidance: Section 524B of the FD&amp;C Act.” This draft guidance proposes select updates to the final guidance “Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions.” This draft guidance, when finalized, will identify the information FDA generally considers to be necessary for cyber devices to support obligations under the new amendments to the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) for ensuring cybersecurity of devices. This draft guidance is not final nor is it for implementation at this time.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit either electronic or written comments on the draft guidance by May 13, 2024 to ensure that the Agency considers your comment on this draft guidance before it begins work on the final version of the guidance.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments on any guidance 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-2021-D-1158 for “Select Updates for the Premarket Cybersecurity Guidance: Section 524B of the FD&amp;C Act.” 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 
                    <PRTPAGE P="18422"/>
                    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>
                <P>You may submit comments on any guidance at any time (see 21 CFR 10.115(g)(5)).</P>
                <P>
                    An electronic copy of the guidance document is available for download from the internet. See the 
                    <E T="02">SUPPLEMENTARY INFORMATION</E>
                     section for information on electronic access to the guidance. Submit written requests for a single hard copy of the draft guidance document entitled “Select Updates for the Premarket Cybersecurity Guidance: Section 524B of the FD&amp;C Act” to the Office of Policy, Center for Devices and Radiological Health, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 66, Rm. 5431, Silver Spring, MD 20993-0002. Send one self-addressed adhesive label to assist that office in processing your request.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Suzanne Schwartz, Center for Devices and Radiological Health, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 66, Rm. 5410, Silver Spring, MD 20993-0002, 301-796-6937; or James Myers, 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>Section 3305 of the Food and Drug Omnibus Reform Act of 2022 (FDORA), enacted on December 29, 2022, added section 524B “Ensuring Cybersecurity of Medical Devices” to the FD&amp;C Act. Under section 524B(a) of the FD&amp;C Act (21 U.S.C. 360n-2(a)), a person who submits a 510(k), premarket approval application (PMA), product development protocol (PDP), De Novo, or humanitarian device exemption (HDE) for a device that meets the definition of a cyber device, as defined under section 524B(c) of the FD&amp;C Act, is required to submit information to ensure that cyber devices meet the cybersecurity requirements under section 524B(b) of the FD&amp;C Act.</P>
                <P>FDA is proposing to selectively update the final guidance “Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions.” This draft guidance, when finalized, will identify the information FDA generally considers to be necessary to support obligations under section 524B of the FD&amp;C Act. Specifically, this draft guidance discusses who is required to comply with section 524B, the devices subject to section 524B, and the documentation recommendations for applicable premarket submissions. Additionally, FDA provides recommendations regarding premarket submissions for changes to cyber devices that had been previously authorized by FDA through 510(k), De Novo, HDE, PDP, and PMA submission pathways, and that require premarket submission. This draft guidance also discusses FDA's review of whether there is a reasonable assurance that the device and related systems are cybersecure for marketing authorizations submitted for cyber devices.</P>
                <P>This draft guidance is being issued consistent with FDA's good guidance practices regulation (21 CFR 10.115). The draft guidance, when finalized, will represent the current thinking of FDA on “Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions.” It does not establish any rights for any person and 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>
                <HD SOURCE="HD1">II. Electronic Access</HD>
                <P>
                    Persons interested in obtaining a copy of the draft guidance may do so by downloading an electronic copy from the internet. A search capability for all Center for Devices and Radiological Health guidance documents is available at 
                    <E T="03">https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/guidance-documents-medical-devices-and-radiation-emitting-products.</E>
                     This guidance document is also available at 
                    <E T="03">https://www.regulations.gov, https://www.fda.gov/regulatory-information/search-fda-guidance-documents</E>
                    , or 
                    <E T="03">https://www.fda.gov/vaccines-blood-biologics/guidance-compliance-regulatory-information-biologics.</E>
                     Persons unable to download an electronic copy of “Select Updates for the Premarket Cybersecurity Guidance: Section 524B of the FD&amp;C Act” may send an email request to 
                    <E T="03">CDRH-Guidance@fda.hhs.gov</E>
                     to receive an electronic copy of the document. Please use the document number GUI00001825 and complete title to identify the guidance you are requesting.
                </P>
                <HD SOURCE="HD1">III. Paperwork Reduction Act of 1995</HD>
                <P>While this guidance contains no new collection of information, it does refer to previously approved FDA collections of information. The previously approved collections of information are subject to review by the Office of Management and Budget (OMB) under the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501-3521). The collections of information in the following table have been approved by OMB:</P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s50,r100,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">21 CFR part; guidance; or FDA form</CHED>
                        <CHED H="1">Topic</CHED>
                        <CHED H="1">OMB control No.</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">807, subpart E</ENT>
                        <ENT>Premarket notification</ENT>
                        <ENT>0910-0120</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">814, subparts A through E</ENT>
                        <ENT>Premarket approval</ENT>
                        <ENT>0910-0231</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">814, subpart H</ENT>
                        <ENT>Humanitarian Use Devices; Humanitarian Device Exemption</ENT>
                        <ENT>0910-0332</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">812</ENT>
                        <ENT>Investigational Device Exemption</ENT>
                        <ENT>0910-0078</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">860, subpart D</ENT>
                        <ENT>De Novo classification process</ENT>
                        <ENT>0910-0844</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">820</ENT>
                        <ENT>Current Good Manufacturing Practice (CGMP); Quality System (QS) Regulation</ENT>
                        <ENT>0910-0073</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <PRTPAGE P="18423"/>
                    <DATED>Dated: March 8, 2024.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05295 Filed 3-12-24; 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 Nos. FDA-2019-E-5660 and FDA-2019-E-5661]</DEPDOC>
                <SUBJECT>Determination of Regulatory Review Period for Purposes of Patent Extension; DAURISMO</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 the Agency) has determined the regulatory review period for DAURISMO and is publishing this notice of that determination as required by law. FDA has made the determination because of the submission of applications to the Director of the U.S. Patent and Trademark Office (USPTO), Department of Commerce, for the extension of patents which claims that human drug product.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Anyone with knowledge that any of the dates as published (see 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                        ) are incorrect may submit either electronic or written comments and ask for a redetermination by May 13, 2024. Furthermore, any interested person may petition FDA for a determination regarding whether the applicant for extension acted with due diligence during the regulatory review period by September 9, 2024. See “Petitions” in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for more information.
                    </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 May 13, 2024. 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 Nos. FDA-2019-E-5660 and FDA-2019-E-5661 for “Determination of Regulatory Review Period for Purposes of Patent Extension; DAURISMO.” 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 § 10.20 (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>Beverly Friedman, Office of Regulatory Policy, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, Rm. 6250, Silver Spring, MD 20993, 301-796-3600.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>The Drug Price Competition and Patent Term Restoration Act of 1984 (Pub. L. 98-417) and the Generic Animal Drug and Patent Term Restoration Act (Pub. L. 100-670) generally provide that a patent may be extended for a period of up to 5 years so long as the patented item (human drug or biological product, animal drug product, medical device, food additive, or color additive) was subject to regulatory review by FDA before the item was marketed. Under these acts, a product's regulatory review period forms the basis for determining the amount of extension an applicant may receive.</P>
                <P>
                    A regulatory review period consists of two periods of time: a testing phase and an approval phase. For human drug products, the testing phase begins when the exemption to permit the clinical investigations of the drug becomes effective and runs until the approval phase begins. The approval phase starts 
                    <PRTPAGE P="18424"/>
                    with the initial submission of an application to market the human drug product and continues until FDA grants permission to market the drug product. Although only a portion of a regulatory review period may count toward the actual amount of extension that the Director of USPTO may award (for example, half the testing phase must be subtracted as well as any time that may have occurred before the patent was issued), FDA's determination of the length of a regulatory review period for a human drug product will include all of the testing phase and approval phase as specified in 35 U.S.C. 156(g)(1)(B).
                </P>
                <P>FDA has approved for marketing the human drug product DAURISMO (glasdegib). DAURISMO is indicated, in combination with low-dose cytarabine, for the treatment of newly diagnosed acute myeloid leukemia in adult patients who are 75 years old and older, or who have comorbidities that preclude use of intensive induction chemotherapy. Subsequent to this approval, the USPTO received a patent term restoration application for DAURISMO (U.S. Patent Nos. 8,148,401; 8,431,597) from Pfizer, Inc. and the USPTO requested FDA's assistance in determining the patent's eligibility for patent term restoration. In a letter dated December 26, 2019, FDA advised the USPTO that this human drug product had undergone a regulatory review period and that the approval of DAURISMO represented the first permitted commercial marketing or use of the product. Thereafter, the USPTO requested that FDA determine the product's regulatory review period.</P>
                <HD SOURCE="HD1">II. Determination of Regulatory Review Period</HD>
                <P>FDA has determined that the applicable regulatory review period for DAURISMO is 3,388 days. Of this time, 3,179 days occurred during the testing phase of the regulatory review period, while 209 days occurred during the approval phase. These periods of time were derived from the following dates:</P>
                <P>
                    <E T="03">1. The date an exemption under section 505(i) of the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) (21 U.S.C. 355(i)) became effective:</E>
                     August 14, 2009. The applicant claims August 15, 2009, as the date the investigational new drug application (IND) became effective. However, FDA records indicate that the IND effective date was August 14, 2009, which was the first date after receipt of the IND that the investigational studies were allowed to proceed.
                </P>
                <P>
                    <E T="03">2. The date the application was initially submitted with respect to the human drug product under section 505 of the FD&amp;C Act:</E>
                     April 27, 2018. FDA has verified the applicant's claim that the new drug application (NDA) for DAURISMO (NDA 210656) was initially submitted on April 27, 2018.
                </P>
                <P>
                    <E T="03">3. The date the application was approved:</E>
                     November 21, 2018. FDA has verified the applicant's claim that NDA 210656 was approved on November 21, 2018.
                </P>
                <P>This determination of the regulatory review period establishes the maximum potential length of a patent extension. However, the USPTO applies several statutory limitations in its calculations of the actual period for patent extension. In its applications for patent extension, this applicant seeks 661 days or 1,121 days of patent term extension.</P>
                <HD SOURCE="HD1">III. Petitions</HD>
                <P>
                    Anyone with knowledge that any of the dates as published are incorrect may submit either electronic or written comments and, under 21 CFR 60.24, ask for a redetermination (see 
                    <E T="02">DATES</E>
                    ). Furthermore, as specified in § 60.30 (21 CFR 60.30), any interested person may petition FDA for a determination regarding whether the applicant for extension acted with due diligence during the regulatory review period. To meet its burden, the petition must comply with all the requirements of § 60.30, including but not limited to: must be timely (see 
                    <E T="02">DATES</E>
                    ), must be filed in accordance with § 10.20, must contain sufficient facts to merit an FDA investigation, and must certify that a true and complete copy of the petition has been served upon the patent applicant. (See H. Rept. 857, part 1, 98th Cong., 2d sess., pp. 41-42, 1984.) Petitions should be in the format specified in 21 CFR 10.30.
                </P>
                <P>
                    Submit petitions electronically to 
                    <E T="03">https://www.regulations.gov</E>
                     at Docket No. FDA-2013-S-0610. Submit written petitions (two copies are required) to the Dockets Management Staff (HFA-305), Food and Drug Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.
                </P>
                <SIG>
                    <DATED>Dated: March 8, 2024.</DATED>
                    <NAME>Lauren K. Roth,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05305 Filed 3-12-24; 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>Health Resources and Services Administration</SUBAGY>
                <SUBJECT>Meeting of the Advisory Committee on Infant and Maternal Mortality</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Health Resources and Services Administration (HRSA), Department of Health and Human Services.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with the Federal Advisory Committee Act, this notice announces that the Advisory Committee on Infant and Maternal Mortality (ACIMM or Committee) has scheduled a public meeting. Information about ACIMM and the agenda for this meeting can be found on the ACIMM website at 
                        <E T="03">https://www.hrsa.gov/advisory-committees/infant-mortality/index.html.</E>
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P/>
                    <P>• April 2, 2024, 9 a.m. to 4 p.m. Central Time (CT);</P>
                    <P>• April 3, 2024, 12 p.m. to 6 p.m. CT; and</P>
                    <P>• April 4, 2024, 9 a.m. to 12 p.m. CT.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        This meeting will be held in-person at Delmar Divine, 5501 Delmar Boulevard, St. Louis, Missouri 63112 and virtually via webinar. The webinar link and log-in information will be available at the ACIMM website before the meeting: 
                        <E T="03">https://www.hrsa.gov/advisory-committees/infant-mortality/index.html.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Vanessa Lee, MPH, Designated Federal Official, Maternal and Child Health Bureau, HRSA, 5600 Fishers Lane, Rockville, Maryland 20857; 301-443-0543; or 
                        <E T="03">SACIM@hrsa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>ACIMM is authorized by section 222 of the Public Health Service Act (42 U.S.C. 217a), as amended. The Committee is governed by provisions of the Federal Advisory Committee Act (5 U.S.C. Chapter 10), as amended.</P>
                <P>
                    ACIMM advises the Secretary of Health and Human Services (Secretary) on department activities, partnerships, policies, and programs directed at reducing infant mortality, maternal mortality and severe maternal morbidity, and improving the health status of infants and women before, during, and after pregnancy. The Committee provides advice on how to coordinate federal, state, local, tribal, and territorial governmental efforts designed to improve infant mortality, related adverse birth outcomes, maternal health, as well as influence 
                    <PRTPAGE P="18425"/>
                    similar efforts in the private and voluntary sectors. The Committee provides guidance and recommendations on the policies, programs, and resources required to address the disparities and inequities in infant mortality, related adverse birth outcomes and maternal health outcomes, including maternal mortality and severe maternal morbidity. With its focus on underlying causes of the disparities and inequities seen in birth outcomes for women and infants, ACIMM advises the Secretary on the health, social, economic, and environmental factors contributing to the inequities and proposes structural, policy, and/or systems level changes.
                </P>
                <P>The agenda for the April 2-4, 2024, meeting is being finalized and may include the following topics: updates on the federal Healthy Start program; Committee discussions on the workgroup topics of rural health care access, social drivers of health, and women's health before/between pregnancies; federal updates; and remarks from individuals with lived experience and community members, including those representing community-based organizations, on how to achieve optimal maternal health and overall birth outcomes for underserved populations, including Black/African-American families. Agenda items are subject to change as priorities dictate. Refer to the ACIMM website listed above for any updated information concerning the meeting.</P>
                <P>
                    Members of the public will have the opportunity to provide written or oral comments. Requests to submit a written statement or make oral comments to ACIMM should be sent to Vanessa Lee, using the email address above at least 3 business days prior to the meeting. Public participants may submit written statements in advance of the scheduled meeting by emailing 
                    <E T="03">SACIM@hrsa.gov.</E>
                     Oral comments will be honored in the order they are requested and may be limited as time allows.
                </P>
                <P>Individuals who plan to attend and need special assistance or a reasonable accommodation should notify Vanessa Lee at the contact information listed above at least 10 business days prior to the meeting.</P>
                <SIG>
                    <NAME>Maria G. Button,</NAME>
                    <TITLE>Director, Executive Secretariat.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05300 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4165-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <DEPDOC>[Docket No. USCG-2024-0183]</DEPDOC>
                <SUBJECT>Information Collection Request to Office of Management and Budget; OMB Control Number: 1625-0109</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Sixty-day notice requesting comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In compliance with the Paperwork Reduction Act of 1995, the U.S. Coast Guard intends to submit an Information Collection Request (ICR) to the Office of Management and Budget (OMB), Office of Information and Regulatory Affairs (OIRA), requesting an extension of its approval for the following collection of information: 1625-0109, Drawbridge Operation Regulations; without change. Our ICR describes the information we seek to collect from the public. Before submitting this ICR to OIRA, the Coast Guard is inviting comments as described below.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must reach the Coast Guard on or before May 13, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments identified by Coast Guard docket number [USCG-2024-0183] to the Coast Guard using the Federal eRulemaking 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>
                    <P>
                        A copy of the ICR is available through the docket on the internet at 
                        <E T="03">https://www.regulations.gov.</E>
                         Additionally, copies are available from: Commandant (CG-6P), Attn: Paperwork Reduction Act Manager, U.S. Coast Guard, 2703 Martin Luther King Jr. Ave. SE, Stop 7710, Washington, DC 20593-7710.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>A.L. Craig, Office of Privacy Management, telephone 202-475-3528, or fax 202-372-8405, for questions on these documents.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Public Participation and Request for Comments</HD>
                <P>
                    This notice relies on the authority of the Paperwork Reduction Act of 1995; 44 U.S.C. 3501 
                    <E T="03">et seq.,</E>
                     chapter 35, as amended. An ICR is an application to OIRA seeking the approval, extension, or renewal of a Coast Guard collection of information (Collection). The ICR contains information describing the Collection's purpose, the Collection's likely burden on the affected public, an explanation of the necessity of the Collection, and other important information describing the Collection. There is one ICR for each Collection.
                </P>
                <P>The Coast Guard invites comments on whether this ICR should be granted based on the Collection being necessary for the proper performance of Departmental functions. In particular, the Coast Guard would appreciate comments addressing: (1) the practical utility of the Collection; (2) the accuracy of the estimated burden of the Collection; (3) ways to enhance the quality, utility, and clarity of information subject to the Collection; and (4) ways to minimize the burden of the Collection on respondents, including the use of automated collection techniques or other forms of information technology.</P>
                <P>In response to your comments, we may revise this ICR or decide not to seek an extension of approval for the Collection. We will consider all comments and material received during the comment period.</P>
                <P>We encourage you to respond to this request by submitting comments and related materials. Comments must contain the OMB Control Number of the ICR and the docket number of this request, [USCG-2024-0183], and must be received by May 13, 2024.</P>
                <HD SOURCE="HD1">Submitting Comments</HD>
                <P>
                    We encourage you to submit comments through the Federal eRulemaking Portal at 
                    <E T="03">https://www.regulations.gov.</E>
                     If your material cannot be submitted using 
                    <E T="03">https://www.regulations.gov,</E>
                     contact the person in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this document for alternate instructions. Documents mentioned in this notice, and all public comments, are in our online docket at 
                    <E T="03">https://www.regulations.gov</E>
                     and can be viewed by following that website's instructions. Additionally, if you go to the online docket and sign up for email alerts, you will be notified when comments are posted.
                </P>
                <P>
                    We accept anonymous comments. All comments received will be posted without change to 
                    <E T="03">https://www.regulations.gov</E>
                     and 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">Information Collection Request</HD>
                <P>
                    <E T="03">Title:</E>
                     Drawbridge Operation Regulations.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1625-0109.
                    <PRTPAGE P="18426"/>
                </P>
                <P>
                    <E T="03">Summary:</E>
                     The Bridge Program receives approximately 412 requests from bridge owners per year to change the operating schedule of various drawbridges across the navigable waters of the United States. The information needed for the change to the operating schedule can only be obtained from the bridge owner and is generally provided to the Coast Guard in either written or electronic format.
                </P>
                <P>
                    <E T="03">Need:</E>
                     33 U.S.C. 499 authorizes the Coast Guard to change the operating schedules drawbridges that cross over navigable waters of the United States.
                </P>
                <P>
                    <E T="03">Forms:</E>
                     None.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     The public and private owners of bridges over navigable waters of the United States.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Hour Burden Estimate:</E>
                     The estimated burden is remains 1,672 hours a year.
                </P>
                <EXTRACT>
                    <FP>(Authority: The Paperwork Reduction Act of 1995; 44 U.S.C. chapter 35, as amended)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: March 8, 2024.</DATED>
                    <NAME>Kathleen Claffie,</NAME>
                    <TITLE>Chief, Office of Privacy Management, U.S. Coast Guard.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05337 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <DEPDOC>[Docket No. USCG-2024-0185]</DEPDOC>
                <SUBJECT>Information Collection Request to Office of Management and Budget; OMB Control Number: 1625-0025</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Sixty-day notice requesting comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In compliance with the Paperwork Reduction Act of 1995, the U.S. Coast Guard intends to submit an Information Collection Request (ICR) to the Office of Management and Budget (OMB), Office of Information and Regulatory Affairs (OIRA), requesting an extension of its approval for the following collection of information: 1625-0025, Carriage of Bulk Solids Requiring Special Handling; without change. Our ICR describes the information we seek to collect from the public. Before submitting this ICR to OIRA, the Coast Guard is inviting comments as described below.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must reach the Coast Guard on or before May 13, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments identified by Coast Guard docket number [USCG-2024-0185] to the Coast Guard using the Federal eRulemaking 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>
                    <P>
                        A copy of the ICR is available through the docket on the internet at 
                        <E T="03">https://www.regulations.gov.</E>
                         Additionally, copies are available from: Commandant (CG-6P), Attn: Paperwork Reduction Act Manager, U.S. Coast Guard, 2703 Martin Luther King Jr. Ave. SE, Stop 7710, Washington, DC 20593-7710.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>A.L. Craig, Office of Privacy Management, telephone 202-475-3528, or fax 202-372-8405, for questions on these documents.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Public Participation and Request for Comments</HD>
                <P>
                    This notice relies on the authority of the Paperwork Reduction Act of 1995; 44 U.S.C. 3501 
                    <E T="03">et seq.,</E>
                     chapter 35, as amended. An ICR is an application to OIRA seeking the approval, extension, or renewal of a Coast Guard collection of information (Collection). The ICR contains information describing the Collection's purpose, the Collection's likely burden on the affected public, an explanation of the necessity of the Collection, and other important information describing the Collection. There is one ICR for each Collection.
                </P>
                <P>The Coast Guard invites comments on whether this ICR should be granted based on the Collection being necessary for the proper performance of Departmental functions. In particular, the Coast Guard would appreciate comments addressing: (1) the practical utility of the Collection; (2) the accuracy of the estimated burden of the Collection; (3) ways to enhance the quality, utility, and clarity of information subject to the Collection; and (4) ways to minimize the burden of the Collection on respondents, including the use of automated collection techniques or other forms of information technology.</P>
                <P>In response to your comments, we may revise this ICR or decide not to seek an extension of approval for the Collection. We will consider all comments and material received during the comment period.</P>
                <P>We encourage you to respond to this request by submitting comments and related materials. Comments must contain the OMB Control Number of the ICR and the docket number of this request, [USCG-2024-0185], and must be received by May 13, 2024.</P>
                <HD SOURCE="HD1">Submitting Comments</HD>
                <P>
                    We encourage you to submit comments through the Federal eRulemaking Portal at 
                    <E T="03">https://www.regulations.gov.</E>
                     If your material cannot be submitted using 
                    <E T="03">https://www.regulations.gov,</E>
                     contact the person in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this document for alternate instructions. Documents mentioned in this notice, and all public comments, are in our online docket at 
                    <E T="03">https://www.regulations.gov</E>
                     and can be viewed by following that website's instructions. Additionally, if you go to the online docket and sign up for email alerts, you will be notified when comments are posted.
                </P>
                <P>
                    We accept anonymous comments. All comments received will be posted without change to 
                    <E T="03">https://www.regulations.gov</E>
                     and 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">Information Collection Request</HD>
                <P>
                    <E T="03">Title:</E>
                     Carriage of Bulk Solids Requiring Special Handling—46 CFR part 148.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1625-0025.
                </P>
                <P>
                    <E T="03">Summary:</E>
                     As specified in 46 CFR part 148, the petition for a Special Permit allows the Coast Guard to determine the manner of safe carriage for unlisted materials. The information required by Dangerous Cargo Manifests and Shipping Papers permit vessel crews and emergency personnel to properly and safely respond to accidents involving hazardous substances. See 46 CFR 148 subpart B and §§ 148.60 and 148.70.
                </P>
                <P>
                    <E T="03">Need:</E>
                     The Coast Guard administers and enforces statutes and rules for the safe transport and stowage of hazardous materials, including bulk solids.
                </P>
                <P>
                    <E T="03">Forms:</E>
                     None.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Owners and operators of vessels that carry certain bulk solids.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Hour Burden Estimate:</E>
                     The estimated burden has decreased from 910 hours to 760 hours a year; due to a decrease in the estimated annual number of responses.
                </P>
                <P>
                    <E T="03">Authority:</E>
                     The Paperwork Reduction Act of 1995; 44 U.S.C. chapter 35, as amended.
                </P>
                <SIG>
                    <DATED>Dated: March 8, 2024.</DATED>
                    <NAME>Kathleen Claffie,</NAME>
                    <TITLE>Chief, Office of Privacy Management, U.S. Coast Guard.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05336 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18427"/>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <DEPDOC>[Docket No. USCG-2024-0184]</DEPDOC>
                <SUBJECT>Information Collection Request to Office of Management and Budget; OMB Control Number: 1625-0007</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Sixty-day notice requesting comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In compliance with the Paperwork Reduction Act of 1995, the U.S. Coast Guard intends to submit an Information Collection Request (ICR) to the Office of Management and Budget (OMB), Office of Information and Regulatory Affairs (OIRA), requesting an extension of its approval for the following collection of information: 1625-0007, Characteristics of Liquid Chemicals Proposed for Bulk Water Movement; without change. Our ICR describes the information we seek to collect from the public. Before submitting this ICR to OIRA, the Coast Guard is inviting comments as described below.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must reach the Coast Guard on or before May 13, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments identified by Coast Guard docket number [USCG-2024-0184] to the Coast Guard using the Federal eRulemaking 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>
                    <P>
                        A copy of the ICR is Available through the docket on the internet at 
                        <E T="03">https://www.regulations.gov.</E>
                         Additionally, copies are available from: Commandant (CG-6P), Attn: Paperwork Reduction Act Manager, U.S. Coast Guard, 2703 Martin Luther King Jr. Ave. SE, Stop 7710, Washington, DC 20593-7710.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>A.L. Craig, Office of Privacy Management, telephone 202-475-3528, or fax 202-372-8405, for questions on these documents.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Public Participation and Request for Comments</HD>
                <P>
                    This notice relies on the authority of the Paperwork Reduction Act of 1995; 44 U.S.C. 3501 
                    <E T="03">et seq.,</E>
                     chapter 35, as amended. An ICR is an application to OIRA seeking the approval, extension, or renewal of a Coast Guard collection of information (Collection). The ICR contains information describing the Collection's purpose, the Collection's likely burden on the affected public, an explanation of the necessity of the Collection, and other important information describing the Collection. There is one ICR for each Collection.
                </P>
                <P>The Coast Guard invites comments on whether this ICR should be granted based on the Collection being necessary for the proper performance of Departmental functions. In particular, the Coast Guard would appreciate comments addressing: (1) the practical utility of the Collection; (2) the accuracy of the estimated burden of the Collection; (3) ways to enhance the quality, utility, and clarity of information subject to the Collection; and (4) ways to minimize the burden of the Collection on respondents, including the use of automated collection techniques or other forms of information technology.</P>
                <P>In response to your comments, we may revise this ICR or decide not to seek an extension of approval for the Collection. We will consider all comments and material received during the comment period.</P>
                <P>We encourage you to respond to this request by submitting comments and related materials. Comments must contain the OMB Control Number of the ICR and the docket number of this request, [USCG-2024-0184], and must be received by May 13, 2024.</P>
                <HD SOURCE="HD1">Submitting Comments</HD>
                <P>
                    We encourage you to submit comments through the Federal eRulemaking Portal at 
                    <E T="03">https://www.regulations.gov.</E>
                     If your material cannot be submitted using 
                    <E T="03">https://www.regulations.gov,</E>
                     contact the person in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this document for alternate instructions. Documents mentioned in this notice, and all public comments, are in our online docket at 
                    <E T="03">https://www.regulations.gov</E>
                     and can be viewed by following that website's instructions. Additionally, if you go to the online docket and sign up for email alerts, you will be notified when comments are posted.
                </P>
                <P>
                    We accept anonymous comments. All comments received will be posted without change to 
                    <E T="03">https://www.regulations.gov</E>
                     and 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">Information Collection Request</HD>
                <P>
                    <E T="03">Title:</E>
                     Characteristics of Liquid Chemicals Proposed for Bulk Water Movement.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1625-0007.
                </P>
                <P>
                    <E T="03">Summary:</E>
                     Chemical manufacturers submit chemical data to the Coast Guard. The Coast Guard evaluates the information for hazardous properties of the chemical to be shipped via tank vessel. A determination is made as to the kind and degree of precaution which must be taken to protect the vessel and its contents.
                </P>
                <P>
                    <E T="03">Need:</E>
                     46 CFR parts 30 to 40, 151, 153, and 154 govern the transportation of hazardous materials. The chemical industry constantly produces new materials that must be moved by water. Each of these new materials has unique characteristics that require special attention to their mode of shipment.
                </P>
                <P>
                    <E T="03">Forms:</E>
                     None.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Manufacturers of chemicals.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Hour Burden Estimate:</E>
                     The estimated annual burden has increased from 600 hours to 2,190 hours a year, due to an increase in the estimate annual number of responses.
                </P>
                <EXTRACT>
                    <FP>(Authority: The Paperwork Reduction Act of 1995; 44 U.S.C. chapter 35, as amended)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: March 8, 2024.</DATED>
                    <NAME>Kathleen Claffie,</NAME>
                    <TITLE>Chief, Office of Privacy Management, U.S. Coast Guard.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05340 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Indian Affairs</SUBAGY>
                <DEPDOC>[245A2100DD/AAKC001030/A0A501010.999900]</DEPDOC>
                <SUBJECT>Indian Gaming; Approval of Tribal-State Class III Gaming Compact Between the Shakopee Mdewakanton Sioux Community of Minnesota and the State of Minnesota for Blackjack</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Indian Affairs, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice publishes the approval of the Addendum to Tribal-State Compact for Control of Class III Blackjack on the Shakopee Mdewakanton Sioux Community Reservation in Minnesota for Class III Card Games.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The compact takes effect on March 13, 2024.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ms. Paula L. Hart, Director, Office of Indian 
                        <PRTPAGE P="18428"/>
                        Gaming, Office of the Assistant Secretary—Indian Affairs, Washington, DC 20240, 
                        <E T="03">IndianGaming@bia.gov;</E>
                         (202) 219-4066.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Under section 11 of the Indian Gaming Regulatory Act (IGRA), Public Law 100-497, 25 U.S.C. 2701 
                    <E T="03">et seq.,</E>
                     the Secretary of the Interior shall publish in the 
                    <E T="04">Federal Register</E>
                     notice of approved Tribal-State compacts for the purpose of engaging in Class III gaming activities on Indian lands. As required by 25 CFR 293.4, all compacts and amendments are subject to review and approval by the Secretary. The Amendment authorizes class III card games in addition to blackjack, adds definitions, regulatory standards for class III card games, background investigations, and provisions for enforcement and dispute resolution. The Amendment is approved.
                </P>
                <SIG>
                    <NAME>Bryan Newland,</NAME>
                    <TITLE>Assistant Secretary—Indian Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05276 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4337-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Forest Service</SUBAGY>
                <AGENCY TYPE="O">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Land Management</SUBAGY>
                <DEPDOC>[BLM_UT_FRN_MO4500172883]</DEPDOC>
                <SUBJECT>Notice of Availability of the Draft Resource Management Plan and Environmental Impact Statement for the Bears Ears National Monument in Utah</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior; Forest Service, Agriculture (USDA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the National Environmental Policy Act of 1969, as amended (NEPA), and the Federal Land Policy and Management Act of 1976, as amended (FLPMA), the Bureau of Land Management (BLM) and U.S. Department of Agriculture, Forest Service (USDA Forest Service), collectively “the Agencies,” have prepared a Draft Resource Management Plan (RMP) and Draft Environmental Impact Statement (EIS) for the Bears Ears National Monument (BENM or Monument), and by this notice are providing information announcing the opening of the comment period on the Draft RMP/EIS and the comment period on proposed areas of critical environmental concern (ACECs) on lands managed by the BLM and proposed recreational shooting closures. The BLM is leading the NEPA process in partnership with the USDA Forest Service, which will sign a decision for the USDA Forest Service-managed lands based on the analysis in the EIS. The Agencies have and will continue to meaningfully engage the Bears Ears Commission in the development of the RMP and EIS, as required by Proclamation 10285.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        This notice announces the opening of a 90-day comment period for the Draft RMP/EIS beginning with the date following the Environmental Protection Agency's (EPA) publication of its Notice of Availability (NOA) of the Draft RMP/EIS in the 
                        <E T="04">Federal Register</E>
                        . The EPA usually publishes its NOAs on Fridays.
                    </P>
                    <P>To afford the Agencies the opportunity to consider comments in the Proposed RMP/Final EIS, please ensure the Agencies receive your comments prior to the close of the 90-day public comment period or 15 days after the last public meeting, whichever is later.</P>
                    <P>In addition, this notice announces the opening of a 90-day comment period for proposed recreational shooting closures and a 90-day comment period for proposed ACECs on lands managed by the BLM. The Agencies must receive your comments by June 11, 2024.</P>
                    <P>
                        The Agencies will hold a total of seven public meetings. Two meetings will be held virtually, and five meetings will be conducted in-person. The specific times and locations of the public meetings will be announced at least 15 days in advance through local media, social media, newspapers, and the ePlanning website (see 
                        <E T="02">ADDRESSES</E>
                        ).
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The Draft RMP/EIS is available for review on the BLM ePlanning project website at 
                        <E T="03">https://eplanning.blm.gov/eplanning-ui/project/2020347/510.</E>
                    </P>
                    <P>Written comments related to the BENM Draft RMP/EIS may be submitted by any of the following methods:</P>
                    <FP SOURCE="FP-1">
                        • 
                        <E T="03">Website: https://eplanning.blm.gov/eplanning-ui/project/2020347/510</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        • 
                        <E T="03">Mail:</E>
                         ATTN: Monument Planning, BLM Monticello Field Office, 365 North Main, Monticello, UT 84535
                    </FP>
                    <P>
                        Documents pertinent to this proposal may be examined online at 
                        <E T="03">https://eplanning.blm.gov/eplanning-ui/project/2020347/570</E>
                         and at the BLM Monticello Field Office, 365 North Main, Monticello, Utah 84535.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jill Stephenson, Project Manager, Bureau of Land Management Canyon Country District, 82 E Dogwood, Moab, Utah, 84532, by phone at 435-587-1529, or email at 
                        <E T="03">BLM_UT_Monticello_Monuments@blm.gov.</E>
                         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 for contacting Ms. Stephenson. 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>This document provides notice that the BLM Utah State Director and Manti-La Sal Forest Supervisor have prepared a Draft RMP/EIS, provides information announcing the opening of the comment period on the Draft RMP/EIS, and announces the comment period on the proposed ACECs and proposed recreational shooting closures. The planning area is located in San Juan County, Utah, and encompasses approximately 1.36 million acres of Federal land.</P>
                <P>Management of BENM is currently guided by the 2020 BENM Approved Monument Management Plans, 2008 Monticello Approved RMP, 2008 Moab Approved RMP, and 1986 Manti-La Sal National Forest Land and Resource Management Plan (LRMP), to the extent the management actions in these plans are consistent with Presidential Proclamation 10285 (October 8, 2021).</P>
                <HD SOURCE="HD1">Purpose and Need for the Planning Effort</HD>
                <P>The purpose and need serve to frame the identification of issues, alternatives development, and effects analysis. Proclamation 10285 directs the Agencies to “prepare and maintain a new management plan for the entire monument” for the specific purposes of “protecting and restoring the objects identified [in Proclamation 10285] and in Proclamation 9558.”</P>
                <P>The RMP's underlying purpose (40 CFR 1502.13) is to provide a management framework—including goals, objectives, and management direction—to guide BENM management consistent with the protection of monument objects and the management direction provided in Proclamation 10285.</P>
                <P>
                    The purpose and need for the BENM RMP is aligned with the purpose and need to amend the plan direction and management allocation for the BENM in the Manti-La Sal National Forest LRMP. The proposed programmatic amendment would incorporate the proposed BENM RMP and boundary 
                    <PRTPAGE P="18429"/>
                    area into the Manti-La Sal LRMP. The scale of the plan amendment applies to USDA Forest Service lands within the BENM boundary area. The Forest Service Planning Rule at 36 CFR 219.13(b)(2) requires responsible officials to provide notice of which substantive requirements of 36 CFR 219.8 through 219.11 are likely to be directly related to the amendment. Based on the criteria at 36 CFR 219.13(b)(5), the substantive Planning Rule provisions that are likely to be directly related to the proposed amendment of the Manti-La Sal National Forest LRMP are: 36 CFR 219.8 (b) (1), (5), and (6), regarding social and economic sustainability; 36 CFR 219.10 (a)(1), (4), (5), (7), (8), and (10), regarding integrated resource management for multiple use; and 36 CFR 219.10 (b)(1)(ii), (iii), and (vi), regarding cultural and historic resources, areas of Tribal importance, and management of designated areas.
                </P>
                <HD SOURCE="HD1">Alternatives Including the Preferred Alternative</HD>
                <P>The Agencies have analyzed five alternatives in detail, including the no action alternative.</P>
                <P>Alternative A, the no action alternative, represents current management from the 2020 BENM Approved Monument Management Plans—which apply to lands that remained in BENM under Proclamation 9681—and to the 2008 Monticello Approved RMP, 2008 Moab Approved RMP, and 1986 Manti-La Sal National Forest LRMP—which apply to the lands that were excluded from BENM under Proclamation 9681—to the extent that those management actions are consistent with Proclamation 10285. In some cases, decisions in the 2008 Monticello Approved RMP, 2008 Moab Approved RMP, and 1986 Manti-La Sal National Forest LRMP are inconsistent with Proclamation 10285; in those instances, Alternative A has been modified to be consistent with Proclamation 10285.</P>
                <P>Alternative B would provide the most permissive management for discretionary actions that are compatible with the protection of BENM objects. This alternative would focus on on-site education and interpretation and allow for the development of facilities to protect BENM objects.</P>
                <P>Alternative C would allow discretionary actions only if necessary to protect BENM objects. This alternative would focus on off-site education and interpretation and allow for limited development of facilities to protect BENM objects.</P>
                <P>Alternative D would allow for the continuation of natural processes by limiting or discontinuing discretionary uses. This alternative would minimize human-created facilities and management and would emphasize natural conditions.</P>
                <P>Alternative E would emphasize resource protection and maximize the consideration and use of Tribal perspectives on managing the BENM landscape. This alternative includes consideration of natural processes and seasonal cycles in the management of the BENM, and extensive collaboration with Tribal Nations to incorporate those considerations into the day-to-day management of the Monument.</P>
                <P>The Agencies considered five additional alternatives but dismissed these alternatives from detailed analysis as explained in the Draft RMP/EIS.</P>
                <P>The State Director and Forest Supervisor have identified Alternative E as the preferred alternative. Alternative E was found to best meet the State Director's and Forest Supervisor's planning guidance and, therefore, was selected as the preferred alternative because it provides goals, objectives, and management direction determined to be effective at protecting monument objects, balancing resource uses, and meeting the purpose and need. The preferred alternative does not constitute a commitment or decision, and there is no requirement to select the preferred alternative in the Records of Decision.</P>
                <HD SOURCE="HD1">Mitigation</HD>
                <P>The Draft RMP/EIS identifies, analyzes, and considers best management practices to mitigate the reasonably foreseeable impacts to resources and monument objects. Best management practices may include measures to avoid, minimize, rectify, reduce, or eliminate reasonably foreseeable impacts over time, and may be considered at multiple scales, including the landscape scale.</P>
                <HD SOURCE="HD1">ACECs</HD>
                <P>
                    Consistent with the BLM's land use planning regulations at 43 CFR 1610.7-2(b), the BLM is announcing the opening of a 90-day comment period on the ACECs proposed for designation on BLM-managed lands. Comments may be submitted using any of the methods listed in the 
                    <E T="02">ADDRESSES</E>
                     section earlier.
                </P>
                <P>The proposed ACECs included in preferred alternative are:</P>
                <P>• San Juan River ACEC—approximately 1,485 acres. Designation proposed to protect scenic and cultural resources, fish and wildlife, natural systems and processes, and geologic features. Identified special management would include preserving the natural visual character of the landscape in some portions of the ACEC (Visual Resource Management (VRM) Class I) and retaining the existing visual character of the landscape in other portions of the ACEC in a manner where authorized changes do not attract the attention of the casual observer (VRM Class II); avoiding rights-of-way (ROW) designations in the San Juan Hill Recreation Management Zone; prohibiting permitted/personal use of woodland products, except for limited on-site collection of dead wood for campfires; making the area available for livestock grazing subject to certain timing and management systems; prohibiting camping if cultural, wildlife, and natural processes are negatively impacted; and designating access trails to cultural sites as necessary to protect cultural resources.</P>
                <P>• Shay Canyon ACEC—approximately 119 acres. Designation proposed to protect cultural and paleontological resources. Identified special management would include retaining the existing visual character of the landscape in a manner where authorized changes do not attract the attention of the casual observer (VRM Class II); prohibiting permitted/personal use of woodland products; limiting livestock grazing to trailing only; prohibiting campfires, camping, and off-trail hiking; prohibiting Special Recreation Permits (SRP) for competitive events, vending, and motorized, mechanized, and equestrian use; limiting SRP group size to 35 individuals; limiting SRPs to day use only; limiting recreation use if cultural and paleontological resources are negatively impacted; and prohibiting surface disturbing activities for vegetation, watershed, or wildlife treatments/improvements.</P>
                <P>
                    • Lavender Mesa ACEC—approximately 649 acres. Designation proposed to protect vegetation resources. Identified special management would include retaining the existing visual character of the landscape in a manner where authorized changes do not attract the attention of the casual observer (VRM Class II); avoiding ROWs; closing the area to OHV use and restricting helicopter access; prohibiting permitted/personal use of woodland products; making the area unavailable for livestock grazing; prohibiting campfires; and protecting vegetation for science and research purposes by limiting land treatments and other improvements (including wildlife habitat improvements and watershed control structures).
                    <PRTPAGE P="18430"/>
                </P>
                <P>• Valley of the Gods ACEC—approximately 22,716 acres. Designation proposed to protect scenic resources. Identified special management would include preserving the natural visual character of the landscape (VRM Class I) (except on 57 acres of highway access portals); excluding ROWs; prohibiting permitted/personal use of woodland products; and prohibiting campfires.</P>
                <P>• Indian Creek ACEC—approximately 3,936 acres. Designation proposed to protect scenic resources. Identified special management would include preserving the natural visual character of the landscape (VRM Class I); avoiding ROWs; closing the area to OHV use; prohibiting permitted/personal use of woodland products, except for limited on-site collection of dead wood for campfires; and revegetating with native species where feasible.</P>
                <P>• John's Canyon Paleontological ACEC—approximately 11,465 acres. Designation proposed to protect paleontological, cultural, and scenic resources; fish and wildlife; and threatened species. Identified special management would include retaining the existing visual character of the landscape in a manner where authorized changes do not attract the attention of the casual observer (VRM Class II); excluding ROWs; and limiting discretionary actions to those necessary to protect BENM objects.</P>
                <P>• Aquifer Protection Area ACEC—approximately 85,856 acres. Designation proposed to protect natural systems/aquifer recharge areas, and scenic, cultural, and paleontological resources. Identified special management would include managing discretionary uses to avoid adversely impacting vegetation communities and ground-water dependent ecosystems; preserving the natural visual character of the landscape in some portions of the ACEC (VRM Class I) and retaining the existing visual character of the landscape in other portions of the ACEC in a manner where authorized changes do not attract the attention of the casual observer (VRM Class II); and requiring hydrologic studies for groundwater withdrawals.</P>
                <P>All nominated ACECs are proposed for designation in the preferred alternative.</P>
                <HD SOURCE="HD1">Dingell Act Proposed Recreational Shooting Closures</HD>
                <P>
                    In accordance with the John D. Dingell, Jr. Conservation, Management, and Recreation Act of 2019 (Dingell Act, Pub. L. 116-9, Section 4103), the Agencies are announcing the opening of a 90-day public comment period on the proposed recreational shooting closures within the Monument. The preferred alternative would close the entire Monument—approximately 1.36 million acres—to recreational shooting to protect BENM objects, whereas the other alternatives would close portions of the Monument to recreational shooting. Comments may be submitted using any of the methods listed in the 
                    <E T="02">ADDRESSES</E>
                     section earlier.
                </P>
                <HD SOURCE="HD1">Schedule for the Decision-Making Process</HD>
                <P>Following this comment period, the Agencies will provide additional opportunities for public participation consistent with the NEPA and land use planning processes, including a 30-day public protest period and a 60-day Governor's consistency review on the Proposed RMP. The Proposed RMP/Final EIS is anticipated to be available for public protest in October 2024 with an Approved RMP and Records of Decision in January 2025. In accordance with 36 CFR 219.59(a), the USDA Forest Service will waive its objections procedures and adopt the BLM's protest procedures.</P>
                <P>The Agencies will continue to consult with Indian Tribal Nations on a government-to-government basis in accordance with Executive Order 13175, BLM Manual Section 1780, and other Departmental policies. Tribal concerns, including impacts on Indian trust assets and potential impacts to cultural resources, will be given due consideration. The Agencies will also continue to meaningfully engage with the Bears Ears Commission, as required by Proclamation 10285.</P>
                <P>
                    You may submit comments on the Draft RMP/EIS in writing to the Agencies at any public meetings or to the Agencies using one of the methods listed in the 
                    <E T="02">ADDRESSES</E>
                     section. To be considered, comments must be received by the end of the 90-day comment period. The ePlanning website (see 
                    <E T="02">ADDRESSES</E>
                    ) includes background information on BENM and the planning process.
                </P>
                <P>Before including your address, phone number, email address, or other personal identifying information in your comment, you should be aware 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>
                <EXTRACT>
                    <FP>(Authority: 16 U.S.C. 7913, 36 CFR 219.16, 36 CFR 219.59, 40 CFR 1506.6, 40 CFR 1506.10, 43 CFR 1610.2, 43 CFR 1610.7-2).</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Gregory Sheehan,</NAME>
                    <TITLE>State Director.</TITLE>
                    <NAME>Barbara Van Alstine,</NAME>
                    <TITLE>Manti-La Sal Forest Supervisor (Acting).</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05203 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4331-25-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Land Management</SUBAGY>
                <DEPDOC>[LLCO923000.14400000.ET0000.223; COC-080735]</DEPDOC>
                <SUBJECT>Notice of Application for Permanent Withdrawal and Transfer of Jurisdiction, Colorado</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of withdrawal application.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Energy, Office of Legacy Management (DOE-LM) has filed an application with the Bureau of Land Management (BLM) requesting that the Secretary of the Interior exercise authority under Title II of the Uranium Mill Tailings Radiation Control Act of 1978 (UMTRCA) to permanently withdraw and transfer administrative jurisdiction over 70 acres of public lands at the Durita Mill Tailings Site in Colorado to DOE-LM. The public land and interests in the land would be withdrawn from operation of the general land laws, including the United States mining laws, the mineral and geothermal leasing laws, and the mineral materials disposal laws, subject to valid existing rights, and would be transferred to DOE-LM for long term maintenance and monitoring under a Nuclear Regulatory Commission license as part of the Durita Mill Tailings Site. This notice announces a 30-day opportunity for the public to comment on the DOE-LM application and request a public meeting.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments and meeting requests must be received on or before April 12, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments and meeting requests should be sent to BLM Colorado State Director, BLM Colorado State Office, P.O. Box 151029, Lakewood, CO 80215.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jennifer Jardine, Realty Specialist, BLM Colorado State Office, telephone: (970) 385-1224, email: 
                        <E T="03">jjardine@blm.gov</E>
                         during regular business hours 8:00 a.m. 
                        <PRTPAGE P="18431"/>
                        to 4:30 p.m., Monday through Friday, except holidays. 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 for contacting Ms. Jardine. 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>DOE-LM filed an application with the BLM that requests the Secretary of the Interior to permanently withdraw and transfer administrative jurisdiction over the following described public lands and federally owned minerals, subject to valid existing rights. DOE-LM has requested that the land and minerals be withdrawn from location and entry under the United States mining laws, from leasing under the mineral or geothermal leasing laws, and from disposal under the mineral materials laws, subject to valid existing rights. Under UMTRCA, as amended by the Uranium Mill Tailings Remedial Action Amendments Act of 1988 (42 U.S.C. 7916), the Secretary of the Interior may make such permanent withdrawals and transfers of administrative jurisdiction. The Secretary's actions under UMTRCA are explicitly exempt from the withdrawal and transfer provisions of Section 204 of the Federal Land Policy and Management Act of 1976, as amended. The following public lands are requested for permanent withdrawal and jurisdictional transfer for long term maintenance and monitoring by the DOE-LM under applicable provisions of UMTRCA:</P>
                <HD SOURCE="HD1">New Mexico Principal Meridian, Colorado</HD>
                <FP SOURCE="FP-2">T. 46 N., R. 16 W.,</FP>
                <FP SOURCE="FP1-2">
                    sec. 34, E
                    <FR>1/2</FR>
                    NE
                    <FR>1/4</FR>
                    NE
                    <FR>1/4</FR>
                    SW
                    <FR>1/4</FR>
                    , E
                    <FR>1/2</FR>
                    SE
                    <FR>1/4</FR>
                    NE
                    <FR>1/4</FR>
                    SW
                    <FR>1/4</FR>
                    , E
                    <FR>1/2</FR>
                    NE
                    <FR>1/4</FR>
                    SE
                    <FR>1/4</FR>
                    SW
                    <FR>1/4</FR>
                    , N
                    <FR>1/2</FR>
                    SW
                    <FR>1/4</FR>
                    SE
                    <FR>1/4</FR>
                    , and N
                    <FR>1/2</FR>
                    SE
                    <FR>1/4</FR>
                    SE
                    <FR>1/4</FR>
                    ;
                </FP>
                <FP SOURCE="FP1-2">
                    sec. 35, W
                    <FR>1/2</FR>
                    NW
                    <FR>1/4</FR>
                    NW
                    <FR>1/4</FR>
                    SW
                    <FR>1/4</FR>
                    , W
                    <FR>1/2</FR>
                    SW
                    <FR>1/4</FR>
                    NW
                    <FR>1/4</FR>
                    SW
                    <FR>1/4</FR>
                    , and W
                    <FR>1/2</FR>
                    NW
                    <FR>1/4</FR>
                    SW
                    <FR>1/4</FR>
                    SW
                    <FR>1/4</FR>
                    .
                </FP>
                <P>The area described contains 70 acres of public lands, according to the official plat of the survey of the said land on file with the BLM.</P>
                <P>
                    The purpose of the requested withdrawal and transfer of administrative jurisdiction is to allow the DOE-LM to administer the lands in perpetuity as a hazardous material site under the authority of UMTRCA, 42 U.S.C. 7902 
                    <E T="03">et seq.</E>
                </P>
                <P>
                    For a period until April 12, 2024, all persons who wish to submit comments, suggestions, or objections in connection with the DOE-LM application may present their views in writing to the BLM Colorado State Office at the address listed in the 
                    <E T="02">ADDRESSES</E>
                     section above. Records related to the applications may be examined by contacting the BLM Colorado State Office at the address listed in the 
                    <E T="02">ADDRESSES</E>
                    ; section above. The BLM is preparing an environmental assessment under the National Environmental Policy Act in connection with the requested withdrawal and jurisdictional transfer. On March 22, 2022, the BLM posted a project description for DOI-BLM-CO-S050-2022-0013-EA on its e-Planning site at 
                    <E T="03">eplanning.blm.gov/eplanning-ui/project/2018643/510.</E>
                </P>
                <P>Comments will be available for public review at the BLM Colorado State Office during regular business hours, 8:00 a.m. to 4:30 p.m. Monday through Friday, except Federal holidays. 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>
                <EXTRACT>
                    <FP>(Authority: 42 U.S.C. 7916)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Douglas J. Vilsack,</NAME>
                    <TITLE>BLM Colorado State Director.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05341 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6450-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[USITC SE-24-012]</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>March 21, 2024 at 11:00 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>
                        1. 
                        <E T="03">Agendas for future meetings:</E>
                         none.
                    </P>
                    <P>2. Minutes.</P>
                    <P>3. Ratification List.</P>
                    <P>4. Commission vote on Inv. No. 731-TA-1203 (Review) (Xanthan Gum from China). The Commission currently is scheduled to complete and file its determination and views of the Commission on April 1, 2024.</P>
                    <P>
                        5. 
                        <E T="03">Outstanding action jackets:</E>
                         none.
                    </P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION:</HD>
                    <P>Sharon Bellamy, Supervisory Hearings and Information Officer, 202-205-2000.</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: March 11, 2024.</DATED>
                    <NAME>Sharon Bellamy,</NAME>
                    <TITLE>Supervisory Hearings and Information Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05484 Filed 3-11-24; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[Investigation No. 337-TA-1292]</DEPDOC>
                <SUBJECT>Certain Replacement Automotive Lamps II; 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>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 January 24, 2022, the Commission instituted this investigation under 
                    <PRTPAGE P="18432"/>
                    section 337 of the Tariff Act of 1930, as amended, 19 U.S.C. 1337 (“section 337”), based on a complaint filed by Hyundai Motor Company of Seoul, Republic of Korea and Hyundai Motor America, Inc. of Fountain Valley, CA (collectively, “Hyundai”). 
                    <E T="03">See</E>
                     87 FR 3583-84 (Jan. 24, 2022). The complaint 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 replacement automotive lamps by reason of infringement of certain claims of U.S. Design Patent Nos. D617,478; D618,835; D618,836; D631,583; D637,319; D640,812; D655,835; D664,690; D709,217; D736,436; D738,003; D739,057; D739,574; D740,980; D759,864; D759,865; D771,292; D780,351; D818,163; D829,947; and D834,225 (collectively, “Asserted Patents”). 
                    <E T="03">Id.</E>
                     The complaint further alleges that a domestic industry exists. 
                    <E T="03">Id.</E>
                     The notice of investigation names four respondents: (1) TYC Brother Industrial Co., Ltd. of Tainan, Taiwan; (2) Genera Corporation (dba. TYC Genera) of Brea, California; (3) LKQ Corporation of Chicago, Illinois; and (4) Keystone Automotive Industries, Inc. of Exeter, Pennsylvania (collectively, “Respondents”). 
                    <E T="03">Id.</E>
                     The Office of Unfair Import Investigations is not named as a party.
                </P>
                <P>
                    On February 7, 2022, the Chief Administrative Law Judge (“CALJ”) ordered an evidentiary hearing for both Inv. Nos. 337-TA-1291 and 337-TA-1292 on the economic prong of the domestic industry requirement pursuant to the Commission's pilot program for interim initial determinations (“IID”). 
                    <E T="03">See</E>
                     Order No. 7 (Feb. 7, 2022). The combined evidentiary hearing was held on April 20, 2022. On July 1, 2022, the CALJ issued an IID finding that Hyundai has satisfied the economic prong of the domestic industry requirement with respect to all of the asserted design patents. On August 24, 2022, the Commission determined to review the IID. 
                    <E T="03">See</E>
                     Comm'n Notice (Aug. 24, 2022).
                </P>
                <P>On January 24, 2023, the CALJ issued a final initial determination (“FID”) finding a violation of section 337 by Respondents based on infringement of each of the Asserted Patents. The FID also finds that no Asserted Patent is invalid as anticipated or obvious. The FID further finds that Hyundai has satisfied the technical prong as to certain representative domestic industry products. Concerning the economic prong of the domestic industry requirement, the FID reduces Hyundai's alleged investments due to Hyundai's failure to establish that certain of its alleged domestic industry products are representative of other alleged domestic industry products. The FID finds, however, that the economic prong of the domestic industry requirement is satisfied for all of the Asserted Patents based on the reduced investments. The CALJ also simultaneously issued a recommended determination on remedy and bonding (“RD”) recommending that, if the Commission finds a violation, it should issue a limited exclusion order but not issue any cease and desist order against any of Respondents.</P>
                <P>On February 6, 2023, Respondents filed a petition for review challenging the FID's findings on the economic prong of the domestic industry requirement, infringement, and validity. Also on February 6, 2023, Hyundai filed a petition for review challenging the RD's recommendations and contingently petitioning regarding the FID's findings concerning non-satisfaction of the technical prong of the domestic industry requirement for certain non-representative products. On February 14, 2023, Respondents and Hyundai filed responses to each other's petitions.</P>
                <P>On February 23, 2023, the Commission received public interest submissions pursuant to Commission Rule 210.50(a)(4) from the LKQ Respondents and the TYC Respondents. 19 CFR 210.50(a)(4). On February 22 and 23, 2023, the Commission received twelve responses to the Commission notice seeking public interest submission. 88 FR 7759-7760 (Feb. 6, 2023).</P>
                <P>
                    On May 11, 2023, the Commission determined to review the FID in its entirety. 88 FR 31522-24 (May 17,2023). The Commission asked the parties to address four questions, which related to infringement, the technical prong of the domestic industry requirement, and the economic prong of the domestic industry requirement. 
                    <E T="03">Id.</E>
                     The Commission also requested briefing from the parties, interested government agencies, and the public concerning remedy, bonding, and the public interest. 
                    <E T="03">Id.</E>
                </P>
                <P>On May 25, 2023, Hyundai and Respondents filed their initial written responses to the Commission's request for briefing. On June 1, 2023, Hyundai and Respondents filed their reply submission.</P>
                <P>On June 15, 2023, Respondents filed a motion to strike a declaration filed with the Hyundai reply submission. On June 26, 2023, Hyundai filed an opposition to the motion to strike.</P>
                <P>Having reviewed the record of the investigation, including the IID, the FID, and the parties' petitions, responses, and other submissions, the Commission has determined to find no violation of section 337 with respect to the Asserted Patents. Specifically, the Commission has determined to vacate the IID and the FID's economic prong findings and find that Hyundai has failed to satisfy the economic prong of the domestic industry requirement with respect to any of the Asserted Patents. The Commission has further determined to take no position on the issues of infringement, satisfaction of the technical prong of the domestic industry requirement, and invalidity. The Commission further finds that Respondents' motion to strike the declaration filed with Hyundai's reply submission is moot in view of the finding that there is no violation of section 337 and the public interest factors do not need to be addressed.</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.</P>
                <P>Commissioner Schmidtlein does not join the majority's opinion but agrees that Hyundai has failed to establish the economic prong of the domestic industry requirement for any of the Asserted Patents. She therefore agrees that there has been no violation of section 337 in this investigation. She explains her views in a concurring opinion.</P>
                <P>The Commission vote for this determination took place on March 7, 2024.</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: March 7, 2024.</DATED>
                    <NAME>Katherine Hiner,</NAME>
                    <TITLE>Supervisory Attorney.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05273 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18433"/>
                <AGENCY TYPE="S">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[Investigation No. 337-TA-1346]</DEPDOC>
                <SUBJECT>Certain Marine Air Conditioning Systems, Components Thereof, and Products Containing the Same; Notice of a Commission Determination To Review in Part and, on Review, To Affirm With Modification a Final Initial Determination Finding No Violation; Termination of Investigation</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>International Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given that the U.S. International Trade Commission has determined to review in part and, on review, to affirm with modification a final initial determination (“FID”) of the presiding administrative law judge (“ALJ”). The investigation is terminated.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Namo Kim, Esq., Office of the General Counsel, U.S. International Trade Commission, 500 E Street SW, Washington, DC 20436, telephone (202) 205-3459. 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>
                    On December 7, 2022, the Commission instituted this investigation based on a complaint, as supplemented, filed by Dometic Corporation of Rosemont, Illinois and Dometic Sweden AB of Solna, Sweden (collectively, “Dometic”). 87 FR 76216-17 (Dec. 13, 2022). The complaint alleges violations of section 337 of the Tariff Act of 1930, as amended, 19 U.S.C. 1337 (“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 marine air conditioning systems, components thereof, and products containing same by reason of the infringement of certain claims of U.S. Patent No. 8,056,351 (“the '351 patent”). 
                    <E T="03">Id.</E>
                     The complaint further alleges that a domestic industry (“DI”) exists. 
                    <E T="03">Id.</E>
                     The notice of institution named four (4) respondents: (1) Shanghai Hopewell Industrial Co. Ltd. of Shanghai, China; (2) Shanghai Hehe Industrial Co. Ltd. of Shanghai, China; (3) CitiMarine, L.L.C. of Doral, Florida; and (4) Mabru Power Systems, Inc. of Dania Beach, Florida (collectively, “Respondents”). 
                    <E T="03">Id.</E>
                </P>
                <P>
                    On August 28, 2023, the Commission granted in part summary determination that the economic prong of the DI requirement is satisfied. Order No. 23, 
                    <E T="03">unreviewed by</E>
                     Comm'n Notice (Aug. 28, 2023).
                </P>
                <P>
                    On September 13, 2023, the Commission affirmed an initial determination granting in part summary determination of invalidity of claims 1-2, 4-5, 7 of the '351 patent. Order No. 19, 
                    <E T="03">aff'd by</E>
                     Comm'n Notice (September 13, 2023).
                </P>
                <P>The presiding ALJ held an evidentiary hearing on September 18-21, 2023.</P>
                <P>
                    On October 31, 2023, the Commission affirmed an initial determination terminating the investigation with respect to claims 3, 11 and 17 of the '351 patent. Order No. 30, 
                    <E T="03">unreviewed by</E>
                     Comm'n Notice (October 31, 2023). Accordingly, at the time the FID was issued, claims 18-22 of the '351 patent remained pending.
                </P>
                <P>On December 8, 2023, the ALJ issued the FID finding no violation of section 337. Specifically, the FID finds that Dometic failed to show infringement or to satisfy the technical prong of the DI requirement because “the DI Products do not possess two axes” as required by the remaining asserted claims under the FID's claim construction. Despite finding no infringement, the ALJ conducted an independent analysis of the accused products beyond the infringement theories presented by Dometic and determined that some accused products satisfy all limitations of the asserted claims. Lastly, the FID finds that all remaining asserted claims are valid.</P>
                <P>The FID also includes a Recommended Determination (“RD”) recommending, should the Commission find a violation of section 337, that the Commission issue: (1) a limited exclusion order with the Commission's standard certification provision, which does not identify non-infringing articles as requested by the respondents; and (2) a cease-and-desist order against any respondent found to be in violation. The RD further recommends that the Commission set no bond (zero percent) during the period of Presidential review.</P>
                <P>On December 22, 2023, both parties (Dometic and Respondents) petitioned for Commission review of FID's findings. Specifically, Dometic requests Commission review of the FID's findings concerning: (1) claim construction; (2) non-infringement; (3) the technical prong of the DI requirement; and (4) validity of the asserted claims concerning the claim construction and secondary considerations. Respondents request Commission review of the FID's findings concerning: (1) the technical prong; (2) certain factual findings related to infringement; (3) excluding Respondents' failure of proof arguments related to infringement; and (4) validity, in particular whether a certain product qualifies as prior art and whether the ALJ abused his discretion by excluding a certain prior art exhibit. Respondents also request contingent review of the following issues: (1) claim construction and (2) validity.</P>
                <P>
                    On December 27, 2023, the Commission published its post-RD 
                    <E T="04">Federal Register</E>
                     notice seeking submissions on public interest issues raised by the relief recommended by the ALJ should the Commission find a violation. 88 FR 89466-67 (Dec. 27, 2023). No responses were filed from the public.
                </P>
                <P>On January 4, 2024, both parties (Dometic and Respondents) responded to each other's petition for review of the FID.</P>
                <P>On January 9, 2024, both parties (Dometic and Respondents) filed a statement on the public interest pursuant to Commission Rule 210.50(a)(4), 19 CFR 210.50(a)(4).</P>
                <P>
                    The Commission, having reviewed the record in this investigation, including the FID and the parties' petitions and responses thereto, has determined to review in part and, on review, to affirm with modification the FID's finding of no violation. In particular, the Commission reviews and, on review, supplements with supporting extrinsic evidence the FID's construction of the claim limitation “the blower being rotatable about [a] first axis so that the outlet can be oriented toward a first direct[i]on and a second direction, and the first and second directions point to substantially different lateral sides of the main body” recited in claim 18 of the '351 patent. The Commission has also determined to review the FID's findings concerning infringement and the technical prong of the DI requirement and, on review, to affirm the FID's finding of non-infringement and non-satisfaction of the technical prong, but to vacate the ALJ's independent findings that some of the accused products (
                    <E T="03">i.e.,</E>
                     Mabru SC07, which represents all Mabru accused products) satisfy all limitations of the asserted claims, as well as the ALJ's independent technical prong findings on the DI products. The Commission 
                    <PRTPAGE P="18434"/>
                    has further determined to review and, on review, to take no position on certain of the FID's invalidity findings and the findings that certain accused products satisfy a dependent claim limitation of the '351 patent. The Commission has determined not to review the remainder of the FID.
                </P>
                <P>The Commission issues its opinion herewith setting forth its determinations on certain issues. The investigation is terminated.</P>
                <P>The Commission vote for this determination took place on March 7, 2024.</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: March 7, 2024.</DATED>
                    <NAME>Katherine Hiner,</NAME>
                    <TITLE>Supervisory Attorney.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05274 Filed 3-12-24; 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-1291]</DEPDOC>
                <SUBJECT>Certain Replacement Automotive Lamps; 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>International Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given that the U.S. International Trade Commission has determined that complainants Kia Corporation and Kia America, Inc. failed to demonstrate a violation of section 337 of the Tariff Act of 1930, as amended, by any of the named respondents in the above-captioned investigation. The investigation is terminated.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Robert Needham, Office of the General Counsel, U.S. International Trade Commission, 500 E Street SW, Washington, DC 20436, telephone (202) 708-5468. 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 (
                        <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>
                    On January 24, 2022, 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 on behalf of complainants Kia Corporation of Seoul, Korea and Kia America, Inc. of Irvine, California (collectively, “Kia”). 87 FR 3584-85 (Jan. 24, 2022). The complaint, as supplemented and amended, alleges a violation of section 337 in the importation into the United States, the sale for importation, and the sale after importation within the United States after importation of certain replacement automotive lamps by reason of infringement of U.S. Design Patent Nos. D592,773 (the “'773 patent”); D635,701 (the “'701 patent”); D636,506 (the “'506 patent”); D650,931 (the “'931 patent”); D695,933 (the “'933 patent”); D705,963 (the “'963 patent”); D709,218 (the “'218 patent”); D714,975 (the “'975 patent”); D714,976 (the “'976 patent”); D720,871 (the “'871 patent”); D749,757 (the “'757 patent”); D749,762 (the “'762 patent”); D749,764 (the “'764 patent”); D774,222 (the “'222 patent”); D774,223 (the “'223 patent”); D776,311 (the “'311 patent”); D781,471 (the “'471 patent”); D785,833 (the “'833 patent”); D785,836 (the “'836 patent”); and D792,989 (the “'989 patent”) (together, “Asserted Patents”). 
                    <E T="03">Id.</E>
                     at 3584. The notice of investigation names as respondents TYC Brother Industrial Co., Ltd. of Tainan, Taiwan; Genera Corporation (dba TYC Genera) of Brea, California; LKQ Corporation of Chicago, Illinois; and Keystone Automotive Industries, Inc. of Exeter, Pennsylvania (together, “Respondents”). The Office of Unfair Import Investigations is not participating in this investigation.
                </P>
                <P>On February 7, 2022, the Chief ALJ (“CALJ”) ordered an evidentiary hearing for both Inv. Nos. 337-TA-1291 and 337-TA-1292 on the economic prong pursuant to the Commission's pilot program for interim initial determinations (“IID”). Order No. 6 (Feb. 7, 2022). The combined evidentiary hearing was held on April 20, 2022. On July 1, 2022, the CALJ issued an IID finding that Kia has satisfied the economic prong of the domestic industry requirement with respect to all of the asserted design patents. On August 24, 2022, the Commission determined to review the IID. Notice (Aug. 24, 2022). The investigation was reassigned to the presiding ALJ on July 6, 2022.</P>
                <P>
                    On January 24, 2023, the presiding ALJ issued a final initial determination (“Final ID”) finding a violation of section 337 by Respondents with respect to the '773, '701, '506, '931, '933, '218, '975, '976, '871, '762, '764, '222, '223, '311, '833, '836, and '989 patents. Final ID at 1. The Final ID finds no violation with respect to the '963, '757, and '471 patents based on noninfringement and failure to satisfy the technical prong of the domestic industry requirement. 
                    <E T="03">Id.</E>
                     at 1, 284-86. The Final ID also finds that no asserted patent is invalid as anticipated or obvious. 
                    <E T="03">Id.</E>
                     Concerning the economic prong of the domestic industry requirement, the Final ID reduced Kia's alleged investments due to Kia's failure to establish that certain of its alleged domestic industry products are representative of other alleged domestic industry products, but finds that the economic prong of domestic industry requirement is satisfied for all of the Asserted Patents. 
                    <E T="03">Id.</E>
                     at 33-37.
                </P>
                <P>On February 6, 2023, Respondents filed a petition for review challenging the Final ID's findings on the economic prong of the domestic industry requirement, infringement, and validity. Also on February 6, 2023, Kia filed a petition for review challenging the Final ID's findings of noninfringement and contingently petitioning regarding the Final ID's findings concerning non-satisfaction of the technical prong of the domestic industry requirement regarding the '963, '757, and '471 patents. On February 14, 2023, Kia and Respondents filed responses to each other's petitions.</P>
                <P>On January 25, 2023, the Commission requested submissions regarding the public interest. 88 FR 5919-20 (Jan. 30, 2023). The Commission received submissions from Thomas Lee, Dennis Shiau, Peter Nguyen, John Chang, Raymond Tsai, Christopher Patti, Edward Salamy, Paul Tetrault, Clark Plucinski, Gay Gordon-Byrne, the Alliance for Automotive Innovation, and Gregory Cote. On February 23, 2023, the Commission also received submissions on the public interest from Respondents pursuant to Commission Rule 210.50(a)(4). 19 CFR 210.50(a)(4).</P>
                <P>
                    On May 11, 2023, the Commission determined to review the Final ID in its entirety and sought briefing from the parties on certain issues and briefing from the parties, interested government agencies, and the public concerning remedy, bonding, and the public interest. 88 FR 31520-22 (May 17, 2023). Kia and Respondents filed initial 
                    <PRTPAGE P="18435"/>
                    submissions on May 25, 2023, and reply submissions on June 1, 2023.
                </P>
                <P>On June 15, 2023, Respondents moved to strike a declaration of Brian Sciumbato, who testified regarding the public interest factors.</P>
                <P>Having examined the record of this investigation, including the IID, the Final ID, the petitions, responses, and other submissions from the parties and the public, the Commission has determined to vacate the IID and the Final ID's economic prong findings and find that Kia has failed to satisfy the economic prong of the domestic industry requirement with respect to any of the Asserted Patents. The Commission has further determined to take no position on the issues of infringement, satisfaction of the technical prong of the domestic industry requirement, and invalidity. The Commission also denies Respondents' motion to strike the Sciumbato declaration as moot.</P>
                <P>The Commission's determinations are explained more fully in the accompanying Opinion. All other findings in the ID under review that are consistent with the Commission's determinations are affirmed. The investigation is hereby terminated.</P>
                <P>Commissioner Schmidtlein does not join the majority's opinion but agrees that Kia has failed to establish the economic prong of the domestic industry requirement for any of the Asserted Patents. She therefore agrees that there has been no violation of section 337 in this investigation. She explains her views in a concurring opinion.</P>
                <P>The Commission vote for this determination took place on March 7, 2024.</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: March 7, 2024.</DATED>
                    <NAME>Katherine Hiner,</NAME>
                    <TITLE>Supervisory Attorney.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05272 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[Investigation No. TA-201-078]</DEPDOC>
                <SUBJECT>Fine Denier Polyester Staple Fiber; Institution of Investigation, Scheduling of Public Hearings, and Determination That the Investigation Is Extraordinarily Complicated</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>United States International Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of institution of investigation and scheduling of public hearings.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Following receipt of a petition for import relief, as filed on February 28, 2024, the Commission has instituted investigation No. TA-201-078 pursuant to section 202 of the Trade Act of 1974 (“the Act”) to determine whether fine denier polyester staple fiber (“fine denier PSF”) is being imported into the United States in such increased quantities as to be a substantial cause of serious injury, or the threat thereof, to the domestic industry producing an article like or directly competitive with the imported article. The Commission has deemed the petition to have been filed on February 28, 2024. The Commission has determined that this investigation is “extraordinarily complicated,” and will make its injury determination by July 9, 2024. The Commission will submit to the President the report required under section 202(f) of the Act within 180 days after the date on which the petition was filed, or by August 26, 2024.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable February 28, 2024.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kristina Lara (202-205-3386), Office of Investigations, U.S. International Trade Commission, 500 E Street SW, Washington, DC 20436. Hearing-impaired persons can obtain information on this matter 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 (
                        <E T="03">https://www.usitc.gov</E>
                        ). The public record for this investigation may be viewed on the Commission's electronic docket (EDIS) at 
                        <E T="03">https://edis.usitc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>Background.—This investigation is being instituted, pursuant to section 202 of the Act (19 U.S.C. 2252), in response to a petition, as filed on February 28, 2024, by Fiber Industries LLC d/b/a Darling Fibers (“Darling”), Nan Ya Plastics Corp, America (“Nan Ya”), and Sun Fiber LLC (“Sun Fiber”), producers of fine denier PSF in the United States. Darling, Nan Ya, and Sun Fiber allege that fine denier PSF is being imported into the United States in such increased quantities as to be a substantial cause of serious injury, and the threat thereof, to the domestic industry producing an article like or directly competitive with the imported article. The Commission must submit its report on this investigation to the President no later than 180 days after institution, which in this case falls on August 26, 2024. (19 U.S.C. 2252(f)).</P>
                <P>The imported article covered by this investigation is fine denier PSF, not carded or combed, measuring less than 3.3 decitex (3 denier) in diameter. The scope covers all fine denier PSF, whether coated or uncoated. The following products are not covered by this investigation:</P>
                <P>(1) PSF equal to or greater than 3.3 decitex (more than 3 denier, inclusive) currently imported under HTSUS statistical reporting numbers 5503.20.0045 and 5503.20.0065.</P>
                <P>(2) Low-melt PSF defined as a bicomponent polyester fiber having a polyester fiber component that melts at a lower temperature than the other polyester fiber component, which is currently imported under HTSUS statistical reporting number 5503.20.0015.</P>
                <P>For Customs purposes, the fine denier PSF covered by the investigation is provided for under Harmonized Tariff Schedule of the United States (“HTSUS”) subheading 5503.20.0025. These HTSUS numbers are provided for convenience and the written description of the scope is dispositive.</P>
                <P>
                    Determination that investigation is extraordinarily complicated.—The Commission has determined that this investigation is “extraordinarily complicated” within the meaning of section 202(b)(2)(B) of the Act (19 U.S.C. 2252(b)(2)(B)). The Commission's decision to designate this investigation “extraordinarily complicated” is based on the complexity of the issues, including the existence of antidumping and countervailing duty orders on certain imports covered by this investigation. Ordinarily, the Commission would have been required to make its injury determination within 120 days after the petition was filed, or by June 27, 2024. (19 U.S.C. 2252 (b)(2)(A)). The statute permits the Commission to take up to 30 additional days to make its injury determination in an investigation where it determines that the investigation is extraordinarily 
                    <PRTPAGE P="18436"/>
                    complicated. In this instance, the Commission intends to take additional days and make its injury determination by July 9, 2024.
                </P>
                <P>
                    Participation in the investigation and public service list.—Persons (other than petitioners) wishing to participate in the investigation as parties must file an entry of appearance with the Secretary to the Commission, as provided in section 201.11 of the Commission's rules, not later than 21 days after publication of this notice in the 
                    <E T="04">Federal Register</E>
                    . The Secretary will prepare a service list containing the names and addresses of all persons, or their representatives, who are parties to this investigation upon the expiration of the period for filing entries of appearance. 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.
                </P>
                <P>
                    Limited disclosure of confidential business information (CBI) under an administrative protective order (APO) and CBI service list.—Pursuant to section 206.17 of the Commission's rules, the Secretary will make CBI gathered in this investigation available to authorized applicants representing interested parties (as defined in 19 CFR 206.17(a)(3)(iii)) under the APO issued in the investigation, provided that the application is made not later than 21 days after the publication of this notice in the 
                    <E T="04">Federal Register</E>
                    . A separate service list will be maintained by the Secretary for those parties authorized to receive CBI under the APO.
                </P>
                <P>The Commission may transmit CBI to the Office of the United States Trade Representative (USTR) and may include CBI in the report it sends to the President and USTR for use in decision-making related to this proceeding. Additionally, all information, including CBI, submitted in this investigation may be disclosed to and used by (i) 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 for cybersecurity purposes. The Commission will not otherwise disclose any CBI in a manner that would reveal the operations of the firm supplying the information.</P>
                <P>Hearings on injury and remedy.—The Commission has scheduled separate hearings in connection with the injury and remedy phases of this investigation. The hearing on injury will be held beginning at 9:30 a.m. on June 4, 2024, at the U.S. International Trade Commission Building, 500 E Street SW, Washington, DC. In the event that the Commission makes an affirmative injury determination or is equally divided on the question of injury in this investigation, a hearing on the question of remedy will be held beginning at 9:30 a.m. on July 23, 2024. Requests to appear at the hearings should be filed in writing with the Secretary to the Commission on or before May 24, 2024, for the injury hearing, and July 17, 2024, for the remedy hearing. A nonparty who has testimony that may aid the Commission's deliberations may request permission to present a short statement at the hearings.</P>
                <P>All parties and nonparties desiring to appear at the hearings and make oral presentations should participate in prehearing conferences to be held on May 31, 2024, for the injury hearing and July 19, 2024, for the remedy hearing, if deemed necessary. Parties shall file and serve written testimony and presentation slides in connection with their presentation at the hearing by no later than 4 p.m. on the business day prior to the hearing. Oral testimony and written materials to be submitted at the public hearings are governed by sections 201.6(b)(2) 201.13(f), and 206.5 of the Commission's rules. Parties must submit any request to present a portion of their hearing testimony in camera no later than 7 business days prior to the date of the respective hearings.</P>
                <P>
                    Any requests to appear as a witness via videoconference must be included with your request to appear. Requests to appear via videoconference must include a statement explaining why the witness cannot appear in person; the Chairman, or other person designated to conduct the investigations, may in their discretion for good cause shown, grant such a request. Requests to appear as remote witness due to illness or a positive COVID-19 test result may be submitted by 3 p.m. the business day prior to the hearing. Further information about participation in the hearing will be posted on the Commission's website at 
                    <E T="03">https://www.usitc.gov/calendarpad/calendar.html.</E>
                </P>
                <P>Written submissions.—Each party who is an interested party may submit a prehearing brief to the Commission. Prehearing briefs must conform with the provisions of sections 201.8, 206.7, and 206.8 of the Commission's rules. The deadline for filing prehearing briefs on injury is May 28, 2024; that for filing prehearing briefs on remedy, including any commitments pursuant to 19 U.S.C. 2252(a)(6)(B), is July 16, 2024. Parties may also file written testimony in connection with their presentation at the hearing, as provided in sections 201.13, 206.5, and 206.8 of the Commission's rules, and posthearing briefs, which must conform with the provisions of sections 201.8, 201.13, 206.7, and 206.8 of Commission's rules. The deadline for filing posthearing briefs for the injury phase of the investigation is June 11, 2024; the deadline for filing posthearing briefs for the remedy phase of the investigation, if any, is July 29, 2024.</P>
                <P>
                    No posthearing brief, either in the injury phase or any remedy phase, shall exceed fifteen (15) pages of textual material, double-spaced and single-sided, when printed out on pages measuring 8.5 x 11 inches. In addition, the presiding official may permit persons to file answers to questions or requests made by the Commission at the hearing for the injury phase, and at any hearing for the remedy phase, within a specified time. In addition, any person who has not entered an appearance as a party to the investigation may submit a written statement of information pertinent to the consideration of injury on or before June 11, 2024, and pertinent to the consideration of remedy on or before July 29, 2024. All written submissions must conform with the provisions of section 201.8 of the Commission's rules; any submissions that contain CBI must also conform with the requirements of sections 201.6 and 206.17 of the Commission's rules. The Commission's Handbook on E-Filing, available on the Commission's website at 
                    <E T="03">https://edis.usitc.gov,</E>
                     elaborates upon the Commission's rules with respect to electronic filing. Any additional written submissions to the Commission, including requests pursuant to section 201.12 of the Commission's rules, will not be accepted unless good cause is shown for accepting such a submission, or unless the submission is pursuant to a specific request by a Commissioner or Commission staff.
                </P>
                <P>In accordance with section 201.16(c) of the Commission's rules, each document filed by a party to the investigation must be served on all other parties to the investigation (as identified by the service list), and a certificate of service must be timely filed. The Secretary will not accept a document for filing without a certificate of service.</P>
                <P>
                    For further information concerning the conduct of this investigation and rules of general application, consult the Commission's Rules of Practice and 
                    <PRTPAGE P="18437"/>
                    Procedure, part 201, subparts A and B (19 CFR part 201), and part 206, subparts A and B (19 CFR part 206).
                </P>
                <P>
                    <E T="03">Authority:</E>
                     This investigation is being conducted under authority of section 202 of the Act; this notice is published pursuant to section 202(b)(3) of the Act.
                </P>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: March 8, 2024.</DATED>
                    <NAME>Katherine Hiner,</NAME>
                    <TITLE>Supervisory Attorney.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05338 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>Notice Pursuant to the National Cooperative Research and Production Act of 1993—ASTM International</SUBJECT>
                <P>
                    Notice is hereby given that, on February 28, 2024, pursuant to section 6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (“the Act”), ASTM International (“ASTM”) has filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing additions or changes to its standards development activities. The notifications were filed for the purpose of extending the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances.
                </P>
                <P>
                    Specifically, ASTM has provided an updated list of current, ongoing ASTM activities originating between December 12, 2023 and February 10, 2024 designated as Work Items. A complete listing of ASTM Work Items, along with a brief description of each, is available at 
                    <E T="03">http://www.astm.org.</E>
                </P>
                <P>
                    On September 15, 2004, ASTM filed its original notification pursuant to section 6(a) of the Act. The Department of Justice published a notice in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on November 10, 2004 (69 FR 65226).
                </P>
                <P>
                    The last notification was filed with the Department on September 26, 2023. A notice was published in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on November 20, 2023 (88 FR 80763).
                </P>
                <SIG>
                    <NAME>Suzanne Morris,</NAME>
                    <TITLE>Deputy Director Civil Enforcement Operations, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05304 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>Notice Pursuant to the National Cooperative Research and Production Act of 1993—Pistoia Alliance, Inc.</SUBJECT>
                <P>
                    Notice is hereby given that, on December 20, 2023, pursuant to section 6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (the “Act”), Pistoia Alliance, Inc. filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing changes in its membership. The notifications were filed for the purpose of extending the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances. Specifically, Blue Hat, London, UNITED KINGDOM; and Amino Data, London, UNITED KINGDOM have been added as parties to the venture.
                </P>
                <P>Also, Binocular Vision Advisors LLC, San Francisco, CA; Pangaea Data, London, UNITED KINGDOM; Qubit Pharmaceuticals, Paris, FRANCE; Molecule One sp.z o.o., Warszawa, POLAND; Vivenics, Oss, NETHERLANDS; A4BEE, Wrocław, POLAND; DeepMatter Limited, Glasgow, UNITED KINGDOM; Gilead Sciences, Foster City, CA; Agilent, Santa Clara, CA; QC Ware Corp., Palo Alto, CA; Orbis Labsystems Services, Leopardstown, IRELAND; Lifebit Biotech Limited, London, UNITED KINGDOM; Eagle Genomics Ltd., Cambridge, UNITED KINGDOM; QuEra, Boston, MA; MolPort, Riga, LATVIA; and Biomage, Edinburgh, UNITED KINGDOM have withdrawn as parties to this venture.</P>
                <P>No other changes have been made in either the membership or planned activity of the group research project. Membership in this group research project remains open, and Pistoia Alliance, Inc. intends to file additional written notifications disclosing all changes in membership.</P>
                <P>
                    On May 28, 2009, Pistoia Alliance, Inc. filed its original notification pursuant to section 6(a) of the Act. The Department of Justice published a notice in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on July 15, 2009 (74 FR 34364).
                </P>
                <P>
                    The last notification was filed with the Department on October 4, 2023. A notice was published in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on February 5, 2024 (89 FR 7731).
                </P>
                <SIG>
                    <NAME>Suzanne Morris,</NAME>
                    <TITLE>Deputy Director Civil Enforcement Operations, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05303 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>Notice Pursuant to the National Cooperative Research and Production Act of 1993—Utility Broadband Alliance</SUBJECT>
                <P>
                    Notice is hereby given that, on February 2, 2024, pursuant to section 6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (“the Act”), Utility Broadband Alliance (“UBBA”) has filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing changes in its membership. The notifications were filed for the purpose of extending the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances. Specifically, Wirepas USA LLC, New York, NY; Rosenberger Site Solutions, LLC, Lake Charles, LA; Colorado Springs Utilities, Colorado Springs, CO; and Tarana Wireless, Milpatas, CA, have been added as parties to this venture.
                </P>
                <P>No other changes have been made in either the membership or planned activity of the group research project. Membership in this group research project remains open, and UBBA intends to file additional written notifications disclosing all changes in membership.</P>
                <P>
                    On May 4, 2021, UBBA filed its original notification pursuant to section 6(a) of the Act. The Department of Justice published a notice in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on June 10, 2021 (86 FR 30981).
                </P>
                <P>
                    The last notification was filed with the Department on November 9, 2023. A notice was published in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on December 15, 2023 (88 FR 86935).
                </P>
                <SIG>
                    <NAME>Suzanne Morris,</NAME>
                    <TITLE>Deputy Director Civil Enforcement Operations, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05317 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18438"/>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>Notice Pursuant to the National Cooperative Research and Production Act of 1993—Cooperative Research Group on Separation Technology Research (Star) Program:  Phase 3 (Star Phase 3)</SUBJECT>
                <P>
                    Notice is hereby given that, on January 9, 2024, pursuant to Section 6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (“the Act”), Southwest Research Institute—Cooperative Research Group Separation Technology Research (STAR) Program: Phase 3 (STAR Phase 3) has filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing changes in its membership. The notifications were filed for the purpose of extending the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances. Specifically, Schlumberger Norge AS, Stavanger, NORWAY, has been added as a party to this venture.
                </P>
                <P>No other changes have been made in either the membership or planned activity of the group research project. Membership in this group research project remains open and STAR Phase 3 intends to file additional written notifications disclosing all changes in membership or planned activities.</P>
                <P>
                    On August 15, 2023, STAR Phase 3 filed its original notification pursuant to Section 6(a) of the Act. The Department of Justice published a notice in the 
                    <E T="04">Federal Register</E>
                     pursuant to Section 6(b) of the Act on October 6, 2023, (88 FR 69671).
                </P>
                <SIG>
                    <NAME>Suzanne Morris,</NAME>
                    <TITLE>Deputy Director Civil Enforcement Operations, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05311 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-11-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>Notice Pursuant to the National Cooperative Research and Production Act of 1993—Z-Wave Alliance, Inc.</SUBJECT>
                <P>
                    Notice is hereby given that, on January 26, 2024, pursuant to section 6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (the “Act”), Z-Wave Alliance, Inc. (the “Joint Venture”) filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing changes in its membership. The notifications were filed for the purpose of extending the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances.
                </P>
                <P>Specifically, Oliver IQ Inc., Sandy, UT; Shenzhen Longzhiyuan Technology Co., Ltd., Shenzhen, PEOPLE'S REPUBLIC OF CHINA; Idlespace Technology Company Co., Ltd., Ontario, CANADA; and iHomeFuture, Dubai, UNITED ARAB EMIRATES have joined as parties to the venture.</P>
                <P>Also, VDA Group SpA a S.U., Pordenone, ITALY; ELTEX Enterprise Ltd., Novosibirsk, RUSSIA; BRK Brands Inc., Aurora, IL; Buo Home SL, Parets Del Valles, SPAIN; GroupSYS Pty Ltd, Erina, AUSTRALIA; Pyronix Limited, Rotherham, UNITED KINGDOM; Worthington Distribution, Tafton, PA; Rently Keyless, Los Angeles, CA; Daikin Airconditioning (Singapore) Pte Ltd., Singapore, SINGAPORE; Spectrum Brands Inc., Lake Forest, CA; Devicebook Inc., Bellevue, WA; and Zone-B2B SARL, Saint-Prex, SWITZERLAND have withdrawn as parties to the venture.</P>
                <P>In addition, an existing member, Fibar Group S.A. has changed its name to Nice-Polska Sp. Z.o.o., Wysogotowo, POLAND.</P>
                <P>Finally, Canny Electrics, Melbourne, AUSTRALIA withdrew as a party to the venture on January 9, 2024; and rejoined as a party to the venture on January 24, 2024.</P>
                <P>No other changes have been made in either the membership or the planned activity of the venture. Membership in this venture remains open, and the Joint Venture intends to file additional written notifications disclosing all changes in membership.</P>
                <P>
                    On November 19, 2020, the Joint Venture filed its original notification pursuant to section 6(a) of the Act. The Department of Justice published a notice in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on December 1, 2020 (85 FR 77241).
                </P>
                <P>
                    The last notification was filed with the Department on November 1, 2023. A notice was published in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on December 15, 2023 (88 FR 86933).
                </P>
                <SIG>
                    <NAME>Suzanne Morris,</NAME>
                    <TITLE>Deputy Director Civil Enforcement Operations, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05308 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>Notice Pursuant to the National Cooperative Research and Production Act of 1993—Resilient Infrastructure + Secure Energy Consortium</SUBJECT>
                <P>
                    Notice is hereby given that, January 5, 2024, pursuant to section 6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (“the Act”), the Resilient Infrastructure + Secure Energy Consortium (“RISE”) has filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing changes in its membership. The notifications were filed for the purpose of extending the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances. Specifically, Avalanche Energy Designs, Inc., Tukwila, WA; Centrifugal Energy LLC, Pompton Plains, NJ; Fedsprout, Princeton, NJ; Inergy, Chubbuck, ID; Iron Bear Technologies LLC, Ellicott City, MD; MobileNuclear Energy LLC, Fernandina Beach, FL; NetThunder, Buffalo Grove, IL; and Noresco, Westborough, MA have been added as parties to this venture.
                </P>
                <P>No other changes have been made in either the membership or planned activity of the group research project. Membership in this group research project remains open, and RISE intends to file additional written notifications disclosing all changes in membership.</P>
                <P>
                    On July 2, 2021, RISE filed its original notification pursuant to section 6(a) of the Act. The Department of Justice published a notice in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on August 23, 2021 (86 FR 47155).
                </P>
                <P>
                    The last notification was filed with the Department on October 3, 2023. A notice was published in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on December 15, 2023 (88 FR 86929).
                </P>
                <SIG>
                    <NAME>Suzanne Morris,</NAME>
                    <TITLE>Deputy Director Civil Enforcement Operations, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05319 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-11-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>Notice Pursuant to the National Cooperative Research and Production Act of 1993—R Consortium, Inc.</SUBJECT>
                <P>
                    Notice is hereby given that, on January 29, 2024, pursuant to section 
                    <PRTPAGE P="18439"/>
                    6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (“the Act”), R Consortium, Inc. (“R Consortium”) has filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing changes in its membership. The notifications were filed for the purpose of extending the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances. Specifically, Parexel International Corporation, Waltham, MA, has withdrawn as a party to this venture.
                </P>
                <P>No other changes have been made in either the membership or planned activity of the group research project. Membership in this group research project remains open, and R Consortium intends to file additional written notifications disclosing all changes in membership.</P>
                <P>
                    On September 15, 2015, R Consortium filed its original notification pursuant to section 6(a) of the Act. The Department of Justice published a notice in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on October 2, 2015 (80 FR 59815).
                </P>
                <P>
                    The last notification was filed with the Department on June 6, 2023. A notice was published in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on August 22, 2023 (88 FR 57129).
                </P>
                <SIG>
                    <NAME>Suzanne Morris,</NAME>
                    <TITLE>Deputy Director Civil Enforcement Operations, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05309 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>Notice Pursuant to the National Cooperative Research and Production Act of 1993—Cooperative Research Group on Numerical Propulsion System Simulation</SUBJECT>
                <P>
                    Notice is hereby given that, on January 4, 2024, pursuant to section 6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (“the Act”), Southwest Research Institute—Cooperative Research Group on Numerical Propulsion System Simulation (“NPSS”) has filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing changes in its membership. The notifications were filed for the purpose of extending the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances. Specifically, GE Vernova, Cambridge, MA, has been added as a party to this venture.
                </P>
                <P>No other changes have been made in either the membership or planned activity of the group research project. Membership in this group research project remains open and NPSS intends to file additional written notifications disclosing all changes in membership or planned activities.</P>
                <P>
                    On December 11, 2013, NPSS filed its original notification pursuant to section 6(a) of the Act. The Department of Justice published a notice in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on February 20, 2014, (79 FR 9767).
                </P>
                <P>
                    The last notification was filed with the Department on November 10, 2023. A notice was published in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on December 15, 2023, (88 FR 86940).
                </P>
                <SIG>
                    <NAME>Suzanne Morris,</NAME>
                    <TITLE>Deputy Director Civil Enforcement Operations, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05312 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>Notice Pursuant to the National Cooperative Research and Production Act of 1993—Expeditionary Missions Consortium—Crane</SUBJECT>
                <P>
                    Notice is hereby given that, on January 11, 2024, pursuant to section 6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (“the Act”), Expeditionary Missions Consortium—Crane (“EMC
                    <SU>2</SU>
                    ”) has filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing (1) the identities of the parties to the venture and (2) the nature and objectives of the venture. The notifications were filed for the purpose of invoking the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances.
                </P>
                <P>
                    Pursuant to section 6(b) of the Act, the identities of the parties to the venture are: ACMI-Austin, LLC, Austin, TX; Advanced Simulation Technology Inc., Herndon, VA; Aegis Power Systems, Inc., Murphy, NC; Aerovel Corporation, Bingen, WA; Alluvionic Inc., Melbourne, FL; Amentum Services, Inc., Chantilly, VA; American Rheinmetall Munition Inc., Stafford, VA; Applied Information Sciences, Inc, Reston, VA; Applied Technology, Inc., King George, VA; Assured Information Security, Inc., Rome, NY; Astrapi Corporation, Dallas, TX; Asymmetric Technologies, LLC, Dublin, OH; Battelle, Columbus, OH; Beast Code LLC, Fort Walton Beach, FL; Bigelow Family Holdings LLC DBA Mettle Ops, Sterling Heights, MI; Boston Engineering Corporation, Waltham, MA; CFD Research Corporation, Huntsville, AL; Cisco Systems, Inc., San Jose, CA; Colvin Run Networks, Inc., Tysons, VA; Concurrent Technologies Corporation, Johnstown, PA; Corvid Technologies, LLC, Mooresville, NC; DataSoft Corp., Phoenix, AZ; Davidson Technologies Incorporated, Huntsville, AL; deciBel Research, Inc., Huntsville, AL; Design West Technologies, Inc., Tustin, CA; Dignitas Technologies, Orlando, FL; DKW Consulting LLC, Tallahassee, FL; ElbitAmerica, Inc., Fort Worth, TX; Eos Energetics Inc., Penrose, CO; EPIQ Design Solutions, Rolling Meadows, IL; EWA Government Systems, Inc.; Exergi Predictive, Hugo, MN; Exquadrum Inc., Victorville, CA; Fenix Group, Inc., Chantilly, VA; G3 Technologies, Columbia, MD; GaN Corporation, Huntsville, AL; GenXComm, Austin, TX; GIRD Systems, Inc, Cincinnati, OH; Graf Research Corporation, Blacksburg, VA; Guidehouse Inc, Mclean, VA; HDT Expeditionary—Global, Solon, OH; HDT Expeditionary Systems, Fredericksburg, VA; Hyperion Technology Group, Inc., Tupelo, MS; iGov Technologies, Inc., Reston, VA; Indiana Microelectronics, LLC, West Lafayette, IN; Integrated Solutions For Systems, Inc., Huntsville, AL; Integration Innovation Inc, Huntsville, AL; Intuitive Research and Technology Corporation, Huntsville, AL; Iron EagleX, Inc., Tampa, FL; JEM Engineering, LLC, Laurel, MD; Karem Aircraft, Inc., Lake Forest, CA; KEF Robotics, Pittsburg, PA; KnowledgeBridge International, Chantilly, VA; Kord Technologies, LLC, Huntsville, AL; Kostas Research Institute, Burlington, MA; Kowalski Heat Treating, Cleveland, OH; KPMG LLP, Mclean, VA; L2NL, LLC, Charleston, SC; L3Harris Maritime Services, Inc., Norfolk, VA; Laine LLC, Goose Creek, SC; Lockheed Martin Corporation, Grand Prairie, TX; Ludlum Measurements, Inc. dba VPI Technology, Draper, UT; Makai Ocean Engineering, Inc., Waimanalo, HI; Marine Ventures International, Inc., Stuart, FL; MATBOCK, LLC, Virginia Beach, VA; MBDA Incorporated, Huntsville, AL; MEPSS LLC, Indian Harbour Beach, FL; Merril Technologies Group, Inc., Saginaw, MI; Mistral Inc., Bethesda, MD; Munro &amp; Associates, Inc., Auburn Hills, MI; NAG, LLC dba NAG Marine, Norfolk, VA; Navmar Applied 
                    <PRTPAGE P="18440"/>
                    Sciences Corporation, Warminster, PA; NIC4, Inc. d/b/a Network Innovations U.S. Government, Tampa, FL; Northrop Grumman Defense Systems, Mclean, VA; Northrop Grumman Systems Corporation, Plymouth, MN; Nostromo, LLC, Kennebunk, ME; NOVA Power Solutions, Inc., Sterling, VA; Oceanetics, Annapolis, MD; Opto-Knowledge Systems, Inc., Torrance, CA; Otoole Tek LLC, Rocky Hill, CT; Outpost Technologies, Inc., Huntsville, AL; Parsons Government Services, Centreville, VA; Pathfinder Wireless Corp., Seattle, WA; Peerless Technologies Corporation, Fairborn, OH; Persistent Systems, LLC, New York, NY; Pison Technology, Boston, MA: Plasan North America, Inc., Walker, MI; Precision Products Inc, Dalton, GA; PTI Tech, Clifton, NJ; Purdue Applied Research Institute, LLC, West Lafayette, IN; Questek Innovations LLC, Evanston, IL; RadioSoft, Inc. (dba LS telcom a RadioSoft operation), Clarkesville, GA; Rafael Systems Global Sustainment, LLC, Reston, VA; R-DEX Systems, Inc., Woodstock, GA; REDLattice, Inc., Chantilly, VA; Resource Management Concepts, Inc., Lexington Park, MD; Rocal Corp d.b.a Rebling Plastings, Warrington, PA; Rocky Mountain Scientific Laboratory, Littleton, CO; Raytheon Company, El Segundo, CA; Saab, Inc., East Syracuse, NY; SAVIT Corporation, Rockaway, NJ; SCHOTT North America, Inc, Duryea, PA; Sciens Innovations, LLC, York, PA; Sentient Digital dba Entrust Government Solutions, New Orleans, LA; Siemens Government Technologies, Inc., Reston, VA; Sierra Nevada Corporation, Englewood, CO; Signature Science LLC, Austin, TX; Smartronix, LLC, Hollywood, MD; Southwest Research Institute, San Antonio, TX; Spectral Labs Incorporated, San Diego, CA; Steiner eOptics, Inc, Miamisburg, OH; Strategy Robot, Inc., Pittsburgh, PA; Technology Service Corporation dba TSC, Arlington, VA; Texas Research Institute Austin, Inc., Austin, TX; Thales Defense &amp; Security, Inc., Clarksburg, MD; ThayerMahan Inc., Groton, CT; The SURVICE Engineering Company, LLC, Belcamp, MD; The University of Alabama in Huntsville, Huntsville, AL; TLC Solutions, Inc., Saint Augustine, FL; Vadum Inc, Raleigh, NC; Valkyrie Enterprises, LLC, Virginia Beach, VA; VES LLC, Aberdeen Proving Ground, MD; Viasat, Carlsbad, CA; Vsolvit LLC, Henderson, NV; W R Systems, Ltd., Fairfax, VA; and XR 2 Lead LLC, Dumfries, VA.
                </P>
                <P>
                    The general area of EMC
                    <SU>2</SU>
                    's planned activity is to conduct research, research and development, and prototyping of projects and programs in the following technology areas: Verification and Validation, Artificial Intelligence/Machine Learning, Multispectral Sensing, Design Assurance, Outreach and Standards, Materials and Processes, Manufacturing Technology, Modeling and Simulation, Spectrum Warfare Technologies, and Expeditionary Warfare Technologies.
                </P>
                <SIG>
                    <NAME>Suzanne Morris,</NAME>
                    <TITLE>Deputy Director Civil Enforcement Operations, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05301 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>Notice Pursuant to the National Cooperative Research and Production Act of 1993—Maritime Sustainment and Technology Innovation Consortium</SUBJECT>
                <P>
                    Notice is hereby given that, on January 8, 2024, pursuant to section 6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (“the Act”), Maritime Sustainment and Technology Innovation Consortium (“MSTIC”) has filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing changes in its membership. The notifications were filed for the purpose of extending the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances. Specifically, 3D Systems Inc., Littleton, CO; ATI, Inc., Pittsburgh, PA; Castheon, Inc., Thousand Oaks, CA; Clear Carbon &amp; Components, Inc., Bristol, RI; Corsha, Inc., Vienna, VA; DM3D Technology LLC, Auburn Hills, MI; DTCUBED LLC, Sewell, NJ; Ellis &amp; Watts Global Industries, Inc., Batavia, OH; Elzly Technology Corp., Reston, VA; Exponent, Inc., Menlo Park, CA; G.S.E. Dynamics, Inc., Hauppauge, NY; L3 Technologies, Inc—L3 KEO, Northampton, MA; Milwaukee Valve Company, Inc., New Berlin, WI; Mission Focused Systems, Inc., Royersford, PA; Pacific Engineering, Inc., Roca, NE; Pioneering Decisive Solutions, Inc., California, MD; Precise Systems, Inc., Lexington Park, MD; Saab, Inc., East Syracuse, NY; Sentient Digital, Inc., New Orleans, LA; Signature Science LLC, Austin, TX; Skuld LLC, London, OH; and The Entwistle Company LLC, Hudson, MA, have been added as parties to this venture.
                </P>
                <P>No other changes have been made in either the membership or planned activity of the group research project. Membership in this group research project remains open, and MSTIC intends to file additional written notifications disclosing all changes in membership.</P>
                <P>
                    On October 21, 2020, MSTIC filed its original notification pursuant to section 6(a) of the Act. The Department of Justice published a notice in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on November 19, 2020 (85 FR 73750).
                </P>
                <P>
                    The last notification was filed with the Department on October 6, 2023. A notice was published in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on December 15, 2023 (88 FR 86936).
                </P>
                <SIG>
                    <NAME>Suzanne Morris,</NAME>
                    <TITLE>Deputy Director Civil Enforcement Operations, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05315 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-11-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>Notice Pursuant to the National Cooperative Research and Production Act of 1993—Naval Surface Technology &amp; Innovation Consortium</SUBJECT>
                <P>
                    Notice is hereby given that, on January 9, 2024, pursuant to Section 6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (“the Act”), Naval Surface Technology &amp; Innovation Consortium (“NSTIC”) has filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing changes in its membership. The notifications were filed for the purpose of extending the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances. Specifically, 3D Systems, Inc., Littleton, CO; Aunautic Technologies, National City, CA; Bowhead Avionics Manufacturing LLC, Plano, TX, CoAspire LLC, Fairfax, VA; DTCUBED LLC, Sewell, NJ; Emelody Worldwide, Inc., Peachtree Corners, GA; G3 Technologies, Columbia, MD; GoHypersonic Incorporated, Dayton, OH; KCG Engineering Group, Inc., Virginia Beach, VA; L3Harris Interstate Electronics Corporation, Anaheim, CA; Nikira Labs, Inc., Mountain View, CA; Signature Science LLC, Austin, TX; Strategy Robot, Inc., Pittsburg, PA; Team Corporation, Burlington, WA; Teledyne FLIR Detection, Stillwater, OK; The 
                    <PRTPAGE P="18441"/>
                    Ross Group Construction Corporation LLC, Tulsa, OK; Torch Technologies, Huntsville, AL; and Xona Space Systems, Burlingame, CA, have been added as parties to this venture.
                </P>
                <P>No other changes have been made in either the membership or planned activity of the group research project. Membership in this group research project remains open, and NSTIC intends to file additional written notifications disclosing all changes in membership.</P>
                <P>
                    On October 8, 2019, NSTIC filed its original notification pursuant to Section 6(a) of the Act. The Department of Justice published a notice in the 
                    <E T="04">Federal Register</E>
                     pursuant to Section 6(b) of the Act on November 12, 2019 (84 FR 61071).
                </P>
                <P>
                    The last notification was filed with the Department on October 11, 2023. A notice was published in the 
                    <E T="04">Federal Register</E>
                     pursuant to Section 6(b) of the Act on December 15, 2023 (88 FR 86934).
                </P>
                <SIG>
                    <NAME>Suzanne Morris,</NAME>
                    <TITLE>Deputy Director Civil Enforcement Operations, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05316 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>Notice Pursuant to the National Cooperative Research and Production Act of 1993—The Institute of Electrical and Electronics Engineers, Inc.</SUBJECT>
                <P>
                    Notice is hereby given that, on November 17, 2023, pursuant to section 6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (“the Act”), The Institute of Electrical and Electronics Engineers, Inc. (“IEEE”) has filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing additions or changes to its standards development activities. The notifications were filed for the purpose of extending the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances. Specifically, 61 new standards have been initiated and 18 existing standards are being revised. More detail regarding these changes can be found at: 
                    <E T="03">https://standards.ieee.org/about/sasb/sba/sep2023/. https://standards.ieee.org/about/sasb/sba/nov2023/.</E>
                     The following pre-standards activities associated with IEEE Industry Connections Activities were launched or renewed: 
                    <E T="03">https://standards.ieee.org/about/bog/cag/approvals/september2023/.</E>
                </P>
                <P>
                    The following conformity assessment programs associated with published IEEE standards and supporting their promulgation were initiated: 
                    <E T="03">https://standards.ieee.org/products-programs/icap/programs/ieee-2621-standards/. https://standards.ieee.org/products-programs/icap/programs/icap-drone-program/.</E>
                </P>
                <P>
                    On September 17, 2004, IEEE filed its original notification pursuant to section 6(a) of the Act. The Department of Justice published a notice in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on November 3, 2004 (69 FR 64105).
                </P>
                <P>
                    The last notification was filed with the Department on July 17, 2023. A notice was published in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on October 5, 2023 (88 FR 69232).
                </P>
                <SIG>
                    <NAME>Suzanne Morris,</NAME>
                    <TITLE>Deputy Director Civil Enforcement Operations, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05306 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>Notice Pursuant to the National Cooperative Research and Production Act of 1993—National Armaments Consortium</SUBJECT>
                <P>
                    Notice is hereby given that, on January 10, 2024, pursuant to section 6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (“the Act”), National Armaments Consortium (“NAC”) has filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing changes in its membership. The notifications were filed for the purpose of extending the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances. Specifically, Augustine Consulting, Inc., Hamilton, NJ; Aegis Power Systems, Inc., Murphy, NC; Agile Decision Sciences, LLC, Huntsville, AL; American Material Handling, Inc., Watkinsville, GA; Appleton Marine, Inc., Appleton, WI; Bridgehill Corporation, Paramus, NJ; Canopy Aerospace, Inc., Littleton, CO; Cimarron Software Services, Inc., Houston, TX; CODE Plus, Inc., Fairfax, VA; Crowdbotics Corporation, Berkeley, CA; Danbury Mission Technologies, LLC, Danbury, CT; DZYNE Technologies, LLC, Fairfax, VA; Espey Manufacturing &amp; Electronics Corp., Saratoga Springs, NY; Final Frontier Security, LLC, Hollywood, MD; FreEnt Techologies, Inc., Huntsville, AL; General Dynamics Information Technology, Falls Church, VA; HAMR Industries, LLC, Clinton, PA; Martinez and Turek, Inc., Rialto, CA; MILCOTS, Mahwah, NJ; Munitions Industrial Base Task Force, Inc., Arlington, VA; National Security Capital, LLC, Owings Mills, MD; QTEC, Inc., Huntsville, AL; Ross Group Construction Corporation, LLC, Tulsa, OK; Sentient Digital, Inc., New Orleans, LA; Shearwater Technology, Inc., Washington, IL; Signature Science, LLC, Austin, TX; Sonardyne, Inc., Houston, TX; TGV Rockets, Inc., Washington, DC; VIAVI Solutions, LLC, Wichita, KS; and, WWM Solutions, LLC, Washington, DC have been added as parties to this venture.
                </P>
                <P>No other changes have been made in either the membership or planned activity of the group research project. Membership in this group research project remains open, and NAC intends to file additional written notifications disclosing all changes in membership.</P>
                <P>
                    On May 2, 2000, NAC filed its original notification pursuant to section 6(a) of the Act. The Department of Justice published a notice in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on June 30, 2000 (65 FR 40693).
                </P>
                <P>
                    The last notification was filed with the Department on October 10, 2023. A notice was published in the 
                    <E T="04">Federal Register</E>
                     pursuant to section 6(b) of the Act on December 15, 2023 (88 FR 86931).
                </P>
                <SIG>
                    <NAME>Suzanne Morris,</NAME>
                    <TITLE>Deputy Director Civil Enforcement Operations, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05318 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-11-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL AERONAUTICS AND SPACE ADMINISTRATION</AGENCY>
                <DEPDOC>[Notice: 24-017]</DEPDOC>
                <SUBJECT>NASA Advisory Council; Science Committee; Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Aeronautics and Space Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with the Federal Advisory Committee Act, as amended, the National Aeronautics and Space Administration (NASA) announces a meeting of the Science Committee of the NASA Advisory Council (NAC). This Committee reports to the NAC. The meeting will be held for the purpose of soliciting, from the scientific community and other persons, 
                        <PRTPAGE P="18442"/>
                        scientific and technical information relevant to program planning.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Monday, March 25, 2024, 10:00 a.m.-4:30 p.m., Eastern Time.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Public attendance will be virtual only. See dial-in and Webex information below under 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ms. KarShelia Kinard, Science Mission Directorate, NASA Headquarters, Washington, DC 20546, (202) 358-2355 or 
                        <E T="03">karshelia.kinard@nasa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>As noted above, this meeting is virtual and will take place telephonically and via Webex. Any interested person must use a touch-tone phone to participate in this meeting. The Webex connectivity information for each day is provided below. For audio, when you join the Webex event, you may use your computer or provide your phone number to receive a call back, otherwise, call the U.S. toll conference number listed for each day.</P>
                <P>
                    On Monday, March 25, the event address for attendees is: 
                    <E T="03">https://nasaevents.webex.com/nasaevents/j.php?MTID=m126693463ff0b0b0024aa7349f9250cb.</E>
                </P>
                <P>The event number is 2830 040 7491 and the event password is JMnk7EmP7Z6 (56657367 from phones and video systems). If needed, the U.S. toll conference number is 1-415-527-5035 and the access code is 283 004 07491.</P>
                <P>The agenda for the meeting includes the following topics:</P>
                <FP SOURCE="FP-1">—Science Mission Directorate (SMD) Missions, Programs and Activities</FP>
                <P>It is imperative that the meeting be held on these dates due to the scheduling priorities of the key participants.</P>
                <SIG>
                    <NAME>Carol J. Hamilton,</NAME>
                    <TITLE>Acting, Advisory Committee Management Officer, National Aeronautics and Space Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05129 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7510-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL SCIENCE FOUNDATION</AGENCY>
                <SUBJECT>Notice of Intent To Seek Approval To Renew an Information Collection System; Grantee Reporting Requirements for the NSF Small Business Innovation Research and the Small Business Technology Transfer (SBIR/STTR) Programs</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Science Foundation.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Under the Paperwork Reduction Act of 1995, and as part of its continuing effort to reduce paperwork and respondent burden, the National Science Foundation (NSF) is inviting the general public or other Federal agencies to comment on this proposed information collection reinstatement.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments on this notice must be received by May 13, 2024, to be assured consideration. Comments received after that date will be considered to the extent practicable. Send comments to the address below.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Suzanne H. Plimpton, Reports Clearance Officer, National Science Foundation, 2415 Eisenhower Avenue, Suite E7400, Alexandria, Virginia 22314; telephone (703) 292-7556; or send email to 
                        <E T="03">splimpto@nsf.gov.</E>
                         Individuals who use a telecommunications device for the deaf (TDD) may call the Federal Information Relay Service (FIRS) at 1-800-877-8339, which is accessible 24 hours a day, 7 days a week, 365 days a year (including federal holidays).
                    </P>
                    <P>
                        <E T="03">Comments:</E>
                         Comments are invited on: (a) whether the proposed collection of information is necessary for the proper performance of the functions of the Foundation, including whether the information will have practical utility; (b) the accuracy of the Foundation's estimate of the burden of the proposed collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on those who are to respond, including through the use of automated collection techniques or other forms of information technology.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title of Collection:</E>
                     Grantee Reporting Requirements for the NSF Small Business Innovation Research and the Small Business Technology Transfer (SBIR/STTR) Programs.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     3145-0252.
                </P>
                <P>
                    <E T="03">Expiration Date of Approval:</E>
                     July 31, 2023.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Reinstatement and request for Office of Management and Budget (OMB) approval of an information collection.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                </P>
                <P>
                    <E T="03">Proposed Project:</E>
                     This request is for reinstating interim reporting requirements for the NSF Small Business Innovation Research (SBIR)/Small Business Technology Transfer Research (STTR) programs.
                </P>
                <P>The NSF SBIR/STTR programs focus on transforming scientific discovery into products and services with commercial potential and/or societal benefit. Unlike fundamental or basic research activities that focus on scientific and engineering discoveries, the NSF SBIR/STTR programs support the creation of opportunities to move fundamental science and engineering out of the lab and into the market at scale, through startups and small businesses representing deep technology ventures.</P>
                <P>The NSF SBIR/STTR programs have two phases: Phase I and Phase II (with an optional Phase IIB as matching supplements). SBIR/STTR Phase I is a 6-12 month experimental or theoretical investigation that allows the awardees to determine the scientific and technical feasibility, as well as the commercial merit of the idea or concept. Phase II further develops the proposed concept, building on the feasibility project undertaken in Phase I, and accelerate the Phase I project to the commercialization stage and enhance the overall strength of the commercial potential. As such, Phase II SBIR/STTR awards have a longer expected period of performance of 24 months.</P>
                <P>The NSF SBIR/STTR programs request approval from OMB on the reinstatement of the NSF SBIR/STTR Phase II interim/progress report data collection.</P>
                <P>The interim/progress report will be required every six months for the life of the Phase II award. The report collects information on the technical progress of the funded NSF work, which allows managing Program Directors to monitor the project and ensure that the award is in good standing.</P>
                <P>The report is divided into 6 sections: (1) Basic Reporting Data, (2) Level of Effort, (3) SBIR-wide Certifications, (4) Cooperative Agreement (NSF-specific Certifications), (5) Technical Narratives, and (6) Project Milestones.</P>
                <P>
                    The kinds of data collected from the report include name of the startup company, information on the principal investigator (PI) (name, email address, and phone number), the number of full-time equivalent (FTE) employees working at the startup, amount of funding received during the award period. In addition, information pertaining to company officers and key personnel, their corresponding ownership status, and their levels of efforts provided to the startups are also requested. Collectively, these data will enable the managing Program Directors to (1) evaluate a given company's business structure, (2) ascertain the level of commitment of the PI(s), co-PI(s), and key personnel to the startup venture, and (3) identify conflicts of interests (if any), as part of the due diligence process that the programs undertake to verify that there are no 
                    <PRTPAGE P="18443"/>
                    fraudulent or inappropriate business practices.
                </P>
                <P>
                    The report also asks about: inputs (
                    <E T="03">i.e.,</E>
                     project expenditures, efforts exerted by key personnel), outputs (
                    <E T="03">i.e.,</E>
                     R&amp;D activities, technical progresses), outcomes (
                    <E T="03">i.e.,</E>
                     research milestones, fundraising activities), and impacts (
                    <E T="03">i.e.,</E>
                     technical and/or commercial successes).
                </P>
                <P>Finally, the report also requests: (1) a discussion of progresses highlighting key technical and commercial activity/results during the reporting period, (2) compliance requirements checklists from the Small Business Administration (SBA) and NSF, and (3) a Gantt chart describing the project status, as well as task assignments to key personnel in the project.</P>
                <P>
                    <E T="03">Use of the Information:</E>
                     The data collected will be used primarily for award monitoring. The data could also be used for congressional requests, inquiries from the NSF's Office of the Inspector General, supporting evidence of litigations, auditing, and other legal investigations, NSF internal reports, and program evaluations, if necessary.
                </P>
                <P>
                    <E T="03">Estimate of Burden:</E>
                     The estimated number of respondents is: 410. Average time to complete the interim report: 18 hours. The estimated total burden hours: 7,380 hours per year.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     The respondents are either PIs or Co-PIs listed on the NSF SBIR/STTR Proposals, Founders, and/or Co-founders of the startups funded by the NSF SBIR/STTR programs.
                </P>
                <SIG>
                    <DATED>Dated: March 7, 2024.</DATED>
                    <NAME>Suzanne H. Plimpton,</NAME>
                    <TITLE>Reports Clearance Officer, National Science Foundation.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05270 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7555-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NUCLEAR REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[Docket No. 50-275 LR-2 and 50-323 LR-2; ASLBP No. 24-983-02-LR-BD01]</DEPDOC>
                <SUBJECT>Pacific Gas and Electric Company; Establishment of Atomic Safety and Licensing Board</SUBJECT>
                <P>
                    Pursuant to the Commission's regulations, 
                    <E T="03">see, e.g.,</E>
                     10 CFR 2.104, 2.105, 2.300, 2.309, 2.313, 2.318, 2.321, notice is hereby given that an Atomic Safety and Licensing Board (Board) is being established to preside over the following proceeding:
                </P>
                <HD SOURCE="HD1">Pacific Gas and Electric Company</HD>
                <HD SOURCE="HD2">(Diablo Canyon Nuclear Power Plant, Units 1 and 2)</HD>
                <P>
                    This proceeding involves an application seeking a twenty-year license renewal of Facility Operating License Nos. DPR-80 and DPR-82 to authorize Pacific Gas and Electric Company to operate Diablo Canyon Nuclear Power Plant, Units 1 and 2, until, respectively, November 2, 2044, and August 26, 2045. In response to a notice published in the 
                    <E T="04">Federal Register</E>
                     announcing the opportunity to request a hearing, 
                    <E T="03">see</E>
                     88 FR 87,817 (Dec. 19, 2023), a hearing request was submitted by email on March 4, 2024 and subsequently filed through the E-Filing System on March 5, 2024 on behalf of San Luis Obispo Mothers for Peace, Friends of the Earth, and Environmental Working Group. Additionally, the California Energy Commission filed a request to participate in the proceeding as a non-party pursuant to 10 CFR 2.315(c).
                </P>
                <P>The Board is comprised of the following Administrative Judges:</P>
                <P>Jeremy A. Mercer, Chair, Atomic Safety and Licensing Board Panel, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001.</P>
                <P>Nicholas G. Trikouros, Atomic Safety and Licensing Board Panel, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001.</P>
                <P>Dr. Gary S. Arnold, Atomic Safety and Licensing Board Panel, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001.</P>
                <P>
                    All correspondence, documents, and other materials shall be filed in accordance with the NRC E-Filing rule. 
                    <E T="03">See</E>
                     10 CFR 2.302.
                </P>
                <SIG>
                    <DATED>Dated: March 7, 2024.</DATED>
                    <NAME>Edward R. Hawkens,</NAME>
                    <TITLE>Chief Administrative Judge, Atomic Safety and Licensing Board Panel, Rockville, Maryland.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05277 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[NRC-2023-0056]</DEPDOC>
                <SUBJECT>Information Collection: Notices, Instructions, and Reports to Workers: Inspection and Investigations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Nuclear Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of submission to the Office of Management and Budget; request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Nuclear Regulatory Commission (NRC) has recently submitted a request for renewal of an existing collection of information to the Office of Management and Budget (OMB) for review. The information collection is entitled, “Notices, Instructions, and Reports to Workers: Inspection and Investigations.”</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments by April 12, 2024. Comments received after this date will be considered if it is practical to do so, but the Commission is able to ensure consideration only for comments received on or before this date.</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">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.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        David Cullison, NRC Clearance Officer, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001; telephone: 301-415-2084; email: 
                        <E T="03">Infocollects.Resource@nrc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Obtaining Information and Submitting Comments</HD>
                <HD SOURCE="HD2">A. Obtaining Information</HD>
                <P>Please refer to Docket ID NRC-2023-0056 when contacting the NRC about the availability of information for this action. You may obtain publicly available information related to this action by 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-2023-0056.
                </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, at 301-415-4737, or by email to 
                    <E T="03">PDR.Resource@nrc.gov.</E>
                     The supporting statement is available in ADAMS under Accession No. ML24039A117.
                </P>
                <P>
                    • 
                    <E T="03">NRC's PDR:</E>
                     The PDR, where you may examine and order copies of publicly available documents, is open by appointment. 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 time (ET), Monday through Friday, except Federal holidays.
                </P>
                <P>
                    • 
                    <E T="03">NRC's Clearance Officer:</E>
                     A copy of the collection of information and related instructions may be obtained without 
                    <PRTPAGE P="18444"/>
                    charge by contacting the NRC's Clearance Officer, David C. Cullison, Office of the Chief Information Officer, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001; telephone: 301-415-2084; email: 
                    <E T="03">Infocollects.Resource@nrc.gov.</E>
                </P>
                <HD SOURCE="HD2">B. Submitting Comments</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">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.
                </P>
                <P>
                    The NRC cautions you not to include identifying or contact information in comment submissions that you do not want to be publicly disclosed in your comment submission. All comment submissions are posted at 
                    <E T="03">https://www.regulations.gov</E>
                     and entered into ADAMS. Comment submissions are not routinely edited to remove identifying or contact information.
                </P>
                <P>If you are requesting or aggregating comments from other persons for submission to the OMB, then you should inform those persons not to include identifying or contact information that they do not want to be publicly disclosed in their comment submission. Your request should state that comment submissions are not routinely edited to remove such information before making the comment submissions available to the public or entering the comment into ADAMS.</P>
                <HD SOURCE="HD1">II. Background</HD>
                <P>Under the provisions of the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35), the NRC recently submitted a request for renewal of an existing collection of information to OMB for review entitled, “Notices, Instructions, and Reports to Workers: Inspection and Investigations.” The NRC hereby informs potential respondents that an agency may not conduct or sponsor, and that a person is not required to respond to, a collection of information unless it displays a currently valid OMB control number.</P>
                <P>
                    The NRC published a 
                    <E T="04">Federal Register</E>
                     notice with a 60-day comment period on this information collection on November 13, 2023, 88 FR 77619.
                </P>
                <P>
                    1. 
                    <E T="03">The title of the information collection:</E>
                     Notices, Instructions, and Reports to Workers: Inspection and Investigations.
                </P>
                <P>
                    2. 
                    <E T="03">OMB approval number:</E>
                     3150-0044.
                </P>
                <P>
                    3. 
                    <E T="03">Type of submission:</E>
                     Extension.
                </P>
                <P>
                    4. 
                    <E T="03">The form number, if applicable:</E>
                     Not applicable.
                </P>
                <P>
                    5. 
                    <E T="03">How often the collection is required or requested:</E>
                     As necessary in order that adequate and timely reports of radiation exposure be made to individuals involved in applicable NRC-licensed activities.
                </P>
                <P>
                    6. 
                    <E T="03">Who will be required or asked to respond:</E>
                     Licensees authorized to receive, possess, use, or transfer material licensed by the NRC.
                </P>
                <P>
                    7. 
                    <E T="03">The estimated number of annual responses:</E>
                     1,889,382 (7 Reporting + 18,200 Recordkeeping + 1,871,174.88 Third-party disclosures).
                </P>
                <P>
                    8. 
                    <E T="03">The estimated number of annual respondents:</E>
                     18,200 (2,200 NRC + 16,000 Agreement States).
                </P>
                <P>
                    9. 
                    <E T="03">The estimated number of hours needed annually to comply with the information collection requirement or request:</E>
                     544,899 (3.5 Reporting + 18,200 Recordkeeping + 521,337.9 Third-party disclosures + 5,358 One-time burden).
                </P>
                <P>
                    10. 
                    <E T="03">Abstract:</E>
                     Part 19 of title 10 of the 
                    <E T="03">Code of Federal Regulations</E>
                     establishes requirements for notices, instructions, and reports by licensees and regulated entities to individuals participating in NRC-licensed and regulated activities and options available to these individuals in connection with Commission inspections of licensees and regulated entities, and to ascertain compliance with the provisions of the Atomic Energy Act of 1954, as amended, titles II and IV of the Energy Reorganization Act of 1974, and regulations, orders, and licenses thereunder. The regulations in this part also establish the rights and responsibilities of the Commission and individuals during interviews compelled by subpoena as part of the agency's inspections or investigations under section 161c of the Atomic Energy Act of 1954, as amended, on any matter within the Commission's jurisdiction.
                </P>
                <SIG>
                    <DATED>Dated: March 8, 2024.</DATED>
                    <P>For the Nuclear Regulatory Commission.</P>
                    <NAME>David Cullison,</NAME>
                    <TITLE>NRC Clearance Officer, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05320 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">POSTAL REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[Docket No. CP2023-30]</DEPDOC>
                <SUBJECT>New Postal Products</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Postal Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Commission is noticing a recent Postal Service filing for the Commission's consideration concerning a negotiated service agreement. This notice informs the public of the filing, invites public comment, and takes other administrative steps.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments are due:</E>
                         March 15, 2024.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit comments electronically via the Commission's Filing Online system at 
                        <E T="03">http://www.prc.gov.</E>
                         Those who cannot submit comments electronically should contact the person identified in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section by telephone for advice on filing alternatives.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>David A. Trissell, General Counsel, at 202-789-6820.</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</FP>
                    <FP SOURCE="FP-2">II. Docketed Proceeding(s)</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>The Commission gives notice that the Postal Service filed request(s) for the Commission to consider matters related to negotiated service agreement(s). The request(s) may propose the addition or removal of a negotiated service agreement from the Market Dominant or the Competitive product list, or the modification of an existing product currently appearing on the Market Dominant or the Competitive product list.</P>
                <P>Section II identifies the docket number(s) associated with each Postal Service request, the title of each Postal Service request, the request's acceptance date, and the authority cited by the Postal Service for each request. For each request, the Commission appoints an officer of the Commission to represent the interests of the general public in the proceeding, pursuant to 39 U.S.C. 505 (Public Representative). Section II also establishes comment deadline(s) pertaining to each request.</P>
                <P>
                    The public portions of the Postal Service's request(s) can be accessed via the Commission's website (
                    <E T="03">http://www.prc.gov</E>
                    ). Non-public portions of the Postal Service's request(s), if any, can be accessed through compliance with the requirements of 39 CFR 3011.301.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See</E>
                         Docket No. RM2018-3, Order Adopting Final Rules Relating to Non-Public Information, June 27, 2018, Attachment A at 19-22 (Order No. 4679).
                    </P>
                </FTNT>
                <P>
                    The Commission invites comments on whether the Postal Service's request(s) 
                    <PRTPAGE P="18445"/>
                    in the captioned docket(s) are consistent with the policies of title 39. For request(s) that the Postal Service states concern Market Dominant product(s), applicable statutory and regulatory requirements include 39 U.S.C. 3622, 39 U.S.C. 3642, 39 CFR part 3030, and 39 CFR part 3040, subpart B. For request(s) that the Postal Service states concern Competitive product(s), applicable statutory and regulatory requirements include 39 U.S.C. 3632, 39 U.S.C. 3633, 39 U.S.C. 3642, 39 CFR part 3035, and 39 CFR part 3040, subpart B. Comment deadline(s) for each request appear in section II.
                </P>
                <HD SOURCE="HD1">II. Docketed Proceeding(s)</HD>
                <P>
                    1. 
                    <E T="03">Docket No(s).:</E>
                     CP2023-30; 
                    <E T="03">Filing Title:</E>
                     USPS Notice of Amendment to Priority Mail &amp; First-Class Package Service Contract 224, Filed Under Seal; 
                    <E T="03">Filing Acceptance Date:</E>
                     March 7, 2024; 
                    <E T="03">Filing Authority:</E>
                     39 CFR 3035.105; 
                    <E T="03">Public Representative:</E>
                     Christopher C. Mohr; 
                    <E T="03">Comments Due:</E>
                     March 15, 2024.
                </P>
                <P>
                    This Notice will be published in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <NAME>Mallory S. Richards,</NAME>
                    <TITLE>Federal Register Liaison.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05288 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-FW-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-99690; File No. SR-NYSEAMER-2024-14]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; NYSE American LLC; Notice of Filing and Immediate Effectiveness of Proposed Change To Establish the NYSE American Aggregated Lite Market Data Feed</SUBJECT>
                <DATE>March 7, 2024.</DATE>
                <P>
                    Pursuant to section 19(b)(1) 
                    <SU>1</SU>
                    <FTREF/>
                     of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>2</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>3</SU>
                    <FTREF/>
                     notice is hereby given that, on February 27, 2024, NYSE American LLC (“NYSE American” or the “Exchange”) filed with the Securities and Exchange Commission (the “Commission”) the proposed rule change as described in Items I, II, and III below, which Items have been prepared by the self-regulatory organization. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         15 U.S.C. 78a.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to establish the NYSE American Aggregated Lite (“NYSE American Agg Lite”) market data feed. The proposed rule change is available on the Exchange's website at 
                    <E T="03">www.nyse.com,</E>
                     at the principal office of the Exchange, and at the Commission's Public Reference Room.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and the Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>The Exchange proposes to establish the NYSE American Agg Lite market data feed. The NYSE American Agg Lite is a NYSE American-only frequency-based depth of book market data feed of the NYSE American's limit order book for up to ten (10) price levels on both the bid and offer sides of the order book for securities traded on the Exchange and for which the Exchange reports quotes and trades under the Consolidated Tape Association (“CTA”) Plan or the Nasdaq/UTP Plan. NYSE American Agg Lite would be a compilation of limit order data that the Exchange would provide to vendors and subscribers. As proposed, the NYSE American Agg Lite data feed would be updated no less frequently than once per second. The NYSE American Agg Lite would include depth of book order data as well as security status messages. The security status message would inform subscribers of changes in the status of a specific security, such as trading halts, short sale restriction, etc. In addition, the NYSE American Agg Lite would also include order imbalance information prior to the opening and closing of trading.</P>
                <P>The Exchange proposes to offer NYSE American Agg Lite after receiving requests from vendors and subscribers that would like to receive the data described above in an integrated fashion at a pre-defined publication interval, in this case updates no less than once per second. An aggregated data feed may provide greater efficiencies and reduce errors for vendors and subscribers that currently choose to integrate the above data into a single offering after receiving it from the Exchange through existing products and adjust the publication frequency based on a subscriber's needs. The Exchange believes that providing vendors and subscribers with the option to subscribe to a market data product that integrates a subset of data from existing products and where such aggregated data is published at a pre-defined interval, thus lowering bandwidth, infrastructure and operational requirements, would allow vendors and subscribers to choose the best solution for their specific business needs. The Exchange notes that publishing only the top ten price levels on both the bid and offer sides of the order book where such data is communicated to subscribers at a pre-defined interval would reduce the overall volume of messages required to be consumed by subscribers when compared to a full order-by-order data feed or a full depth of book data feed. Providing data in this format and publication frequency would make NYSE American Agg Lite more easily consumable by vendors and subscribers, especially for display purposes.</P>
                <P>The Exchange proposes to offer NYSE American Agg Lite through the Exchange's Liquidity Center Network (“LCN”), a local area network in the Exchange's Mahwah, New Jersey data center that is available to users of the Exchange's co-location services. The Exchange would also offer NYSE American Agg Lite through the ICE Global Network (“IGN”), through which all other users and members access the Exchange's trading and execution systems and other proprietary market data products.</P>
                <P>The Exchange will file a separate rule filing to establish fees for NYSE American Agg Lite. The Exchange will announce the implementation date of this proposed rule change by Trader Update, which, subject to the effectiveness of this proposed rule change, will be no later than the second quarter of 2024.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that the proposed rule change is consistent with section 6(b) 
                    <SU>4</SU>
                    <FTREF/>
                     of the Act (“Act”), in general, and furthers the objectives of 
                    <PRTPAGE P="18446"/>
                    section 6(b)(5) 
                    <SU>5</SU>
                    <FTREF/>
                     of the Act, in particular, in that it is 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 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 it is not designed to permit unfair discrimination among customers, brokers, or dealers. This proposal is in keeping with those principles in that it promotes increased transparency through the dissemination of NYSE American Agg Lite to those interested in receiving it.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>The Exchange also believes this proposal is consistent with section 6(b)(5) of the Act because it protects investors and the public interest and promotes just and equitable principles of trade by providing investors with new options for receiving market data as requested by market data vendors and subscribers. The proposed rule change would benefit investors by facilitating their prompt access to the frequency-based depth of book contained in the NYSE American Agg Lite market data feed.</P>
                <P>
                    The Exchange also believes that the proposed rule change is consistent with section 11(A) of the Act 
                    <SU>6</SU>
                    <FTREF/>
                     in that it supports (i) fair competition among brokers and dealers, among exchange markets, and between exchange markets and markets other than exchange markets and (ii) the availability of information with respect to quotations for and transactions in securities to brokers, dealers, and investors. Furthermore, the proposed rule change is consistent with Rule 603 of Regulation NMS,
                    <SU>7</SU>
                    <FTREF/>
                     which provides that any national securities exchange that distributes information with respect to quotations for or transactions in an NMS stock do so on terms that are not unreasonably discriminatory. The NYSE American Agg Lite market data feed would be accessed and subscribed to on a voluntary basis, in that neither the Exchange nor market data vendors are required by any rule or regulation to make this data available. Accordingly, vendors and subscribers can discontinue their use at any time and for any reason.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         15 U.S.C. 78k-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         17 CFR 242.603.
                    </P>
                </FTNT>
                <P>In adopting Regulation NMS, the Commission granted self-regulatory organizations (“SROs”) and broker dealers increased authority and flexibility to offer new and unique market data to consumers of such data. It was believed that this authority would expand the amount of data available to users and consumers of such data and also spur innovation and competition for the provision of market data. The Exchange believes that NYSE American Agg Lite is precisely the sort of market data product that the Commission envisioned when it adopted Regulation NMS. The Commission concluded that Regulation NMS would itself further the Act's goals of facilitating efficiency and competition:</P>
                <EXTRACT>
                    <P>
                        Efficiency is promoted when broker-dealers who do not need the data beyond the prices, sizes, market center identifications of the NBBO and consolidated last sale information are not required to receive (and pay for) such data. The Commission also believes that efficiency is promoted when broker-dealers may choose to receive (and pay for) additional market data based on their own internal analysis of the need for such data.
                        <SU>8</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 51808 (June 9, 2005), 70 FR 37496 (June 29, 2005) (Regulation NMS Adopting Release).
                        </P>
                    </FTNT>
                </EXTRACT>
                <P>
                    In addition, NYSE American Agg Lite removes impediments to and perfects the mechanism of a free and open market and a national market system by providing investors with alternative market data and would compete with similar market data products currently offered by the four U.S. equities exchanges operated by Cboe Exchange, Inc.—Cboe BZX Exchange, Inc. (“BZX”), Cboe BYX Exchange, Inc. (“BYX”), Cboe EDGA Exchange, Inc. (“EDGA”), and Cboe EDGX Exchange, Inc. (“EDGX”), each of which offers a market data product called BZX Summary Depth, BYX Summary Depth, EDGA Summary Depth and EDGX Summary Depth, respectively (collectively, the “Cboe Summary Depth”).
                    <SU>9</SU>
                    <FTREF/>
                     Similar to Cboe Summary Depth, NYSE American Agg Lite can be utilized by vendors and subscribers to quickly access and distribute aggregated order book data. As noted above, NYSE American Agg Lite, similar to Cboe Summary Depth, would provide aggregated depth per security, including the bid, ask and share quantity for orders received by NYSE American, except unlike Cboe Summary Depth, which provides aggregated depth per security for up to five price levels, NYSE American Agg Lite would provide aggregated depth per security for up to ten price levels on both the bid and offer sides of the NYSE American limit order book. The proposed market data product is also similar to the NYSE American Integrated Feed,
                    <SU>10</SU>
                    <FTREF/>
                     and Nasdaq TotalView.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         BZX Rule 11.22(m) BZX Summary Depth; BYX Rule 11.22(k) BYX Summary Depth; EDGA Rule 13.8(f) EDGA Summary Depth; and EDGX Rule 13.8(f) EDGX Summary Depth. The Cboe Summary Depth offered by BZX, BYX, EDGA and EDGX are each a data feed that offers aggregated two-sided quotations for all displayed orders for up to five (5) price levels and contains the individual last sale information, market status, trading status and trade break messages.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         The NYSE American Integrated Feed provides a real-time market data in a unified view of events, in sequence, as they appear on the NYSE American matching engine. The NYSE American Integrated Feed includes depth of book order data, last sale data, and opening and closing imbalance data, as well as security status updates (
                        <E T="03">e.g.,</E>
                         trade corrections and trading halts) and stock summary messages. 
                        <E T="03">See also</E>
                         Securities Exchange Act Release No. 74127 (January 23, 2015), 80 FR 4956 (January 29, 2015) (SR-NYSEMKT-2015-06) (Notice of Filing and Immediate Effectiveness of Proposed Rule Change Establishing the NYSE American Integrated Feed Data Feed).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Nasdaq TotalView displays the full order book depth on Nasdaq, including every single quote and order at every price level in Nasdaq-, NYSE-, NYSE American- and regional-listed securities on Nasdaq. 
                        <E T="03">See https://www.nasdaq.com/solutions/nasdaq-totalview?_bt=659478569450&amp;_bk=totalview&amp;_bm=b&amp;_bn=g&amp;_bg=144616828050&amp;utm_term=totalview&amp;utm_campaign=&amp;utm_source=google&amp;utm_medium=ppc&amp;gclid=EAIaIQobChMIsZqiorTS_wIV2Y5bCh2xxQdUEAAYASAAEgKlyfD_BwE.</E>
                    </P>
                </FTNT>
                <P>The Exchange notes that the existence of alternatives to the Exchange's proposed product, including real-time consolidated data, free delayed consolidated data, and proprietary data from other sources, as well as the continued availability of the Exchange's separate data feeds, ensures that the Exchange is not unreasonably discriminatory because vendors and subscribers can elect these alternatives as their individual business cases warrant.</P>
                <P>The NYSE American Agg Lite market data feed will help to protect a free and open market by providing additional data to the marketplace and by giving investors greater choices. In addition, the proposal would not permit unfair discrimination because the data feed would be available to all vendors and subscribers through both the LCN and IGN.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>
                    In accordance with section 6(b)(8) of the Act,
                    <SU>12</SU>
                    <FTREF/>
                     the Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. Because other exchanges already offer similar products, the Exchange's proposed NYSE American Agg Lite will enhance competition. The NYSE American Agg Lite will foster 
                    <PRTPAGE P="18447"/>
                    competition by providing an alternative to similar products offered by other exchanges, including the Cboe Summary Depth.
                    <SU>13</SU>
                    <FTREF/>
                     The NYSE American Agg Lite market data feed would provide investors with a new option for receiving market data, which was a primary goal of the market data amendments adopted by Regulation NMS.
                    <SU>14</SU>
                    <FTREF/>
                     Thus, the Exchange believes the proposed rule change is necessary to permit fair competition among national securities exchanges.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         15 U.S.C. 78f(b)(8).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See supra,</E>
                         note 9.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See supra,</E>
                         note 8, at 37503.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>No written comments were solicited or received with respect to the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The Exchange has filed the proposed rule change pursuant to section 19(b)(3)(A)(iii) of the Act 
                    <SU>15</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>16</SU>
                    <FTREF/>
                     Because the proposed rule change does not: (i) significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) become operative prior to 30 days from the date on which it was filed, or such shorter time as the Commission may designate, if consistent with the protection of investors and the public interest, the proposed rule change has become effective pursuant to section 19(b)(3)(A) of the Act and Rule 19b-4(f)(6)(iii) thereunder.
                    <SU>17</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         17 CFR 240.19b-4(f)(6)(iii). In addition, Rule 19b-4(f)(6) requires a self-regulatory organization to give the Commission written notice of its intent to file the proposed rule change at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>
                    At any time within 60 days of the filing of such proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings under section 19(b)(2)(B) 
                    <SU>18</SU>
                    <FTREF/>
                     of the Act to determine whether the proposed rule change should be approved or disapproved.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         15 U.S.C. 78s(b)(2)(B).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-NYSEAMER-2024-14 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE, Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to file number SR-NYSEAMER-2024-14. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's internet website (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for website viewing and printing in the Commission's Public Reference Room, 100 F Street NE, Washington, DC 20549, on official business days between the hours of 10 a.m. and 3 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the Exchange. Do not include personal identifiable information in submissions; you should submit only information that you wish to make available publicly. We may redact in part or withhold entirely from publication submitted material that is obscene or subject to copyright protection. All submissions should refer to file number SR-NYSEAMER-2024-14 and should be submitted on or before April 3, 2024.
                </FP>
                <P>
                    For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                    <SU>19</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         17 CFR 200.30-3(a)(12).
                    </P>
                </FTNT>
                <SIG>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05254 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-99686; File No. SR-CboeBZX-2024-018]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Cboe BZX Exchange, Inc.; Notice of Filing of a Proposed Rule Change To List and Trade Shares of the Franklin Ethereum ETF, a Series of the Franklin Ethereum Trust, Under BZX Rule 14.11(e)(4), Commodity-Based Trust Shares</SUBJECT>
                <DATE>March 7, 2024.</DATE>
                <P>
                    Pursuant to section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”),
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     notice is hereby given that on February 22, 2024, Cboe BZX Exchange, Inc. (the “Exchange” or “BZX”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I, II, and III below, which Items have been prepared by the Exchange. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </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>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    Cboe BZX Exchange, Inc. (“BZX” or the “Exchange”) is filing with the Securities and Exchange Commission (“Commission” or “SEC”) a proposed rule change to list and trade shares of the Franklin Ethereum ETF (the “Fund”), a series of the Franklin Ethereum Trust (the “Trust”),
                    <SU>3</SU>
                    <FTREF/>
                     under BZX Rule 14.11(e)(4), Commodity-Based Trust Shares.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The Trust was formed as a Delaware statutory trust on February 8, 2024. The Fund is operated as a grantor trust for U.S. federal tax purposes. The Trust and the Fund have no fixed termination date.
                    </P>
                </FTNT>
                <P>
                    The text of the proposed rule change is also available on the Exchange's website (
                    <E T="03">http://markets.cboe.com/us/equities/regulation/rule_filings/bzx/</E>
                    ), at the Exchange's Office of the Secretary, and at the Commission's Public Reference Room.
                    <PRTPAGE P="18448"/>
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the Exchange included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant aspects of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>
                    The Exchange proposes to list and trade the Shares under BZX Rule 14.11(e)(4),
                    <SU>4</SU>
                    <FTREF/>
                     which governs the listing and trading of Commodity-Based Trust Shares on the Exchange.
                    <SU>5</SU>
                    <FTREF/>
                     Franklin Holdings, LLC is the sponsor of the Fund (“Sponsor”). The Shares will be registered with the Commission by means of the Trust's registration statement on Form S-1 (the “Registration Statement”).
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The Commission approved BZX Rule 14.11(e)(4) in Securities Exchange Act Release No. 65225 (August 30, 2011), 76 FR 55148 (September 6, 2011) (SR-BATS-2011-018).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Any of the statements or representations regarding the index composition, the description of the portfolio or reference assets, limitations on portfolio holdings or reference assets, dissemination and availability of index, reference asset, and intraday indicative values, or the applicability of Exchange listing rules specified in this filing to list a series of Other Securities (collectively, “Continued Listing Representations”) shall constitute continued listing requirements for the Shares listed on the Exchange.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         On February 12, 2024, the Trust filed with the Commission the Registration Statement on Form S-1, submitted to the Commission by the Sponsor on behalf of the Trust (333-277008). The descriptions of the Trust, the Shares, and the Index (as defined below) contained herein are based, in part, on information in the Registration Statement. The Registration Statement is not yet effective and the Shares will not trade on the Exchange until such time that the Registration Statement is effective.
                    </P>
                </FTNT>
                <P>
                    The Commission has historically approved or disapproved exchange filings to list and trade series of Trust Issued Receipts, including spot-based Commodity-Based Trust Shares, on the basis of whether the listing exchange has in place a comprehensive surveillance sharing agreement with a regulated market of significant size related to the underlying commodity to be held.
                    <SU>7</SU>
                    <FTREF/>
                     With this in mind, the CME Ether Futures market, which launched in February 2021, is the proper market to consider in determining whether there is a related regulated market of significant size.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 83723 (July 26, 2018), 83 FR 37579 (August 1, 2018). This proposal was subsequently disapproved by the Commission. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 83723 (July 26, 2018), 83 FR 37579 (August 1, 2018) (the “Winklevoss Order”). Prior orders from the Commission have pointed out that in every prior approval order for Commodity-Based Trust Shares, there has been a derivatives market that represents the regulated market of significant size, generally a Commodity Futures Trading Commission (the “CFTC”) regulated futures market. Further to this point, the Commission's prior orders have noted that the spot commodities and currency markets for which it has previously approved spot ETPs are generally unregulated and that the Commission relied on the underlying futures market as the regulated market of significant size that formed the basis for approving the series of Currency and Commodity-Based Trust Shares, including gold, silver, platinum, palladium, copper, and other commodities and currencies. The Commission specifically noted in the Winklevoss Order that the approval order issued related to the first spot gold ETP “was based on an assumption that the currency market and the spot gold market were largely unregulated.” 
                        <E T="03">See</E>
                         Winklevoss Order at 37592. As such, the regulated market of significant size test does not require that the spot bitcoin market be regulated in order for the Commission to approve this proposal, and precedent makes clear that an underlying market for a spot commodity or currency being a regulated market would actually be an exception to the norm. These largely unregulated currency and commodity markets do not provide the same protections as the markets that are subject to the Commission's oversight, but the Commission has consistently looked to surveillance sharing agreements with the underlying futures market in order to determine whether such products were consistent with the Act.
                    </P>
                </FTNT>
                <P>
                    Recently, the Commission issued an order granting approval for proposals to list bitcoin-based commodity trust and bitcoin-based trust issued receipts (these funds are nearly identical to the Fund, but hold bitcoin instead of ethereum) (“Spot Bitcoin ETPs”).
                    <SU>8</SU>
                    <FTREF/>
                     By way of background, in 2022 the Commission disapproved proposals 
                    <SU>9</SU>
                    <FTREF/>
                     to list Spot Bitcoin ETPs, including the Grayscale Order.
                    <SU>10</SU>
                    <FTREF/>
                     Grayscale appealed the decision with the U.S. Court of Appeals for the D.C. Circuit, which held that the Commission had failed to adequately explain its reasoning that the proposing exchange had not established that the CME bitcoin futures market was a market of significant size related to spot bitcoin, or that the “other means” asserted were sufficient to satisfy the statutory standard. As a result, the court vacated the Grayscale Order and remanded the matter to the Commission.
                    <SU>11</SU>
                    <FTREF/>
                     In considering the remand of the Grayscale Order and Spot Bitcoin ETPs, the Commission determined in the Spot Bitcoin ETP Approval Order that the CME Bitcoin Futures market is a regulated market of significant size. Specifically, the Commission stated:
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Exchange Act Release No. 99306 (January 10, 2024), 89 FR 3008 (January 17, 2024) (Self-Regulatory Organizations; NYSE Arca, Inc.; The Nasdaq Stock Market LLC; Cboe BZX Exchange, Inc.; Order Granting Accelerated Approval of Proposed Rule Changes, as Modified by Amendments Thereto, To List and Trade Bitcoin-Based Commodity-Based Trust Shares and Trust Units) (the “Spot Bitcoin ETP Approval Order”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         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. 97102 (Mar. 10, 2023), 88 FR 16055 (Mar. 15, 2023) (SR-CboeBZX-2022-035) (“VanEck Order II”) and n.11 therein for the complete list of previous proposals.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 95180 (June 29, 2022) 87 FR 40299 (July 6, 2022) (SR-NYSEArca-2021-90) (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) (the “Grayscale Order”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See Grayscale Investments, LLC</E>
                         v. 
                        <E T="03">SEC,</E>
                         82 F.4th 1239 (D.C. Cir. 2023).
                    </P>
                </FTNT>
                <EXTRACT>
                    <P>
                        [B]ased on the record before the Commission and the improved quality of the correlation analysis in the record . . . the Commission is able to conclude that fraud or manipulation that impacts prices in spot bitcoin markets would likely similarly impact CME bitcoin futures prices. And because the CME's surveillance can assist in detecting those impacts on CME bitcoin futures prices, the Exchanges' comprehensive surveillance-sharing agreement with the CME—a U.S. regulated market whose bitcoin futures market is consistently highly correlated to spot bitcoin, albeit not of “significant size” related to spot bitcoin—can be reasonably expected to assist in surveilling for fraudulent and manipulative acts and practices in the specific context of the [p]roposals.
                        <SU>12</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             
                            <E T="03">See</E>
                             the Spot Bitcoin ETP Approval Order at 3011-3012.
                        </P>
                    </FTNT>
                </EXTRACT>
                <P>As further discussed below, both the Exchange and the Sponsor believe that this proposal and the included analysis are sufficient to establish that the CME Ether Futures market represents a regulated market of significant size and that this proposal should be approved.</P>
                <HD SOURCE="HD3">Background</HD>
                <P>
                    Ethereum (also referred to as “ETH” or “ether”) is free software that is hosted on computers distributed throughout the globe. It employs an array of logic, called a protocol, to create a unified understanding of ownership, commercial activity, and business logic. This allows users to engage in commerce without the need to trust any of its participants or counterparties. Ethereum code creates verifiable and unambiguous rules that assign clear, strong property rights to create a platform for unrestrained business formation and free exchange. It is widely understood that no single intermediary or entity operates or controls the Ethereum network (referred to as “decentralization”), the transaction 
                    <PRTPAGE P="18449"/>
                    validation and recordkeeping infrastructure of which is collectively maintained by a disparate user base. The Ethereum network allows people to exchange tokens of value, or ETH, which are recorded on a distributed public recordkeeping system or ledger known as a blockchain (the “Ethereum Blockchain”), and which can be used to pay for goods and services, including computational power on the Ethereum network, or converted to fiat currencies, such as the U.S. dollar, at rates determined on digital asset exchanges or in individual peer-to-peer transactions. Furthermore, by combining the recordkeeping system of the Ethereum Blockchain with a flexible scripting language that is programmable and can be used to implement sophisticated logic and execute a wide variety of instructions, the Ethereum network is intended to act as a foundational infrastructure layer on top of which users can build their own custom software programs, as an alternative to centralized web servers. In theory, anyone can build their own custom software programs on the Ethereum network. In this way, the Ethereum network represents a project to expand blockchain deployment beyond a limited-purpose, peer-to-peer private money system into a flexible, distributed alternative computing infrastructure that is available to all. On the Ethereum network, ETH is the unit of account that users pay for the computational resources consumed by running their programs.
                </P>
                <P>
                    Heretofore, U.S. retail investors have lacked a U.S. regulated, U.S. exchange-traded vehicle to gain exposure to ETH. Instead, current options include: (i) facing the counter-party risk, legal uncertainty, technical risk, and complexity associated with accessing spot ether; or (ii) over-the-counter ether funds (“OTC ETH Funds”) with high management fees and potentially volatile premiums and discounts. Meanwhile, investors in other countries, including Germany, Switzerland and France, are able to use more traditional exchange listed and traded products (including exchange-traded funds holding physical ETH) to gain exposure to ETH. Investors across Europe have access to products which trade on regulated exchanges and provide exposure to a broad array of spot crypto assets. U.S. investors, by contrast, are left with fewer and more risky means of getting ether exposure.
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         The Exchange notes that the list of countries above is not exhaustive and that securities regulators in a number of additional countries have either approved or otherwise allowed the listing and trading of Spot Ether ETPs.
                    </P>
                </FTNT>
                <P>
                    To this point, the lack of an ETP that holds spot ETH (a “Spot Ether ETP”) exposes U.S. investor assets to significant risk because investors that would otherwise seek cryptoasset exposure through a Spot Ether ETP are forced to find alternative exposure through generally riskier means. For example, investors in OTC ETH Funds are not afforded the benefits and protections of regulated Spot Ether ETPs, resulting in retail investors suffering losses due to drastic movements in the premium/discount of OTC ETH Funds. An investor who purchased the largest OTC ETH Fund in January 2021 and held the position at the end of 2022 would have suffered a 69% loss due to the premium/discount, even if the price of ETH did not change. Many retail investors likely suffered losses due to this premium/discount in OTC ETH Fund trading; all such losses could have been avoided if a Spot Ether ETP had been available. Additionally, many U.S. investors that held their digital assets in accounts at FTX,
                    <SU>14</SU>
                    <FTREF/>
                     Celsius Network LLC,
                    <SU>15</SU>
                    <FTREF/>
                     BlockFi Inc.
                    <SU>16</SU>
                    <FTREF/>
                     and Voyager Digital Holdings, Inc.
                    <SU>17</SU>
                    <FTREF/>
                     have become unsecured creditors in the insolvencies of those entities. If a Spot Ether ETP was available, it is likely that at least a portion of the billions of dollars tied up in those proceedings would still reside in the brokerage accounts of U.S. investors, having instead been invested in a transparent, regulated, and well-understood structure—a Spot Ether ETP. To this point, approval of a Spot Ether ETP would represent a major win for the protection of U.S. investors in the cryptoasset space. The Fund, like all other series of Commodity-Based Trust Shares, is designed to protect investors against the risk of losses through fraud and insolvency that arise by holding digital assets, including ETH, on centralized platforms.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See</E>
                         FTX Trading Ltd., et al., Case No. 22-11068.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         Celsius Network LLC, et al., Case No. 22-10964.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See</E>
                         BlockFi Inc., Case No. 22-19361.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See</E>
                         Voyager Digital Holdings, Inc., et al., Case No. 22-10943.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Ether Futures ETFs</HD>
                <P>The Exchange and Sponsor applaud the Commission for allowing the launch of ETFs registered under the Investment Company Act of 1940, as amended (the “1940 Act”), that provide exposure to ether primarily through CME Ether Futures (“Ether Futures ETFs”). Allowing such products to list and trade is a productive first step in providing U.S. investors and traders with transparent, exchange-listed tools for expressing a view on ether.</P>
                <P>The structure of Ether Futures ETFs provides negative outcomes for buy and hold investors as compared to a Spot Ether ETP. Specifically, the cost of rolling CME Ether Futures contracts will cause the Ether Futures ETFs to lag the performance of ether itself and, at over a billion dollars in assets under management, would cost U.S. investors significant amounts of money on an annual basis compared to Spot Ether ETPs. Such rolling costs would not be required for Spot Ether ETPs that hold ether. Further, Ether Futures ETFs could potentially hit CME position limits, which would force an Ether Futures ETF to invest in non-futures assets for ether exposure and cause potential investor confusion and lack of certainty about what such Ether Futures ETFs are actually holding to try to get exposure to ether, not to mention completely changing the risk profile associated with such an ETF. While Ether Futures ETFs represent a useful trading tool, they are clearly a sub-optimal structure for U.S. investors that are looking for long-term exposure to ether that will unnecessarily cost U.S. investors significant amounts of money every year compared to Spot Ether ETPs and the Exchange believes that any proposal to list and trade a Spot Ether ETP should be reviewed by the Commission with this important investor protection context in mind.</P>
                <P>
                    To the extent the Commission may view differential treatment of Ether Futures ETFs and Spot Ether ETPs as warranted based on the Commission's concerns about the custody of physical ether that a Spot Ether ETP would hold (compared to cash-settled futures contracts),
                    <SU>18</SU>
                    <FTREF/>
                     the Sponsor believes this concern is mitigated to a significant degree by the custodial arrangements that the Fund has contracted with the Custodian to provide, as further outlined below. In the custody statement, the Commission stated that the fourth step that a broker-dealer could take to shield traditional securities customers and others from the risks and consequences of digital asset security fraud, theft, or loss is to establish, maintain, and enforce reasonably designed written policies, procedures, and controls for safekeeping 
                    <PRTPAGE P="18450"/>
                    and demonstrating the broker-dealer has exclusive possession or control over digital asset securities that are consistent with industry best practices to protect against the theft, loss, and unauthorized and accidental use of the private keys necessary to access and transfer the digital asset securities the broker-dealer holds in custody. While ether is not a security and the Custodian is not a broker-dealer, the Sponsor believes that similar considerations apply to the Custodian's holding of the Fund's ether. After diligent investigation, the Sponsor believes that the Custodian's policies, procedures, and controls for safekeeping, exclusively possessing, and controlling the Fund's ether holdings are consistent with industry best practices to protect against the theft, loss, and unauthorized and accidental use of the private keys. As a trust company chartered by the NYDFS, the Sponsor notes that the Custodian is subject to extensive regulation and has among longest track records in the industry of providing custodial services for digital asset private keys. Under the circumstances, therefore, to the extent the Commission believes that its concerns about the risks of spot ether custody justifies differential treatment of a Ether Futures ETF versus a Spot Ether ETP, the Sponsor believes that the fact that the Custodian employs the same types of policies, procedures, and safeguards in handling spot ether that the Commission has stated that broker-dealers should implement with respect to digital asset securities would appear to weaken the justification for treating a Ether Futures ETF compared to a Spot Ether ETP differently due to spot ether custody concerns.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         See, 
                        <E T="03">e.g.,</E>
                         Division of Investment Management Staff, Staff Statement on Funds Registered Under the Investment Company Act Investing in the Bitcoin Futures Market, May 11, 2021 (“The Bitcoin Futures market also has not presented the custody challenges associated with some cryptocurrency-based investing because the futures are cash-settled”).
                    </P>
                </FTNT>
                <P>Based on the foregoing, the Exchange and Sponsor believe that any objective review of the proposals to list Spot Ether ETPs compared to the Ether Futures ETFs would lead to the conclusion that Spot Ether ETPs should be available to U.S. investors and, as such, this proposal and other comparable proposals to list and trade Spot Ether ETPs should be approved by the Commission. Stated simply, U.S. investors will continue to lose significant amounts of money from holding Ether Futures ETFs as compared to Spot Ether ETPs, losses which could be prevented by the Commission approving Spot Ether ETPs. Additionally, any concerns related to preventing fraudulent and manipulative acts and practices related to Spot Ether ETPs would apply equally to the spot markets underlying the futures contracts held by an Ether Futures ETF. Both the Exchange and Sponsor believe that the CME Ether Futures market is a regulated market of significant size and that such manipulation concerns are mitigated, as described extensively below. After allowing the listing and trading of Ether Futures ETFs that hold primarily CME Ether Futures, however, the only consistent outcome would be approving Spot Ether ETPs on the basis that the CME Ether Futures market is a regulated market of significant size.</P>
                <P>Given the current landscape, approving this proposal (and others like it) and allowing Spot Ether ETPs to be listed and traded alongside Ether Futures ETFs and Spot Bitcoin ETPs would establish a consistent regulatory approach, provide U.S. investors with choice in product structures for ether exposure, and offer flexibility in the means of gaining exposure to ether through transparent, regulated, U.S. exchange-listed vehicles.</P>
                <HD SOURCE="HD3">
                    CME Ether Futures 
                    <SU>19</SU>
                    <FTREF/>
                </HD>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         Unless otherwise noted, all data and analysis presented in this section and referenced elsewhere in the filing has been provided by the Sponsor.
                    </P>
                </FTNT>
                <P>
                    CME began offering trading in Ether Futures in February 2021. Each contract represents 50 ETH and is based on the CME CF Ether-Dollar Reference Rate.
                    <SU>20</SU>
                    <FTREF/>
                     The contracts trade and settle like other cash-settled commodity futures contracts. Most measurable metrics related to CME Ether Futures have generally trended up since launch, although some metrics have slowed recently. For example, there were 76,293 CME Ether Futures contracts traded in July 2023 (approximately $7.3 billion) compared to 70,305 ($11.1 billion) and 158,409 ($7.5 billion) contracts traded in July 2021, and July 2022 respectively.
                    <SU>21</SU>
                    <FTREF/>
                     The Sponsor's research indicates daily correlation between the spot ETH and the CME Ether Futures is 0.998 from the period of 9/1/22 through 9/1/23.
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         The CME CF Ether-Dollar Reference Rate is based on a publicly available calculation methodology based on pricing sourced from several crypto trading platforms, including Bitstamp, Coinbase, Gemini, itBit, Kraken, and LMAX Digital.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         Source: CME, 7/31/23.
                    </P>
                </FTNT>
                <P>
                    The number of large open interest holders 
                    <SU>22</SU>
                    <FTREF/>
                     and unique accounts trading CME Ether Futures have both increased, even in the face of heightened ether price volatility.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         A large open interest holder in CME Ether Futures is an entity that holds at least 25 contracts, which is the equivalent of 1,250 ether. At a price of approximately $1,867 per ether on 7/31/2023, more than 59 firms had outstanding positions of greater than $2.3 million in CME Ether Futures.
                    </P>
                </FTNT>
                <BILCOD>BILLING CODE 8011-01-P</BILCOD>
                <GPH SPAN="3" DEEP="201">
                    <PRTPAGE P="18451"/>
                    <GID>EN13MR24.000</GID>
                </GPH>
                <GPH SPAN="3" DEEP="250">
                    <GID>EN13MR24.001</GID>
                </GPH>
                <GPH SPAN="3" DEEP="202">
                    <PRTPAGE P="18452"/>
                    <GID>EN13MR24.002</GID>
                </GPH>
                <GPH SPAN="3" DEEP="242">
                    <GID>EN13MR24.003</GID>
                </GPH>
                <BILCOD>BILLING CODE 8011-01-C</BILCOD>
                <HD SOURCE="HD3">Section 6(b)(5) and the Applicable Standards</HD>
                <P>
                    The Commission has approved numerous series of Trust Issued Receipts,
                    <SU>23</SU>
                    <FTREF/>
                     including Commodity-Based Trust Shares,
                    <SU>24</SU>
                    <FTREF/>
                     to be listed on U.S. national securities exchanges. In order for any proposed rule change from an exchange to be approved, the Commission must determine that, among other things, the proposal is consistent with the requirements of section 6(b)(5) of the Act, specifically including: (i) the requirement that a national securities exchange's rules are designed to prevent fraudulent and manipulative acts and practices; 
                    <SU>25</SU>
                    <FTREF/>
                     and (ii) the requirement that an exchange proposal be designed, in general, to protect investors and the public interest. The Exchange believes that this proposal is consistent with the requirements of section 6(b)(5) of the Act and that this filing sufficiently 
                    <PRTPAGE P="18453"/>
                    demonstrates that the CME Ether Futures market represents a regulated market of significant size and that, on the whole, the manipulation concerns previously articulated by the Commission are sufficiently mitigated to the point that they are outweighed by quantifiable investor protection issues that would be resolved by approving this proposal.
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">See</E>
                         Exchange Rule 14.11(f).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         Commodity-Based Trust Shares, as described in Exchange Rule 14.11(e)(4), are a type of Trust Issued Receipt.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         The Exchange believes that ETH is resistant to price manipulation and that “other means to prevent fraudulent and manipulative acts and practices” exist to justify dispensing with the requisite surveillance sharing agreement. The geographically diverse and continuous nature of ETH trading render it difficult and prohibitively costly to manipulate the price of ETH. The fragmentation across ETH platforms, the relatively slow speed of transactions, and the capital necessary to maintain a significant presence on each trading platform make manipulation of ETH prices through continuous trading activity challenging. To the extent that there are ETH exchanges engaged in or allowing wash trading or other activity intended to manipulate the price of ETH on other markets, such pricing does not normally impact prices on other exchange because participants will generally ignore markets with quotes that they deem non-executable. Moreover, the linkage between the ETH markets and the presence of arbitrageurs in those markets means that the manipulation of the price of ETH price on any single venue would require manipulation of the global ETH price in order to be effective. 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 ETH or OTC trading platform. As a result, the potential for manipulation on a trading platform would require overcoming the liquidity supply of such arbitrageurs who are effectively eliminating any cross-market pricing differences.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(i) Designed To Prevent Fraudulent and Manipulative Acts and Practices</HD>
                <P>
                    In order to meet this standard in a proposal to list and trade a series of Commodity-Based Trust Shares, the Commission requires that an exchange demonstrate that there is a comprehensive surveillance-sharing agreement in place 
                    <SU>26</SU>
                    <FTREF/>
                     with a regulated market of significant size. Both the Exchange and CME are members of the Intermarket Surveillance Group (“ISG”).
                    <SU>27</SU>
                    <FTREF/>
                     The only remaining issue to be addressed is whether the Ether Futures market constitutes a market of significant size, which both the Exchange and the Sponsor believe that it does. 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 manipulate the ETP, so that a surveillance-sharing agreement would assist the listing exchange 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>28</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         As previously articulated by the Commission, “The standard requires such surveillance-sharing agreements since “they provide a necessary deterrent to manipulation because they facilitate the availability of information needed to fully investigate a manipulation if it were to occur.” The Commission has emphasized that it is essential for an exchange listing a derivative securities product to enter into a surveillance-sharing agreement with markets trading underlying securities for the listing exchange to have the ability 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. 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.” The Commission has historically held that joint membership in the ISG constitutes such a surveillance sharing agreement. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 88284 (February 26, 2020), 85 FR 12595 (March 3, 2020) (SR-NYSEArca-2019-39) (the “Wilshire Phoenix Disapproval”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         For a list of the current members and affiliate members of ISG, 
                        <E T="03">see www.isgportal.com.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">See</E>
                         Wilshire Phoenix Disapproval.
                    </P>
                </FTNT>
                <P>
                    The Commission has also recognized that the “regulated market of significant size” standard is not the only means for satisfying section 6(b)(5) of the Act, specifically providing that a listing exchange could demonstrate that “other means to prevent fraudulent and manipulative acts and practices” are sufficient to justify dispensing with the requisite surveillance-sharing agreement.
                    <E T="51">29 30</E>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See</E>
                         Winklevoss Order at 37580. The Commission has also specifically noted that it “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">Id.</E>
                         at 37582.
                    </P>
                    <P>
                        <SU>30</SU>
                         The Commission allowed the launch of ETFs registered under the 1940 Act that provide exposure to ETH through CME Ether Futures (“ETH Futures ETFs”) in October 2023.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(a) Manipulation of the ETP</HD>
                <P>
                    The significant market test requires that there is a reasonable likelihood that a person attempting to manipulate the ETP would also have to trade on that market to manipulate the ETP, so that a surveillance-sharing agreement would assist the listing exchange in detecting and deterring misconduct. In light of the similarly high correlation between spot ETH/CME Ether Futures and spot bitcoin/CME Bitcoin Futures, applying the same rationale that the Commission applied to a Spot Bitcoin ETP in the Spot Bitcoin ETP Approval Order 
                    <SU>31</SU>
                    <FTREF/>
                     also indicates that this test is satisfied for this proposal. As noted above, in the Spot Bitcoin ETP Approval Order, the SEC concluded that:
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         
                        <E T="03">See</E>
                         the Spot Bitcoin ETP Approval Order.
                    </P>
                </FTNT>
                <EXTRACT>
                    <FP>
                        . . . fraud or manipulation that impacts prices in spot bitcoin markets would likely similarly impact CME bitcoin futures prices. And because the CME's surveillance can assist in detecting those impacts on CME bitcoin futures prices, the Exchanges' comprehensive surveillance-sharing agreement with the CME . . . can be reasonably expected to assist in surveilling for fraudulent and manipulative acts and practices in the specific context of the [p]roposals.
                        <SU>32</SU>
                        <FTREF/>
                    </FP>
                    <FTNT>
                        <P>
                            <SU>32</SU>
                             
                            <E T="03">See</E>
                             the Spot Bitcoin ETP Approval Order at 3011-3012.
                        </P>
                    </FTNT>
                </EXTRACT>
                <P>The assumptions from this statement are also true for CME Ether Futures. CME Ether Futures pricing is based on pricing from spot ether markets. The statement from the Spot Bitcoin ETP Approval Order that the surveillance-sharing agreement with the CME “can be reasonably expected to assist in surveilling for fraudulent and manipulative acts and practices in the specific context of the [p]roposals” makes clear that the Commission believes that CME's surveillance can capture the effects of trading on the relevant spot markets on the pricing of CME Bitcoin Futures. This same logic would extend to CME Ether Futures markets where CME's surveillance would be able to capture the effects of trading on the relevant spot markets on the pricing of CME Ether Futures.</P>
                <HD SOURCE="HD3">(b) Predominant Influence on Prices in Spot and ETH Futures</HD>
                <P>
                    The Exchange and Sponsor also believe that trading in the Shares would not be the predominant force on prices in the CME Ether Futures market for a number of reasons. First, because the Fund would not hold CME Ether Futures contracts, the only way that it could be the predominant force on prices in that market is through the spot markets that CME Ether Futures contracts use for pricing.
                    <SU>33</SU>
                    <FTREF/>
                     The Sponsor notes that ether total 24-hour spot trading volume has averaged $9.4 billion over the year ending September 1, 2023.
                    <SU>34</SU>
                    <FTREF/>
                     The Sponsor expects that the Fund would represent a very small percentage of this daily trading volume in the spot ether market even in its most aggressive projections for the Fund's assets and, thus, the Fund would not have an impact on the spot market and therefore could not be the predominant force on prices in the CME Ether Futures market. Second, much like the CME Bitcoin Futures market, the CME Ether Futures market has progressed and matured significantly. As the court found in the Grayscale Order, “Because the spot market is deeper and more liquid than the futures market, manipulation should be more difficult, not less.” The Exchange and sponsor agree with this sentiment and believe it applies equally to the spot ether and CME Ether Futures markets.
                </P>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         This logic is reflected by the court in the Grayscale Order at 17-18. Specifically, the court found that “Because Grayscale owns no futures contracts, trading in Grayscale can affect the futures market only through the spot market . . . But Grayscale holds just 3.4 percent of outstanding bitcoin, and the Commission did not suggest Grayscale can dominate the price of bitcoin.”
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         Source: TokenTerminal.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(c) Other Means To Prevent Fraudulent and Manipulative Acts and Practices</HD>
                <P>
                    As noted above, the Commission also permits a listing exchange to demonstrate that “other means to prevent fraudulent and manipulative acts and practices” are sufficient to justify dispensing with the requisite 
                    <PRTPAGE P="18454"/>
                    surveillance-sharing agreement. The Exchange and Sponsor believe that such conditions are present.
                </P>
                <P>The Exchange believes that the proposal is designed to protect investors and the public interest. Over the past several years, U.S. investor exposure to ether through OTC ETH Funds has grown into the tens of billions of dollars and more than a billion dollars of exposure through Ether Futures ETFs. With that growth, so too has grown the quantifiable investor protection issues to U.S. investors through roll costs for Ether Futures ETFs and premium/discount volatility and management fees for OTC ETH Funds. The Exchange believes that the concerns related to the prevention of fraudulent and manipulative acts and practices have been sufficiently addressed to be consistent with the Act and, to the extent that the Commission disagrees with that assertion, also believes that such concerns are now outweighed by these investor protection concerns. As such, the Exchange believes that approving this proposal (and comparable proposals) provides the Commission with the opportunity to allow U.S. investors with access to ether 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 Ether Futures ETFs and operating companies that are imperfect proxies for ether exposure; and (iv) providing an alternative to custodying spot ether.</P>
                <HD SOURCE="HD3">Franklin Ethereum ETF</HD>
                <P>
                    Delaware Trust Company is the trustee (“Trustee”). Bank of New York Mellon is the custodian for the Fund's cash and cash equivalents 
                    <SU>35</SU>
                    <FTREF/>
                     (the “Cash Custodian”) and also serves as the Fund's administrator and transfer agent (the “Administrator” or “Transfer Agent”). Coinbase Trust Company, LLC (the “Custodian”) will be responsible for custody of the Fund's ether.
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         Cash equivalents are short-term instruments with maturities of less than 3 months.
                    </P>
                </FTNT>
                <P>According to the Registration Statement, each Share will represent a fractional undivided beneficial interest in the Fund's net assets. The Fund's assets will only consist of ether, cash, and cash equivalents.</P>
                <P>
                    According to the Registration Statement, the Trust is neither an investment company registered under the 1940 Act,
                    <SU>36</SU>
                    <FTREF/>
                     nor a commodity pool for purposes of the Commodity Exchange Act (“CEA”), and neither the Trust, the Fund nor the Sponsor is subject to regulation as a commodity pool operator or a commodity trading adviser in connection with the Shares.
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         15 U.S.C. 80a-1.
                    </P>
                </FTNT>
                <P>According to the Registration Statement, the Sponsor may, from time to time, stake a portion of the Fund's assets through one or more trusted staking providers, which may include an affiliate of the Sponsor (“Staking Providers”). In consideration for any staking activity in which the Fund may engage, the Fund would receive certain staking rewards of ether tokens, which may be treated as income to the Fund.</P>
                <P>
                    When the Fund sells or redeems its Shares, it will do so in cash transactions in large blocks of 50,000 Shares (a “Creation Basket”) at the Fund's net asset value (“NAV”). A third party will use cash to buy and deliver ether to create Shares or withdraw and sell ether for cash to redeem Shares, on behalf of the Fund. For creations, authorized participants will deliver, or facilitate the delivery of, cash to the Fund's account with the Cash Custodian in exchange for Shares. Upon receipt of an approved creation order, the Sponsor, on behalf of the Fund, will submit an order to buy the amount of ether represented by a Creation Basket. Based off ether executions, the Cash Custodian will request the required cash from the authorized participant. Following receipt by the Cash Custodian of the cash from an authorized participant, the Sponsor, on behalf of the Fund, will approve an order with one or more previously onboarded trading partners to purchase the amount of ether represented by the Creation Basket.
                    <SU>37</SU>
                    <FTREF/>
                     Authorized participants may then offer Shares to the public at prices that depend on various factors, including the supply and demand for Shares, the value of the Fund's assets, and market conditions at the time of a transaction. Shareholders who buy or sell Shares during the day from their broker may do so at a premium or discount relative to the NAV of the Shares of the Fund.
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         For redemptions, the process will occur in the reverse order. Upon receipt of an approved redemption order, the Sponsor, on behalf of the Fund, will submit an order to sell the amount of ether represented by a Creation Basket and the cash proceeds will be remitted to the authorized participant when the large block of Shares is received by the Transfer Agent.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Investment Objective</HD>
                <P>
                    According to the Registration Statement and as further described below, the investment objective of the Fund is to generally reflect the performance of the price of ether before payment of the Fund's expenses and liabilities. In seeking to achieve its investment objective, the Fund will hold only ether, cash, and cash equivalents. The Fund will value its Shares daily based on the value of ether as reflected by the CME CF Ether-Dollar Reference Rate—New York Variant (the “Index”), which is an independently calculated value based on an aggregation of executed trade flow of major ether spot trading platforms. Specifically, the Index is calculated based on certain transactions of all of its constituent ether trading platforms, which are currently Bitstamp, Coinbase, itBit, Kraken, Gemini, and LMAX Digital, and which may change from time to time. If the Index is not available or the Sponsor determines, in its sole discretion, that the Index should not be used, the Fund's holdings may be fair valued in accordance with the policy approved by the Sponsor.
                    <SU>38</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         Any alternative method will only be employed on an ad hoc basis. Any permanent change to the calculation of the NAV would require a proposed rule change under Rule 19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">The Index</HD>
                <P>As described in the Registration Statement, the Fund will value its Shares daily based on the value of ether as reflected by the Index. The Index is calculated daily and aggregates the notional value of ether trading activity across major ether spot trading platforms. The Index is designed based on the International Organization of Securities Commissions (“IOSCO”) Principals for Financial Indexes. The administrator of the Index is CF Benchmarks Ltd. (the “Index Provider”).</P>
                <P>The Index serves as a once-a-day benchmark rate of the U.S. dollar price of ether (USD/ETH), calculated as of 4:00 p.m. ET. The Index aggregates the trade flow of several ether trading platforms, during an observation window between 3:00 p.m. and 4:00 p.m. ET into the U.S. dollar price of one ether at 4:00 p.m. ET. Specifically, the Index is calculated based on the “Relevant Transactions” (as defined below) of all of its constituent ether trading platforms, which are currently Coinbase, Bitstamp, Kraken, itBit, LMAX Digital and Gemini (the “Constituent Platforms”), as follows:</P>
                <P>• All Relevant Transactions are added to a joint list, recording the time of execution, trade price and size for each transaction.</P>
                <P>• The list is partitioned by timestamp into 12 equally-sized time intervals of 5 (five) minute length.</P>
                <P>
                    • For each partition separately, the volume-weighted median trade price is calculated from the trade prices and 
                    <PRTPAGE P="18455"/>
                    sizes of all Relevant Transactions, 
                    <E T="03">i.e.,</E>
                     across all Constituent Platforms. A volume-weighted median differs from a standard median in that a weighting factor, in this case trade size, is factored into the calculation.
                </P>
                <P>• The Index is then determined by the equally-weighted average of the volume medians of all partitions.</P>
                <P>The Index does not include any futures prices in its methodology. 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. ET on a Constituent Platform in the ETH/USD pair that is reported and disseminated by a Constituent Platform through its publicly available Application Programming Interface (“API”) and observed by the Index Provider.</P>
                <P>The Sponsor believes that the use of the Index is reflective of a reasonable valuation of the average spot price of ether and that resistance to manipulation is a priority aim of its design methodology. The methodology: (i) takes an observation period and divides it into equal partitions of time; (ii) then calculates the volume-weighted median of all transactions within each partition; and (iii) the value is determined from the arithmetic mean of the volume-weighted medians, equally weighted. By employing the foregoing steps, the Index thereby seeks to ensure that transactions in ether conducted at outlying prices do not have an undue effect on the value of the Index, large trades or clusters of trades transacted over a short period of time will not have an undue influence on the Index value, and the effect of large trades at prices that deviate from the prevailing price are mitigated from having an undue influence on the Index value.</P>
                <P>In addition, the Sponsor notes that an oversight function is implemented by the Index Provider in seeking to ensure that the Index is administered through codified policies for Index integrity.</P>
                <P>
                    Index data and the description of the Index are based on information made publicly available by the Index Provider on its website at 
                    <E T="03">https://www.cfbenchmarks.com.</E>
                </P>
                <HD SOURCE="HD3">Net Asset Value</HD>
                <P>NAV means the total assets of the Fund (which includes ether, cash and cash equivalents) less total liabilities of the Fund. The Administrator will determine the NAV of the Fund on each day that the Exchange is open for regular trading, as promptly as practical after 4:00 p.m. EST. The NAV of the Fund is the aggregate value of the Fund's assets less its estimated accrued but unpaid liabilities (which include accrued expenses). In determining the Fund's NAV, the Administrator values the ether held by the Fund based on the price set by the Index as of 4:00 p.m. EST. The Administrator also determines the NAV per Share.</P>
                <P>The NAV for the Fund will be calculated by the Administrator once a day and will be disseminated daily to all market participants at the same time.</P>
                <P>If the Index is not available or the Sponsor determines, in its sole discretion, that the Index should not be used, the Fund's holdings may be fair valued in accordance with the policy approved by the Sponsor.</P>
                <HD SOURCE="HD3">Availability of Information</HD>
                <P>
                    The website for the Fund, which will be publicly accessible at no charge, will contain the following information: (a) the current NAV per Share daily and the prior business day's NAV and the reported closing price; (b) the BZX Official Closing Price 
                    <SU>39</SU>
                    <FTREF/>
                     in relation to the NAV as of the time the NAV is calculated and a calculation of the premium or discount of such price against such NAV; (c) data in chart form displaying the frequency distribution of discounts and premiums of the Official Closing Price against the NAV, within appropriate ranges for each of the four previous calendar quarters (or for the life of the Fund, if shorter); (d) the prospectus; and (e) other applicable quantitative information. The aforementioned information will be published as of the close of business available on the Fund's website at 
                    <E T="03">https://www.franklintempleton.com/investments/options/exchange-traded-funds,</E>
                     or any successor thereto. The Fund will also disseminate its holdings on a daily basis on its website.
                </P>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         As defined in Rule 11.23(a)(3), the term “BZX Official Closing Price” shall mean the price disseminated to the consolidated tape as the market center closing trade.
                    </P>
                </FTNT>
                <P>The Intraday Indicative Value (“IIV”) will 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 Fund's ether holdings during the trading day, which is based on CME CF Ether-Dollar Real Time Index. The IIV disseminated during Regular Trading Hours should not be viewed as an actual real-time update of the NAV, which will be calculated only once at the end of each trading day. The IIV will be widely disseminated on a per Share basis every 15 seconds during the Exchange's Regular Trading Hours through the facilities of the consolidated tape association (CTA) and Consolidated Quotation System (CQS) high speed lines. In addition, the IIV will be available through on-line information services such as Bloomberg and Reuters.</P>
                <P>The price of ether will be made available by one or more major market data vendors, updated at least every 15 seconds during Regular Trading Hours.</P>
                <P>
                    As noted above, the Index is calculated daily and aggregates the notional value of ether trading activity across major ether spot trading platforms. Index data, the Index value, and the description of the Index are based on information made publicly available by the Index Provider on its website at 
                    <E T="03">https://www.cfbenchmarks.com.</E>
                </P>
                <P>Quotation and last sale information for ether is widely disseminated through a variety of major market data vendors, including Bloomberg and Reuters. Information relating to trading, including price and volume information, in ether is available from major market data vendors and from the trading platforms on which ether are traded. Depth of book information is also available from ether trading platforms. The normal trading hours for ether trading platforms are 24 hours per day, 365 days per year.</P>
                <P>Information regarding market price and trading volume of the Shares will be continually available on a real-time basis throughout the day on brokers' computer screens and other electronic services. Information regarding the previous day's closing price and trading volume information for the Shares will be published daily in the financial section of newspapers. Quotation and last-sale information regarding the Shares will be disseminated through the facilities of the Consolidated Tape Association (“CTA”).</P>
                <HD SOURCE="HD3">The Custodian</HD>
                <P>
                    The Custodian carefully considers the design of the physical, operational and cryptographic systems for secure storage of the Fund's private keys in an effort to lower the risk of loss or theft. The Custodian utilizes a variety of security measures to ensure that private keys necessary to transfer digital assets remain uncompromised and that the Fund maintains exclusive ownership of its assets. The Custodian will keep the private keys associated with the Fund's ether in “cold storage” 
                    <SU>40</SU>
                    <FTREF/>
                     (the “Cold 
                    <PRTPAGE P="18456"/>
                    Vault Balance”). The hardware, software, systems, and procedures of the ether Custodian may not be available or cost-effective for many investors to access directly. Only specific individuals are authorized to participate in the custody process, and no individual acting alone will be able to access or use any of the private keys. In addition, no combination of the executive officers of the Sponsor, acting alone or together, will be able to access or use any of the private keys that hold the Fund's ether.
                </P>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         The term “cold storage” refers to a safeguarding method by which the private keys corresponding to ether stored on a digital wallet are removed from any computers actively connected to the internet. Cold storage of private keys may involve keeping such wallet on a non-networked computer or 
                        <PRTPAGE/>
                        electronic device or storing the public key and private keys relating to the digital wallet on a storage device (for example, a USB thumb drive) or printed medium (for example, papyrus or paper) and deleting the digital wallet from all computers.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Creation and Redemption of Shares</HD>
                <P>
                    When the Fund sells or redeems its Shares, it will do so in cash transactions in blocks of Shares that are based on the quantity of ether attributable to each Share of the Fund (
                    <E T="03">e.g.,</E>
                     a Creation Basket) at the NAV. According to the Registration Statement, on any business day, an authorized participant may place an order to create one or more Creation Baskets. Purchase orders for cash transaction Creation Baskets must be placed by 2:00 p.m. Eastern Time, or the close of regular trading on the Exchange, whichever is earlier. The day on which an order is received is considered the purchase order date. The Administrator determines the required deposit for a given day by dividing the number of ether held by the Fund as of the opening of business on that business day, adjusted for the amount of ether constituting estimated accrued but unpaid fees and expenses of the Fund 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 number of Shares in a Creation Basket. The procedures by which an authorized participant can redeem one or more Creation Baskets mirror the procedures for the creation of Creation Baskets.
                </P>
                <P>The authorized participants will deliver only cash to create Shares and will receive only cash when redeeming Shares. Further, authorized participants will not directly or indirectly purchase, hold, deliver, or receive ether as part of the creation or redemption process or otherwise direct the Fund or a third party with respect to purchasing, holding, delivering, or receiving ether as part of the creation or redemption process.</P>
                <P>The Fund will create Shares by receiving ether from a third party that is not the authorized participant and the Fund—not the authorized participant—is responsible for selecting the third party to deliver the ether. Further, the third party will not be acting as an agent of the authorized participant with respect to the delivery of the ether to the Fund or acting at the direction of the authorized participant with respect to the delivery of the ether to the Fund. The Fund will redeem Shares by delivering ether to a third party that is not the authorized participant and the Fund—not the authorized participant—is responsible for selecting the third party to receive the ether. Further, the third party will not be acting as an agent of the authorized participant with respect to the receipt of the ether from the Fund or acting at the direction of the authorized participant with respect to the receipt of the ether from the Fund.</P>
                <P>A third party, that is unaffiliated with the Fund and the Sponsor, will use cash to buy and deliver ether to create Shares or withdraw and sell ether for cash to redeem Shares, on behalf of the Fund.</P>
                <P>The Sponsor (including its delegates) will maintain ownership and control of the Fund's ether in a manner consistent with good delivery requirements for spot commodity transactions.</P>
                <HD SOURCE="HD3">Rule 14.11(e)(4)—Commodity-Based Trust Shares</HD>
                <P>
                    The Shares will be subject to BZX Rule 14.11(e)(4), which sets forth the initial and continued listing criteria applicable to Commodity-Based Trust Shares. The Exchange represents that, for initial and continued listing, the Fund must be in compliance with Rule 10A-3 under the Act. A minimum of 100,000 Shares will be outstanding at the commencement of listing on the Exchange. The Exchange will obtain a representation that the NAV will be calculated daily and that the NAV and information about the assets of the Fund will be made available to all market participants at the same time. The Exchange notes that, as defined in Rule 14.11(e)(4)(C)(i), the Shares will be: (a) issued by a trust that holds (1) a specified commodity 
                    <SU>41</SU>
                    <FTREF/>
                     deposited with the trust, or (2) a specified commodity and, in addition to such specified commodity, cash; (b) issued by such trust in a specified aggregate minimum number in return for a deposit of a quantity of the underlying commodity and/or cash; and (c) when aggregated in the same specified minimum number, may be redeemed at a holder's request by such trust which will deliver to the redeeming holder the quantity of the underlying commodity and/or cash.
                </P>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         For purposes of Rule 14.11(e)(4), the term commodity takes on the definition of the term as provided in the Commodity Exchange Act.
                    </P>
                </FTNT>
                <P>
                    Upon termination of the Fund, the Shares will be removed from listing. The Trustee, Delaware Trust Company, is a trust company having substantial capital and surplus and the experience and facilities for handling corporate trust business, as required under Rule 14.11(e)(4)(E)(iv)(a) and that no change will be made to the trustee without prior notice to and approval of the Exchange. The Exchange also notes that, pursuant to Rule 14.11(e)(4)(F), neither the Exchange nor any agent of the Exchange shall have any liability for damages, claims, losses or expenses caused by any errors, omissions or delays in calculating or disseminating any underlying commodity value, the current value of the underlying commodity required to be deposited to the Fund in connection with issuance of Commodity-Based Trust Shares; resulting from any negligent act or omission by the Exchange, or any agent of the Exchange, or any act, condition or cause beyond the reasonable control of the Exchange, its agent, including, but not limited to, an act of God; fire; flood; extraordinary weather conditions; war; insurrection; riot; strike; accident; action of government; communications or power failure; equipment or software malfunction; or any error, omission or delay in the reports of transactions in an underlying commodity. Finally, as required in Rule 14.11(e)(4)(G), the Exchange notes that any registered market maker (“Market Maker”) in the Shares must file with the Exchange in a manner prescribed by the Exchange and keep current a list identifying all accounts for trading in an underlying commodity, related commodity futures or options on commodity futures, or any other related commodity derivatives, which the registered Market Maker may have or over which it may exercise investment discretion. No registered Market Maker shall trade in an underlying commodity, related commodity futures or options on commodity futures, or any other related commodity derivatives, in an account in which a registered Market Maker, directly or indirectly, controls trading activities, or has a direct interest in the profits or losses thereof, which has not been reported to the Exchange as required by this Rule. In addition to the existing obligations under Exchange rules regarding the production of books and records (see, 
                    <E T="03">e.g.,</E>
                     Rule 4.2), the registered Market Maker in Commodity-Based Trust Shares shall make available to the Exchange such books, records or other information pertaining to 
                    <PRTPAGE P="18457"/>
                    transactions by such entity or registered or non-registered employee affiliated with such entity for its or their own accounts for trading the underlying physical commodity, related commodity futures or options on commodity futures, or any other related commodity derivatives, as may be requested by the Exchange.
                </P>
                <P>The Exchange is able to obtain information regarding trading in the Shares and the underlying ether, Eth Futures contracts, options on Eth Futures, or any other ether derivative through members acting as registered Market Makers, in connection with their proprietary or customer trades.</P>
                <P>As a general matter, the Exchange has regulatory jurisdiction over its Members and their associated persons, which include any person or entity controlling a Member. To the extent the Exchange may be found to lack jurisdiction over a subsidiary or affiliate of a Member that does business only in commodities or futures contracts, the Exchange could obtain information regarding the activities of such subsidiary or affiliate through surveillance sharing agreements with regulatory organizations of which such subsidiary or affiliate is a member.</P>
                <HD SOURCE="HD3">Trading Halts</HD>
                <P>With respect to trading halts, the Exchange may consider all relevant factors in exercising its discretion to halt or suspend trading in the Shares. The Exchange will halt trading in the Shares under the conditions specified in BZX Rule 11.18. Trading may be halted because of market conditions or for reasons that, in the view of the Exchange, make trading in the Shares inadvisable. These may include: (1) the extent to which trading is not occurring in the ether underlying the Shares; or (2) whether other unusual conditions or circumstances detrimental to the maintenance of a fair and orderly market are present. Trading in the Shares also will be subject to Rule 14.11(e)(4)(E)(ii), which sets forth circumstances under which trading in the Shares may be halted.</P>
                <P>If the IIV or the value of the Index is not being disseminated as required, the Exchange may halt trading during the day in which the interruption to the dissemination of the IIV or the value of the Index occurs. If the interruption to the dissemination of the IIV or the value of the Index persists past the trading day in which it occurred, the Exchange will halt trading no later than the beginning of the trading day following the interruption.</P>
                <P>In addition, if the Exchange becomes aware that the NAV with respect to the Shares is not disseminated to all market participants at the same time, it will halt trading in the Shares until such time as the NAV is available to all market participants.</P>
                <HD SOURCE="HD3">Trading Rules</HD>
                <P>The Exchange deems the Shares to be equity securities, thus rendering trading in the Shares subject to the Exchange's existing rules governing the trading of equity securities. BZX will allow trading in the Shares during all trading sessions on the Exchange. The Exchange has appropriate rules to facilitate transactions in the Shares during all trading sessions. As provided in BZX Rule 11.11(a) the minimum price variation for quoting and entry of orders in securities traded on the Exchange is $0.01 where the price is greater than $1.00 per share or $0.0001 where the price is less than $1.00 per share. The Shares of the Fund will conform to the initial and continued listing criteria set forth in BZX Rule 14.11(e)(4).</P>
                <HD SOURCE="HD3">Surveillance</HD>
                <P>The Exchange represents that its surveillance procedures are adequate to properly monitor the trading of the Shares on the Exchange during all trading sessions and to deter and detect violations of Exchange rules and the applicable federal securities laws. Trading of the Shares through the Exchange will be subject to the Exchange's surveillance procedures for derivative products, including Commodity-Based Trust Shares. FINRA conducts certain cross-market surveillances on behalf of the Exchange pursuant to a regulatory services agreement. The Exchange is responsible for FINRA's performance under this regulatory services agreement.</P>
                <P>
                    The Exchange or FINRA, on behalf of the Exchange, or both, will communicate as needed regarding trading in the Shares and Ether Futures with other markets and other entities that are members of the ISG, and the Exchange, or FINRA, on behalf of the Exchange, or both, may obtain trading information regarding trading in the Shares and Ether Futures from such markets and other entities.
                    <SU>42</SU>
                    <FTREF/>
                     The Exchange may obtain information regarding trading in the Shares and Eth Futures via ISG, from other exchanges who are members or affiliates of the ISG, or with which the Exchange has entered into a comprehensive surveillance sharing agreement.
                </P>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         For a list of the current members and affiliate members of ISG, 
                        <E T="03">see www.isgportal.com.</E>
                    </P>
                </FTNT>
                <P>In addition, the Exchange also has a general policy prohibiting the distribution of material, non-public information by its employees.</P>
                <P>The issuer has represented to the Exchange that it will advise the Exchange of any failure by the Fund or the Shares to comply with the continued listing requirements, and, pursuant to its obligations under section 19(g)(1) of the Exchange Act, the Exchange will surveil for compliance with the continued listing requirements. If the Fund or the Shares are not in compliance with the applicable listing requirements, the Exchange will commence delisting procedures under Exchange Rule 14.12.</P>
                <HD SOURCE="HD3">Information Circular</HD>
                <P>
                    Prior to the commencement of trading, the Exchange will inform its members in an Information Circular of the special characteristics and risks associated with trading the Shares. Specifically, the Information Circular will discuss the following: (i) the procedures for the creation and redemption of Creation Baskets (and that the Shares are not individually redeemable); (ii) BZX Rule 3.7, which imposes suitability obligations on Exchange members with respect to recommending transactions in the Shares to customers; (iii) how information regarding the IIV and the Fund's NAV are disseminated; (iv) the risks involved in trading the Shares outside of Regular Trading Hours 
                    <SU>43</SU>
                    <FTREF/>
                     when an updated IIV will not be calculated or publicly disseminated; (v) the requirement that members deliver a prospectus to investors purchasing newly issued Shares prior to or concurrently with the confirmation of a transaction; and (vi) trading information. The Information Circular will also reference the fact that there is no regulated source of last sale information regarding ether, that the Commission has no jurisdiction over the trading of ether as a commodity, and that the CFTC has regulatory jurisdiction over the trading of Ether Futures contracts and options on Ether Futures contracts.
                </P>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         Regular Trading Hours is the time between 9:30 a.m. and 4:00 p.m. Eastern Time.
                    </P>
                </FTNT>
                <P>
                    In addition, the Information Circular will advise members, prior to the commencement of trading, of the prospectus delivery requirements applicable to the Shares. Members purchasing the Shares for resale to investors will deliver a prospectus to such investors. The Information Circular will also discuss any exemptive, no-action and interpretive relief granted by the Commission from any rules under the Act.
                    <PRTPAGE P="18458"/>
                </P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that the proposal is consistent with section 6(b) of the Act 
                    <SU>44</SU>
                    <FTREF/>
                     in general and section 6(b)(5) of the Act 
                    <SU>45</SU>
                    <FTREF/>
                     in particular in that it is 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 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.
                </P>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         15 U.S.C. 78f.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>
                    The Commission has approved numerous series of Trust Issued Receipts,
                    <SU>46</SU>
                    <FTREF/>
                     including Commodity-Based Trust Shares,
                    <SU>47</SU>
                    <FTREF/>
                     to be listed on U.S. national securities exchanges. In order for any proposed rule change from an exchange to be approved, the Commission must determine that, among other things, the proposal is consistent with the requirements of section 6(b)(5) of the Act, specifically including: (i) the requirement that a national securities exchange's rules are designed to prevent fraudulent and manipulative acts and practices; 
                    <SU>48</SU>
                    <FTREF/>
                     and (ii) the requirement that an exchange proposal be designed, in general, to protect investors and the public interest. The Exchange believes that this proposal is consistent with the requirements of section 6(b)(5) of the Act and that this filing sufficiently demonstrates that the CME Ether Futures market represents a regulated market of significant size and that, on the whole, the manipulation concerns previously articulated by the Commission are sufficiently mitigated to the point that they are outweighed by quantifiable investor protection issues that would be resolved by approving this proposal.
                </P>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         See Exchange Rule 14.11(f).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         Commodity-Based Trust Shares, as described in Exchange Rule 14.11(e)(4), are a type of Trust Issued Receipt.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         The Exchange believes that ETH is resistant to price manipulation and that “other means to prevent fraudulent and manipulative acts and practices” exist to justify dispensing with the requisite surveillance sharing agreement. The geographically diverse and continuous nature of ETH trading render it difficult and prohibitively costly to manipulate the price of ETH. The fragmentation across ETH platforms, the relatively slow speed of transactions, and the capital necessary to maintain a significant presence on each trading platform make manipulation of ETH prices through continuous trading activity challenging. To the extent that there are ETH exchanges engaged in or allowing wash trading or other activity intended to manipulate the price of ETH on other markets, such pricing does not normally impact prices on other exchange because participants will generally ignore markets with quotes that they deem non-executable. Moreover, the linkage between the ETH markets and the presence of arbitrageurs in those markets means that the manipulation of the price of ETH price on any single venue would require manipulation of the global ETH price in order to be effective. 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 ETH exchange or OTC platform. As a result, the potential for manipulation on a trading platform would require overcoming the liquidity supply of such arbitrageurs who are effectively eliminating any cross-market pricing differences.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(i) Designed To Prevent Fraudulent and Manipulative Acts and Practices</HD>
                <P>
                    In order to meet this standard in a proposal to list and trade a series of Commodity-Based Trust Shares, the Commission requires that an exchange demonstrate that there is a comprehensive surveillance-sharing agreement in place 
                    <SU>49</SU>
                    <FTREF/>
                     with a regulated market of significant size. Both the Exchange and CME are members of ISG.
                    <SU>50</SU>
                    <FTREF/>
                     The only remaining issue to be addressed is whether the ETH Futures market constitutes a market of significant size, which both the Exchange and the Sponsor believe that it does. 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 manipulate the ETP, so that a surveillance-sharing agreement would assist the listing exchange 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>51</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         As previously articulated by the Commission, “The standard requires such surveillance-sharing agreements since “they provide a necessary deterrent to manipulation because they facilitate the availability of information needed to fully investigate a manipulation if it were to occur.” The Commission has emphasized that it is essential for an exchange listing a derivative securities product to enter into a surveillance- sharing agreement with markets trading underlying securities for the listing exchange to have the ability 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. 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.” The Commission has historically held that joint membership in ISG constitutes such a surveillance sharing agreement. See Wilshire Phoenix Disapproval.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         For a list of the current members and affiliate members of ISG, see 
                        <E T="03">www.isgportal.com.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         
                        <E T="03">See</E>
                         Wilshire Phoenix Disapproval.
                    </P>
                </FTNT>
                <P>
                    The Commission has also recognized that the “regulated market of significant size” standard is not the only means for satisfying section 6(b)(5) of the Act, specifically providing that a listing exchange could demonstrate that “other means to prevent fraudulent and manipulative acts and practices” are sufficient to justify dispensing with the requisite surveillance-sharing agreement.
                    <SU>52</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         
                        <E T="03">See</E>
                         Winklevoss Order at 37580. The Commission has also specifically noted that it “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">Id.</E>
                         at 37582.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(a) Manipulation of the ETP</HD>
                <P>
                    The significant market test requires that there is a reasonable likelihood that a person attempting to manipulate the ETP would also have to trade on that market to manipulate the ETP, so that a surveillance-sharing agreement would assist the listing exchange in detecting and deterring misconduct. In light of the similarly high correlation between spot ETH/CME Ether Futures and spot bitcoin/CME Bitcoin Futures, applying the same rationale that the Commission applied to a Spot Bitcoin ETP in the Spot Bitcoin ETP Approval Order 
                    <SU>53</SU>
                    <FTREF/>
                     also indicates that this test is satisfied for this proposal. As noted above, in the Spot Bitcoin ETP Approval Order, the SEC concluded that:
                </P>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         
                        <E T="03">See</E>
                         the Spot Bitcoin ETP Approval Order.
                    </P>
                </FTNT>
                <EXTRACT>
                    <FP>
                        . . . fraud or manipulation that impacts prices in spot bitcoin markets would likely similarly impact CME bitcoin futures prices. And because the CME's surveillance can assist in detecting those impacts on CME bitcoin futures prices, the Exchanges' comprehensive surveillance-sharing agreement with the CME . . . can be reasonably expected to assist in surveilling for fraudulent and manipulative acts and practices in the specific context of the [p]roposals.
                        <SU>54</SU>
                        <FTREF/>
                    </FP>
                    <FTNT>
                        <P>
                            <SU>54</SU>
                             
                            <E T="03">See</E>
                             the Spot Bitcoin ETP Approval Order at 3011-3012.
                        </P>
                    </FTNT>
                </EXTRACT>
                <P>
                    The assumptions from this statement are also true for CME Ether Futures. CME Ether Futures pricing is based on pricing from spot ether markets. The statement from the Spot Bitcoin ETP Approval Order that the surveillance-sharing agreement with the CME “can be reasonably expected to assist in surveilling for fraudulent and manipulative acts and practices in the specific context of the [p]roposals” makes clear that the Commission 
                    <PRTPAGE P="18459"/>
                    believes that CME's surveillance can capture the effects of trading on the relevant spot markets on the pricing of CME Bitcoin Futures. This same logic would extend to CME Ether Futures markets where CME's surveillance would be able to capture the effects of trading on the relevant spot markets on the pricing of CME Ether Futures.
                </P>
                <HD SOURCE="HD3">(b) Predominant Influence on Prices in Spot and ETH Futures</HD>
                <P>
                    The Exchange and Sponsor also believe that trading in the Shares would not be the predominant force on prices in the CME Ether Futures market for a number of reasons. First, because the Fund would not hold CME Ether Futures contracts, the only way that it could be the predominant force on prices in that market is through the spot markets that CME Ether Futures contracts use for pricing.
                    <SU>55</SU>
                    <FTREF/>
                     The Sponsor notes that ether total 24-hour spot trading volume has averaged $9.4 billion over the year ending September 1, 2023.
                    <SU>56</SU>
                    <FTREF/>
                     The Sponsor expects that the Fund would represent a very small percentage of this daily trading volume in the spot ether market even in its most aggressive projections for the Fund's assets and, thus, the Fund would not have an impact on the spot market and therefore could not be the predominant force on prices in the CME Ether Futures market. Second, much like the CME Bitcoin Futures market, the CME Ether Futures market has progressed and matured significantly. As the court found in the Grayscale Order, “Because the spot market is deeper and more liquid than the futures market, manipulation should be more difficult, not less.” The Exchange and sponsor agree with this sentiment and believe it applies equally to the spot ether and CME Ether Futures markets.
                </P>
                <FTNT>
                    <P>
                        <SU>55</SU>
                         This logic is reflected by the court in the Grayscale Order at 17-18. Specifically, the court found that “Because Grayscale owns no futures contracts, trading in Grayscale can affect the futures market only through the spot market. . .But Grayscale holds just 3.4 percent of outstanding bitcoin, and the Commission did not suggest Grayscale can dominate the price of bitcoin.”
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>56</SU>
                         Source: TokenTerminal.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">(c) Other Means To Prevent Fraudulent and Manipulative Acts and Practices</HD>
                <P>As noted above, the Commission also permits a listing exchange to demonstrate that “other means to prevent fraudulent and manipulative acts and practices” are sufficient to justify dispensing with the requisite surveillance-sharing agreement. The Exchange and Sponsor believe that such conditions are present.</P>
                <P>The Exchange believes that the proposal is designed to protect investors and the public interest. Over the past several years, U.S. investor exposure to ether through OTC ETH Funds has grown into the tens of billions of dollars and more than a billion dollars of exposure through Ether Futures ETFs. With that growth, so too has grown the quantifiable investor protection issues to U.S. investors through roll costs for Ether Futures ETFs and premium/discount volatility and management fees for OTC ETH Funds. The Exchange believes that the concerns related to the prevention of fraudulent and manipulative acts and practices have been sufficiently addressed to be consistent with the Act and, to the extent that the Commission disagrees with that assertion, also believes that such concerns are now outweighed by these investor protection concerns. As such, the Exchange believes that approving this proposal (and comparable proposals) provides the Commission with the opportunity to allow U.S. investors with access to ether 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 Ether Futures ETFs and operating companies that are imperfect proxies for ether exposure; and (iv) providing an alternative to custodying spot ether.</P>
                <HD SOURCE="HD3">Commodity-Based Trust Shares</HD>
                <P>The Exchange believes that the proposed rule change is designed to prevent fraudulent and manipulative acts and practices in that the Shares will be listed on the Exchange pursuant to the initial and continued listing criteria in Exchange Rule 14.11(e)(4). The Exchange believes that its surveillance procedures are adequate to properly monitor the trading of the Shares on the Exchange during all trading sessions and to deter and detect violations of Exchange rules and the applicable federal securities laws. Trading of the Shares through the Exchange will be subject to the Exchange's surveillance procedures for derivative products, including Commodity-Based Trust Shares. The issuer has represented to the Exchange that it will advise the Exchange of any failure by the Fund or the Shares to comply with the continued listing requirements, and, pursuant to its obligations under section 19(g)(1) of the Exchange Act, the Exchange will surveil for compliance with the continued listing requirements. If the Fund or the Shares are not in compliance with the applicable listing requirements, the Exchange will commence delisting procedures under Exchange Rule 14.12. The Exchange may obtain information regarding trading in the Shares and listed ether derivatives via the ISG, from other exchanges who are members or affiliates of the ISG, or with which the Exchange has entered into a comprehensive surveillance sharing agreement.</P>
                <HD SOURCE="HD3">Availability of Information</HD>
                <P>
                    In addition to the price transparency of the Index, the Fund will provide information regarding the Fund's ETH holdings as well as additional data regarding the Fund. The website for the Fund, which will be publicly accessible at no charge, will contain the following information: (a) the current NAV per Share daily and the prior business day's NAV and the reported closing price; (b) the BZX Official Closing Price 
                    <SU>57</SU>
                    <FTREF/>
                     in relation to the NAV as of the time the NAV is calculated and a calculation of the premium or discount of such price against such NAV; (c) data in chart form displaying the frequency distribution of discounts and premiums of the Official Closing Price against the NAV, within appropriate ranges for each of the four previous calendar quarters (or for the life of the Fund, if shorter); (d) the prospectus; and (e) other applicable quantitative information. The aforementioned information will be published as of the close of business available on the Fund's website at 
                    <E T="03">https://www.franklintempleton.com/investments/options/exchange-traded-funds,</E>
                     or any successor thereto. The Fund will also disseminate its holdings on a daily basis on its website.
                </P>
                <FTNT>
                    <P>
                        <SU>57</SU>
                         As defined in Rule 11.23(a)(3), the term “BZX Official Closing Price” shall mean the price disseminated to the consolidated tape as the market center closing trade.
                    </P>
                </FTNT>
                <P>
                    The IIV will 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 Fund's ether holdings during the trading day, which is based on CME CF Ether-Dollar Real Time Index. The IIV disseminated during Regular Trading Hours should not be viewed as an actual real-time update of the NAV, which will be calculated only once at the end of each trading day. The IIV will be widely disseminated on a per Share basis every 15 seconds during the Exchange's Regular Trading Hours through the facilities of the consolidated tape association (CTA) and Consolidated Quotation System (CQS) high speed lines. In addition, the IIV will be available through on-line information services such as Bloomberg and Reuters.
                    <PRTPAGE P="18460"/>
                </P>
                <P>The price of ether will be made available by one or more major market data vendors, updated at least every 15 seconds during Regular Trading Hours.</P>
                <P>
                    As noted above, the Index is calculated daily and aggregates the notional value of ether trading activity across major ether spot trading platforms. Index data, the Index value, and the description of the Index are based on information made publicly available by the Index Provider on its website at 
                    <E T="03">https://www.cfbenchmarks.com.</E>
                </P>
                <P>Quotation and last sale information for ether is widely disseminated through a variety of major market data vendors, including Bloomberg and Reuters. Information relating to trading, including price and volume information, in ether is available from major market data vendors and from the trading platforms on which ether are traded. Depth of book information is also available from ether trading platforms. The normal trading hours for ether trading platforms are 24 hours per day, 365 days per year.</P>
                <P>Information regarding market price and trading volume of the Shares will be continually available on a real-time basis throughout the day on brokers' computer screens and other electronic services. Information regarding the previous day's closing price and trading volume information for the Shares will be published daily in the financial section of newspapers. Quotation and last-sale information regarding the Shares will be disseminated through the facilities of the CTA.</P>
                <P>In sum, the Exchange believes that this proposal is consistent with the requirements of section 6(b)(5) of the Act, that this filing sufficiently demonstrates that the CME Ether Futures market represents a regulated market of significant size, and that on the whole the manipulation concerns previously articulated by the Commission are sufficiently mitigated to the point that they are outweighed by investor protection issues that would be resolved by approving this proposal.</P>
                <P>The Exchange believes that the proposal is, in particular, designed to protect investors and the public interest. Premium and discount volatility, high fees, rolling costs, insufficient disclosures, and technical hurdles are putting U.S. investor money at risk on a daily basis that could potentially be eliminated through access to a Spot Ether ETP. As such, the Exchange believes that this proposal acts to limit the risk to U.S. investors that are increasingly seeking exposure to ether by providing direct, 1-for-1 exposure to ether in a regulated, transparent, exchange-traded vehicle, specifically by: (i) reducing premium/discount volatility; (ii) reducing management fees through meaningful competition; (iii) providing an alternative to Ether Futures ETFs which will eliminate roll cost; (iv) reducing risks associated with investing in operating companies that are imperfect proxies for ether exposure; and (v) providing an alternative to custodying spot ether. The investor protection issues for U.S. investors has grown significantly over the last several years, through roll costs for Ether Futures ETFs and premium/discount volatility and management fees for OTC ETH Funds. As discussed throughout, this growth investor protection concerns need to be reevaluated and rebalanced with the prevention of fraudulent and manipulative acts and practices concerns that previous disapproval orders have relied upon. Finally, the Exchange notes that in addition to all of the arguments herein which it believes sufficiently establishes the CME Ether Futures market as a regulated market of significant size, it is logically inconsistent to find that the CME Ether Futures market is a significant market as it relates to the CME Ether Futures market, but not a significant market as it relates to the ether spot market for the numerous reasons laid out above.</P>
                <P>For the above reasons, the Exchange believes that the proposed rule change is consistent with the requirements of section 6(b)(5) of the Act.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purpose of the Act. The Exchange notes that the proposed rule change, rather will facilitate the listing and trading of an additional exchange-traded product that will enhance competition among both market participants and listing venues, to the benefit of investors and the marketplace.</P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>The Exchange has neither solicited nor received written comments on the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    Within 45 days of the date of publication of this notice in the 
                    <E T="04">Federal Register</E>
                     or within such longer period up to 90 days (i) as the Commission may designate if it finds such longer period to be appropriate and publishes its reasons for so finding or (ii) as to which the Exchange consents, the Commission will:
                </P>
                <P>A. by order approve or disapprove such proposed rule change, or</P>
                <P>B. institute proceedings to determine whether the proposed rule change should be disapproved.</P>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-CboeBZX-2024-018 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE, Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to file number SR-CboeBZX-2024-018. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's internet website (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for website viewing and printing in the Commission's Public Reference Room, 100 F Street NE, Washington, DC 20549, on official business days between the hours of 10 a.m. and 3 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the Exchange. Do not include personal identifiable information in submissions; you should submit only information that you wish to make available publicly. We may redact in part or withhold entirely from publication submitted material that is obscene or 
                    <PRTPAGE P="18461"/>
                    subject to copyright protection. All submissions should refer to file number SR-CboeBZX-2024-018 and should be submitted on or before April 3, 2024.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>58</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>58</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05251 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-99692; File No. SR-CboeBZX-2024-019]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Cboe BZX Exchange, Inc.; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Modify the Company Listing Fees as Provided Under Exchange Rule 14.13</SUBJECT>
                <DATE>March 7, 2024.</DATE>
                <P>
                    Pursuant to section 19(b)(1) 
                    <SU>1</SU>
                    <FTREF/>
                     of the Securities Exchange Act of 1934 (“Act”) and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     notice is hereby given that on February 22, 2024, Cboe BZX Exchange, Inc. (the “Exchange” or “BZX”) filed with the Securities and Exchange Commission (the “Commission”) the proposed rule change as described in Items I, II, and III below, which Items have been prepared by the Exchange. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </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>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>Cboe BZX Exchange, Inc. (“BZX” or the “Exchange”) is filing with the Securities and Exchange Commission (“Commission” or “SEC”) a proposed rule change to modify the Company Listing Fees as provided under Exchange Rule 14.13. The text of the proposed rule change is provided in Exhibit 5.</P>
                <P>
                    The text of the proposed rule change is also available on the Exchange's website (
                    <E T="03">http://markets.cboe.com/us/equities/regulation/rule_filings/BZX/</E>
                    ), at the Exchange's Office of the Secretary, and at the Commission's Public Reference Room.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the Exchange included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant aspects of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>
                    The Exchange proposes to modify the Company Listing Fees under Rule 14.13 to provide for an application fee, entry fee, and annual fee specifically applicable to acquisition companies, as described in Rule 14.2(b) (an “Acquisition Company”). The Exchange also proposes to adopt new fees applicable to a Company that lists additional shares of an existing class of security already listed on the Exchange or an additional class of security, as further described below, (collectively referred to as “Additional Listings”).
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The Exchange initially filed the proposed fee change on January 23, 2024 (SR-CboeBZX-2024-009). On February 5, 2024, the Exchange withdrew that filing and submitted another proposal (SR-CboeBZX-2024-014). On February 9, 2024, the Exchange withdrew SR-CboeBZX-2024-014 and submitted another proposal (SR-CboeBZX-2024-015). On February 22, 2024, the Exchange withdrew SR-CboeBZX-2024-015 and submitted this proposal (SR-CboeBZX-2024-019).
                    </P>
                </FTNT>
                <P>
                    Acquisition Companies may be listed as Tier I or Tier II securities on the Exchange, provided that they meet the applicable listing requirements of the applicable tier and the additional requirements set forth in Rule 14.2(b). Currently, Acquisition Companies, among other issuers that are not otherwise identified in Rule 14.13,
                    <SU>4</SU>
                    <FTREF/>
                     are subject to the application fee, entry fee, and annual fee as provided under Rule 14.13(b)(1), (2), and (3), respectively, and are assessed the fee based on their listing as a Tier I or Tier II security.
                    <SU>5</SU>
                    <FTREF/>
                     Now, the Exchange proposes to adopt new fees specifically applicable to Acquisition Companies listed as either Tier I or Tier II securities on the Exchange. Such fee would be the same regardless of whether the Acquisition Company is listed as a Tier I or Tier II security.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         For example, the entry fees and annual fees for ETPs are cited under Rule 14.13(b)(2)(E) and 14.3(b)(3)(D), respectively. There is no application fee for ETPs listed on the Exchange.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         For Tier I securities listed on the Exchange, the application fee is $25,000, unless the Company is at any point during the Exchange's review of the application simultaneously engaged in the application process to list on another national securities exchange, in which case the application fee will be $50,000 (Rule 14.13(b)(1)); the entry fee is $100,00 less the application fee (Rule 14.13(b)(2)(A)); and the annual fee is $35,000 (Rule 14.13(b)(3)(A)). For a Tier II securities listed on the Exchange, the application fee is $25,000, unless the Company is at any point during the Exchange's review of the application simultaneously engaged in the application process to list on another national securities exchange, in which case the application fee will be $50,000 (Rule 14.13(b)(1)); the entry fee is $50,00 less the application fee (Rule 14.13(b)(2)(B)); and the annual fee is $20,000 (Rule 14.13(b)(3)(B)).
                    </P>
                </FTNT>
                <P>First, the Exchange proposes to modify the application fees. The Exchange first proposes to re-letter the existing application fee to Rule 14.13(b)(1)(A) with no substantive change, except as described below. Currently, Acquisition Companies are subject to the application fee of $25,000 or $50,000, as applicable for Tier I or Tier II securities, as provided in Rule 14.13(b)(1). The Exchange proposes to adopt Rule 14.13(b)(1)(B), which would provide that an Acquisition Company, under Rule 14.2(b), shall pay to the Exchange a modified application fee of $5,000 regardless of the Tier under which the Acquisition Company lists on the Exchange. The application fee will be $5,000, which must be submitted with the Company's application. If the Company does not list within 12 months of submitting its application, it will be assessed an additional non-refundable $5,000 application fee each 12 months thereafter to keep its application open.</P>
                <P>
                    When a Company that lists a substantial period of time after it first submitted its application, the Exchange must complete additional reviews of the application prior to the listing. These additional reviews are substantially equivalent to the review for a newly applying company and include, for example, additional reviews of individuals associated with the company, staff monitoring of disclosures and public filings by the applicant while its application is pending, and often extensive discussions with the applicant. To offset the costs associated with the ongoing monitoring and additional reviews for companies whose application remains open for an extended period, the Exchange proposes to require that an applicant that does not list within 12 months of submitting its application pay an additional $5,000 application fee each subsequent 12-month period. The 
                    <PRTPAGE P="18462"/>
                    Exchange believes that the proposed additional application fee may result in companies closing unrealistic applications rather than maintaining such applications indefinitely.
                </P>
                <P>
                    Like the proposed application fee, the proposed additional application fee for applications open greater than 12 months would be credited towards the entry fee payable upon listing if the application remains open until such listing.
                    <SU>6</SU>
                    <FTREF/>
                     Thus, under the newly adopted fees for an Acquisition Company that ultimately lists on the Exchange, there would be no difference in the overall fee paid if the application was open greater than 12 months.
                    <SU>7</SU>
                    <FTREF/>
                     If a company does not timely pay the additional application fee, its application will be closed and it will be required to submit a new application, and pay a new application fee, if it subsequently reapplies.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         proposed Exchange Rule 14.13(b)(2)(C).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Proposed Exchange Rule 14.13(b)(1)(B) provides that the application fee and any additional application fee is non-refundable.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         proposed Exchange Rule 14.13(b)(1)(B).
                    </P>
                </FTNT>
                <P>The Exchange proposes to adopt Rule 14.13(b)(1)(C), which would provide that the fees described in this Rule 14.13(b)(1)(A) and (B) shall not be applicable to Additional Listings, as described in proposed Rule 14.13(b)(2)(D) and further below. Thus, Additional Listings would not be assessed an application fee.</P>
                <P>The Exchange also proposes to modify the entry fees. Currently, Acquisition Companies are subject to an entry fee of $50,000 or $100,000 (less the application fee), as applicable for Tier I or Tier II securities, as provided in Rules 14.13(b)(2)(A) and (B). Now, the Exchange proposes to adopt an entry fee specifically applicable to Acquisition Companies under proposed Rule 14.13(b)(2)(C). Proposed Rule 14.13(b)(2)(C) would state that a Company that receives conditional approval to list an Acquisition Company as a Tier I or Tier II security shall pay to the Exchange a fee of $60,000 less the application fee, which covers both the primary equity securities and also warrants and rights, if any. This fee will be assessed on the date the Exchange provides conditional approval. The proposed fee would result in an increased fee of $10,000 for Acquisition Companies that currently list as Tier II securities on the Exchange, and decrease by $40,000 for Acquisition Companies that currently list as Tier I securities on the Exchange.</P>
                <P>
                    A Company listed as an Acquisition Company under Rule 14.2(b) (until the Company has satisfied the condition in Rule 14.2(b)(2) 
                    <SU>9</SU>
                    <FTREF/>
                     that lists an additional class of equity securities (not otherwise identified in this Rule 14.13)) is not subject to entry fees under this Rule, but is charged a non-refundable $5,000 initial application fee as described in Rule 14.13(a)(1)(B). While the Exchange believes it is unlikely to occur, Acquisition Companies that choose to list additional shares of an existing class of security already listed on the Exchange would be subject to the Additional Listings fee of $10,000 as provided in proposed Exchange Rule 14.13(2)(D). The proposed fee entry fee for Acquisition Companies under Rule 14.13(b)(2)(C) would be subject to the provisions of existing Rule 14.13(b)(2)(D),
                    <SU>10</SU>
                    <FTREF/>
                     (F),
                    <SU>11</SU>
                    <FTREF/>
                     and (G) 
                    <SU>12</SU>
                    <FTREF/>
                     in the same manner as all Tier I and Tier II securities listed on the Exchange.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Rule 14.2(b)(2) states: Within 36 months of the effectiveness of its initial public offering registration statement, or such shorter period that the company specifies in its registration statement, the Company must complete one or more business combinations having an aggregate fair market value of at least 80% of the value of the deposit account (excluding any deferred underwriters fees and taxes payable on the income earned on the deposit account) at the time of the agreement to enter into the initial combination.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Rule 14.13(b)(2)(D) provides that the Exchange Board of Directors or its designee may, in its discretion, defer or waive all or any part of the entry fee prescribed herein.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Existing Rule 14.13(b)(2)(F) (and proposed Rule 14.13(b)(2)(H) provides that the fees described in this Rule 14.13(b)(1) and (2) shall not be applicable with respect to any securities that (i) are listed on another national securities exchange but not listed on the Exchange, if the issuer of such securities transfers their listing exclusively to the Exchange; (ii) are listed on another national securities exchange and the Exchange, if the issuer of such securities ceases to maintain their listing on the other exchange and the securities instead are designated as national market system securities under Rule 14.3(d); or (iii) are listed on another national securities exchange but not listed on the Exchange, if the issuer of such securities is acquired by an unlisted company and, in connection with the acquisition, the unlisted company lists exclusively on the Exchange.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         Existing Rule 14.13(b)(2)(G) and proposed Rule 14.13(b)(2)(I) provides that the fees described in this Rule 14.13(b)(1) and (2) shall not be applicable to a Company: (i) whose securities are listed on another national securities exchange and designated as national market securities pursuant to the plan governing such securities at the time such securities are approved for listing on the Exchange; and (ii) that maintains such listing and designation after it lists such securities on the Exchange.
                    </P>
                </FTNT>
                <P>
                    The Exchange also proposes to adopt an entry fee, applicable to all Tier I and Tier II securities listed on the Exchange not otherwise identified in Rule 14.13, for Additional Listings under proposed Rule 14.13(b)(2)(D).
                    <SU>13</SU>
                    <FTREF/>
                     Specifically, a Company that lists additional shares of an existing class of security already listed on the Exchange or an additional class of primary equity securities, rights, warrants, convertible debt, preferred stock, or secondary classes of common stock, shall be required to pay to the Exchange a fee of $10,000. This fee will be assessed on the date the Exchange provides conditional approval.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         As described above, an Acquisition Company that issues an additional class of equity security (not otherwise identified in this Rule 14.13)) will not be subject to proposed Rule 14.13(b)(2)(D).,
                    </P>
                </FTNT>
                <P>The Exchange proposes to re-letter existing Rules 14.13(b)(2)(C) through (G) to accommodate the addition of proposed Rules 14.13(b)(2)(C) and (D).</P>
                <P>
                    The Exchange also proposes to modify the annual fees. Currently, Acquisition Companies are subject to an annual fee of $20,000 or $35,000, as applicable for Tier I or Tier II securities, as provided in Rules 14.13(b)(3)(A) and (B). Now, the Exchange proposes to adopt an annual fee specifically applicable to Acquisition Companies listed as Tier I or Tier II securities on the Exchange under proposed Rule 14.13(b)(3)(C). Proposed Rule 14.13(b)(3)(C) would provide that the issuer of an Acquisition Company listed on the Exchange as a Tier I or Tier II security shall pay to the Exchange an annual fee of $55,000. Therefore, the annual fee would increase by $35,000 for Acquisition Companies currently listed as Tier II securities on the Exchange, and $20,000 for Acquisition Companies currently listed as Tier I securities on the Exchange. The proposed fee would be subject to the provisions of Rule 14.13(b)(3)(D),
                    <SU>14</SU>
                    <FTREF/>
                     (E),
                    <SU>15</SU>
                    <FTREF/>
                     (F),
                    <SU>16</SU>
                    <FTREF/>
                     (G),
                    <SU>17</SU>
                    <FTREF/>
                     and 
                    <PRTPAGE P="18463"/>
                    (H) 
                    <SU>18</SU>
                    <FTREF/>
                     in the same manner as all Tier I and Tier II securities listed on the Exchange.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         Existing Rule 14.13(b)(3)(D) and proposed Rule 14.13(b)(3)(F) provides that the Exchange Board of Directors or its designee may, in its discretion, defer or waive all or any part of the annual fee prescribed herein.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         Existing Rule 14.13(b)(3)(E) and proposed Rule 14.13(b)(3)(G) provides that if a class of securities is removed from the Exchange that portion of the annual fees for such class of securities attributable to the months following the date of removal shall not be refunded except that ETPs that have liquidated and as a result are delisted from the Exchange will be prorated for the portion of the calendar year that such issue was listed on the Exchange, based on trading days listed that calendar year, and refunded.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         Existing Rule 14.13(b)(3)(F) and proposed Rule 14.13(b)(3)(H) provides that in lieu of the fees described in Rules 14.13(b)(3)(A) and (B), the annual fee shall be $15,000 for each Company: (i) whose securities are listed on another national securities exchange and designated as national market system securities pursuant to the plan governing such securities at the time such securities are approved for listing on the Exchange; and; (ii) that maintains such listing and designation after it lists such securities on the Exchange. Such annual fee shall be assessed on the first anniversary of the Company's listing on the Exchange.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         Existing Rule 14.13(b)(3)(G) and proposed Rule 14.13(b)(3)(I) provides that the fees described in this Rule 14.13(b)(3), except for pricing applicable to ETPs as set forth in sub-paragraph (C) above, shall not be applicable with respect to any securities that have had a consolidated average daily volume equal to or greater than 2 million shares per day for the immediately preceding two (2) calendar months
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         Existing Rule 14.13(b)(3)(H) and proposed Rule 14.13(b)(3)(K) provides that unless otherwise specified, the Exchange will assess all annual fees set forth in this Rule 14.13(b)(3) upon initial listing and on each anniversary of the security's listing on the Exchange.
                    </P>
                </FTNT>
                <P>Last, the Exchange proposed to adopt Rule 14.13(b)(3)(C), which would provide that the annual fees provided in existing Rules 14.13(b)(3)(A), (B), and (D) would not be applicable to Additional Listings, as described under Rule 14.13(b)(2)(D). Currently, Additional Listings would be subject to the full application and entry fee for Tier I and Tier II Securities, which total $50,000 and $100,000 respectively. Therefore, the proposed annual fee would decrease for all Tier I or Tier II securities that are Additional Listings. Additionally, the Exchange does not propose to charge any annual fee for Additional Listings by Acquisition Companies as the Exchange expects this is unlikely to occur.</P>
                <P>The Exchange proposes to re-letter existing Rule 14.13(c)(3)(C) through (H) to accommodate the addition of proposed Rules 14.13(b)(3)(C) and (D). The Exchange also proposes to modify the text of existing Rule 14.13(b)(3)(G) to reference new Rule 14.13(b)(3)(E).</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes the proposed rule change is consistent with the Act and the rules and regulations thereunder applicable to the Exchange and, in particular, the requirements of section 6(b) of the Act.
                    <SU>19</SU>
                    <FTREF/>
                     Specifically, the Exchange believes the proposed rule change is consistent with the section 6(b)(5) 
                    <SU>20</SU>
                    <FTREF/>
                     requirements that the rules of an exchange be 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. Additionally, the Exchange believes the proposed rule change is consistent with the section 6(b)(5) 
                    <SU>21</SU>
                    <FTREF/>
                     requirement that the rules of an exchange not be designed to permit unfair discrimination between customers, issuers, brokers, or dealers as well as section 6(b)(4) 
                    <SU>22</SU>
                    <FTREF/>
                     as it is designed to provide for the equitable allocation of reasonable dues, fees and other charges among its Members and other persons using its facilities.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         15 U.S.C. 78f(b)(4).
                    </P>
                </FTNT>
                <P>The Exchange first notes that its corporate listing business operates in a highly competitive market in which Companies can readily list on another national securities exchange if they deem fee levels or any other factor at a particular venue to be insufficient or excessive. The Exchange believes that Exchange Rule 14.13 reflects a competitive pricing structure designed to incentivize Companies to list new securities, which the Exchange believes will enhance competition both among Companies, issuers, and listing venues, to the benefit of investors.</P>
                <P>
                    The Exchange believes it is reasonable and not unfairly discriminatory to charge Acquisition Companies a lower application fee and lower fee for listing an additional class of security than other operating companies. The proposed application fee for Acquisition Companies is $5,000, which is less than the existing application fee for Tier I and Tier II securities listed on the Exchange, which range from $25,000 to $50,000.
                    <SU>23</SU>
                    <FTREF/>
                     Further, the proposed fee for Companies that list an additional class of security on the Exchange is $10,000, except for Acquisition Companies which are not subject to the Additional Listings fee but instead the $5,000 application fee. The Exchange's initial review of an Acquisition Company is generally less costly than conducting an initial listing review of other types of companies for a number of reasons. Specifically, review of an Acquisition Company's IPO application is generally much simpler and quicker than an application of an operating company because an Acquisition Company has no underlying operating business. For the same reason, the Exchange believes an Acquisition Company's SEC filings and IPO documentation are much less detailed and its financial statements are relatively simple. Because an Acquisition Company must not have identified the target at the time of the IPO, the Acquisition Company's registration statement does not have an operating business to describe and has no risk factors related to an operating business. Further, Acquisition Companies generally qualify as Emerging Growth Companies under section 2(a)(19) of the Act, which results in scaled requirements for narrative disclosure and financial reporting.
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">See</E>
                         Exchange Rule 14.13(b)(1).
                    </P>
                </FTNT>
                <P>
                    The Exchange acknowledges that the annual fee for Acquisition Companies listed on other exchange listing venues is typically less than the annual fee for operating companies because Acquisition Companies generally require less exchange resources than operating companies. Nonetheless, the Exchange's current annual fee for Tier I and Tier II securities are considerably lower than other competitor listing markets because those fees have not increased since they were adopted in 2011,
                    <SU>24</SU>
                    <FTREF/>
                     and remain lower than competitors in order to incentivize operating companies to list on the Exchange. Additionally, an Acquisition Company will list on the Exchange for a maximum of three years, the Exchange can only reasonably expect to assess a maximum of three years of annual fees. In contrast, operating companies may list an indefinite number of years on the Exchange, resulting in a potentially indefinite number of annual fee assessments. Therefore, the Exchange does not believe it is discriminatory to charge Acquisition Companies a higher annual fee as their potential total costs for annual fees for the life of the listed product may be significantly less than that of an operating company.
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act No. 65225 (August 30, 2011) 76 FR 55148 (September 6, 2011) (SR-BATS-2011-018) (Order Approving Proposed Rule Change To Adopt Rules for the Qualification, Listing and Delisting of Companies on the Exchange).
                    </P>
                </FTNT>
                <P>
                    The Exchange also believes that the proposal to assess an additional application fee to Acquisition Companies that do not list within 12 months of submitting its application is reasonable because it is designed to recoup a portion of the costs associated with the Exchange having to re-review the Acquisition Company. Further, as described above, all application fees would be credited to the entry fee; thus, for an Acquisition Company that ultimately lists on the Exchange, there would be no change in the collective application fee and entry fee regardless of whether the application was open for greater than 12 months. The Exchange notes that another exchange similarly provides that an additional application fee for Acquisition Companies that do not list within 12 months of submitting its application will be assessed an additional non-refundable application fee each 12 months to keep its application open.
                    <SU>25</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See</E>
                         Nasdaq Rule 5910(a)(11).
                    </P>
                </FTNT>
                <P>
                    As proposed, the entry fee applicable to an Acquisition Company would decrease for Tier I securities and increase for Tier II securities listed on the Exchange. Specifically, the entry fee 
                    <PRTPAGE P="18464"/>
                    would decrease from $100,000 to $60,000 for Tier I securities and increase from $50,000 to $60,000 for Tier II securities. The Exchange believes it is reasonable to charge Acquisition Companies the same entry fee regardless of whether they are listed as a Tier I or Tier II security given that they are treated the same. For example, each receive identical services from the Exchange upon announcing a business combination. The Exchange believes the proposed entry fee strikes a balance between the existing entry fees applicable to Acquisition Companies and is representative of the Exchange's resources spent in listing such an Acquisition Company on the Exchange. Furthermore, the Exchange competes with other listing markets, which have adopted entry fees for Acquisition Companies that are higher than those proposed by the Exchange.
                    <SU>26</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         Nasdaq Rules 5910(a)(1)(B) and 5920(a)(1)(B) provide that the entry fee for Acquisition Companies for Nasdaq Global Market and Nasdaq Capital Market, respectively, is $80,000, of which $5,000 is a non-refundable initial application fee. Section 145a of the NYSE American LLC Company Guide provides that Acquisition Companies are subject to a flat listing fee of $85,000 that will be applied at the time a company first lists as an Acquisition Company on NYSE American.
                    </P>
                </FTNT>
                <P>
                    The Exchange believes it is reasonable not unfairly discriminatory to adopt entry fees specifically applicable to Additional Listings for Companies already listed on the Exchange. Under the current fee structure, the listing of additional shares or an additional class of equity security are subject to the application fee and entry fee for a Tier I or Tier II security, as applicable. Now, the Exchange proposes to provide that no application fee will be applicable to Additional Listings, and that the entry fee will be reduced to $10,000. The Exchange believes this proposed change better reflects the value of listing an additional class of security for already listed companies and to better align such value with the Exchange's regulatory resources expended in connection with such applications. In particular, the Exchange believes it is reasonable to charge only a non-refundable entry fee of $10,000 because the company listing an additional class or additional shares of the same class of security on the Exchange is already subject to Exchange rules, including the applicable corporate governance requirements. Accordingly, the Exchange expects to expend less regulatory resources qualifying an additional class of equity security for listing. The Exchange also notes that other exchanges have similarly adopted separate fees applicable to an additional class of equity security, which are higher than the Exchange's proposed fee.
                    <SU>27</SU>
                    <FTREF/>
                     The Exchange believes its proposal that Additional Listings be charged no application or annual fee is reasonable and equitable because it will result in lower costs to all companies seeking to list Additional Listings on the Exchange.
                    <SU>28</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">See e.g.</E>
                        <E T="03">,</E>
                         Nasdaq Global Market Rule 5910(a)(1)(A)(ii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         The fees applicable to listings as set forth in Rule 14.13(b) are applicable based on security listed on the exchange rather than the Company itself.
                    </P>
                </FTNT>
                <P>The Exchange continues to believe that differentiating fees applicable to Acquisition Companies and operating companies from ETPs is reasonable because of the unique and different characteristics of listings ETPs. For example, certain types of ETPs by their nature require multiple listings. The existing fee structure for such listings is designed to encourage issuers of such products to list multiple ETPs on the Exchange at a reduced cost. As such, the Exchange believes it is reasonable and non-discriminatory to assess fees to ETPs in a different manner than Acquisition Companies and operating companies.</P>
                <P>Finally, the Exchange believes that the proposed conforming changes to re-letter existing rules and update applicable rule references will maintain the clarity of the Exchange's rulebook, to the benefit of all investors.</P>
                <P>Given the foregoing, the Exchange believes the proposed fee amendments are consistent with the Act.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The market for listing services is extremely competitive and listed companies may freely choose alternative venues based on the aggregate fees assessed, and the value provided by each listing.</P>
                <P>The proposal changes the application fee, entry fee, and annual fee for Acquisition Companies listed on the Exchange and also changes the application and entry fee applicable to Additional Listings on the Exchange. The Exchange does not believe that these changes will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. Specifically, the proposal to assess application fees, entry fees, and annual fees specific to Acquisition Companies listed on the Exchange is reasonable because it provides a tailored fee structure to such companies in a similar manner as other exchanges.</P>
                <P>The Exchange believes it is reasonable to charge Acquisition Companies the same entry fee regardless of whether they are listed as a Tier I or Tier II security given that they are treated the same. For example, each receive identical services from the Exchange upon announcing a business combination. The Exchange believes the proposed entry fee strikes a balance between the existing entry fees applicable to Acquisition Companies, and is representative of the Exchange's resources spent in listing such an Acquisition Company on the Exchange.</P>
                <P>The Exchange continues to believe that differentiating fees applicable to Acquisition Companies and operating companies from ETPs is reasonable because of the unique and different characteristics of listings ETPs. For example, certain types of ETPs by their nature require multiple listings. The existing fee structure for such listings is designed to encourage issuers of such products to list multiple ETPs on the Exchange at a reduced cost. As such, the Exchange believes it is reasonable and non-discriminatory to assess fees to ETPs in a different manner than Acquisition Companies and operating companies.</P>
                <P>
                    The Exchange does not believe that the proposal to adopt entry fees specifically applicable to Additional Listings for Companies already listed on the Exchange will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. Under the current fee structure, the listing of additional shares or an additional class of equity security are subject to the application fee and entry fee for a Tier I or Tier II security, as applicable. Now, the Exchange proposes to provide that no application fee will be applicable to Additional Listings, and that the entry fee will be reduced to $10,000. The Exchange believes this proposed change better reflects the value of listing an additional class of security for already listed companies and to better align such value with the Exchange's regulatory resources expended in connection with such applications. In particular, the Exchange believes it is reasonable to charge only a non-refundable entry fee of $10,000 because the company listing an additional class or additional shares of the same class of security on the Exchange is already subject to Exchange rules, including the applicable corporate governance requirements. Accordingly, the Exchange expects to expend less regulatory resources qualifying an 
                    <PRTPAGE P="18465"/>
                    additional class of equity security for listing. The Exchange also notes that other exchanges have similarly adopted separate fees applicable to an additional class of equity security, which are higher than the Exchange's proposed fee.
                    <SU>29</SU>
                    <FTREF/>
                     The Exchange believes its proposal that Additional Listings be charged no application or annual fee is reasonable and equitable because it will result in lower costs to all companies seeking to list Additional Listings on the Exchange.
                    <SU>30</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See e.g.</E>
                        <E T="03">,</E>
                         Nasdaq Global Market Rule 5910(a)(1)(A)(ii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         The fees applicable to listings as set forth in Rule 14.13(b) are applicable based on security listed on the exchange rather than the Company itself.
                    </P>
                </FTNT>
                <P>The Exchange believes that the proposed amendments do not encumber competition for listings with other listing venues, which are similarly free to set their fees. Rather, it reflects competition among listing venues and will further enhance competition.</P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>The Exchange neither solicited nor received comments on the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The foregoing rule change has become effective pursuant to section 19(b)(3)(A) of the Act 
                    <SU>31</SU>
                    <FTREF/>
                     and paragraph (f) of Rule 19b-4 
                    <SU>32</SU>
                    <FTREF/>
                     thereunder. At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission will institute proceedings to determine whether the proposed rule change should be approved or disapproved.
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         17 CFR 240.19b-4(f).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-CboeBZX-2024-019 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE, Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to file number SR-CboeBZX-2024-019. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's internet website (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for website viewing and printing in the Commission's Public Reference Room, 100 F Street NE, Washington, DC 20549, on official business days between the hours of 10 a.m. and 3 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the Exchange. Do not include personal identifiable information in submissions; you should submit only information that you wish to make available publicly. We may redact in part or withhold entirely from publication submitted material that is obscene or subject to copyright protection. All submissions should refer to file number SR-CboeBZX-2024-019 and should be submitted on or before April 3, 2024.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>33</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>33</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05256 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-99687; File No. SR-PHLX-2023-40]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Nasdaq PHLX LLC; Notice of Withdrawal of a Proposed Rule Change, as Modified by Partial Amendment No. 1, To Amend Equity 4, Rules 3301A and 3301B To Establish New “Contra Midpoint Only” and “Contra Midpoint Only With Post-Only” Order Types and To Make Other Corresponding Changes to the Rulebook</SUBJECT>
                <DATE>March 7, 2024.</DATE>
                <P>
                    On August 28, 2023, Nasdaq PHLX LLC (“Exchange”) filed with the Securities and Exchange Commission (“Commission”), pursuant to section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change to amend Equity 4, Rules 3301A and 3301B to establish new “Contra Midpoint Only” and “Contra Midpoint Only with Post-Only” order types and to make other corresponding changes to the rulebook. The proposed rule change was published for comment in the 
                    <E T="04">Federal Register</E>
                     on September 8, 2023.
                    <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. 98280 (Sept. 1, 2023), 88 FR 62129. Comments received by the Commission on the proposed rule change are available on the Commission's website at: 
                        <E T="03">https://www.sec.gov/comments/sr-phlx-2023-40/srphlx202340.htm.</E>
                    </P>
                </FTNT>
                <P>
                    On September 26, 2023, pursuant to section 19(b)(2) of the 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 November 2, 2023, the Exchange filed Partial Amendment No. 1 to the proposed rule change.
                    <SU>6</SU>
                    <FTREF/>
                     On December 5, 2023, the Commission published Partial Amendment No. 1 for notice and comment and instituted proceedings under section 19(b)(2)(B) of the Act 
                    <SU>7</SU>
                    <FTREF/>
                     to determine whether to approve or 
                    <PRTPAGE P="18466"/>
                    disapprove the proposed rule change, as modified by Partial Amendment No. 1.
                    <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. 98528, 88 FR 67846 (Oct. 2, 2023). The Commission designated December 7, 2023, as the date by which the Commission shall approve or disapprove, or institute proceedings to determine whether to approve or disapprove, the proposed rule change.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Amendment No. 1 is available at 
                        <E T="03">https://www.sec.gov/comments/sr-phlx-2023-40/srphlx202340-293100-713082.pdf.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         15 U.S.C. 78s(b)(2)(B).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 99083, 88 FR 85964 (Dec. 11, 2023).
                    </P>
                </FTNT>
                <P>
                    On March 4, 2024, the Exchange withdrew the proposed rule change, as modified by Partial Amendment No. 1 (File No. SR-PHLX-2023-40).
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         17 CFR 200.30-3(a)(12).
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>9</SU>
                    </P>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05252 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-99689; File No. SR-NYSE-2024-12]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; New York Stock Exchange LLC; Notice of Filing and Immediate Effectiveness of Proposed Rule Change To Establish the NYSE Aggregated Lite Market Data Feed</SUBJECT>
                <DATE>March 7, 2024.</DATE>
                <P>
                    Pursuant to section 19(b)(1) 
                    <SU>1</SU>
                    <FTREF/>
                     of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>2</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>3</SU>
                    <FTREF/>
                     notice is hereby given that on February 27, 2024, New York Stock Exchange LLC (“NYSE” or the “Exchange”) filed with the Securities and Exchange Commission (the “Commission”) the proposed rule change as described in Items I, II, and III below, which Items have been prepared by the self-regulatory organization. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         15 U.S.C. 78a.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to establish the NYSE Aggregated Lite (“NYSE Agg Lite”) market data feed. The proposed rule change is available on the Exchange's website at 
                    <E T="03">www.nyse.com,</E>
                     at the principal office of the Exchange, and at the Commission's Public Reference Room.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and the Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>The Exchange proposes to establish the NYSE Agg Lite market data feed. The NYSE Agg Lite is a NYSE-only frequency-based depth of book market data feed of the NYSE's limit order book for up to ten (10) price levels on both the bid and offer sides of the order book for securities traded on the Exchange and for which the Exchange reports quotes and trades under the Consolidated Tape Association (“CTA”) Plan or the Nasdaq/UTP Plan. NYSE Agg Lite would be a compilation of limit order data that the Exchange would provide to vendors and subscribers. As proposed, the NYSE Agg Lite data feed would be updated no less frequently than once per second. The NYSE Agg Lite would include depth of book order data as well as security status messages. The security status message would inform subscribers of changes in the status of a specific security, such as trading halts, short sale restriction, etc. In addition, the NYSE Agg Lite would also include order imbalance information prior to the opening and closing of trading.</P>
                <P>The Exchange proposes to offer NYSE Agg Lite after receiving requests from vendors and subscribers that would like to receive the data described above in an integrated fashion at a pre-defined publication interval, in this case updates no less than once per second. An aggregated data feed may provide greater efficiencies and reduce errors for vendors and subscribers that currently choose to integrate the above data into a single offering after receiving it from the Exchange through existing products and adjust the publication frequency based on a subscriber's needs. The Exchange believes that providing vendors and subscribers with the option to subscribe to a market data product that integrates a subset of data from existing products and where such aggregated data is published at a pre-defined interval, thus lowering bandwidth, infrastructure and operational requirements, would allow vendors and subscribers to choose the best solution for their specific business needs. The Exchange notes that publishing only the top ten price levels on both the bid and offer sides of the order book where such data is communicated to subscribers at a pre-defined interval would reduce the overall volume of messages required to be consumed by subscribers when compared to a full order-by-order data feed or a full depth of book data feed. Providing data in this format and publication frequency would make NYSE Agg Lite more easily consumable by vendors and subscribers, especially for display purposes.</P>
                <P>The Exchange proposes to offer NYSE Agg Lite through the Exchange's Liquidity Center Network (“LCN”), a local area network in the Exchange's Mahwah, New Jersey data center that is available to users of the Exchange's co-location services. The Exchange would also offer NYSE Agg Lite through the ICE Global Network (“IGN”), through which all other users and members access the Exchange's trading and execution systems and other proprietary market data products.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that the proposed rule change is consistent with section 6(b) 
                    <SU>4</SU>
                    <FTREF/>
                     of the Act (“Act”), in general, and furthers the objectives of section 6(b)(5) 
                    <SU>5</SU>
                    <FTREF/>
                     of the Act, in particular, in that it is 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 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 it is not designed to permit unfair discrimination among customers, brokers, or dealers. This proposal is in keeping with those principles in that it promotes increased transparency through the dissemination of NYSE Agg Lite to those interested in receiving it.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>
                    The Exchange also believes this proposal is consistent with section 6(b)(5) of the Act because it protects investors and the public interest and promotes just and equitable principles of trade by providing investors with new options for receiving market data as requested by market data vendors and subscribers. The proposed rule change would benefit investors by facilitating their prompt access to the frequency-
                    <PRTPAGE P="18467"/>
                    based depth of book information contained in the NYSE Agg Lite market data feed.
                </P>
                <P>
                    The Exchange also believes that the proposed rule change is consistent with section 11(A) of the Act 
                    <SU>6</SU>
                    <FTREF/>
                     in that it supports (i) fair competition among brokers and dealers, among exchange markets, and between exchange markets and markets other than exchange markets and (ii) the availability of information with respect to quotations for and transactions in securities to brokers, dealers, and investors. Furthermore, the proposed rule change is consistent with Rule 603 of Regulation NMS,
                    <SU>7</SU>
                    <FTREF/>
                     which provides that any national securities exchange that distributes information with respect to quotations for or transactions in an NMS stock do so on terms that are not unreasonably discriminatory. The NYSE Agg Lite market data feed would be accessed and subscribed to on a voluntary basis, in that neither the Exchange nor market data vendors are required by any rule or regulation to make this data available. Accordingly, vendors and subscribers can discontinue their use at any time and for any reason.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         15 U.S.C. 78k-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         17 CFR 242.603.
                    </P>
                </FTNT>
                <P>In adopting Regulation NMS, the Commission granted self-regulatory organizations (“SROs”) and broker dealers increased authority and flexibility to offer new and unique market data to consumers of such data. It was believed that this authority would expand the amount of data available to users and consumers of such data and also spur innovation and competition for the provision of market data. The Exchange believes that NYSE Agg Lite is precisely the sort of market data product that the Commission envisioned when it adopted Regulation NMS. The Commission concluded that Regulation NMS would itself further the Act's goals of facilitating efficiency and competition:</P>
                <EXTRACT>
                    <P>
                        Efficiency is promoted when broker-dealers who do not need the data beyond the prices, sizes, market center identifications of the NBBO and consolidated last sale information are not required to receive (and pay for) such data. The Commission also believes that efficiency is promoted when broker-dealers may choose to receive (and pay for) additional market data based on their own internal analysis of the need for such data.
                        <SU>8</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 51808 (June 9, 2005), 70 FR 37496 (June 29, 2005) (Regulation NMS Adopting Release).
                        </P>
                    </FTNT>
                </EXTRACT>
                <P>
                    In addition, NYSE Agg Lite removes impediments to and perfects the mechanism of a free and open market and a national market system by providing investors with alternative market data and would compete with similar market data products currently offered by the four U.S. equities exchanges operated by Cboe Exchange, Inc.—Cboe BZX Exchange, Inc. (“BZX”), Cboe BYX Exchange, Inc. (“BYX”), Cboe EDGA Exchange, Inc. (“EDGA”), and Cboe EDGX Exchange, Inc. (“EDGX”), each of which offers a market data product called BZX Summary Depth, BYX Summary Depth, EDGA Summary Depth and EDGX Summary Depth, respectively (collectively, the “Cboe Summary Depth”).
                    <SU>9</SU>
                    <FTREF/>
                     Similar to Cboe Summary Depth, NYSE Agg Lite can be utilized by vendors and subscribers to quickly access and distribute aggregated order book data. As noted above, NYSE Agg Lite, similar to Cboe Summary Depth, would provide aggregated depth per security, including the bid, ask and share quantity for orders received by NYSE, except unlike Cboe Summary Depth, which provides aggregated depth per security for up to five price levels, NYSE Agg Lite would provide aggregated depth per security for up to ten price levels on both the bid and offer sides of the NYSE limit order book. The proposed market data product is also similar to the NYSE Integrated Feed,
                    <SU>10</SU>
                    <FTREF/>
                     and Nasdaq TotalView.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         BZX Rule 11.22(m) BZX Summary Depth; BYX Rule 11.22(k) BYX Summary Depth; EDGA Rule 13.8(f) EDGA Summary Depth; and EDGX Rule 13.8(f) EDGX Summary Depth. The Cboe Summary Depth offered by BZX, BYX, EDGA and EDGX are each a data feed that offers aggregated two-sided quotations for all displayed orders for up to five (5) price levels and contains the individual last sale information, market status, trading status and trade break messages.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         The NYSE Integrated Feed provides a real-time market data in a unified view of events, in sequence, as they appear on the NYSE matching engine. The NYSE Integrated Feed includes depth of book order data, last sale data, and opening and closing imbalance data, as well as security status updates (
                        <E T="03">e.g.,</E>
                         trade corrections and trading halts) and stock summary messages. 
                        <E T="03">See also</E>
                         Securities Exchange Act Release No. 74128 (January 23, 2015), 80 FR 4951 (January 29, 2015) (SR-NYSE-2015-03) (Notice of Filing and Immediate Effectiveness of Proposed Rule Change Establishing the NYSE Integrated Feed Data Feed).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Nasdaq TotalView displays the full order book depth on Nasdaq, including every single quote and order at every price level in Nasdaq-, NYSE-, NYSE American- and regional-listed securities on Nasdaq. 
                        <E T="03">See https://www.nasdaq.com/solutions/nasdaq-totalview?_bt=659478569450&amp;_bk=totalview&amp;_bm=b&amp;_bn=g&amp;_bg=144616828050&amp;utm_term=totalview&amp;utm_campaign=&amp;utm_source=google&amp;utm_medium=ppc&amp;gclid=EAIaIQobChMIsZqiorTS_wIV2Y5bCh2xxQdUEAAYASAAEgKlyfD_BwE</E>
                        .
                    </P>
                </FTNT>
                <P>The Exchange notes that the existence of alternatives to the Exchange's proposed product, including real-time consolidated data, free delayed consolidated data, and proprietary data from other sources, as well as the continued availability of the Exchange's separate data feeds, ensures that the Exchange is not unreasonably discriminatory because vendors and subscribers can elect these alternatives as their individual business cases warrant.</P>
                <P>The NYSE Agg Lite market data feed will help to protect a free and open market by providing additional data to the marketplace and by giving investors greater choices. In addition, the proposal would not permit unfair discrimination because the data feed would be available to all vendors and subscribers through both the LCN and IGN.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>
                    In accordance with section 6(b)(8) of the Act,
                    <SU>12</SU>
                    <FTREF/>
                     the Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. Because other exchanges already offer similar products, the Exchange's proposed NYSE Agg Lite will enhance competition. The NYSE Agg Lite will foster competition by providing an alternative to similar products offered by other exchanges, including the Cboe Summary Depth.
                    <SU>13</SU>
                    <FTREF/>
                     The NYSE Agg Lite market data feed would provide investors with a new option for receiving market data, which was a primary goal of the market data amendments adopted by Regulation NMS.
                    <SU>14</SU>
                    <FTREF/>
                     Thus, the Exchange believes the proposed rule change is necessary to permit fair competition among national securities exchanges.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         15 U.S.C. 78f(b)(8).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See supra,</E>
                         note 9.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See supra,</E>
                         note 8, at 37503.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>No written comments were solicited or received with respect to the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The Exchange has filed the proposed rule change pursuant to section 19(b)(3)(A)(iii) of the Act 
                    <SU>15</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>16</SU>
                    <FTREF/>
                     Because the proposed rule change does not: (i) significantly affect the protection of investors or the public interest; (ii) impose any significant burden on 
                    <PRTPAGE P="18468"/>
                    competition; and (iii) become operative prior to 30 days from the date on which it was filed, or such shorter time as the Commission may designate, if consistent with the protection of investors and the public interest, the proposed rule change has become effective pursuant to section 19(b)(3)(A) of the Act and Rule 19b-4(f)(6)(iii) thereunder.
                    <SU>17</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         17 CFR 240.19b-4(f)(6)(iii). In addition, Rule 19b-4(f)(6) requires a self-regulatory organization to give the Commission written notice of its intent to file the proposed rule change at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>
                    At any time within 60 days of the filing of such proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings under section 19(b)(2)(B) 
                    <SU>18</SU>
                    <FTREF/>
                     of the Act to determine whether the proposed rule change should be approved or disapproved.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         15 U.S.C. 78s(b)(2)(B).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-NYSE-2024-12 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE, Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to file number SR-NYSE-2024-12. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's internet website (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for website viewing and printing in the Commission's Public Reference Room, 100 F Street NE, Washington, DC 20549, on official business days between the hours of 10 a.m. and 3 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the Exchange. Do not include personal identifiable information in submissions; you should submit only information that you wish to make available publicly. We may redact in part or withhold entirely from publication submitted material that is obscene or subject to copyright protection. All submissions should refer to file number SR-NYSE-2024-12 and should be submitted on or before April 3, 2024.
                </FP>
                <P>
                    For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                    <SU>19</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         17 CFR 200.30-3(a)(12).
                    </P>
                </FTNT>
                <SIG>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05253 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-99691; File No. SR-NYSECHX-2024-08]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; NYSE Chicago, Inc.; Notice of Filing and Immediate Effectiveness of Proposed Rule Change To Establish the NYSE Chicago Aggregated Lite Market Data Feed</SUBJECT>
                <DATE>March 7, 2024.</DATE>
                <P>
                    Pursuant to section 19(b)(1) 
                    <SU>1</SU>
                    <FTREF/>
                     of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>2</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>3</SU>
                    <FTREF/>
                     notice is hereby given that, on February 27, 2024, the NYSE Chicago, Inc. (“NYSE Chicago” or the “Exchange”) filed with the Securities and Exchange Commission (the “Commission”) the proposed rule change as described in Items I, II, and III below, which Items have been prepared by the self-regulatory organization. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         15 U.S.C. 78a.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to establish the NYSE Chicago Aggregated Lite (“NYSE Chicago Agg Lite”) market data feed. The proposed rule change is available on the Exchange's website at 
                    <E T="03">www.nyse.com,</E>
                     at the principal office of the Exchange, and at the Commission's Public Reference Room.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and the Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>The Exchange proposes to establish the NYSE Chicago Agg Lite market data feed. The NYSE Chicago Agg Lite is a NYSE Chicago-only frequency-based depth of book market data feed of the NYSE Chicago's limit order book for up to ten (10) price levels for securities traded on the Exchange and for which the Exchange reports quotes and trades under the Consolidated Tape Association (“CTA”) Plan or the Nasdaq/UTP Plan. NYSE Chicago Agg Lite would be a compilation of limit order data that the Exchange would provide to vendors and subscribers. As proposed, the NYSE Chicago Agg Lite data feed would be updated no less frequently than once per second. The NYSE Chicago Agg Lite would include depth of book order data as well as security status messages. The security status message would inform subscribers of changes in the status of a specific security, such as trading halts, short sale restriction, etc.</P>
                <P>
                    The Exchange proposes to offer NYSE Chicago Agg Lite after receiving requests from vendors and subscribers that would like to receive the data described above in an integrated fashion at a pre-defined publication interval, in this case 
                    <PRTPAGE P="18469"/>
                    updates no less than once per second. An aggregated data feed may provide greater efficiencies and reduce errors for vendors and subscribers that currently choose to integrate the above data into a single offering after receiving it from the Exchange through existing products and adjust the publication frequency based on a subscriber's needs. The Exchange believes that providing vendors and subscribers with the option to subscribe to a market data product that integrates a subset of data from existing products and where such aggregated data is published at a pre-defined interval, thus lowering bandwidth, infrastructure and operational requirements, would allow vendors and subscribers to choose the best solution for their specific business needs. The Exchange notes that publishing only the top ten price levels on both the bid and offer sides of the order book where such data is communicated to subscribers at a pre-defined interval would reduce the overall volume of messages required to be consumed by subscribers when compared to a full order-by-order data feed or a full depth of book data feed. Providing data in this format and publication frequency would make NYSE Chicago Agg Lite more easily consumable by vendors and subscribers, especially for display purposes.
                </P>
                <P>The Exchange proposes to offer NYSE Chicago Agg Lite through the Exchange's Liquidity Center Network (“LCN”), a local area network in the Exchange's Mahwah, New Jersey data center that is available to users of the Exchange's co-location services. The Exchange would also offer NYSE Chicago Agg Lite through the ICE Global Network (“IGN”), through which all other users and members access the Exchange's trading and execution systems and other proprietary market data products.</P>
                <P>The Exchange will file a separate rule filing to establish fees for NYSE Chicago Agg Lite. The Exchange will announce the implementation date of this proposed rule change by Trader Update, which, subject to the effectiveness of this proposed rule change, will be no later than the second quarter of 2024.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that the proposed rule change is consistent with section 6(b) 
                    <SU>4</SU>
                    <FTREF/>
                     of the Act (“Act”), in general, and furthers the objectives of section 6(b)(5) 
                    <SU>5</SU>
                    <FTREF/>
                     of the Act, in particular, in that it is 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 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 it is not designed to permit unfair discrimination among customers, brokers, or dealers. This proposal is in keeping with those principles in that it promotes increased transparency through the dissemination of NYSE Chicago Agg Lite to those interested in receiving it.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>The Exchange also believes this proposal is consistent with section 6(b)(5) of the Act because it protects investors and the public interest and promotes just and equitable principles of trade by providing investors with new options for receiving market data as requested by market data vendors and subscribers. The proposed rule change would benefit investors by facilitating their prompt access to the frequency-based depth of book information contained in the NYSE Chicago Agg Lite market data feed.</P>
                <P>
                    The Exchange also believes that the proposed rule change is consistent with section 11(A) of the Act 
                    <SU>6</SU>
                    <FTREF/>
                     in that it supports (i) fair competition among brokers and dealers, among exchange markets, and between exchange markets and markets other than exchange markets and (ii) the availability of information with respect to quotations for and transactions in securities to brokers, dealers, and investors. Furthermore, the proposed rule change is consistent with Rule 603 of Regulation NMS,
                    <SU>7</SU>
                    <FTREF/>
                     which provides that any national securities exchange that distributes information with respect to quotations for or transactions in an NMS stock do so on terms that are not unreasonably discriminatory. The NYSE Chicago Agg Lite market data feed would be accessed and subscribed to on a voluntary basis, in that neither the Exchange nor market data vendors are required by any rule or regulation to make this data available. Accordingly, vendors and subscribers can discontinue their use at any time and for any reason.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         15 U.S.C. 78k-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         17 CFR 242.603.
                    </P>
                </FTNT>
                <P>In adopting Regulation NMS, the Commission granted self-regulatory organizations (“SROs”) and broker dealers increased authority and flexibility to offer new and unique market data to consumers of such data. It was believed that this authority would expand the amount of data available to users and consumers of such data and also spur innovation and competition for the provision of market data. The Exchange believes that NYSE Chicago Agg Lite is precisely the sort of market data product that the Commission envisioned when it adopted Regulation NMS. The Commission concluded that Regulation NMS would itself further the Act's goals of facilitating efficiency and competition:</P>
                <EXTRACT>
                    <P>
                        Efficiency is promoted when broker-dealers who do not need the data beyond the prices, sizes, market center identifications of the NBBO and consolidated last sale information are not required to receive (and pay for) such data. The Commission also believes that efficiency is promoted when broker-dealers may choose to receive (and pay for) additional market data based on their own internal analysis of the need for such data.
                        <SU>8</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 51808 (June 9, 2005), 70 FR 37496 (June 29, 2005) (Regulation NMS Adopting Release).
                        </P>
                    </FTNT>
                </EXTRACT>
                <P>
                    In addition, NYSE Chicago Agg Lite removes impediments to and perfects the mechanism of a free and open market and a national market system by providing investors with alternative market data and would compete with similar market data products currently offered by the four U.S. equities exchanges operated by Cboe Exchange, Inc.—Cboe BZX Exchange, Inc. (“BZX”), Cboe BYX Exchange, Inc. (“BYX”), Cboe EDGA Exchange, Inc. (“EDGA”), and Cboe EDGX Exchange, Inc. (“EDGX”), each of which offers a market data product called BZX Summary Depth, BYX Summary Depth, EDGA Summary Depth and EDGX Summary Depth, respectively (collectively, the “Cboe Summary Depth”).
                    <SU>9</SU>
                    <FTREF/>
                     Similar to Cboe Summary Depth, NYSE Chicago Agg Lite can be utilized by vendors and subscribers to quickly access and distribute aggregated order book data. As noted above, NYSE Chicago Agg Lite, similar to Cboe Summary Depth, would provide aggregated depth per security, including the bid, ask and share quantity for orders received by NYSE Chicago, except unlike Cboe Summary Depth, which provides aggregated depth per security for up to five price levels, NYSE Chicago Agg Lite would provide aggregated depth per security for up to ten price levels on both the bid and offer 
                    <PRTPAGE P="18470"/>
                    sides of the NYSE Chicago limit order book. The proposed market data product is also similar to the NYSE Chicago Integrated Feed,
                    <SU>10</SU>
                    <FTREF/>
                     and Nasdaq TotalView.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         BZX Rule 11.22(m) BZX Summary Depth; BYX Rule 11.22(k) BYX Summary Depth; EDGA Rule 13.8(f) EDGA Summary Depth; and EDGX Rule 13.8(f) EDGX Summary Depth. The Cboe Summary Depth offered by BZX, BYX, EDGA and EDGX are each a data feed that offers aggregated two-sided quotations for all displayed orders for up to five (5) price levels and contains the individual last sale information, market status, trading status and trade break messages.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         The NYSE Chicago Integrated Feed provides a real-time market data in a unified view of events, in sequence, as they appear on the NYSE Chicago matching engine. The NYSE Chicago Integrated Feed includes top of book and depth of book order data, last sale data, and security status updates (
                        <E T="03">e.g.,</E>
                         trade corrections and trading halts) and stock summary messages. 
                        <E T="03">See also</E>
                         Securities Exchange Act Release No. 87389 (October 23, 2019), 84 FR 57904 (October 29, 2019) (SR-NYSECHX-2019-15) (Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Establish the NYSE Chicago BBO, NYSE Chicago Trades and NYSE Chicago Integrated Feed Market Data Feeds).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Nasdaq TotalView displays the full order book depth on Nasdaq, including every single quote and order at every price level in Nasdaq-, NYSE-, NYSE American- and regional-listed securities on Nasdaq. 
                        <E T="03">See https://www.nasdaq.com/solutions/nasdaq-totalview?_bt=659478569450&amp;_bk=totalview&amp;_bm=b&amp;_bn=g&amp;_bg=144616828050&amp;utm_term=totalview&amp;utm_campaign=&amp;utm_source=google&amp;utm_medium=ppc&amp;gclid=EAIaIQobChMIsZqiorTS_wIV2Y5bCh2xxQdUEAAYASAAEgKlyfD_BwE.</E>
                    </P>
                </FTNT>
                <P>The Exchange notes that the existence of alternatives to the Exchange's proposed product, including real-time consolidated data, free delayed consolidated data, and proprietary data from other sources, as well as the continued availability of the Exchange's separate data feeds, ensures that the Exchange is not unreasonably discriminatory because vendors and subscribers can elect these alternatives as their individual business cases warrant.</P>
                <P>The NYSE Chicago Agg Lite market data feed will help to protect a free and open market by providing additional data to the marketplace and by giving investors greater choices. In addition, the proposal would not permit unfair discrimination because the data feed would be available to all vendors and subscribers through both the LCN and IGN.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>
                    In accordance with section 6(b)(8) of the Act,
                    <SU>12</SU>
                    <FTREF/>
                     the Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. Because other exchanges already offer similar products, the Exchange's proposed NYSE Chicago Agg Lite will enhance competition. The NYSE Chicago Agg Lite will foster competition by providing an alternative to similar products offered by other exchanges, including the Cboe Summary Depth.
                    <SU>13</SU>
                    <FTREF/>
                     The NYSE Chicago Agg Lite market data feed would provide investors with a new option for receiving market data, which was a primary goal of the market data amendments adopted by Regulation NMS.
                    <SU>14</SU>
                    <FTREF/>
                     Thus, the Exchange believes the proposed rule change is necessary to permit fair competition among national securities exchanges.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         15 U.S.C. 78f(b)(8).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See supra,</E>
                         note 9.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See supra,</E>
                         note 8, at 37503.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>No written comments were solicited or received with respect to the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The Exchange has filed the proposed rule change pursuant to section 19(b)(3)(A)(iii) of the Act 
                    <SU>15</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>16</SU>
                    <FTREF/>
                     Because the proposed rule change does not: (i) significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) become operative prior to 30 days from the date on which it was filed, or such shorter time as the Commission may designate, if consistent with the protection of investors and the public interest, the proposed rule change has become effective pursuant to section 19(b)(3)(A) of the Act and Rule 19b-4(f)(6)(iii) thereunder.
                    <SU>17</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         17 CFR 240.19b-4(f)(6)(iii). In addition, Rule 19b-4(f)(6) requires a self-regulatory organization to give the Commission written notice of its intent to file the proposed rule change at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>
                    At any time within 60 days of the filing of such proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings under section 19(b)(2)(B) 
                    <SU>18</SU>
                    <FTREF/>
                     of the Act to determine whether the proposed rule change should be approved or disapproved.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         15 U.S.C. 78s(b)(2)(B).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-NYSECHX-2024-08 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE, Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to file number SR-NYSECHX-2024-08. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's internet website (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for website viewing and printing in the Commission's Public Reference Room, 100 F Street NE, Washington, DC 20549, on official business days between the hours of 10 a.m. and 3 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the Exchange. Do not include personal identifiable information in submissions; you should submit only information that you wish to make available publicly. We may redact in part or withhold entirely from publication submitted material that is obscene or subject to copyright protection. All submissions should refer to file number SR-NYSECHX-2024-08 and should be submitted on or before April 3, 2024.
                </FP>
                <P>
                    For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                    <SU>19</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         17 CFR 200.30-3(a)(12).
                    </P>
                </FTNT>
                <SIG>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05255 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18471"/>
                <AGENCY TYPE="N">SOCIAL SECURITY ADMINISTRATION</AGENCY>
                <DEPDOC>[Docket No: SSA-2024-0007]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Proposed Request and Comment 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 revisions of OMB-approved information collections, and one new collection for OMB-approval.</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>(OMB) Office of Management and Budget, Attn: Desk Officer for SSA, Fax: 202-395-6974.</P>
                <P>
                    (SSA) Social Security Administration, OLCA, Attn: Reports Clearance Director, Mail Stop 3253 Altmeyer, 6401 Security Blvd., Baltimore, MD 21235, Fax: 833-410-1631, Email address: 
                    <E T="03">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>
                     by clicking on Currently under Review—Open for Public Comments and choosing to click on one of SSA's published items. Please reference Docket ID Number [SSA-2024-0007] in your submitted response.
                </P>
                <P>I. 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 May 13, 2024. Individuals can obtain copies of the collection instruments by writing to the above email address.</P>
                <P>
                    <E T="03">1. Request for Waiver of Overpayment Recovery and Request for Change in Overpayment Recovery Rate—20 CFR 404.502, 404.506-404.512, 416.550-416.558, 416.570-416.571—0960-0037.</E>
                     When Social Security beneficiaries and Supplemental Security Income (SSI) recipients receive an overpayment, they must return the extra money. These beneficiaries and recipients can use Form SSA-632-BK, Request for Waiver of Overpayment Recovery, to request a waiver from repaying their overpayment. Beneficiaries and recipients can also use Form SSA-634, Request for Change in Overpayment Recovery, to request a change to the monthly recovery rate of their overpayment. The respondents must provide financial information to help the agency determine how much the overpaid person can afford to repay each month. The respondents are individuals who are overpaid Social Security or SSI payments who are requesting: (1) a waiver of recovery of an overpayment, or (2) a lesser rate of withholding.
                </P>
                <P>The Social Security Administration (SSA) is requesting public comments on this information collection. We encourage members of the public to provide their feedback and comments on the following matters outlined in the notice:</P>
                <P>a. How can SSA most effectively ask questions related to determining whether or not a respondent is “without fault” in a manner that is minimally burdensome? Specifically, we are soliciting feedback on replacing the free-form response option, “Tell us what you know about why the overpayment may have happened” with a set of structured response options intended to reflect common reasons related to a failure to timely report a change to the agency. SSA is seeking comments on adding the following response options for which the respondent would be able to pick the choice that fits best:</P>
                <P>• I did not know that I needed to report the change that SSA says caused the overpayment.</P>
                <P>• I did not know about the change that SSA says caused the overpayment.</P>
                <P>• I did not believe it was a significant enough change to report.</P>
                <P>• I knew that I was supposed to report the change but chose not to report it.</P>
                <P>• I thought I reported the change, or I tried to report the change but was unable to.</P>
                <P>• I do not believe SSA is correct that there was a change.</P>
                <P>• I forgot to report the change.</P>
                <P>• I don't know.</P>
                <P>• Other (this option would allow for a fill-in text box to include the reason).</P>
                <P>b. Currently, Question #2, part 2 of the SSA-632 asks for the reason for requesting an overpayment waiver through a write-in text box. Please comment on other ways for us to request this information.</P>
                <P>c. How can SSA revise the SSA-632, associated notice, or agency business processes to most effectively create a minimally burdensome collection of the questions we currently ask on the form?</P>
                <P>d. How can SSA revise the form, associated notice, or agency business processes to most effectively minimize the burdensome collection requirements for individuals who have already pursued an appeal in good faith, but still have an overpayment as the result of receiving benefits under the statutory benefits continuation policy?</P>
                <P>e. Please provide other suggestions for improving the design or communication on the form or associated notices to reduce burden on respondents.</P>
                <P>f. Should SSA provide a mechanism on the form to allow for respondents to jointly request a reconsideration and a waiver on the same form?</P>
                <P>g. Are there less burdensome ways SSA can ask respondents about the expenses they incur, or are there alternative ways for us to ask whether or not a claimant uses their income for ordinary and necessary living expenses?</P>
                <P>h. Should SSA require documentation for expenses when an individual's alleged expenses are not unusually high?</P>
                <P>i. In your experience, are there particular payment rules that, are particularly difficult to comply with or understand, resulting in overpayments?</P>
                <P>j. Does SSA's burden estimate of 60 minutes accurately reflect the beginning-to-end time burden associated with this form? As stated in our documentation, the current time burden may include reviewing and understanding relevant notices; reading and understanding instructions; tracking down records and documentation; filling out the form; consulting with any third parties to help navigate form requirements (to include time spent by third-parties separate from the respondent's time spent); and any travel associated with the collection.</P>
                <P>Your input on these items is valuable to us as we strive to improve our processes and better serve the public. In addition, we encourage you to comment on any other aspects of this information collection.</P>
                <P>
                    <E T="03">Type of Request:</E>
                     Revision of an OMB-approved information collection.
                    <PRTPAGE P="18472"/>
                </P>
                <GPOTABLE COLS="8" OPTS="L2,nj,tp0,i1" CDEF="s50,10,10,10,10,10,10,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
                            <LI>total annual</LI>
                            <LI>burden</LI>
                            <LI>(hours)</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>theoretical</LI>
                            <LI>hourly cost</LI>
                            <LI>amount</LI>
                            <LI>(dollars) *</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>wait time in</LI>
                            <LI>field office</LI>
                            <LI>or for</LI>
                            <LI>teleservice</LI>
                            <LI>centers</LI>
                            <LI>(minutes) **</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual
                            <LI>opportunity</LI>
                            <LI>cost</LI>
                            <LI>(dollars) ***</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">SSA-632—Request for Waiver of Overpayment Recovery (If completing entire paper form, including the AFI authorization)</ENT>
                        <ENT>400,000</ENT>
                        <ENT>1</ENT>
                        <ENT>60</ENT>
                        <ENT>400,000</ENT>
                        <ENT>* $12.81</ENT>
                        <ENT>** 21</ENT>
                        <ENT>*** $6,917,400</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">SSA-634—Request for Change in Overpayment Recovery Rate (Completing paper form)</ENT>
                        <ENT>100,000</ENT>
                        <ENT>1</ENT>
                        <ENT>45</ENT>
                        <ENT>75,000</ENT>
                        <ENT>* 12.81</ENT>
                        <ENT>** 21</ENT>
                        <ENT>*** 1,409,100</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Totals</ENT>
                        <ENT>500,000</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>475,000</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>*** 8,326,500</ENT>
                    </ROW>
                    <TNOTE>
                        * We based this figure on the average DI payments based on SSA's current FY 2023 data (
                        <E T="03">https://www.ssa.gov/legislation/2023factsheet.pdf</E>
                        ).
                    </TNOTE>
                    <TNOTE>** We based this figure on averaging both the average FY 2023 wait times for field offices and teleservice centers, based on SSA's current management information data.</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>
                <P>
                    <E T="03">2. Development of Participation in a Vocational Rehabilitation or Similar Program—20 CFR 404.316(c), 404.337(c), 404.352(d), 404.1586(g), 404.1596, 404.1597(a), 404.327, 404.328, 416.1321(d), 416.1331(a)-(b), and 416.1338, 416.1402—0960-0282.</E>
                     State Disability Determination Services (DDS) determine if Social Security disability payment recipients whose disability ceased and who participate in vocational rehabilitation programs may continue to receive disability payments. To do this, DDSs needs information about the recipients, the types of program participation, and the services they receive under the rehabilitation program. SSA uses Form SSA-4290 to collect this information. The respondents are State employment networks, vocational rehabilitation agencies, or other providers of educational or job training services.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Revision of an OMB-approved information collection.
                </P>
                <GPOTABLE COLS="8" OPTS="L2,nj,tp0,i1" CDEF="s50,10,10,10,10,10,10,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
                            <LI>total annual</LI>
                            <LI>burden</LI>
                            <LI>(hours)</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>theoretical</LI>
                            <LI>hourly cost</LI>
                            <LI>amount</LI>
                            <LI>(dollars) *</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>wait time in</LI>
                            <LI>field office</LI>
                            <LI>or for</LI>
                            <LI>teleservice</LI>
                            <LI>centers</LI>
                            <LI>(minutes) **</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual
                            <LI>opportunity</LI>
                            <LI>cost</LI>
                            <LI>(dollars) ***</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">SSA-4290-F5 (By mail)</ENT>
                        <ENT>2,400</ENT>
                        <ENT>1</ENT>
                        <ENT>40</ENT>
                        <ENT>1,600</ENT>
                        <ENT>* $18.52</ENT>
                        <ENT>** N/A</ENT>
                        <ENT>*** $30,372.80</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">SSA-4290-F5 (Telephone)</ENT>
                        <ENT>600</ENT>
                        <ENT>1</ENT>
                        <ENT>30</ENT>
                        <ENT>300</ENT>
                        <ENT>* 18.52</ENT>
                        <ENT>** N/A</ENT>
                        <ENT>*** 5,741.20</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Totals</ENT>
                        <ENT>3,000</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>1,900</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>*** 36,114.00</ENT>
                    </ROW>
                    <TNOTE>* We based this figure on average Social and Human Service Assistant's hourly salary, as reported by Bureau of Labor Statistics.</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>
                <P>
                    <E T="03">3. Application to Collect a Fee for Payee Services—20 CFR 404.2040a &amp; 416.640a—0960-0719.</E>
                     Sections 205(j) and 1631(a) of the Act allow SSA to authorize certain organizational representative payees to collect a fee for providing payee services. Before an organization may collect this fee, they complete and submit Form SSA-445. SSA uses the information to determine whether to authorize or deny permission to collect fees for payee services. The respondents are private sector businesses, or State and local government offices, applying to become a fee-for-service organizational representative payee.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Revision of an OMB-approved information collection.
                </P>
                <GPOTABLE COLS="7" OPTS="L2,nj,tp0,i1" CDEF="s50,10,10,10,10,10,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
                            <LI>total annual</LI>
                            <LI>burden</LI>
                            <LI>(hours)</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>theoretical</LI>
                            <LI>hourly cost</LI>
                            <LI>amount</LI>
                            <LI>(dollars) *</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual
                            <LI>opportunity</LI>
                            <LI>cost</LI>
                            <LI>(dollars) **</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Private sector business</ENT>
                        <ENT>80</ENT>
                        <ENT>1</ENT>
                        <ENT>13</ENT>
                        <ENT>17</ENT>
                        <ENT>* $17.41</ENT>
                        <ENT>** $296</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">State/local government offices</ENT>
                        <ENT>10</ENT>
                        <ENT>1</ENT>
                        <ENT>10</ENT>
                        <ENT>2</ENT>
                        <ENT>* 17.41</ENT>
                        <ENT>** 35</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Totals</ENT>
                        <ENT>90</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>19</ENT>
                        <ENT/>
                        <ENT>** 331</ENT>
                    </ROW>
                    <TNOTE>
                        * We based these figures on average Personal Care and Service Occupations hourly wages, as reported by Bureau of Labor Statistics data (
                        <E T="03">https://www.bls.gov/oes/current/oes390000.htm</E>
                        ).
                        <PRTPAGE P="18473"/>
                    </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>
                <P>
                    <E T="03">4. Screen Pop—20 CFR 401.45—0960-0790.</E>
                     Section 205(a) of the Social Security Act requires SSA to verify the identity of individuals who request a record or information pertaining to themselves, and to establish procedures for disclosing personal information. SSA established Screen Pop, an automated telephone process, to speed up verification for such individuals. Accessing Screen Pop, callers enter their Social Security number (SSN) using their telephone keypad or speech technology prior to speaking with a National 800 Number Network (N8NN) agent. The automated Screen Pop application collects the SSN and routes it to the “Start New Call” Customer Help and Information (CHIP) screen. Functionality for the Screen Pop application ends once the SSN connects to the CHIP screen and the SSN routes to the agent's screen. When the call connects to the N8NN agent, the agent can use the SSN to access the caller's record as needed. The respondents for this collection are individuals who contact SSA's N8NN to speak with an agent.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Revision of an OMB-approved information collection.
                </P>
                <GPOTABLE COLS="8" OPTS="L2,nj,tp0,i1" CDEF="s50,10C,12C,12C,12C,12C,12C,16C">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            Modality of
                            <LI>completion</LI>
                        </CHED>
                        <CHED H="1">Number of respondents</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
                            <LI>burden</LI>
                            <LI>(hours)</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>theoretical</LI>
                            <LI>hourly cost</LI>
                            <LI>amount</LI>
                            <LI>(dollars) *</LI>
                        </CHED>
                        <CHED H="1">
                            Average wait
                            <LI>time for </LI>
                            <LI>teleservice</LI>
                            <LI>centers</LI>
                            <LI>(minutes) **</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual
                            <LI>opportunity</LI>
                            <LI>cost (dollars) ***</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Screen Pop</ENT>
                        <ENT>51,933,760</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>865,563</ENT>
                        <ENT>* $29.76</ENT>
                        <ENT>** 17</ENT>
                        <ENT>*** $463,664,609</ENT>
                    </ROW>
                    <TNOTE>
                        * We based this figure on average U.S. worker's hourly wages, as reported by Bureau of Labor Statistics data (
                        <E T="03">https://www.bls.gov/oes/current/oes_nat.htm#00-00000</E>
                        ).
                    </TNOTE>
                    <TNOTE>** We based this figure on the average FY 2023 wait times for teleservice centers, based on SSA's current management information data.</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.</E>
                    </TNOTE>
                </GPOTABLE>
                <P>
                    <E T="03">5. Electronic Consent Based Social Security Number Verification—20 CFR 400.100—0960-0817.</E>
                     The electronic Consent Based Social Security Number Verification (eCBSV) is a fee-based SSN verification service which allows permitted entities (a financial institution as defined by Section 509 of the Gramm-Leach-Bliley Act. 42 U.S.C. 405b(b)(4), Public Law 115-174, Title II, 215(b)(4), or service provider, subsidiary, affiliate, agent, subcontractor, or assignee of a financial institution), to verify that an individual's name, date of birth (DOB), and SSN match our records based on the SSN holder's signed, including electronic consent in connection with a credit transaction or any circumstance described in section 604 of the Fair Credit Reporting Act (15 U.S.C. 1681b).
                </P>
                <HD SOURCE="HD1">Background</HD>
                <P>SSA established the eCBSV service in response to section 215 of the Economic Growth, Regulatory Relief, and Consumer Protection Act of 2018 (Banking Bill), Public Law 115-174. Permitted entities are able to submit the SSN, name, and DOB of the number holder in connection with a credit transaction, or any circumstances described in Section 604 of the Fair Credit Reporting Act to SSA for verification via an application programming interface. eCBSV allows SSA to verify permitted entities who submit SSN, name, and DOB Matches, or does not match the data contained in SSA's records. After obtaining number holders' consents, a permitted entity submits the names, DOBs, and SSNs of number holders to the eCBSV service. SSA matches the information against our Master File, using SSN, name, and DOB. The eCBSV service responds in real time with a match, or no match indicator (and an indicator if our records show that the number holder died). SSA does not provide specific information on what data elements did not match, nor does SSA provide any SSNs or other identifiable information. The verification does not authenticate the identity of the number holders or conclusively prove the number holders we verify are who they are claiming to be.</P>
                <HD SOURCE="HD1">Consent Requirements</HD>
                <P>Under the eCBSV process, the permitted entities does not submit the number holder's consent forms to SSA. SSA requires each permitted entity to retain a valid consent for each SSN verification request submitted for a period of 5 years. SSA permits the permitted entities to retain the consent in an electronic format, and SSA requires a wet or electronic signature on the consent. Permitted entities may request verification of a number holder's SSN on behalf of a financial institution pursuant to the terms of the Banking Bill, the user agreement between SSA and the PE, and the SSN Holder's consent. The permitted entity ensures the financial institution agrees to the terms in the user agreement to only use the SSN verification for the purpose stated in the consent, and prohibits public entities from further using or disclosing the SSN verification. This relationship is subject to the terms in the user agreement between SSA and the PE.</P>
                <HD SOURCE="HD1">Compliance Review</HD>
                <P>SSA requires each permitted entity to undergo compliance reviews which are conducted by an SSA approved certified public accountant (CPA). The compliance reviews ensure the permitted entities meet all terms and conditions of the user agreement, including obtaining valid consent from number holders. The permitted entities pays all compliance review costs through the eCBSV fees. In general, SSA requests annual reviews with additional reviews as necessary. The CPA follows review standards established by the American Institute of Certified Public Accountants and contained in the Generally Accepted Government Auditing Standards (GAGAS).</P>
                <P>
                    Initially, SSA only allowed 10 permitted entities access to use the service, with an estimated 307,000,000 requests. Now, with the open enrollment, eCBSV is available to all interested permitted entities, as defined in Section 215 of the Banking Bill with an estimated annual 77,000,000 requests. The respondents are permitted entities; members of the public who consent to SSN verifications; and CPAs 
                    <PRTPAGE P="18474"/>
                    who provide compliance review services.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Revision of an OMB-approved information collection.
                </P>
                <GPOTABLE COLS="7" OPTS="L2,nj,tp0,i1" CDEF="s50,12,12,12,12,12,14">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Requirement</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Frequency of
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>burden per</LI>
                            <LI>response</LI>
                            <LI>(minutes)</LI>
                        </CHED>
                        <CHED H="1">
                            Estimated
                            <LI>total annual</LI>
                            <LI>burden</LI>
                            <LI>(hours)</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>theoretical</LI>
                            <LI>hourly cost</LI>
                            <LI>amount</LI>
                            <LI>(dollars) *</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual
                            <LI>opportunity</LI>
                            <LI>cost</LI>
                            <LI>(dollars) **</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">(a) People whose SSNs SSA will verify—Reading and Signing</ENT>
                        <ENT>76,000,000</ENT>
                        <ENT>1</ENT>
                        <ENT>3</ENT>
                        <ENT>3,800,000</ENT>
                        <ENT>* $12.81</ENT>
                        <ENT>** $48,678,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">(a) Sending in the verification request, calling our system, getting a response</ENT>
                        <ENT>76,000,000</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>1,266,667</ENT>
                        <ENT>* 41.39</ENT>
                        <ENT>** 52,427,347</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">(c) CPA Compliance Review and Report ***</ENT>
                        <ENT>21</ENT>
                        <ENT>1</ENT>
                        <ENT>4,800</ENT>
                        <ENT>1,680</ENT>
                        <ENT>* 41.70</ENT>
                        <ENT>** 70,056</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Totals</ENT>
                        <ENT>152,000,021</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>5,068,347</ENT>
                        <ENT/>
                        <ENT>** 101,175,403</ENT>
                    </ROW>
                    <TNOTE>
                        * We based these figures on average Business and Financial operations occupations (
                        <E T="03">https://www.bls.gov/oes/current/oes130000.htm</E>
                        ), and Accountants and Auditors hourly salaries (
                        <E T="03">https://www.bls.gov/oes/current/oes132011.htm</E>
                        ), as reported by Bureau of Labor Statistics data, and average DI payments, as reported in SSA's disability insurance payment data (
                        <E T="03">https://www.ssa.gov/legislation/2023factsheet.pdf</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>
                    <TNOTE>
                        *** The enrollment process occurs automatically through the eCBSV Customer Connection, and entails providing consent for SSA to verify the EIN; electronically signing the eCBSV User Agreement, and the permitted entities certification; selecting their annual tier level; and linking to 
                        <E T="03">pay.gov</E>
                         to make payment for services.
                    </TNOTE>
                    <TNOTE>**** There will be one CPA firm (an SSA-approved contractor) to conduct compliance reviews and prepare written reports of findings on the 113 permitted entities.</TNOTE>
                </GPOTABLE>
                <HD SOURCE="HD1">Cost Burden</HD>
                <P>The public cost burden depends on the number of permitted entities using the service and the annual transaction volume. SSA based the current tier fee schedule below on 20 participating public entities in fiscal year (FY) 2023 submitting an anticipated annual volume of 65 million transactions. For FY 2024, we are maintaining the current tier structure, based our analysis, which estimated 20 participating public entities with an anticipated annual volume of 52 million. Since our analysis and initial estimate, one permitted entity noted the potential for a significant increase in volume in FY 2024. The total cost for developing and operating the service is $62 million through FY 2023. Of this amount, $37 million remains unrecovered/unreimbursed. The current subscription tier structure and associated fees intend to recover these costs over a four-year period, assuming projected enrollments and transaction volumes meet these projections. SSA uses the fee to allocate for forecasted systems and operational expenses; agency oversight; and overhead necessary to sustain the service.</P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s50,r200,12">
                    <TTITLE>
                        <E T="01">e</E>
                        CBSV Tier Fee Schedule
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">Tier</CHED>
                        <CHED H="1">Annual transaction threshold</CHED>
                        <CHED H="1">Annual fee</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">1</ENT>
                        <ENT>Up to 10,000 (1-10,000)</ENT>
                        <ENT>$7,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2</ENT>
                        <ENT>Up to 200,000 (10,001-200,000)</ENT>
                        <ENT>130,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3</ENT>
                        <ENT>Up to 1 million (200,001-1 million)</ENT>
                        <ENT>630,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4</ENT>
                        <ENT>Up to 2.5 million (1,000,001-2.5 million)</ENT>
                        <ENT>1,500,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">5</ENT>
                        <ENT>Up to 5 million (2,500,001-5 million)</ENT>
                        <ENT>3,000,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">6</ENT>
                        <ENT>Up to 10 million (5,000,001-10 million)</ENT>
                        <ENT>4,500,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7</ENT>
                        <ENT>Up to 15 million (10,000,001-15 million)</ENT>
                        <ENT>5,000,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">8</ENT>
                        <ENT>Up to 20 million (15,000,001-20 million)</ENT>
                        <ENT>6,250,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">9</ENT>
                        <ENT>Up to 25 million (20,000,001-25 million)</ENT>
                        <ENT>7,250,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10</ENT>
                        <ENT>Up to 75 million (25,000,001-200 million)</ENT>
                        <ENT>8,250,000</ENT>
                    </ROW>
                </GPOTABLE>
                <P>SSA calculates fees based on forecasted systems and operational expenses, agency oversight, overhead, and Certified Public Accountant audit contract costs.</P>
                <P>
                    Section 215(h)(1)(B) of the Banking Bill requires that the Commissioner shall “periodically adjust” the price paid by users to ensure that amounts collected are sufficient to fully offset the costs of administering the eCBSV system. SSA will monitor costs incurred to provide eCBSV services on at least and annual basis, and will revise the tier fee schedule accordingly. SSA will notify permitted entities of the tier fee schedule in effect at the renewal of the eCBSV user agreements; when a permitted entity begins a new 365-day agreement period; and via notice in the 
                    <E T="04">Federal Register</E>
                    . SSA will govern permitted entities renewals by the tier in effect at the time of renewal.
                </P>
                <P>
                    II. SSA submitted the information collections below to OMB for clearance. Your comments regarding these information collections would be most useful if OMB and SSA receive them 30 days from the date of this publication. To be sure we consider your comments, we must receive them no later than April 12, 2024. Individuals can obtain copies of these OMB clearance packages by writing to the 
                    <E T="03">OR.Reports.Clearance@ssa.gov.</E>
                </P>
                <P>
                    <E T="03">Employee Work Activity Questionnaire—20 CFR 404.1574(a)(1)-(3)—0960-0483.</E>
                     SSDI beneficiaries and SSI recipients qualify for payments when a verified physical or mental impairment prevents them from working. If disability claimants attempt 
                    <PRTPAGE P="18475"/>
                    to return to work after receiving payments, but are unable to continue working, they submit Form SSA-3033, Employee Work Activity Questionnaire, so SSA can evaluate their work attempt. In addition, SSA uses this form to evaluate unsuccessful subsidy work and determine applicants' continuing eligibility for disability payments. The respondents are employers of SSDI beneficiaries and SSI recipients who unsuccessfully attempted to return to work.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Revision of an OMB-approved information collection.
                </P>
                <GPOTABLE COLS="8" OPTS="L2,nj,tp0,i1" CDEF="s50,12,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
                            <LI>of response</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>burden</LI>
                            <LI>per response</LI>
                            <LI>(minutes)</LI>
                        </CHED>
                        <CHED H="1">
                            Estimated
                            <LI>total annual</LI>
                            <LI>burden</LI>
                            <LI>(hours)</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>theoretical</LI>
                            <LI>hourly cost</LI>
                            <LI>amount</LI>
                            <LI>(dollars) *</LI>
                        </CHED>
                        <CHED H="1">
                            Average wait
                            <LI>time for</LI>
                            <LI>teleservice</LI>
                            <LI>centers</LI>
                            <LI>(minutes) **</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual
                            <LI>opportunity</LI>
                            <LI>cost</LI>
                            <LI>(dollars) ***</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">SSA-3033 Phone</ENT>
                        <ENT>5,000</ENT>
                        <ENT>1</ENT>
                        <ENT>15</ENT>
                        <ENT>1,250</ENT>
                        <ENT>$59.07</ENT>
                        <ENT>19</ENT>
                        <ENT>*** $167,345</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">SSA-3033 Returned via mail</ENT>
                        <ENT>10,000</ENT>
                        <ENT>1</ENT>
                        <ENT>15</ENT>
                        <ENT>2,500</ENT>
                        <ENT>59.07</ENT>
                        <ENT/>
                        <ENT>*** 147,675</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Totals</ENT>
                        <ENT>15,000</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>3,750</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>315,020</ENT>
                    </ROW>
                    <TNOTE>
                        * We based this figure on average general and operations manager's hourly salary, as reported by Bureau of Labor Statistics data (
                        <E T="03">https://www.bls.gov/oes/current/oes111021.htm</E>
                        ).
                    </TNOTE>
                    <TNOTE>** We based this figure on the average FY 2023 wait times for field offices, based on SSA's current management information data.</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: March 8, 2024. </DATED>
                    <NAME>Naomi Sipple,</NAME>
                    <TITLE>Reports Clearance Officer, Social Security Administration.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05296 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4191-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF STATE</AGENCY>
                <DEPDOC>[Public Notice: 12356]</DEPDOC>
                <SUBJECT>60-Day Notice of Proposed Information Collection: Reta Jo Lewis Local Diplomat Program—City Applications</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of request for public comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of State (the Department) is seeking Office of Management and Budget (OMB) approval for the information collection described below. In accordance with the Paperwork Reduction Act of 1995, 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 preceding submission of the collection to OMB.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The Department will accept comments from the public up to May 13, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Web:</E>
                         Persons with access to the internet may comment on this notice by going to 
                        <E T="03">www.Regulations.gov.</E>
                         You can search for the document by entering “Docket Number: DOS-2024-0005” in the Search field. Then click the “Comment Now” button and complete the comment form.
                    </P>
                    <P>
                        • 
                        <E T="03">Email: subnational@state.gov.</E>
                    </P>
                    <P>You must include the DS form number (if applicable), information collection title, and the OMB control number in any correspondence.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Direct requests for additional information regarding the collection listed in this notice, including requests for copies of the proposed collection instrument, and supporting documents, to Sharmeen Khan, who may be reached on 202-647-2615 or at 
                        <E T="03">subnational@state.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    • 
                    <E T="03">Title of Information Collection:</E>
                     Reta Jo Lewis Local Diplomat Program—Local Offices Application.
                </P>
                <P>
                    • 
                    <E T="03">OMB Control Number:</E>
                     1405-XXXX.
                </P>
                <P>
                    • 
                    <E T="03">Type of Request:</E>
                     New Collection.
                </P>
                <P>
                    • 
                    <E T="03">Originating Office:</E>
                     E/SDU.
                </P>
                <P>
                    • 
                    <E T="03">Form Number:</E>
                     DS-4320.
                </P>
                <P>
                    • 
                    <E T="03">Respondents:</E>
                     Local government offices, including city, state, and county offices.
                </P>
                <P>
                    • 
                    <E T="03">Estimated Number of Respondents:</E>
                     2,000.
                </P>
                <P>
                    • 
                    <E T="03">Estimated Number of Responses:</E>
                     2,000.
                </P>
                <P>
                    • 
                    <E T="03">Average Time per Response:</E>
                     0.5 hours.
                </P>
                <P>
                    • 
                    <E T="03">Total Estimated Burden Time:</E>
                     1,000 hours.
                </P>
                <P>
                    • 
                    <E T="03">Frequency:</E>
                     Once.
                </P>
                <P>
                    • 
                    <E T="03">Obligation to Respond:</E>
                     Voluntary.
                </P>
                <P>We are soliciting public comments to permit the Department to:</P>
                <P>• Evaluate whether the proposed information collection is necessary for the proper functions of the Department.</P>
                <P>• Evaluate the accuracy of our estimate of the time and cost burden for this proposed collection, including the validity of the methodology and assumptions used.</P>
                <P>• Enhance the quality, utility, and clarity of the information to be collected.</P>
                <P>• Minimize the reporting burden on those who are to respond, including the use of automated collection techniques or other forms of information technology.</P>
                <P>Please note that comments submitted in response to this Notice are public record. Before including any detailed personal information, you should be aware that your comments as submitted, including your personal information, will be available for public review.</P>
                <HD SOURCE="HD1">Abstract of Proposed Collection</HD>
                <P>The Subnational Diplomacy Unit under the Department runs the Reta Jo Lewis Local Diplomat Program, which details a Foreign Service Officer or Civil Service employee to a local office, including a city, state, or county, for a year. The selection of local offices for this program must be competitive to provide a fair opportunity to all local offices that are interested in participating in the program. Therefore, to select local offices to participate in the program, the Subnational Diplomacy Unit must collect applications from local offices interested in the program.</P>
                <HD SOURCE="HD1">Methodology</HD>
                <P>The form will be emailed to local governments. After completion by the local governments, the form will be submitted via Microsoft Forms to the Department.</P>
                <SIG>
                    <NAME>Nina L. Hachigian,</NAME>
                    <TITLE>Special Representative for City and State Diplomacy, Subnational Diplomacy Unit, Department of State.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05278 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4710-AE-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18476"/>
                <AGENCY TYPE="S">DEPARTMENT OF STATE</AGENCY>
                <DEPDOC>[Public Notice: 12313]</DEPDOC>
                <SUBJECT>Determination Under Section 7014(b) of the Department of State, Foreign Operations, and Related Programs Appropriations Act, 2022</SUBJECT>
                <P>
                    Pursuant to the authority vested in me by section 7014(b) of the Department of State, Foreign Operations, and Related Programs Appropriations Act, 2022 (Div K, Pub. L. 117-103) (FY 2022 SFOAA), and Department of State Delegation of Authority 513, I hereby determine that a significant change in circumstances makes it unlikely that the following funds specifically designated for particular programs or activities by the FY 2022 SFOAA or any other act can be obligated during the original periods of availability of such funds: $45,050,000 in development assistance account; $11,637,500 in the global health programs-USAID account; $11,190,193 in the nonproliferation, anti-terrorism, demining, and related programs account; and $2,128,660 in the peacekeeping operations (PKO) account. This determination shall be published in the 
                    <E T="04">Federal Register</E>
                     and, along with the accompanying 7014(b) Memorandum of Justification, shall be transmitted to Congress.
                </P>
                <SIG>
                    <DATED>Dated: September 12, 2023.</DATED>
                    <NAME>Richard Verma,</NAME>
                    <TITLE>Deputy Secretary of State for Management and Resources, Department of State.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05343 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4710-10-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Notice of Intent of Waiver With Respect to Land; Grand Rapids/Itasca County Airport, Grand Rapids, MN</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA is considering a proposal to change 4.31 acres of airport land from aeronautical use to non-aeronautical use and to authorize the sale of airport property located at Grand Rapids/Itasca County Airport, Grand Rapids, MN. The aforementioned land is not needed for aeronautical use. The subject property is a wooded area located outside of the airport perimeter fence on the west side of Runway 16/34. The proposed use of the property is to be sold to a private company for industrial use development.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before April 12, 2024.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>All requisite and supporting documentation will be made available for review by appointment at the FAA Dakota-Minnesota Airports District Office, Jeremy McLeod, Program Manager, 2301 University Dr., Bldg. 23B, Bismarck, ND 58504. Telephone: (701) 323-7380.</P>
                    <P>Written comments on the Sponsor's request may be submitted using any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov,</E>
                         and follow the instructions for sending your comments electronically.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Jeremy McLeod, Program Manager, Federal Aviation Administration, Dakota-Minnesota Airports District Office, 2301 University Dr., Bldg. 23B, Bismarck, ND 58504.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         Deliver to mail address above between 8 a.m. and 5 p.m. Monday through Friday, excluding Federal holidays.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jeremy McLeod, Program Manager, Federal Aviation Administration, Dakota-Minnesota Airports District Office, 2301 University Dr., Bldg. 23B, Bismarck, ND 58504. Telephone Number: (701) 323-7380.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    In accordance with section 47107(h) of title 49, United States Code, this notice is required to be published in the 
                    <E T="04">Federal Register</E>
                     30 days before modifying the land-use assurance that requires the property to be used for an aeronautical purpose.
                </P>
                <P>The subject property makes up a portion of airport Parcel 45. Parcel 45 is 4.99 acres and was acquired by the airport sponsor on May 5, 1978 with FAA Airport Development Aid Program (ADAP) grant number 6-27-0037-02 funding. A 0.68-acre portion of the parcel is used for the airport perimeter road and fence. The airport will retain this portion of Parcel 45. The remaining 4.31-acre portion of the parcel to be sold is vacant wooded land and does not serve an aeronautical use. The airport plans to sell the land at fair market value to a privately held retail company for industrial use.</P>
                <P>
                    The disposition of proceeds from the sale of the airport property will be in accordance with FAA's Policy and Procedures Concerning the Use of Airport Revenue, published in the 
                    <E T="04">Federal Register</E>
                     on February 16, 1999 (64 FR 7696).
                </P>
                <P>This notice announces that the FAA is considering the release of the subject airport property at the Grand Rapids/Itasca County Airport, Grand Rapids, MN, from federal land covenants, subject to a reservation for continuing right of flight as well as restrictions on the released property as required in FAA Order 5190.6B section 22.16. Approval does not constitute a commitment by the FAA to financially assist in the disposal of the subject airport property nor a determination of eligibility for grant-in-aid funding from the FAA.</P>
                <P>
                    <E T="03">Legal Description:</E>
                     That part of the East 330.00 feet of the South Half of the Southeast Quarter of the Northeast Quarter of section 33, Township 55 North, Range 25 West, Itasca County, Minnesota, lying southwesterly of the following described line:
                </P>
                <P>Commencing at the southeast corner of said Southeast Quarter of the Northeast Quarter; thence on an assigned bearing of North 01 degrees 20 minutes 08 seconds West, along the east line of said Southeast Quarter of the Northeast Quarter, a distance of 151.91 feet to the point of beginning of the line herein described; thence North 14 degrees 18 minutes 12 seconds West 523.41 feet to the north line of the South Half of the Southeast Quarter of the Northeast Quarter and said line terminating thereat.</P>
                <SIG>
                    <DATED>Issued in Minneapolis, MN, on March 7, 2024.</DATED>
                    <NAME>E. Lindsay Terry,</NAME>
                    <TITLE>Manager, Dakota-Minnesota Airports District Office, FAA, Great Lakes Region.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05248 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Motor Carrier Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. FMCSA-2023-0143]</DEPDOC>
                <SUBJECT>Request for Information: Drivers' Leasing Agreements for Commercial Motor Vehicles (CMVs)</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; extension of comment period.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>FMCSA extends the comment period for its February 16, 2024, notice requesting information from the public, including commercial motor vehicle drivers, to assist the Agency's Truck Leasing Task Force in reviewing such leases to identify terms and conditions that may be unfair to drivers. FMCSA extends the comment period until April 2, 2024.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        The comment period for the request for information published 
                        <PRTPAGE P="18477"/>
                        February 16, 2024, at 89 FR 12411, is extended. Comments should be received on or before April 2, 2024.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by Docket Number FMCSA-2023-0143 using any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov/docket/FMCSA-2023-0143/document.</E>
                         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, Washington, DC 20590-0001.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery or Courier:</E>
                         Dockets Operations, U.S. Department of Transportation, West Building, Ground Floor, 1200 New Jersey Avenue SE, Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (202) 493-2251.
                    </P>
                    <P>
                        • 
                        <E T="03">Submissions Containing Confidential Business Information (CBI):</E>
                         Brian Dahlin, Chief, Regulatory Evaluation Division, Federal Motor Carrier Safety Administration, 1200 New Jersey Avenue SE, Washington, DC 20590.
                    </P>
                    <P>
                        To avoid duplication, please use only one of these four methods. See the “Confidential Business Information” 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>
                        Shannon L. Watson, Senior Advisor to the Associate Administrator for Policy and Deputy Designated Federal Officer, Truck Leasing Task Force (TLTF), Federal Motor Carrier Safety Administration, 1200 New Jersey Avenue SE, Washington, DC 20590-0001; (202) 360-2925; 
                        <E T="03">TLTF@dot.gov.</E>
                         If you have questions on 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">A. Submitting Comments</HD>
                <P>If you submit a comment, please include the docket number for this request for information (RFI) (FMCSA-2023-0143), indicate the specific section of this document to which your 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">https://www.regulations.gov/docket/FMCSA-2023-0143/document,</E>
                     click on this RFI, click “Comment,” and type your comment into the text box on the following screen.
                </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. FMCSA will consider all comments and material received during the comment period.
                </P>
                <HD SOURCE="HD1">Confidential Business Information (CBI)</HD>
                <P>CBI is commercial or financial information that is both customarily and actually treated as private by its owner. Under the Freedom of Information Act (5 U.S.C. 552), CBI is exempt from public disclosure. If your comments responsive to the RFI contain commercial or financial information that is customarily treated as private, that you actually treat as private, it is important that you clearly designate the submitted comments as CBI. Please mark each page of your submission that constitutes CBI as “PROPIN” to indicate it contains proprietary information. FMCSA will treat such marked submissions as confidential under the Freedom of Information Act, and they will not be placed in the public docket of the RFI. Submissions containing CBI should be sent to Brian Dahlin, Chief, Regulatory Analysis Division, Office of Policy, Federal Motor Carrier Safety Administration, 1200 New Jersey Avenue SE, Washington, DC 20590-0001. Any comments FMCSA receives not specifically designated as CBI will be placed in the public docket.</P>
                <HD SOURCE="HD1">B. Viewing Comments and Documents</HD>
                <P>
                    To view comments, as well as any documents mentioned in this RFI as being available in the docket, go to 
                    <E T="03">https://www.regulations.gov/docket/FMCSA-2023-0143/document</E>
                     and choose the document to review. To view comments, click this RFI, and click “Browse Comments.” If you do not have access to the internet, you may view the docket online by visiting Dockets Operations on the ground floor of the DOT West Building, 1200 New Jersey Avenue SE, Washington, DC 20590, between 9 a.m. and 5 p.m., 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="HD1">C. Privacy Act</HD>
                <P>
                    DOT posts comments received, 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.transportation.gov/privacy.</E>
                     The comments are posted without edit and are searchable by the name of the submitter.
                </P>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    On February 16, 2024, FMCSA published a notice in the 
                    <E T="04">Federal Register</E>
                     requesting information from the public, including commercial motor vehicle (CMV) drivers, to assist the Agency's Truck Leasing Task Force (TLTF) in reviewing such leases to identify terms and conditions that may be unfair to drivers.
                </P>
                <P>The Owner-Operator Independent Drivers Association (OOIDA) filed a comment to the public docket requesting that the comment period be extended. OOIDA stated:</P>
                <P>This will give drivers and other members of the public sufficient time to collect and submit leasing information. We also believe extending the comment period will allow feedback from OOIDA members and other drivers who will be attending the Mid-America Trucking Show that will be held March 21st through 23rd in Louisville, Kentucky.</P>
                <P>FMCSA believes it appropriate to extend the March 18, 2024, deadline to provide interested parties additional time to submit responses to the docket. Therefore, FMCSA extends the comment period until April 2, 2024.</P>
                <SIG>
                    <NAME>Larry W. Minor,</NAME>
                    <TITLE>
                        <E T="03">Associate Administrator for Policy.</E>
                    </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05342 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-EX-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Railroad Administration</SUBAGY>
                <DEPDOC>[Docket Number FRA-2020-0038]</DEPDOC>
                <SUBJECT>Petition for Extension of Waiver of Compliance</SUBJECT>
                <P>
                    Under part 211 of title 49 Code of Federal Regulations (CFR), this document provides the public notice that on December 20, 2023, and February 29, 2024, the City of San Clemente, California, (the City) and the Southern California Regional Rail Authority (Metrolink) petitioned the Federal Railroad Administration (FRA) for an extension of a waiver of compliance from certain provisions of the Federal railroad safety regulations 
                    <PRTPAGE P="18478"/>
                    contained at 49 CFR part 222 (Use of Locomotive Horns at Public Highway-Rail Grade Crossings). The relevant Docket Number is FRA-2020-0038.
                </P>
                <P>Specifically, the City and Metrolink (Petitioners) jointly seek relief from the requirements of 49 CFR 222.59(a)(1), to continue use of a Pedestrian Audible Warning System (PAWS), which is similar to a wayside horn, when approaching seven highway-rail grade crossings, instead of a locomotive horn. Petitioners also request to extend relief from certain provisions of 49 CFR part 222, appendix E (Paragraphs 4 and 6), to allow a minimum sound level of 80 dB(A) and direction of the PAWS. The seven crossings that are the subject of this request are:</P>
                <FP SOURCE="FP-1">• Dije Court—USDOT Number 922847D—MP 203.95—pedestrian—3 PAWS</FP>
                <FP SOURCE="FP-1">• El Portal—USDOT Number 922848K—MP 204.04—pedestrian—2 PAWS</FP>
                <FP SOURCE="FP-1">• Corto Lane—USDOT Number 026977D—MP 204.56—pedestrian—3 PAWS</FP>
                <FP SOURCE="FP-1">• Pier Service Road—USDOT Number 026997P—MP 204.73—private—4 PAWS</FP>
                <FP SOURCE="FP-1">• T Street—USDOT Number 922849S—MP 205.16—pedestrian—3 PAWS</FP>
                <FP SOURCE="FP-1">• Lost Winds—USDOT Number 922850L—MP 205.56—pedestrian—2 PAWS</FP>
                <FP SOURCE="FP-1">• Calafia—USDOT Number 026637S—MP 206.00—pedestrian—2 PAWS</FP>
                <P>In support of its request, Petitioners submitted maintenance, communication, and malfunction/response plans for the PAWS.</P>
                <P>In its February 26, 2024, addendum, Petitioners note their plans to augment the existing fencing system along “the beach trail from Mile Post 203.71 . . . to Mile Post 206.00.” They explain that the plan “is in response to the current deficiency in fencing elevation along certain portions of the trail and is intended to improve the public safety of the area.”</P>
                <P>
                    A copy of the petition, as well as any written communications concerning the petition, is available for review online at 
                    <E T="03">www.regulations.gov.</E>
                </P>
                <P>Interested parties are invited to participate in these proceedings by submitting written views, data, or comments. FRA does not anticipate scheduling a public hearing in connection with these proceedings since the facts do not appear to warrant a hearing. If any interested parties desire an opportunity for oral comment and a public hearing, they should notify FRA, in writing, before the end of the comment period and specify the basis for their request.</P>
                <P>
                    All communications concerning these proceedings should identify the appropriate docket number and may be submitted at 
                    <E T="03">www.regulations.gov.</E>
                     Follow the online instructions for submitting comments.
                </P>
                <P>Communications received by May 13, 2024 will be considered by FRA before final action is taken. Comments received after that date will be considered if practicable.</P>
                <P>
                    Anyone can search the electronic form of any written communications and comments received into any of our dockets by the name of the individual submitting the comment (or signing the document, if submitted on behalf of an association, business, labor union, etc.). Under 5 U.S.C. 553(c), DOT solicits comments from the public to better inform its processes. 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">https://www.transportation.gov/privacy.</E>
                     See also 
                    <E T="03">https://www.regulations.gov/privacy-notice</E>
                     for the privacy notice of 
                    <E T="03">regulations.gov</E>
                    .
                </P>
                <SIG>
                    <P>Issued in Washington, DC.</P>
                    <NAME>John Karl Alexy,</NAME>
                    <TITLE>Associate Administrator for Railroad Safety, Chief Safety Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05282 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Railroad Administration</SUBAGY>
                <DEPDOC>[Docket Number FRA-2007-28454]</DEPDOC>
                <SUBJECT>Petition for Extension of Waiver of Compliance</SUBJECT>
                <P>Under part 211 of title 49 Code of Federal Regulations (CFR), this document provides the public notice that on January 23, 2024, and February 13, 2024, Union Pacific Railroad Company (UPRR) petitioned the Federal Railroad Administration (FRA) for an extension of a waiver of compliance from certain provisions of the Federal railroad safety regulations contained at 49 CFR part 232 (Brake System Safety Standards for Freight and Other Non-Passenger Trains and Equipment; End-of-Train Devices). The relevant Docket Number is FRA-2007-28454.</P>
                <P>
                    Specifically, UPRR requests to extend its existing waiver in this docket, which provides conditional relief from the requirements for performing the single car air brake test (SCABT) as prescribed in 49 CFR 232.305(b)(2), 
                    <E T="03">Single car air brake tests.</E>
                     The relief allows UPRR to replace non-FRA condemnable wheelsets on railcars as part of an in-train wheelset replacement program at North Platte, Nebraska; South Morrill, Nebraska; and Roseville, California, without the need to also perform the SCABT as required, if the car has not received a SCABT within the previous 12 months.
                </P>
                <P>In support of its request, UPRR states that the in-train repair “wheel change outs have allowed for a reduced stress state[,] resulting in fewer derailments attributed to broken rails, joint bars, and other track infrastructure deterioration.” UPRR also asserts that there has been a “41% reduction in wheel, axle, and bearing related incidents” on UPRR.</P>
                <P>
                    A copy of the petition, as well as any written communications concerning the petition, is available for review online at 
                    <E T="03">www.regulations.gov.</E>
                </P>
                <P>Interested parties are invited to participate in these proceedings by submitting written views, data, or comments. FRA does not anticipate scheduling a public hearing in connection with these proceedings since the facts do not appear to warrant a hearing. If any interested parties desire an opportunity for oral comment and a public hearing, they should notify FRA, in writing, before the end of the comment period and specify the basis for their request.</P>
                <P>
                    All communications concerning these proceedings should identify the appropriate docket number and may be submitted at 
                    <E T="03">www.regulations.gov.</E>
                     Follow the online instructions for submitting comments.
                </P>
                <P>Communications received by May 13, 2024 will be considered by FRA before final action is taken. Comments received after that date will be considered if practicable.</P>
                <P>
                    Anyone can search the electronic form of any written communications and comments received into any of our dockets by the name of the individual submitting the comment (or signing the document, if submitted on behalf of an association, business, labor union, etc.). Under 5 U.S.C. 553(c), DOT solicits comments from the public to better inform its processes. 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">https://www.transportation.gov/privacy.</E>
                     See also 
                    <E T="03">https://www.regulations.gov/privacy-notice</E>
                     for the privacy notice of 
                    <E T="03">regulations.gov</E>
                    .
                </P>
                <SIG>
                    <PRTPAGE P="18479"/>
                    <P>Issued in Washington, DC.</P>
                    <NAME>John Karl Alexy,</NAME>
                    <TITLE>Associate Administrator for Railroad Safety, Chief Safety Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05283 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Railroad Administration</SUBAGY>
                <DEPDOC>[Docket Number FRA-2024-0029]</DEPDOC>
                <SUBJECT>Petition for Waiver of Compliance</SUBJECT>
                <P>Under part 211 of title 49 Code of Federal Regulations (CFR), this document provides the public notice that on February 12, 2024, Strasburg Rail Road Company (SRC) petitioned the Federal Railroad Administration (FRA) for a waiver of compliance from certain provisions of the Federal railroad safety regulations contained at 49 CFR part 240 (Qualification and Certification of Locomotive Engineers). FRA assigned the petition Docket Number FRA-2024-0029.</P>
                <P>Specifically, SRC requests relief from § 240.201, which requires that only certified persons operate locomotives and trains. The relief would allow noncertified persons to operate a historic locomotive as part of a visitor experience program, under the supervision of qualified personnel. In support of its petition, SRC notes that the relief would only apply to persons participating in the program, and that participants would be 18 years of age or older and under the direct supervision of a certified and qualified locomotive engineer. Further, all movements would take place during daylight hours and at restricted speed on approximately one mile of track, and no public grade crossings will be traversed.</P>
                <P>
                    A copy of the petition, as well as any written communications concerning the petition, is available for review online at 
                    <E T="03">www.regulations.gov.</E>
                </P>
                <P>Interested parties are invited to participate in these proceedings by submitting written views, data, or comments. FRA does not anticipate scheduling a public hearing in connection with these proceedings since the facts do not appear to warrant a hearing. If any interested party desires an opportunity for oral comment and a public hearing, they should notify FRA, in writing, before the end of the comment period and specify the basis for their request.</P>
                <P>
                    All communications concerning these proceedings should identify the appropriate docket number and may be submitted at 
                    <E T="03">https://www.regulations.gov.</E>
                     Follow the online instructions for submitting comments.
                </P>
                <P>Communications received by May 13, 2024 will be considered by FRA before final action is taken. Comments received after that date will be considered if practicable.</P>
                <P>
                    Anyone can search the electronic form of any written communications and comments received into any of our dockets by the name of the individual submitting the comment (or signing the document, if submitted on behalf of an association, business, labor union, etc.). Under 5 U.S.C. 553(c), the U.S. Department of Transportation (DOT) solicits comments from the public to better inform its processes. 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">https://www.transportation.gov/privacy.</E>
                     See also 
                    <E T="03">https://www.regulations.gov/privacy-notice</E>
                     for the privacy notice of 
                    <E T="03">regulations.gov</E>
                    .
                </P>
                <SIG>
                    <P>Issued in Washington, DC.</P>
                    <NAME>John Karl Alexy,</NAME>
                    <TITLE>Associate Administrator for Railroad Safety Chief Safety Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2024-05280 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Pipeline and Hazardous Materials Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. PHMSA-2021-0109; Notice No. 2023-16]</DEPDOC>
                <SUBJECT>Hazardous Materials: Frequently Asked Questions—Training Requirements</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Pipeline and Hazardous Materials Safety Administration (PHMSA), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>On March 22, 2022, PHMSA announced an initiative to convert historical letters of interpretation (LOI) applicable to the Hazardous Materials Regulations (HMR) that have been issued to specific stakeholders into broadly applicable frequently asked questions (FAQ). On December 9, 2022, PHMSA published the first set of FAQ regarding applicability of the HMR. On August 18, 2023, PHMSA published the second set of FAQ regarding incident reporting. Today's notice contains the third set of FAQ regarding training requirements.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Interested persons are invited to submit comments on or before April 12, 2024. Comments received after that date will be considered to the extent practicable.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by the Docket Number PHMSA-2021-0109 by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         1-202-493-2251.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Docket Management System; U.S. Department of Transportation, West Building, Ground Floor, Room W12-140, Routing Symbol M-30, 1200 New Jersey Avenue SE, Washington, DC 20590.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         Docket Management System; Room W12-140 on the ground floor of the West Building, 1200 New Jersey Avenue SE, Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except federal holidays.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions must include the agency name and Docket Number (PHMSA-2021-0109) for this notice. To avoid duplication, please use only one of these four methods. All comments received will be posted without change to the Federal Docket Management System (FDMS) and will include any personal information you provide.
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         For access to the dockets to read background documents or comments received, go to 
                        <E T="03">http://www.regulations.gov</E>
                         or DOT's Docket Operations Office (see 
                        <E T="02">ADDRESSES</E>
                        ).
                    </P>
                    <P>
                        <E T="03">Privacy Act:</E>
                         In accordance with 5 U.S.C. 553(c), DOT solicits comments from the public. DOT posts these comments, without edit, including any personal information the commenter provides, to 
                        <E T="03">http://www.regulations.gov,</E>
                         as described in the system of records notice (DOT/ALL-14 FDMS), which can be reviewed at 
                        <E T="03">http://www.dot.gov/privacy.</E>
                    </P>
                    <P>
                        <E T="03">Confidential Business Information (CBI):</E>
                         CBI is commercial or financial information that is both customarily and actually treated as private by its owner. Under the Freedom of Information Act (FOIA) (5 U.S.C. 552), CBI is exempt from public disclosure. If your comments responsive to this notice contain commercial or financial information that is customarily treated as private, that you actually treat as private, and is relevant or responsive to this notice, it is important that you clearly designate the submitted comments as “CBI.” Please mark each page of your submission containing CBI as “PROPIN.” Submissions containing 
                        <PRTPAGE P="18480"/>
                        CBI should be sent to Arthur Pollack, Standards and Rulemaking Division, 202-366-8553, Pipeline and Hazardous Materials Safety Administration, U.S. Department of Transportation, 1200 New Jersey Avenue SE, Washington, DC 20590-0001. Any commentary that PHMSA receives that is not specifically designated as CBI will be placed in the public docket for this notice.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Arthur Pollack, Standards and Rulemaking Division, 202-366-8553, Pipeline and Hazardous Materials Safety Administration, U.S. Department of Transportation, 1200 New Jersey Avenue SE, Washington, DC 20590-0001.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    On March 22, 2022, PHMSA 
                    <SU>1</SU>
                    <FTREF/>
                     announced an initiative 
                    <SU>2</SU>
                    <FTREF/>
                     to convert historical LOI applicable to the HMR 
                    <SU>3</SU>
                    <FTREF/>
                     that have been issued to specific stakeholders into broadly applicable FAQ to facilitate better public understanding and awareness of the HMR. In that initial set of FAQ, PHMSA also requested comment on the initiative and solicited input on the prioritization of future sets of FAQ. FAQ are not substantive rules themselves and do not create legally enforceable rights, assign duties, or impose new obligations not otherwise contained in the existing regulations and standards. Instead, FAQ are intended as an aid to the regulated community to better understand how to comply with the regulations. An individual who is able to demonstrate that it is acting in accordance with the FAQ, however, is likely to be able to demonstrate compliance with the relevant regulations. If an individual chooses not to follow the FAQ, the individual must be able to demonstrate that its conduct is in accordance with the regulations.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Hazardous Materials: Frequently Asked Questions-Applicability of the Hazardous Material Regulations. 87 FR 16308 (March 22, 2022), available at: 
                        <E T="03">https://www.regulations.gov/document/PHMSA-2021-0109-0001.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Hazardous Materials: Frequently Asked Questions-Applicability of the Hazardous Material Regulations (Dec. 9, 2022), available at: 
                        <E T="03">https://www.regulations.gov/document/PHMSA-2021-0109-0013;</E>
                         Hazardous Materials: Frequently Asked Questions-Incident Reporting. 88 FR 56702 (August 18, 2023), available at: 
                        <E T="03">https://www.regulations.gov/document/PHMSA-2021-0109-0014.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         49 CFR parts 171-180.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Purpose of the FAQ Initiative</HD>
                <P>
                    This initiative provides additional value to PHMSA's Online Code of Federal Regulations (oCFR) tool.
                    <SU>4</SU>
                    <FTREF/>
                     The oCFR tool is an interactive web-based application that allows users to navigate with a single click between all content, including LOI, connected to an HMR citation. The oCFR tool includes the ability to sort, filter, and export search results. Upon completion of this initiative, PHMSA's Office of Hazardous Materials Safety (OHMS) will be able to achieve efficiencies for other more complex or novel requests for LOI and devote resources to other hazardous materials transportation safety projects. This initiative will also allow resources to be made available for other improvement-related operations, such as petitions for rulemakings, public outreach and engagement, and economically beneficial regulatory and policy improvements. In the section of this notice titled “Frequently Asked Questions: Hazmat Training Requirements,” PHMSA is publishing its third set of FAQ developed under this initiative.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         PHMSA's Online CFR (oCFR), available at: 
                        <E T="03">https://www.phmsa.dot.gov/standards-rulemaking/hazmat/phmsas-online-cfr-ocfr.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Frequently Asked Questions</HD>
                <HD SOURCE="HD2">Hazardous Materials (Hazmat) Training Requirements</HD>
                <P>
                    The requirements for hazmat training are outlined under Subpart H to Part 172 of the HMR—specifically, §§ 172.700 through 172.704.
                    <SU>5</SU>
                    <FTREF/>
                     Therefore, as noted above, to facilitate better public understanding and awareness of the HMR, the FAQ pertaining to hazmat training are as follows:
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">https://www.ecfr.gov/current/title-49/part-172/subpart-H.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">1. Question: What are the hazardous materials training requirements?</HD>
                <P>
                    <E T="03">Answer:</E>
                     A hazmat employee, defined under § 171.8, is subject to training under § 172.700. Each hazmat employer must train and test their hazmat employees, certify their training, and develop and retain records of current training. The HMR requires a systematic training program that ensures a hazmat employee has familiarity with the general provisions of the HMR; is able to recognize and identify hazardous materials; has knowledge of specific requirements of the HMR applicable to functions performed by the employee; and has knowledge of emergency response information, self-protection measures, and accident prevention methods and procedures.
                </P>
                <HD SOURCE="HD3">2. Question: What is required as part of a complete hazmat training program?</HD>
                <P>
                    <E T="03">Answer:</E>
                     Section 172.704 requires that hazmat training include:
                </P>
                <P>• general awareness/familiarization training;</P>
                <P>• function-specific training;</P>
                <P>• safety training;</P>
                <P>• security awareness training; and</P>
                <P>• in-depth security training if a security plan is required.</P>
                <P>Additionally, § 172.700 requires hazmat employees receive modal-specific training for the individual modes of transportation the employee operates.</P>
                <P>This training can be performed by the hazmat employer, by the hazmat employee, or by a contracted training service so long as all the training requirements in Subpart H to Part 172 are met.</P>
                <HD SOURCE="HD3">3. Question: Who is considered a “hazmat employee?”</HD>
                <P>
                    <E T="03">Answer:</E>
                     A hazmat employee is defined in § 171.8 as any person who—in the course of employment—directly affects hazmat transportation safety and includes, but is not limited to, loading, unloading, or handling hazmat; inspecting hazmat packaging; preparing hazmat shipments; operating vehicles used to transport hazmat; and anyone responsible for hazmat transportation safety.
                </P>
                <HD SOURCE="HD3">4. Question: Who is considered a “hazmat employer?”</HD>
                <P>
                    <E T="03">Answer:</E>
                     A hazmat employer is defined in § 171.8 as a person who uses one or more of its hazmat employees to transport hazmat in commerce; to cause hazmat to be transported in commerce; or designs, manufactures, fabricates, inspects, marks, maintains, reconditions, tests, or repairs containers, drums, or packagings as qualified for use in the transportation of hazardous materials.
                </P>
                <HD SOURCE="HD3">5. Question: Do the HMR allow a hazmat employee to self-train?</HD>
                <P>
                    <E T="03">Answer:</E>
                     Yes. Hazmat employees may self-train, provided the general awareness/familiarization training, function-specific training, safety training, security awareness training, in-depth security training, testing, recordkeeping, and certification requirements specified in § 172.704 are met.
                </P>
                <HD SOURCE="HD3">6. Question: What training materials and resources are available from PHMSA?</HD>
                <P>
                    <E T="03">Answer:</E>
                     PHMSA's Outreach and Training Branch offers training publications, videos, and brochures, which can be found at: 
                    <E T="03">
                        https://
                        <PRTPAGE P="18481"/>
                        www.phmsa.dot.gov/training/hazmat/hazardous-materials-outreach-engagement.
                    </E>
                </P>
                <HD SOURCE="HD3">7. Question: Is a hazmat trainer required to have a certification or minimum level of training?</HD>
                <P>
                    <E T="03">Answer:</E>
                     No. PHMSA does not specify or require minimum qualifications for hazmat trainers. A trainer needs to be able to convey the training requirements under § 172.704.
                </P>
                <HD SOURCE="HD3">8. Question: What documentation or recordkeeping is required for hazardous materials training?</HD>
                <P>
                    <E T="03">Answer:</E>
                     Hazmat employers must keep training records for each hazmat employee in accordance with § 172.704(d). Compliance with recordkeeping requirements can be achieved in many ways (
                    <E T="03">e.g.,</E>
                     certificate, electronic, or even written paperwork) and could involve partnerships with any organization offering training that meets the needs of the hazmat employer. The training records must include the following information:
                </P>
                <P>• the hazmat employee's name;</P>
                <P>• date of the most recently completed training;</P>
                <P>• information about the training materials;</P>
                <P>• name and address of the trainer; and</P>
                <P>• a certification that the hazmat employee has been trained and tested in accordance with the HMR.</P>
                <P>Regardless of who performs the training or generates the records, the hazmat employer is ultimately responsible for compliance with the recordkeeping requirements of § 172.704(d).</P>
                <HD SOURCE="HD3">9. Question: Is testing of hazmat employees—for example, a test or exam—required as part of a training program?</HD>
                <P>
                    <E T="03">Answer:</E>
                     Yes. While the HMR do not prescribe detailed test procedures for hazmat employees, some type of test or exam is required. The purpose of testing is to ensure that each hazmat employee has been trained on appropriate areas of responsibility and can perform their assigned duties in compliance with the HMR. (See § 172.702; see also § 172.704.) Any method of testing that achieves this purpose is acceptable. No specific testing document is required.
                </P>
                <P>Although the requirements in § 172.702(d) do not state that a hazmat employee must “pass” a test, a hazmat employee must be trained in accordance with the applicable HMR and may only be certified in those areas in which the hazmat employee can successfully perform their assigned duties. Employees may be tested on the training requirements specified in § 172.704 by any appropriate means.</P>
                <HD SOURCE="HD3">10. Question: May an employee successfully take a test and have the hazmat training or recurrent training requirement waived?</HD>
                <P>
                    <E T="03">Answer:</E>
                     No. An employee may not take and pass an exam, and then have the hazmat training or the recurrent training requirement waived. Hazmat training and recurrent training must cover the primary areas as specified under the training requirements in § 172.704, 
                    <E T="03">i.e.,</E>
                     general awareness/familiarization training, function-specific training, safety training, security awareness training, and in-depth security training (if applicable).
                </P>
                <HD SOURCE="HD3">11. Question: How often must a hazmat employee be trained?</HD>
                <P>
                    <E T="03">Answer:</E>
                     In accordance with § 172.704(c)(2), a hazmat employee must receive the required training at least once every three years.
                </P>
                <HD SOURCE="HD3">12. Question: If an employee's job function changes, and new hazmat functions are performed or PHMSA regulations are amended, is further training required?</HD>
                <P>
                    <E T="03">Answer:</E>
                     Yes. A hazmat employer must ensure that each hazmat employee is thoroughly instructed in the requirements that apply to functions performed by that employee. (See § 172.702(b).) Section 172.704(c)(1) requires that a new hazmat employee or a hazmat employee who changes job functions must complete their hazmat training within 90 days after employment or job function change. However, they may perform the job functions prior to the completion of training under the direct supervision of a properly trained and knowledgeable hazmat employee. When PHMSA adopts a new regulation or changes an existing regulation that relates to a function performed by a hazmat employee, the hazmat employee must be instructed in the new or revised function-specific requirements as soon as necessary based on the new requirement's compliance timeline without regard to the three-year training cycle.
                </P>
                <HD SOURCE="HD3">13. Question: How does a hazmat employer determine what function-specific training is required under § 172.704?</HD>
                <P>
                    <E T="03">Answer:</E>
                     Function-specific training is specific to the function(s) for which the hazmat employee is responsible. The hazmat employer must determine what tasks the hazmat employee is responsible for that are directly regulated under the HMR, and then provide the necessary training in accordance with Subpart H to Part 172.
                </P>
                <HD SOURCE="HD3">14. Question: Is online, computer-based, and virtual training authorized under the HMR?</HD>
                <P>
                    <E T="03">Answer:</E>
                     Yes. A hazmat employer may use any type of training method, including forms of digital training (
                    <E T="03">e.g.,</E>
                     online, computer-based, and virtual training programs), that ensures each hazmat employee receives general awareness/familiarization training, function-specific training, safety training, security awareness training, and in-depth security training. (See § 172.704; see also § 172.702.) The hazmat employer must also ensure that testing, recordkeeping, and certification requirements as specified in § 172.704
                    <E T="03"> are met.</E>
                </P>
                <HD SOURCE="HD3">15. Question: Can previously completed Occupational Safety and Health Administration (OSHA), U.S. Environmental Protection Agency (EPA), or other required safety training substitute for hazmat training?</HD>
                <P>
                    <E T="03">Answer:</E>
                     Training conducted to comply with the hazard communication programs required by OSHA, EPA, or training programs required by other federal or international agencies may be used to satisfy portions of the training requirements set forth in Subpart H to Part 172.
                </P>
                <HD SOURCE="HD3">16. Question: What are the penalties for violation of the requirements of the HMR, such as training?</HD>
                <P>
                    <E T="03">Answer:</E>
                     A hazmat employer must ensure that each of its hazmat employees is trained in accordance with the requirements prescribed under Subpart H to Part 172
                    <E T="03">.</E>
                     (See § 172.702.) A person who knowingly violates a requirement of the HMR or the Federal Hazmat Transportation Law, 49 U.S.C. 5101 
                    <E T="03">et seq.,</E>
                     may be liable for a civil penalty of not more than $ 99,756.
                    <SU>6</SU>
                    <FTREF/>
                     For a violation that results in death, serious illness, severe injury, or substantial property destruction, the maximum penalty is increased to $ 232,762.
                    <SU>6</SU>
                     For violations related to training, there is a minimum penalty of $ 601. (See § 107.329.) Maximum and minimum penalty limitations are updated annually to adjust for inflation.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         As of December 28, 2023, 
                        <E T="03">https://www.federalregister.gov/documents/2023/12/28/2023-28066/revisions-to-civil-penalty-amounts-2024.</E>
                         Annual updates to civil penalty amounts are codified at § 107.329.
                    </P>
                </FTNT>
                <PRTPAGE P="18482"/>
                <HD SOURCE="HD3">17. Question: Who is responsible for the required hazmat training of a subcontractor's employees?</HD>
                <P>
                    <E T="03">Answer:</E>
                     Under § 171.8, a subcontractor's hazmat employee is a hazmat employee. In accordance with § 172.702(a), the subcontractor, as the hazmat employer for its hazmat employees, is responsible for ensuring that each of its hazmat employees are trained in accordance with Subpart H to Part 172. However, § 172.702(c) provides flexibility on who can provide the training. The training may be provided by the hazmat employer or by some other public or private source.
                </P>
                <HD SOURCE="HD3">18. Question: Is a person located outside the United States who offers a shipment from a foreign location for transportation in the United States—in accordance with an international standard recognized by the HMR—subject to the training requirements in Subpart H to Part 172?</HD>
                <P>
                    <E T="03">Answer:</E>
                     Yes. § 171.22 prescribes additional requirements for the use of international standards for shipments offered for transportation or transported in the United States and includes shipments originating in a foreign location and transported to the United States. Under § 171.22(g)(2), the training requirements in Subpart H to Part 172, including function specific training, must be satisfied. Training conducted, in accordance with § 171.22, to comply with the international standards may be used to satisfy the training requirements set forth in § 172.704, to the extent that such training addresses the training components specified in § 172.704(a). It is not necessary to duplicate training. However, the hazmat employer must provide additional training to employees performing covered functions for any training components required by the HMR that were not previously addressed.
                </P>
                <HD SOURCE="HD3">19. Question: Is a driver required to have hazmat training in accordance with Subpart H to Part 172 if the driver has a hazmat endorsement on a CDL?</HD>
                <P>
                    <E T="03">Answer:</E>
                     Yes. In accordance with § 177.800(c), each driver who is a hazmat employee is subject to the training requirements in Subpart H to Part 172, and the driver training requirements in § 177.816, regardless of whether a hazmat endorsement is required. However, the training required to obtain a hazmat endorsement may be used to satisfy some of the training requirements of the HMR to the extent that such training addresses the training components of § 172.704. (See § 177.816(c).)
                </P>
                <HD SOURCE="HD1">IV. Future FAQ Topics</HD>
                <P>With the completion of this set of FAQ specific to training requirements, PHMSA will begin consideration for its next set of FAQ based on public input received. As such, PHMSA will continue concurrent work on future FAQ notices and subsequent topics may include FAQ pertaining to classification, hazard communication, hazardous substances, hazardous wastes, modal-specific requirements, or packaging.</P>
                <SIG>
                    <DATED>Issued in Washington, DC, on March 7, 2024, under authority delegated in 49 CFR 1.97.</DATED>
                    <NAME>William S. Schoonover,</NAME>
                    <TITLE>Associate Administrator for Hazardous Materials Safety, Pipeline and Hazardous Materials Safety Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05268 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-60-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Pipeline and Hazardous Materials Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. PHMSA-2022-0127 (Notice No. 2023-09)]</DEPDOC>
                <SUBJECT>Hazardous Materials: Clarification of Applications for Special Permits Submitted in the Public Interest</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Pipeline and Hazardous Materials Safety Administration (PHMSA), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>PHMSA is publishing this notice to inform interested parties on how PHMSA evaluates and determines whether a special permit can be considered consistent with the public interest. This notice outlines the criteria PHMSA used to evaluate special permit applications on the basis of public interest.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Don Burger, Standards and Rulemaking Division, 202-366-4314, Pipeline and Hazardous Materials Safety Administration, U.S. Department of Transportation, 1200 New Jersey Avenue SE, Washington, DC 20590-0001.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>PHMSA is responsible for regulations to ensure the safe transport of hazardous materials. The Hazardous Materials Regulations (HMR) have many performance-oriented regulations that provide the regulated community some flexibility in meeting safety requirements. Even so, not every transportation situation can be anticipated and addressed by the current regulations. The hazardous materials community develops new materials, technologies, and innovative ways to move hazardous materials safely. Such innovation strengthens our economy, and some new technologies and operational techniques may enhance safety.</P>
                <P>In order to accommodate and encourage continued development and innovation in the safe transport of hazardous materials, PHMSA is authorized to issue variances from the HMR via special permits, which set forth alternative requirements to those currently in the HMR. Special permits provide a mechanism for applying new technologies, promoting increased transportation efficiency and productivity, and ensuring global competitiveness without compromising safety. In addition, special permits enable the hazardous materials industry to integrate new products and technologies into production and the transportation stream safely, quickly, and effectively.</P>
                <P>
                    The Department of Transportation (DOT), through PHMSA, issues special permits under the Hazardous Materials Program Procedures (49 CFR part 107, subpart B). By issuing a special permit, PHMSA is in effect waiving requirements of the HMR and often imposing alternative requirements, 
                    <E T="03">i.e.,</E>
                     a special permit may allow a person to perform a function not otherwise permitted under the HMR.
                    <SU>1</SU>
                    <FTREF/>
                     PHMSA's Approvals and Permits Branch issues the special permits on behalf of the Associate Administrator.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">https://www.govinfo.gov/content/pkg/USCODE-2011-title49/html/USCODE-2011-title49-subtitleIII-chap51.htm.</E>
                    </P>
                </FTNT>
                <P>
                    The HMR requires that special permits must achieve a level of safety that is at least equal to that required by the regulation from which the special permit is sought; or, if a required safety level does not exist, is consistent with the public interest.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         49 CFR 107.105(d).
                    </P>
                </FTNT>
                <P>
                    Various stakeholders have inquired about the criteria for evaluating special permits consistent with the public interest, as well as how these special permits are evaluated. PHMSA is publishing this guidance to inform stakeholders and interested parties seeking a special permit in the public interest of the types of information PHMSA requires when it reviews a special permit application, and to provide examples of previous approved 
                    <PRTPAGE P="18483"/>
                    applications for a special permit in the public interest.
                </P>
                <P>PHMSA guidance—such as this notice—is not substantive rules themselves and does not create legally enforceable rights, assign duties, or impose new obligations not otherwise contained in the existing regulations and standards. Instead, PHMSA guidance is intended as an aid to demonstrate compliance with the relevant regulations. An individual who can demonstrate compliance with PHMSA guidance is likely to demonstrate compliance with the relevant regulations. If a different course of action is taken by an individual, the individual must be able to demonstrate that its conduct is in accordance with the regulations.</P>
                <HD SOURCE="HD1">II. Examples of Special Permits Consistent With the Public Interest</HD>
                <P>
                    In the past, PHMSA has considered a special permit consistent with the public interest if the special permit provides a positive net benefit to the welfare or well-being of the public; 
                    <E T="03">i.e.,</E>
                     the benefit to society from the waiver authorized in the special permit will outweigh potential harms. For example, while the transport of an unapproved explosive substance is forbidden under the HMR, it would be in the public interest to allow for a one-time transport of the substance to remove it from a location that creates higher risk for the public—such as removal of a seized explosive from a port—provided the risk to the public can be minimized through operational controls.
                    <SU>3</SU>
                    <FTREF/>
                     Similarly, while movement of a certain hazardous material by passenger aircraft might be forbidden under the HMR, the movement might be justified if it is the only mode of transport available to a remote location and sufficient operational controls are in place to minimize risk to the public to the extent possible (
                    <E T="03">e.g.,</E>
                     limiting only to a specific carrier with defined route).
                    <SU>4</SU>
                    <FTREF/>
                     Other examples of public interest special permits have supported responses to public health crises. For example, in response to the Ebola outbreak, PHMSA allowed specialized packaging to transport waste for disposal, subject to operational controls.
                    <SU>5</SU>
                    <FTREF/>
                     Prior to issuance of the special permit, there were no packagings authorized under the HMR that could have handled the large quantities of waste, so it was in the public interest to authorize an alternative means to transport the waste for incineration and disposal.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         DOT-SP 21357, Special Permit for Gateway Pyrotechnic Productions, LLC. PHMSA's Office of Hazardous Materials Safety maintains a searchable database of issued special permits on its website at 
                        <E T="03">https://www.phmsa.dot.gov/approvals-and-permits/hazmat/special-permits-search.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         See DOT-SP 16392, Special Permit for Gem Air, LLC; DOT-SP 12674, Special Permit for G &amp; S Aviation, LLC; DOT-SP 15243, Special Permit for Katmailand, Inc.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         See DOT-SP 16279; DOT-SP 16278 &amp; DOT-SP 16266, Special Permits for Stericycle, Inc.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Justification for Special Permit Applications</HD>
                <P>
                    Section 107.105(d) 
                    <SU>6</SU>
                    <FTREF/>
                     outlines the information the applicant must provide when requesting a special permit application. An applicant seeking a special permit, whether on the basis of an equal level of safety required by the HMR or as consistent with the public interest, must provide:
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         49 CFR 107.105(d).
                    </P>
                </FTNT>
                <P>• Information describing all relevant shipping and incident experience of which the applicant is aware that relates to the application.</P>
                <P>• A statement identifying any increased risk to safety or property that may result if the special permit is granted, and a description of the measures to be taken to address that risk.</P>
                <P>• Either one of the following:</P>
                <P>
                    ○ Substantiation, with applicable analyses, data, or test results, (
                    <E T="03">e.g.,</E>
                     failure mode and effect analysis), that the proposed alternative will achieve a level of safety that is at least equal to that required by the regulation from which the special permit is sought; or
                </P>
                <P>○ If the regulations do not establish a level of safety, an analysis that identifies each hazard, potential failure mode, and the probability of its occurrence, and how the risks associated with each hazard and failure mode are controlled by the provisions of the prospective permit.</P>
                <P>Without the applicant providing information outlined in § 107.105(d), PHMSA may not be able to complete its evaluation of the application as required by § 107.113(f). Further, in providing the above information and analysis, the applicant should demonstrate that the proposed alternative will achieve a level of safety that is consistent with the public interest and will adequately protect against the risks to life and property inherent in the transportation of hazardous materials in commerce.</P>
                <HD SOURCE="HD1">IV. Adequate Protection Against the Risks to Life and Property</HD>
                <P>
                    As discussed above, an applicant seeking a special permit consistent with public interest must demonstrate that their proposed alternative to the HMR will achieve a level of safety that adequately protects against risks to life and property.
                    <SU>7</SU>
                    <FTREF/>
                     This is often achieved by proposing various operational controls for a special permit in the application. A determination by PHMSA that an application and the proposed operational controls provide “adequate protection” against risks to life and property does not indicate such operational controls provide a lower level of safety than a special permit that was determined to have at least an “equivalent level of safety” to the HMR. Rather it is a safety determination in the absence of a standard to compare against the proposed approach in the special permit application.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         49 CFR 107.113(f)(2).
                    </P>
                </FTNT>
                <P>A special permit application seeking to show it is consistent with the public interest must include information on how the applicant will minimize any safety risk to the maximum extent practicable. Applicants should include explanations of: (1) the hazardous material and how it is contained; (2) known risks of the hazardous material; (3) mitigation of the risks posed by the hazardous material via packaging, hazard communication, and/or operational controls; and (4) any other relevant factors to support mitigation of any safety risks.</P>
                <P>Operational controls to help minimize transportation risks are also important features of permits issued in the public interest. Operational controls are requirements designed to enhance safety and oversight when transporting hazardous materials under special permits. Though special permits may waive some regulatory requirements due to unusual circumstances, operational controls allow permit holders to improve safety through policies, procedures, and communication. Operational controls in special permits have included selecting and training specific personnel; implementing additional equipment inspections and maintenance; limiting transport to certain times, routes, or conditions; using tracking and communication systems; documenting the permitted shipment; and other measures tailored to the situation. Operational controls may also limit the movement of the hazardous material to specific modes of transportation.</P>
                <HD SOURCE="HD1">V. Supporting Documentation and Duration for Public Interest Special Permits</HD>
                <P>
                    Providing detailed supporting documentation is key to supporting PHMSA's decision-making process. PHMSA evaluates all information and data outlined in this notice in reviewing and issuing a special permit application 
                    <PRTPAGE P="18484"/>
                    in the public interest. If the information outlined in the HMR and described in this notice is not provided in a special permit request, it is unlikely that a special permit would be issued in the public interest as the application would not be sufficient.
                </P>
                <P>
                    Finally, PHMSA will consider the length of time that the special permit issued in the public interest should remain in effect. New special permits are limited to a maximum of two years in duration by 49 U.S.C. 5117(a)(2). Emergencies—
                    <E T="03">e.g.,</E>
                     natural disasters, failure of containment of a hazardous material in transport, etc.—require quick decision-making by PHMSA to mitigate the potential hazards to the public and the environment. Special permits issued in the public interest, such as in the case of emergencies, typically are only issued for an amount of time expected to be sufficient to address the emergency.
                </P>
                <HD SOURCE="HD1">VI. Future Actions</HD>
                <P>This notice serves as guidance for interested parties looking to obtain special permits in the public interest. PHMSA encourages applicants seeking a special permit in the public interest to ensure applications include all necessary information to address the requirements of the HMR as outlined in this notice.</P>
                <SIG>
                    <DATED>Issued in Washington, DC, on March 7, 2024.</DATED>
                    <NAME>William S. Schoonover,</NAME>
                    <TITLE>Associate Administrator of Hazardous Materials Safety, Pipeline and Hazardous Materials Safety Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05250 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-60-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <SUBJECT>Proposed Collection; Comment Request Relating to Carryover of Passive Activity Losses and Credits and At-Risk Losses to Bankruptcy Estates of Individuals</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Internal Revenue Service, as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on continuing information collections, as required by the Paperwork Reduction Act of 1995. The IRS is soliciting comments concerning carryover of passive activity losses and credits and at-risk losses to bankruptcy estates of individuals.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before May 13, 2024 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all written comments to Andres Garcia, Internal Revenue Service, Room 6526, 1111 Constitution Avenue NW, Washington, DC 20224, or by email to 
                        <E T="03">pra.comments@irs.gov.</E>
                         Please include OMB Number 1545-1375 or TD 8537 in the Subject Line of the message. Requests for additional information or copies of this regulation should be directed to Sara Covington, at (202) 317-5744 or Internal Revenue Service, Room 6526, 1111 Constitution Avenue NW, Washington, DC 20224, or through the internet at 
                        <E T="03">Sara.L.Covington@irs.gov.</E>
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title:</E>
                     Carryover of Passive Activity Losses and Credits and At-Risk losses to Bankruptcy Estates for Individuals.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1375.
                </P>
                <P>
                    <E T="03">Regulation Project Number:</E>
                     T.D. 8537.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     These regulations relate to the application of carryover of passive activity losses and credits and at risk losses to the bankruptcy estates of individuals. The final regulations affect individual taxpayers who file bankruptcy petitions under chapter 7 or chapter 11 of title 11 of the United States Code and have passive activity losses and credits under section 469 or losses under section 465.
                </P>
                <P>
                    <E T="03">Current Actions:</E>
                     There are no changes being made to this existing regulation or to the paperwork burden previously approved by OMB.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals or households.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     500.
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     12 Minutes.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     100.
                </P>
                <P>The following paragraph applies to all of the collections of information covered by this notice:</P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless the collection of information displays a valid OMB control number.</P>
                <P>Books or records relating to a collection of information must be retained as long as their contents may become material in the administration of any internal revenue law. Generally, tax returns and tax return information are confidential, as required by 26 U.S.C. 6103.</P>
                <P>
                    <E T="03">Request for Comments:</E>
                     Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. All comments will become a matter of public record. Comments are invited on: (a) whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information shall have practical utility; (b) the accuracy of the agency's estimate of the burden of the collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; (d) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or other forms of information technology; and (e) estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information.
                </P>
                <SIG>
                    <DATED>Approved: March 6, 2024.</DATED>
                    <NAME>Sara L. Covington,</NAME>
                    <TITLE>IRS Tax Analyst.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05257 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <SUBJECT>Proposed Collection; Comment Request for Form 8582</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Internal Revenue Service (IRS), as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on information collections, as required by the Paperwork Reduction Act of 1995. The IRS is soliciting comments concerning, Passive Activity Los Limitations.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before May 13, 2024 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all written comments to Andres Garcia, Internal Revenue Service, Room 6526, 1111 Constitution Avenue NW, Washington, DC 20224, or by email to 
                        <E T="03">pra.comments@irs.gov.</E>
                         Include “OMB Number 1545-1008—Passive Activity Loss Limitations” in the subject line of the message.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Requests for additional information or copies of this collection should be directed to Martha R. Brinson, at (202) 
                        <PRTPAGE P="18485"/>
                        317-5753, or at Internal Revenue Service, Room 6526, 1111 Constitution Avenue NW, Washington, DC 20224, or through the internet at 
                        <E T="03">Martha.R.Brinson@irs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title:</E>
                     Passive Activity Loss Limitations.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1008.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     8582.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Internal Revenue Code section 469 limits the passive activity losses that a taxpayer may deduct. The passive activity losses from passive activities, to the extent that they exceed income from passive activities, cannot be deducted against nonpassive income. Form 8582 is used to figure the passive activity loss allowed and the actual loss to be reported on the tax returns.
                </P>
                <P>
                    <E T="03">Current Actions:</E>
                     There is no change to the form at this time.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals or households, estates, and trusts.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     250,000.
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     3 hours, 30 minutes.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     875,000.
                </P>
                <P>The following paragraph applies to all of the collections of information covered by this notice:</P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless the collection of information displays a valid OMB control number.</P>
                <P>Books or records relating to a collection of information must be retained as long as their contents may become material in the administration of any internal revenue law. Generally, tax returns and tax return information are confidential, as required by 26 U.S.C. 6103.</P>
                <P>
                    <E T="03">Request for Comments:</E>
                     Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. Comments will be of public record. Comments are invited on: (a) whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information has practical utility; (b) the accuracy of the agency's estimate of the burden of the collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; (d) ways to minimize the burden of the collection of information on or other forms of information technology; and (e) estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information.
                </P>
                <SIG>
                    <DATED>Approved: March 5, 2024.</DATED>
                    <NAME>Martha R. Brinson,</NAME>
                    <TITLE>Tax Analyst.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05334 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <SUBJECT>Proposed Collection; Comment Request for Form 1099-A</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Internal Revenue Service (IRS), as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on information collections, as required by the Paperwork Reduction Act of 1995. The IRS is soliciting comments concerning, Acquisition or Abandonment of Secured Property.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before May 13, 2024 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all written comments to Andres Garcia, Internal Revenue Service, Room 6526, 1111 Constitution Avenue NW, Washington, DC 20224, or by email to 
                        <E T="03">pra.comments@irs.gov.</E>
                         Include “OMB Number 1545-0877—Acquisition or Abandonment of Secured Property” in the subject line of the message.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Requests for additional information or copies of this collection should be directed to Martha R. Brinson, at (202) 317-5753, or at Internal Revenue Service, Room 6526, 1111 Constitution Avenue NW, Washington, DC 20224, or through the internet at 
                        <E T="03">Martha.R.Brinson@irs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title:</E>
                     Acquisition or Abandonment of Secured Property.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0877.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     1099-A.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This form is used by persons who lend money in connection with a trade or business, and who acquire an interest in the property that is security for the loan or who have reason to know that the property has been abandoned, to report the acquisition or abandonment.
                </P>
                <P>
                    <E T="03">Current Actions:</E>
                     There are no changes being made to the form at this time.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Businesses or other for-profit organizations.
                </P>
                <P>
                    <E T="03">Estimated Number of Responses:</E>
                     466,000.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     9 minutes.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     74,560.
                </P>
                <P>The following paragraph applies to all of the collections of information covered by this notice:</P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless the collection of information displays a valid OMB control number.</P>
                <P>Books or records relating to a collection of information must be retained as long as their contents may become material in the administration of any internal revenue law. Generally, tax returns and tax return information are confidential, as required by 26 U.S.C. 6103.</P>
                <P>
                    <E T="03">Request for Comments:</E>
                     Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. Comments will be of public record. Comments are invited on: (a) whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information has practical utility; (b) the accuracy of the agency's estimate of the burden of the collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; (d) ways to minimize the burden of the collection of information on or other forms of information technology; and (e) estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information.
                </P>
                <SIG>
                    <DATED>Approved: March 5, 2024.</DATED>
                    <NAME>Martha R. Brinson,</NAME>
                    <TITLE>Tax Analyst.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05333 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <SUBJECT>Proposed Collection; Comment Request for Form 8924</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Internal Revenue Service (IRS), as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this 
                        <PRTPAGE P="18486"/>
                        opportunity to comment on information collections, as required by the Paperwork Reduction Act of 1995. The IRS is soliciting comments concerning, Excise Tax on Certain Transfers of Qualifying Geothermal or Mineral Interests.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before May 13, 2024 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all written comments to Andres Garcia, Internal Revenue Service, Room 6526, 1111 Constitution Avenue NW, Washington, DC 20224, or by email to 
                        <E T="03">pra.comments@irs.gov.</E>
                         Include “OMB Number 1545-2099—Excise Tax on Certain Transfers of Qualifying Geothermal or Mineral Interests” in the subject line of the message.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Requests for additional information or copies of this collection should be directed to Martha R. Brinson, at (202) 317-5753, or at Internal Revenue Service, Room 6526, 1111 Constitution Avenue NW, Washington, DC 20224, or through the internet at 
                        <E T="03">Martha.R.Brinson@irs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title:</E>
                     Excise Tax on Certain Transfers of Qualifying Geothermal or Mineral Interests.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-2099.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     8924.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This form is required by Section 403 of the Tax Relief and Health Care Act of 2006 which imposes an excise tax on certain transfers of qualifying mineral or geothermal interests.
                </P>
                <P>
                    <E T="03">Current Actions:</E>
                     There are no changes being made to the form at this time.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Businesses or other for-profit organizations.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     20.
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     5 hours, 33 minutes.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     111.
                </P>
                <P>The following paragraph applies to all of the collections of information covered by this notice:</P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless the collection of information displays a valid OMB control number. Books or records relating to a collection of information must be retained as long as their contents may become material in the administration of any internal revenue law. Generally, tax returns and tax return information are confidential, as required by 26 U.S.C. 6103.</P>
                <P>
                    <E T="03">Request for Comments:</E>
                     Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. Comments will be of public record. Comments are invited on: (a) whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information has practical utility; (b) the accuracy of the agency's estimate of the burden of the collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; (d) ways to minimize the burden of the collection of information on or other forms of information technology; and (e) estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information.
                </P>
                <SIG>
                    <DATED>Approved: March 5, 2024.</DATED>
                    <NAME>Martha R. Brinson,</NAME>
                    <TITLE>Tax Analyst.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2024-05335 Filed 3-12-24; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </NOTICE>
    </NOTICES>
    <VOL>89</VOL>
    <NO>50</NO>
    <DATE>Wednesday, March 13, 2024</DATE>
    <UNITNAME>Presidential Documents</UNITNAME>
    <PRESDOCS>
        <PRESDOCU>
            <PROCLA>
                <TITLE3>Title 3—</TITLE3>
                <PRES>
                    The President
                    <PRTPAGE P="18339"/>
                </PRES>
                <PROC>Proclamation 10709 of March 8, 2024</PROC>
                <HD SOURCE="HED">U.S. Hostage and Wrongful Detainee Day, 2024</HD>
                <PRES>By the President of the United States of America</PRES>
                <PROC>A Proclamation</PROC>
                <FP>Today—and every day—the United States reaffirms our sacred pledge to American hostages and detainees wrongfully held abroad: We see you. We stand with you. We will not stop working until you are home and reunited with your family.</FP>
                <FP>This has been a priority for my Administration since day one—and we have made important progress. Over the last 3 years, we have brought home more than 60 Americans being held hostage or wrongfully detained around the world, including from Afghanistan, Burma, Gaza, Haiti, Iran, Russia, Rwanda, Venezuela, West Africa, and more. But we have much more work to do. Too many Americans remain illegally and wrongfully detained, fearing for their lives and not knowing what tomorrow will bring. Too many families remain ripped apart, living in agony and uncertainty every day their loved one remains wrongfully held abroad. No family—and no American—should have to endure this suffering and separation.</FP>
                <FP>That is why my Administration has taken unprecedented action to secure the release of all Americans held hostage or wrongfully detained abroad. In 2022, I signed an Executive Order to strengthen our efforts to address the scourge of hostage-taking and wrongful detention, including issuing more severe consequences for actors that illegally detain American citizens and attempt to use human beings as bargaining chips. Last year, we issued the first-ever sanctions against actors—including in Russia and Iran—for engaging in this abhorrent practice. My Administration has also focused on preventing these cases from occurring in the first place. We have joined 74 nations around the world and the European Union in endorsing the Declaration Against Arbitrary Detention. Finally, we have focused on providing families with loved ones held hostage or wrongfully detained abroad with the resources and support services they deserve.</FP>
                <FP>Here at home, the Department of State launched a risk indictor that warns travelers if there is a high threat of wrongful detention at their destination. For more information on travel advisories, go to travel.state.gov.</FP>
                <FP>As President, I have no higher duty than ensuring the safety and security of my fellow Americans—including all those who remain held hostage or wrongfully detained abroad. I will continue to work to bring them home. I will continue to leverage every resource to punish and deter actors who engage in this despicable and unacceptable practice. I will not stop these efforts until every American is accounted for and safely back home. Today—and every day—that is my pledge.</FP>
                <FP>The Congress, by Public Law 118-31 approved December 22, 2023, has designated March 9 of each year as “U.S. Hostage and Wrongful Detainee Day.”</FP>
                <FP>
                    NOW, THEREFORE, I, JOSEPH R. BIDEN JR., President of the United States of America, do hereby proclaim March 9, 2024, as U.S. Hostage and Wrongful Detainee Day. On this day, as we fly the Hostage and Wrongful Detainee flag at the White House, I call upon the people of the United States to observe this day with relevant programs, ceremonies, and activities.
                    <PRTPAGE P="18340"/>
                </FP>
                <FP>IN WITNESS WHEREOF, I have hereunto set my hand this eighth day of March, in the year of our Lord two thousand twenty-four, and of the Independence of the United States of America the two hundred and forty-eighth.</FP>
                <GPH SPAN="1" DEEP="80" HTYPE="RIGHT">
                    <GID>BIDEN.EPS</GID>
                </GPH>
                <PSIG> </PSIG>
                <FRDOC>[FR Doc. 2024-05441 </FRDOC>
                <FILED>Filed 3-12-24; 8:45 am]</FILED>
                <BILCOD>Billing code 3395-F4-P</BILCOD>
            </PROCLA>
        </PRESDOCU>
    </PRESDOCS>
    <VOL>89</VOL>
    <NO>50</NO>
    <DATE>Wednesday, March 13, 2024</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="18487"/>
            <PARTNO>Part II</PARTNO>
            <AGENCY TYPE="P">Federal Communications Commission</AGENCY>
            <CFR>47 CFR Part 9</CFR>
            <TITLE>Location-Based Routing for Wireless 911 Calls; Final Rule</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="18488"/>
                    <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                    <CFR>47 CFR Part 9</CFR>
                    <DEPDOC>[PS Docket No. 18-64; FCC 24-4; FR ID 202993]</DEPDOC>
                    <SUBJECT>Location-Based Routing for Wireless 911 Calls</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Federal Communications Commission.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Final rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>The Federal Communications Commission (the FCC or Commission) adopted a Report and Order in PS Docket No. 18-64, FCC 24-4, on January 25, 2024, and released on January 26, 2024. This document is a summary of the Commission's Report and Order. The Report and Order adopted rules to more precisely route wireless 911 calls and Real-Time Texts (RTT) to Public Safety Answering Points (PSAPs), which can result in faster response times during emergencies. Wireless 911 calls have historically been routed to PSAPs based on the location of the cell tower that handles the call. Sometimes, however, the 911 call is routed to the wrong PSAP because the cell tower is not in the same jurisdiction as the 911 caller. This can happen, for instance, when an emergency call is placed near a county border. These misrouted 911 calls must be transferred from one PSAP to another, which consumes time and resources and can cause confusion and delay in emergency response. The Report and Order requires wireless providers to deploy technology that supports location-based routing, a method that relies on precise information about the location of the wireless caller's device, on their internet Protocol (IP)-based networks and to use location-based routing to route 911 voice calls and RTT communications to 911 originating on those networks when caller location is accurate and timely. The Report and Order provides six months for nationwide wireless providers to implement location-based routing for wireless 911 voice calls and provides 24 months for non-nationwide wireless providers to implement location-based routing of wireless 911 voice calls. The Report and Order provides 24 months for all wireless providers to implement location-based routing for RTT communications to 911.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P> </P>
                        <P>
                            <E T="03">Effective date:</E>
                             May 13, 2024.
                        </P>
                        <P>
                            <E T="03">Compliance date:</E>
                             Compliance will not be required for § 9.10(s)(4) and (5) until a document is published in the 
                            <E T="04">Federal Register</E>
                             announcing a compliance date and revising or removing § 9.10(s)(6).
                        </P>
                    </EFFDATE>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            Rachel Wehr, Attorney Advisor, Policy and Licensing Division, Public Safety and Homeland Security Bureau, (202) 418-1138, 
                            <E T="03">Rachel.Wehr@fcc.gov,</E>
                             or Brenda Boykin, Deputy Division Chief, Policy and Licensing Division, Public Safety and Homeland Security Bureau, (202) 418-2062, 
                            <E T="03">Brenda.Boykin@fcc.gov</E>
                            .
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>
                        This document is a summary of the Commission's Report and Order. The full text of the Report and Order is available for public inspection at 
                        <E T="03">https://docs.fcc.gov/public/attachments/FCC-24-4A1.pdf</E>
                        . To request materials in accessible formats for people with disabilities (Braille, large print, electronic files, audio format), or to request reasonable accommodations (
                        <E T="03">e.g.,</E>
                         accessible format documents, sign language interpreters, CART, etc.), send an email to 
                        <E T="03">fcc504@fcc.gov</E>
                         or call the Consumer &amp; Governmental Affairs Bureau at 202-418-0530 (voice).
                    </P>
                    <HD SOURCE="HD1">Congressional Review Act</HD>
                    <P>The Commission has determined, and the Administrator of the Office of Information and Regulatory Affairs, Office of Management and Budget, concurs, that this rule is major under the Congressional Review Act, 5 U.S.C. 804(2). The Commission will send a copy of the Report and Order to Congress and the Government Accountability Office pursuant to 5 U.S.C. 801(a)(1)(A).</P>
                    <HD SOURCE="HD1">Synopsis</HD>
                    <HD SOURCE="HD1">I. Background</HD>
                    <P>
                        1. This document is a summary of the Commission's Report and Order. In this document, we require Commercial Mobile Radio Service (CMRS) providers 
                        <SU>1</SU>
                        <FTREF/>
                         to implement location-based routing for wireless 911 voice calls and real-time text (RTT) communications 
                        <SU>2</SU>
                        <FTREF/>
                         to 911 nationwide. With location-based routing (LBR) as implemented under these rules, CMRS providers will use precise location information to route wireless 911 voice calls and RTT communications to 911 to the appropriate public safety answering point (PSAP). For the millions of individuals seeking emergency assistance each year by wireless 911 voice call or RTT communication to 911, improving routing for these services will reduce emergency response times and save lives.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             In this document and the Report and Order, we use the term Commercial Mobile Radio Service (CMRS) provider to refer to providers of CMRS, as defined in 47 CFR 9.3 (“Commercial mobile radio service (CMRS)”). When addressing the record in this proceeding, we assume that commenters using terms such as “wireless carriers” or “wireless providers” refer to CMRS providers subject to part 9 of the Commission's rules.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             The Commission defines real-time text as “[t]ext communications that are transmitted over internet Protocol (IP) networks immediately as they are created, 
                            <E T="03">e.g.,</E>
                             on a character-by-character basis.” 47 CFR 9.3; 
                            <E T="03">accord id.</E>
                             67(g). In this document and the Report and Order, we use the term “RTT communications” to refer to instances in which an RTT user initiates contact with 911, for consistency with our part 9 and part 67 rules. 
                            <E T="03">See</E>
                             47 CFR 9.10(c), 67.1(g), 67.2(c)(2). When addressing the record in this proceeding, we assume that commenters using the terms “RTT call” or “RTT message” refer to the same RTT communications described in the Commission's part 9 and part 67 rules.
                        </P>
                    </FTNT>
                    <P>
                        2. In December 2022, the Commission adopted a notice of proposed rulemaking proposing to require CMRS providers and covered text providers to implement location-based routing for wireless 911 voice calls and texts nationwide.
                        <SU>3</SU>
                        <FTREF/>
                         Public safety commenters overwhelmingly supported the Commission's proposals. Legacy tower-based routing results in millions of 911 voice calls nationwide arriving at the incorrect PSAP for the caller's location, which can result in a delay of a minute or more in dispatch and response.
                        <SU>4</SU>
                        <FTREF/>
                         The record confirms that implementing location-based routing is technologically feasible and will significantly reduce wireless 911 voice call transfers, saving valuable time for both PSAPs and callers. As a result of the location-based routing rules we adopt, millions more wireless 911 calls will reach the appropriate PSAP without the need for transfer or delay.
                    </P>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             
                            <E T="03">Location-Based Routing for Wireless 911 Calls,</E>
                             PS Docket No. 18-64, Notice of Proposed Rulemaking, 37 FCC Rcd 15183, 15184, para. 1 (2022), 88 FR 2565 (January 17, 2023) (notice of proposed rulemaking or NPRM).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             The Commission has previously found that a one minute increase in response times increases mortality, and that a one minute decrease in response times decreases mortality. 
                            <E T="03">See, e.g., Wireless E911 Location Accuracy Requirements,</E>
                             Third Further Notice of Proposed Rulemaking, 29 FCC Rcd 2374, 2388-89, para. 33 &amp; n.70 (2014), 79 FR 17820 (March 28, 2014). As stated in the notice of proposed rulemaking and affirmed in the Report and Order, the Commission estimates that the implementation of wireless location-based routing under the rules we adopt in this document will save 13,837 lives annually, assuming a one-minute decrease in response time. 
                            <E T="03">See</E>
                             Notice of Proposed Rulemaking, 37 FCC Rcd at 15206-07, para. 61 &amp; n.161.
                        </P>
                    </FTNT>
                    <P>3. To facilitate the implementation of location-based routing for wireless 911 voice calls and RTT communications to 911, we take the following actions:</P>
                    <P>
                        • We require CMRS providers to deploy location-based routing technology for wireless 911 voice calls and RTT communications to 911 on their internet Protocol (IP)-based 
                        <PRTPAGE P="18489"/>
                        networks (
                        <E T="03">i.e.,</E>
                         4G LTE, 5G, and subsequent generations of IP-based networks). We also require CMRS providers to use location-based routing to route wireless 911 voice calls and RTT communications to 911 originating on their IP-based networks when location information meets certain thresholds for accuracy and timeliness.
                    </P>
                    <P>• We require CMRS providers to use location-based routing for wireless 911 voice calls and RTT communications to 911 when caller location information available to the CMRS provider's network at time of routing is ascertainable within a radius of 165 meters at a confidence level of at least 90%. In the absence of these conditions, CMRS providers must use alternative routing methods based on “best available” location information, which may include but is not limited to device-based or tower-based location information.</P>
                    <P>
                        • We adopt the proposed six-month timeline for nationwide CMRS providers to implement location-based routing for wireless 911 voice calls and provide twenty-four months for non-nationwide CMRS providers to implement location-based routing of wireless 911 voice calls.
                        <SU>5</SU>
                        <FTREF/>
                         In addition, we provide 24 months for all CMRS providers to implement location-based routing for RTT communications to 911.
                    </P>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             The Commission defines a “[n]on-nationwide CMRS provider” for purposes of its part 9 rules as “[a]ny CMRS provider other than a nationwide CMRS provider.” 47 CFR 9.10(i)(1)(v). A “[n]ationwide CMRS provider” for purposes of the Commission's part 9 rules is “[a] CMRS provider whose service extends to a majority of the population and land area of the United States.” 47 CFR 9.10(i)(1)(iv).
                        </P>
                    </FTNT>
                    <P>• We require CMRS providers within 60 days of the applicable compliance deadlines to certify and submit evidence of compliance with location-based routing requirements. At that time, CMRS providers also must submit one-time live call data reporting on the routing methodologies for calls in live call areas, and they must certify the privacy of location information used for location-based routing.</P>
                    <P>
                        • We defer consideration of proposals in the notice of proposed rulemaking to require CMRS providers and covered text providers 
                        <SU>6</SU>
                        <FTREF/>
                         to implement location-based routing for Short Message Service (SMS) texts to 911.
                    </P>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             The Commission defines “covered text provider” as including “all CMRS providers as well as all providers of interconnected text messaging services that enable consumers to send text messages to and receive text messages from all or substantially all text-capable U.S. telephone numbers, including through the use of applications downloaded or otherwise installed on mobile phones.” 47 CFR 9.10(q)(1).
                        </P>
                    </FTNT>
                    <P>
                        • We defer consideration of proposals and issues raised in the notice of proposed rulemaking concerning IP-formatted delivery of wireless 911 voice calls, texts, and associated routing information for consideration in the Commission's pending Next Generation 911 (NG911) Transition docket (PS Docket No. 21-479—Facilitating Implementation of Next Generation 911 Services).
                        <SU>7</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             
                            <E T="03">See Facilitating Implementation of Next Generation 911 Services (NG911),</E>
                             PS Docket No. 21-479, Notice of Proposed Rulemaking, FCC 23-47, 2023 WL 3946685 (June 9, 2023), 88 FR 43514 (July 10, 2023), 
                            <E T="03">https://www.fcc.gov/document/fcc-proposes-action-expedite-transition-next-generation-911-0</E>
                             (
                            <E T="03">NG911 Notice of Proposed Rulemaking</E>
                            ).
                        </P>
                    </FTNT>
                    <P>
                        4. Legacy Enhanced 911 Routing. When the first 911 call was placed in 1968, 911 service was provided to the public over wireline telephone networks, and wireline providers used the fixed location of the calling telephone to route 911 calls to the nearest PSAP.
                        <SU>8</SU>
                        <FTREF/>
                         With the deployment of the first generation of cellular service, wireless 911 voice calls could originate from any location served by the wireless network, and the caller could move locations during the call. To enable timely routing of wireless 911 voice calls, CMRS providers typically programmed their networks to use the location of the first cell tower receiving the call to determine the nearest PSAP and route the call accordingly. This became the basis for routing of wireless Enhanced 911 (E911) calls (legacy E911 routing).
                    </P>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             
                            <E T="03">Location-Based Routing for Wireless 911 Calls,</E>
                             PS Docket No. 18-64, Notice of Inquiry, 33 FCC Rcd 3238, 3240, para. 6 (2018) (
                            <E T="03">Notice of Inquiry</E>
                            ).
                        </P>
                    </FTNT>
                    <P>
                        5. Wireless 911 Voice Call Misroutes. Technical limitations of legacy E911 routing can result in a CMRS provider routing a wireless 911 voice call to a PSAP other than the one designated by the relevant state or local 911 authority to receive 911 calls from the caller's actual location.
                        <SU>9</SU>
                        <FTREF/>
                         The Commission considers wireless 911 voice calls routed to a PSAP other than the one designated for the caller's location to be “misrouted,” although such misroutes generally result from tower-based call routing mechanisms working as designed, not from technical failure of those mechanisms. The Alliance for Telecommunications Industry Solutions (ATIS) estimates that on average 12% of wireless legacy E911 voice calls nationwide are misrouted.
                        <SU>10</SU>
                        <FTREF/>
                         Other commenters indicate that the percentage of misrouted wireless 911 voice calls is higher in some jurisdictions.
                        <SU>11</SU>
                        <FTREF/>
                         These estimates support the conclusion that tower-based routing causes millions of wireless 911 voice calls to be misrouted annually.
                        <SU>12</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             Notice of Proposed Rulemaking, 37 FCC Rcd at 15185-86, para. 7. For example, a cell tower in Northern Virginia may pick up a wireless 911 voice call originating in Washington, DC, but route the call to a Virginia PSAP. 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             Alliance for Telecommunications Industry Solutions (ATIS), Analysis of Predetermined Cell Sector Routing Outcomes Compared to Caller's Device Location, 
                            <E T="03">ATIS-0500039</E>
                             at 4 (July 2, 2019), 
                            <E T="03">https://access.atis.org/apps/group_public/document.php?document_id=48697</E>
                             (
                            <E T="03">ATIS-0500039</E>
                            ). Intrado cites a 2018 study concluding that 12.96% out of a set of five million wireless 911 calls were misrouted. Intrado Life &amp; Safety, Inc. (Intrado) Public Notice Comments at 3 &amp; n.8, 4 (rec. July 11, 2022) (Intrado PN Comments).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             For example, the Fayetteville (Arkansas) Police Department reports that “roughly 30% or more” of the 911 calls its jurisdiction receives are misrouted from neighboring jurisdictions. Natisha Claypool, Assistant Dispatch Manager, Fayetteville Police Department Public Notice Comments (rec. July 11, 2022). Intrado estimates, based on data collected in AT&amp;T's pilot implementation of location-based routing in February/March 2022, that Palm Beach County, Florida, was experiencing misrouted calls with tower-based routing at a rate of at least 11%, and as high as 20-50% along PSAP boundaries. Intrado PN Comments at 4-5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             In the Commission's 2023 annual 911 fee report, respondents reported receiving a combined total of approximately 158 million wireless 911 voice calls in calendar year 2022. FCC, Fifteenth Annual Report to Congress on State Collection and Distribution of 911 and Enhanced 911 Fees and Charges at 16, Table 3 (2023), 
                            <E T="03">https://www.fcc.gov/general/911-fee-reports</E>
                             (Fifteenth Annual 911 Fee Report). Assuming 12% of these calls were misrouted, misroutes would total nearly 19 million calls. NENA: The 9-1-1 Association (NENA) estimates that 23 million wireless 911 voice calls are misrouted annually. NENA Notice of Proposed Rulemaking Comments at 2 (rec. Feb. 15, 2023) (NENA NPRM Comments).
                        </P>
                    </FTNT>
                    <P>
                        6. When a wireless 911 voice call is misrouted, the answering telecommunicator must transfer the call to the PSAP that has jurisdiction to dispatch aid to the 911 caller's location. This process consumes time and resources for both the transferring PSAP and the receiving PSAP and delays the dispatch of first responders to render aid. Commenters submit anecdotal evidence that a typical misroute introduces a delay of about a minute.
                        <SU>13</SU>
                        <FTREF/>
                         NENA estimates that call transfers consume over 200,000 hours per year of excess 911 professional labor. Misrouted wireless 911 voice calls can also contribute to confusion and delay in 
                        <PRTPAGE P="18490"/>
                        emergency response.
                        <SU>14</SU>
                        <FTREF/>
                         This delay can have deadly consequences.
                        <SU>15</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Association of Public-Safety Communications Officials International, Inc. (APCO) Public Notice Comments at 2 (rec. July 11, 2022) (APCO PN Comments) (noting that “it's possible that a misrouted call will introduce a delay of a minute or longer”); NENA Public Notice Comments at 4 (rec. July 11, 2022) (“[T]he general anecdotal consensus was that a call transfer typically takes ‘about a minute.’ ”); Peninsula Fiber Network Public Notice Comments at 1 (rec. July 8, 2022) (“Each transfer takes between 15 to 90 seconds to set up and complete.”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             For example, on June 4, 2020, 16-year-old Fitz Thomas drowned at Confluence Park on the Potomac River, which separates Loudoun County, Virginia, and Montgomery County, Maryland. Press Release, Loudoun County Office of the County Administrator, Public Affairs and Communications, Loudoun County Releases Significant Incident Review of Goose Creek Drowning at 1 (Aug. 31, 2020), 
                            <E T="03">https://www.loudoun.gov/ArchiveCenter/ViewFile/Item/10062.</E>
                             Due to the incident's proximity to the jurisdictional border of the Potomac River and the use of legacy E911 routing, both counties received wireless 911 calls routed from the park located on the Virginia side of the river. 
                            <E T="03">Id.</E>
                             at 2. Efforts to determine Thomas's actual location contributed to a delay in dispatching first responders. 
                            <E T="03">Id.</E>
                             On July 15, 2022, Ma Kaing was shot and killed by a stray bullet outside her home in the East Colfax neighborhood of Denver. Jennifer Kovaleski, 
                            <E T="03">Stuck on the line: Cellphone calls routed to the wrong 911 center are costing life-saving seconds,</E>
                             Denver7 (Nov. 19, 2022), 
                            <E T="03">https://www.denver7.com/news/investigations/stuck-on-the-line-cellphone-calls-routed-to-the-wrong-911-center-are-costing-life-saving-seconds.</E>
                             The news media reported that four calls from her family and neighbors were misrouted to a neighboring PSAP and required transfer; three callers hung up after waiting minutes on hold. 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             The news media have widely reported on such tragic occurrences. For example, in December 2015, dispatchers were unable to locate Shanell Anderson, who drowned after accidentally driving off the road and into a pond close to the line between Fulton and Cherokee Counties in Georgia. Brendan Keefe and Phillip Kish, 
                            <E T="03">Lost on the Line: Why 911 is broken,</E>
                             11ALIVE (Aug. 12, 2019), 
                            <E T="03">https://www.11alive.com/article/news/local/lost-on-the-line-why-911-is-broken/85-225104578.</E>
                             According to the news media, Shanell Anderson was able to call 911, but the call was picked up by a cell tower in Fulton County and routed to that county's PSAP, where critical minutes were lost while dispatchers sought to determine the county in which she was located (Cherokee County). 
                            <E T="03">Id.</E>
                             In another incident in 2008, Olidia Kerr Day made a wireless 911 call before she was fatally shot in a murder-suicide in front of the Plantation, Florida, police department. Sofia Santana, 
                            <E T="03">Cell Phone 911 Calls Are Often Routed to the Wrong Call Centers,</E>
                             Sun Sentinel (June 21, 2008), 
                            <E T="03">https://www.sun-sentinel.com/sfl-flbsafe911calls0621sbjun21-story.html.</E>
                             According to the news media, although she placed the call in Plantation, the call was routed to the 911 center in Sunrise, Florida, and had to be transferred to Plantation. 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        7. Location-Based Routing Notice of Inquiry. In 2018, the Commission released a Notice of Inquiry seeking comment on issues related to misrouted wireless 911 calls, including the feasibility of location-based routing. Historically, generating precise caller location information typically required too much time to be used for 911 call routing. The Commission noted, however, that then-recent advances in location technology suggested it was feasible to pinpoint a wireless 911 voice caller's location quickly enough to support an initial routing determination. The Commission also found that many location-based routing methods were promising. The record received in response to the Notice of Inquiry confirmed the emergence of potential location-based routing solutions but also indicated uncertainty about the capabilities of such solutions at the time.
                        <SU>16</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>16</SU>
                             Commenters to the 
                            <E T="03">Notice of Inquiry</E>
                             offered varying opinions about whether technologies were capable of location-based routing without delaying 911 calls. 
                            <E T="03">See, e.g.,</E>
                             AT&amp;T Notice of Inquiry Reply at 11 (rec. June 28, 2018) (“Even the most promising of location-based technologies . . . have limits.”); Motorola Solutions, Inc. Notice of Inquiry Comments at 2 (rec. May 7, 2018) (asserting that testing has confirmed that location-based wireless routing is faster and more accurate than legacy wireless routing).
                        </P>
                    </FTNT>
                    <P>
                        8. Location-Based Routing Public Notice. In June 2022, the Commission released a Public Notice to refresh the record on location-based routing developments since the Notice of Inquiry.
                        <SU>17</SU>
                        <FTREF/>
                         Commenters confirmed that continued reliance on legacy E911 routing methodology results in a considerable number of wireless 911 voice call misroutes, which imposes significant burdens on public safety. Public safety commenters agreed that early location-based routing implementations by CMRS providers had shown that the technology was now technologically feasible. Several commenters noted that device-based hybrid (DBH) location technologies 
                        <SU>18</SU>
                        <FTREF/>
                         were widely available on mobile devices and could be used for routing a high percentage of wireless 911 voice calls.
                    </P>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             
                            <E T="03">Federal Communications Commission Seeks to Refresh the Record on Location-Based Routing for Wireless 911 Calls,</E>
                             PS Docket No. 18-64, Public Notice, 37 FCC Rcd 7196, 7196 (2022) (
                            <E T="03">Public Notice</E>
                            ).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             Device-based hybrid (DBH) location is an estimation method that typically utilizes either a selection or a combination of location methods available to the handset in a given environment, including crowd-sourced Wi-Fi, A-GNSS, and possibly other handset-based sensors. 
                            <E T="03">Public Notice,</E>
                             37 FCC Rcd at 7197-98 n.8 (citing 
                            <E T="03">CSRIC V LBR Report</E>
                             at 16). It also includes an associated uncertainty estimate reflective of the quality of the returned location. 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        9. Location-Based Routing Notice of Proposed Rulemaking. On December 22, 2022, the Commission adopted the notice of proposed rulemaking in this proceeding, which proposed rules for CMRS and covered text providers to implement location-based routing for wireless 911 voice calls and 911 texts 
                        <SU>19</SU>
                        <FTREF/>
                         nationwide, including wireless 911 voice calls and 911 text messages originating in legacy, transitional, and NG911-capable public safety jurisdictions.
                        <SU>20</SU>
                        <FTREF/>
                         The Commission proposed to establish requirements with respect to the accuracy and timeliness of location information CMRS and covered text providers would use to comply with location-based routing requirements. In particular, the Commission proposed to require CMRS providers and covered text providers to use location-based routing for 911 calls and texts when they have location information that meets the following specifications for timeliness and accuracy: (i) the information must be available to the provider network at the time the call or text is routed, and (ii) the information must identify the caller's horizontal location within a radius of 165 meters at a confidence level of at least 90%.
                    </P>
                    <FTNT>
                        <P>
                            <SU>19</SU>
                             A “911 text message” is “a message, consisting of text characters, sent to the short code ‘911’ and intended to be delivered to a PSAP by a covered text provider, regardless of the text messaging platform used.” 47 CFR 9.10(q)(9). The Commission's text-to-911 rules are technology neutral and apply to both Short Message Service (SMS) and real-time text (RTT). 
                            <E T="03">Transition from TTY to Real-Time Text Technology; Petition for Rulemaking to Update the Commission's Rules for Access to Support the Transition from TTY to Real-Time Text Technology, and Petition for Waiver of Rules Requiring Support of TTY Technology,</E>
                             CG Docket No. 16-145, GN Docket No. 15-178, Report and Order, 31 FCC Rcd 13568, 13593, para. 45 n.181 (2016), 82 FR 7699 (January 23, 2017) (
                            <E T="03">RTT Order</E>
                            ). RTT transition obligations only apply to a subset of covered text providers: “those entities that are involved in the provision of IP-based wireless voice communication service, and only to the extent that their services are subject to existing TTY technology support requirements under Parts 6, 7, 14, 20, or 64 of the Commission's rules.” 
                            <E T="03">RTT Order,</E>
                             31 FCC Rcd at 13576-77, para. 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>20</SU>
                             Notice of Proposed Rulemaking, 37 FCC Rcd at 15184-85, para. 3. In the notice of proposed rulemaking, the Commission used the term “NG911-capable” to refer to PSAPs or jurisdictions that have implemented IP-based network and software components that are capable of supporting the provision of NG911, including but not limited to an Emergency Services internet Protocol Network (ESInet). 
                            <E T="03">Id.</E>
                             at 15184, para. 3 n.5. NG911 relies on IP-based architecture rather than the Public Switched Telephone Network (PSTN)-based architecture of legacy 911 to provide an expanded array of emergency communications services that encompasses both the core functionalities of legacy E911 and additional functionalities that take advantage of the enhanced capabilities of IP-based devices and networks. 
                            <E T="03">Framework for Next Generation 911 Deployment,</E>
                             PS Docket No. 10-255, Notice of Inquiry, 25 FCC Rcd 17869, 17877, para. 18 (2010), 76 FR 2297 (January 13, 2011). NG911 architecture also provides for transitional network components to enable delivery of legacy 911 calls to ESInets during the transition to full end-state NG911. 
                            <E T="03">See id.</E>
                             at 17878, para. 20 (explaining that emergency calls can be delivered to ESInets from legacy networks).
                        </P>
                    </FTNT>
                    <P>
                        10. The Commission also proposed that when location information does not meet one or both of these requirements, CMRS providers and covered text providers would be required to route 911 calls and texts based on the best available location information, which could include cell tower coordinates. In addition, to help ensure that public safety jurisdictions transitioning to NG911 could realize the benefits of location-based routing in an efficient and cost-effective manner, the Commission proposed to require CMRS providers and covered text providers to deliver wireless 911 voice calls, texts, 
                        <PRTPAGE P="18491"/>
                        and location information for routing 
                        <SU>21</SU>
                        <FTREF/>
                         in IP format upon request of 911 authorities 
                        <SU>22</SU>
                        <FTREF/>
                         who have established the capability to accept NG911-compatible IP-based 911 communications. At the time of the notice of proposed rulemaking, AT&amp;T, T-Mobile, and Verizon had stated publicly in the record or elsewhere that they had deployed or planned to deploy location-based routing to some extent on their networks for voice calls.
                        <SU>23</SU>
                        <FTREF/>
                         The Commission received twenty-six comments, fourteen replies, and several ex parte filings.
                    </P>
                    <FTNT>
                        <P>
                            <SU>21</SU>
                             In NG911 architecture, device-based location information embedded in IP-formatted 911 calls is first used by the provider to route the call to an ESInet, and the ESInet operator then applies NG911 network routing policies to the embedded information to route the call to the appropriate PSAP. Notice of Proposed Rulemaking, 37 FCC Rcd at 15203, para. 53.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>22</SU>
                             While the Commission has not specifically defined the term “911 authorities” in this proceeding, we use this term in this document to generally mean “[t]he state, territorial, regional, Tribal, or local agency or entity with the authority and responsibility under applicable law to designate the point(s) to receive emergency calls.” 
                            <E T="03">NG911 Notice of Proposed Rulemaking</E>
                             at *21, para. 53 (proposing a definition of the term “911 Authority” that would define the term for purposes of Commission rules related to the NG911 transition).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>23</SU>
                             Press Release, T-Mobile USA, Inc. (T-Mobile), T-Mobile First to Roll Out Cutting-Edge 911 Capabilities (Dec. 17, 2020), 
                            <E T="03">https://www.t-mobile.com/news/network/tmobile-next-generation-911-location-based-routing</E>
                             (T-Mobile Dec. 17, 2020 Press Release); T-Mobile Public Notice Reply at 2 &amp; n.6 (rec. July 25, 2022) (T-Mobile PN Reply); AT&amp;T PN Comments at 4; CB Cotton, Verizon plans to update 911 routing technology after Denver's East 
                            <E T="03">Colfax</E>
                             neighborhood calls for change, Denver7 (Aug. 5, 2022), 
                            <E T="03">https://www.denver7.com/news/local-news/verizon-plans-to-update-911-routing-technology-after-denvers-east-colfax-neighborhood-calls-for-change.</E>
                        </P>
                    </FTNT>
                    <P>11. Virtually all public safety commenters and some additional commenters support Commission action to require CMRS providers to implement location-based routing for wireless 911 voice calls. Multiple public safety commenters and Intrado support the Commission's proposal that CMRS providers implement location-based routing nationwide. Commenters representing wireless interests urge the Commission to allow CMRS providers to implement location-based routing voluntarily or on a PSAP-by-PSAP basis, as opposed to a nationwide mandate. With respect to text-to-911, numerous commenters support requiring covered text providers to implement location-based routing, but some commenters contend that such a requirement would be premature. Citing a lack of technical standards for routing SMS texts to 911, NENA, ATIS, and Southern Linc oppose requiring covered text providers to implement location-based routing for SMS but suggest that the Commission should require location-based routing for IP-based text solutions such as RTT.</P>
                    <P>
                        12. In response to the Commission's proposed timeliness and accuracy requirements for use of location-based routing, some commenters express support for the proposed requirements,
                        <SU>24</SU>
                        <FTREF/>
                         while others oppose the proposed accuracy threshold and request flexibility for providers to set their own thresholds. In response to the Commission's proposed requirement for CMRS and covered text providers to deliver 911 calls, texts, and associated routing information in IP format upon request of 911 authorities who have established the capability to accept such communications, multiple commenters ask the Commission to address such proposals together with corresponding proposed requirements for other types of originating service providers in a separate proceeding.
                        <SU>25</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>24</SU>
                             APCO NPRM Comments at 2; Adams County et al. NPRM Comments at 3; Boulder Regional Emergency Telephone Service Authority (BRETSA) Notice of Proposed Rulemaking Reply at 6 (rec. Mar. 20, 2023) (BRETSA NPRM Reply); Intrado NPRM Comments at 5; 
                            <E T="03">see also</E>
                             AT&amp;T NPRM Comments at 4 (supporting a definition of “device-based location information” that is tied to timeliness and accuracy metrics “that the Commission believes would represent a significant improvement over cell-based routing methodologies”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>25</SU>
                             Letter from Christiaan Segura, Director, Regulatory Affairs, CTIA—The Wireless Association (CTIA), to Marlene H. Dortch, Secretary, FCC, PS Docket No. 18-64, at 2 (filed July 3, 2023) (CTIA July 3, 2023 Ex Parte); Intrado NPRM Comments at 2, 5-6; Texas 9-1-1 Entities NPRM Comments at 5-6 n.21; NENA NPRM Reply at 4-5; Verizon Notice of Proposed Rulemaking Reply at 4-5 (rec. Mar. 20, 2023) (Verizon NPRM Reply) (recommending the Commission “coupl[e] LBR with a framework for i3-based NG911 implementation”); see also Letter from Joely Denkinger, Regulatory Counsel, Federal Affairs, GCI Communication Corp. (GCI), to Marlene H. Dortch, Secretary, FCC, PS Docket Nos. 18-64, 21-479, at 1 (filed July 17, 2023) (GCI July 17, 2023 Ex Parte).
                        </P>
                    </FTNT>
                    <P>13. NG911 Notice of Proposed Rulemaking. In June 2023, the Commission adopted a notice of proposed rulemaking in PS Docket No. 21-479 to advance the nationwide transition to Next Generation 911 (NG911 Notice of Proposed Rulemaking). In the NG911 Notice of Proposed Rulemaking, the Commission proposed to require wireline, interconnected Voice over internet Protocol (VoIP), and internet-based Telecommunications Relay Service (TRS) providers to complete all translation and routing to deliver 911 calls, including associated location information, in the requested IP-based format to an Emergency Services IP network (ESInet) or other designated point(s) that allow emergency calls to be answered, upon request of 911 authorities who have certified the capability to accept IP-based 911 communications. This proposal is similar to that proposed for CMRS and covered text providers in the notice of proposed rulemaking in this proceeding.</P>
                    <P>
                        14. Ongoing Location-Based Routing Deployment. As the Commission noted in the notice of proposed rulemaking, several developments indicate that location-based routing has become a viable methodology for CMRS providers to route wireless 911 voice calls and texts. These developments include studies on misroutes and location-based routing technology and increased deployment of DBH location technologies on consumer handsets.
                        <SU>26</SU>
                        <FTREF/>
                         In 2019, ATIS published two studies on legacy E911 misroutes and the feasibility of location-based routing.
                        <SU>27</SU>
                        <FTREF/>
                         In those studies, ATIS concluded that “location-based routing is technically feasible within the timing considerations recommended by [Communications Security, Reliability, and Interoperability Council (CSRIC)] V” 
                        <SU>28</SU>
                        <FTREF/>
                         and evaluated where “sub-optimal routing” occurred for a sample set of wireless emergency calls. ATIS has also issued two standards that support location-based routing: ATIS-0700042 (Enhancing Location-Based Routing of Emergency Calls) and ATIS-0700015 (ATIS Standard for Implementation of 3GPP Common IMS Emergency Procedures for IMS Origination and ESInet/Legacy Selective Router 
                        <PRTPAGE P="18492"/>
                        Termination). The Competitive Carriers Association (CCA) states that in these and other documents, “ATIS has defined several architecture options that carriers can use to provide location-based routing as well as several call flow options from which carriers can choose to employ to conduct location-based routing.” 
                        <SU>29</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>26</SU>
                             Press Release, CTIA, Wireless Industry Announces Development in Improving 9-1-1 Location Accuracy (Sept. 5, 2018), 
                            <E T="03">https://www.ctia.org/news/wireless-industry-announces-development-in-improving-9-1-1-location-accuracy;</E>
                             Letter from Paul Margie, Counsel, Apple Inc., to Marlene H. Dortch, Secretary, FCC, PS Docket No. 18-64 et al., at 2 (filed Sept. 24, 2019) (Apple Sept. 24, 2019 
                            <E T="03">Ex Parte</E>
                            ). Device-based hybrid (DBH) location is “[a]n estimation method that typically utilizes either a selection or a combination of location methods available to the handset in a given environment—including crowd-sourced Wireless Fidelity (Wi-Fi), Assisted-Global Navigation Satellite System (A-GNSS), and possibly other handset-based sensors.” 
                            <E T="03">ATIS-0700042</E>
                             at 2. “It also includes an associated uncertainty estimate reflective of the quality of the returned location.” 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>27</SU>
                             
                            <E T="03">ATIS-0700042; ATIS-0500039.</E>
                             ATIS observed that calls that are “sub-optimally routed” tend to occur “[a]long PSAP boundaries,” “[i]n areas having a dense concentration of PSAPs,” “[a]round major water features,” and “[a]long narrow strips of jurisdictional territory.” 
                            <E T="03">ATIS-0500039</E>
                             at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>28</SU>
                             
                            <E T="03">ATIS-0700042</E>
                             at 22. CSRIC is a Federal advisory committee subject to the requirements of the Federal Advisory Committee Act (FACA), 5 U.S.C. App. 2, and charged with providing recommendations to the Commission to ensure, among other things, the security and reliability of communications systems. FCC, 
                            <E T="03">Communications Security, Reliability, and Interoperability Council, https://www.fcc.gov/about-fcc/advisory-committees/communications-security-reliability-and-interoperability-council-0</E>
                             (last visited Jan. 17, 2023).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>29</SU>
                             CCA NPRM Comments at 7. CCA also states that “3GPP has also addressed how to implement location-based routing, and several 3GPP specifications relate to location services and emergency calling.” CCA NPRM Comments at 9. In particular, CCA identifies TS 23.167, entitled “Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS) emergency sessions,” as identifying “architectural principles, location information principles, a reference architecture, functional descriptions, procedures for establishing an IMS emergency session, call flows, and related information.” 
                            <E T="03">Id.</E>
                             CCA also notes that other 3GPP specifications, including TS 36.305—“Stage 2 functional specification of User Equipment (UE) positioning in E-UTRAN” and TS 38.305—“NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN,” provide additional pertinent information regarding the implementation of location services data. 
                            <E T="03">Id.</E>
                             at 9-10.
                        </P>
                    </FTNT>
                    <P>
                        15. The three nationwide CMRS providers are continuing to deploy location-based routing for wireless 911 voice calls on their networks. AT&amp;T completed the rollout of location-based routing on its network in June 2022 and uses location-based routing to deliver wireless 911 voice calls to nearly all PSAPs nationwide, regardless of whether such PSAPs support legacy E911 or are transitioning to NG911.
                        <SU>30</SU>
                        <FTREF/>
                         T-Mobile launched location-based routing on its network in the states of Texas and Washington in 2020 and as of December 2023 had deployed location-based routing for wireless 911 voice calls to 1,591 PSAPs with an additional 596 in progress.
                        <SU>31</SU>
                        <FTREF/>
                         In December 2023, Verizon reported that it had implemented location-based routing for wireless 911 voice calls to 414 PSAPs with an additional 277 PSAPs in progress.
                    </P>
                    <FTNT>
                        <P>
                            <SU>30</SU>
                             AT&amp;T PN Comments at 4; AT&amp;T NPRM Comments at 1. AT&amp;T notes that a few PSAPs are using unique internal routing solutions and that the company is working to ensure that its implementation of location-based routing meets the needs of these PSAPs. AT&amp;T PN Comments at 4 n.3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>31</SU>
                             Letter from Eric Hagerson, Government Affairs Director, Public Safety and Security, T-Mobile, to Marlene H. Dortch, Secretary, FCC, PS Docket No. 18-64 at 1 (filed Dec. 21, 2023) (T-Mobile Dec. 21, 2023 
                            <E T="03">Ex Parte</E>
                            ). T-Mobile reports that it only deploys location-based routing in response to a PSAP's request. 
                            <E T="03">See, e.g.,</E>
                             T-Mobile Public Notice Comments at 1, 4-7 (rec. July 11, 2022) (T-Mobile PN Comments); T-Mobile PN Reply at 2-4. For context, the latest NENA data indicate that 5,748 PSAPs operate in the United States. NENA, 
                            <E T="03">9-1-1 Statistics, https://www.nena.org/page/911Statistics</E>
                             (last visited Jan. 17, 2024).
                        </P>
                    </FTNT>
                    <P>
                        16. For wireless 911 voice calls, AT&amp;T, T-Mobile, and Verizon have, to date, implemented their own different thresholds to determine whether device location information arriving with the call is sufficiently precise for routing. According to Intrado, AT&amp;T's location-based routing solution uses a threshold with a radius of 165 meters and 90% confidence, which has enabled AT&amp;T to use location-based routing for over 80% of all wireless 911 voice calls on its network. T-Mobile reports that it has implemented “a location estimate uncertainty threshold for LBR currently set to 300 meters with a confidence level of 90%,” and reports that more than 95% of location estimates available at call routing fall within these metrics.
                        <SU>32</SU>
                        <FTREF/>
                         Verizon reports that it uses “an accuracy threshold of 200 meters maximum horizontal uncertainty with confidence of 90 percent.” AT&amp;T, T-Mobile, and Verizon state that they default to legacy E911 routing when device location information arriving with the call exceeds the radius of the providers' respective thresholds.
                    </P>
                    <FTNT>
                        <P>
                            <SU>32</SU>
                             Letter from Kristine Laudadio Devine, Counsel to T-Mobile USA, Inc., HWG LLP, to Marlene H. Dortch, Secretary, FCC, P.S. Docket Nos. 18-64, 21-479, at 1 (filed July 26, 2023) (T-Mobile July 26, 2023 
                            <E T="03">Ex Parte</E>
                            ). For purposes of this document, we assume that when commenters specify an uncertainty measurement for an implementation of location-based routing, that they are referring to the radius in meters from the reported position at the same confidence level. This assumption is consistent with prior Commission discussion of confidence and uncertainty data in the 
                            <E T="03">Wireless Location Accuracy</E>
                             proceeding, 
                            <E T="03">i.e.,</E>
                             that the uncertainty statistical estimate is expressed as a radius in meters around the reported position, and the confidence level is expressed as a percentage, indicating the statistical probability that the caller is within the area defined by the uncertainty. 
                            <E T="03">See, e.g., Wireless E911 Location Accuracy Requirements,</E>
                             Fourth Report and Order, PS Docket No. 07-114, 30 FCC Rcd 1259, 1326-27, para. 182 n.458 (2015), 80 FR 11806 (March 4, 2015).
                        </P>
                    </FTNT>
                    <P>
                        17. Text Messaging Platforms. Since 2014, all CMRS providers and covered text providers have been required to support delivery of 911 texts to PSAPs that are capable of receiving them. While availability of text-to-911 has increased significantly as more PSAPs become text-capable, the number of 911 texts sent by the public is far smaller than the number of wireless 911 voice calls.
                        <SU>33</SU>
                        <FTREF/>
                         The Commission's text-to-911 rules are technology neutral and apply to both SMS and RTT.
                    </P>
                    <FTNT>
                        <P>
                            <SU>33</SU>
                             In the Commission's 2023 annual 911 fee report, respondents reported receiving a combined total of 824,609 texts to 911 in comparison to 157,999,298 wireless 911 voice calls reported by respondents in calendar year 2022. Fifteenth Annual 911 Fee Report at 13-16, Table 3.
                        </P>
                    </FTNT>
                    <P>
                        18. SMS is the predominant mobile wireless messaging technology in use for 911 texts today. SMS is not an IP-native format, though IP-enabled networks can deliver SMS traffic. All three nationwide CMRS providers report that they are using location-based routing for at least some SMS texts to 911, but this implementation appears to be distinct from and less extensive than the implementation of location-based routing for 911 voice calls. According to Verizon, “SMS still uses call path, routing and device processing methods that are distinct from VoLTE and RTT calls, with architecture configurations that still resembles second- and third-generation networks in some respects.” AT&amp;T reports that it provides device-based hybrid location for “the majority of text messages” but does not provide specifics.
                        <SU>34</SU>
                        <FTREF/>
                         T-Mobile reports that it is using location-based routing for at least some text-to-911 messages.
                        <SU>35</SU>
                        <FTREF/>
                         Verizon indicates that it “has worked with its wireless 911 vendor Comtech to incorporate LBR in Comtech's centralized text control center (TCC) in a manner that supports LBR for 911 text messages nationwide.” 
                        <SU>36</SU>
                        <FTREF/>
                         Moreover, while the nationwide providers appear to be capable of using location-based routing for some SMS texts, NENA and other commenters indicate that standards have not been developed for location-based routing of SMS and that further work on standards is needed.
                    </P>
                    <FTNT>
                        <P>
                            <SU>34</SU>
                             AT&amp;T PN Comments at 5. AT&amp;T explains that “[w]hen the SMS message arrives at the TCC, [the TCC] queries [AT&amp;T's] wireless network for commercial location estimates to deliver the text message to the appropriate PSAP.” 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>35</SU>
                             T-Mobile July 26, 2023 
                            <E T="03">Ex Parte</E>
                             at 3. T-Mobile explains that texts to 911 are routed from T-Mobile's network to its TCC vendor and, “whenever possible,” T-Mobile includes device-based hybrid location information with those texts. 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>36</SU>
                             Verizon Dec. 7, 2023 
                            <E T="03">Ex Parte</E>
                             at 1. Verizon states that its location-based routing implementation will support location-based routing for RTT. Verizon NPRM Comments at 5.
                        </P>
                    </FTNT>
                    <P>
                        19. RTT, unlike SMS, is a native IP technology, in which each text character appears on the receiving device at roughly the same time it is typed on the sending device, allowing for a conversational flow of communication. RTT also allows text characters to be sent simultaneously with voice, which allows the PSAP to both see the typed message and hear background noises and potentially the voice of the caller. The Commission's rules require that CMRS providers choosing to implement RTT to and from any PSAP served by their network in lieu of text telephone (TTY) technology must do so in a manner that fully complies with all applicable 911 rules.
                        <SU>37</SU>
                        <FTREF/>
                         The Commission also requires CMRS providers who choose to support RTT to make RTT backward-compatible with TTY devices. This enables PSAPs without end-to-end RTT capability to use their existing TTY 
                        <PRTPAGE P="18493"/>
                        terminals to handle RTT 911 communications.
                        <SU>38</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>37</SU>
                             
                            <E T="03">RTT Order,</E>
                             31 FCC Rcd at 13591-92, para. 43. This includes the requirement to deliver RTT communications within six months to PSAPs that submit a valid request. 
                            <E T="03">Id.</E>
                             at 13592-93, para. 45 &amp; n.181.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>38</SU>
                             
                            <E T="03">RTT Order,</E>
                             31 FCC Rcd at 13590, para. 39. Currently, RTT communications to 911 that are received at many PSAPs are converted to TTY. Letter from AnnMarie Killian, Chief Executive Officer, TDIforAccess, Inc., and Mark Seeger, Policy Coordinator, TDIforAccess, Inc., to Marlene H. Dortch, Secretary, FCC, PS Docket No. 18-64, at 2 (filed Aug. 31, 2023).
                        </P>
                    </FTNT>
                    <P>
                        20. While SMS is used more frequently than RTT for messaging to 911, CMRS providers are beginning to partner with some PSAPs to implement end-to-end RTT capabilities. T-Mobile reports that it is currently operating NG911 RTT technology at a PSAP in Hood County, Texas. Verizon indicates that it now supports RTT for 911 in Livingston Parish, Louisiana, and Logan County, West Virginia. The record does not indicate the degree to which CMRS providers have implemented location-based routing for RTT communications to 911, but the providers and other industry commenters state that location-based routing for RTT communications to 911 is feasible.
                        <SU>39</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>39</SU>
                             Verizon NPRM Comments at 5 (“Verizon's planned LBR implementation for VoLTE will support real-time-text (RTT) 911 calls.”); 
                            <E T="03">see also</E>
                             ATIS NPRM Comments at 3 (urging the Commission “to clarify that only providers of such next generation text solutions [as defined in ATIS and NENA standards] are required to use LBR”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">A. Location-Based Routing</HD>
                    <HD SOURCE="HD3">1. Wireless 911 Voice Calls</HD>
                    <P>
                        21. We adopt requirements for nationwide and non-nationwide CMRS providers to implement location-based routing as proposed in the notice of proposed rulemaking for voice calls, with certain modifications. Specifically, we require all CMRS providers to (1) deploy technology that supports location-based routing on their IP-based networks (
                        <E T="03">i.e.,</E>
                         4G LTE, 5G, and subsequent generations of IP-based networks), and (2) use location-based routing to route all wireless 911 voice calls originating on their IP-based networks when location information meets certain requirements for accuracy and timeliness. We note that nothing in this decision, including the definition of “location-based routing” and other rules we adopt, authorizes the use of any non-U.S. satellite system in conjunction with the 911 system. CMRS providers seeking to employ foreign satellite navigation systems for 911 should follow the existing approval process.
                    </P>
                    <P>22. We require nationwide CMRS providers to comply with these location-based routing requirements for voice calls within six months after the effective date of the final rules. We require non-nationwide CMRS providers to comply with these location-based routing requirements for voice calls within 24 months after the effective date of the final rules in recognition of resource constraints faced by these providers. As discussed below, we adopt these requirements in light of record support that location-based routing for wireless 911 voice calls promotes public safety, is technologically feasible at reasonable cost for both nationwide and non-nationwide CMRS providers, and has been deployed by the three nationwide CMRS providers. We find that these requirements are necessary to extend the demonstrated, life-saving benefits of location-based routing to all wireless 911 callers nationwide.</P>
                    <HD SOURCE="HD3">a. Nationwide and Network-Wide Implementation</HD>
                    <P>23. We require all CMRS providers to deploy location-based routing technologies for voice calls across their IP-based networks. In the notice of proposed rulemaking, the Commission sought comment on whether CMRS providers should be required to use location-based routing to deliver 911 calls to all PSAPs served by their networks, or whether the requirement should be triggered by PSAP request or limited to certain categories of PSAPs. We find that requiring CMRS providers to implement this technology across their IP network areas is necessary to ensure that wireless 911 callers receive the demonstrated benefits of improved routing, regardless of the caller's geographic location or CMRS provider.</P>
                    <P>
                        24. We find that nationwide implementation of location-based routing will reduce 911 call transfers and improve wireless 911 service. As wireless 911 voice calls account for the vast majority of communications to 911, we consider it to be particularly important that these calls are routed to the appropriate PSAP.
                        <SU>40</SU>
                        <FTREF/>
                         CMRS providers' voluntary deployments of location-based routing have resulted in important and evident improvements to 911 wireless voice call routing. The record indicates that ongoing deployments of location-based routing have significantly reduced the occurrence of transferred wireless 911 voice calls.
                        <SU>41</SU>
                        <FTREF/>
                         AT&amp;T estimates that, as a result of its nationwide implementation, 10% of all wireless 911 voice calls on its network received a more optimal route and therefore did not need to be transferred. The National Association of State 911 Administrators (NASNA) states that uniform implementation of location-based routing has the potential to route 911 calls to the right PSAP faster than traditional cell sector-based routing in many cases and, in an emergency, “seconds can mean the difference between life and death.” Public safety commenters emphasize, and we agree, that increasing the implementation of location-based routing will reduce delays and save lives.
                        <SU>42</SU>
                        <FTREF/>
                         We find that it is in the public interest that the benefits of location-based routing should extend to all wireless 911 callers, regardless of the CMRS provider or jurisdiction from which the call is made.
                    </P>
                    <FTNT>
                        <P>
                            <SU>40</SU>
                             In the Commission's 2023 annual 911 fee report, respondents reported receiving a combined total of 157,999,298 wireless 911 voice calls in calendar year 2022 out of a total call volume of 217,654,456 from wireless wireline, VoIP, and other providers. Fifteenth Annual 911 Fee Report at 13-16, Table 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>41</SU>
                             AT&amp;T NPRM Comments at 2; Texas 9-1-1 Entities Public Notice Comments at 2-4 (rec. July 11, 2022) (Texas 9-1-1 Entities PN Comments) (showing that average percentage of 911 call transfers for two out of three PSAPs in initial beta sites decreased by roughly 4-5% after T-Mobile implemented location-based routing; the remaining PSAP showed a slight increase in transfers of less than 1%); T-Mobile, 
                            <E T="03">T-Mobile First to Roll Out Cutting-Edge 911 Capabilities</E>
                             (Dec. 17, 2020), 
                            <E T="03">https://www.tmobile.com/news/network/tmobile-next-generation-911-location-based-routing</E>
                             (announcing that some areas where T-Mobile implemented location-based routing have experienced up to 40% fewer call transfers).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>42</SU>
                             BRETSA NPRM Comments at 9 (“By eliminating delay in delivery of a 9-1-1 call to the correct PSAP, LBR can improve outcomes.”); BRETSA NPRM Reply at 4 (“LBR reduces delay in processing and dispatching 9-1-1 calls even where 9-1-1 [m]isroutes do not occur.”); Industry Council for Emergency Response Technologies, Inc. (iCERT) NPRM Comments at 2 (“The improved location and routing methodology made available with LBR will reduce the potential for 911 voice calls and texts to be directed to Public Safety Answering Points (PSAPs) that are not the ones best able to provide timely and effective response. As a result, the use of LBR technologies should eliminate the delays associated with 911 call transfers, improve emergency response times, and save lives.”); Intrado NPRM Comments at 2 (“Requiring LBR for all CMRS and text providers will ensure the availability of this life saving location technology for all 911 callers while increasing the efficiency of Public Safety Answering Points (PSAPs) by eliminating the time and effort to execute call transfers.”); Defense Information Systems Agency (DISA) NPRM Comments at 2 (“The vast majority of 911 calls from wireless devices destined for DoD PSAPs are currently being misrouted. DoD bases would immediately benefit from the reduction in call delivery time has a direct and immediate impact on emergency incident response.”); APCO NPRM Comments at 1 (noting that location-based routing has saved valuable time for PSAPs and callers). In addition, AT&amp;T notes that Kurt Mills, the Executive Director of Snohomish County (Washington) 911, has described location-based routing as a “game changer” that caused the County to experience a “significant decrease in 9-1-1 transfers.” AT&amp;T NPRM Comments at 1-2.
                        </P>
                    </FTNT>
                    <P>
                        25. Further, the public safety community strongly supports requiring CMRS providers to deploy location-based routing on a nationwide basis. Several public safety organizations urge the Commission to require CMRS providers to implement location-based 
                        <PRTPAGE P="18494"/>
                        routing. Other public safety commenters and Intrado also support a nationwide location-based routing requirement.
                        <SU>43</SU>
                        <FTREF/>
                         The record indicates that the nationwide CMRS providers have implemented location-based routing without increased costs or problems for public safety.
                        <SU>44</SU>
                        <FTREF/>
                         In particular, no commenter indicates that AT&amp;T's nationwide implementation of location-based routing, completed to “virtually all” PSAPs in June 2022, has caused additional cost or other problems for public safety.
                        <SU>45</SU>
                        <FTREF/>
                         Given the success of nationwide CMRS providers in voluntarily implementing location-based routing on their IP-based networks, and in particular the success of AT&amp;T's nationwide implementation, we agree with Boulder Regional Emergency Telephone Service Authority (BRETSA), which states that requiring wireless service providers to implement location-based routing at the earliest possible moment is “a no-brainer.” 
                        <SU>46</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>43</SU>
                             
                            <E T="03">See, e.g.,</E>
                             APCO NPRM Comments at 2 (stating that “location-based routing should be required of wireless carriers nationwide”); DISA NPRM Comments at 2 (“CMRS providers should use LBR to deliver 911 calls to 
                            <E T="03">all</E>
                             PSAPs served by their networks.” (emphasis in original)); Adams County et al. NPRM Comments at 2 (“The Commission should require location-based routing on a nationwide basis.”); Loudoun County NPRM Comments at 3 (“Loudoun strongly supports the proposed rules requiring wireless carriers and covered text providers to implement all available technology options for location-based routing of 911 calls and texts nationwide using the device-based location.”); BRETSA NPRM Comments at 10 (“There is no question but that the Commission should require all CMRS providers to implement LBR for wireless voice calls and text messages as soon as possible.”); Intrado NPRM Comments at 1 (“Intrado strongly supports the Commission's proposed requirement for nationwide implementation of location-based routing (LBR) of wireless 911 calls and texts.”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>44</SU>
                             Adams County et al. NPRM Comments at 2 (stating that the commenting entities “have not experienced increased costs, adverse impacts, or significant issues with the implementation of location-based routing”); Colorado Council of Authorities (CCOA) NPRM Reply at 3 (stating that “deployments [of LBR for at least six Colorado 911 authorities] were successful and without significant issue or additional expense”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>45</SU>
                             We note that AT&amp;T indicated in July of last year that it had “very few exceptions” to its nationwide rollout, and indicated that “a few PSAPs are using unique applications of Emergency Services Numbers to implement internal routing solutions. . . and that [the company was] working with these PSAPs to ensure [its] location-based routing solution meets their unique needs.” AT&amp;T PN Comments at 4, n.3. T-Mobile also notes that it is aware of “at least one instance” in which “an emergency calling authority requested that another 911 vendor indefinitely suspend using LBR for 911 calls to its PSAPs because the vendor's LBR implementation resulted in a greater number of 911 calls that required transfer to another PSAP.” T-Mobile NPRM Comments at 5. T-Mobile did not provide additional details on this occurrence, including when it occurred or whether or not the issue was resolved.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>46</SU>
                             BRETSA NPRM Comments at 3 (internal quotations omitted). Joseph Lyons, Dispatch Supervisor for the City of Poughkeepsie 911 Communications Center, also states that location-based routing is a “no brainer.” Joseph Lyons NPRM Comments at 1.
                        </P>
                    </FTNT>
                    <P>
                        26. We also find that requiring location-based routing to all PSAPs nationwide supports the Commission's goal to promote parity of wireless 911 service across jurisdictions. NASNA states, and we agree, that “[a]ttempting to create areas of exclusive enhanced location accuracy fosters deployment of disparate levels of service; all those who call or text 911 should benefit from LBR.” NENA points out, and we agree, that “[i]t would be inequitable to restrict the life-saving benefits of location-based routing only to residents of and visitors to the United States with the good fortune of having an emergency in a convenient location.” Commenters also urge the Commission not to limit deployment of this technology to jurisdictions subject to frequent misroutes or to jurisdictions that have deployed NG911 capabilities. Intrado comments that even in low misroute areas, the implementation of location-based routing will result in a significant reduction in misroutes compared to relying exclusively on tower-based routing.
                        <SU>47</SU>
                        <FTREF/>
                         Public safety commenters also note that implementation of location-based routing on a nationwide basis will provide technological consistency for PSAPs, which will help them provide better service, and that technological consistency between CMRS providers is important for managing the expectations of 911 callers.
                        <SU>48</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>47</SU>
                             Intrado NPRM Comments at 3, n.6. 
                            <E T="03">See also</E>
                             Colorado Public Utilities Commission (COPUC) NPRM Comments at 5-6 (“The implementation of location-based routing on all cell tower sectors is the best way to ensure that instances of misrouted calls are minimized to the greatest extent possible.”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>48</SU>
                             Michigan State 911 NPRM Comments at 1 (“[H]aving some [CMRS providers] provide LBR while others do not, creates an expectation for callers that all wireless calls provide this information to 911 centers, and that 911 centers will be able to locate them when they are experiencing an emergency.”).
                        </P>
                    </FTNT>
                    <P>
                        27. Wireless industry commenters oppose a mandatory nationwide approach,
                        <SU>49</SU>
                        <FTREF/>
                         arguing instead that CMRS providers should implement location-based routing voluntarily or only in response to individual PSAP requests.
                        <SU>50</SU>
                        <FTREF/>
                         These commenters argue that CMRS providers should only be required to use location-based routing for 911 calls to a particular PSAP after receiving a valid request from that PSAP. In addition, they argue that for a PSAP request to be deemed valid, the PSAP should be required to demonstrate that it is “technically ready” 
                        <SU>51</SU>
                        <FTREF/>
                         to receive calls routed using location-based routing and to provide shapefiles of PSAP boundaries to CMRS providers.
                        <SU>52</SU>
                        <FTREF/>
                         As explained below, we find that the concerns of industry commenters are unsupported in the record, contradict the stated preferences of public safety for a nationwide approach to deployment, and would unnecessarily delay the benefits of location-based routing to the public.
                    </P>
                    <FTNT>
                        <P>
                            <SU>49</SU>
                             
                            <E T="03">See, e.g.,</E>
                             T-Mobile NPRM Comments at 3 (“T-Mobile cautions the Commission from adopting rules that require wireless carriers to do nothing more than turn on location-based routing regardless of PSAP preference.”); Verizon NPRM Comments at 2 (“[I]nstead of a blanket flash-cut nationwide implementation deadline, implementation should be based on PSAP requests. . . .”); CTIA NPRM Comments at 4 (“[A]ny obligation for a provider to commence use of LBR to route wireless 9-1-1 voice calls to a PSAP should only be triggered by a `valid request' from a state or local 9-1-1 authority.”). One public safety commenter, the Colorado Council of Authorities (CCOA), also “gives deference to the comments of T-Mobile, Verizon, and CTIA that deployment of LBR for wireless 911 voice calls should be initiated by a valid request from a PSAP or governing 911 authority.” CCOA NPRM Reply at 1 (footnote omitted).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>50</SU>
                             Verizon NPRM Comments at 2; T-Mobile NPRM Comments at 3; iCert NPRM Comments at 2; RWA NPRM Comments at 4; Southern Linc NPRM Reply at 4; 
                            <E T="03">see also</E>
                             AT&amp;T NPRM Comments at 3 (arguing for either a per-PSAP approach or “a process under which a PSAP could signal that it requires more time to achieve readiness, and that PSAP would be carved out from the six-month requirement.”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>51</SU>
                             CTIA NPRM Comments at 4 (stating that “[t]o make a valid request, a PSAP should be technically ready to receive 9-1-1 calls routed using LBR”); CCA Notice of Proposed Rulemaking Reply at 6 (rec. Mar. 20, 2023) (CCA NPRM Reply); RWA NPRM Comments at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>52</SU>
                             T-Mobile NPRM Comments at 7 (stating that a valid request must be conditioned on “the provision of accurate shapefiles—and the maintenance and update of those shapefiles”).
                        </P>
                    </FTNT>
                    <P>
                        28. Per-PSAP Implementation. We decline to adopt a per-PSAP deployment approach. Contrary to the assertion of industry commenters, the record does not demonstrate that individual PSAPs must take specific technical steps in order to be ready to receive wireless 911 calls routed using location-based routing. The generation of location-based routing information as contemplated in this proceeding occurs entirely within CMRS provider networks prior to call delivery to the PSAP,
                        <SU>53</SU>
                        <FTREF/>
                         and therefore there are no specific actions that PSAPs need to take to be technically ready to receive wireless 911 calls routed by device-based rather than tower-based location. As the Colorado Public Utilities Commission (COPUC) states, “Because LBR is performed before the call is even delivered to the 9-1-1 system service provider for delivery to the PSAP, there 
                        <PRTPAGE P="18495"/>
                        is no additional preparation that must be made by the PSAP in order for carrier-provided LBR to be of benefit.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>53</SU>
                             As Intrado notes, CMRS providers must implement a geospatial routing-capable Gateway Mobile Location Center (GMLC) in order to enable their networks to support location-based routing. Intrado NPRM Comments at 3.
                        </P>
                    </FTNT>
                    <P>
                        29. AT&amp;T's completed rollout of location-based routing on its nationwide network provides additional evidence that location-based routing can be successfully deployed without requiring PSAPs to demonstrate technical readiness. AT&amp;T deployed location-based routing in 2022 on a region-by-region basis and completed its nationwide rollout in less than six months.
                        <SU>54</SU>
                        <FTREF/>
                         Moreover, although AT&amp;T supports the Commission adopting a per-PSAP approach in which each PSAP would have to request location-based routing, it is notable that AT&amp;T did not use this approach in its own rollout. Instead, AT&amp;T deployed location-based routing to “virtually all PSAPs” in the U.S. without soliciting PSAP-by-PSAP requests or requiring each PSAP to demonstrate technical readiness. Thus, it does not appear that these are necessary prerequisite steps before CMRS providers implement location-based routing nationwide on their networks.
                    </P>
                    <FTNT>
                        <P>
                            <SU>54</SU>
                             AT&amp;T Comments at 3. In a news release announcing AT&amp;T's rollout of location-based routing, AT&amp;T stated “The nationwide rollout has started and is available in Alaska, Colorado, Hawaii, Idaho, Montana, Oregon, Washington, Wyoming, Kansas, Illinois, Iowa, Minnesota, North Dakota, Missouri, Nebraska, South Dakota and Guam. Additional regions will be rolled out over the next several weeks. The nationwide rollout is scheduled to be completed by the end of June.” Press Release, AT&amp;T, AT&amp;T Launches First-Ever Nationwide Location-Based Routing with Intrado to Improve Public Safety Response for Wireless 9-1-1 Calls (May 10, 2022), at 
                            <E T="03">https://about.att.com/story/2022/nationwide-location-based-routing.html.</E>
                        </P>
                    </FTNT>
                    <P>
                        30. We also do not agree with commenters' assertions that PSAPs are not ready from an operational perspective to manage changes in call distribution or volume resulting from the implementation of location-based routing on a nationwide basis. T-Mobile asserts that “[m]any emergency authorities want to understand the impact LBR will have on operations, call volume, and workflows before deploying it; they often also want the ability to implement reporting and tracking of call transfers prior to enabling LBR in order to understand and see the effects of the new 911 routing.” 
                        <SU>55</SU>
                        <FTREF/>
                         T-Mobile cites its initial implementation of location-based-routing in Minnesota and Texas,
                        <SU>56</SU>
                        <FTREF/>
                         where T-Mobile states that 911 authorities required First Office Applications (FOAs) before expanding deployment to more PSAPs. However, T-Mobile's initial deployments in those areas occurred at a time when no other carrier had deployed location-based routing for 911 anywhere in the U.S., which could reasonably lead the first PSAPs receiving location-based routed calls to take a cautious approach. Since then, AT&amp;T has implemented location-based routing nationwide to thousands of PSAPs with no reported adverse operational impacts. To the contrary, the record indicates that PSAPs have reaped operational benefits from implementation of location-based routing in the form of reduced misroutes and call transfers.
                    </P>
                    <FTNT>
                        <P>
                            <SU>55</SU>
                             T-Mobile NPRM Comments at 5 (emphasis omitted).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>56</SU>
                             
                            <E T="03">See</E>
                             Metropolitan Emergency Services Board, Metropolitan Emergency Services Board 9-1-1 Technical Operations Committee July 15, 2021 Draft Meeting Minutes at 7, 
                            <E T="03">https://mn-mesb.org/wp-content/uploads/July-TOC-Meeting-Packet-070921.pdf</E>
                             (indicating that at the time of deployment in select counties in Minnesota, no other carriers had deployed or announced future deployment of location-based routing); Metropolitan Emergency Services Board, Metropolitan Emergency Services Board 9-1-1 Technical Operations Committee Agenda at 25 (Jan. 21, 2021), 
                            <E T="03">https://mn-mesb.org/wp-content/uploads/January-Meeting-911-TOC-Packet-012121.pdf</E>
                             (including a presentation from T-Mobile to Greater Harris County, Texas, indicating that “[t]oday, T-Mobile is the only wireless carrier positioned to route 911 calls based on caller location, rather that [sic] cell sector”).
                        </P>
                    </FTNT>
                    <P>
                        31. CMRS providers' assertions about potential adverse operational impacts to PSAPs are also contradicted by virtually all statements of public safety commenters on the record. Despite industry commenters' preference,
                        <SU>57</SU>
                        <FTREF/>
                         the vast majority of public safety commenters support a rapid nationwide rollout of location-based routing and specifically oppose the per-PSAP approach advocated by CMRS providers. Only one public safety commenter, the Colorado Council of Authorities, Inc. (CCOA), supports the per-PSAP approach in order to ensure “collaboration” between PSAPs and service providers. We agree that such collaboration is important to the successful implementation of location-based routing, and we encourage PSAPs and 911 authorities to collaborate during the implementation period established. However, this does not require establishing a process in which every PSAP must affirmatively opt in to location-based routing. In fact, such a process would be far more cumbersome than a uniform nationwide implementation timetable and could lead to fragmented and inconsistent deployment. We agree with APCO that given the immediate feasibility of nationwide implementation, substantial voluntary deployment that has already occurred, and the clear public safety benefits of location-based routing, deployment and use of location-based routing should not be optional or conditional.
                    </P>
                    <FTNT>
                        <P>
                            <SU>57</SU>
                             T-Mobile NPRM Comments at 5; 
                            <E T="03">see also</E>
                             iCERT NPRM Comments at 2 (arguing for a per-PSAP approach as location-based routing “may impact a PSAP's operations”).
                        </P>
                    </FTNT>
                    <P>
                        32. We are also not persuaded by commenters who compare implementation of location-based routing to past implementation of the Commission's E911 Phase I and Phase II location requirements 
                        <SU>58</SU>
                        <FTREF/>
                         or text-to-911,
                        <SU>59</SU>
                        <FTREF/>
                         which were predicated on individual PSAPs achieving the technical capability to receive E911 location data and 911 texts, respectively.
                        <SU>60</SU>
                        <FTREF/>
                         For location-based routing, there is no similar reason to predicate CMRS provider compliance on PSAP technical capability, because AT&amp;T's rollout demonstrates that PSAPs do not need to have any specific technical capabilities in place to receive calls routed using location-based routing. Accordingly, we agree with COPUC that “[t]here is no compelling reason to require PSAPs to opt in to this service or to predicate the use of location-based routing methodology on any sort of `readiness' of the PSAP.” Implementing location-based routing on a per-PSAP basis could lead to uneven and inconsistent implementation of routing approaches between jurisdictions and result in a risk of wireless 911 misroutes for jurisdictions that do not request location-based routing service. We find that this would be contrary to the public interest and the Commission's interest in facilitating improved routing of wireless 911 voice calls.
                    </P>
                    <FTNT>
                        <P>
                            <SU>58</SU>
                             T-Mobile NPRM Comments at 4; CCOA NPRM Reply Comments at 1-2; 
                            <E T="03">see also</E>
                             47 CFR 9.10(d)(1), (f), (g), (m).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>59</SU>
                             T-Mobile NPRM Comments at 4; CTIA NPRM Comments at 4; 
                            <E T="03">see also</E>
                             47 CFR 9.10(q)(10)(ii) and (iii).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>60</SU>
                             To receive texts, PSAPs must either upgrade their equipment to receive text messages or implement text-to-911 capabilities on existing equipment. 
                            <E T="03">T911 Second Report and Order,</E>
                             29 FCC Rcd at 9861, para. 32, 79 FR 55367 (September 16, 2014). To receive Phase I location information, PSAPs must use switches, protocols, and signaling systems that will allow them to obtain the calling party's number from the transmission of ANI. 
                            <E T="03">Revision of the Commission's Rules to Ensure Compatibility with Enhanced 911 Emergency Calling Systems,</E>
                             CC Docket No. 94-102, RM-8143, Report and Order, 11 FCC Rcd 18676, 18709, para. 63 n.119 (1996), 61 FR 40348 (August 2, 1996). To receive Phase II location information, PSAPs must “install equipment to determine the geographic coordinates of the caller, transfer that information through the telephone networks, and have a mapping system in place at the PSAP that can display the latitude and longitude coordinates of the caller as a map location for dispatching assistance.” General Accounting Office, Uneven Implementation of Wireless Enhanced 911 Raises Prospect of Piecemeal Availability for Years to Come, GAO-04-55, at 9 (Nov. 2003), 
                            <E T="03">https://www.gao.gov/assets/gao-04-55.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        33. Voluntary Implementation. We also decline to permit CMRS providers to deploy location-based routing on a 
                        <PRTPAGE P="18496"/>
                        purely voluntary basis. Wireless entities supporting voluntary implementation argue that flexibility in implementation is needed to account for differences in providers' networks and devices and to allow technologies to continue to evolve.
                        <SU>61</SU>
                        <FTREF/>
                         However, public safety commenters note that permitting CMRS providers to deploy location-based routing on a purely voluntary basis would require additional and unnecessary coordination and would only delay the implementation of location-based routing as a general matter. The record confirms the Commission's reasoning in the notice of proposed rulemaking that relying on voluntary implementation would “result in inconsistent routing of calls to PSAPs and a higher risk of 911 misroutes for subscribers on CMRS networks that did not support location-based routing.” Thus, we find that allowing CMRS providers to implement location-based routing on a voluntary basis would undermine our goal of ensuring that this important capability benefits all wireless 911 callers nationwide.
                    </P>
                    <FTNT>
                        <P>
                            <SU>61</SU>
                             CTIA NPRM Reply at 3 (urging the Commission to provide flexibility for wireless providers to implement location-based routing in the manner that meets their “unique network and handset configurations” and is coordinated with public safety); 
                            <E T="03">see also</E>
                             CCA NPRM Reply at 1-2.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Technical Considerations</HD>
                    <P>34. Technological Feasibility. We find that implementing location-based routing for wireless 911 voice calls is technologically feasible for nationwide and non-nationwide CMRS providers. The three nationwide CMRS providers have implemented location-based routing for wireless 911 voice calls across or for some part of their networks. CCA, an industry association with membership including non-nationwide CMRS providers, states that “wireless carriers can eventually deploy location-based routing to any PSAP” if provided with adequate time and financial support. iCERT agrees that location-based routing is technologically feasible. NGA 911 also offers support for this conclusion, stating that both Google's Emergency Location Service (ELS) and Apple's Hybridized Emergency Location (HELO) provide a device location estimate, and these mobile operating systems comprise 99.62% of the handset market. NENA states that AT&amp;T's nationwide deployment of location-based routing demonstrates that “transitional location-based routing mechanisms are technically feasible and improve 9-1-1 outcomes, and are in use today.” No commenter argues that implementing location-based routing on CMRS provider networks is technologically infeasible.</P>
                    <P>
                        35. Calls originating on IP-based networks. In light of the technical obstacles and ongoing retirement of legacy networks, we apply our location-based routing requirements to IP-based networks but we decline to require location-based routing for 911 calls originating on circuit-switched, time-division multiplex (TDM) networks. This is consistent with the Commission's proposal in the notice of proposed rulemaking and is supported by commenters. For example, the Rural Wireless Association (RWA) agrees that requiring location-based routing for 911 calls originating on TDM networks would be unduly burdensome. CCA asserts that “TDM networks can lack the speed and capacity necessary to transmit and evaluate confidence and uncertainty information and query the location server for PSAP routing instructions prior to the time for a call to commence.” ATIS assumes for purposes of 
                        <E T="03">ATIS-0700042</E>
                         that location-based routing is only supported on originating networks supporting Long Term Evolution (LTE) and beyond.
                        <SU>62</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>62</SU>
                             
                            <E T="03">ATIS-0700042</E>
                             at 6. CCA argues that limiting location-based routing to IP-based wireless networks provides “an important increment of regulatory relief” but notes that this relief is limited because many non-nationwide carriers have already retired non IP-based technology. CCA NPRM Comments at 12. CCA also asserts that limiting location-based routing to IP networks does not reduce costs burdens on the wireless sector. 
                            <E T="03">Id.</E>
                             at 12-13. Nonetheless, we find that this provision will ease burdens for CMRS providers that have not yet transitioned to IP-based networks.
                        </P>
                    </FTNT>
                    <P>
                        36. PSAP Boundary Maps. Some commenters contend that location-based routing requirements should be conditioned on 911 authorities providing updated maps or shapefiles of PSAP boundaries to CMRS providers. We conclude that such a condition is unnecessary. We recognize that accurately mapping PSAP jurisdictional boundaries is important to the accurate routing of 911 calls. However, the record demonstrates that CMRS providers and the third-party vendors they use to route 911 calls already have maps and shapefile records of PSAP boundaries generated to support earlier E911 deployments and upgrades,
                        <SU>63</SU>
                        <FTREF/>
                         and that “numerous companies” maintain PSAP boundary shapefile information to support CMRS 911 call routing. CMRS providers have long used this information to support legacy tower-based routing of 911 voice calls.
                        <SU>64</SU>
                        <FTREF/>
                         Moreover, the Commission has never conditioned the 911 routing obligations of CMRS providers on PSAPs or 911 authorities providing mapping data. As NASNA explains, legacy and E911 routing “relies on tabular location databases that are updated by the originating service provider,” and 911 authorities may support the maintenance and quality assurance of these databases, but “there are no rules addressing how frequently this data must be updated, nor is there transparency when data updates are operationalized.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>63</SU>
                             
                            <E T="03">See</E>
                             Verizon July 13, 2023 
                            <E T="03">Ex Parte</E>
                             at 1 (“If Verizon has a [s]hapefile of the PSAP's boundaries due to earlier E911 deployments or upgrades, the PSAP may be able to simply confirm that the earlier document remains accurate.”); GCI Aug. 7, 2023 
                            <E T="03">Ex Parte</E>
                             at 5 (“GCI's network serves geographic areas where the boundaries between PSAP service areas are sparsely populated or unpopulated, in general. Therefore, the existing shapefiles could likely be used to route calls using more precise on-device location as well.”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>64</SU>
                             
                            <E T="03">See</E>
                             NASNA NPRM Comments at 4 (“Legacy and enhanced 911 relies on tabular location databases that are updated by the originating service providers (OSPs), and maintained by the 911 service provider to act as the authoritative source of location information used to validate the location of the 911 caller.”).
                        </P>
                    </FTNT>
                    <P>
                        37. The record indicates that CMRS providers and their vendors can use existing PSAP boundary information to support location-based routing to the same extent that such information has supported tower-based routing. The purpose of this information is to associate a specified location—whether it is the caller's location or the tower location—with the jurisdiction served by a particular PSAP, and CMRS providers are already using this information to support their implementation of location-based routing. If PSAP boundary maps are not updated to reflect current jurisdictional boundaries, it is possible that some calls originated near those boundaries could be misrouted even when location-based routing is used. However, the overall frequency of misroutes is still likely to be lower than with tower-based location because tower-based location routes all calls in a cell sector to the same PSAP regardless of the jurisdiction where the caller is located. For example, GCI states that “existing shapefiles could likely be used to route calls using more precise on-device location” information on its network, although the importance of updated maps may be affected in some locations by factors such as population density near the PSAP boundary area, the number of PSAPs served, and the density of cell sites. BRETSA comments that the record does not indicate whether the provider of the PSAP boundary maps AT&amp;T is relying on “could and would also provide them to non-national providers and on what terms.” As noted above, we conclude 
                        <PRTPAGE P="18497"/>
                        that it is not necessary for AT&amp;T's provider of PSAP boundary maps to provide them to other CMRS providers, who should be able to use their existing sources of boundary maps.
                    </P>
                    <P>38. While we do not require PSAPs to provide updated shapefiles as a prerequisite to location-based routing, we recognize that location-based routing is most effective when service providers use up-to-date shapefiles that precisely and accurately identify jurisdictional boundaries for routing purposes. In addition, we recognize that 911 authorities and PSAPs are the most authoritative source for current jurisdictional boundary information. Therefore, we encourage CMRS providers and their third-party vendors to work with 911 authorities and PSAPs to ensure that location-based routing decisions on CMRS provider networks are based on shapefiles that accurately reflect current boundaries. NENA suggests establishment of an “authoritative database for PSAP boundary information” and states that with sufficient funding and appropriate governance, this tool could be expanded to serve as the industry's authoritative reference for location-based routing purposes. We encourage 911 authorities, relevant industry groups, and CMRS providers to consider further whether such a database is needed, what steps to take, and what parties should take them.</P>
                    <P>
                        39. NG911 Geospatial Routing. NASNA and the Texas 9-1-1 Entities suggest that as jurisdictions transition to NG911, location-based routing by CMRS providers may not be necessary and could cause delay in call routing by NG911-capable jurisdictions that will use ESInets and geospatial routing to route calls to individual PSAPs.
                        <SU>65</SU>
                        <FTREF/>
                         While these parties are correct that NG911 will introduce new geospatial routing mechanisms, this does not obviate the need for the location-based routing requirements we adopt, nor will these requirements impede NG911 call routing.
                    </P>
                    <FTNT>
                        <P>
                            <SU>65</SU>
                             NASNA NPRM Comments at 11 (“By definition, LBR will introduce delay into the delivery of the 911 call or text to NG911 that is no longer needed with a fully functional NG911 system that is using geospatial routing.”); Texas 9-1-1 Entities NPRM Comments at 4 (noting that the NG911 transition in some areas “may potentially make it unnecessary for some CMRS providers to make LBR modifications to their existing legacy 9-1-1 solutions, at least in those areas”).
                        </P>
                    </FTNT>
                    <P>
                        40. First, while many states have already made significant commitments to implementing NG911, the NG911 transition remains ongoing, and there are no fully enabled NG911 systems yet operating. As COPUC notes, “most 911 call delivery networks do not have the ability to provide geospatial routing at this time and it is unknown when such technology will be universally deployed. Requiring CMRS providers to deploy LBR in the meantime is essential . . . .” 
                        <SU>66</SU>
                        <FTREF/>
                         We agree.
                    </P>
                    <FTNT>
                        <P>
                            <SU>66</SU>
                             NASNA NPRM Comments at 6 (“For localities that have deployed any form of NG911 this unrestricted access to 911 call routing data is mission critical. . . .”).
                        </P>
                    </FTNT>
                    <P>
                        41. Second, the provision of location-based routing information by CMRS providers will remain essential in the NG911 environment because NG911 systems will need this information to perform the additional geospatial routing functions necessary to direct 911 calls to the correct PSAP behind the ESInet.
                        <SU>67</SU>
                        <FTREF/>
                         APCO notes that “[w]ireless service providers perform routing functions before passing a 9-1-1 call or text to a 9-1-1 network—regardless of whether the 9-1-1 network is legacy or IP-based—and even if such networks are able to perform an additional routing function, carriers should remain responsible for first engaging in location-based routing.” BRETSA further notes that location-based routing “is not inconsistent with the eventual transition to full i3 NG9-1-1.” 
                        <SU>68</SU>
                        <FTREF/>
                         Finally, we do not agree that location-based routing implemented on CMRS networks consistent with the proposed rules will introduce delay into NG911 call routing. The location-based routing requirements we adopt expressly apply only when location information meeting the accuracy threshold is available at time of routing. Thus, these requirements will not delay delivery of 911 calls in either the legacy E911 environment or the NG911 environment.
                        <SU>69</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>67</SU>
                             
                            <E T="03">See</E>
                             Verizon NPRM Comments at 3 (stating that some jurisdictions “have implemented their own form of LBR and prefer that originating service providers not also perform LBR on a call”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>68</SU>
                             BRETSA NPRM Reply Comments at 5; 
                            <E T="03">see also</E>
                             Intrado PN Comments at 10 n.14 (“Implementing LBR on the carrier side has the added benefit of avoiding any potential adverse consequences to the present transitional NG911 environment and eventual NG911 end state. In fact, LBR (and the enhanced location information behind it) will work hand-in-hand with the PSAPs ongoing NG911 adoption of IP-based, geospatial ESInets.”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>69</SU>
                             
                            <E T="03">See</E>
                             Intrado NPRM Comments at 5 (“[T]he carrier GMLC now has sufficient information and time with 4G/5G to determine, transmit and evaluate confidence and uncertainty of device-based location information and to query the location server for PSAP routing instructions before the time to route.”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Compliance Timelines</HD>
                    <P>42. Overview. We require nationwide CMRS providers to comply with the location-based routing requirements within six months after the effective date of the final rules, as proposed in the notice of proposed rulemaking. We require non-nationwide CMRS providers to comply with the location-based routing requirements within 24 months after the effective date of the final rules, a time frame which is six months longer than the eighteen months proposed in the notice of proposed rulemaking. We also permit a PSAP and a CMRS or covered text provider to set, by mutual consent, alternative deadlines to implement location-based routing in the PSAP's jurisdiction that are different from those otherwise established by the rules.</P>
                    <P>
                        43. Nationwide CMRS Providers. We require nationwide CMRS providers to comply with the location-based routing requirements within six months after the effective date of the final rules, as proposed in the notice of proposed rulemaking. NENA, COPUC, NASNA, DISA, and iCERT support the proposed six-month timeline for nationwide CMRS providers, and no commenter indicates that it would be infeasible or burdensome for nationwide CMRS providers to complete the implementation of location-based routing within six months. The three nationwide CMRS providers have already deployed or are actively working toward deploying location-based routing capabilities on their networks, indicating that they have made substantial progress in implementing this technology at the network level.
                        <SU>70</SU>
                        <FTREF/>
                         AT&amp;T has already deployed location-based routing on a nationwide basis. Verizon has indicated that it is “turning up Location-Based Routing for hundreds of PSAPs nationwide” and directs “PSAPs that are interested in deploying Location Based Routing to contact Verizon engineers.” This statement indicates Verizon's readiness to deploy location-based routing and that Verizon has made necessary progress to implement the technology at the network level. T-Mobile was the first to deploy this technology on its network in 2020 and as of December 2023 had fully implemented location-based routing for 1,591 PSAPs with an additional 596 PSAPs in progress, which indicates that 
                        <PRTPAGE P="18498"/>
                        it has made progress on implementing the technology on a network level.
                    </P>
                    <FTNT>
                        <P>
                            <SU>70</SU>
                             AT&amp;T completed the rollout of location-based routing on its network in June 2022 and uses location-based routing to deliver wireless 911 voice calls and texts to nearly all PSAPs nationwide. AT&amp;T PN Comments at 4; AT&amp;T NPRM Comments at 1. T-Mobile launched location-based routing on its network in the states of Texas and Washington in 2020 and as of December 2023 has fully implemented location-based routing for 1,591 PSAPs with an additional 596 PSAPs in progress. T-Mobile NPRM Comments at 3-5; T-Mobile PN Reply at 2 n.6. In December 2023, Verizon reported that it had initiated location-based routing for 414 PSAPs with an additional 277 PSAPs in progress. Verizon Dec. 7, 2023 
                            <E T="03">Ex Parte</E>
                             at 1.
                        </P>
                    </FTNT>
                    <P>44. The nationwide CMRS providers do not argue for an implementation timeline that is longer than six months from the effective date of the rules. Instead, T-Mobile, AT&amp;T, Verizon, and CTIA support a six-month timeline for nationwide providers conditioned on each PSAP requesting location-based routing and demonstrating technical and operational readiness. As discussed above, we have determined that a per-PSAP request mechanism would delay the critical benefits of a nationwide deployment of location-based routing and is not a necessary component to ensure PSAP operational continuity during the transition. Industry commenters' arguments nevertheless indicate that nationwide providers are capable, from both a technical and cost perspective, of deploying location-based routing within a six month timeframe. Indeed, if the Commission were to adopt a per-PSAP request mechanism and all or virtually all PSAPs opted in immediately, the nationwide CMRS providers would effectively be required to deploy location-based routing nationwide within six months. Finally, we accord little weight to AT&amp;T's request to condition CMRS provider compliance timelines on PSAP requests, as AT&amp;T deployed location-based routing on a nationwide basis and states that it “was able to deploy location-based routing to virtually all PSAPs within a six-month timeframe,” with few exceptions.</P>
                    <P>45. Some commenters point out that the nationwide CMRS providers had several years to plan and carry out their voluntary implementation of location-based routing. However, we disagree that this argues in favor of allowing the nationwide providers more than six months to complete nationwide implementation. Location-based routing technology is no longer nascent, unknown to PSAPs, or unproven. Use of location-based routing has expanded significantly since 2020, when T-Mobile first deployed it, technical standards now exist for its implementation, all three nationwide carriers have deployed it on their networks, and public safety is aware of and eager for this improved routing technology. Given the extent of this progress, we believe that six months is more than adequate for nationwide CMRS providers to implement location-based routing nationwide. We therefore find that six months from the effective date of the rules provides adequate time for these providers to complete the implementation on their networks. NENA, COPUC, NASNA, DISA, and iCERT support the proposed six-month timeline for nationwide CMRS providers, and no commenter indicates that it would be infeasible or burdensome for nationwide CMRS providers to complete the implementation of location-based routing within six months.</P>
                    <P>46. APCO, Adams County et al., and Fenwick support a timeline shorter than six months for nationwide providers to deploy location-based routing. We decline to adopt a shorter mandatory timeline, as it is unclear whether it is feasible for all three nationwide CMRS providers to complete their deployment of location-based routing in fewer than six months. However, nationwide CMRS providers may deploy location-based routing voluntarily prior to the compliance deadline.</P>
                    <P>
                        47. Non-Nationwide CMRS Providers. In the notice of proposed rulemaking, the Commission proposed an 18-month timeline for non-nationwide CMRS providers to implement location-based routing.
                        <SU>71</SU>
                        <FTREF/>
                         We received mixed comments on this issue. NASNA, iCERT, and COPUC support the proposed 18-month timeline for non-nationwide CMRS providers,
                        <SU>72</SU>
                        <FTREF/>
                         while other public safety entities argue for a shorter timeline.
                        <SU>73</SU>
                        <FTREF/>
                         On the other hand, CMRS provider commenters generally support a longer timeline for non-nationwide CMRS providers to implement location-based routing. CTIA states that “non-nationwide providers need more time to deploy LBR capability than the 18 months proposed in the NPRM due to the significant costs and technical modifications necessary to implement LBR.” GCI recommends that non-nationwide CMRS providers be given a timeline of at least 24 months or potentially longer. RWA recommends that small rural CMRS providers be given 36 months to implement location-based routing.
                        <SU>74</SU>
                        <FTREF/>
                         CCA asserts that non-nationwide providers need at least four years to “select, test, modify, perfect, and deploy” location-based routing, stating that AT&amp;T's deployment took four years and that “[m]ost CCA member companies do not possess anywhere near the scope and scale of resources that AT&amp;T enjoys.” Southern Linc agrees with CCA's concerns that non-nationwide CMRS providers may require considerably longer than 18 months.
                    </P>
                    <FTNT>
                        <P>
                            <SU>71</SU>
                             Notice of Proposed Rulemaking, 37 FCC Rcd at 15195, para. 26.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>72</SU>
                             NASNA NPRM Comments at 11 (agreeing with 18-month timeline for non-nationwide CMRS providers); iCERT NPRM Comments at 2 (supporting 18-month timeline for non-nationwide CMRS providers); COPUC NPRM Comments at 3 (agreeing with the 18-month timeline for non-nationwide CMRS providers); 
                            <E T="03">see also</E>
                             NENA Comments at 3 (stating, as a general matter, that “the Commission has proposed sufficient compromises to avoid undue burden on the wireless industry, such as a later implementation date for non-nationwide CMRS providers”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>73</SU>
                             Adams County et al. NPRM Comments at 2 (stating that 18-month implementation schedule for non-nationwide CMRS providers is “acceptable,” but noting that “[s]ooner is better”); APCO NPRM Comments at 3. BRETSA comments that non-nationwide CMRS providers have not yet determined the actual cost and time required to implement location-based routing, and urges the Commission to require non-nationwide CMRS providers to implement location-based routing within six or twelve months (
                            <E T="03">i.e.,</E>
                             rather than eighteen months) and to “grant waivers or extensions upon showings of the actual costs of and impediments to deployment.” BRETSA NPRM Reply at ii; 
                            <E T="03">id.</E>
                             at 13 (“Such an approach would allow providers a reasonable time to implement LBR, while avoiding unnecessary delay and impacts upon victims of accidents, illnesses, crimes, and fires.”). BRETSA also suggests that in rural areas, which generally have a lower incidence of misroutes (
                            <E T="03">e.g.,</E>
                             because a single PSAP serves the entire county), regional wireless providers should have an “earlier date for implementation of LBR,” with deployment prioritized based on the level of misroutes, and “allowing a longer overall phase-in period.” BRETSA NPRM Comments at 7-8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>74</SU>
                             RWA NPRM Comments at 1-3. RWA discusses reasons smaller carriers require more time and financial support, including that “many RWA members are in the midst of efforts to `rip and replace' unsecure Huawei and ZTE equipment in their networks,” 
                            <E T="03">id.</E>
                             at 2, which is a “top priority over regulatory compliance unrelated to national security.” 
                            <E T="03">Id.</E>
                             at 3. RWA requests small rural CMRS providers have 36 months from effective date of final rules to implement, “and then only if the PSAP is capable of handling the call routing.” 
                            <E T="03">Id.</E>
                             at 3.
                        </P>
                    </FTNT>
                    <P>
                        48. The Commission has previously recognized that non-nationwide CMRS providers can face obstacles that warrant additional time for compliance beyond the time afforded to nationwide CMRS providers during technology transitions. Smaller CMRS providers may have difficulty obtaining necessary commitments from device makers, technology vendors, and software service providers to implement location-based routing within a time frame that would be feasible for nationwide CMRS providers. We therefore adopt a timeline of twenty-four months (two years) from the effective date of the rules for non-nationwide CMRS providers to deploy and begin using location-based routing. This timeline provides an additional 18 months beyond the deadline applicable to nationwide CMRS providers. We adopt this extended timeline in recognition of the obstacles that non-nationwide CMRS providers may encounter in deploying location-based routing on their networks. We also anticipate that the additional time will assist non-nationwide CMRS providers in absorbing capital costs. It is consistent with past Commission decisions to permit non-nationwide CMRS providers additional time to 
                        <PRTPAGE P="18499"/>
                        accommodate technology transitions.
                        <SU>75</SU>
                        <FTREF/>
                         Based on the progress that nationwide CMRS providers have made and that some non-nationwide CMRS providers advocate for a 24-month timeline, it is our predictive judgment that the 24 months afforded will be sufficient from both technological feasibility and cost perspectives for non-nationwide CMRS providers to implement location-based routing. If individual CMRS providers encounter unique or unusual factual circumstances that support a lengthier timeline, they may seek a waiver under the Commission's waiver rules.
                        <SU>76</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>75</SU>
                             For example, for horizontal location accuracy requirements, certain benchmarks for non-nationwide CMRS providers are tied to the deployment of specifical technical capabilities, which has permitted additional time for compliance. 
                            <E T="03">See</E>
                             47 CFR 9.10(i)(2)(i)(B)(
                            <E T="03">3</E>
                            ), (
                            <E T="03">4</E>
                            ). For vertical location accuracy requirements, certain non-nationwide CMRS providers are permitted an additional year to meet relevant benchmarks. 
                            <E T="03">See</E>
                             47 CFR 9.10(i)(2)(ii)(F).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>76</SU>
                             47 CFR 1.925.
                        </P>
                    </FTNT>
                    <P>
                        49. We decline to extend the timeline for compliance for non-nationwide CMRS providers to thirty-six months or four years, as advocated by RWA and CCA, respectively. RWA argues that small non-nationwide CMRS providers should have 36 months to comply with location-based routing requirements because they are simultaneously focusing “substantial time and attention” on replacing network equipment under the Secure and Trusted Communications Networks Reimbursement Program (Reimbursement Program), which they assert takes “top priority over regulatory compliance unrelated to national security.” We see no basis for extending the 24-month location-based routing timeline for non-nationwide CMRS providers based on their concurrent obligations under the Reimbursement Program. Protecting national security and ensuring effective 911 emergency response are both important regulatory obligations that all CMRS providers must meet. We reject the view that one takes priority over the other. In addition, RWA has failed to show how the timeline for the Reimbursement Program would conflict with non-nationwide provider implementation of location-based routing when Reimbursement Program removal, replacement, and disposal deadlines are determined on an application-specific basis 
                        <SU>77</SU>
                        <FTREF/>
                         and may be extended pursuant to the conditions set forth in the Secure and Trusted Communications Networks Act and the Commission's rules.
                        <SU>78</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>77</SU>
                             FCC, 
                            <E T="03">Secure and Trusted Communications Networks Reimbursement Program Second Report</E>
                             at 4 (July 10, 2023), 
                            <E T="03">https://docs.fcc.gov/public/attachments/DOC-395005A1.pdf. See Protecting Against National Security Threats to the Communications Supply Chain Through FCC Programs,</E>
                             WC Docket No. 18-89, Second Report and Order, 35 FCC Rcd 14284, 14354, para. 170 (2020), 86 FR 2904 (January 13, 2021). The Commission may grant recipients extensions of this term on an individual basis. 
                            <E T="03">See</E>
                             Secure and Trusted Communications Networks Act of 2019, Public Law 116-124, section 4(d)(6)(C), 134 Stat. 158, 163 (2020) (Secure Networks Act) (codified at 47 U.S.C. 1603(d)(6)(C)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>78</SU>
                             A Reimbursement Program recipient may request and the Commission may grant an individual extension of a recipient's removal, replacement, and disposal term for a period of up to six months after the Bureau finds, that due to no fault of such recipient, such recipient is unable to complete the permanent removal, replacement, and disposal by the end of the term. 47 CFR 1.50004(h)(2); 
                            <E T="03">see also</E>
                             Secure Networks Act section 4(d)(6)(C); 
                            <E T="03">see also, e.g., Protecting Against National Security Threats to the Communications Supply Chain Through FCC Programs,</E>
                             WC Docket No. 18-89, Order, DA 23-875, at 1, para. 1 (WCB Sept. 22, 2023) (granting Stealth Communications Services, LLC's request for extension from September 29, 2023 until March 29, 2024); 
                            <E T="03">Protecting Against National Security Threats to the Communications Supply Chain Through FCC Programs,</E>
                             WC Docket No. 18-89, Order, DA 23-938 (WCB Oct. 10, 2023) (granting extension of time requests by WorldCell Solutions, LLC, Mediacom Communications Corporation, Virginia Everywhere, LLC, James Valley Cooperative Telephone Company, and NE Colorado Cellular, Inc. d/b/a Viaero Wireless); 
                            <E T="03">Protecting Against National Security Threats to the Communications Supply Chain Through FCC Programs,</E>
                             WC Docket No. 18-89, Order, DA 23-1016 at 1, para. 1 (WCB Oct. 27, 2023) (granting extension of time requests of Point Broadband Fiber Holding, LLC and SI Wireless, LLC).
                        </P>
                    </FTNT>
                    <P>
                        50. RWA also argues that location-based routing should only be required “to the extent that there is federal financial support afforded to small providers for the cost of compliance and additional time afforded for compliance beyond that proposed in the NPRM.” The Commission has never conditioned CMRS providers' compliance with 911 obligations on the receipt of Federal funding and we decline to do so. Further, the record does not provide compelling evidence that such funding is necessary. RWA fails to provide any specific estimates as to the actual cost of compliance for its members or to otherwise document a need for Federal financial support.
                        <SU>79</SU>
                        <FTREF/>
                         Without information on the actual cost of compliance or specific impacts of such compliance on CMRS providers, naked claims that Federal financial support is necessary in order for CMRS providers to comply with the Commission's 911 requirements lack merit. As noted above, if an individual CMRS provider encounters unique or unusual factual circumstances, it may seek a waiver under the Commission's waiver rules.
                        <SU>80</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>79</SU>
                             RWA NPRM Comments at 1, n.3 (acknowledging that “RWA members have received no specific vendor estimates as to the actual cost of compliance”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>80</SU>
                             47 CFR 1.925.
                        </P>
                    </FTNT>
                    <P>51. CCA argues that a four-year timeline is needed to account for “levels of support the nation's smaller wireless carriers typically receive from device makers, technology vendors, and software service providers and with the continued, incremental progress of PSAP systems in all areas of the country to support the location-based routing of emergency communications.” However, CCA has not documented the need for a four-year timeline as opposed to twenty-four months to address the specific obstacles faced by these providers. Once nationwide CMRS providers complete their six-month deployment obligation, non-nationwide providers will have 18 months to engage with device makers, vendors, and consultants. In addition, as noted above, the timeline is not dependent on PSAPs making “incremental progress” to support location-based routing because PSAPs do not need to take any specific technical steps to be ready to receive location-based routed calls.</P>
                    <P>
                        52. CCA and RWA also argue that non-nationwide CMRS providers should be afforded a four-year timeline because “AT&amp;T required four years to deploy location-based routing.” We disagree. First, AT&amp;T states that it was able to deploy location-based routing to virtually all PSAPs within six months, not four years as asserted by CCA and RWA.
                        <SU>81</SU>
                        <FTREF/>
                         Second, even if AT&amp;T or other nationwide CMRS providers took additional time to plan early implementation of nationwide location-based routing across their networks, it does not follow that non-nationwide CMRS providers need the same amount of time 
                        <E T="03">after</E>
                         the nationwide CMRS providers have completed their implementations.
                        <SU>82</SU>
                        <FTREF/>
                         BRETSA notes that other providers are likely to require less time than AT&amp;T to deploy location-based routing because “AT&amp;T has already developed the solution and provided a roadmap for implementation of LBR.” In fact, the nationwide CMRS providers have already done critical work to enable location-based routing by adopting highly accurate handset-based location, which AT&amp;T has confirmed “is available for location-based routing on the vast majority of iOS and Android devices.” The nationwide carriers have also validated that location-based routing can be used for the vast majority of wireless 911 calls and that it does not result in additional call delay or an increase in abandoned 911 calls. We agree with iCERT that existing support for location-
                        <PRTPAGE P="18500"/>
                        based routing by nationwide carriers “provides ample evidence that LBR will soon be ready for wider implementation.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>81</SU>
                             AT&amp;T NPRM Comments at 3 (“AT&amp;T was able to deploy location-based routing to virtually all PSAPs within a six-month timeframe.”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>82</SU>
                             
                            <E T="03">See</E>
                             Intrado PN Comments at 10 (“AT&amp;T's implementation model provides a roadmap to the other carriers.”).
                        </P>
                    </FTNT>
                    <P>53. CCA also argues that non-nationwide CMRS providers need longer timelines to ensure network reliability and quality of service before undertaking network-wide location-based routing implementation. Again, CCA fails to provide specific examples of how non-nationwide CMRS providers' network reliability and quality of service would be compromised by implementing location-based routing within a 24-month timeline. CCA also asserts that non-nationwide CMRS providers may use “different LTE and 5G-NR network specifications” than the nationwide providers and that it will be challenging for non-nationwide CMRS providers to implement location-based routing given the “array of potentially viable standards any one of which might, over time, fail to achieve scale and fall behind the other standards in features, support, and adoption.” We believe a 24-month timeline is sufficient to address these issues. As BRETSA notes, non-nationwide CMRS providers have not provided specific vendor estimates as to the actual cost to implement location-based routing. We agree with BRETSA that nationwide CMRS providers have provided a path for implementing location-based routing, and there is no reason to delay implementation by non-nationwide CMRS providers beyond the two years afforded. We conclude that the considerable benefits of improved 911 routing should extend to all callers, including subscribers to non-nationwide CMRS providers' services, and that delaying improved 911 routing by more than 24 months would be inequitable for these subscribers.</P>
                    <P>
                        54. Some entities representing non-nationwide CMRS providers argue that location-based routing will provide minimal improvement in the areas which their members serve, and therefore that the Commission either should not require location-based routing or should further delay compliance with location-based routing rules for non-nationwide CMRS providers. CCA asserts that “location-based routing may not provide any meaningful improvement over the status quo at the cost of dangerously longer call set up times” for smaller CMRS providers that tend to serve less densely populated areas.
                        <SU>83</SU>
                        <FTREF/>
                         Alaska Telecom notes that Alaska's unique situation of geography and low population areas means fewer misroutes and less benefit from location-based routing, such that “costs that carriers will bear to implement LBR on a short timescale will far outstrip the potential benefits.” We acknowledge that the advantages of location-based routing in comparison to legacy E911 routing may not be uniform across all areas or across all CMRS providers. However, we agree with Intrado that “[e]ven in low misroute areas, LBR implementation will result in a significant reduction in misroutes compared to the current system of exclusively relying on tower-based routing.” The benefits of improved routing should accrue to all 911 callers nationwide, across jurisdictions and CMRS providers, and 911 authorities have articulated a clear need for consistent routing technology across CMRS providers. We therefore decline to exempt or postpone location-based routing implementation on the basis that it may provide less benefit in some areas than others.
                    </P>
                    <FTNT>
                        <P>
                            <SU>83</SU>
                             CCA NPRM Comments at 2-3. As discussed herein, the Commission's location-based routing rules require providers to route on precise location information that is available at the network at time of routing, which renders moot the potential need for call holding.
                        </P>
                    </FTNT>
                    <P>
                        55. Modification of Deadlines by Agreement. We recognize that there may be some narrow scenarios in which individual PSAPs need additional time to facilitate location-based routing.
                        <SU>84</SU>
                        <FTREF/>
                         AT&amp;T states that while it was able to deploy location-based routing to virtually all PSAPs within six months, “some PSAPs required special attention and more time.” To provide flexibility for PSAPs that request it, we adopt a rule allowing a PSAP and a CMRS provider to set, by mutual consent, deadlines to implement location-based routing in the PSAP's jurisdiction that are different from those otherwise established by the rules. For example, the parties may mutually agree to extend the provider's timeline for location-based routing implementation in the PSAP's jurisdiction. We emphasize that parties may not use this exception to delay implementation and deployment of location-based routing indefinitely. Accordingly, in the event of any agreement to an alternate time frame for implementing location-based routing, we require the CMRS provider to notify the Commission of the agreed-to dates within 30 days of the parties' agreement or 30 days from the effective date of the final rules, whichever is later.
                        <SU>85</SU>
                        <FTREF/>
                         The CMRS provider must subsequently notify the Commission of the actual date by which it comes into compliance with the location-based routing requirements, within 30 days of that actual date of compliance or 30 days from the effective date of the final rules, whichever is later.
                    </P>
                    <FTNT>
                        <P>
                            <SU>84</SU>
                             
                            <E T="03">See, e.g.,</E>
                             T-Mobile NPRM Comments at 5 (stating that “in at least one instance, T-Mobile is aware that an emergency calling authority requested that another 911 vendor indefinitely suspend using LBR for 911 calls to its PSAPs because the vendor's LBR implementation resulted in a greater number of 911 calls that required transfer to another PSAP”); AT&amp;T PN Comments at 4 &amp; n.3 (stating that AT&amp;T completed its location-based routing deployment by the end of June 2022 “with very few exceptions” and stating that “[a] few PSAPs are using unique applications of Emergency Services Numbers to implement internal routing solutions” and that AT&amp;T is “working with these PSAPs to ensure [its] location-based routing solution meets their unique needs”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>85</SU>
                             CMRS providers must file such notifications in PS Docket No. 18-64.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Text-to-911</HD>
                    <P>
                        56. We require nationwide and non-nationwide CMRS providers to deploy and use location-based routing for RTT communications to 911 within 24 months from the effective date of the final rules adopted. This is a modification of the rules proposed in the notice of proposed rulemaking, which would have required CMRS providers and all other covered text providers to deploy and use location-based routing for all 911 texts within 18 months.
                        <SU>86</SU>
                        <FTREF/>
                         We extend the compliance timeline from 18 to 24 months in order to align compliance timelines for RTT communications to 911 with the compliance timelines for non-nationwide providers to implement location-based routing for wireless 911 voice calls. In addition, we limit our rules to the routing of RTT communications to 911 by CMRS providers. We decline at this time to extend location-based routing requirements to SMS text messages to 911, both because industry has not yet developed standards for implementing location-based routing on SMS networks and to avoid requiring providers to retrofit legacy SMS networks. We similarly defer extending location-based routing requirements to interconnected text providers.
                    </P>
                    <FTNT>
                        <P>
                            <SU>86</SU>
                             Notice of Proposed Rulemaking, 37 FCC Rcd at 15197, para. 33. The term “`covered text provider' includes all CMRS providers as well as all providers of interconnected text messaging services that enable consumers to send text messages to and receive text messages from all or substantially all text-capable U.S. telephone numbers, including through the use of applications downloaded or otherwise installed on mobile phones.” 47 CFR 9.10(q)(1).
                        </P>
                    </FTNT>
                    <P>
                        57. Location-Based Routing for RTT. We find that it is technologically feasible for CMRS providers to enable location-based routing for RTT communications. Because RTT is an IP-native service, RTT communications are processed on IP-based networks 
                        <PRTPAGE P="18501"/>
                        similarly to voice calls originating on IP-based networks. According to NENA, an RTT session is “handled and routed the same way as a voice call and delivers location just as a voice call would.” 
                        <SU>87</SU>
                        <FTREF/>
                         We agree with NENA that our rules “should reflect this reality.” In addition, because RTT resembles voice calling in that it is a real-time, two-way service, the user experience of RTT is likely to be similarly sensitive to the delays associated with misroutes. Given the technical similarities with processing voice calls originating on IP-based networks and strong support for implementing requirements for location-based routing for text-to-911 as a general matter, we adopt a requirement for location-based routing for RTT communications to 911 consistent with the requirements we adopt for wireless 911 voice calls originating on IP-based CMRS networks. In addition, commenters specifically support location-based routing for RTT communications.
                        <SU>88</SU>
                        <FTREF/>
                         CMRS providers urge the Commission to incentivize both PSAPs and CMRS providers to move toward next generation texting technologies such as RTT. We find that these requirements will help to ensure that the benefits of location-based routing extend to RTT users as more CMRS providers implement RTT service. We note that this rule is not intended to expand CMRS providers' existing obligations to deploy RTT capabilities to PSAPs beyond what is already required by the Commission.
                        <SU>89</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>87</SU>
                             NENA NPRM Reply at 10. Unlike SMS text-to-911, which uses a Text Control Center for routing, “RTT uses the existing IP-based voice architecture.” NENA, NENA PSAP Readiness for Real-Time Text (RTT) Information Document, NENA-INF-042.1-2021 at 10 (Jan. 20, 2021), 
                            <E T="03">https://cdn.ymaws.com/www.nena.org/resource/resmgr/standards/nena-inf-042.1-2021_rtt_appv.pdf</E>
                             (
                            <E T="03">NENA RTT Information Document</E>
                            ). The RTT communication “enters the Common IMS Network via the Proxy/Emergency Call Session Control Functions (P/E-CSCF) which provide the routing functions.” 
                            <E T="03">NENA RTT Information Document</E>
                             at 13. This is also how wireless 911 voice calls originating on IP-based networks are processed. 
                            <E T="03">See ATIS-0700015.v005</E>
                             (“[The P-CSCF] receives the emergency call from the User Equipment via the Access Network. The P-CSCF detects that the call is an emergency call and forwards it to/toward the E-CSCF.”). Then, “[t]he Common IMS Network will acquire location using the Location Retrieval Function (LRF) and Location Server (LS) and determine the routing using the Routing Determination Function (RDF).” 
                            <E T="03">NENA RTT Information Document</E>
                             at 13. Again, this is also how wireless 911 voice calls originating on IP-based networks are processed. 
                            <E T="03">See ATIS-0700015.v005</E>
                             at 24 (“The LRF obtains location information associated with the emergency call (by interacting with an LS, if necessary) and uses that location to acquire routing information for the emergency call from the RDF.”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>88</SU>
                             T-Mobile NPRM Comments at 11 (stating that “stakeholders should focus their efforts on supporting more robust means of text-based communication with PSAPs, including RTT”); Verizon NPRM Comments at 5 (“Verizon's planned LBR implementation for VoLTE will support real-time-text (RTT) 911 calls.”); NENA NPRM Reply at 9 (“The Commission's rules should apply to end-to-end RTT calls regardless of NG9-1-1 capability.”); ATIS NPRM Comments at 3 (urging the Commission “to clarify that only providers of such next generation text solutions [as defined in ATIS and NENA standards] are required to use LBR”); 
                            <E T="03">see also</E>
                             CTIA NPRM Reply at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>89</SU>
                             RTT transition obligations apply to “those entities that are involved in the provision of IP-based wireless voice communication service, and only to the extent that their services are subject to existing TTY technology support requirements under Parts 6, 7, 14, 20, or 64 of the Commission's rules.” 
                            <E T="03">RTT Order,</E>
                             31 FCC Rcd at 13576-77, para. 12. The Commission requires CMRS providers transmitting over an IP network that choose to enable the transmission and receipt of communications via RTT, in lieu of TTY technology, to and from any PSAP served by their network, to enable such service in a manner that fully complies with all applicable 911 rules. 
                            <E T="03">Id.</E>
                             at 13591-92, para. 43. PSAPs require special capabilities to receive RTT communications from CMRS providers. 
                            <E T="03">Id.</E>
                             at 13592, para. 43. We recognize that many PSAPs are not currently capable of supporting RTT communications and remain reliant on TTY technology to receive calls from people with disabilities. Texas 9-1-1 Entities NPRM Comments at 5; 
                            <E T="03">see RTT Order</E>
                             at 13592, para. 43; FCC, What Public Safety Answering Points Should Know about Real-Time Text at 2 (Oct. 2, 2018), 
                            <E T="03">https://www.fcc.gov/sites/default/files/documents/events/fact_sheet_about_real-time_text_for_public_safety_answering_points.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        58. Compliance Deadlines for Location-Based Routing for RTT. We require CMRS providers to implement location-based routing for RTT within 24 months after the effective date of the final rules on location-based routing. This timeline is six months longer than the eighteen-month period the Commission proposed in the notice of proposed rulemaking for all covered text providers to route all texts to 911. Most of the comments received on timelines address 911 texts in general, without specifically addressing issues related to RTT implementation in particular.
                        <SU>90</SU>
                        <FTREF/>
                         Some commenters support the originally proposed 18-month timeline for text-to 911,
                        <SU>91</SU>
                        <FTREF/>
                         while others support a shorter timeline. NASNA suggests that “it may be more appropriate to apply the same implementation timeframes for 911 texts that are being applied to voice 911 calls.” Other commenters urge that covered text providers be given a longer timeline to implement location-based routing. For example, Verizon notes that several parties echo its own comments regarding the need for a longer implementation period for 911 texts. Verizon “expects that an implementation period of 18-24 months for a ‘best available location’ approach could be technically feasible, 
                        <E T="03">provided that</E>
                         the rules afford wireless providers flexibility in the location query methods and per-call thresholds governing whether precise versus coarse location is used for routing.” 
                        <SU>92</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>90</SU>
                             Verizon does comment on RTT specifically and distinguishes it from other 911 texting, with an indication that it may be easier for Verizon to implement RTT than SMS location-based routing. Verizon states that “[w]hile Verizon's planned LBR implementation for VoLTE will support real-time-text (RTT) 911 calls, LBR for SMS is not feasible using our existing platforms and capabilities, and would require substantial network- and device-level changes and upgrades.” Verizon NPRM Comments at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>91</SU>
                             
                            <E T="03">See, e.g.,</E>
                             iCERT NPRM Comments at 2 (supporting 18-month timeline for all covered text providers, “without regard to service area”); NENA NPRM Comments at 1; AT&amp;T NPRM Comments at 6 (supporting 18-month compliance timetable, but conditioned on PSAP request and readiness).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>92</SU>
                             Verizon NPRM Reply at 2; 
                            <E T="03">see also, e.g.,</E>
                             RWA NPRM Comments at 3 (indicating smaller providers need more time to comply than larger providers, and requesting small rural providers be given 36 months from the effective date of the rules to implement text-to-911, “and then only if the PSAP is capable of handling the call routing”); Southern Linc NPRM Reply at 6-8 (stating that if Commission requires location-based routing for SMS-based texts to 911, nationwide CMRS providers should have at least 18-24 months from the effective date of the rules and non-nationwide CMRS providers should have an additional 12-18 months beyond that, in recognition of smaller carriers' “additional challenges and resource constraints” and that a CMRS provider's obligation to commence use should only be triggered by a valid request from the PSAP or other relevant authority).
                        </P>
                    </FTNT>
                    <P>
                        59. We conclude that a timeline of 24 months after the effective date of the rules is technically feasible for CMRS providers to implement location-based routing for RTT. We also believe that 24 months will provide sufficient time for both nationwide and non-nationwide CMRS providers to implement location-based routing for RTT. We decline to adopt a shorter timeline for nationwide CMRS providers and instead opt, consistent with the notice of proposed rulemaking, to apply the same timetable to all providers for implementation of location-based routing for RTT communications. Unlike for 911 voice calls, the extent to which nationwide CMRS providers have implemented location-based routing for RTT is not clear, though we note that T-Mobile and Verizon explicitly support this step. In addition, few PSAPs have developed the capability to receive end-to-end RTT communications.
                        <SU>93</SU>
                        <FTREF/>
                         Since RTT remains in the early stages of development, we believe that a unified timeline for nationwide and non-nationwide CMRS providers is consistent with the approach in the Commission's existing text-to-911 rules, which do not distinguish between nationwide and 
                        <PRTPAGE P="18502"/>
                        non-nationwide CMRS providers.
                        <SU>94</SU>
                        <FTREF/>
                         In addition, given that RTT uses call processing similar to that used for voice calls, we anticipate that non-nationwide CMRS providers will be able to implement this capability on the same timeline as location-based routing for voice calls originating on IP-based networks. However, we encourage CMRS providers (nationwide or non-nationwide) to adopt location-based routing for RTT before the 24-month deadline if feasible.
                    </P>
                    <FTNT>
                        <P>
                            <SU>93</SU>
                             
                            <E T="03">See</E>
                             Donny Jackson, 
                            <E T="03">APCO speakers say RTT being used operationally, could be key platform for 911 in the future,</E>
                             IWCE's Urgent Communications (Aug. 8, 2023), 
                            <E T="03">https://urgentcomm.com/2023/08/08/apco-speakers-say-rtt-being-used-operationally-could-be-key-platform-for-911-in-the-future/</E>
                             (Jackson, 
                            <E T="03">APCO speakers</E>
                            ) (noting 911 officials stress the “nascent operation of RTT for emergency calling, as only a handful of PSAPs are using the technology at the moment”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>94</SU>
                             
                            <E T="03">See</E>
                             47 CFR 9.10(q)(1), (10).
                        </P>
                    </FTNT>
                    <P>
                        60. Location-based routing for SMS. Some public safety commenters urge the Commission to require location-based routing for all texts to 911, including SMS, so that improved text routing is available to individuals who are deaf, hard of hearing, or have speech related disabilities, and to people in situations where the sound of a voice call would place them in peril.
                        <SU>95</SU>
                        <FTREF/>
                         We agree with public safety commenters that location-based routing could provide benefits to communities that rely on text messaging to contact 911. However, we decline to require location-based routing for SMS messages at this time because the record indicates that industry has not yet developed standards for implementing location-based routing on SMS networks and because of the potential cost of requiring covered text providers to retrofit legacy SMS networks.
                    </P>
                    <FTNT>
                        <P>
                            <SU>95</SU>
                             COPUC NPRM Comments at 8; BRETSA NPRM Reply at 8; NASNA NPRM Comments at 13. DISA also argues that location-based routing for text-to-911 could also decrease the response time for 911 texts originating outside the three-mile line off U.S. and Territorial shores. DISA NPRM Comments at 1.
                        </P>
                    </FTNT>
                    <P>
                        61. In particular, commenters note that enabling location-based routing for SMS would require updates to the relevant technical standard, ATIS/TIA J-STD-110.
                        <SU>96</SU>
                        <FTREF/>
                         According to NENA, implementing standards-based SMS solutions would add at least two years for standards development, product development, and deployment. T-Mobile, Alaska Telecom, and Verizon also note that implementing location-based routing for SMS would require potentially costly retrofitting of legacy SMS networks. Verizon argues that enabling location-based routing for SMS “would require substantial upgrades of Short Message Service Center (SMSC) and Text Control Center (TCC) facilities . . . and device changes to enable the device to override security, privacy and other functions to access the caller's device-level location information.” In addition, Verizon argues that requiring location-based routing for SMS could impose duplicative cost and implementation burdens that would be unnecessary once a jurisdiction launches i3 NG911 capabilities. We also note that some PSAPs remain incapable of receiving texts and that the volume of 911 texts is far smaller than volume of wireless 911 voice calls.
                        <SU>97</SU>
                        <FTREF/>
                         In light of these factors, we find that it would not serve the public interest to require CMRS providers to retrofit legacy SMS networks.
                    </P>
                    <FTNT>
                        <P>
                            <SU>96</SU>
                             Verizon NPRM Comments at 5; Southern Linc NPRM Reply at 7; NENA NPRM Reply at 9, n.41; ATIS NPRM Comments at 3. ATIS/TIA J-STD-110.v002 defines the requirements, architecture, and procedures for text messaging to 911 emergency services using native wireless operator SMS capabilities for the existing and NG911 PSAPs. ATIS and Telecommunications Industry Association (TIA), 
                            <E T="03">Joint ATIS/TIA Native SMS/MMS Text to 9-1-1 Requirements and Architecture Specification—Release 2</E>
                             at sections 7, 8, and 9 (May 2015), 
                            <E T="03">https://webstore.ansi.org/standards/atis/std110</E>
                             (
                            <E T="03">ATIS/TIA J-STD-110.v002</E>
                            ). In 2014, the Commission explained that “The scope of the J-STD-110 is limited to text messaging to 9-1-1 for native SMS capabilities, and it does not address support of text-to-911 for interconnected text services using ‘over-the-top’ SMS.” 
                            <E T="03">T911 Second Report and Order,</E>
                             29 FCC Rcd at 9864, para. 39 n.106 (citing to a previous version of ATIS/TIA J-STD-110, Section 1.1).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>97</SU>
                             As of December 2023, the Commission's Text-to-911 Registry lists 3,201 PSAPs as text-capable. 
                            <E T="03">See</E>
                             FCC, PSAP Text-to-911 Readiness and Certification Registry, 
                            <E T="03">https://www.fcc.gov/general/psap-text-911-readiness-and-certification-form.</E>
                             In calendar year 2022, U.S. PSAPs received a combined total of 824,609 texts to 911 in comparison to 157,999,298 wireless 911 voice calls. Fifteenth Annual 911 Fee Report at 13-16, Table 3.
                        </P>
                    </FTNT>
                    <P>
                        62. We recognize that the three nationwide CMRS providers are using non-standardized location-based routing techniques to route some SMS texts to 911 today.
                        <SU>98</SU>
                        <FTREF/>
                         We encourage all CMRS providers to deploy location-based routing for SMS messages voluntarily to the extent that their resources permit, and we intend to monitor the development of standards, products, and other advances affecting location-based routing for SMS text-to-911. However, we agree with NENA that “the Commission's rules should not back the market into adopting non-standardized technologies for a legacy platform that the industry is actively working to phase out.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>98</SU>
                             
                            <E T="03">See</E>
                             AT&amp;T PN Comments at 5 (describing AT&amp;T's location-based routing for text-to-911 implementation); T-Mobile July 26, 2023 
                            <E T="03">Ex Parte</E>
                             at 3; Verizon Dec. 7, 2023 
                            <E T="03">Ex Parte</E>
                             at 1. NENA also states “There are non-standards-based mechanisms for supporting location-based routing for interim text 156 which are available and in-use in the market today.” NENA NPRM Reply at 9.
                        </P>
                    </FTNT>
                    <P>
                        63. We decline to adopt commenters' alternative proposal to require CMRS providers to route SMS text messages using “best available” location information. Instead of a tiered system, in which CMRS providers would use precise location information within a radius of 165 meters at a 90% confidence level and otherwise default to best available location information, these commenters suggest a requirement to route SMS text messages based on best available location information (
                        <E T="03">i.e.,</E>
                         there would be no requirement to use highly precise location information when it is available from the handset). Intrado argues that, unlike wireless 911 voice calls to 911, for SMS “there is no fallback information available for text and no technologic way or need to implement LBR for text differently nor any means to apply a specific uncertainty/confidence requirement . . . .” As with the proposed requirement to route text messages when available location information meets our accuracy and timeliness criteria, solutions that route using “best available” location information are still not standards-based. Therefore, we decline to require CMRS providers to implement non-standard location-based routing solutions for SMS text messages at this time. The Commission may reconsider if applicable standards are developed.
                    </P>
                    <P>
                        64. Under the Commission's existing text-to-911 rules, “covered text providers must obtain location information sufficient to route text messages to the same PSAP to which a 911 voice call would be routed, unless the responsible local or state entity designates a different PSAP to receive 911 text messages . . . .” 
                        <SU>99</SU>
                        <FTREF/>
                         The implementation of location-based routing, which uses more precise location information than the tower-based routing method, may change the PSAP to which a 911 voice call would otherwise be routed. We do not interpret this provision to require covered text providers to obtain the same precise location information for SMS or other non-RTT text messages that would be used for a voice call subject to the Commission's location-based routing rules. Instead, this provision would continue to require covered text providers to obtain location information sufficient to route text messages (other than RTT) to the same PSAP to which a wireless 911 voice call would be routed using coarse location or other equivalent means, the routing technology in use at the time of adoption of this rule.
                        <SU>100</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>99</SU>
                             47 CFR 9.10(q)(10)(i).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>100</SU>
                             
                            <E T="03">T911 Second Report and Order,</E>
                             29 FCC Rcd at 9874, para. 57 (“We require covered text providers to route texts to 911 using coarse location (cell ID and cell sector) or other equivalent means that allows the covered text provider to route a text to the appropriate PSAP.”).
                        </P>
                    </FTNT>
                    <P>
                        65. Location-based routing for other text-messaging platforms. We decline to consider location-based routing for other types of text-messaging platforms, such as Multimedia Messaging Service 
                        <PRTPAGE P="18503"/>
                        (MMS) platforms, at this time. To the extent that commenters discussed other text messaging platforms, such comments combined arguments regarding SMS and MMS platforms.
                        <SU>101</SU>
                        <FTREF/>
                         As discussed herein, MMS platforms rely on many of the same functional network elements that would be used to process SMS messages. We therefore decline to consider requirements for location-based routing for MMS for the same reasons discussed in this section for SMS text. We also decline consideration of location-based routing for over-the-top (OTT) platforms, as no commenter discussed OTT platforms.
                    </P>
                    <FTNT>
                        <P>
                            <SU>101</SU>
                             
                            <E T="03">See, e.g.,</E>
                             GCI July 17, 2023 
                            <E T="03">Ex Parte</E>
                             at 1 (“LBR for SMS/MMS text-to-911 would be much more difficult than for IP-originated wireless calls . . . .”); NENA NPRM Reply at 8 (discussing that “interim text uses SMS/MMS for emergency text calls”); Intrado NPRM Comments at 4 (discussing “SMS/MMS design”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Definitions</HD>
                    <P>
                        66. In the notice of proposed rulemaking, the Commission proposed to define “location-based routing” as routing based on the location of the calling device rather than the location of network elements such as cell site or sector. The Commission also proposed a definition of “device-based location information” and sought comment on whether the definition adequately encompasses current and future location technologies. We adopt these definitions as proposed and find that they will add clarity to the rules while remaining flexible and allowing for the future evolution of new technologies. We defer consideration of the proposed definitions of other terms relating to IP delivery for NG911 networks to the separate NG911 transition proceeding in PS Docket No. 21-479.
                        <SU>102</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>102</SU>
                             
                            <E T="03">NG911 Notice of Proposed Rulemaking</E>
                             at *20, para. 51. For example, commenters discussed definitions for the terms “NG911,” “ ‘IP-based’ 911,” and “NG911-capable PSAPs,” which we believe would be better addressed in the NG911 proceeding so as to apply to a wider array of 911 originating service providers. 
                            <E T="03">See</E>
                             APCO NPRM Comments at 5; CTIA NPRM Comments at 8; Southern Linc NPRM Reply at 8-9; NENA NPRM Reply at 4-5, 7-8.
                        </P>
                    </FTNT>
                    <P>
                        67. Location-Based Routing. The notice of proposed rulemaking proposed to define “location-based routing” as the use of information on the location of a device, including but not limited to device-based location information, to deliver 911 calls and texts to point(s) designated by the authorized local or state entity to receive wireless 911 calls and texts, such as an Emergency Services internet Protocol Network (ESInet) or PSAP, or to an appropriate local emergency authority. Most commenters addressing the issue, including NASNA, NENA, COPUC, and Alaska Telecom, support the proposed definition.
                        <SU>103</SU>
                        <FTREF/>
                         Alaska Telecom states that the proposed definition is flexible and “will give carriers, 911 vendors, and public safety entities the ability to invest time and resources into new and improved location technologies.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>103</SU>
                             NASNA NPRM Comments at 14; COPUC NPRM Comments at 8; Alaska Telecom NPRM Reply at 4 (noting also that Alaska Telecom “believes that it is important that ‘location’ be limited to the autonomous location derived by the device, with accuracy based on what is coming from the device, not information derived by the carrier network”).
                        </P>
                    </FTNT>
                    <P>
                        68. APCO and AT&amp;T suggest that the definition avoid reference to “device-based location information” or to ESInets. APCO states that it does not disagree with the assumption that ESInets may be a potential delivery point for 911 calls, but contends that “a simpler approach that does not reference ESInets could avoid unintentional limitations.” 
                        <SU>104</SU>
                        <FTREF/>
                         AT&amp;T argues that identifying ESInets as end points that state or local 911 authorities can designate is outside the scope of the proceeding and unnecessary.
                        <SU>105</SU>
                        <FTREF/>
                         NENA and Alaska Telecom oppose narrowing the definition, and DISA and COPUC support including ESInets as an illustrative example. Alaska Telecom states that “[t]he Commission's proposed definition allows for technological development and improvement over time, in contrast to the changes suggested by APCO” to define “location-based routing” by reference to uncertainty and confidence metrics.
                    </P>
                    <FTNT>
                        <P>
                            <SU>104</SU>
                             APCO NPRM Comments at 4. APCO does not specifically identify what such “unintentional limitations” are, but cites to its discussion of “the current state of ESInet capabilities.” APCO NPRM Comments at 4, n.20. APCO asserts that “ESInets may or may not be capable of performing location-based routing after receiving the call from a wireless service provider. Thus, the NPRM's consideration of `NG9-1-1 capabilities' and ESInets as factors for the location-based routing requirements raises concerns. The Commission can and should adopt location-based routing requirements without considering `NG9-1-1' progress or ESInet deployment.” 
                            <E T="03">Id.</E>
                             at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>105</SU>
                             AT&amp;T NPRM Comments at 8. However, AT&amp;T also states that “individual states and PSAP authorities can designate ESInets as an endpoint for the delivery of 911 calls[,]” and “encourages the Commission . . . to confirm that states and local jurisdictions have this authority.” 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>69. We adopt the proposed definition in order to provide guidance to regulated entities on how to comply with our location-based routing rules. This definition of location-based routing does not extend to tower-based routing methodologies. We disagree with APCO that referring to ESInets in the rules as an illustrative example could unintentionally limit the location-based routing definition. APCO objects to referencing ESInets in the definition because “ESInets may or may not be capable of performing location-based routing.” However, the term is used in the definition merely to identify ESInets as a potential delivery point for 911 voice calls and RTT communications, without any reference to the technical capabilities of ESInets. Including ESInets as an illustrative example clarifies that providers can use location-based routing to deliver 911 calls to ESInets, without precluding or limiting use of other network architectures and end points. We similarly disagree with the view that use of the term “device-based location information” in the definition is too limiting. Again, the term is included as an illustrative example rather than a technological restriction. Thus, location technologies that do not use device-based location information may also fall within the scope of the location-based routing definition.</P>
                    <P>
                        70. Device-Based Location Information. The notice of proposed rulemaking proposed to define “device-based location information” as “[i]nformation regarding the location of a device used to call or text 911 generated all or in part from on-device sensors and data sources.” The Commission noted that this term is used in the existing rule on delivery of 911 text messages and that the proposed definition would also apply to that rule. We conclude that this definition of “device-based location information” provides useful guidance to regulated entities for compliance with the location-based routing rules, while remaining flexible enough to account for future technological development. COPUC supports the definition proposed in the notice of proposed rulemaking. Several other commenters urge the Commission to ensure that the definition is flexible enough to encompass current and future technologies.
                        <SU>106</SU>
                        <FTREF/>
                         We find that the definition is sufficiently broad and flexible to meet this goal.
                    </P>
                    <FTNT>
                        <P>
                            <SU>106</SU>
                             AT&amp;T NPRM Comments at 3-4 (citing Commission's wording in the notice of proposed rulemaking); 
                            <E T="03">see also</E>
                             Alaska Telecom NPRM Reply at 4 (supporting Commission's proposed definition as allowing for technological development and improvement over time); NENA NPRM Reply at 4 (citing AT&amp;T NPRM Comments at 3-4).
                        </P>
                    </FTNT>
                    <P>
                        71. We also decline to adopt several suggestions from the record to modify the definition of “device-based location information.” AT&amp;T supports “a definition of `device-based location information' that is tied to timeliness and accuracy metrics . . . .” However, the “device-based location information” definition is intended to describe a mechanism for deriving location 
                        <PRTPAGE P="18504"/>
                        information rather than determining the timeliness or accuracy of the information. In addition, we separately set forth timeliness and accuracy metrics elsewhere in the rules. DISA suggests adding language to indicate that the location is to be determined “at origination (setup) of [a] voice call.” We decline to adopt this suggested change, as the issue of timeliness of the location information used for location-based routing is addressed in other rules we adopt.
                    </P>
                    <HD SOURCE="HD3">4. Timeliness and Accuracy of Location-Based Routing Information</HD>
                    <P>
                        72. We require CMRS providers to use location-based routing for wireless 911 voice calls and RTT communications to 911 when the location information available to the CMRS provider's network at time of routing is ascertainable within a radius of 165 meters at a confidence level of at least 90%. We anticipate that a substantial percentage of wireless 911 voice calls and RTT communications to 911 will route on location information meeting the accuracy and timeliness threshold under the rules adopted. If location information meeting this threshold is not available at the time of routing, we require CMRS providers to use the “best available” location information for routing wireless 911 voice calls and RTT communications to 911. Such “best available” location information may include but is not limited to device-based location information that does not meet the accuracy threshold, tower-based location information (
                        <E T="03">e.g.,</E>
                         the centroid of the area served by the cell sector that first picks up the call), or other location information. The requirements we adopt are those proposed in the notice of proposed rulemaking with slight definitional modifications.
                    </P>
                    <HD SOURCE="HD3">a. Timeliness Threshold</HD>
                    <P>
                        73. As noted in the notice of proposed rulemaking, location-based routing requires information about the caller's location to be available quickly enough to enable the call to be routed without delaying the normal call set-up process. We adopt the Commission's proposal from the notice of proposed rulemaking to require the use of location-based routing only if caller location information is available to the CMRS provider network at the time that the CMRS provider would otherwise route the call.
                        <SU>107</SU>
                        <FTREF/>
                         This timeliness threshold is intended to avoid delay in transmitting wireless 911 voice calls and RTT communications to PSAPs.
                    </P>
                    <FTNT>
                        <P>
                            <SU>107</SU>
                             For CMRS providers, “all 911 calls” include “those [911 calls CMRS providers] are required to transmit pursuant to subpart C of this part [9].” 47 CFR 9.3. This definition therefore extends to texts, which are subject to 47 CFR 9.10(q), a provision which resides in subpart C of part 9 of the Commission's rules. In this document, we distinguish between 911 wireless voice calls, 911 texts, and RTT communications for the sake of precision. However, we preserve the language from the notice of proposed rulemaking for the purposes of this paragraph.
                        </P>
                    </FTNT>
                    <P>
                        74. The record indicates that currently available technology is routinely capable of delivering location information to CMRS provider networks for wireless 911 voice calls and RTT communications to 911 in time for routing without delay.
                        <SU>108</SU>
                        <FTREF/>
                         Nationwide CMRS providers' implementations have demonstrated that obtaining such location in time for routing is feasible. Devices that are capable of producing high accuracy, low latency location for emergency calling are in wide use, and IP network technology supports rapidly obtaining such precise location estimates. The location-based routing deployments of AT&amp;T,
                        <SU>109</SU>
                        <FTREF/>
                         T-Mobile,
                        <SU>110</SU>
                        <FTREF/>
                         and Verizon 
                        <SU>111</SU>
                        <FTREF/>
                         demonstrate that precise location information can be made routinely available to CMRS providers' networks in time for routing wireless 911 voice calls. Both Android devices using ELS and iOS devices using HELO are capable of generating high accuracy, low latency location information in time to support 911 call routing.
                        <SU>112</SU>
                        <FTREF/>
                         Moreover, iOS and Android devices account for 99.62% of the U.S. device market, meaning that this capability is widely available to consumers. Intrado states that 4G LTE and newer networks can obtain device-based location information, calculate confidence and uncertainty, and query the location server for PSAP routing instructions within the normal call set-up interval. T-Mobile states that the “IP Multimedia Subsystem (`IMS') technology and advancement of device-based hybrid location solutions has enabled the use of a caller's estimated device location for call routing without delaying call set-up.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>108</SU>
                             
                            <E T="03">See</E>
                             Notice of Proposed Rulemaking, 37 FCC Rcd at 15199, para. 38 (citing Intrado PN Comments at 6, 8; Apple Sept. 24, 2019 
                            <E T="03">Ex Parte</E>
                             at 2; and Android, 
                            <E T="03">Emergency Location Service—How It Works, https://www.android.com/safety/emergency-help/emergency-location-service/how-it-works/</E>
                             (last visited Jan. 17, 2024)); Verizon NPRM Comments at 6 (stating that RTT “will also benefit from the same routing improvements and advantages as i3 voice calls”); NENA NPRM Comments at 12 (stating that an RTT communication in NG911 “requires no special handling compared [to] a `conventional' voice call”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>109</SU>
                             AT&amp;T has used location-based routing for over 80% of all AT&amp;T wireless calls. Intrado PN Comments at 2. Intrado further notes that AT&amp;T's location-based routing solution provides location-based routing “without any impact to the timeline or call.” Intrado PN Comments at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>110</SU>
                             T-Mobile indicates that more than 95% of location estimates available at call routing on T-Mobile's network fall within the company's threshold, 
                            <E T="03">i.e.,</E>
                             “300 meters with a confidence level of 90%.” T-Mobile July 26, 2023 
                            <E T="03">Ex Parte</E>
                             at 1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>111</SU>
                             
                            <E T="03">See</E>
                             Verizon July 13, 2023 
                            <E T="03">Ex Parte</E>
                             at 1 (“To determine whether device-based hybrid location information provided by the device during a call is adequate for routing, Verizon uses an accuracy threshold of 200 meters maximum horizontal uncertainty with confidence of 90 percent.”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>112</SU>
                             Notice of Proposed Rulemaking, 37 FCC Rcd at 15191, para. 16. 
                            <E T="03">See also</E>
                             Android, Emergency Location Service—How It Works, 
                            <E T="03">https://www.android.com/safety/emergency-help/emergency-location-service/how-it-works/</E>
                             (last visited Jan. 17, 2024) (“On average, ELS is able to get a first location 3-4 seconds after the call has started.”); Android, Emergency Location Service—Overview, 
                            <E T="03">https://www.android.com/safety/emergency-help/emergency-location-service/</E>
                             (last visited Jan. 17, 2024) (“ELS works on over 99% of active Android devices running OS4.4 and up, with Google Play Services installed-no new hardware or activation required.”); Apple Sept. 24, 2019 
                            <E T="03">Ex Parte</E>
                             at 2 (indicating that device-based hybrid location is available from certain devices during call set-up and that location-based routing can be enabled on models 6s and later running iOS 13 and Apple Watch devices running watch OS 6).
                        </P>
                    </FTNT>
                    <P>
                        75. Some commenters suggest that the Commission should require CMRS providers to route 911 calls within five seconds to “prevent a CMRS provider from holding onto a call for eight to ten seconds or even longer waiting for a location fix.” 
                        <SU>113</SU>
                        <FTREF/>
                         We decline to adopt this requirement because doing so could incentivize CMRS providers to hold wireless 911 voice calls and RTT communications to 911 for the full five seconds when location information does not meet the threshold for accuracy, which could result in delays for wireless 911 voice calls and RTT communications to 911. The requirement that location information be available at time of routing, as the Commission stated in the notice of proposed rulemaking, “is intended to avoid delay in transmitting 911 calls and texts because there would be no requirement to hold calls and texts for purposes of obtaining a routing fix.” Intrado points out that deploying location-based routing under the Commission's proposed framework “renders moot the potential need for call holding.” We agree that the framework as adopted avoids 
                        <PRTPAGE P="18505"/>
                        introducing new delays for wireless 911 voice calls and RTT communications to 911. Conversely, if we were to set a maximum five-second time frame for routing, it could incentivize CMRS providers to hold calls and RTT communications at the network for the full five-second window to ensure routing based on “best available” location. This in turn could create delays in connecting callers to a PSAP and cause some callers to terminate their 911 calls. To avoid such adverse impacts, we decline to set a maximum time frame for routing wireless 911 voice calls or RTT communications to 911.
                    </P>
                    <FTNT>
                        <P>
                            <SU>113</SU>
                             NASNA NPRM Comments at 14; see also COPUC NPRM Comments at 6-7; iCERT NPRM Comments at 3 (“[W]e support the FCC's proposal to require use of LBR when the wireless network provider can determine the location of the caller within the recommended five-second window. If the caller's location is not available within this timeframe, the provider should use traditional cell site-based methods.”); see also BRETSA NPRM Reply at 14-15 (arguing that minimum hold times might increase the percentage of calls that can be routed on device-based hybrid location information where providers still operate 3G networks, or that 911 authorities may wish to participate in tests to determine whether holding calls would allow for additional calls on IP-based networks to be routed using location-based routing).
                        </P>
                    </FTNT>
                    <P>76. We also decline to specify, as suggested by DISA, that the location information used for routing be determined “at origination (setup) of [a] voice call.” While we expect that location for most calls will be determined at origination, DISA's proposal could inadvertently be too restrictive, if location were to arrive after the setup of a voice call but before routing. We believe it is sufficient to require only that location information be available at the time of call routing, regardless of when the location is determined.</P>
                    <P>77. NGA 911 asserts that a timeliness requirement “appears to leave a big gap in the implementation because a carrier may always be able to claim the information was not available at time of call routing.” The record indicates, however, that CMRS providers are already deploying technology that routinely provides the required location information at the time of call routing with no delay. For example, Intrado states that in AT&amp;T's network, location information meeting the threshold is available in time to route wireless 911 voice calls 80% of the time, and that routing on the network “requires no call delay.” We intend to monitor the deployment and use of location-based routing on CMRS provider networks with reporting requirements discussed herein. Should we learn that some CMRS providers are not taking full advantage of available technology that provides location-based routing information at the time of the call, we will consider whether additional measures are needed.</P>
                    <HD SOURCE="HD3">b. Accuracy Threshold</HD>
                    <P>78. Turning to the required accuracy threshold for location-based routing, we adopt the requirement that CMRS providers use location-based routing to route wireless 911 voice calls and RTT communications to 911 if the location information available at the time of routing identifies the horizontal location of the device within a radius of 165 meters at a confidence level of at least 90%. This requirement is consistent with the requirement the Commission proposed in the notice of proposed rulemaking.</P>
                    <P>79. We adopt the 165-meter threshold with a confidence level of at least 90% in light of the demonstrated efficacy of location-based routing using such a threshold and because this threshold provides enough flexibility to be compatible with nationwide CMRS providers' existing implementations of location-based routing. We believe that this location accuracy threshold will substantially reduce the number of misroutes associated with legacy E911 routing. AT&amp;T has applied a location accuracy threshold with a radius of 165 meters at a confidence level of 90% in its own network. Intrado states that location information meeting this location accuracy threshold is available to AT&amp;T's network to route calls 80% of the time, and most calls route on information that identifies the location of the device within 50 meters. As a result, AT&amp;T's solution “provid[es] a more optimal route than sector-based routing for approximately 10% of all wireless 911 calls” and “[t]herefore, 10% of calls will be getting to the correct PSAP on the first try and will not require transfers from the neighboring PSAP.”</P>
                    <P>
                        80. We agree with public safety entities and Intrado that it is imperative that we set an accuracy threshold that is realistic in light of existing technology while also providing room for future technological improvement.
                        <SU>114</SU>
                        <FTREF/>
                         APCO supports the proposed location accuracy threshold but remains open to an alternative that “strikes an appropriate balance between how often the device's location will be known quickly and accurately enough to use location-based routing rather than cell-sector based routing, and how effective the use of location-based routing will be at delivering the call to the correct ECC [emergency communications center].” AT&amp;T supports a location accuracy threshold “that the Commission believes would represent a significant improvement over cell-based routing methodologies.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>114</SU>
                             APCO NPRM Comments at 2; Adams County et al. NPRM Comments at 3 (“The proposed confidence levels are acceptable, but ideally, over time, the radiuses and confidence levels in the proposed rule should be tightened so that 911 calls are routed more precisely.”); BRETSA NPRM Comments at 8 (“Intrado has found that LBR from hybrid device location information will allow accurate routing of wireless 9-1-1 calls over 
                            <E T="03">80 percent</E>
                             of the time using thresholds of 165 meters and a 90 percent confidence level. 
                            <E T="03">The Commission should require national and regional wireless providers [to] implement LBR at the earliest possible time.”</E>
                             (Footnote omitted, citing Intrado PN Comments at 9)); Intrado NPRM Comments at 5.
                        </P>
                    </FTNT>
                    <P>
                        81. Some wireless industry commenters oppose the proposed location accuracy threshold and claim that additional flexibility is needed for providers to set individualized thresholds.
                        <SU>115</SU>
                        <FTREF/>
                         Verizon argues that a rigid location accuracy threshold is unnecessary to meet the Commission's public safety objectives and that any particular location accuracy threshold should at most serve as a safe harbor. ATIS asserts that providers should “strive” but not be mandated to produce location information for purposes of routing within a radius of 300 meters or less at a confidence level of 90%.
                        <SU>116</SU>
                        <FTREF/>
                         ATIS also asserts that it is developing best practices for carriers to implement location-based routing, and T-Mobile states that the Commission should wait for these best practices before requiring specific distance and confidence metrics for location-based routing.
                        <SU>117</SU>
                        <FTREF/>
                         We encourage ATIS to conclude any such efforts on a timeline that is consistent with the requirements adopted.
                    </P>
                    <FTNT>
                        <P>
                            <SU>115</SU>
                             CTIA NPRM Comments at 5; T-Mobile NPRM Comments at 10; Verizon NPRM Comments at 3; ATIS NPRM Comments at 3-4; 
                            <E T="03">see also</E>
                             Southern Linc NPRM Reply at 5-6 (agreeing with ATIS, T-Mobile, Verizon, and CTIA that it is premature to adopt specific metrics).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>116</SU>
                             ATIS NPRM Comments at 4. We note that a location accuracy threshold with a radius of 300 meters would also be an acceptable location-based routing implementation under the rules we adopt.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>117</SU>
                             T-Mobile July 26, 2023 
                            <E T="03">Ex Parte</E>
                             at 2; T-Mobile NPRM Reply at 3-4; T-Mobile NPRM Comments at 9; 
                            <E T="03">see also</E>
                             ATIS NPRM Comments at 4 (“[T]he Commission should defer to the recommendations regarding the feasibility of location accuracy from industry groups such as ATIS ESIF.”).
                        </P>
                    </FTNT>
                    <P>
                        82. We conclude that a mandatory threshold is necessary. The accuracy threshold we set ensures that all CMRS providers will use location-based routing nationwide for 911 calls and RTT communications to 911 when location information at the time of routing meets a high accuracy standard. We also disagree that there is a need to wait for the development of best practices, as the location-based routing rules we adopt require CMRS providers to use this methodology when the location information available to the network is highly accurate, and further permit CMRS providers to use location-based routing methodologies in additional scenarios. We observe that the nationwide CMRS providers have all completed or are currently implementing location-based routing on their IP-based networks, and all use location-based routing to route wireless 911 voice calls when available location meets this mandatory threshold for 
                        <PRTPAGE P="18506"/>
                        precision.
                        <SU>118</SU>
                        <FTREF/>
                         While no best practices have currently been developed, CMRS providers' implementations indicate a practical consensus that location-based routing can consistently be used when location information meets this threshold. We therefore decline to condition compliance with these rules on the completion of best practices by ATIS. We encourage ATIS to develop best practices to promote optimal routing on CMRS providers' networks.
                    </P>
                    <FTNT>
                        <P>
                            <SU>118</SU>
                             Verizon and T-Mobile also use location-based routing for less precise location estimates.
                        </P>
                    </FTNT>
                    <P>
                        83. While we require CMRS providers to use location-based routing when available location information is within a 165-meter radius at a standardized 90% confidence level, we emphasize that CMRS providers may also use location-based routing when location information available at time of routing is less precise than the accuracy threshold we adopt. To this extent, we agree with Verizon that CMRS providers should have flexibility to identify “provider-optimized threshold range[s] to accommodate individual service providers' vendor capabilities and user device capabilities.” We therefore provide flexibility to providers to set their own thresholds for use of location-based routing at a radius exceeding 165 meters at a 90% confidence level. While AT&amp;T uses the 165-meter accuracy threshold, Verizon and T-Mobile have implemented accuracy thresholds of 200 meters and 300 meters, respectively, with a standardized 90% confidence level.
                        <SU>119</SU>
                        <FTREF/>
                         This formulation provides flexibility for all three nationwide CMRS providers to continue applying their respective thresholds for determining when to use location-based routing for 911 calls and RTT communications to 911.
                    </P>
                    <FTNT>
                        <P>
                            <SU>119</SU>
                             Intrado notes that AT&amp;T's threshold is 165 meters at a 90% confidence level. Intrado PN Comments at 9. T-Mobile indicates that its threshold is 300 meters at a 90% confidence level. T-Mobile July 26, 2023 
                            <E T="03">Ex Parte</E>
                             at 1. Verizon indicates that its threshold is 200 meters at a 90% confidence level. Verizon July 13, 2023 
                            <E T="03">Ex Parte</E>
                             at 1.
                        </P>
                    </FTNT>
                    <P>
                        84. We confirm that the location accuracy threshold used for location-based routing of a radius of 165 meters at a confidence level of at least 90% would apply equally to both estimated civic address and coordinate-based location. We agree with NENA that a CMRS provider may have access to an estimated civic address for a calling device that may be used for location-based routing.
                        <SU>120</SU>
                        <FTREF/>
                         Many fixed broadband internet access devices, particularly those provided to the consumer by the broadband service provider, are permanently located at a civic (street) address, which is known to the network provider.
                        <SU>121</SU>
                        <FTREF/>
                         If a CMRS provider has access to either an estimated civic address or coordinate-based location that represents a horizontal location uncertainty level of the device within a radius of 165 meters at a confidence level of at least 90% and that location is available at time of routing, the CMRS provider must use such information to comply with the Commission's location-based routing rules.
                    </P>
                    <FTNT>
                        <P>
                            <SU>120</SU>
                             NENA NPRM Comments at 3 (arguing that “location-based routing rules should apply equally to geodetic and civic locations known to the originating service provider”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>121</SU>
                             
                            <E T="03">Amending the Definition of Interconnected VoIP Service in Section 9.3 of the Commission's Rules; Wireless E911 Location Accuracy Requirements; E911 Requirements for IP-Enabled Service Providers,</E>
                             GN Docket No. 11-117, PS Docket No. 07-114, WC Docket No. 05-196, Third Report and Order (76 FR 59916, September 28, 2011) and Notice of Proposed Rulemaking and Second Further Notice of Proposed Rulemaking (76 FR 47114, August 4, 2011), 26 FCC Rcd 10074, 10105, para. 92 (2011). Examples of scenarios in which the CMRS provider would have an estimated civic address include a caller connecting to the network using a Wi-Fi access point or femtocell. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Default to Best Available Location Information</HD>
                    <P>85. In the notice of proposed rulemaking, the Commission proposed that when location information does not meet one or both thresholds for accuracy and timeliness under our rules, CMRS and covered text providers would be required to route wireless 911 voice calls and texts to 911 based on the best location information available at the time the call is routed, which may include cell tower coordinates. We adopt this requirement as proposed for CMRS providers' routing of wireless 911 voice calls and RTT communications to 911. We find that this approach allows flexibility for CMRS providers to determine the best available location information for routing when the available location information does not meet the thresholds for timeliness and accuracy.</P>
                    <P>
                        86. Commenters generally support a flexible fallback approach to routing of calls and texts that do not meet the timeliness and accuracy thresholds for location-based routing.
                        <SU>122</SU>
                        <FTREF/>
                         As the Commission stated in the notice of proposed rulemaking, a requirement to default to best available location information is consistent with ATIS-0500039, which assumes that “the fallback for location-based routing should be cell sector routing `for cases wherein no position estimate is available in time to be used for [location-based routing] or the position estimates lack requisite accuracy.' ” This approach is also consistent with current CMRS provider deployments of location-based routing, which default to legacy E911 routing when location does not meet carriers' individually-set thresholds for accuracy and timely availability. For scenarios in which available location information does not meet the accuracy or timeliness thresholds, we believe that the CMRS provider is best suited to make the determination of the location information that is most likely to support accurate call routing. Defaulting to best available location information when preferred location is unavailable is consistent with other Commission rules regarding the provision of location information with 911 calls. In these rules, the Commission requires providers to supply highly precise location information when technically feasible but permits reliance on alternative location information when highly precise location information is not available.
                        <SU>123</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>122</SU>
                             Southern Linc NPRM Reply at 6 (stating that to the extent available location information does not meet the requirements for timeliness or location accuracy for a particular 911 call, CMRS providers are in the best position to determine what kind of location information constitutes the “best available”); CTIA NPRM Comments at 4-5; Verizon NPRM Comments at 4 (“Verizon agrees that network-based routing will remain necessary as a fallback when available location information does not meet the relevant accuracy and confidence/uncertainty threshold. This approach serves 911 callers' needs as a large majority of calls using network-based routing will be as reliable as LBR.”); DISA NPRM Comments at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>123</SU>
                             
                            <E T="03">See, e.g.,</E>
                             47 CFR 9.16(b)(3)(ii) (stating that “an on-premises non-fixed device associated with a multi-line telephone system shall provide to the appropriate PSAP automated dispatchable location, when technically feasible; otherwise, it shall provide dispatchable location based on end user manual update, or alternative location as defined in § 9.3”).
                        </P>
                    </FTNT>
                    <P>
                        87. Some commenters argue that CMRS providers should be required to use tower-based routing when the device-based location information available to the network at the time of routing exceeds the threshold,
                        <SU>124</SU>
                        <FTREF/>
                         or that the Commission should limit tower-based routing to scenarios in which “no other option exists.” We agree with CTIA and iCERT that location information that is less accurate than the proposed accuracy threshold but more accurate than cell sector, for example, device-based location information that arrives at the network in time for routing but exceeds the 165-meter threshold, could still enhance the 
                        <PRTPAGE P="18507"/>
                        likelihood of routing the call to the appropriate PSAP, and the rules we adopt allow the use of such information for routing if it is the best available.
                    </P>
                    <FTNT>
                        <P>
                            <SU>124</SU>
                             Intrado NPRM Comments at 5 (“Intrado recommends that when the location information does not meet these timing/accuracy specifications, the proposed rules require fallback to tower-based routing rather than best available location information consistent with current CMRS deployments of LBR and industry standards.”); NASNA NPRM Comments at 12; COPUC NPRM Comments at 6.
                        </P>
                    </FTNT>
                    <P>
                        88. We make minor modifications to the rule to clarify that the “best available location information” to the network at time of routing may take several forms. In the notice of proposed rulemaking, the proposed rule stated that best available location information “
                        <E T="03">may</E>
                         include the latitude/longitude of the cell tower.” We emphasize that the Commission used the latitude/longitude of the cell tower only as an illustrative example and that this language was not intended to limit CMRS providers to only using cell tower coordinates as a default or fallback. Southern Linc states that the most effective way to minimize misroutes is to enable CMRS providers to route calls based on the best location information available at the time of the call, regardless of the technology or solution. We agree. NENA states that the most appropriate geodetic location for each sector would be the centroid of the area served by each cell sector, instead of the coordinates of the cell tower. We revise the proposed rule language to indicate that when information of a device's location does not meet either one or both requirements for timeliness and accuracy, CMRS providers must route the wireless 911 voice calls or RTT communications to 911 based on the best available location information, which may include, but is not limited to, device-based location information that does not meet the timeliness and accuracy requirements, the centroid of the cell sector that first picks up the call, or other location information.
                    </P>
                    <HD SOURCE="HD3">d. Validation</HD>
                    <P>
                        89. In the notice of proposed rulemaking, the Commission sought comment on whether to require validation of location information for wireless 911 voice calls and texts to 911 for purposes of location-based routing and, if so, what validation steps CMRS and covered text providers should be required to take. Some commenters support validation, citing concerns that 911 calls can be spoofed or purposefully misrouted for swatting incidents. However, AT&amp;T states that in its experience, invalid location under location-based routing is “extremely rare.” BRETSA contends that requiring validation would be counterproductive because “[v]alidating caller/device locations against cell-site (Phase I) location would appear to defeat the purpose of device-based LBR.” 
                        <SU>125</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>125</SU>
                             BRETSA NPRM Reply at 10. BRETSA states that “[r]eference to the tower location for verification would simply invalidate the caller location in those cases in which the caller is located in a jurisdiction other than that in which the PSAP to which 9-1-1 calls received by the cell site are default routed. It would result in the very misrouting of the call LBR is being implemented to correct.” 
                            <E T="03">Id.</E>
                             at 11.
                        </P>
                    </FTNT>
                    <P>
                        90. We decline to implement a validation requirement for the location information used by CMRS providers for routing at this time, as validation protocols are still evolving.
                        <SU>126</SU>
                        <FTREF/>
                         We will continue to monitor location information validation and will consider validation requirements for CMRS providers if such requirements become necessary. To aid in this monitoring, in the certification and reporting requirements discussed herein, we adopt requirements for CMRS to collect and report information on validation procedures they use with location-based routing.
                    </P>
                    <FTNT>
                        <P>
                            <SU>126</SU>
                             Most commenters who address the issue oppose a validation requirement. 
                            <E T="03">See, e.g.,</E>
                             AT&amp;T NPRM Comments at 4-5; T-Mobile NPRM Comments at 10; T-Mobile NPRM Reply at 4; Verizon NPRM Comments at 4; Verizon NPRM Reply at 2; ATIS NPRM Comments at 4-5; BRETSA NPRM Reply at i, 10-11.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. Delivery of Wireless 911 Calls and Texts to NG911 Networks</HD>
                    <P>
                        91. In the notice of proposed rulemaking, the Commission proposed requiring CMRS and covered text providers to deliver 911 calls, texts, and associated routing information in IP format upon request of 911 authorities who have established the capability to accept NG911-compatible IP-based 911 communications. In the subsequent NG911 Notice of Proposed Rulemaking, the Commission proposed similar requirements for wireline, interconnected VoIP, and internet-based TRS providers. Several commenters express support for addressing IP delivery requirements for CMRS and covered text providers as part of a consolidated NG911 proceeding.
                        <SU>127</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>127</SU>
                             CTIA July 3, 2023 
                            <E T="03">Ex Parte</E>
                             at 2; Intrado NPRM Comments at 2, 5-6; Texas 9-1-1 Entities NPRM Comments at 5-6 n.21; NENA NPRM Reply at 5 (“NENA supports Intrado's request to initiate an NG9-1-1 proceeding to refresh the record on NG9-1-1.”); Verizon NPRM Reply at 5 (“[C]oupling LBR with a framework for i3-based NG911 implementation would promote more efficient deployment by minimizing redundant implementation of interim and i3 NG911-based LBR while also rewarding wireless providers that have diligently worked to support end-to-end i3-based NG911.”); 
                            <E T="03">see also</E>
                             GCI July 17, 2023 
                            <E T="03">Ex Parte</E>
                             at 1 (“[A]ddressing any new requirements for IP delivery of wireless calls to PSAPs as part of the FCC's larger NG911 proceeding will facilitate consistent rules across network types and will make compliance with any new rules more efficient and effective for all service providers.”); Alaska Telecom Association NPRM Comments at 8-9 (rec. Aug. 9, 2023) (filed in both PS Dockets 21-497 and 18-64) (“[T]he FCC should address and align any new requirements for IP delivery of wireless calls to PSAPs proposed in the LBR proceeding (PS Docket No. 18-64) with any IP-delivery requirements adopted in this NG911 proceeding.”).
                        </P>
                    </FTNT>
                    <P>
                        92. We agree that consolidating similar issues and aligning requirements for NG911 services across different types of originating service providers will result in more consistent rules and avoid confusion among stakeholders. Accordingly, we defer consideration of IP delivery for CMRS and covered text providers, including all associated proposals and issues raised in the notice of proposed rulemaking, to the NG911 transition proceeding, PS Docket No. 21-479. We acknowledge the comments in the record of this proceeding regarding the Commission's proposals on this issue, and we will address those comments in the NG911 proceeding.
                        <SU>128</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>128</SU>
                             Commenters who filed comments on this issue in the docket for this proceeding (PS Docket No. 18-64) do not need to re-file their comments in PS Docket No. 21-479.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">C. Certification and Reporting Requirements</HD>
                    <P>93. Certification and Reporting Requirements. In the notice of proposed rulemaking, the Commission sought comment on whether it should implement any new data collections to assist in monitoring compliance with the proposed location-based routing rules. The Commission also sought comment on what information providers should include and how frequently they should be required to report. In addition, the Commission asked whether it should require providers to certify that they are in compliance with requirements for location-based routing.</P>
                    <P>
                        94. NASNA and COPUC support an information collection to assess compliance and implementation of location-based routing. To help the Commission monitor compliance with the location-based routing requirements we adopt, we adopt certain one-time certification and reporting requirements. Specifically, we require that within sixty days after CMRS providers' respective compliance deadlines, they must certify that they are in compliance with the location-based routing requirements applicable to them. As part of the certification, CMRS providers must substantiate compliance by identifying specific network architecture, systems, location validation,
                        <SU>129</SU>
                        <FTREF/>
                         and procedures used to comply with the location-based routing requirements. We also require CMRS providers on a one-time basis to collect and report aggregate data on the routing technologies used for live 911 calls in 
                        <PRTPAGE P="18508"/>
                        the locations specified for live 911 call location data in § 9.10(i)(3)(ii) of the Commission's rules. CMRS providers must collect these data for a thirty-day period beginning on the applicable compliance date.
                    </P>
                    <FTNT>
                        <P>
                            <SU>129</SU>
                             As we discuss herein, we do not require validation of location information used for location-based routing. However, if providers perform any validation of routing location data, they should identify such practices as part of their certification.
                        </P>
                    </FTNT>
                    <P>
                        95. CTIA requests that we establish a “presumption of confidentiality from disclosure of detailed network information” that is required to be included in the certifications outlined in the Report and Order. In support of its request, CTIA states that “wireless providers customarily treat network information as confidential for competitive and security reasons” and cites to a proceeding in which the Commission concluded that outage reports should be routinely treated as confidential information and are presumptively protected from public disclosure under the Freedom of Information Act. Based on the current state of the record, we decline to establish a presumption of confidentiality for the one-time certification and reporting requirements adopted in the Report and Order. CMRS providers may request confidential treatment under the Commission's existing confidentiality rules 
                        <SU>130</SU>
                        <FTREF/>
                         for materials submitted pursuant to these new requirements, specifying the information they wish to keep confidential and providing the required justification. We note that the Commission retains the right to release aggregated or anonymized data that would not reveal specific information for which confidential treatment has been sought, including doing so on its website, in order to facilitate transparency and compliance with the rules. In addition, nothing in this document or the Report and Order is intended to limit the authority of state and local 911 agencies to publish 911 call data to the extent authorized under state or local law.
                    </P>
                    <FTNT>
                        <P>
                            <SU>130</SU>
                             
                            <E T="03">See</E>
                             47 CFR 0.459.
                        </P>
                    </FTNT>
                    <P>96. CTIA requests that the Commission permit providers to submit certifications in the public docket “while separately allowing providers to submit the required network information and live call data directly to Commission staff.” We direct the Public Safety and Homeland Security Bureau to issue a Public Notice prior to the deadline for nationwide CMRS providers to file compliance certifications and live call data. Such a Public Notice will include necessary instructions for CMRS providers to file certifications and reports in compliance with the requirements adopted.</P>
                    <P>97. CMRS providers must file the required certifications and live call data within 60 days after the compliance deadlines applicable to them under the location-based routing rules. This means that for voice calls to 911, a nationwide CMRS provider must file its certification and live call data within 60 days after the six-month deadline for deploying location-based routing technology on its IP-based networks, and a non-nationwide CMRS provider must file its certification and live call within 60 days after the 24-month deadline for deploying location-based routing technology on its IP-based networks. In addition, all CMRS providers that have implemented the capability for RTT communications to 911 must file a certification within 60 days after the 24-month deadline for deploying a technology that supports location-based routing for RTT communications. We do not require live call data reporting for RTT communications to 911.</P>
                    <P>
                        98. Under the one-time reporting requirement for live 911 calls, CMRS providers must collect and report on (1) the number and percentage of wireless 911 voice calls routed with device-based location information that meets the accuracy threshold we adopt (
                        <E T="03">i.e.,</E>
                         within a radius of 165 meters or less at a confidence level of at least 90%); (2) the number and percentage of wireless 911 voice calls routed with device-based location information that exceeds that threshold (
                        <E T="03">i.e.,</E>
                         within a radius larger than 165 meters at a confidence level of 90%); and (3) the number and percentage of wireless 911 voice calls routed by tower-based routing. We believe that this information will help us evaluate each CMRS provider's deployment of location-based routing. We also encourage but do not require CMRS providers to include the number of device-based location results being discarded as invalid in their reports filed with the FCC. To minimize the reporting burden on CMRS providers, we require them to collect and report on 911 routing methods for live 911 voice calls only once, only for the areas specified for live 911 call location data in § 9.10(i)(3)(ii) of the rules,
                        <SU>131</SU>
                        <FTREF/>
                         and only for a thirty-day period following specified compliance dates. As noted above, we do not require similar reporting for RTT communications to 911.
                    </P>
                    <FTNT>
                        <P>
                            <SU>131</SU>
                             CMRS providers providing service in any of the Test Cities or portions thereof must collect and report aggregate data on the location technologies used for live 911 calls in those areas. 47 CFR 9.10(i)(3)(ii). Non-nationwide CMRS providers are required to report from alternative areas as specified in 47 CFR 9.10(i)(3)(ii)(D) and (E).
                        </P>
                    </FTNT>
                    <P>99. We believe that these limited data collections strike an appropriate balance between the public safety community's interest in greater transparency with respect to compliance and our goal of limiting the burden of responding to mandatory information collections, particularly for small entities. These limited information collections will promote transparency by ensuring that the public has a clear understanding of timelines for providers' implementations of location-based routing technology and the level of compliance with location-based routing rules. Moreover, they will promote accountability by requiring CMRS providers to show steps they are taking to ensure that wireless 911 voice calls and RTT communications to 911 are routed to the appropriate PSAP.</P>
                    <P>
                        100. 
                        <E T="03">Recurring Reporting Requirements.</E>
                         The Commission also sought comment on whether it should adopt recurring or ongoing reporting requirements. NASNA and COPUC support requiring CMRS providers to disclose on a recurring basis to the FCC how many 911 calls are routed by location-based routing and how many are routed using legacy E911 call routing. NASNA and COPUC argue that “[t]his will allow the Commission to determine if certain carriers are resorting to default routing more frequently than others, which may prompt an investigation to determine if those carriers are making sufficient efforts to fully implement LBR.” RWA opposes recurring data collection and reporting requirements as “extremely burdensome” for small providers, although it suggests that the Commission could request performance data on a voluntary basis. We believe that the one-time certification and reporting requirements we adopt will be sufficient for providers to demonstrate location-based routing implementation without posing an undue burden for providers, particularly small entities. Therefore, we decline to adopt ongoing reporting requirements.
                    </P>
                    <P>
                        101. Privacy and Security. The Electronic Privacy Information Center (EPIC) expresses concern about potential misuse of emergency location data and urges the Commission to clarify that the privacy and security requirements for dispatchable location and z-axis location data also apply to location-based routing data.
                        <SU>132</SU>
                        <FTREF/>
                         EPIC also 
                        <PRTPAGE P="18509"/>
                        urges the Commission to clarify the data use cases that fall within the scope of “911 purposes” and to allow the use of such data only for routing calls and dispatch assistance. In particular, EPIC urges the Commission “to clarify that law enforcement cannot use 911 location data for investigative leads or for enforcement unrelated to the purpose of the 911 call.” EPIC also asks the Commission to clarify that carriers are responsible for their third-party vendors' collection, use, and disclosure of device-based location data.
                        <SU>133</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>132</SU>
                             
                            <E T="03">See</E>
                             Electronic Privacy Information Center (EPIC) Notice of Proposed Rulemaking Comments at 6-7 (rec. Feb. 16, 2023) (EPIC NPRM Comments). The Commission's data privacy and security requirements for dispatchable location and z-axis location information provide that prior to use of dispatchable location information or z-axis location information, respectively, to meet the location accuracy requirements, CMRS providers must certify that neither they nor any third party they rely on to obtain such location information will use 
                            <PRTPAGE/>
                            such location information or associated data for any non-911 purpose, except with prior express consent or as otherwise required by law. 47 CFR 9.10(i)(4)(iv) and (v). The certification must state that CMRS providers and any third party they rely on to obtain such location information will implement measures sufficient to safeguard the privacy and security of such location information. 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>133</SU>
                             EPIC NPRM Comments at 7. EPIC states that “[t]he location data market is a multi-billion-dollar industry. Like many other companies that collect location data, carriers have sold their customers' information to data brokers who have then sold access to anyone willing to buy—from bounty hunters to the government. The disclosure and sale of location data has serious implications for equity because vulnerable people are most likely to be the targets of surveillance.” 
                            <E T="03">Id.</E>
                             at 3 (footnotes omitted).
                        </P>
                    </FTNT>
                    <P>
                        102. We agree that it is imperative for service providers to ensure the privacy and security of location-based routing information, and we adopt a rule clarifying that the Commission's existing rules on the privacy and security of dispatchable location and z-axis information apply to information used for location-based routing. In particular, we require CMRS providers to certify that neither they nor any third party they rely on to obtain location information or associated data used for compliance with the location-based routing requirements will use such information or associated data for any non-911 purpose, except with prior express consent or as otherwise required by law. The certification also must state that the CMRS providers and any third parties they rely on to obtain location information or associated data used for compliance with the location-based routing requirements have implemented measures sufficient to safeguard the privacy and security of such information.
                        <SU>134</SU>
                        <FTREF/>
                         These requirements make clear that CMRS providers who work with third-party vendors in the context of location-based routing are responsible for ensuring that those vendors take appropriate measures to address privacy and security concerns.
                        <SU>135</SU>
                        <FTREF/>
                         The privacy and security certifications are due at the same time as the other location-based routing certifications (
                        <E T="03">i.e.,</E>
                         within 60 days after the compliance deadlines applicable to the CMRS providers under the location-based routing rules).
                    </P>
                    <FTNT>
                        <P>
                            <SU>134</SU>
                             Under the definition we adopt, location information used for location-based routing may include, but is not limited to, device-based location information.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>135</SU>
                             
                            <E T="03">Wireless E911 Location Accuracy Requirements,</E>
                             PS Docket No. 07-114, Sixth Report and Order and Order on Reconsideration, 35 FCC Rcd 7752, 7777, at para. 57 (2020), 85 FR 53234 (August 28, 2020).
                        </P>
                    </FTNT>
                    <P>
                        103. EPIC also asks the Commission to clarify how its privacy and security rules, including those governing using, disclosing, and permitting access to Customer Proprietary Network Information (CPNI), apply to device-based location data.
                        <SU>136</SU>
                        <FTREF/>
                         Section 222 of the Communications Act of 1934, as amended, requires CMRS providers, among others, to protect the confidentiality of location information and prohibits them from using, disclosing, or permitting access to location information without the customer's express prior authorization, but provides an exception for the provision of a customer's call location information to a PSAP or other emergency response authority in connection with a 911 call.
                        <SU>137</SU>
                        <FTREF/>
                         To help remove uncertainty for CMRS providers, we clarify that the obligations that apply to dispatchable location data also apply to location information used for location-based routing, including device-based location data.
                    </P>
                    <FTNT>
                        <P>
                            <SU>136</SU>
                             
                            <E T="03">See</E>
                             EPIC NPRM Comments at 5-6. The Commission's privacy rules, including those governing the use, disclosure, and access to CPNI, are at 47 CFR 64.2001 through 64.2011.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>137</SU>
                             47 U.S.C. 222(d)(4)(A).
                        </P>
                    </FTNT>
                    <P>104. We decline EPIC's request to clarify the definition of “911 purposes.” We believe that the Commission's existing privacy protections for 911 location data are sufficiently clear, and that determining whether a particular use of location data is for “911 purposes” is likely to be a fact-specific inquiry best addressed on a case-by-case basis as the need arises. We decline to address the issue of law enforcement's ability to use 911 location data for investigative or law enforcement purposes, as this is an area outside the Commission's regulatory authority. We also decline EPIC's request to require CMRS and covered text providers to delete location data as outside the scope of this proceeding, as the notice of proposed rulemaking did not propose or seek comment on requirements for data minimization. We recognize data minimization as an important tool to protect the privacy and security of customers' information, and we encourage providers not to retain 911 location routing data longer than is necessary to fulfill the 911 purpose of the data or comply with applicable law.</P>
                    <P>
                        105. Per-Call Disclosure Requirements. The Commission sought comment on whether to require CMRS providers to disclose to PSAPs or state or local 911 authorities the routing methodology used for each 911 call, although the Commission declined to propose such a requirement. COPUC and BRETSA urge the Commission to require per-call disclosure. COPUC states that “[n]ot knowing whether the call was routed using LBR technology or default E911 methodology, the PSAP will have to follow up on 
                        <E T="03">every</E>
                         misrouted call to determine the cause of the misroute.” 
                        <SU>138</SU>
                        <FTREF/>
                         BRETSA states that routing methodology information can allow dispatchers to assess the likelihood that they need to transfer the call and the reliability of the caller location information. However, T-Mobile and NENA argue that such a requirement is unnecessary.
                        <SU>139</SU>
                        <FTREF/>
                         T-Mobile asserts that the positioning technology used to route each call is not actionable for PSAPs and that in a full NG911 environment, positioning technology information will be available with each call. NENA similarly states that NG911 system elements already “partly” meet the need for per-call information on routing mechanisms and that additional standards development is under way and should meet this need “in full.” In light of the forthcoming development of NG911 standards that will support disclosure of per-call routing methodology, we agree with T-Mobile and NENA that any incremental benefit from requiring such disclosures at this time would not outweigh the potential costs of this requirement.
                    </P>
                    <FTNT>
                        <P>
                            <SU>138</SU>
                             COPUC NPRM Comments at 7 (also stating that if a call “was routed using LBR and still was delivered to the wrong PSAP, that indicates the possibility of an error in the GIS [geographic information system] dataset being used by the CMRS provider to determine the proper destination for the 911 call”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>139</SU>
                             AT&amp;T NPRM Comments at 5; T-Mobile NPRM Comments at 8; T-Mobile NPRM Reply at 5-6; NENA NPRM Comments at 6 (stating that standards under development make such disclosure requirements unnecessary, but also stating that “[i]t is imperative that the positioning source for the 9-1-1 caller is provided with the call”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">D. Additional Proposals</HD>
                    <P>106. Several commenters raised additional issues or proposals in response to the notice of proposed rulemaking. We discuss each of these issues or proposals in turn below.</P>
                    <P>
                        107. Role of Next Generation Core Services (NGCS) Providers. NENA and T-Mobile indicate that the proposals in the notice of proposed rulemaking 
                        <PRTPAGE P="18510"/>
                        regarding routing obligations and ESInets may leave a regulatory gap with respect to routing functions performed by ESInet administrators and next generation core services (NGCS) providers.
                        <SU>140</SU>
                        <FTREF/>
                         T-Mobile notes that once a carrier hands the 911 call over to the NGCS provider at the ESInet ingress point, the carrier cannot control how the call is routed, and the notice of proposed rulemaking “does not contemplate that the NGCS provider is 
                        <E T="03">also</E>
                         required to use LBR when routing to the appropriate PSAP.” T-Mobile urges the Commission to ensure that carriers do not “bear the burden of noncompliance” after the carrier routes the 911 call to ESInets. Because the Commission only considered requirements for CMRS and covered text providers in the notice of proposed rulemaking, we decline to consider the role of NGCS providers in routing at this time and defer to the NG911 transition proceeding in PS Docket No. 21-479 the consideration of NGCS providers' responsibilities with regard to location-based routing and any related liabilities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>140</SU>
                             NENA NPRM Comments at 11 (“Under the proposal to establish an ESInet as a termination point for location, there may exist a gap in regulatory coverage. There may be a need to apply regulatory coverage to ESInet providers to ensure that calls and location are delivered through the ESInet all the way to the PSAP.”); T-Mobile NPRM Comments at 7 (asserting that there is a gap in the NPRM with respect to routing obligations for calls delivered to an ESInet and that “[t]his raises the question of where the burden of compliance rests if a call is misrouted in this scenario”).
                        </P>
                    </FTNT>
                    <P>108. 2019 Wireline Forbearance Memorandum Opinion and Order. We received a comment from Mr. Ronald R. Fenwick urging the Commission to revisit and revise a 2019 Memorandum Opinion and Order in another proceeding which granted price cap incumbent Local Exchange Carriers (LECs) forbearance from legacy regulatory obligations. Mr. Fenwick asserts that the Memorandum Opinion and Order resulted in diminishing subscribers to traditional landline services, and that wireless customers are not properly apprised of the advantages of wireline service. We decline to revisit the 2019 Memorandum Opinion and Order, which does not deal with wireless services and is therefore outside the scope of this proceeding.</P>
                    <P>109. Calls and Texts Originating Outside the United States. We received a comment from staff of the Defense Information Systems Agency (DISA) asking the Commission to consider location-based routing for 911 calls and texts originating outside the United States and its territories. This request raises legal and policy issues that are beyond the scope of this proceeding.</P>
                    <P>110. Location-Based Routing for VoIP. We received a comment from DISA asking the Commission to apply location-based routing requirements to “landline-based VoIP 9-1-1 calls coming from Ethernet wired end instruments and connecting to the Public Switch Telephone Network using Session Initiation Protocol (SIP) trunks from an IP-PBX.” We note that in the Next Generation 911 proceeding (PS Docket 21-479), the Commission proposed rules (NG911 Notice of Proposed Rulemaking) requiring interconnected VoIP providers to complete all translation necessary to deliver 911 calls, including associated location information, in the requested IP-based format to an ESInet or other designated point(s) that allow emergency calls to be answered. We defer consideration of this issue to the Next Generation 911 proceeding.</P>
                    <HD SOURCE="HD2">E. Promoting Digital Equity and Inclusion</HD>
                    <P>
                        111. As noted in the notice of proposed rulemaking, the Commission is engaged in a continuing effort to advance digital equity for all,
                        <SU>141</SU>
                        <FTREF/>
                         including people of color, persons with disabilities, persons who live in rural or Tribal areas, and others who are or have been historically underserved, marginalized, or adversely affected by persistent poverty or inequality.
                        <SU>142</SU>
                        <FTREF/>
                         The notice of proposed rulemaking invited comment on equity-related considerations and benefits, if any, that may be associated with the proposals and issues under consideration. Specifically, the Commission sought comment on how its proposals may promote or inhibit advances in diversity, equity, inclusion, and accessibility.
                    </P>
                    <FTNT>
                        <P>
                            <SU>141</SU>
                             Section 1 of the Communications Act of 1934 as amended provides that the FCC “regulat[es] interstate and foreign commerce in communication by wire and radio so as to make [such service] available, so far as possible, to all the people of the United States, without discrimination on the basis of race, color, religion, national origin, or sex.” 47 U.S.C. 151.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>142</SU>
                             Notice of Proposed Rulemaking, 37 FCC Rcd at 15205-06, para. 59. The term “equity” is used here consistent with Executive Order 13985 as the consistent and systematic fair, just, and impartial treatment of all individuals, including individuals who belong to underserved communities that have been denied such treatment, such as Black, Latino, and Indigenous and Native American persons, Asian Americans and Pacific Islanders and other persons of color; members of religious minorities; lesbian, gay, bisexual, transgender, and queer (LGBTQ+) persons; persons with disabilities; persons who live in rural areas; and persons otherwise adversely affected by persistent poverty or inequality. 
                            <E T="03">See</E>
                             E.O. 13985, 86 FR 7009, Executive Order on Advancing Racial Equity and Support for Underserved Communities Through the Federal Government (Jan. 20, 2021).
                        </P>
                    </FTNT>
                    <P>112. Several parties submitted comments on these issues. NENA states that location-based routing should be deployed regardless of a jurisdiction's NG911 status and that “[i]t would be inequitable to restrict the life-saving benefits of location-based routing” only to those “with the good fortune of having an emergency in a convenient location” with NG911 capability. As discussed herein, we adopt rules that require CMRS providers to implement location-based routing on their IP-based networks for wireless 911 voice calls nationwide, regardless of whether a particular jurisdiction has NG911 capability. These rules will help to ensure that location-based routing is available for wireless 911 voice calls nationwide and regardless of the service provider the caller has chosen.</P>
                    <P>113. NASNA notes that in the notice of proposed rulemaking, the Commission sought comment not just on equity-related considerations, but also “on the degree to which funding and operating transitional facilities extend the timeline and add to the cost incurred by state and local 911 authorities to transition to NG911.” NASNA believes that “these two issues are inextricably linked,” and NASNA raises “the issues facing our members in providing equal access to 911 services to all citizens through local NG911 systems.” Pointing to the NG911 Notice of Proposed Rulemaking comment record as well, NASNA urges that “the equity-access consideration for 911 at this point in time should begin at the network level in which 911 calls themselves are transported.” NASNA states, “If all those calling or texting 911 do not have a consistent level of access to network functionality, we believe the gap in digital disparity in effective and reliable access to 911 across the country will widen all the more.” Because NASNA's comments regarding equity and access are more closely related to the NG911 proceeding than the instant proceeding, we defer consideration of these points to the NG911 proceeding.</P>
                    <P>
                        114. COPUC advocates for applying the same implementation time frames for 911 texts that are being applied to wireless 911 voice calls (
                        <E T="03">i.e.,</E>
                         six months for nationwide CMRS providers and eighteen months for non-nationwide CMRS providers) as “a matter of equity for 911 users that rely on text-to-911.” 
                        <SU>143</SU>
                        <FTREF/>
                         As discussed herein, at this 
                        <PRTPAGE P="18511"/>
                        time we decline to require location-based routing for text-to-911 services other than RTT communications to 911 in the absence of technical standards for location-based routing for SMS. However, we reiterate our commitment to monitoring the development of standards, products, and other advances affecting location-based routing for SMS text-to-911.
                    </P>
                    <FTNT>
                        <P>
                            <SU>143</SU>
                             COPUC NPRM Comments at 8; 
                            <E T="03">see also</E>
                             NENA NPRM Reply at 9 (concurring with NASNA's equity comments on supporting location-based routing for text-to-911, but arguing that the Commission's rules “should not back the market into adopting non-standardized technologies for a legacy platform” 
                            <PRTPAGE/>
                            and encouraging only voluntary deployment of location-based routing for “interim” text-to-911).
                        </P>
                    </FTNT>
                    <P>
                        115. EPIC states that government entities, carriers, and others have misused location data to target individuals and groups, and says that “the lack of clear privacy and security safeguards would have a disproportionately negative impact on certain vulnerable groups.” 
                        <SU>144</SU>
                        <FTREF/>
                         As discussed herein and consistent with certain of EPIC's requests, we adopt a requirement applying the Commission's existing rules on the privacy and security of dispatchable location and z-axis information to location-based routing information.
                    </P>
                    <FTNT>
                        <P>
                            <SU>144</SU>
                             EPIC NPRM Comments at 1; 
                            <E T="03">see id.</E>
                             at 2, 8 (noting that Microsoft also raised similar privacy and security concerns in earlier comments in the instant proceeding).
                        </P>
                    </FTNT>
                    <P>116. In sum, we acknowledge the importance of the continuing effort to advance digital equity for all. We believe that the rules we adopt, requiring CMRS providers to implement location-based routing on their IP-based networks for wireless 911 voice calls nationwide and requiring CMRS providers to implement location-based routing where they deploy RTT capabilities, will help to advance those goals.</P>
                    <HD SOURCE="HD2">F. Summary of Benefits and Costs for Location-Based Routing</HD>
                    <P>117. As we discuss below, the implementation of location-based routing has potential annual benefits of over $173 billion in terms of reduced mortality and reduced call transfer burdens to PSAPs. We determine that the rules we adopt, which will affect CMRS providers, will result in an industry-wide compliance cost of $215 million.</P>
                    <HD SOURCE="HD3">1. Benefits of Location-Based Routing</HD>
                    <P>
                        118. We believe that the Commission's benefit assessment from the notice of proposed rulemaking remains valid. The Commission estimated that implementation of location-based routing would save 13,837 lives annually. While the Commission did not attempt to place a value on human life, it relied on the U.S. Department of Transportation's (DOT) valuation of a statistical life (VSL) of $11.8 million from base year 2021.
                        <SU>145</SU>
                        <FTREF/>
                         The Commission estimated that the benefit of reduced mortality would be 13,837 × $11.8 million or approximately $163 billion, but stated that this estimate was conservative.
                        <SU>146</SU>
                        <FTREF/>
                         We received no comments on the estimated reduced mortality benefit. Using the latest VSL of $12.5 million for base year 2022,
                        <SU>147</SU>
                        <FTREF/>
                         our new estimate of reduced mortality benefit is approximately $173 billion for wireless voice calls to 911. At this time, we have no data on the number of RTT communications to 911 to estimate a benefit from this service,
                        <SU>148</SU>
                        <FTREF/>
                         but we anticipate that as RTT usage becomes more widespread, significant reduced mortality benefits will accrue.
                    </P>
                    <FTNT>
                        <P>
                            <SU>145</SU>
                             Notice of Proposed Rulemaking, 37 FCC Rcd at 15207-08, para. 62 &amp; n.162 (citing U.S. Department of Transportation, 
                            <E T="03">Departmental Guidance on Valuation of a Statistical Life in Economic Analysis</E>
                             (Mar. 4, 2022) (later updated May 1, 2023), 
                            <E T="03">https://www.transportation.gov/office-policy/transportation-policy/revised-departmental-guidance-on-valuation-of-a-statistical-life-in-economic-analysis</E>
                            ).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>146</SU>
                             Notice of Proposed Rulemaking, 37 FCC Rcd at 15207-08, para. 62 (stating that the estimate does not include “the value of reduced human suffering and property destruction occurring due to a delayed arrival of first responders” or “the benefits of location-based routing for text messages”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>147</SU>
                             
                            <E T="03">See</E>
                             U.S. Department of Transportation, Departmental Guidance on Valuation of a Statistical Life in Economic Analysis (effective May 1, 2023), 
                            <E T="03">https://www.transportation.gov/office-policy/transportation-policy/revised-departmental-guidance-on-valuation-of-a-statistical-life-in-economic-analysis.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>148</SU>
                             Respondents reported a combined total of 824,609 texts to 911 in 2022. Fifteenth Annual 911 Fee Report at 12-13, para. 14.
                        </P>
                    </FTNT>
                    <P>
                        119. The Commission sought specificity on the time and cost savings to PSAPs and state and local 911 authorities under the proposed rules. While we received no specific figures in the record, BRETSA agrees that misrouting of 911 calls ties up resources at the PSAP to which the call was misrouted and delays receipt of the call at the PSAP that can dispatch first responders, while T-Mobile states that call transfers can delay emergency response and result in the loss of vital incident information, including caller location. The Commission estimated that with implementation of location-based routing, “1,368,000 calls would avoid the need for a transfer due to a misroute, reducing the response time for these calls by one minute.” 
                        <SU>149</SU>
                        <FTREF/>
                         This would result in a time savings of 22,800 hours annually for PSAPs, although NENA estimates that call transfers consume over 200,000 hours per year of excess 911 professional labor. We estimate the mean wage of 911 call operators to be $25.04 per hour,
                        <SU>150</SU>
                        <FTREF/>
                         which leads to an estimated total labor cost of $36.31 per hour after accounting for benefits.
                        <SU>151</SU>
                        <FTREF/>
                         We estimate that PSAPs would realize an annual savings benefit range of approximately $0.8 million to $74.3 million per year for wireless 911 voice calls.
                        <SU>152</SU>
                        <FTREF/>
                         We do not have sufficient data to estimate such a benefit for RTT, though we similarly anticipate that time and cost savings benefits for PSAPs will accrue for RTT as usage grows.
                    </P>
                    <FTNT>
                        <P>
                            <SU>149</SU>
                             Notice of Proposed Rulemaking, 37 FCC Rcd at 15206-07, para. 61 n.161. NENA estimates that 80% or more of the total calls to 911 annually are from wireless devices. NENA, 
                            <E T="03">9-1-1 Statistics, https://www.nena.org/page/911Statistics</E>
                             (last visited Jan. 17, 2024). According to the National Association of State Emergency Medical Services Officials (NASEMSO), local Emergency Medical Services (EMS) agencies respond to nearly 28.5 million 911 dispatches each year. NASEMSO (Laura French), 
                            <E T="03">National Association of State EMS Officials releases stats on local agencies, 911 Calls</E>
                             (Apr. 10, 2020), 
                            <E T="03">https://www.ems1.com/ambulance-service/articles/national-association-of-state-ems-officials-releases-stats-on-local-agencies-911-calls-LPQTHJrK2oIpxuR1/</E>
                            . Assuming that 80% of these calls are from wireless devices yields an estimate of 22.8 million wireless calls for 911 dispatch annually. The Commission estimated that 12% of the wireless calls for dispatch (or 2,736,000 calls) would be misrouted. Notice of Proposed Rulemaking, 37 FCC Rcd at 15206-07, para. 61 n.161 (citing 
                            <E T="03">ATIS-0500039</E>
                             at 4). The Commission also estimated that location-based routing with a horizontal uncertainty value of 300 meters would resolve approximately 50% of these misroutes. 
                            <E T="03">Id.</E>
                             (citing 
                            <E T="03">ATIS-0500039</E>
                             at 13). Accordingly, the Commission estimated that 1,368,000 calls would avoid the need for a transfer due to a misroute, reducing the response time for these calls by one minute. 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>150</SU>
                             The mean wage for Public Safety Telecommunicators in May 2022 was $23.74 per hour. U.S. Bureau of Labor Statistics, 
                            <E T="03">Occupational Employment and Wages, May 2022, 43-5031 Public Safety Telecommunicators</E>
                             (Apr. 25, 2023), 
                            <E T="03">https://www.bls.gov/oes/current/oes435031.htm</E>
                            . The average hourly private wage increased by 5.5% according to the Bureau of Labor Statistics between May 2022 and August 2023, so to correct for inflation we increase the wage estimate by 5.5% to $25.04 per hour. Federal Reserve Bank of St. Louis, 
                            <E T="03">Average Hourly Earnings of All Employees, Total Private (CES0500000003), https://fred.stlouisfed.org/series/CES0500000003</E>
                             (last visited Jan. 17, 2024) (
                            <E T="03">Inflation Adjustment</E>
                            ).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>151</SU>
                             To account for benefits, we mark up wages by 45%, which results in total hourly compensation of $25.04 × 145% = $36.31. According to the Bureau of Labor Statistics, as of June 2023, civilian wages and salaries averaged $29.86/hour and benefits averaged $13.39/hour. Total compensation therefore averaged $29.86 + $13.39, rounded to $43.26. 
                            <E T="03">See</E>
                             Press Release, Bureau of Labor Statistics, 
                            <E T="03">Employer Costs for Employee Compensation—June 2023</E>
                             (Sept. 12, 2023), 
                            <E T="03">https://www.bls.gov/news.release/pdf/ecec.pdf</E>
                            . Using these figures, benefits constitute a markup of $13.39/$29.86 ~ 45%.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>152</SU>
                             PSAPs would realize an annual savings benefit of 1,368,000 calls  ×  1 minute (0.0166 hours)  ×  $36.31, or over $828,000 per year. Using NENA's estimate, PSAPs would realize a savings benefit of 200,000 hours  ×  $36.31, or approximately $7.3 million per year.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Costs of Implementation</HD>
                    <P>
                        120. In the notice of proposed rulemaking, the Commission provided separate cost estimates for materials and labor. The Commission sought comment 
                        <PRTPAGE P="18512"/>
                        on, 
                        <E T="03">inter alia,</E>
                         hardware, software, services, GIS, and testing; provider costs and timelines necessary to work with OS-based location providers; costs for providers to implement the required software, hardware, and service upgrades to comply with proposed rules; and how many work-hours and what kind of workers would be required; and planned or expended costs by providers that have implemented or plan to implement location-based routing. RWA and BRETSA state that non-nationwide and smaller carriers have not determined actual costs. We did not receive specific cost information to better inform the Commission's cost assessments. Commenters provided information about network elements, tasks, and burdens that would factor into costs; however, commenters generally discussed such factors in the context of seeking more time to comply rather than cost aspects.
                        <SU>153</SU>
                        <FTREF/>
                         RWA calls for additional time and Federal funding to support carrier implementation of location-based routing and alleges that RWA members will not be able to comply with an unfunded mandate. As discussed herein, we are increasing the timelines for non-nationwide CMRS providers to implement location-based routing for wireless 911 voice calls and RTT communications, and deferring consideration of location-based routing requirements for texts to 911 and requirements to deliver 911 calls and texts in IP-based format.
                    </P>
                    <FTNT>
                        <P>
                            <SU>153</SU>
                             For example, CCA states that location-based routing implementation will be economically and practically infeasible in the proposed eighteen-month timeline for non-nationwide carriers, noting that a nationwide carrier took four years. CCA NPRM Comments at 2.
                        </P>
                    </FTNT>
                    <P>
                        121. Material Costs. The Commission tentatively concluded that CMRS providers implement location-based routing at the PSAP level, while CMRS providers incur material costs on a per-PSAP basis. The Commission estimated that the average material cost of software features or component upgrades for each CMRS provider would be $10,000 per PSAP as an upper bound, with an “implied material cost upper bound [of] approximately $106 million.” 
                        <SU>154</SU>
                        <FTREF/>
                         We received no comments to inform the Commission's material cost estimate for CMRS providers to deploy location-based routing to PSAPs they serve. However, commenters identified core network elements necessary to implement location-based routing. Intrado states that carriers will need to implement geospatial routing capable Gateway Mobile Location Centers (GMLCs) so that routing decisions will occur within their networks.
                        <SU>155</SU>
                        <FTREF/>
                         CCA states that “[i]ncorporating location-based routing into the wireless ecosystem . . . requires a carefully orchestrated series of changes that affects the wireless carriers' device inventory, transport networks, and several aspects of the core network systems. These potentially include access and mobility management, data authentication, geospatial data repository functions, session management, and network security.” CCA further states that carriers will need to “implement the array of device upgrades and non-standard, proprietary network solutions needed for location-based routing.” RWA describes hardware and software modifications needed to implement location-based routing as a “massive expense,” and notes that member budgets for capital expenses are “already pared close to the bone.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>154</SU>
                             Notice of Proposed Rulemaking, 37 FCC Rcd at 15210-11, para. 71. The Commission assumed no material costs for AT&amp;T because it has already deployed location-based routing to its network. 
                            <E T="03">Id.</E>
                             at 15210, para. 71. The Commission stated (at the time of the notice of proposed rulemaking) that it is unclear the extent to which Verizon plans to implement location-based routing, and did not estimate Verizon's material costs. 
                            <E T="03">Id.</E>
                             at 15210-11, para. 71. The Commission found that T-Mobile has yet to implement location-based routing to 4,896 PSAPs, while non-nationwide CMRS providers collectively must upgrade 5,728 PSAPs, with any PSAP receiving service from usually one non-nationwide CMRS provider along with the nationwide CMRS providers. 
                            <E T="03">Id.</E>
                             at 15211, para. 71. The Commission found that T-Mobile and non-nationwide CMRS providers need to implement location-based routing for 10,624 PSAPs (4,896 + 5,728), at $10,000 per PSAP, for a cost of approximately $106 million. 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>155</SU>
                             Intrado NPRM Comments at 3. NENA defines a GMLC as “the point of interface between the GSM [Global Standard for Mobile Communications] wireless network and the Emergency Services Network. The GMLC retrieves, forwards, stores and controls position data associated with wireless callers. This includes the processing of location requests and updates (rebids).” NENA, 
                            <E T="03">GMLC/MLC (Gateway Mobile Location Center)</E>
                             (Sept. 13, 2021), 
                            <E T="03">https://kb.nena.org/wiki/GMLC/MLC_(Gateway_Mobile_Location_Center.</E>
                            )
                        </P>
                    </FTNT>
                    <P>122. We agree with commenters that providers have certain material costs associated with the network core that are not necessarily dependent on the number of PSAPs they serve. We clarify, however, that the material costs that we calculated on a per-PSAP basis in the notice of proposed rulemaking also include other costs that are not necessarily incurred at the PSAP. We agree that implementation costs of upgrading equipment or software can, for instance, involve changes to the network core. We also note that such costs vary with the size of the network that remains to be converted to location-based routing, especially if any equipment needs to be updated. We therefore chose the per-PSAP basis because we find it a convenient proxy of remaining network area. T-Mobile and Verizon report partial implementation of location-based routing based on the number of PSAPs. For providers with no known implementation, the number of their covered PSAPs serves as a proxy for the size of their entire network. We therefore continue to use the per-PSAP basis as a proxy for network size in our current material costs calculations. We note, additionally, that even if the per-PSAP cost that we use below were to double, the aggregate expected costs of our rules would fall well below the expected benefits.</P>
                    <P>
                        123. The latest NENA data indicate that 5,748 PSAPs operate in the United States. AT&amp;T has already deployed location-based routing nationwide, so our rules impose no additional material costs for AT&amp;T. The Commission did not provide an estimate of T-Mobile's material costs in the notice of proposed rulemaking. As of December 2023, T-Mobile states that it has fully implemented location-based routing for 1,591 PSAPs, with an additional 596 PSAPs in progress. Thus, T-Mobile must implement location-based routing to 3,561 remaining PSAPs. The Commission did not provide an estimate of Verizon's material costs in the notice of proposed rulemaking, but Verizon states that it has “fully implemented LBR for 414 PSAPs; implementation is in progress for an additional 277 PSAPs.” Thus, the rules would impose no additional material costs for existing and planned deployments to Verizon for 691 PSAPs, which leaves 5,057 PSAPs remaining for Verizon to implement location-based routing. The remaining CMRS providers collectively must upgrade the full national set of 5,748 PSAPs, assuming no more than one remaining CMRS provider serving a particular PSAP.
                        <SU>156</SU>
                        <FTREF/>
                         Using the Commission's $10,000 per PSAP upper bound in the notice of proposed rulemaking, we estimate that CMRS providers collectively need to deploy location-based routing to a total of 14,366 PSAPs,
                        <SU>157</SU>
                        <FTREF/>
                         resulting in the 
                        <PRTPAGE P="18513"/>
                        implied material cost of approximately $143.7 million.
                    </P>
                    <FTNT>
                        <P>
                            <SU>156</SU>
                             
                            <E T="03">See</E>
                             Notice of Proposed Rulemaking, 37 FCC Rcd at 15211, para. 71 (citing FCC, 
                            <E T="03">Mobile Deployment Form 477 Data</E>
                             (Jul. 29, 2022), 
                            <E T="03">https://www.fcc.gov/mobile-deployment-form-477-data,</E>
                             and stating that “[s]taff analysis of Form 477 data suggests that when that when there is a fourth non-nationwide wireless provider in any particular location, it is usually the only one”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>157</SU>
                             We count 3,561 PSAPs remaining for T-Mobile, 5,057 PSAPs remaining for Verizon, and 5,748 PSAPs for the CMRS providers that have not yet begun to implement location-based routing.
                        </P>
                    </FTNT>
                    <P>
                        124. Labor Costs. The Commission estimated that the labor cost per CMRS provider is $366,600.
                        <SU>158</SU>
                        <FTREF/>
                         The Commission explicitly mentioned the tasks of installing equipment and running trials as part of this labor. Commenters described other tasks such as internal planning, outreach, and testing. Since these tasks do not involve materials but rather involve work burdens, we categorize them as labor costs for the purpose of this analysis.
                    </P>
                    <FTNT>
                        <P>
                            <SU>158</SU>
                             Notice of Proposed Rulemaking, 37 FCC Rcd at 15211-12, para. 72 (estimating that the labor cost of employing software workers would be $35.25 per hour; that the upper bound of the time to implement the upgrades with trials is 6 months (26 weeks), and workers have a forty hour work week, or 1,040 hours per worker; that ten simultaneous workers at a time on average is a generous upper bound, resulting in 10,400 labor hours per CMRS provider; and that the labor cost per CMRS provider is $366,600).
                        </P>
                    </FTNT>
                    <P>
                        125. Labor Costs (i): Internal Planning. CCA described CMRS providers' internal planning tasks prior to implementation of location-based routing, which we categorize under labor. CCA states that carriers will need to vet and select potentially appropriate technical location-based routing solutions, budget for related required procurements, and make related plans to allocate and prioritize necessary resources to the projects.
                        <SU>159</SU>
                        <FTREF/>
                         CCA states that “[t]he proposed rule would require carriers with IP-based networks to make major strategic decisions for their wireless networks” and “stand up project teams [comprised] of senior engineers and business leaders with specialized experience in network operations to assess the needs of the marketplace and review the state of technology development globally, nationally, and with respect to their individual network technologies.” CCA states that carriers will need to make “a candid assessment of existing network resources, the purposeful allocation of limited technical and business resources, and a successful matching of technology within the market to the unique features of that carrier's network systems and status within the product evolution lifecycle” and conduct “intensive” decision making.
                    </P>
                    <FTNT>
                        <P>
                            <SU>159</SU>
                             CCA NPRM Reply at 5. The planning costs CCA cites include “identifying acceptance of the technical implementation.” CCA NPRM Comments at 11.
                        </P>
                    </FTNT>
                    <P>126. Labor Costs (ii): Outreach. Next, CCA described providers' outreach tasks, such as collaboration with network and handset vendors; and work with device makers, technology vendors, and software service providers. However, CCA notes that non-nationwide CMRS providers face challenges attracting attention and assistance from global and national vendors who are more responsive to larger clients.</P>
                    <P>127. Labor Costs (iii): Deployment. Commenters provided few details of labor tasks associated with deployment, including equipment and device installation and upgrades.</P>
                    <P>128. Labor Costs (iv): Testing. Commenters described CMRS providers' testing tasks involved with location-based routing implementation. RWA states that providers will need to “test, modify, [and] perfect” location-based routing solutions. CCA states that AT&amp;T performed extensive lab testing, performance testing, trials at PSAPs, evaluation of results with its vendor Intrado, and additional PSAP testing. CCA states that AT&amp;T “confirm[ed] the metrics, obtain[ed] feedback from the PSAPs, and implement[ed] several proprietary changes.”</P>
                    <P>129. While the notice of proposed rulemaking explicitly mentioned the tasks of installing equipment and running trials as part of its labor calculation, the estimate was not meant to be solely inclusive of all tasks. According to Commission staff experience with typical network upgrades, team members will often work on tasks from multiple of the above categories of internal planning, outreach, deployment, and testing. The notice of proposed rulemaking calculation assumes a large team of ten workers over a period of six months to account for the various phases of labor and shifting tasks amongst workers.</P>
                    <P>
                        130. Absent more specific data in the record on each task category, we rely on the Commission's labor cost estimation methodology per CMRS provider.
                        <SU>160</SU>
                        <FTREF/>
                         To better reflect the wide array of complex tasks, including internal network planning, that would need to be undertaken by highly skilled and senior staff, we will assume a higher wage for the workers than that assumed in the notice of proposed rulemaking because some of the tasks involved will have to be undertaken by senior staff. To the extent that less senior staff would be necessary to complete any of these tasks, we view the wage that we use as conservatively high. Using the Bureau of Labor Statistics 75th percentile wage for network engineers, we assume worker compensation to be $81.29 per hour.
                        <SU>161</SU>
                        <FTREF/>
                         Marking up hourly compensation by 45% to account for benefits results in a total hourly compensation estimate of $117.87. Assuming that work is completed over 26 work-weeks of five, 8 work-hour days, and a team of 10, the aggregate upper bound of work-hours would be 10,400 and the total cost of those work-hours would be $1,225,853. While non-nationwide CMRS providers will have 24 months rather than six to implement location-based routing, smaller CMRS providers have constraints on the number of staff they can assign to any one project. In addition, while non-nationwide CMRS providers may take longer to implement location-based routing, assigning the same amount of work-time as nationwide CMRS providers represents both the spreading out of tasks over a longer period and an overestimate since non-nationwide CMRS providers have much smaller networks. Given that AT&amp;T has already implemented location-based routing, we estimate the labor cost associated with implementation for the networks for the 56 remaining providers, plus T-Mobile and Verizon, to be $71.1 million (≉ $1,225,853 × 58 providers = $71,099,474).
                        <SU>162</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>160</SU>
                             Notice of Proposed Rulemaking, 37 FCC Rcd at 15211-12, para. 72 (estimating that the labor cost of employing software workers would be $35.25 per hour; that the upper bound of the time to implement the upgrades with trials is 6 months (26 weeks), and workers have a forty hour work week, or 1,040 hours per worker; that ten simultaneous workers at a time on average is a generous upper bound, resulting in 10,400 labor hours per CMRS provider; and that the labor cost per CMRS provider is $366,600).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>161</SU>
                             The Bureau of Labor Statistics considers the title “computer network architect” to be synonymous with “network engineer.” U.S. Bureau of Labor Statistics, 
                            <E T="03">Computer Network Architects: What Computer Network Architects Do</E>
                             (Sept. 12, 2023), 
                            <E T="03">https://www.bls.gov/ooh/computer-and-information-technology/computer-network-architects.htm#tab-2</E>
                            . To approximate the wages of senior network engineers, we use the 75th percentile of the hourly wage of computer network architects in May 2022, $77.06 per hour. U.S. Bureau of Labor Statistics, 
                            <E T="03">Occupational Employment and Wages, May 2022, 15-1241 Computer Network Architects</E>
                             (Apr. 25, 2023), 
                            <E T="03">https://www.bls.gov/oes/current/oes151241.htm</E>
                            . After adjusting for wage inflation to August 2023, the wage increases to $81.29 per hour. 
                            <E T="03">See Inflation Adjustment</E>
                            .
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>162</SU>
                             To the extent that T-Mobile and Verizon have already begun implementing location-based routing, this cost may be an overestimate.
                        </P>
                    </FTNT>
                    <P>
                        131. In addition to network costs, several commenters indicate that public safety-grade GIS data or shapefiles that precisely define PSAP boundaries should be developed or provided, though they differ on which parties should be responsible.
                        <SU>163</SU>
                        <FTREF/>
                         We agree with 
                        <PRTPAGE P="18514"/>
                        NENA that it is the responsibility of providers to maintain their own jurisdictional maps. Accordingly, we assign the cost of maps to the providers. We anticipate that map costs will largely be labor to update already existing maps. To come up with a cost ceiling, we assume that every provider will need to update its maps, even though many providers likely have up-to-date maps. We anticipate that updating the map will only entail labor costs for mapping specialists to update maps. In the Supporting Document of Study Area Boundary Data Reporting in Esri Shapefile Format, the Office of Information and Regulatory Affairs estimates that it takes an average of 26 hours for a data scientist to modify a shapefile.
                        <SU>164</SU>
                        <FTREF/>
                         We believe that 26 hours would be an upper bound of the time required for a party to update its maps. Given that the average wage rate is $60.44/hour for data scientists in the telecommunications industry,
                        <SU>165</SU>
                        <FTREF/>
                         with a 45% markup for benefits, we arrive at $87.63 as the hourly compensation rate for a data scientist. We estimate an upper bound for the cost of map updating to be approximately $134,000 (≉ $87.63 per hour × 26 hours × 59 providers = $134,424.42).
                    </P>
                    <FTNT>
                        <P>
                            <SU>163</SU>
                             Intrado NPRM Comments at 3 (suggesting carriers and the PSAPs should develop GIS data); BRETSA NPRM Reply at ii (suggesting state and/or local 911 authorities should develop GIS data); T-Mobile NPRM Comments at 6 (suggesting that PSAPs should provide shapefiles, though some PSAPs may not want to provide shapefiles because they consider such information confidential); 
                            <E T="03">see also</E>
                             CCOA NPRM Reply at 3; CTIA NPRM Reply 
                            <PRTPAGE/>
                            at 3, 6-7 (agreeing with T-Mobile regarding the need for accurate shapefiles of PSAP boundaries).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>164</SU>
                             
                            <E T="03">See</E>
                             Office of Information and Regulatory Affairs, Office of Management and Budget, Executive Office of the President, 2022 Study Area Boundary Data Reporting in Esri Shapefile Format, DA 12-1777 and DA 13-282, Supporting Statement—OMB Control No. 3060-1181, at 5, para. 12 (Feb. 15, 2022), 
                            <E T="03">https://www.reginfo.gov/public/do/PRAViewDocument?ref_nbr=202202-3060-009</E>
                            ; 
                            <E T="03">see also Wireless Emergency Alerts</E>
                            ; 
                            <E T="03">Amendments to Part 11 of the Commission's Rules Regarding the Emergency Alert System,</E>
                             PS Docket Nos. 15-91 and 15-94, Third Report and Order, FCC 23-88, at 37, para. 66 (Oct. 20, 2023).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>165</SU>
                             The mean hourly wage for data scientists in the telecommunications industry in May 2022 is $57.29. U.S. Bureau of Labor Statistics, 
                            <E T="03">May 2022 National Industry-Specific Occupational Employment and Wage Estimates NAICS 517000—Telecommunications</E>
                             (Apr. 25, 2023), 
                            <E T="03">https://www.bls.gov/oes/current/naics4_517000.htm</E>
                            . After adjusting for wage inflation to August 2023, the wage increases to $60.44 per hour. 
                            <E T="03">See Inflation Adjustment</E>
                            .
                        </P>
                    </FTNT>
                    <P>132. In addition, the one-time certification of compliance with our requirements together with the submission of data on call percentages by routing methods will impose a one-time cost on CMRS providers. As this required information should be available to each provider internally, we anticipate work to compile this information to take no longer than a week of five business days. We believe that one network engineer would be sufficient to complete this task in this time frame, resulting in a total provider cost of 40 work-hours. Assuming the same hourly labor cost of network engineers as in the previous cost estimate for network implementation, the total cost of reporting is $280,000 (≉ $117.87 per hour × 40 hours × 59 providers = $278,173.20).</P>
                    <P>133. The Commission sought comment on costs to state and local 911 authorities. Intrado and APCO state that PSAPs will not need to make changes to their networks or call handling systems. We agree. Likewise, because we find that providers must maintain their own jurisdictional maps, we do not recognize any costs for state and local 911 authorities and PSAPs.</P>
                    <P>134. Because we are adopting location-based routing requirements for RTT, we also consider the costs for CMRS providers. Given that CMRS providers process and route RTT communications similarly to voice calls, we assume that CMRS providers' material and labor costs to deploy location-based routing for RTT are included in our cost estimates above. As part of this analysis, we note that as of the release date of the Report and Order, we are aware of only a small number of PSAPs that are receiving RTT communications.</P>
                    <P>135. In sum, we estimate upper bounds of the costs that CMRS providers will bear to be material costs of $143.7 million, network implementation costs of $71.1 million, GIS costs of $134,000, and certification costs of $280,000. Altogether, the upper bound of costs is approximately $215 million. However, we underscore that this cost is far outweighed by the benefits of over $173 billion in terms of reduced mortality and call transfer time eliminated.</P>
                    <HD SOURCE="HD1">II. Procedural Matters</HD>
                    <P>
                        136. 
                        <E T="03">Regulatory Flexibility Act.</E>
                         The Regulatory Flexibility Act of 1980, as amended (RFA),
                        <SU>166</SU>
                        <FTREF/>
                         requires that an agency prepare a regulatory flexibility analysis for notice and comment rulemakings, unless the agency certifies that “the rule will not, if promulgated, have a significant economic impact on a substantial number of small entities.” 
                        <SU>167</SU>
                        <FTREF/>
                         Accordingly, we have prepared a Final Regulatory Flexibility Analysis (FRFA) concerning the possible impact of the rule changes contained in this document and the Report and Order on small entities. The FRFA is set forth below.
                    </P>
                    <FTNT>
                        <P>
                            <SU>166</SU>
                             
                            <E T="03">See</E>
                             5 U.S.C. 604. The RFA, 5 U.S.C. 601-612. The RFA was amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (SBREFA), Public Law 104-121, Title II, 110 Stat. 857 (1996).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>167</SU>
                             5 U.S.C. 605(b).
                        </P>
                    </FTNT>
                    <P>
                        137. 
                        <E T="03">Paperwork Reduction Act of 1995 Analysis.</E>
                         This document contains new information collection requirements subject to the Paperwork Reduction Act of 1995 (PRA), Public Law 104-13. It will be submitted to the Office of Management and Budget (OMB) for review under section 3507(d) of the PRA.
                        <SU>168</SU>
                        <FTREF/>
                         OMB, the general public, and other Federal agencies will be invited to comment on the new information collection requirements contained in this proceeding. In addition, we note that, pursuant to the Small Business Paperwork Relief Act of 2002,
                        <SU>169</SU>
                        <FTREF/>
                         we previously sought, but did not receive, specific comment on how the Commission might further reduce the information collection burden for small business concerns with fewer than 25 employees. The Commission does not believe that the new information collection requirements in § 9.10(s)(4) and (5) will be unduly burdensome on small businesses. We describe impacts that might affect small businesses, which includes most businesses with fewer than 25 employees, in the FRFA below.
                    </P>
                    <FTNT>
                        <P>
                            <SU>168</SU>
                             44 U.S.C. 3507(d).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>169</SU>
                             Public Law 107-198, 116 Stat. 729 (2002) (codified at 44 U.S.C. 3506(c)(4)).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">III. Final Regulatory Flexibility Analysis</HD>
                    <P>
                        138. As required by the Regulatory Flexibility Act of 1980, as amended (RFA), an Initial Regulatory Flexibility Analysis (IRFA) was incorporated in the 
                        <E T="03">NPRM</E>
                         adopted in December 2022. The Commission sought written public comment on the proposals in the 
                        <E T="03">NPRM,</E>
                         including comments on the IRFA. No comments were filed addressing the IRFA. This Final Regulatory Flexibility Analysis (FRFA) conforms to the RFA.
                    </P>
                    <HD SOURCE="HD2">A. Need for, and Objectives of, the Final Rules</HD>
                    <P>
                        139. Technical limitations of legacy Enhanced 911 (E911) routing can result in a Commercial Mobile Radio Service (CMRS) provider routing a wireless 911 call to a Public Safety Answering Point (PSAP) other than the one designated by the relevant state or local 911 authority to receive calls from the actual location of the caller. Misroutes can occur for several reasons, including when more than one PSAP is within the coverage area of a cell site or sector. Such legacy tower-based routing results in approximately 12% of wireless 911 calls arriving at the incorrect PSAP for the caller's location. When a 911 call is misrouted, the answering telecommunicator must transfer the call to the PSAP that has jurisdiction to 
                        <PRTPAGE P="18515"/>
                        dispatch aid to the 911 caller's location, resulting in confusion and an estimated delay of a minute or more in dispatch and response. This delay can have deadly consequences. In addition, misroutes consume time and resources for both the transferring PSAP and the receiving PSAP. One national public safety organization estimates that these types of call transfers consume over 200,000 hours per year of excess 911 professional labor.
                    </P>
                    <P>140. In the Report and Order, the Commission adopted rules and procedures to require CMRS providers to implement location-based routing (LBR) for wireless 911 voice calls and real-time text (RTT) communications to 911 nationwide. With location-based routing as implemented under the Commission's rules, CMRS providers will use precise location information to route wireless 911 voice calls and RTT communications to 911 to the appropriate public safety answering point. For the millions of individuals seeking emergency assistance each year by wireless 911 voice call or RTT communication to 911, improving routing for these services will reduce emergency response time and save lives.</P>
                    <P>141. To facilitate the implementation of location-based routing for wireless 911 voice calls and RTT communications to 911, the Commission took the following actions:</P>
                    <P>
                        • The Commission required CMRS providers to deploy location-based routing technology for wireless 911 voice calls and RTT communications to 911 on their internet Protocol (IP)-based networks (
                        <E T="03">i.e.,</E>
                         4G LTE, 5G, and subsequent generations of IP-based networks). The Commission also required CMRS providers to use location-based routing to route wireless 911 voice calls and RTT communications to 911 originating on their IP-based networks when location information meets certain thresholds for accuracy and timeliness.
                    </P>
                    <P>• The Commission required CMRS providers to use location-based routing for wireless 911 voice calls and RTT communications to 911 when caller location information available to the CMRS provider's network at time of routing is ascertainable within a radius of 165 meters at a confidence level of at least 90%. In the absence of these conditions, CMRS providers must use alternative routing methods based on “best available” location information, which may include but is not limited to device-based or tower-based location information.</P>
                    <P>• The Commission adopted the proposed six-month timeline for nationwide CMRS providers to implement location-based routing for wireless 911 voice calls and provided twenty-four months for implementation by non-nationwide CMRS providers. In addition, the Commission provided 24 months for all CMRS providers to implement location-based routing for RTT communications to 911.</P>
                    <P>• The Commission required CMRS providers within 60 days of the applicable compliance deadlines to certify and submit evidence of compliance with location-based routing requirements and to certify the privacy of location information used for location-based routing. At that time, CMRS providers also must submit one-time live call data reporting specifying routing methodologies for calls in live call areas.</P>
                    <P>
                        • The Commission deferred consideration of proposals in the 
                        <E T="03">NPRM</E>
                         to require CMRS providers and covered text providers to implement location-based routing for Short Message Service (SMS) texts to 911.
                    </P>
                    <P>
                        • The Commission deferred consideration of proposals and issues raised in the 
                        <E T="03">NPRM</E>
                         concerning IP-formatted delivery of wireless 911 voice calls, texts, and associated routing information, for consideration in the Commission's pending Next Generation 911 (NG911) Transition docket (PS Docket No. 21-479, Facilitating Implementation of Next Generation 911 Services).
                    </P>
                    <HD SOURCE="HD2">B. Summary of Significant Issues Raised by Public Comments in Response to the IRFA</HD>
                    <P>142. There were no comments filed that specifically addressed the proposed rules and policies presented in the IRFA.</P>
                    <HD SOURCE="HD2">C. Response to Comments by the Chief Counsel for Advocacy of the Small Business Administration</HD>
                    <P>143. Pursuant to the Small Business Jobs Act of 2010, which amended the RFA, the Commission is required to respond to any comments filed by the Chief Counsel for Advocacy of the Small Business Administration (SBA), and to provide a detailed statement of any change made to the proposed rules as a result of those comments. The Chief Counsel did not file any comments in response to the proposed rules in this proceeding.</P>
                    <HD SOURCE="HD2">D. Description and Estimate of the Number of Small Entities to Which the Rules Will Apply</HD>
                    <P>144. The RFA directs agencies to provide a description of and, where feasible, an estimate of the number of small entities that may be affected by the rules adopted. The RFA generally defines the term “small entity” as having the same meaning as the terms “small business,” “small organization,” and “small governmental jurisdiction.” In addition, the term “small business” has the same meaning as the term “small business concern” under the Small Business Act.” A “small business concern” is one which: (1) is independently owned and operated; (2) is not dominant in its field of operation; and (3) satisfies any additional criteria established by the SBA.</P>
                    <P>
                        145. 
                        <E T="03">Small Businesses, Small Organizations, Small Governmental Jurisdictions.</E>
                         Our actions, over time, may affect small entities that are not easily categorized at present. We therefore describe, at the outset, three broad groups of small entities that could be directly affected herein. First, while there are industry specific size standards for small businesses that are used in the regulatory flexibility analysis, according to data from the Small Business Administration's (SBA) Office of Advocacy, in general a small business is an independent business having fewer than 500 employees. These types of small businesses represent 99.9% of all businesses in the United States, which translates to 33.2 million businesses.
                    </P>
                    <P>146. Next, the type of small entity described as a “small organization” is generally “any not-for-profit enterprise which is independently owned and operated and is not dominant in its field.” The Internal Revenue Service (IRS) uses a revenue benchmark of $50,000 or less to delineate its annual electronic filing requirements for small exempt organizations. Nationwide, for tax year 2020, there were approximately 447,689 small exempt organizations in the U.S. reporting revenues of $50,000 or less according to the registration and tax data for exempt organizations available from the IRS.</P>
                    <P>
                        147. Finally, the small entity described as a “small governmental jurisdiction” is defined generally as “governments of cities, counties, towns, townships, villages, school districts, or special districts, with a population of less than fifty thousand.” U.S. Census Bureau data from the 2017 Census of Governments indicate there were 90,075 local governmental jurisdictions consisting of general purpose governments and special purpose governments in the United States. Of this number, there were 36,931 general purpose governments (county, municipal, and town or township) with populations of less than 50,000 and 12,040 special purpose governments—independent school districts with 
                        <PRTPAGE P="18516"/>
                        enrollment populations of less than 50,000. Accordingly, based on the 2017 U.S. Census of Governments data, we estimate that at least 48,971 entities fall into the category of “small governmental jurisdictions.”
                    </P>
                    <HD SOURCE="HD1">IV. Telecommunications Service Providers</HD>
                    <HD SOURCE="HD2">A. Wireless Telecommunications Providers</HD>
                    <P>148. Pursuant to 47 CFR 9.10(a), the Commission's 911 service requirements are only applicable to CMRS providers, excluding mobile satellite service (MSS) operators, to the extent that they: (1) offer real-time, two way switched voice service that is interconnected with the public switched network; and (2) use an in-network switching facility that enables the provider to reuse frequencies and accomplish seamless hand-offs of subscriber calls. These requirements are applicable to entities that offer voice service to consumers by purchasing airtime or capacity at wholesale rates from CMRS licensees.</P>
                    <P>149. Below, for those services subject to auctions, we note that, as a general matter, the number of winning bidders that qualify as small businesses at the close of an auction does not necessarily represent the number of small businesses currently in service. Also, the Commission does not generally track subsequent business size unless, in the context of assignments or transfers, unjust enrichment issues are implicated.</P>
                    <P>
                        150. 
                        <E T="03">All Other Telecommunications.</E>
                         This industry is comprised of establishments primarily engaged in providing specialized telecommunications services, such as satellite tracking, communications telemetry, and radar station operation. This industry also includes establishments primarily engaged in providing satellite terminal stations and associated facilities connected with one or more terrestrial systems and capable of transmitting telecommunications to, and receiving telecommunications from, satellite systems. Providers of internet services (
                        <E T="03">e.g.,</E>
                         dial-up internet service providers (ISPs)) or Voice over internet Protocol (VoIP) services, via client-supplied telecommunications connections are also included in this industry. The SBA small business size standard for this industry classifies firms with annual receipts of $35 million or less as small. U.S. Census Bureau data for 2017 show that there were 1,079 firms in this industry that operated for the entire year. Of those firms, 1,039 had revenue of less than $25 million. Based on this data, the Commission estimates that the majority of “All Other Telecommunications” firms can be considered small.
                    </P>
                    <P>
                        151. 
                        <E T="03">Advanced Wireless Services (AWS)—(1710-1755 MHz and 2110-2155 MHz bands (AWS-1); 1915-1920 MHz, 1995-2000 MHz, 2020-2025 MHz and 2175-2180 MHz bands (AWS-2); 2155-2175 MHz band (AWS-3); 2000-2020 MHz and 2180-2200 MHz (AWS-4)).</E>
                         Spectrum is made available and licensed in these bands for the provision of various wireless communications services. Wireless Telecommunications Carriers (except Satellite) is the closest industry with an SBA small business size standard applicable to these services. The SBA small business size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated in this industry for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. Thus, under the SBA size standard, the Commission estimates that a majority of licensees in this industry can be considered small.
                    </P>
                    <P>152. According to Commission data as December 2021, there were approximately 4,472 active AWS licenses. The Commission's small business size standards with respect to AWS involve eligibility for bidding credits and installment payments in the auction of licenses for these services. For the auction of AWS licenses, the Commission defined a “small business” as an entity with average annual gross revenues for the preceding three years not exceeding $40 million, and a “very small business” as an entity with average annual gross revenues for the preceding three years not exceeding $15 million. Pursuant to these definitions, 57 winning bidders claiming status as small or very small businesses won 215 of 1,087 licenses. In the most recent auction of AWS licenses 15 of 37 bidders qualifying for status as small or very small businesses won licenses.</P>
                    <P>153. In frequency bands where licenses were subject to auction, the Commission notes that as a general matter, the number of winning bidders that qualify as small businesses at the close of an auction does not necessarily represent the number of small businesses currently in service. Further, the Commission does not generally track subsequent business size unless, in the context of assignments or transfers, unjust enrichment issues are implicated. Additionally, since the Commission does not collect data on the number of employees for licensees providing these services, at this time we are not able to estimate the number of licensees with active licenses that would qualify as small under the SBA's small business size standard.</P>
                    <P>
                        154. 
                        <E T="03">Competitive Local Exchange Carriers (LECs).</E>
                         Neither the Commission nor the SBA has developed a size standard for small businesses specifically applicable to local exchange services. Providers of these services include several types of competitive local exchange service providers. Wired Telecommunications Carriers is the closest industry with an SBA small business size standard. The SBA small business size standard for Wired Telecommunications Carriers classifies firms having 1,500 or fewer employees as small. U.S. Census Bureau data for 2017 show that there were 3,054 firms that operated in this industry for the entire year. Of this number, 2,964 firms operated with fewer than 250 employees. Additionally, based on Commission data in the 2022 Universal Service Monitoring Report, as of December 31, 2021, there were 3,378 providers that reported they were competitive local exchange service providers. Of these providers, the Commission estimates that 3,230 providers have 1,500 or fewer employees. Consequently, using the SBA's small business size standard, most of these providers can be considered small entities.
                    </P>
                    <P>
                        155. 
                        <E T="03">Incumbent Local Exchange Carriers (Incumbent LECs).</E>
                         Neither the Commission nor the SBA have developed a small business size standard specifically for incumbent local exchange carriers. Wired Telecommunications Carriers is the closest industry with an SBA small business size standard. The SBA small business size standard for Wired Telecommunications Carriers classifies firms having 1,500 or fewer employees as small. U.S. Census Bureau data for 2017 show that there were 3,054 firms in this industry that operated for the entire year. Of this number, 2,964 firms operated with fewer than 250 employees. Additionally, based on Commission data in the 2022 Universal Service Monitoring Report, as of December 31, 2021, there were 1,212 providers that reported they were incumbent local exchange service providers. Of these providers, the Commission estimates that 916 providers have 1,500 or fewer employees. Consequently, using the SBA's small business size standard, the Commission estimates that the majority of incumbent local exchange carriers can be considered small entities.
                    </P>
                    <P>
                        156. 
                        <E T="03">Broadband Personal Communications Service.</E>
                         The broadband personal communications services (PCS) spectrum encompasses 
                        <PRTPAGE P="18517"/>
                        services in the 1850-1910 and 1930-1990 MHz bands. The closest industry with an SBA small business size standard applicable to these services is Wireless Telecommunications Carriers (except Satellite). The SBA small business size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated in this industry for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. Thus, under the SBA size standard, the Commission estimates that a majority of licensees in this industry can be considered small.
                    </P>
                    <P>157. Based on Commission data as of November 2021, there were approximately 5,060 active licenses in the Broadband PCS service. The Commission's small business size standards with respect to Broadband PCS involve eligibility for bidding credits and installment payments in the auction of licenses for these services. In auctions for these licenses, the Commission defined “small business” as an entity that, together with its affiliates and controlling interests, has average gross revenues not exceeding $40 million for the preceding three years, and a “very small business” as an entity that, together with its affiliates and controlling interests, has had average annual gross revenues not exceeding $15 million for the preceding three years. Winning bidders claiming small business credits won Broadband PCS licenses in C, D, E, and F Blocks.</P>
                    <P>158. In frequency bands where licenses were subject to auction, the Commission notes that as a general matter, the number of winning bidders that qualify as small businesses at the close of an auction does not necessarily represent the number of small businesses currently in service. Further, the Commission does not generally track subsequent business size unless, in the context of assignments or transfers, unjust enrichment issues are implicated. Additionally, since the Commission does not collect data on the number of employees for licensees providing these, at this time we are not able to estimate the number of licensees with active licenses that would qualify as small under the SBA's small business size standard.</P>
                    <P>
                        159. 
                        <E T="03">Narrowband Personal Communications Services.</E>
                         Narrowband Personal Communications Services (
                        <E T="03">Narrowband PCS</E>
                        ) are PCS services operating in the 901-902 MHz, 930-931 MHz, and 940-941 MHz bands. PCS services are radio communications that encompass mobile and ancillary fixed communication that provide services to individuals and businesses and can be integrated with a variety of competing networks. Wireless Telecommunications Carriers (
                        <E T="03">except</E>
                         Satellite) is the closest industry with an SBA small business size standard applicable to these services. The SBA small business size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated in this industry for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. Thus, under the SBA size standard, the Commission estimates that a majority of licensees in this industry can be considered small.
                    </P>
                    <P>
                        160. According to Commission data as of December 2021, there were approximately 4,211 active 
                        <E T="03">Narrowband PCS</E>
                         licenses. The Commission's small business size standards with respect to 
                        <E T="03">Narrowband PCS</E>
                         involve eligibility for bidding credits and installment payments in the auction of licenses for these services. For the auction of these licenses, the Commission defined a “small business” as an entity that, together with affiliates and controlling interests, has average gross revenues for the three preceding years of not more than $40 million. A “very small business” is defined as an entity that, together with affiliates and controlling interests, has average gross revenues for the three preceding years of not more than $15 million. Pursuant to these definitions, 7 winning bidders claiming small and very small bidding credits won approximately 359 licenses. One of the winning bidders claiming a small business status classification in these 
                        <E T="03">Narrowband PCS</E>
                         license auctions had an active license as of December 2021.
                    </P>
                    <P>161. In frequency bands where licenses were subject to auction, the Commission notes that as a general matter, the number of winning bidders that qualify as small businesses at the close of an auction does not necessarily represent the number of small businesses currently in service. Further, the Commission does not generally track subsequent business size unless, in the context of assignments or transfers, unjust enrichment issues are implicated. Additionally, since the Commission does not collect data on the number of employees for licensees providing these services, at this time we are not able to estimate the number of licensees with active licenses that would qualify as small under the SBA's small business size standard.</P>
                    <P>
                        162. 
                        <E T="03">Offshore Radiotelephone Service.</E>
                         This service operates on several ultra high frequency (UHF) television broadcast channels that are not used for television broadcasting in the coastal areas of states bordering the Gulf of Mexico. Wireless Telecommunications Carriers (
                        <E T="03">except</E>
                         Satellite) is the closest industry with an SBA small business size standard applicable to this service. The SBA small business size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated in this industry for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. Thus, under the SBA size standard, the Commission estimates that a majority of licensees in this industry can be considered small. Additionally, based on Commission data, as of December 2021, there was one licensee with an active license in this service. However, since the Commission does not collect data on the number of employees for this service, at this time we are not able to estimate the number of licensees that would qualify as small under the SBA's small business size standard.
                    </P>
                    <P>
                        163. 
                        <E T="03">Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing.</E>
                         This industry comprises establishments primarily engaged in manufacturing radio and television broadcast and wireless communications equipment. Examples of products made by these establishments are: transmitting and receiving antennas, cable television equipment, Global Positioning System (GPS) equipment, pagers, cellular phones, mobile communications equipment, and radio and television studio and broadcasting equipment. The SBA small business size standard for this industry classifies businesses having 1,250 employees or less as small. U.S. Census Bureau data for 2017 show that there were 656 firms in this industry that operated for the entire year. Of this number, 624 firms had fewer than 250 employees. Thus, under the SBA size standard, the majority of firms in this industry can be considered small.
                    </P>
                    <P>
                        164. 
                        <E T="03">Rural Radiotelephone Service.</E>
                         Neither the Commission nor the SBA have developed a small business size standard specifically for small businesses providing Rural Radiotelephone Service. Rural Radiotelephone Service is radio service in which licensees are authorized to offer and provide radio telecommunication services for hire to subscribers in areas where it is not feasible to provide communication services by wire or other means. A significant subset of the Rural Radiotelephone Service is the Basic Exchange Telephone Radio System 
                        <PRTPAGE P="18518"/>
                        (BETRS). Wireless Telecommunications Carriers (
                        <E T="03">except</E>
                         Satellite) is the closest applicable industry with an SBA small business size standard. The SBA small business size standard for Wireless Telecommunications Carriers (
                        <E T="03">except</E>
                         Satellite) classifies firms having 1,500 or fewer employees as small. For this industry, U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated for the entire year. Of this total, 2,837 firms employed fewer than 250 employees. Thus, under the SBA size standard, the Commission estimates that the majority of Rural Radiotelephone Services firm are small entities. Based on Commission data as of December 27, 2021, there were approximately 119 active licenses in the Rural Radiotelephone Service. The Commission does not collect employment data from these entities holding these licenses and therefore we cannot estimate how many of these entities meet the SBA small business size standard.
                    </P>
                    <P>
                        165. 
                        <E T="03">Wireless Communications Services.</E>
                         Wireless Communications Services (WCS) can be used for a variety of fixed, mobile, radiolocation, and digital audio broadcasting satellite services. Wireless spectrum is made available and licensed for the provision of wireless communications services in several frequency bands subject to part 27 of the Commission's rules. Wireless Telecommunications Carriers (
                        <E T="03">except</E>
                         Satellite) is the closest industry with an SBA small business size standard applicable to these services. The SBA small business size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated in this industry for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. Thus, under the SBA size standard, the Commission estimates that a majority of licensees in this industry can be considered small.
                    </P>
                    <P>166. The Commission's small business size standards with respect to WCS involve eligibility for bidding credits and installment payments in the auction of licenses for the various frequency bands included in WCS. When bidding credits are adopted for the auction of licenses in WCS frequency bands, such credits may be available to several types of small businesses based average gross revenues (small, very small and entrepreneur) pursuant to the competitive bidding rules adopted in conjunction with the requirements for the auction and/or as identified in the designated entities section in part 27 of the Commission's rules for the specific WCS frequency bands.</P>
                    <P>167. In frequency bands where licenses were subject to auction, the Commission notes that as a general matter, the number of winning bidders that qualify as small businesses at the close of an auction does not necessarily represent the number of small businesses currently in service. Further, the Commission does not generally track subsequent business size unless, in the context of assignments or transfers, unjust enrichment issues are implicated. Additionally, since the Commission does not collect data on the number of employees for licensees providing these services, at this time we are not able to estimate the number of licensees with active licenses that would qualify as small under the SBA's small business size standard.</P>
                    <P>
                        168. 
                        <E T="03">Wireless Telecommunications Carriers (except Satellite).</E>
                         This industry comprises establishments engaged in operating and maintaining switching and transmission facilities to provide communications via the airwaves. Establishments in this industry have spectrum licenses and provide services using that spectrum, such as cellular services, paging services, wireless internet access, and wireless video services. The SBA size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms in this industry that operated for the entire year. Of that number, 2,837 firms employed fewer than 250 employees. Additionally, based on Commission data in the 2022 Universal Service Monitoring Report, as of December 31, 2021, there were 594 providers that reported they were engaged in the provision of wireless services. Of these providers, the Commission estimates that 511 providers have 1,500 or fewer employees. Consequently, using the SBA's small business size standard, most of these providers can be considered small entities.
                    </P>
                    <P>
                        169. 
                        <E T="03">Wireless Telephony.</E>
                         Wireless telephony includes cellular, personal communications services, and specialized mobile radio telephony carriers. The closest applicable industry with an SBA small business size standard is Wireless Telecommunications Carriers (except Satellite). The size standard for this industry under SBA rules is that a business is small if it has 1,500 or fewer employees. For this industry, U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. Additionally, based on Commission data in the 2022 Universal Service Monitoring Report, as of December 31, 2021, there were 331 providers that reported they were engaged in the provision of cellular, personal communications services, and specialized mobile radio services. Of these providers, the Commission estimates that 255 providers have 1,500 or fewer employees. Consequently, using the SBA's small business size standard, most of these providers can be considered small entities.
                    </P>
                    <P>
                        170. 
                        <E T="03">700 MHz Guard Band Licensees.</E>
                         The 700 MHz Guard Band encompasses spectrum in 746-747/776-777 MHz and 762-764/792-794 MHz frequency bands. Wireless Telecommunications Carriers (
                        <E T="03">except</E>
                         Satellite) is the closest industry with an SBA small business size standard applicable to licenses providing services in these bands. The SBA small business size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated in this industry for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. Thus, under the SBA size standard, the Commission estimates that a majority of licensees in this industry can be considered small.
                    </P>
                    <P>171. According to Commission data as of December 2021, there were approximately 224 active 700 MHz Guard Band licenses. The Commission's small business size standards with respect to 700 MHz Guard Band licensees involve eligibility for bidding credits and installment payments in the auction of licenses. For the auction of these licenses, the Commission defined a “small business” as an entity that, together with its affiliates and controlling principals, has average gross revenues not exceeding $40 million for the preceding three years, and a “very small business” an entity that, together with its affiliates and controlling principals, has average gross revenues that are not more than $15 million for the preceding three years. Pursuant to these definitions, five winning bidders claiming one of the small business status classifications won 26 licenses, and one winning bidder claiming small business won two licenses. None of the winning bidders claiming a small business status classification in these 700 MHz Guard Band license auctions had an active license as of December 2021.</P>
                    <P>
                        172. In frequency bands where licenses were subject to auction, the Commission notes that as a general matter, the number of winning bidders that qualify as small businesses at the 
                        <PRTPAGE P="18519"/>
                        close of an auction does not necessarily represent the number of small businesses currently in service. Further, the Commission does not generally track subsequent business size unless, in the context of assignments or transfers, unjust enrichment issues are implicated. Additionally, since the Commission does not collect data on the number of employees for licensees providing these services, at this time we are not able to estimate the number of licensees with active licenses that would qualify as small under the SBA's small business size standard.
                    </P>
                    <P>
                        173. 
                        <E T="03">Lower 700 MHz Band Licenses.</E>
                         The lower 700 MHz band encompasses spectrum in the 698-746 MHz frequency bands. Permissible operations in these bands include flexible fixed, mobile, and broadcast uses, including mobile and other digital new broadcast operation; fixed and mobile wireless commercial services (including frequency division duplex (FDD)- and time division duplex (TDD)-based services); as well as fixed and mobile wireless uses for private, internal radio needs, two-way interactive, cellular, and mobile television broadcasting services. Wireless Telecommunications Carriers (
                        <E T="03">except</E>
                         Satellite) is the closest industry with an SBA small business size standard applicable to licenses providing services in these bands. The SBA small business size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated in this industry for the entire year. Of this number, 2,837 firms employed fewer than 250 employees. Thus, under the SBA size standard, the Commission estimates that a majority of licensees in this industry can be considered small.
                    </P>
                    <P>174. According to Commission data as of December 2021, there were approximately 2,824 active Lower 700 MHz Band licenses. The Commission's small business size standards with respect to Lower 700 MHz Band licensees involve eligibility for bidding credits and installment payments in the auction of licenses. For auctions of Lower 700 MHz Band licenses the Commission adopted criteria for three groups of small businesses. A very small business was defined as an entity that, together with its affiliates and controlling interests, has average annual gross revenues not exceeding $15 million for the preceding three years, a small business was defined as an entity that, together with its affiliates and controlling interests, has average gross revenues not exceeding $40 million for the preceding three years, and an entrepreneur was defined as an entity that, together with its affiliates and controlling interests, has average gross revenues not exceeding $3 million for the preceding three years. In auctions for Lower 700 MHz Band licenses seventy-two winning bidders claiming a small business classification won 329 licenses, twenty-six winning bidders claiming a small business classification won 214 licenses, and three winning bidders claiming a small business classification won all five auctioned licenses.</P>
                    <P>175. In frequency bands where licenses were subject to auction, the Commission notes that as a general matter, the number of winning bidders that qualify as small businesses at the close of an auction does not necessarily represent the number of small businesses currently in service. Further, the Commission does not generally track subsequent business size unless, in the context of assignments or transfers, unjust enrichment issues are implicated. Additionally, since the Commission does not collect data on the number of employees for licensees providing these services, at this time we are not able to estimate the number of licensees with active licenses that would qualify as small under the SBA's small business size standard.</P>
                    <P>
                        176. 
                        <E T="03">Upper 700 MHz Band Licenses.</E>
                         The upper 700 MHz band encompasses spectrum in the 746-806 MHz bands. Upper 700 MHz D Block licenses are nationwide licenses associated with the 758-763 MHz and 788-793 MHz bands. Permissible operations in these bands include flexible fixed, mobile, and broadcast uses, including mobile and other digital new broadcast operation; fixed and mobile wireless commercial services (including FDD- and TDD-based services); as well as fixed and mobile wireless uses for private, internal radio needs, two-way interactive, cellular, and mobile television broadcasting services. Wireless Telecommunications Carriers (
                        <E T="03">except</E>
                         Satellite) is the closest industry with an SBA small business size standard applicable to licenses providing services in these bands. The SBA small business size standard for this industry classifies a business as small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that there were 2,893 firms that operated in this industry for the entire year. Of that number, 2,837 firms employed fewer than 250 employees. Thus, under the SBA size standard, the Commission estimates that a majority of licensees in this industry can be considered small.
                    </P>
                    <P>177. According to Commission data as of December 2021, there were approximately 152 active Upper 700 MHz Band licenses. The Commission's small business size standards with respect to Upper 700 MHz Band licensees involve eligibility for bidding credits and installment payments in the auction of licenses. For the auction of these licenses, the Commission defined a “small business” as an entity that, together with its affiliates and controlling principals, has average gross revenues not exceeding $40 million for the preceding three years, and a “very small business” an entity that, together with its affiliates and controlling principals, has average gross revenues that are not more than $15 million for the preceding three years. Pursuant to these definitions, three winning bidders claiming very small business status won five of the twelve available licenses.</P>
                    <P>178. In frequency bands where licenses were subject to auction, the Commission notes that as a general matter, the number of winning bidders that qualify as small businesses at the close of an auction does not necessarily represent the number of small businesses currently in service. Further, the Commission does not generally track subsequent business size unless, in the context of assignments or transfers, unjust enrichment issues are implicated. Additionally, since the Commission does not collect data on the number of employees for licensees providing these services, at this time we are not able to estimate the number of licensees with active licenses that would qualify as small under the SBA's small business size standard.</P>
                    <P>
                        179. 
                        <E T="03">Wireless Resellers.</E>
                         Neither the Commission nor the SBA have developed a small business size standard specifically for Wireless Resellers. The closest industry with an SBA small business size standard is Telecommunications Resellers. The Telecommunications Resellers industry comprises establishments engaged in purchasing access and network capacity from owners and operators of telecommunications networks and reselling wired and wireless telecommunications services (except satellite) to businesses and households. Establishments in this industry resell telecommunications and they do not operate transmission facilities and infrastructure. Mobile virtual network operators (MVNOs) are included in this industry. Under the SBA size standard for this industry, a business is small if it has 1,500 or fewer employees. U.S. Census Bureau data for 2017 show that 1,386 firms in this industry provided resale services during that year. Of that number, 1,375 firms operated with fewer than 250 employees. Thus, for this industry under the SBA small 
                        <PRTPAGE P="18520"/>
                        business size standard, the majority of providers can be considered small entities.
                    </P>
                    <HD SOURCE="HD2">B. Equipment Manufacturers</HD>
                    <P>
                        180. 
                        <E T="03">Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing.</E>
                         This industry comprises establishments primarily engaged in manufacturing radio and television broadcast and wireless communications equipment. Examples of products made by these establishments are: transmitting and receiving antennas, cable television equipment, GPS equipment, pagers, cellular phones, mobile communications equipment, and radio and television studio and broadcasting equipment. The SBA small business size standard for this industry classifies businesses having 1,250 employees or less as small. U.S. Census Bureau data for 2017 show that there were 656 firms in this industry that operated for the entire year. Of this number, 624 firms had fewer than 250 employees. Thus, under the SBA size standard, the majority of firms in this industry can be considered small.
                    </P>
                    <P>
                        181. 
                        <E T="03">Semiconductor and Related Device Manufacturing.</E>
                         This industry comprises establishments primarily engaged in manufacturing semiconductors and related solid state devices. Examples of products made by these establishments are integrated circuits, memory chips, microprocessors, diodes, transistors, solar cells and other optoelectronic devices. The SBA small business size standard for this industry classifies entities having 1,250 or fewer employees as small. U.S. Census Bureau data for 2017 show that there were 729 firms in this industry that operated for the entire year. Of this total, 673 firms operated with fewer than 250 employees. Thus, under the SBA size standard, the majority of firms in this industry can be considered small.
                    </P>
                    <HD SOURCE="HD2">C. Description of Projected Reporting, Recordkeeping, and Other Compliance Requirements for Small Entities</HD>
                    <P>182. The rules adopted to implement location-based routing for wireless 911 voice calls and RTT communications to 911 will impose new or additional reporting, recordkeeping, and/or other compliance obligations on small entities. Small and other CMRS providers are required to certify their compliance with the applicable location-based routing requirements, and inform the Commission of the specific network architecture, systems, and location validation procedures used to comply with the location-based routing requirements. More specifically, the adopted rules require small and other CMRS providers, within 60 days after their respective deadlines, to deploy location-based routing on their IP-based networks, and submit a one-time certification with substantiating evidence of compliance with location-based routing requirements applicable to them as of the deadline. As part of the certification, small and other CMRS providers must: (i) substantiate compliance by identifying specific network architecture, systems, location validation, and procedures used to comply with the location-based routing rules; (ii) collect and report aggregate information on the routing technologies for all live wireless 911 voice calls in the locations specified for live 911 call location data under the Commission's rule at 47 CFR 9.10(i)(3)(ii); and (iii) certify that location information used for location-based routing by service providers and third parties will only be used for valid 911 purposes. Small and other CMRS providers can request confidential treatment of any information they submit in accordance with the Commission's confidentiality rules.</P>
                    <P>
                        183. In the 
                        <E T="03">NPRM,</E>
                         the Commission sought comments on the proposals in this proceeding and requested cost and benefit information to help the Commission identify and evaluate relevant matters for small entities. Although several comments filed in response to the 
                        <E T="03">NPRM</E>
                         discussed categories of potential expenses to comply with location-based routing requirements, and any related reporting and recordkeeping requirements, with some asserting that there would be a greater burden on smaller providers, these comments and the record as a whole do not contain detailed information on costs required for either small or large entities. In fact, the Rural Wireless Association (RWA) and the Boulder Regional Emergency Telephone Service Authority (BRETSA) expressly indicated that neither non-nationwide nor small carriers have determined their implementation costs. Moreover, while stating that “[t]he $366,600 figure referenced in the NPRM may be a conservative estimate,” RWA did not provide an alternative to the Commission's estimate and noted that to date, RWA members have not received any specific vendor estimates regarding their actual cost of compliance.
                    </P>
                    <P>
                        184. In the 
                        <E T="03">NPRM,</E>
                         the Commission proposed an “upper bound” estimate for labor costs of $366,600 per CMRS provider, and for material costs such as software features or component upgrades for each CMRS provider, of $10,000 per PSAP. In response to the comments we received, we clarify that material costs estimated in the NPRM are not limited to those incurred at the PSAP, but also in the network core, and that the per PSAP calculation is a proxy for the size of the network that remains to be converted to location-based routing. Using the Commission's methodology in the 
                        <E T="03">NPRM,</E>
                         we estimate that CMRS providers collectively need to deploy location-based routing to a total of 14,366 PSAPs, resulting in the implied material cost of approximately $143.7 million.
                    </P>
                    <P>
                        185. Our total labor costs analysis added internal planning, outreach, and testing to the costs for equipment installation and conducting trials the Commission proposed and discussed in the 
                        <E T="03">NPRM.</E>
                         To better reflect the wide array of complex tasks that will be undertaken with highly skilled and senior staff, we will assume a higher wage for the workers than that assumed in the 
                        <E T="03">NPRM</E>
                         because some of the tasks involved will have to be undertaken by senior staff. Using the Bureau of Labor Statistics 75th percentile wage for network engineers, we assume worker compensation to be $81.29 per hour. Marking up hourly compensation by 45% to account for benefits results in a total hourly compensation estimate of $117.87. Assuming that work is completed over 26 work-weeks of five, 8 work-hour days, and a team of 10, the aggregate upper bound of work-hours would 10,400 and the total cost of those work-hours would be $1,225,853. While non-nationwide CMRS providers will have 24 months rather than six to implement location-based routing, smaller CMRS providers have constraints on the number of staff they can assign to any one project. In addition, while non-nationwide CMRS providers may take longer to implement location-based routing, assigning the same amount of work-time as nationwide CMRS providers represents both the spreading out of tasks over a longer period and an overestimate since non-nationwide CMRS providers have much smaller networks. Given that AT&amp;T has already implemented location-based routing, we estimate the labor cost associated with implementation for network for the 56 remaining providers, plus T-Mobile and Verizon, to be $71 million (≉ $1,225,853 × 58 providers = $71,099,474).
                    </P>
                    <P>
                        186. In addition to network costs, several commenters indicate that public safety-grade GIS data or shapefiles that precisely define PSAP boundaries should be developed or provided, though they differ on which parties should be responsible. We agree with 
                        <PRTPAGE P="18521"/>
                        NENA that it is the responsibility of providers to maintain their own jurisdictional maps. Accordingly, we assign the cost of maps to the providers. We anticipate that map costs will largely be labor to update already existing maps. To come up with a cost ceiling, we assume that every provider will need to update its maps, even though many providers likely have up-to-date maps. We anticipate that updating the map will only entail labor costs for mapping specialists to update maps. In the Supporting Document of Study Area Boundary Data Reporting in Esri Shapefile Format, the Office of Information and Regulatory Affairs estimates that it takes an average of 26 hours for a data scientist to modify a shapefile. We believe that 26 hours would be an upper bound of the time required for a party to update its maps. Given that the average wage rate is $60.44/hour for data scientists in the telecommunications industry, with a 45% markup for benefits, we arrive at $87.63 as the hourly compensation rate for a data scientist. We estimate an upper bound for the cost of map updating to be approximately $134,000 (≉ $87.63 per hour × 26 hours × 59 providers = $134,424.42).
                    </P>
                    <P>187. In addition, the one-time certification of compliance with our requirements together with the submission of data on call percentages by routing methods will impose a one-time cost on CMRS providers. As this required information should be available to each provider internally, we anticipate work to compile this information to take no longer than a week of five business days. We believe that one network engineer would be sufficient to complete this task in this time frame, resulting in a total provider cost of 40 work-hours. Assuming the same hourly labor cost of network engineers as in the previous cost estimate for network implementation, the total cost of reporting is $280,000 (≉ $117.87 per hour × 40 hours × 59 providers = $278,173.20).</P>
                    <P>188. Because we are adopting location-based routing requirements for RTT communications to 911, we also consider the costs for CMRS providers. Given that CMRS providers process and route RTT communications to 911 similarly to voice calls, we assume that CMRS providers' material and labor costs to deploy location-based routing for RTT are included in our cost estimates above. As part of this analysis, we note that as of the release date of the Report and Order, we are aware of only a small number of PSAPs that are receiving RTT communications.</P>
                    <P>189. In sum, we estimate upper bounds of the costs that CMRS providers will bear to be material costs of $143.7 million, network implementation costs of $71.1 million, GIS costs of $134,000, and certification costs of $280,000. Altogether, the upper bound of costs is approximately $215 million. We note that the three major CMRS providers (AT&amp;T, T-Mobile, and Verizon) have already implemented location-based routing for wireless 911 voice calls nationwide, or are in the process of implementing it. Although some commenters argue that this progress by three major carriers will not necessarily translate into reduced costs and greater efficiency for smaller providers to implement location-based routing, it appears that this progress by larger providers may have at least some measure of positive impact on implementation by smaller providers, such as by demonstrating potential implementation technologies and strategies, although they may be required to hire professionals to fulfill their compliance obligations.</P>
                    <P>190. The important public safety benefits that will result from the requirements the Commission adopted outweigh the associated implementation and compliance burdens for CMRS providers. The rule changes to implement nationwide location-based routing will significantly decrease misrouted wireless 911 calls and RTT communications to 911, reduce emergency response time, save lives, and save many PSAP personnel hours and resources lost in 911 transfers. Accordingly, these rule changes serve the public interest.</P>
                    <HD SOURCE="HD2">D. Steps Taken To Minimize the Significant Economic Impact on Small  Entities, and Significant Alternatives Considered</HD>
                    <P>191. The RFA requires an agency to provide “a description of the steps the agency has taken to minimize the significant economic impact on small entities . . . including a statement of the factual, policy, and legal reasons for selecting the alternative adopted in the final rule and why each one of the other significant alternatives to the rule considered by the agency which affect the impact on small entities was rejected.”</P>
                    <P>
                        192. In the previous section we described the significant public safety benefits to be achieved from requiring all CMRS providers to implement location-based routing for wireless 911 voice calls and RTT messages originating on IP-based networks on a nationwide basis. From the record in this proceeding, it appears to be technologically feasible for CMRS providers to implement location-based routing for a significant percentage of wireless 911 voice calls and RTT messages. In the Report and Order we expressly found that it is technologically feasible for all CMRS providers, nationwide and non-nationwide, to support location-based routing for a significant percentage of wireless 911 voice calls. The Commission considered comments advocating for a voluntary location-based routing approach to allow providers the flexibility which would take into account the differences in providers' networks, configurations and devices. We found, however, that implementing location-based routing on a voluntary basis is not consistent with the Commission's goal of ensuring that location-based routing is available to all wireless 911 callers on a nationwide basis. Accordingly, the rules we adopt require both nationwide and non-nationwide CMRS providers to implement location-based routing consistent with the proposals in the 
                        <E T="03">NPRM.</E>
                    </P>
                    <P>193. The Commission also considered a per-PSAP approach to implement location-based routing but determined that there could be uneven and inconsistent implementation in routing approaches between jurisdictions, and there was also a risk of 911 misroutes for jurisdictions that do not request location-based routing service. The Commission found that a per-PSAP approach was not consistent with its interest in facilitating improved routing of 911 voice calls, and was not in the public interest. Additionally, we determined this approach would impose unnecessary cost burdens on PSAPs to affirmatively request such service. The rules we adopted in the Report and Order were intended to be cost effective and minimally burdensome for small and other entities impacted by the rules. Below we discuss the specific steps the Commission has taken to minimize costs and reduce the economic impact for small entities, as well as various alternatives considered.</P>
                    <P>
                        194. Location-Based Routing Requirements. Consistent with the Commission's proposal in the 
                        <E T="03">NPRM</E>
                         and to reduce potential cost burdens for small and other wireless providers, our location-based routing rules apply only to wireless 911 voice calls and RTT communications originating on IP-based networks (
                        <E T="03">i.e.,</E>
                         4G LTE, 5G, and subsequent generations of IP-based networks). The record indicated that while nationwide CMRS providers are in the process of retiring or have completed the retirement of circuit-
                        <PRTPAGE P="18522"/>
                        switched, time-division multiplex (TDM) 2G and 3G networks, and some non-nationwide providers announced dates to sunset their 3G networks in 2022, the transition from these networks that are less compatible with location-based routing has not been fully completed. In the 
                        <E T="03">NPRM,</E>
                         the Commission tentatively concluded that requiring location-based routing for 911 calls or texts originating on TDM-based networks would be unduly burdensome, especially for non-nationwide providers who would bear the greatest burden, even if given additional time to comply with such a requirement. Moreover, although the Commission considered requiring location-based routing for all 911 calls, the Commission in the 
                        <E T="03">NPRM</E>
                         ultimately proposed to require location-based routing only for 911 calls originating on IP-based networks, 
                        <E T="03">i.e.,</E>
                         4G LTE, 5G, and subsequently deployed IP-based networks. In the Report and Order, the Commission adopted the proposed rule which will minimize some burdens and economic impact for small entities, particularly those that are non-nationwide providers, due to the limited scope of the requirement.
                    </P>
                    <P>
                        195. Rather than imposing a rigid location-based routing requirement, the rules the Commission adopted provide flexibility to small and other entities to route wireless 911 voice calls or RTT communications based on the best available location information (which may include cell tower coordinates or other information) when the location information available at time of routing does not meet either one or both of the rules' requirements for accuracy and timeliness. The Commission recognized the continued need for legacy E911 routing, at least as a fallback method, because accurate device location information is not available in all scenarios. Further, the Commission's requirement to default to best available location is consistent with the 
                        <E T="03">ATIS-0500039</E>
                         standard for location-based routing, which assumes that the fallback for location-based routing should be cell-sector routing for cases where no position estimate is available in time to be used for location-based routing, or the position estimates lack requisite accuracy. Our requirement is also consistent with current CMRS provider deployments of location-based routing, which default to legacy E911 routing when location does not meet CMRS providers' standards of accuracy and timeliness.
                    </P>
                    <P>196. The Report and Order also adopted baseline requirements involving the accuracy and timeliness of location information used for location-based routing that are consistent with industry standards. Under the rules adopted, CMRS providers must use location-based routing only if the location information is available to the provider network at the time the wireless 911 voice call or RTT communication is routed, and the information identifies the caller's horizontal location with a radius of 165 meters at a confidence level of at least 90%. These metrics are consistent with AT&amp;T's successful nationwide implementation of location-based routing, and received support as a model for other wireless carriers to implement location-based routing. In addition, the rule's confidence metric is consistent with ATIS's recommendation that uncertainty values for location-based routing “be standardized to a 90% confidence for effective call handling.” When location information does not meet the baseline accuracy and timeliness requirements, the adopted requirements allow CMRS providers to instead route based on best available location information, which may include device-based location information that does not meet the accuracy threshold, the centroid of the area served by the cell sector that first picks up the call, or other location information. This will help to minimize any significant economic impact on small entities and other CMRS providers.</P>
                    <P>
                        197. Compliance Timelines. The rules adopted in the Report and Order provide small and other providers flexibility in the compliance timelines to implement the location-based routing requirements, which should reduce the economic burden for small entities. The compliance timelines differ from those the Commission proposed in the 
                        <E T="03">NPRM,</E>
                         which provided different deadlines for nationwide CMRS providers and non-nationwide CMRS providers to implement location-based routing on their IP-based networks when available location information meets requirements for accuracy and timeliness. To further reduce the burden on small entities in the rules adopted, the Commission granted longer compliance timelines to non-nationwide CMRS providers than those proposed in the 
                        <E T="03">NPRM</E>
                         and eliminated the requirements for covered text providers that are not CMRS providers. Specifically, non-nationwide CMRS providers (which includes a substantial number of small entities) are required to implement location-based routing for wireless 911 voice calls within 24 months from the effective date of the final rules, rather than 18 months as proposed in the 
                        <E T="03">NPRM.</E>
                         Nationwide CMRS providers are required to implement location-based routing for wireless 911 voice calls within six months from the effective date of the final rules. For RTT, all CMRS providers are required to implement location-based routing for RTT messages where they implement RTT capability within 24 months from the effective date of the final rules, rather than the 12 months proposed in the 
                        <E T="03">NPRM.</E>
                    </P>
                    <P>198. The Commission has also minimized any significant economic impact on small entities by limiting the requirement to implement location-based routing to operators of IP-based networks only when certain requirements are met. Small entities are not required to comply with the location-based routing requirement if they do not operate an IP-based network, or if the location information available on the IP-based network does not meet either one or both of the requirements for timeliness and accuracy, in which case, small entities may use the best available location information for routing. Small entities will further benefit from the Commission's adoption of provisions that allow PSAPs and CMRS providers to enter into agreements that establish an alternate timeframe for meeting the location-based routing requirements. The flexibility to negotiate an alternative timeframe that meets a CMRS provider's business and financial needs is a significant step by the Commission that could minimize the economic impact for small entities.</P>
                    <P>
                        199. Reporting and Certification Requirements. The Commission considered the level of data collection, reporting, and certification, if any, that should be required from CMRS providers on location-based routing issues, weighing the potential burden of such requirements on small and other entities against the need to ensure compliance with the rules. The Commission also considered not adopting a certification requirement. However, absent a certification requirement, the Commission and the public would have no insight into providers' implementation of location-based routing. Furthermore, the Commission's ability to easily determine whether carriers are in compliance would be limited. Another alternative the Commission evaluated was adopting periodic reporting requirements. However, such ongoing reporting requirements have the potential to overburden providers, particularly small entities. Therefore, the rules adopted do not contain any periodic reporting requirements. We believe the one-time certification and 
                        <PRTPAGE P="18523"/>
                        live call data reporting requirement we adopt will be sufficient for providers to demonstrate location-based routing implementation. This limited data collection best balances the need for transparency on compliance with the limited ability of some providers, particularly small entities, to respond to mandatory data collections. The adopted certification requirement will also help provide important privacy and security protections, which we believe greatly outweigh any minor burden that this requirement might impose on small or other entities.
                    </P>
                    <P>
                        200. Deferral of Certain Proposed Rules and Removal From This Rulemaking Proceeding. In the Report and Order, the Commission deferred taking action on certain rules that were proposed in the 
                        <E T="03">NPRM.</E>
                         Specifically, in the 
                        <E T="03">NPRM</E>
                         the Commission proposed requiring covered text providers to implement location-based routing for all 911 texts originating on their IP-based networks when location information meets certain accuracy and timeliness requirements. In the Report and Order we required CMRS providers to deploy and use location-based routing only for RTT communications. We deferred action on requiring covered text providers to deploy and use location-based routing for other types of text messages to 911, such as Short Message Service (SMS). The Commission also proposed requiring CMRS and covered text providers to deliver 911 calls, texts, and associated routing information in IP format upon request of 911 authorities that have established the capability to accept NG911-compatible IP-based 911 communications. To align requirements for NG911 services amongst providers and avoid confusion among stakeholders, we deferred consideration of CMRS and covered text provider NG911 IP delivery requirements to the pending NG911 transition proceeding in PS Docket No. 21-479. Our deferral of the two proposed requirements above eliminated consideration of these rules from the current rulemaking proceeding. By eliminating these rules from the proceeding, the Commission has reduced the compliance costs for small entities and any related implementation burdens small entities may have incurred.
                    </P>
                    <HD SOURCE="HD2">E. Report to Congress</HD>
                    <P>
                        201. The Commission will send a copy of the Report and Order, including this FRFA, in a report to Congress pursuant to the Congressional Review Act. In addition, the Commission will send a copy of the Report and Order, including this FRFA, to the Chief Counsel for Advocacy of the SBA. A copy of the Report and Order and FRFA (or summaries thereof) will also be published in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                    <HD SOURCE="HD1">V. Ordering Clauses</HD>
                    <P>
                        1. Accordingly, 
                        <E T="03">it is ordered,</E>
                         pursuant to sections 1, 2, 4(i), 10, 201, 214, 222, 251(e), 301, 302, 303, 307, 309, 316, and 332, of the Communications Act of 1934, as amended, 47 U.S.C. 151, 152(a), 154(i), 160, 201, 214, 222, 251(e), 301, 302a, 303, 307, 309, 316, 332; the Wireless Communications and Public Safety Act of 1999, Public Law 106-81, 47 U.S.C. 615 note, 615, 615a, 615b; and section 106 of the Twenty-First Century Communications and Video Accessibility Act of 2010, Public Law 111-260, 47 U.S.C. 615c, that the Report and Order 
                        <E T="03">is adopted.</E>
                    </P>
                    <P>
                        2. 
                        <E T="03">It is further ordered</E>
                         that the amendments to part 9 of the Commission's rules, as set forth in Appendix A of the Report and Order, 
                        <E T="03">are adopted,</E>
                         effective sixty (60) days after publication in the 
                        <E T="04">Federal Register</E>
                        . Compliance will not be required for § 9.10(s)(4) and (5) until after approval by the Office of Management and Budget. The Commission delegates authority to the Public Safety and Homeland Security Bureau to publish a document in the 
                        <E T="04">Federal Register</E>
                         announcing that compliance date and revising § 9.10(s)(6).
                    </P>
                    <P>
                        3. 
                        <E T="03">It is further ordered</E>
                         that the Commission's Office of the Secretary, Reference Information Center, 
                        <E T="03">shall send</E>
                         a copy of the Report and Order, including the Final Regulatory Flexibility Analysis, to the Chief Counsel for Advocacy of the Small Business Administration.
                    </P>
                    <P>
                        4. 
                        <E T="03">It is further ordered</E>
                         that the Office of the Managing Director, Performance Program Management, 
                        <E T="03">shall send</E>
                         a copy of the Report and Order in a report to be sent to Congress and the Government Accountability Office pursuant to the Congressional Review Act, 5 U.S.C. 801(a)(1)(A).
                    </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 47 CFR Part 9</HD>
                        <P>Communications, Communications common carriers, Communications equipment, Internet, Radio, Reporting and recordkeeping requirements, Satellites, Security measures, Telecommunications, Telephone.</P>
                    </LSTSUB>
                    <SIG>
                        <FP>Federal Communications Commission.</FP>
                        <NAME>Marlene Dortch,</NAME>
                        <TITLE>Secretary, Office of the Secretary.</TITLE>
                    </SIG>
                    <HD SOURCE="HD1">Final Rules</HD>
                    <P>For the reasons discussed in the preamble, the Federal Communications Commission amends 47 CFR part 9 as follows:</P>
                    <PART>
                        <HD SOURCE="HED">PART 9—911 REQUIREMENTS</HD>
                    </PART>
                    <REGTEXT TITLE="47" PART="9">
                        <AMDPAR>1. The authority citation for part 9 continues to read as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>47 U.S.C. 151-154, 152(a), 155(c), 157, 160, 201, 202, 208, 210, 214, 218, 219, 222, 225, 251(e), 255, 301, 302, 303, 307, 308, 309, 310, 316, 319, 332, 403, 405, 605, 610, 615, 615 note, 615a, 615b, 615c, 615a-1, 616, 620, 621, 623, 623 note, 721, and 1471, and Section 902 of Title IX, Division FF, Pub. L. 116-260, 134 Stat. 1182, unless otherwise noted.</P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="47" PART="9">
                        <AMDPAR>2. Amend § 9.3 by adding definitions for “Device-based location information” and “Location-based routing” in alphabetical order to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 9.3 </SECTNO>
                            <SUBJECT>Definitions.</SUBJECT>
                            <STARS/>
                            <P>
                                <E T="03">Device-based location information.</E>
                                 Information regarding the location of a device used to call or text 911 generated all or in part from on-device sensors and data sources.
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Location-based routing.</E>
                                 The use of information regarding the location of a device, including but not limited to device-based location information, to deliver 911 calls and real-time text communications to point(s) designated by the authorized local or state entity to receive wireless 911 voice calls and real-time text communications to 911, such as an Emergency Services internet Protocol Network (ESInet) or PSAP, or to an appropriate local emergency authority.
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="47" PART="9">
                        <AMDPAR>3. Amend § 9.10 by revising paragraph (a) introductory text and adding paragraph (s) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 9.10 911 </SECTNO>
                            <SUBJECT>Service.</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Scope of this section.</E>
                                 Except as described in paragraph (r) of this section, the following requirements of paragraphs (a) through (s) of this section are only applicable to CMRS providers, excluding mobile satellite service (MSS) operators, to the extent that they:
                            </P>
                            <STARS/>
                            <P>
                                (s) 
                                <E T="03">Location-based routing requirements</E>
                                —(1) 
                                <E T="03">Wireless 911 voice calls.</E>
                                 (i) By November 13, 2024, nationwide CMRS providers must deploy a technology that supports location-based routing for wireless 911 voice calls on their internet Protocol-based networks (4G LTE, 5G, and subsequent generations of internet Protocol-based networks) nationwide. At that time, nationwide CMRS providers must route all wireless 911 voice calls originating on their internet Protocol-based networks pursuant to the requirements of paragraph (s)(3) of this section.
                                <PRTPAGE P="18524"/>
                            </P>
                            <P>(ii) By May 13, 2026, non-nationwide CMRS providers must deploy a technology that supports location-based routing for wireless 911 voice calls on their internet Protocol-based networks (4G LTE, 5G, and subsequent generations of internet Protocol-based networks). At that time, non-nationwide CMRS providers must route all wireless 911 voice calls originating on their internet Protocol-based networks pursuant to the requirements of paragraph (s)(3) of this section.</P>
                            <P>
                                (2) 
                                <E T="03">Real-time text communications to 911.</E>
                                 By May 13, 2026, CMRS providers must deploy a technology that supports location-based routing for real-time text communications to 911 originating on their internet-Protocol-based networks (4G LTE, 5G, and subsequent generations of internet Protocol-based networks). At that time, CMRS providers must route all real-time text communications to 911 originating on their internet Protocol-based networks pursuant to the requirements of paragraph (s)(3) of this section.
                            </P>
                            <P>
                                (3) 
                                <E T="03">Timeliness and accuracy threshold.</E>
                                 (i) Notwithstanding requirements for confidence and uncertainty described in paragraph (j) of this section, CMRS providers must use location information that meets the following specifications for routing wireless 911 voice calls and real-time text communications to 911 under paragraphs (s)(1) and (2) of this section:
                            </P>
                            <P>(A) The location information reports the horizontal location uncertainty level of the device within a radius of 165 meters at a confidence level of at least 90%; and</P>
                            <P>(B) The location information is available to the CMRS provider network at the time of routing the wireless 911 voice call or real-time text communication to 911.</P>
                            <P>(ii) When the location information does not meet either one or both of the requirements in paragraphs (s)(3)(i)(A) and (B) of this section, CMRS providers must route the wireless 911 voice call or real-time text communication to 911 based on the best available location information, which may include but is not limited to device-based location information that does not meet the requirements in paragraphs (s)(3)(i)(A) and (B), the centroid of the area served by the cell sector that first picks up the call, or other location information.</P>
                            <P>
                                (4) 
                                <E T="03">Certification and reporting.</E>
                                 Within 60 days after each benchmark specified in paragraphs (s)(1)(i) and (ii) and (s)(2) of this section, CMRS providers must comply with the following certification and reporting requirements.
                            </P>
                            <P>(i) CMRS providers must:</P>
                            <P>(A) Certify that they are in compliance with the requirements specified in paragraphs (s)(1)(i) and (ii) and (s)(2) of this section applicable to them;</P>
                            <P>(B) Identify specific network architecture, systems, and procedures used to comply with paragraphs (s)(1)(i) and (ii) and (s)(2) of this section, including the extent to which the CMRS provider validates location information for routing purposes and the validation practices used in connection with this information; and</P>
                            <P>(C) Certify that neither they nor any third party they rely on to obtain location information or associated data used for compliance with paragraph (s)(1)(i) or (ii) or (s)(2) of this section will use such location information or associated data for any non-911 purpose, except with prior express consent or as otherwise required by law. The certification must state that the CMRS provider and any third parties it relies on to obtain location information or associated data used for compliance with paragraph (s)(1)(i) or (ii) or (s)(2) have implemented measures sufficient to safeguard the privacy and security of such location information or associated data.</P>
                            <P>(ii) CMRS providers also must:</P>
                            <P>(A) Collect and report aggregate data on the routing technologies used for all live wireless 911 voice calls in the locations specified for live 911 call location data in paragraph (i)(3)(ii) of this section for a thirty-day period which begins on the compliance date(s) specified in paragraphs (s)(1)(i) and (ii) of this section. CMRS providers must retain live wireless 911 voice call data gathered pursuant to this section for a period of 2 years. CMRS providers must collect and report the following data, expressed as both a number and percentage of the total number of live wireless 911 voice calls for which data is collected pursuant to this section:</P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) Live wireless 911 voice calls routed with location-based routing using location information that meets the timeliness and accuracy thresholds defined in paragraphs (s)(3)(i)(A) and (B) of this section;
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) Live wireless 911 voice calls routed with location-based routing using location information that does not meet the timeliness or accuracy thresholds defined in paragraphs (s)(3)(i)(A) and (B) of this section; and
                            </P>
                            <P>
                                (
                                <E T="03">3</E>
                                ) Live wireless 911 voice calls routed using tower-based routing.
                            </P>
                            <P>
                                (5) 
                                <E T="03">Modification of deadlines by agreement.</E>
                                 Nothing in this section shall prevent PSAPs and CMRS providers from establishing, by mutual consent, deadlines different from those established for CMRS provider compliance in paragraphs (s)(1)(i) and (ii) and (s)(2) of this section. The CMRS provider must notify the Commission of the dates and terms of the alternate time frame within 30 days of the parties' agreement or June 11, 2024, whichever is later. The CMRS provider must subsequently notify the Commission of the actual date by which it comes into compliance with the location-based routing requirements in paragraph (s)(1)(i) or (ii) or (s)(2) within 30 days of that date or June 11, 2024, whichever is later. CMRS providers must file such notifications pursuant to this paragraph (s)(5) in PS Docket No. 18-64. The parties may not use this paragraph (s)(5) to delay compliance with paragraph (s)(1)(i) or (ii) or (s)(2) of this section indefinitely.
                            </P>
                            <P>
                                (6) 
                                <E T="03">Compliance dates.</E>
                                 Paragraphs (s)(4) and (5) of this section contain information collection and recordkeeping requirements. Compliance with paragraphs (s)(4) and (5) will not be required until after approval by the Office of Management and Budget. The Commission will publish a document in the 
                                <E T="04">Federal Register</E>
                                 announcing that compliance date and revising or removing this paragraph (s)(6) accordingly.
                            </P>
                        </SECTION>
                    </REGTEXT>
                </SUPLINF>
                <FRDOC>[FR Doc. 2024-03157 Filed 3-8-24; 4:15 pm]</FRDOC>
                <BILCOD>BILLING CODE 6712-01-P</BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
    <VOL>89</VOL>
    <NO>50</NO>
    <DATE>Wednesday, March 13, 2024</DATE>
    <UNITNAME>Presidential Documents</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="18525"/>
            <PARTNO>Part III</PARTNO>
            <PRES>The President</PRES>
            <PNOTICE>Notice of March 12, 2024—Continuation of the National Emergency With Respect to Iran</PNOTICE>
        </PTITLE>
        <PRESDOCS>
            <PRESDOCU>
                <PRNOTICE>
                    <TITLE3>Title 3—</TITLE3>
                    <PRES>
                        The President
                        <PRTPAGE P="18527"/>
                    </PRES>
                    <PNOTICE>Notice of March 12, 2024</PNOTICE>
                    <HD SOURCE="HED">Continuation of the National Emergency With Respect to Iran</HD>
                    <FP>On March 15, 1995, by Executive Order 12957, the President declared a national emergency pursuant to the International Emergency Economic Powers Act (50 U.S.C. 1701-1706) to deal with the unusual and extraordinary threat to the national security, foreign policy, and economy of the United States constituted by the actions and policies of the Government of Iran. On May 6, 1995, the President issued Executive Order 12959, imposing more comprehensive sanctions on Iran to further respond to this threat. On August 19, 1997, the President issued Executive Order 13059, consolidating and clarifying those previous orders. The President took additional steps pursuant to this national emergency in Executive Order 13553 of September 28, 2010; Executive Order 13574 of May 23, 2011; Executive Order 13590 of November 20, 2011; Executive Order 13599 of February 5, 2012; Executive Order 13606 of April 22, 2012; Executive Order 13608 of May 1, 2012; Executive Order 13622 of July 30, 2012; Executive Order 13628 of October 9, 2012; Executive Order 13645 of June 3, 2013; Executive Order 13716 of January 16, 2016, which revoked Executive Orders 13574, 13590, 13622, 13645, and provisions of Executive Order 13628; Executive Order 13846 of August 6, 2018, which revoked Executive Orders 13716 and 13628; Executive Order 13871 of May 8, 2019; Executive Order 13876 of June 24, 2019; Executive Order 13902 of January 10, 2020; and Executive Order 13949 of September 21, 2020.</FP>
                    <FP>The actions and policies of the Government of Iran—including its proliferation and development of missiles and other asymmetric and conventional weapons capabilities, its network and campaign of regional aggression, its support for terrorist groups, and the malign activities of the Islamic Revolutionary Guard Corps and its surrogates—continue to pose an unusual and extraordinary threat to the national security, foreign policy, and economy of the United States.</FP>
                    <FP>For these reasons, the national emergency declared on March 15, 1995, must continue in effect beyond March 15, 2024. Therefore, in accordance with section 202(d) of the National Emergencies Act (50 U.S.C. 1622(d)), I am continuing for 1 year the national emergency with respect to Iran declared in Executive Order 12957. The emergency declared by Executive Order 12957 constitutes an emergency separate from that declared on November 14, 1979, by Executive Order 12170, in connection with the hostage crisis. This renewal, therefore, is distinct from the emergency renewal of November 7, 2023.</FP>
                    <PRTPAGE P="18528"/>
                    <FP>
                        This notice shall be published in the 
                        <E T="03">Federal Register</E>
                         and transmitted to the Congress.
                    </FP>
                    <GPH SPAN="1" DEEP="80" HTYPE="RIGHT">
                        <GID>BIDEN.EPS</GID>
                    </GPH>
                    <PSIG> </PSIG>
                    <PLACE>THE WHITE HOUSE,</PLACE>
                    <DATE>March 12, 2024.</DATE>
                    <FRDOC>[FR Doc. 2024-05568 </FRDOC>
                    <FILED>Filed 3-12-24; 12:15 pm]</FILED>
                    <BILCOD>Billing code 3395-F4-P</BILCOD>
                </PRNOTICE>
            </PRESDOCU>
        </PRESDOCS>
    </NEWPART>
</FEDREG>
